From: Pete Toscano <pete@research.netsol.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: linux ipv6 questions. bugs?
Date: Wed, 13 Dec 2000 14:45:58 -0500 [thread overview]
Message-ID: <20001213144558.L1139@tesla.admin.cto.netsol.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
i'm using test12 with ipv6 enabled. i'm seeing something strange, but i
can't tell if it's a linux or openbsd bug.
i have two boxes, one's running 2.4.0-test12 and the other's running
openbsd 2.8 (the same problem was seen with this machine using 2.7 too).
they are on a little ipv6 network, with a 125 bit prefix length.
i have two question, one short, one longer. i'll start with the short
one:
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? on the
openbsd box, i can ping6 ::1 just fine.
1. i can only ping6 the ipv6 address of the openbsd machine once i put
the openbsd box's ethernet interface into promisc mode (with tcpdump).
after that (and even once the openbsd box's eth is back in non-promisc
mode), i can ping6 the openbsd box fine. looking at a packet capture,
i see the neighbor solicitation packets from the linux box, but i
noticed something strange; in the ethernet header of the n.s. packets,
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. shouldn't this be the
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?
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
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2000-12-13 20:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 19:45 Pete Toscano [this message]
2000-12-13 20:27 ` linux ipv6 questions. bugs? kuznet
2000-12-13 21:25 ` Pete Toscano
2000-12-13 23:41 ` Pete Toscano
2000-12-14 17:40 ` kuznet
2000-12-14 19:11 ` Matthew G. Marsh
2000-12-14 19:24 ` kuznet
2000-12-14 12:10 ` Russell King
2000-12-14 19:31 ` kuznet
2000-12-14 19:37 ` Russell King
2000-12-14 19:46 ` kuznet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001213144558.L1139@tesla.admin.cto.netsol.com \
--to=pete@research.netsol.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox