On Wed, Jul 01, 2015 at 07:24:25AM +0000, David Dahlberg wrote: > > No global inet6 address available. Looks like autoconf did not succeed. >
As I stated in my original message we are only supposed to recieve a default route via autoconf, not an IP address. The "Managed address configuration" flag is set in the RA, meaning IP assignment should be achieved in "some other way". In our case this is handled by DHCP6. Having a global address on the outside interface is not necessary in out case either, since the default route uses an fe80 address. > > defrouter_select: called unexpectedly (forwarding=1) > > nd6_ra_input: invalid prefixlen 48 for rfc2374 prefix > > XXXX:XXX:XXXX::, ignored > > === > > See? ;-) > >From the error message it is not obvious if it is only the prefix that is being ignored, or the RA as a whole. However, since disabling ip6 forwarding allowed the route to be created, the RA is still considered for other information. > > It is a common assumtion, that autoconf only works on /64 prefixes. > Even Wikipedia claimed this, citing the wrong RFC, which did not even > support their claim m( > > True is, that SLAAC is defined in RFC 4826, that it es defined > regardless of the prefix length, but /64 is assumed to be the usual > one. Also true is, hat OpenBSD seems to require a 64 bit prefix, just > like most other implementations. > > I cannot estimate, how much work it would be to support other prefix > lengths (e.g. as EUI-64 cannot be uses on non-64-bit prefixes) and > whether or not it is a worthwhile target to persue. > There indeed seems to be some confusion how v6 should behave in the real world as opposed to (some) papers. This is one of the reasons I wanted to lift the issues with the mailing list. -- Patrik Lundin
