[radvd-devel-l] Problem----Down one interface,Up another!

Greg Daley greg.daley at eng.monash.edu.au
Wed Sep 7 01:44:56 EDT 2005

Hi Nathan,

Sorry for the late reply.

Nathan Lutchansky wrote:
> Hash: SHA1
> On Thu, 18 Aug 2005, John wrote:
>>No.   Time       Source                  Destination  Protocol  Info
>>1304 73.970193  fe80::20a:ebff:fe9b:fada  ff02::1     ICMPv6   Router advertisement
>>No.   Time       Source                  Destination  Protocol  Info
>>1305 74.019727  ::                        ff02::16    ICMPv6  Unknown (0xce) (Unknown (0x00))
>>No.   Time       Source                  Destination  Protocol   Info
>>1306 74.699676  ::                        ff02::16    ICMPv6  Unknown (0xce) (Unknown (0x00))
>>No. Time         Source                  Destination  Protocol   Info
>>1307 74.870249  fe80::20a:ebff:fe98:68b7  ff02::1     ICMPv6 Router advertisement
>>     We can see,the interval between last RA from eth1 and first RA from eth2 is nearly 
>>1s. Can this interval be reduced?How?
> The router just sent an RA (1304) only 50 msec before getting the RS, and
> routers won't reply to an RS immediately if they have sent an RA recently.
> You can change this delay with MinDelayBetweenRAs in radvd.conf, but you
> really should have a good reason for doing so.

Indeed.   There are reasons and means to do this outlined in RFC 3775 
(Mobile IPv6), but there are serious overhead issues which reduce its

>>    And what the destination--ff02::16 mean?Can it be eliminated?
> Why? ff02::16 is the well-known address for router discovery...  -Nathan

Actually, ff02::16 is the well known multicast group for MLDv2.
The groups for solicited nodes' addresses (and ff02::2 - all routers -
if it is a router) are being joined when the interface is being
brought up.

These messages aren't associated with router discovery (except 


More information about the radvd-devel-l mailing list