From: Brian Haley <brian.haley@hp.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Patrick McHardy <kaber@trash.net>,
Mark Smith
<nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org>,
greearb@candelatech.com, David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, shemminger@linux-foundation.org
Subject: Re: MACVLANs really best solution? How about a bridge with multiple bridge virtual interfaces?
Date: Mon, 09 Mar 2009 14:33:28 -0400 [thread overview]
Message-ID: <49B560F8.4090602@hp.com> (raw)
In-Reply-To: <m13admbsuk.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> There are two tricky parts.
>
> One problem is that macvlans and the primary hardware device share the
> same transmit queue. So when I have a broadcast packet on the primary
> devices queue I don't know if I have already sent it out to the
> macvlan devices or not.
>
> The second problem is that when I transmit a multicast packet and I
> have a local listener. I believe replicating the packet both at the
> ip layer and at the ethernet layer will result in receiving the packet
> locally twice.
If you want a local listener to see the packet you have to set
IP_MULTICAST_LOOP. A packet from a local source address coming off the "wire"
will be dropped in fib_validate_source(), it would have to come over lo. I'm
not sure how that relates to how macvlan works, just something I've run into
before (2 nics in same subnet, listener on one, sender on other,
IP_MULTICAST_LOOP=0, no packets).
-Brian
next prev parent reply other threads:[~2009-03-09 18:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 10:45 MACVLANs really best solution? How about a bridge with multiple bridge virtual interfaces? (was Re: [PATCH] macvlan: Support creating macvlans from macvlans) Mark Smith
2009-03-07 16:30 ` Ben Greear
2009-03-07 18:13 ` Eric W. Biederman
2009-03-07 22:32 ` Mark Smith
2009-03-08 16:54 ` Ben Greear
2009-03-09 1:14 ` Mark Smith
2009-03-09 13:31 ` Patrick McHardy
2009-03-09 14:56 ` Eric W. Biederman
2009-03-09 15:02 ` Patrick McHardy
2009-03-09 15:48 ` MACVLANs really best solution? How about a bridge with multiple bridge virtual interfaces? Eric W. Biederman
2009-03-09 15:53 ` Patrick McHardy
2009-03-09 16:34 ` Eric W. Biederman
2009-03-09 16:45 ` Patrick McHardy
2009-03-09 18:58 ` Ben Greear
2009-03-09 21:17 ` Eric W. Biederman
2009-03-09 21:23 ` Ben Greear
2009-03-09 18:33 ` Brian Haley [this message]
2009-03-09 18:54 ` Ben Greear
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=49B560F8.4090602@hp.com \
--to=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=greearb@candelatech.com \
--cc=kaber@trash.net \
--cc=nanog@85d5b20a518b8f6864949bd940457dc124746ddc.nosense.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@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 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).