From: Stephen Hemminger <shemminger@osdl.org>
To: Cameron Hutchison <camh+lbr@xdna.net>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Non-forwarding bridge
Date: Wed, 30 Jun 2004 15:53:06 -0700 [thread overview]
Message-ID: <20040630155306.0c43b5fd@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <20040630222436.GA14452@imladris>
On Thu, 1 Jul 2004 08:24:36 +1000
Cameron Hutchison <camh+lbr@xdna.net> wrote:
> Is it possible to set up a non-forwarding bridge? I have two interfaces
> that I'd like to combine, where one is a fast main link and the other is
> a slower backup. I'd like traffic to go out the fast link only, if it is
> available, and failover to the backup if it is not available. I never
> want to forward packets between the interfaces.
You want bonding not bridging.
> One issue may be the 802.11g card on the laptop - a broadcom card
> running with ndiswrapper (0.8). I'm not sure if this configuration
> supports promiscuous mode and whether or not that is the cause of my
> problem.
Wise to suspect that, easy to test though. Just run your favorite
packet sniffer (tcpdump, ethereal).
> However, back to the original question: Can you setup a non-forwarding
> bridge? My problem would go away if you could. Or is there another way
> to configure networking to achieve the same functional result?
Then it isn't a bridge, it is bonding.
next prev parent reply other threads:[~2004-06-30 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 22:24 [Bridge] Non-forwarding bridge Cameron Hutchison
2004-06-30 22:53 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-30 13:03 Cameron Hutchison
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=20040630155306.0c43b5fd@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=camh+lbr@xdna.net \
/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