[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. Ok, we will have to check route(8) then, there might be a bug that needs fixing there. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14385 * 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. Assignee deleted (tuxillo) debugged it further: route add 172.31.1.1/32 -iface vtnet0 will result in: add net 172.31.1.1: gateway vtnet0 while route add 172.31.1.1 -iface vtnet0 will result in add host 172.31.1.1: gateway vtnet0 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. Found the bug. So when I change: route add 172.31.1.1/32 -iface vtnet0 to route add 172.31.1.1 -iface vtnet0 it works! Might be a parsing problem in `route`. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14381 * 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
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: 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 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. "We" probably should :). I guess DragonFly uses a different "dhclient" than FreeBSD, so diffing is not an option. Is "dhclient" going to be deprecated in DragonFly, or why is there a working alterantive (dhcpcd)? Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14379 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. Nice! The question is now, should we find out what's the problem with dhclient? Because it might be uncovering at the very least a _route(8)_ issue. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14378 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. yes, dhcpcd_enable="YES" alone works! Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14377 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. It seems to be related with our dhclient, it's definitely route related becuase if I use the config below in my rc.conf I'll get the bug you're reporting. ifconfig_vtnet0="DHCP" However, if I just use dhcpcd, all seems to work fine, can you please try it? dhcpcd_enable="YES" Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14376 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. I didn't know DHCP was supposed to work, I'll give it a try and see what's up. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14375 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. Hi tuxillo, 1000x thanks! With your snippet above, it works! Now I can install things and maybe we can figure out why DHCP does not work properly. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14374 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. Can you please try this in your rc.conf? [...] static_routes="hetzner default" route_hetzner="172.31.1.1 -interface vtnet0" route_default="default 172.31.1.1" ifconfig_vtnet0="inet x.x.x.x netmask 255.255.255.255" [...] Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14373 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. I'd like to setup the routes manually (not via dhclient), but I am strugging with it. This is what I do: ifconfig vtnet0 inet 192.119.117.156 netmask 255.255.255.255 up route add -interface 172.31.1.1 vtnet0 route add default 172.31.1.1 But, it's not showing "link#1" in the Gateway field for route 172.31.1.1 (it is initially empty, and later shows the MAC address) as it does when this route is added via `dhclient`. Not sure what I am doing wrong? Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14372 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. File clipboard-202206140730-vzpkc.png added This error message might be of interest: rtsock: received more addr bits than sockaddrs. !clipboard-202206140730-vzpkc.png! Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14371 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. I also checked the integrity of the ISO image by doing an `dd if=/dev/cd0s0 bs=2k | md5` and it is correct (d41d8...27e; 6.2.1). Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14370 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. File clipboard-202206140707-0biu1.png added Some dmesg output: !clipboard-202206140707-0biu1.png! Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14369 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. I have to correct myself. It's possible to mount a custom ISO. You just need to ask the support to do it (the dragonfly ISO is a custom ISO) Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14368 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. No, it's not possible to mount a custom ISO image. But I asked the support, and ~30 minutes later, they had the DragonFly (dfly-...) image uploaded and made available!!! Kudos. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14367 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. Also, is it possible to mount a custom image from the Hetzner Cloud panel? I dont' see an option for that. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14366 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. I will try to use `kgdb` at the weekend. Yes, I think it's KVM. The "garbage" changes when I remove the routes and add them again. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14365 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by tuxillo. I wonder if those characters are garbage. Have you tried using kgdb to inspect the kernel structures? I don't know from the top of my head which ones are. I'm assuing that's a KVM VM (since it's using vtnet) Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14364 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. ah wait, no, I can't get `ping` to work. when I `route delete 172.31.1.1` and then `route add default 172.31.1.1` I have again two routes and one of them contains the strange characters in the Gateway column. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14363 * 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) -- 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
[DragonFlyBSD - Bug #3317] Network vtnet0 not working on Hetzner cloud
Issue #3317 has been updated by mneumann. I can get `ping` to work when I flush the default route and add it again. Bug #3317: Network vtnet0 not working on Hetzner cloud http://bugs.dragonflybsd.org/issues/3317#change-14362 * 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) -- 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
