From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2e59e6970912150828r35af13c6r9e99be828a29576b@mail.gmail.com> Message-ID: <0016e6d58ca2562149047ac6fcfa@google.com> Date: Tue, 15 Dec 2009 16:36:02 +0000 From: jhautbois@gmail.com Content-Type: multipart/alternative; boundary=0016e6d58ca256212f047ac6fcf7 Subject: [Bridge] =?iso-8859-1?q?Re=A0=3ARe=3A__Bridging_partially_=28rx_e?= =?iso-8859-1?q?th0_-=3E_tx_eth1=29?= List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "richardvoigt@gmail.com" , jhautbois@gmail.com Cc: bridge@lists.linux-foundation.org --0016e6d58ca256212f047ac6fcf7 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > 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 ? I am still looking at the doc. JM --0016e6d58ca256212f047ac6fcf7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > 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) traf= fic to the host, and forward everything else ?

I am still lookin= g at the doc.

JM --0016e6d58ca256212f047ac6fcf7--