From: Arnd Bergmann <arnd@arndb.de>
To: evb@yahoogroups.com
Cc: "'Stephen Hemminger'" <shemminger@linux-foundation.org>,
"'Fischer, Anna'" <anna.fischer@hp.com>,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, davem@davemloft.net,
kaber@trash.net, adobriyan@gmail.com,
"'Or Gerlitz'" <ogerlitz@voltaire.com>
Subject: Re: [evb] Re: [PATCH][RFC] net/bridge: add basic VEPA support
Date: Mon, 10 Aug 2009 17:23:10 +0200 [thread overview]
Message-ID: <200908101723.10832.arnd@arndb.de> (raw)
In-Reply-To: <005101ca1797$70dcf5b0$5296e110$@edu>
On Friday 07 August 2009, Paul Congdon (UC Davis) wrote:
>
> I don't think your scheme works too well because broadcast packet coming
> from other interfaces on br0 would get replicated and sent across the wire
> to ethB multiple times.
Right, that won't work. So the bridge patch for the hairpin turn
is still the best solution. Btw, how will that interact with
the bride-netfilter (ebtables) setup? Can you apply any filters
that work on current bridges also between two VEPA ports while
doing the hairpin turn?
Arnd <><
next prev parent reply other threads:[~2009-08-10 15:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 17:33 [PATCH][RFC] net/bridge: add basic VEPA support Fischer, Anna
2009-08-07 4:00 ` Stephen Hemminger
2009-08-07 11:29 ` Arnd Bergmann
[not found] ` <005101ca1797$70dcf5b0$5296e110$@edu>
2009-08-10 15:23 ` Arnd Bergmann [this message]
2009-08-10 15:59 ` [evb] " Fischer, Anna
2009-08-10 16:16 ` Arnd Bergmann
2009-08-07 18:58 ` Paul Congdon (UC Davis)
2009-08-08 9:49 ` Arnd Bergmann
2009-08-10 13:16 ` Fischer, Anna
2009-08-10 15:06 ` Arnd Bergmann
2009-08-10 15:07 ` Arnd Bergmann
2009-08-11 14:30 ` Fischer, Anna
2009-08-11 14:55 ` Paul Congdon (UC Davis)
2009-08-12 13:19 ` Arnd Bergmann
2009-08-12 14:32 ` Fischer, Anna
2009-08-12 16:27 ` Arnd Bergmann
2009-08-13 22:11 ` Fischer, Anna
2009-08-13 22:24 ` Fischer, Anna
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=200908101723.10832.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=adobriyan@gmail.com \
--cc=anna.fischer@hp.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=evb@yahoogroups.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@voltaire.com \
--cc=shemminger@linux-foundation.org \
--cc=virtualization@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox