Just did a quick test with hnet against ISC dhcp behaving the same
(IA_PD-only) and it worked out fine.
Am 03.05.2014 07:59, schrieb Steven Barth:
Hi Gert,
Am 02.05.2014 23:14, schrieb Gert Doering:
Hi,
On Fri, May 02, 2014 at 10:56:07PM +0200, Gert Doering wrote:
... so, something I am missing... :-/
Oh well. First thing is "I should have looked at 'ifstatus wan_6'"
which
indeed tells me "WAN is working":
root@OpenWrt:/etc/config# ifstatus wan_6
{
"up": false,
"pending": true,
"available": true,
"autostart": true,
"proto": "dhcpv6",
"device": "eth0",
"data": {
}
}
doesn't really look like working.
Questions :-)
- is hnetd intentionally ignoring the A-Bit in RA?
hnetd doesn't reimplement the dhcpv6-client it uses OpenWrt's internal
dhcpv6-protocol-handler.
So it behaves the same as if you had an interface with proto=dhcpv6
and option forceprefix 1. If it works with that you should be good to
go (unless there is a bug somewhere sigh)
And normally the dhcpv6 handler ignores O/M-bits and just asks for
IA_NA + IA_PD first in a solicit and when that fails (server returns
with NoAddrsAvail) tries with IA_PD-only which should succeed in your
case (don't know why it didn't though).
- what's the recommended config on the upstream side to make it work?
Remove the "O"-Bit? (I have that because I cannot send RFC6106 info
from IOS, so RA+stateless DHCP is what we currently use to get IPv6
addresses + DNS addresses into the client devices)
I'll try to confirm / fix a bug tomorrow or on monday. I could offer
you a workaround at the moment which is: Open
/lib/netifd/proto/hnet.sh and search for json_add_string proto dhcpv6
Below that insert a line:
json_add_string reqaddress none
which should disable it asking for an IA_NA alltogether.
thanks,
gert
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
