From: Cameron Hutchison <camh@xdna.net>
To: bridge@lists.osdl.org
Subject: [Bridge] Non-forwarding bridge
Date: Wed, 30 Jun 2004 23:03:11 +1000 [thread overview]
Message-ID: <20040630130311.GB5624@imladris> (raw)
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.
My specific setup is a laptop with a 100M ethernet and a 802.11g wireless
link, kernel 2.6.7. The two networks are already bridged with a linksys
WRT54G (running OpenWRT).
When I try to set up a bridge in my laptop, I'm getting a loop on my
network. I have STP enabled in both bridges and I have set the bridge
priority of the laptop to the lowest possible (65535) - the linksys is
still at the default 0x8000.
I dont seem to get all packets looped - it seems to be mostly samba
packets. I'm watching the link with ethereal and the packets stop when I
kill the bridge on the laptop.
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.
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?
Thanks
next reply other threads:[~2004-06-30 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 13:03 Cameron Hutchison [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-30 22:24 [Bridge] Non-forwarding bridge Cameron Hutchison
2004-06-30 22:53 ` Stephen Hemminger
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=20040630130311.GB5624@imladris \
--to=camh@xdna.net \
--cc=bridge@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.