Use caution on upgrade to 5.1 or 5.2, I cannot recall which one did this, BUT*****************************
Somehow through the upgrade process the Virtual AP's did not work, so I removed all of them. Had just he main AP which i called basement AP, whic I clearly recal setting up after the upgrade since I had to disable wireless package so that the 100 %CPU issue didnt come up, which I found to be when additional Virtual AP's are added thag is when the cpu goes to 100% When adding a Virtual AP, the MAC address is 00:00:00:00:00 where before when there was no problem, the MAC would fill in automatically with the MAC of that wireless card.
Save time, if it is all 0's it will set your board to 100% cpu, and all interfaces in list will not show up. ( yes a BUG) still in 5.2 verified, and drove 20 Km's with note book to fix that board again.
But this is NOT why I am pissed.. I had 5.1 running with the main AP set to basement AP, where before I had the main ap and 2 virtual ap's Ie My own Private AP, MainFloorAP and BasementAP.
Needless to say the basment and main were on seperate bridges, and my private ap was on my private bridge, even called PRIVATE. On the upgrade to 5.2 SOMEHOW that only AP that I set up, called basementAP SOMEHOW switched from the bridge I set it to, being Basment bridge, and after the upgrade it was on the Bridge called PRIVATE.....
so, needless to say, that wasnt what I wanted, my tenants roaming my network, which has alot of sensitive data, and has full access to other networks.
MT Fix these issues, how can you put 5.2 as a stable version on the download page if its been released this same day?
Fix the Virtual AP issues.
And for anyone wantign to test it, set up 3 ap's named " AirMatrix-SK " " BasementAP " and "MainFloorAP" put them on theier seperate bridges with 2 or 3 ehter ports, have DHCP on basement ap and main ap, but none on private bridge. is it because the names end with AP? I dont know, but it will put the board, in my case a 493, to 100% and then interfaces will not be listed. To fix, disable the wireless package, reboot, may require a site visit, some times it boots, sometimes it doesnt.