On Sun, 10 Mar 2002, Jan Oravec wrote:
> On Sat, Mar 09, 2002 at 08:40:17PM +0200, Pekka Savola wrote:
> > On Sat, 9 Mar 2002 kuznet@xxxxxxxxxxxxx wrote:
> > > Pekka, please, reread the report; they talk about _neigbour_
> > > _solicitations_.
> > > They have nothing to do either with ifp->probes, RS, DA or with addrconf.c
> > > at all. It is deal of ndisc.c/neghbour.c.
> >
> > Well, DAD *does* use neighbour solicitations. But the problem report was
> > indeed rather unclear; at least tcpdumps would have been nice.
>
> We hadn't log files until now, because this problem happens about once per
> 2-3 days.
>
> Here is example of tcpdump log...
>
> fe80::201:2ff:fedc:d28c is FreeBSD box
> fe80::3e18:401b is Linux box (2.4.18)
>
> after some time without any problem it started to answer with redirect
> instead of neighbor advertisement.
>
> #tcpdump -i gif0 -n icmp6
>
> 04:42:40.187050 fe80::201:2ff:fedc:d28c > fe80::3e18:401b: icmp6: neighbor
> sol: who has fe80::3e18:401b
> 04:42:40.223644 fe80::3e18:401b > fe80::201:2ff:fedc:d28c: icmp6: redirect
> fe80::3e18:401b to fe80::3e18:401b
> 04:42:40.224794 fe80::201:2ff:fedc:d28c > fe80::3e18:401b: icmp6: neighbor
> sol: who has fe80::3e18:401b
> 04:42:40.226296 fe80::201:2ff:fedc:d28c > fe80::201:2ff:fedc:d28c: icmp6:
> fe80::3e18:401b unreachable address
I think I've seen something similar to this before, and IIRC it was caused
by the fact that loopback interface had been brought down.
If loopback has been taken down and is back up, IIRC the addresses of the
interfaces must be "refreshed" (e.g. by also taking the interfaces down
and up).
HTH,
--
Pekka Savola "Tell me of difficulties surmounted,
Netcore Oy not those you stumble over and fall"
Systems. Networks. Security. -- Robert Jordan: A Crown of Swords
|