From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com
Cc: svallet@gmail.com
Subject: Fw: [Bugme-new] [Bug 4482] New: natsemi: incorrect initialization of IPv6 Neighbor-discovery multicast
Date: Wed, 13 Apr 2005 10:36:42 -0700 [thread overview]
Message-ID: <20050413103642.172d3976.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Wed, 13 Apr 2005 07:19:38 -0700
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 4482] New: natsemi: incorrect initialization of IPv6 Neighbor-discovery multicast
http://bugme.osdl.org/show_bug.cgi?id=4482
Summary: natsemi: incorrect initialization of IPv6 Neighbor-
discovery multicast
Kernel Version: 2.6.11.7
Status: NEW
Severity: normal
Owner: jgarzik@pobox.com
Submitter: svallet@gmail.com
Distribution: Debian Sarge (testing)
Hardware Environment:
Arch is PowerPC/BeigeG3
Problematic NIC has a DP83815 chipset (Netgear FA311)
Software Environment:
iproute2/ifconfig
Problem Description:
"ifconfig eth0 up" *apparently* allows multicast on the device :
# ifconfig eth0
...
UP BROADCAST RUNNING MULTICAST
...
# ip maddr show
...
1: eth0
link 33:33:ff:be:0a:ed
link 33:33:00:00:00:01
...
inet6 ff02::1:ffbe:aed
inet6 ff02::1
However, the NIC does *not* reply to neighbor-sollicitation multicasts, neither
on 33:33:00:00:00:01 (ping6 ff02::1) or on the sollicited-node multicast.
It *is* however responding *after* being brought in promiscuous mode (using
tcpdump) or an "ifconfig eth0 multicast" has been issued. Shuting down and up
brings the problem back again
Steps to reproduce:
# ifconfig eth0 down
# ifconfig eth0 up
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-04-13 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 17:36 Andrew Morton [this message]
2005-04-16 6:24 ` Fw: [Bugme-new] [Bug 4482] New: natsemi: incorrect initialization of IPv6 Neighbor-discovery multicast Herbert Xu
2005-05-15 22:19 ` Jeff Garzik
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=20050413103642.172d3976.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
--cc=svallet@gmail.com \
/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).