From: Noah Meyerhans <noahm@debian.org>
To: md@linux.it, linuxppc-dev@lists.linuxppc.org,
debian-powerpc@lists.debian.org
Cc: Noah Meyerhans <noahm@debian.org>
Subject: Re: IPv6 ND on PPC hardware
Date: Wed, 3 Jul 2002 11:31:08 -0400 [thread overview]
Message-ID: <20020703113108.H7563@morgul.net> (raw)
In-Reply-To: <20020703003931.GC7981@wonderland.linux.it>; from md@Linux.IT on Wed, Jul 03, 2002 at 02:39:31AM +0200
On Wed, Jul 03, 2002 at 02:39:31AM +0200, Marco d'Itri wrote:
> Yes, allmulti fixes it. Where else should I look?
Well, I definitely think you've found a card with broken multicast
support.
> 00:0c.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet LANCE] (rev 26)
You should probably contact the author of the driver and see if they
have anything to say about it. Many drivers don't implement multicast
correctly because the author doesn't use it and therefore can't test it.
> I do not think this is a hardware problem because the same thing happens
> on two twin machines (a couple of IBM B50).
What I meant by "hardware problem" is not a problem with your specific
card, but a problem with the chipset itself not doing the right thing.
Multicast support must be present and working in the hardware in order
for it to work in software. I don't know how common this type of
problem is, and I don't know if there's a way to get around it in
software.
noah
--
_______________________________________________________
| Web: http://web.morgul.net/~frodo/
| PGP Public Key: http://web.morgul.net/~frodo/mail.html=20
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-07-03 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 11:36 IPv6 ND on PPC hardware Marco d'Itri
2002-07-02 20:54 ` Noah Meyerhans
[not found] ` <20020703003931.GC7981@wonderland.linux.it>
2002-07-03 15:31 ` Noah Meyerhans [this message]
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=20020703113108.H7563@morgul.net \
--to=noahm@debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=md@linux.it \
/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).