From: TC Hough <tchough@austin.rr.com>
To: bridge@lists.osdl.org
Subject: [Bridge] Misbehaving bridge...
Date: Wed, 14 Apr 2004 22:17:55 -0500 [thread overview]
Message-ID: <407DFEE3.3000705@austin.rr.com> (raw)
I'm trying to bridge a wired network and a wireless network, but I'm
having some trouble. No traffic seems to be passing through the
bridge. When I issue a "showmacs" command to brctl, I am able to see
MAC addresses from both networks. I am also able to ping both networks
from the bridge machine. When I issue a "showstp" command to brctl, the
wireless access point that my card is connected to is shown as the root
bridge no matter how low I set the bridge priority. If I tell my
wireless card to act as the master, the bridge seems to function perfectly.
The card I'm using is a D-Link DWL-520 Rev E1 with a Prism2.5 chipset
using the HostAP drivers. I read in the FAQ page that some wireless
cards cannot act as bridges because they are unable to spoof MAC
addresses. I do not believe this to be the case with my card. I am
able to change my MAC address without problems by issuing the following
command:
ifconfig wlan0 hw ether XXXXXXXXXXXX
The card functions normally with a fake MAC address. It'll even show up
on my access point's station list as the fake address. So am I doing
something wrong? Should this work, or did I misunderstand the FAQ? Is
altering the MAC address a thorough enough test of whether my card is
capable of being a wireless bridge?
The bridge machine I'm using is an older PPC Macintosh running Debian
unstable. Could the architecture be a problem?
If it is impossible for me to bridge the networks when I am a wireless
client in managed mode, would it be possible to bridge the hardware
access point and this linux box functioning in master mode?
Thank you for your time,
TC
PS: If this is the wrong place to post these sorts of questions, I
apologize for the inconvenience.
reply other threads:[~2004-04-15 3:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=407DFEE3.3000705@austin.rr.com \
--to=tchough@austin.rr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox