[Bridge] [ebtables]Explanation of the packet flow...

Jean-Michel Hautbois jhautbois at gmail.com
Sun Jan 17 10:14:06 PST 2010

2010/1/17 Bart De Schuymer <bdschuym at pandora.be>:
> Jean-Michel Hautbois schreef:
>>>> Well, when a bridge is between two interfaces, this is quite the same
>>>> than saying it is forwarded from one to the other, in my point of
>>>> view. No ?
>>> The bridge indeed forwards the packets, not ebtables. You don't need
>>> ebtables for that unless you want to filter the traffic.
>> Well, let's take my example.
>> I have a bridge between eth0 and eth1. This bridge is stp disabled,
>> and the ebtables filter table accepts input, forward and output.
>> I didn't specify any filtering rule.
>> When I send a packet (LACP for me), it is not going from one eth to the other.
>> I have to say, explicitly, that the packet with ethertype 0x8809 are
>> accepted in "forward".
>> This is why I have some difficulties understanding the packetFlow,
>> because, depending on the protocol, the behaviour doesn't seem to be
>> the same...
> You don't provide enough information for us (at least for me) to tell
> you what's wrong. It's probably something as simple as changing the
> default policy of the FORWARD chain from DROP to ACCEPT. Just rmmod the
> ebtables kernel module if you don't need it...

Default policy of the FORWARD chain is on ACCEPT.
I can't rmmod, because I do need ebtables for one of the interfaces.


More information about the Bridge mailing list