RE: ipv6 stateless autoconfiguration failing
The bridge was not started by default. I thought that it might cause me
problems so I only started the virtual machine (and of course the bridge)
after the global ipv6 was lost.
If I recall correctly though a trace on the Broadcom interface indicated
that RA's were received from the router.
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
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.
Then I reinserted the commands in the router. Debian did nothing.
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. 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.
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
-----Original Message-----
From: Pascal Hambourg [mailto:pascal.mail@plouf.fr.eu.org]
Sent: Saturday, August 14, 2010 3:10 AM
To: debian-ipv6@lists.debian.org
Subject: Re: ipv6 stateless autoconfiguration failing
George Manousakis a écrit :
> The global ipv6 address is lost at about 5 minutes after booting.
Does it match the prefix lifetime advertised in the RA's ?
> There are no ip6tables rules installed.
>
> Router advertisments are received correctly and I found out about this
with
> two tests:
> a) I used whireshark to see the ipv6 packets from where I saw the ra
packets
> arriving
> b) I boot a windows virtual machine via virtualbox using a bridged
interface
> and the virtual machine got a ipv6 address with no problem.
Was the Broadcom interface bridged from the start or did you bridge it
after it lost its IPv6 global address in order to run the virtual
machine ? Bridged interfaces on the host cannot receive RA's, only the
bridge interface can, unless special ebtables rules are installed.
> Is there a way to trigger manually to install a global ipv6 address via
> autoconfiguration? I tried ifdown, ifup still with no success.
This means that something has changed since the interface was first
brought up.
>
> -----Original Message-----
> From: Pascal Hambourg [mailto:pascal.mail@plouf.fr.eu.org]
> Sent: Friday, August 13, 2010 11:58 PM
> To: debian-ipv6@lists.debian.org
> Subject: Re: ipv6 stateless autoconfiguration failing
>
> Hello,
>
> George Manousakis a écrit :
>> I have configured my router to advertise its ipv6 prefix and the nd
>> packets are received for the debian host updated with the testing
> packages.
>> Just after the boot the interface "Broadcom Corporation NetXtreme
>> BCM5704 Gigabit Ethernet" is getting a global ipv6 address correctly but
>> after a while the address is lost and on the interface only the link
>> local address remains.
>
> "A while" being what kind of delay ? Seconds, minutes, hours, days ?
>
>> Why is that happening?
>
> Maybe because the host does not receive router advertisements any more.
> Maybe ip6tables rules drop them.
>
>
--
To UNSUBSCRIBE, email to debian-ipv6-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Archive: 4C65DEBC.4080209@plouf.fr.eu.org">http://lists.debian.org/4C65DEBC.4080209@plouf.fr.eu.org
Reply to: