[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ipv6 stateless autoconfiguration failing



On Fri, 2010-08-13 at 18:22 +0300, George Manousakis wrote:
> Dear All,
> 
>  
> 
> 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.

As soon as you configure the box as a router, it will stop listening to
upstream router advertisements, on the assumption that it will have been
manually configured by that point.

While that's normally the desirable behaviour, it can be overridden by
setting the right values in /etc/sysctl.conf (/etc/sysctl.conf.d
perhaps) so that it continues to listen to router advertisements.


net.ipv6.conf.all.autoconf = 1

There's actually a bunch of those tweaks regarding exactly which part of
the router advertisement you might want it to listen to:

accept_ra
accept_ra_defrtr
accept_ra_pinfo
accept_ra_rt_info_max_plen
accept_ra_rtr_pref
accept_redirects
accept_source_route
...

I recommend reading the Linux kernel documentation for these in
Documentation/networking/ipv6.txt - it's all pretty clear which ones you
would / wouldn't need to set.

Also, in the example line above I've used '.all.', but of course you
probably want to narrow this down to a particular interface.  Hopefully
one you *know* that you control completely, so that no naughty person
could connect to it and spoof router advertisements at you, in order to
filter your traffic through their system.

Cheers,
					Andrew McMillan.

> 
>  
> 
> linux:~# dmesg | grep eth0
> 
>  
> 
> [    1.894066] eth0: Tigon3 [partno(BCM95704A6) rev 2002]
> (PCIX:133MHz:64-bit) MAC address 00:0b:db:95:18:cc
> 
> [    1.894074] eth0: attached PHY is 5704 (10/100/1000Base-T Ethernet)
> (WireSpeed[1])
> 
> [    1.894079] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0]
> TSOcap[1]
> 
> [    1.894083] eth0: dma_rwctrl[769f4000] dma_mask[64-bit]
> 
> [   27.186395] ADDRCONF(NETDEV_UP): eth0: link is not ready
> 
> [   28.737619] tg3: eth0: Link is up at 100 Mbps, full duplex.
> 
> [   28.737624] tg3: eth0: Flow control is on for TX and on for RX.
> 
> [   28.737828] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> 
>  
> 
>  
> 
> Why is that happening? What can I do about that? I cannot locate any
> logs regarding the ipv6 procedures.
> 
>  
> 
>  
> 
>  
> 
> Any ideas?
> 
>  
> 
> George Manousakis
> 
> 

-- 
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com                            +64(272)DEBIAN
                   You will outgrow your usefulness.
------------------------------------------------------------------------

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: