(usagi-users 03666) Re: Problems with stateless autoconf tests ...

Heiko,
It may be that you need to send more than on DAD.  You could set it to a
number greater than one and retest.

Or it could be that the TN timed out too quickly to see the DAD from the
NUT.

Go to the "stateless-addrconf" directory of the test suite.  Look at the
file "LLA_DADSuccess.seq" and you will see that the error you get can be
caused by a timeout:

"TN received no DAD NS sent from NUT. It seems that NUT doesn't perform
DAD process." 

You can edit the "config.pl" file in this same directory and change the
time out values and retest.

Good luck,
Phil Bellino 

-----Original Message-----
From: Heiko Gerstung [mailto:[email protected]] 
Sent: Friday, May 12, 2006 7:46 AM
To: [email protected]
Subject: (usagi-users 03664) Re: Problems with stateless autoconf tests
...

>Heiko,
>Issue  "sysctl -a | grep accept_ra"
>If "net.ipv6.conf.eth0.accept_ra" (assuming eth0) is set to 0, then use

>the "sysctl" program to add the following:
>"net.ipv6.conf.eth0.accept_ra = 1" - Stateless autoconfiguration
>
>Issue  "sysctl -a | grep dad_transmits"
>If "net.ipv6.conf.eth0.dad_transmits" (assuming eth0) is set to 0, then

>use the "sysctl" program to add the following:
>"net.ipv6.conf.eth0.dad_transmits = 3" - Duplicate Address Detection 
>probes to send.
>
>Phil Bellino


Hi, Phil:

Thank you for your help. In fact, the two settings
(net.ipv6.conf.eth0.accept_ra and .dad_transmits) are both enabled (=1),
but no DAD_NS is detected. Any other possibilies?

Kind regards,
Heiko