Re: ipv6 stateless autoconfiguration failing
George Manousakis a écrit :
> If I recall correctly though a trace on the Broadcom interface indicated
> that RA's were received from the router.
In my experience, the kernel logs a message ("<interface>: no IPv6
routers present") when stateless autoconfiguration is enabled and no
RA's are received, but is silent when RA's are received.
> Anyway, I did a check triggered by your comment of the prefix lifetime.
>
> The router was configured with those values:
> ipv6 nd prefix default 180 120
What are these numbers ? Valid and preferred lifetimes ?
> ipv6 nd ra interval 10
>
> and that's because I use a 6to4 tunnel to "simulate" my ipv6 connectivity
> and I have a dynamic ipv4 from my isp. So I want the information of the
> change of the ip to be propagated ASAP.
>
> When I removed those lines from the router the debian host took the ipv6
> address and hold it.
What do you mean exactly ? Did the Debian host take a global IPv6
address without rebooting, after it initially took and lost it ?
> Then I reinserted the commands in the router. Debian did nothing.
Again, what do you mean exactly ?
> But when I caused a renewal of my public ipv4 the router found out about the
> change and reconfigured the general prefix but it seems that debian is
> ignoring the new RA's.
After or without rebooting ?
It seems to have stuck with the old global ipv6 and
> of course no ipv6 destination is reachable.
>
> I still cannot find any information on the debian regarding the timers or
> logs of the autoconfigured ipv6.
Stateless autoconfiguration is done entirely by the kernel (except the
processing of the RDNSS option which requires some userland), so it is
not Debian specific. It is controlled by a set of per-interface sysctl
parameters, in net.ipv6.conf.<interface>, see
Documentation/ip-sysctl.txt for information.
> I don't know if there has anything to do but I am mentioning about this
> since it's an ipv6 operation: on my debian host I run quagga with zebra,
> bgpd, ospfd and ospf6d
Is IPv6 forwarding enabled ? If so, this disables stateless
autoconfiguration. (And by the way IPv6-wise the box is a router, not a
host.)
Reply to: