From: "J. K. Cliburn" <jcliburn@gmail.com>
To: David Madore <david.madore@ens.fr>
Cc: Linux Kernel Mailing-List <linux-kernel@vger.kernel.org>,
Linux NetDev Mailing-List <netdev@vger.kernel.org>,
atl1-devel@lists.sourceforge.net
Subject: Re: atl1e Ethernet driver not seeing packets sent to 33:33:00:00:00:01 multicast
Date: Tue, 11 Nov 2008 08:06:11 -0600 [thread overview]
Message-ID: <20081111080611.7f6d4371@osprey.hogchain.net> (raw)
In-Reply-To: <20081111133108.GA7124@clipper.ens.fr>
On Tue, 11 Nov 2008 14:31:08 +0100
David Madore <david.madore@ens.fr> wrote:
> Hi,
>
> This is on Ubuntu 8.10 "Intrepid Ibex" using its stock kernel
> (2.6.27-7.16), with an Eee PC 901 whose Ethernet adapter is (according
> to lspci):
>
> 04:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit
> Ethernet Adapter (rev b0)
Just to verify your system is fitted with the L1e and not the L1 chip,
can you please provide the output of lspci -vvnn?
>
> using driver atl1e of said kernel.
>
> _Unless_ the network device is put in promiscuous mode (e.g., by
> running tcpdump), it does not see packets sent to Ethernet multicast
> address 33:33:00:00:00:01. E.g., IPv6 packets to ff02::1
> (ip6-allnodes) are not seen.
>
> Practical consequence: IPv6 is broken, because router advertisements
> are not received.
>
> ("ip maddr show" does give "link 33:33:00:00:00:01" among the
> subscribed multicast addresses, so it's not a config problem.)
>
> Is this a known problem? Is there a patch fixing it?
>
> Until then, a workaround is to put the device in promiscuous mode.
>
> Happy hacking,
>
next prev parent reply other threads:[~2008-11-11 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 13:31 atl1e Ethernet driver not seeing packets sent to 33:33:00:00:00:01 multicast David Madore
2008-11-11 14:06 ` J. K. Cliburn [this message]
2008-11-11 15:59 ` David Madore
2008-11-11 16:08 ` J. K. Cliburn
2008-11-11 22:00 ` David Madore
2008-11-12 0:13 ` J. K. Cliburn
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=20081111080611.7f6d4371@osprey.hogchain.net \
--to=jcliburn@gmail.com \
--cc=atl1-devel@lists.sourceforge.net \
--cc=david.madore@ens.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).