Markus Stenberg
Markus Stenberg
I accepted the PR, as it looks good enough (I would have done it perhaps slightly differently, e.g. detect the IPv4/IPv6 reverse domains it is trying to avoid).
This is odhcpd bug (hnetd ULAs will not get given to clients currently if GUA is up); will be fixed sooner or later by sbyx (assigned).
http://employees.org/~mstenber/x/logs.tgz
Hmm. Is there some configuration option on per-interface basis that would disable this, I wonder.. At least based on http://wiki.openwrt.org/doc/uci/network it does not seem possible unfortunately.
This seems like client-side issue; DHCPv6 client is not using ip -6 route replace (or change), but instead doing del + add, and for some reason that seems to take...
Aha. We identified problem in the bundled (generic) dhcpv6.script at least (it removes + adds addresses -> potential time for NUD etc). Given OpenWrt client, this should not happen, but...
I will declare victory. Reopen if the problem persists with sbyx's patch ;)
To me it sounds as if you had some non-homenet-aware DHCP server on eth1 and it does (completely logically) assume it is upstream and therefore does no assignments on it....
Do valid/preferred lifetimes get updated? That might cause it at least.
Linux loopback used to have some issues (hardcoded routing/firewalling logic associated with it). Not sure if that is the case still.