[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3317 has been updated by mneumann.

Assignee deleted (tuxillo)

debugged it further:

<pre><code class="shell">
route add 172.31.1.1/32 -iface vtnet0
</code></pre>

will result in:

<pre>
add net 172.31.1.1: gateway vtnet0
</pre>

while

<pre><code class="shell">
route add 172.31.1.1 -iface vtnet0
</code></pre>

will result in 

<pre>
add host 172.31.1.1: gateway vtnet0
</pre>


An IP with /32 doesn't really look like a network to me. Maybe something is going havoc in the kernel if a network with /32 is given?

----------------------------------------
Bug #3317: Network vtnet0 not working on Hetzner cloud
http://bugs.dragonflybsd.org/issues/3317#change-14383

* Author: mneumann
* Status: In Progress
* 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