Re: Multi-Bridge How-To ?

"Taylor, Grant" <[email protected]>
Newsgroups gmane.linux.network.bridge.ebtables.user
Message-ID <[email protected]>
Michael L Owen wrote:
> The documentation I have found so far adequately describes how to bind
> eth0 and eth1 to a brdidge (br0). Is there any documentation ao article
> that describes how to enslave more that two interfaces. My goal is to
> have one upstream interface, and two downstream interfaces on the
> bridge. The two downstream interfaces probably shouldn't be able to
> communicate.
> 
> Thanks in advance for any links and help
> 
> Moke

I think I just answered a question very similar to this on a different mail list.  Here is basically what I said then.

brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
brctl addif br0 eth2

ebtables -t filter -P FORWARD DROP
ebtables -t filter -F FORWARD
ebtables -t filter -A FORWARD -i eth1 -o eth0 -j ACCEPT
ebtables -t filter -A FORWARD -i eth0 -o eth1 -j ACCEPT
ebtables -t filter -A FORWARD -i eth2 -o eth0 -j ACCEPT
ebtables -t filter -A FORWARD -i eth0 -o eth2 -j ACCEPT

In this scenario eth0 is he upstream connection and eth1 and eth2 are the down stream connections.  This ebtables script should allow eth1 and eth0 to communicate with each other and eth2 and eth0 to communicate with each other but not allow eth1 and eth2 to communicate with each other.  Do keep in mind that I have not tested any of this so I can not say for sure that it will work, but I think this is what you are after.  If you don't mind please let me know one way or the other, preferable on the list for future archive searches.



Grant. . . .


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.