From: jhautbois@gmail.com
To: "richardvoigt@gmail.com" <richardvoigt@gmail.com>, jhautbois@gmail.com
Cc: bridge@lists.linux-foundation.org
Subject: [Bridge] Re :Re: Re :Re: Bridging partially (rx eth0 -> tx eth1)
Date: Tue, 15 Dec 2009 18:41:01 +0000 [thread overview]
Message-ID: <00504502c76d525f97047ac8bb01@google.com> (raw)
In-Reply-To: <2e59e6970912151006v2d8c1b34ua34aff0a6a66c16c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Le , "richardvoigt@gmail.com" <richardvoigt@gmail.com> a écrit :
> On Tue, Dec 15, 2009 at 10:36 AM, jhautbois@gmail.com> wrote:
> >> ebtables can select which traffic gets bridged.
> >>
> > Thnks you for answering.
> > AFAIK, ebtables works like iptables, but within the L2 layer ?
> > This means I could eventually send only IP (and VLAN) traffic to the
> host,
> > and forward everything else ?
> Yes, or you can match based on input interface, which solves your
> original problem if you rephrase the question "how can I bridge all
> packets coming in from eth0 and none coming in from eth1?"
> look at the -i and --physdev-in options
I would like to do something like that :
-->| eth0 |-------IP-->| Host |--->Some treatment based on sockets
| |------Everything else------>| eth1|-->
-->| eth1 | ---> | eth0 |
I think I can do that only with -i and -physdev-in.
I will think about it.
JM
[-- Attachment #2: Type: text/html, Size: 1283 bytes --]
prev parent reply other threads:[~2009-12-15 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 18:06 [Bridge] Re :Re: Bridging partially (rx eth0 -> tx eth1) richardvoigt
2009-12-15 18:41 ` jhautbois [this message]
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=00504502c76d525f97047ac8bb01@google.com \
--to=jhautbois@gmail.com \
--cc=bridge@lists.linux-foundation.org \
--cc=richardvoigt@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 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.