Feature #1104
closedmwl driver patch to enable generation of new BSSIDs for additional VAPs
0%
Description
The current version of the mwl driver we are using has something that is disabling the code that generates new BSSIDs for additional VAPs that are created (at least for the two cards I have, anyway). As far as I can tell, the flag that it uses to disable it only has any functional effect on only one part of the entire driver - the part that picks the BSSID for each VAP. I've tried commenting out the lines having to do with setting that flag and now all of my VAPs seem to work fine - a client can associate to any, rather than only one of them. Each VAP is now getting a different BSSID in the same way as it happens on ath.
So far I've only tested this with two VAPs, only one client associated, and only communicating with the router; but the change should only have an effect when there is more than one VAP (the first one has the original BSSID either way) and use of more than one VAP on mwl is already broken anyway.
Files