@Vincent-TP 

> I have double check your screenshots and found that it seems that you don't have this configuration? Please kindly have a check.
 

@GRL

I think I got your point. Thank you for pointing this out. Always going forward step by step.

  @Vincent-TP 
 

Vincent-TP wrote

Hi  @relvy 

 

Just to confirm, does that mean, the issue was fixed by changing the Authentention Type from Port based to MAC based?

If yes, does this only apply for the switch port that EAP was plugged in? Or all the switch ports?

No, it is not. The ports the EAP is connected to have no authentication enabled or the EAP would have to authenticate itself, otherwise.

  @Vincent-TP 

Vincent-TP wrote

Hi  @relvy 

 

Thanks for the confirmation.

 

So, what's the current status? Has this issue been resolved? Do you need any further assistance?  Sorry for any misunderstanding.

 

 

Well, yes, the problem still persists. I suppose it is a firmware issue because I have no other explanation for why does the EAP783 not assign the VLAN to the mobile client it receives from the access-accept packet ...

Vincent-TP wrote

  @relvy 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID250529487, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!

I have not got a reply yet so far.

I updated the OC300 controller to new version:

Still no success.

However, in this announcement  https://community.tp-link.com/en/business/forum/topic/816664  I found this:

"3)  *Added support for assigning multiple VLANs to a single SSID in Site View > Settings > WLAN > SSID > Advanced Settings > VLAN > Add VLAN. Supports dynamic VLAN allocation with automatic client assignment and fallback during DHCP failure, improving flexibility in network resource management."

This sounds exactly to be my issue. I did not know this is not yet supported.

Vincent-TP wrote

  @relvy 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID250529487, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!

I just got a reply. They confirm my configuration is correct.
They just asked to use the Network Tools if the EAP can ping the freeradius server. Yes, it can.