1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MultiSSID Issue

Discussion in 'Tomato Firmware' started by GhaladReam, Aug 10, 2013.

  1. GhaladReam

    GhaladReam Network Guru Member

    I'm running Shibby's 112-64K AIO build on my RT-N66U. I've been using MultiSSID for quite some time now without issue.

    I've come across an issue I cannot figure out. Up until now, I've been running 2 virtual SSID's in addition to the 2 main ones for 2.4 and 5 GHZ. I have wl0.1 (2.4 GHz) and wl1.1 (5Ghz).

    I recently tried to add another 2.4 Ghz virtual SSID (wl0.2) but this time I need to give it a specific MAC for the reason listed in the link below:


    However, when I try to change its mac in Advanced->MAC Address, it does not change properly, thus nothing can connect to it.

    If I try to change the mac on wl0.2, the following message appears in the Virtual Wireless config: "warning: WL driver reports BSSID 00:00:00:00:00:00" and I can't use it.

    If I change the MAC on wl0.1, IT WORKS, however then wl0.2 reports: "warning: WL driver reports BSSID SameMacAsWAN"... Huh?

    I have tried resetting NVRAM multiple times, and tried several different combinations of config, like using wl0.3 and wl0.4 instead of 0.1 and 0.2, but it results in MAC conflicts with BSSID every time, unless I use wl0.1 only which does work for changing the MAC.

    Bottom line: I cannot change (spoof) a specific MAC address on any Virtual Wireless interface other than wl0.1. Am I doing something wrong?
    Last edited: Aug 11, 2013
  2. lefty

    lefty Networkin' Nut Member

    i wouldn't think that you could set virtual interface's MAC address - they basically are just a clone of the non-virtual interface. Is same as far as channel selection for the interfaces, whatever you set the physical interface's channel to be is the same that the virtual interface will use as well, and this can't be adjusted, namely in part due to broadcom's wireless drivers. With ath9k, you can do this, just not on broadcom devices that i have seen.
  3. GhaladReam

    GhaladReam Network Guru Member

    You can set the mac on virtual SSID's. Broadcom drivers have been able to set unique BSSID's on virtual interfaces for a while now. If what you are saying were true, I wouldn't be able to get this to work on the wl0.1 virtual interface, which I can. It's wl0.2 and above that give me problems. I believe this is a bug in the MultiSSID code... Unfortunately I'm not a coder and I wouldn't know the first thing about fixing it...
  4. lefty

    lefty Networkin' Nut Member

    Hrm, i wouldn't consider it a 'bug' in the multiSSID code as you say. Perhaps not a feature that is implemented into this firmware. Is it possible for you to select a different channel on the virtual interface apart from the main physical interface?
  5. GhaladReam

    GhaladReam Network Guru Member

    No, the wireless channel is the same as the physical interface's SSID. I also wanted to point out that if I do a wl down and wl up in SSH, the error reads: warning: WL driver reports BSSID 32:xx:xx:xx:xx:30 on wl0.2 even though I've set it to the 46:xx:xx:xx:xx:xx one.
  6. GhaladReam

    GhaladReam Network Guru Member

    Ok, so after several hours of fiddling, I found a "fix", but i'm not sure exactly why this works:

    My goal was to set wl0.2's MAC address (BSSID) to 40:53:50:4F:4F:46. In order for this to work, I discovered that I needed to also set wl0.1's mac to 40:53:50:4F:4F:45 (one digit lower than the above MAC). When I did this, the WL driver did not report any warnings, and all Virtual interfaces now work 100%! If I keep wl0.1's mac at it's default value of 32:xx:xx:xx:xx:xx (in the same range as all the other MACs on my router) then I would get the error(s) described in my first post.

    I'm glad I figured this out, but does anyone know exactly why I had to also change wl0.1's MAC to a similar range? Note that I ddin't have to change wl0/eth1 or wl1/eth2's MAC, only wl0.1.

Share This Page