BIG BUG WITH VIRTUAL APs

RouterOS Wireless Networking
1

Hi all, after troubleshooting a lot of problems or malfunctions with virtual APs and WDS links, I find a nice problem with virtual AP creation in 4.10. I have no time to try it in more versions..

I have a RB with 2 phisical radios wlan1 and wlan2. Configured as:
wlan1@5640@wpa aes
wlan2@5500@wpa aes

I need to create a virtual AP with a WDS in, to link a remote place. Then i need:

wlan1@apbridge
wlan2@apbridge
|_virtualAP1
|_WDS1

To get this configuration, I click in new virtual AP and set the name in the first tab (virtualAP1) and press apply and OK, the virtual AP is created with the same MAC as wlan1 but with 02:MA:CO:FW:LA:N1 at the beggining.. This is normal, because wlan1 is the default master interface during creation.
Then.. if you change the master interface to wlan2, to configure my scenario, the MAC continues like first created and the virtualAP1 (02:MA:CO:FW:LA:N1) and it change aparently to the master interface wlan2.. you could see it in winbox and in console.. that virtualAP1 is a son of wlan2..
But if you make a scan with wlan1, you can’t see the virtualAP and if you make a scan with wlan2, you could see the virtualAP, with 5640 frequency.. The real master interface is the interface that has the “same” MAC as virtualAP1…

With virtualAP creation, the thing is that if you make click to apply button and OK, before change the real master interface you need to use, the master interface, will always be the wlan1. No matter the changes you try to make to master interface..

2

Please send this description and your supout.rif file to support. Also try this with rc1 to make sure this problem is not isolated to an older version.

3

I get this error with 4.11.

I don’t have the supout because is a remote place without internet.

You can reproduce easy with a RB with 2 wlans:

To get this configuration, I click in new virtual AP and set the name in the first tab (virtualAP1) and press apply and OK, the virtual AP is created with the same MAC as wlan1 but with 02:MA:CO:FW:LA:N1 at the beggining.. This is normal, because wlan1 is the default master interface during creation.
Then.. if you change the master interface to wlan2, to configure my scenario, the MAC continues like first created and the virtualAP1 (02:MA:CO:FW:LA:N1) and it change aparently to the master interface wlan2.. you could see it in winbox and in console.. that virtualAP1 is a son of wlan2..
But if you make a scan with wlan1, you can't see the virtualAP and if you make a scan with wlan2, you could see the virtualAP, with 5640 frequency.. The real master interface is the interface that has the "same" MAC as virtualAP1...
4

still, email support with all this description

5

Done.