ugh, bad form, i know, but i forgot this little dollop of information:
it looks like the incorrectly mac addressed n.s. packets are being fed
right back into the linux box's ip stack (as it sees an ethernet packet
with the destination set to its own mac address):
[root@nsv6 /root]# ping6 X:Y::1
PING X:Y::1(X:Y::1) from X:Y::4 : 56 data bytes
From ::1: Destination unreachable: Address unreachable
From ::1: Destination unreachable: Address unreachable
.
.
.
From ::1: Destination unreachable: Address unreachable
64 bytes from X:Y::1: icmp_seq=16 hops=64 time=433 usec
64 bytes from X:Y::1: icmp_seq=15 hops=64 time=1.000 sec
the pings start working when i put the X:Y::1 box's ethernet card
into promsc mode and it sees an ipv6 packet destined for one of its
multicast addresses. (i guess promsc mode tells the eth to just ignore
all link-level addressing info.)
pete
On Wed, 13 Dec 2000, Pete Toscano wrote:
>
> On Wed, 13 Dec 2000, kuznet@ms2.inr.ac.ru wrote:
>
> > Hello!
> >
> > > 0. whenever i ping6 the loopback interface (::1/128), all echo requests
> > > seem to be dropped and i get no echo replies. is this correct?
>
> > Your guess? 8) Of course, it is incorrect. I even have no idea
> > how it is possible to put system into such sad state.
>
> well, just power it on, it seems. but then again, this is just a guess.
> =;]
>
> > Though... probably, you forgot to up loopback.
>
> doesn't look it:
>
> [root@nsv6 /root]# ifconfig lo
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:7952 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> [root@nsv6 /root]# ping6 ::1
> PING ::1(::1) from ::1 : 56 data bytes
>
> --- ::1 ping statistics ---
> 156 packets transmitted, 0 packets received, 100% packet loss
>
> ...and this is right after boot.
>
> > > the destination mac address is set to the linux box's mac address and
> > > the source mac address is set to 0:0:0:0:0:0.
> >
> > I think it is consequence of above. When loopback interface is missing,
> > networking does not work.
> >
> >
> > > other way around? this would explain why the openbsd box doesn't
> > > respond to the linux box's n.s. until it starts looking at all the
> > > packets in promisc mode, right?
> >
> > Rather it means that openbsd is buggy, its stack accepts packets
> > not destined to it. It cannot react to those strange packets, which
> > you have just described.
>
> that may very well be, but shouldn't the neighbor solisitation packets
> from the linux box have the source mac address set to its mac address
> and the destination mac address set to 0:0:0:0:0:0 and not the other way
> around?
>
> thanks,
> pete
-- Pete Toscano p:sigsegv@psinet.com w:pete@research.netsol.com GPG fingerprint: D8F5 A087 9A4C 56BB 8F78 B29C 1FF0 1BA7 9008 2736
This archive was generated by hypermail 2b29 : Fri Dec 15 2000 - 21:00:27 EST