Thread (3 messages) 3 messages, 2 authors, 2005-03-30

Re: [PATCH] bridge hub_enabled option

From: Alpt <hidden>
Date: 2005-03-30 11:14:24
Also in: bridge

On Tue, Mar 29, 2005 at 02:27:19PM -0800, Stephen Hemminger wrote  :
~> On Sat, 26 Mar 2005 23:40:30 +0100
~> Alpt [off-list ref] wrote:
~> > Bridge hub_enabled patch:
~> > this patch adds the hub_enabled option for bridge.
~> > 
~> > By default the hub_enabled flag is set to 1. In this case nothing changes, the
~> > bridge, as usually, acts as a hub and flood_forward the input pkts to all its
~> > ports. When hun_enabled is set to 0, the bridge stops to flood_forward the input
~> > traffic and takes only the pkts sent to it.
~> > Disabling the hub option is useful to join multiple interfaces into a unique virtual
~> > one, thus becomes possible to have easily an ad-hoc network topology using multiple
~> > interfaces.
~> 
~> Could you give a better example of how this would be useful?
~> Why would you not want A to talk to C? 

For example to test a routing protocol.

~> Why not enforce the policy with ebtables?

To not rely to the ip addresses but just having x interfaces merged and to have
a cleaner and simpler way to do it.

Regards
-- 
:wq!
"I don't know nothing" The One Who reached the Thinking Matter   '.'

[ Alpt --- Freaknet Medialab ]
[ GPG Key ID 441CF0EE ]
[ Key fingerprint = 8B02 26E8 831A 7BB9 81A9  5277 BFF8 037E 441C F0EE ]

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help