Date: Thu, 23 Aug 2001 10:39:45 -0700 (PDT) From: wpaul@FreeBSD.ORG (Bill Paul) To: francois.tigeot@nic.fr (Francois Tigeot) Cc: freebsd-net@FreeBSD.ORG Subject: Re: Problem with IPv6 autoconfiguration and DFE-550TX Message-ID: <20010823173945.3E56137B405@hub.freebsd.org> In-Reply-To: <20010823120933.A87977@brazil.nic.fr> from Francois Tigeot at "Aug 23, 2001 12:09:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi,
>
> IPv6 autoconfiguration with -STABLE and Dlink DFE-550TX network adapters is
> not working as it should.
>
> My network topology is simple : 3 machines on the same ethernet segment,
> connected by a 10/100 hub. They are running 4.4-RC as of today and use the
> same NIC, a Dlink DFE-550TX (ste driver).
I need you do "pciconf -l | grep ste" so that I can see which revision
of the Sundance Technologies "alta" chip you have on your card. I have
samples of these cards (which I used to write the driver) but they're
old. I want to be sure this problem isn't due to behavioral differences
between your chip rev and mine.
> Here are some tcpdump results observed after running a single 'rtsol' command
> on the client:
For the record, the best way to run tcpdump is:
# tcpdump -n -e -i foo0
This will show you the ethernet frame header, which is sort of important
when you're trying to debug an ethernet problem. In this case, had you
used the -e flag, we would have seen that the problem is you aren't
receiving multiast packets, or at least certain multicast packets.
Forcing the NIC into promisc mode gets around the problem, but the
real issue is that the multicast filter isn't being programmed
correctly. This is usually one of the things I test during driver
development though, so I'm a little confused to see that it's not
working now. (It should have been working before, or I would not have
committed the driver.)
I'm going to stick one of my sample DFE-550TX cards in a test box
in the lab and see if I can duplicate this problem, but it would help
if you could run tcpdump -n -e -i ste0 so that we can see just what
multicast address the NIC should be receiving.
> Is this a known problem with the ste driver ?
Ok, you know, I'm getting tired of people asking this question. It
makes it sound like I leave bugs lying around just for people to
trip on. If I knew about this problem, I would have fixed it.
> How can I be sure the client does not receive the advertisement without
> running tcpdump ?
You can also run tcpdump -n -e -p -i ste0. The -p flag means "don't
put the interface into promisc mode."
-Bill
--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wpaul@windriver.com | Wind River Systems
=============================================================================
"I like zees guys. Zey are fonny guys. Just keel one of zem." -- The 3 Amigos
=============================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010823173945.3E56137B405>