I will give an appraisal on Amazon to warn People not to buy this thing and i personally will never buy any tp-Link hardware again.

Happy hacking!!

i found this on amazon. But there are also bugs left. These are beta versions. And both still have the DHCP issue!

AP500v1_160418.BETA.MSSID.zip
http://tp-link-support.de/firmware/AP500/AP500v1_160418.BETA.MSSID.zip

AP500v1_160607.BETA.DHCPwtMSSID.zip
http://tp-link-support.de/firmware/AP500/AP500v1_160607.BETA.DHCPwtMSSID.zip

Did you try this firmware : http://static.tp-link.com/resources/software/AP500_un-up-ver1-0-0-P1_20160607-rel48929_.zip ?
It's the best one for me (Multi-SSID and VLAN).

Recently tp-link support sent me another firmware AP500_us-up-ver1-0-0-P1[20170720-rel56961] but it doesn't solve my issue.

Thx but i think this will not work on my ap, because i have a europe version.

tplinkuser12123 wrote

Thx but i think this will not work on my ap, because i have a europe version.

You can check #14 for Europe version.

sorry this firmware doesn´t work for me.
i will exchange this AP with another device. for sure not from tp-link. :-)

Since there is much interest, let me provide an update on my findings and experience.

I've been in communication with TP-Link support, and they've provided me two firmware so far, the latest being 1.0.0 Build 20170720 Rel. 56961.

Very interestingly, this last firmware initially tags the egress traffic from AP500 correctly. But after a short while, they become untagged again. In effect, what a test device experiences is that upon initial association with the VLAN tagged SSID on the AP500, web surfing works fine. But a short while later, the network is inaccessible again.

My upstream router is a pfSense. Tcpdump on it reveals that traffic coming from the AP500 is tagged initially, then becomes untagged after a while.

I have managed to get another AP to verify the pfSense is really working fine. With the other AP (a MikroTik), the tagging works fine over an extended test period.

I've also updated TP-Link support with my new findings, and hopefully they will resolve the problem.

Thank you lzs for your feedback.

Let's hope a stable release soon.

I've also lodged a support ticket on this, and had no response yet.

Unbelievable that they don't respond to problems on a very expensive router failing to work for a very simple and well-advertised feature of their product. Hoping this will be resolved ASAP or else I will be returning the product and giving my review online.

lzs wrote

I've also updated TP-Link support with my new findings, and hopefully they will resolve the problem.

Did TPLink resolve this problem in the last 2 months?

Share the bate firmware with you : http://support.tp-link.com/f/a596579351/?dl=1