From: Alpt <alpt@freaknet.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, bridge@lists.osdl.org
Subject: Re: [PATCH] bridge hub_enabled option
Date: Wed, 30 Mar 2005 13:14:24 +0200 [thread overview]
Message-ID: <20050330111424.GA16289@nihil> (raw)
In-Reply-To: <20050329142719.4bd7cb57@dxpl.pdx.osdl.net>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Tue, Mar 29, 2005 at 02:27:19PM -0800, Stephen Hemminger wrote :
~> On Sat, 26 Mar 2005 23:40:30 +0100
~> Alpt <alpt@freaknet.org> 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 ]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Bridge mailing list
Bridge@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/bridge
prev parent reply other threads:[~2005-03-30 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 22:40 [PATCH] bridge hub_enabled option Alpt
2005-03-29 22:27 ` [Bridge] " Stephen Hemminger
2005-03-30 11:14 ` Alpt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050330111424.GA16289@nihil \
--to=alpt@freaknet.org \
--cc=bridge@lists.osdl.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).