From: "maxd@inwind.it" <maxd@inwind.it>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] IGMP snooping not filtering multicast messages
Date: Tue, 31 May 2011 19:48:52 +0200 (CEST) [thread overview]
Message-ID: <21909438.382941306864132965.JavaMail.defaultUser@defaultHost> (raw)
Hi. I have a partial mesh network composed by Linux nodes. Each linux node may
have up to 4 ethernet interfaces, which are exploited to create point-to-point
connections with other linux nodes. I have bridged the ethernet interfaces in
each node, so that the whole network, which is physically composed by a set of
network segments, appears as a single layer-2 domain. I have enabled spanning
tree to avoid loops. In this scenario, I would like to exploit the IGMP
snooping functionality, but it seems that it is not working properly. I am
using iperf to set a multicast source (iperf client) and a few multicast sinks
in the network (iperf servers). I am using tcpdump, instead, to check where
multicast messages are received. What I notice is that there is apparently no
filtering of the multicast messages, that are always flooded in the network. I
tried to repeat the test varying the multicast address (paying attention not to
get reserved addresses), with and without multicast clients set, with the
multicast_router option set to 1 (default) and to 0. To double check that IGMP
is working, I have also tried to disable it; the only difference I see is that
tcpdump does not show IGMP query messages when the IGMP snooping is disabled.
So, I am wondering if the IGMP snooping implementation currently available can
deal with my scenario. In particular, I would stress the following points that
I think might be relevant:
-I have no multicast router in my network (it looks like a single stand-alone
lan)
-Each node acts as a bridge, so I have multiple bridges in my network,
connected each other.
Any idea would be greatly appreciated!
Massimiliano
reply other threads:[~2011-05-31 17:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=21909438.382941306864132965.JavaMail.defaultUser@defaultHost \
--to=maxd@inwind.it \
--cc=bridge@lists.linux-foundation.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.