Hello,
I have the same issue.
I never cared about IPv6 so the rest is only IPv4 relevant.
I used hetzner from 6.2 to 6.5 without issues. Starting with 6.6 IPv4 does
not work out of the box and needs the suggested workaround. This includes
system upgraded with sysupgrade, system upgraded with install cd/upgrade and
also fresh installation of new system (I reproduced this with all three
methods on hetzner).
In case of installer upgrade or installer fresh install the installation
fails when the vio0 is configured. kernel prints "arpresolve: 172.31.1.1:
route contains no arp information" and the installation sets are not
accessible through http.
In case of sysupgrade the system upgrade finishes ok (as the sets are
downloaded with 6.5), but the resulting system is not accessible with ssh,
ping or anything. Neither can anything outside be accessed from the inside
("ping google.com" fails). But from hetzner web console it is still possible
to run:
> route del default 172.31.1.1
> route add default 172.31.1.1
or to add these in rc.local and then the "arpresolve: 172.31.1.1: route
contains no arp information" stops to be added to dmesg and networking
returns to normal.
In my tests (and ignoring IPv6) the -soii in hostname.vio0 makes no
difference.
Regards
Vaclav Synacek
--
Sent from:
http://openbsd-archive.7691.n7.nabble.com/openbsd-dev-bugs-f183916.html
