[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
bugtracker-admin at leaf.dragonflybsd.org
bugtracker-admin at leaf.dragonflybsd.org
Fri Jun 17 02:38:31 PDT 2022
Issue #3317 has been updated by mneumann.
File clipboard-202206171102-blgae.png added
There is `/sbin/dhclient-script` which is invoked with the following env variables set:
!clipboard-202206171102-blgae.png!
I could image that this script is doing something wrong.
The script is calling the following commands:
<pre><code class="shell">
ifconfig vtnet0 inet 168.119.117.156 netmask 255.255.255.255 broadcast 168.119.117.156
route add 172.31.1.1/32 -iface vtnet0
route add default 172.31.1.1
</code></pre>
after afterwards one of the routes shows up scrabled, as in the original bug report.
I tried to enter exactly the same commands as dhclient-script produces, and voila I end up with the same scrabled route entry. So, it's not the fault of `dhclient`!!!
----------------------------------------
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14380
* Author: mneumann
* Status: New
* Priority: Normal
* Category: Networking
* Target version: 6.4
* Start date: 2022-06-09
----------------------------------------
After running `dhclient vtnet0`, I cannot ping anything except the default gateway (172.31.1.1).
`route show` shows two entries for the default route (172.31.1.1) and
one contains *very* strange characters:
!clipboard-202206091711-dw2gp.png!
(See the second line for 172.31.1.1...)
---Files--------------------------------
clipboard-202206091711-dw2gp.png (69.3 KB)
clipboard-202206140707-0biu1.png (326 KB)
clipboard-202206140730-vzpkc.png (302 KB)
clipboard-202206171102-blgae.png (66 KB)
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs
mailing list