RE: ipv6 stateless autoconfiguration failing
> -----Original Message-----
> From: Pascal Hambourg [mailto:pascal.mail@plouf.fr.eu.org]
> Sent: Sunday, August 15, 2010 1:45 AM
> To: debian-ipv6@lists.debian.org
> Subject: Re: ipv6 stateless autoconfiguration failing
>
> George Manousakis a écrit :
> >
> >>> The router was configured with those values:
> >>> ipv6 nd prefix default 180 120
> >> What are these numbers ? Valid and preferred lifetimes ?
> >
> > Yes, valid = 180 sec , pref = 120 sec
> [...]
> > The sequence was that I removed those lines from my cisco router and
> > rebooted the debian. When it was on, it got the global ipv6 correctly
> and
> > till now (10 hours later) it's still there.
>
> I guess that's because the router's default lifetime values apply now
> and are much longer (as radvd default values), so after hours the
> prefix
> is still valid. You can check it on the Debian box with "ip addr" which
> shows the current valid and preferred lifetimes.
>
Good point:
After almost a day the timers for the "old" ipv6 are:
valid_lft 2510166sec preferred_lft 522966sec
> > But it's not the correct one
> > anymore. The dynamic ip of me isp interconnection changed and so the
> /48
> > subnet that I could use via 6to4 tunneling.
> >
> > Router still sends the RA's with the correct prefix but debian just
> ignores
> > them!
>
> I expected this. An RA is accepted at startup, then something happens
> and further RA's are ignored.
>
> > linux:~# cat /proc/sys/net/ipv6/conf/all/forwarding
> > 1
> >
> > And then I changed the value to "0"
> >
> > The interface took immediately the new ipv6 address. Ok, it hasn't
> released
> > the old one but at least it took the new one and was able to ping
> > ipv6.google.com again.
> >
> > It's just odd because I remembered checking that value previously and
> find
> > it "0".
>
> When was "previously" ?
>
I can recall when exactly was that previously but I am afraid that it was
before installing quagga!
> > I didn't change it because the box only has one ipv6 enabled
> > interface so ipv6 forwarding is not an issue. I have no idea how the
> value
> > was set to "1"
>
> Maybe the routing daemon enabled IPv6 forwarding. In previous Debian
> releases, the radvd startup script enabled it if it was disabled.
>
That's exactly was is happening. When quagga is restarting both values for
forwarding (ipv4 and ipv6) are set to "1". And that happens even if ospf6d
is disabled. Still when you restart the routing suite the values are set to
"1" and autoconfiguration fails!
> > and of course I had no idea that by setting this value to "1"
> > autoconfiguration is disabled.
>
> It is described in Documentation/networking/ip-sysctl.txt in the kernel
> documentation.
>
> > Thank you for your help!
>
> You're welcome.
>
>
> --
> To UNSUBSCRIBE, email to debian-ipv6-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> Archive: 4C671C70.2040305@plouf.fr.eu.org">http://lists.debian.org/4C671C70.2040305@plouf.fr.eu.org
Reply to: