Linux Ethernet Bridging - Dec 2009 - [Bridge] Re :Re: Bridging partially (rx eth0 -> tx eth1)

On Tue, Dec 15, 2009 at 10:36 AM,  <jhautbois at 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?"
>
> I am still looking at the doc.
look at the -i and --physdev-in options
>
> JM

Le , "richardvoigt at gmail.com" <richardvoigt at gmail.com> a
?crit :
> On Tue, Dec 15, 2009 at 10:36 AM, jhautbois at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.linux-foundation.org/pipermail/bridge/attachments/20091215/91c6ba26/attachment.htm