From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Brian Haley <brian.haley@hp.com>, netdev <netdev@vger.kernel.org>
Subject: Re: multicast: bug or "feature"
Date: Wed, 17 Oct 2007 16:23:07 -0400 [thread overview]
Message-ID: <47166F2B.5010706@hp.com> (raw)
In-Reply-To: <OF5E5E93CF.68389D89-ON88257377.006E39CF-88257377.006EB529@us.ibm.com>
David Stevens wrote:
> I'm not clear on your configuration.
>
> Are the sender and receiver running on the same machine? Are
> you saying eth0 and eth1 are connected on the same link?
Yes and Yes.
I know it's a strange config, but it works with IPv6.
Here is the info off the reproducing system:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:17:08:7D:47:18
inet addr:10.202.1.23 Bcast:10.202.255.255 Mask:255.255.0.0
inet6 addr: 2001:1890:1109:a10:217:8ff:fe7d:4718/64 Scope:Global
inet6 addr: fe80::217:8ff:fe7d:4718/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1094 errors:0 dropped:0 overruns:0 frame:0
TX packets:669 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:107776 (105.2 KiB) TX bytes:109874 (107.2 KiB)
Base address:0x4000 Memory:f9de0000-f9e00000
eth1 Link encap:Ethernet HWaddr 00:18:FE:7F:49:C8
inet addr:10.202.1.26 Bcast:10.202.255.255 Mask:255.255.0.0
inet6 addr: 2001:1890:1109:a10:218:feff:fe7f:49c8/64 Scope:Global
inet6 addr: fe80::218:feff:fe7f:49c8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:479 errors:0 dropped:0 overruns:0 frame:0
TX packets:35 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:52236 (51.0 KiB) TX bytes:4467 (4.3 KiB)
Interrupt:41 Memory:f6000000-f6012100
# ip r l
10.202.0.0/16 dev eth0 proto kernel scope link src 10.202.1.23
10.202.0.0/16 dev eth1 proto kernel scope link src 10.202.1.26
default via 10.202.1.1 dev eth0
-vlad
next prev parent reply other threads:[~2007-10-17 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 19:58 multicast: bug or "feature" Vlad Yasevich
2007-10-17 20:10 ` David Stevens
2007-10-17 20:23 ` Vlad Yasevich [this message]
2007-10-17 20:29 ` David Stevens
2007-10-17 21:25 ` Vlad Yasevich
2007-10-17 23:11 ` David Stevens
2007-10-18 1:20 ` Vlad Yasevich
[not found] ` <47166BD5.7090207@hp.com>
2007-10-17 20:19 ` Vlad Yasevich
2007-10-18 16:17 ` Vlad Yasevich
2007-10-19 11:43 ` Herbert Xu
2007-10-19 15:21 ` David Stevens
2007-10-19 16:49 ` Vlad Yasevich
2007-10-19 17:43 ` David Stevens
2007-10-19 18:43 ` Vlad Yasevich
2007-10-19 20:23 ` David Stevens
2007-10-19 20:39 ` Brian Haley
2007-10-19 21:25 ` David Stevens
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=47166F2B.5010706@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=brian.haley@hp.com \
--cc=dlstevens@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.