DragonFlyBSD

I can get `ping` to work when I flush the default route and add it again.

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.

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)

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.

Also, is it possible to mount a custom image from the Hetzner Cloud panel? I dont' see an option for that.

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.

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)

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).

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?

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" 

[...]

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.

I didn't know DHCP was supposed to work, I'll give it a try and see what's up.

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" 

yes,

dhcpcd_enable="YES"

alone works!

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.

"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)?

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`.

Ok, we will have to check route(8) then, there might be a bug that needs fixing there.