@BobTheBuilding 

Accessing the management interface from a non-management vlan in previous versions: This sounds like a security vulnerability.

Putting management on a different vlan:

On old TPlink APs, such as the pile of old 801NDv2's I have, you can set which vlan management is on, and have it tagged if you want to. Annoyingly they have 'simplified' the interface by removing those configurations, hardcoding vlan1 to be untagged and management to run on that.

Importantly, this means that '1' in the vlan field in the access point actually means 'untagged', and you can do this confusing setup:

Configure the switchport to have vlan7 untagged, vlan8 tagged, vlan1 excluded or not existing.

Then on the AP configure the office-ssid to be 'vlan1'=untagged, and the guest-ssid to be vlan8.

This actually gives you vlan7 and vlan8 on the AP, and management interface on vlan7/office, but do not put any evil people on vlan7/office. Due to the packets between the AP and switch being untagged, it is possible to add extra tags and have packets emerge on vlan8.

/KKP

@kkpdk   (I am replying to myself)

Update: I have now been running the 20210628-rel55053 beta for 60 days.

I have 5 SSIDs on vlan1, 2 SSIDs on vlan4 (2.4+5GHz), and 1 SSID on vlan 5 (5GHz). Clients are notebooks, phones, various IOT devices, and a gaming PC.

It's good so far.

I have not had any disconnections, handshake problems, need to reset/reconfigure/troubleshoot the AP, or speed problems.

@DrKalvin my mobiles are not connecting when I put the Password I get message of incorrect password.Do I need to deactivate my mobile data when I am connecting 

@kkpdk (yes, replying to myself yet again)

I have now been running the 20210628-rel55053 beta for ~5 months.

Everything is stable and good, UNLESS I turn on my Canon LBP-6030w printer.

• The printer can do WPS against the AP. My method is to disable all SSIDs other than the one I want the printer to be on, perform WPS button pushing, and then reenable the other SSIDs on the AP. I then powercycle the AP.
• Within 3 days of the printer being connected to the AP, the AP crashes. Even if the printer is only powered on for a single print and then off, the AP will die later.
• When the AP dies, it still forwards traffic from some clients, but new clients cannot connect to the AP, and the web interface becomes inaccessible. The AP responds to ARP and icmp echo request.
• The latest time-to-die was 59 hours, happened while everyone was sleeping, and did not coincide with any scheduled tasks, such as the phones doing backup.

I have repeated this 4 times now (the WPS operation only once).

/kkpdk

@Solla-topee I'm a user of this product with VLans / MultiSSID ; 

since this beta firmware i'm able to use it, and i thank you for that

I saw that TPlink has published a new firmware TL-WA1201(EU)_V2_220103

I tried it, but the issues came back

I had to downgrade to your beta firmware to be able to use it again.

Do you know if your fix for VLans / MultiSSID will be integrated in a next official firmware ?

Thanks in advance :)

PS : I'd be glad that AP Isolation feature will be available in a next firmware too. it's still missing in VLans / MultiSSID mod, and i need to isolate devices in a SSID

I came here to say I just recently bought a TL-WA1201. I only bought it because I wanted to use multiple ssids and different vlans. I realized that it was dropping packets almost immediately and updated to the latest firmware. I can confirm that the issue IS NOT FIXED in the latest 2022 release. 

I had to downgrade to the beta release below to "fix" the issue:

https://static.tp-link.com/beta/2021/202106/20210628/TL-WA1201v2_eu-up-ver1-0-1-P1[20210628-rel55053].zip

Hopefully this continues to work. I love my tp-link smart plugs thats why I got this AP. Thought I could trust the brand. But this really does make me wonder. Have any kind of quality check team??