#1131: WDS / bridging in Ad-Hoc mode
----------------------------------------+-----------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mrenzmann
Type: enhancement | Status: assigned
Priority: minor | Milestone: version 0.9.4
Component: madwifi: 802.11 stack | Version: trunk
Resolution: | Keywords: adhoc wds
Patch_attached: 1 |
----------------------------------------+-----------------------------------
Comment (by mtaylor):
There is a known issue that i have written about on the WDS page in the
Wiki. The VAP for the IBSS or AP needs to be a different MAC than the WDS
links if you want to bridge them. The problem is that the bridge takes
the lowest MAC address of the enslaved devices (typically your master
device's MAC), then you wind up with a bridge having the master device's
MAC for the bridge, all WDS links, and the IBSS vap.
The workaround is to use -bssid when creating the IBSS VAP. Then bridging
will work because the IBSS vap will not get confused and consume packets
that should have been forwarded to the bridge and vise-versa.
I'm not sure if this is something that can/should be fixed in the driver
but I have also submitted a fix to svn that allows WDS likes to be
assigned locally managed (sometimes called "cloned") MAC addresses.
Try to make sure the device of the bridge and the main IBSS or AP ap are
not the same. Spent all day figuring this one out yesterday.
Cheers,
Mike
--
Ticket URL: <http://madwifi.org/ticket/1131#comment:16>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
