Hi  @Hank21,

I use the following config/Devices:

 

--------

Using EAP683LR  with the passhrase of Personal (VLAN 1), I have no issues. 

Using EAP683LR with the passhrase of Zakelijk (VLAN 30), speed drops to 1Mbps or lower.

Using EAP650-outdoor with the passhrase of Personal (VLAN 1), I have no issues. 

Using EAP650-outdoor with the passhrase of Zakelijk (VLAN 30), I have no issues.

devices used to test:

• iPhone 13
• MacBook Pro 2021
• MacBook Air 2015

I use the following wireless config:

-----

Test Results while having problems:

 (using iPhone 13)

Hi  @Hank21, 

That's correct. There is no VLAN-tagging set on the AP. One VLAN-IP (named personal) has no VLAN-ID set to it. That's because I need it to default to VLAN-1. That's also the only VLAN that works great on the EAP683LR.

I have changed the cable between the switch and the EAP683LR and tested connecting it straight to the main switch. None of the changes made any difference.

Yesterday, I swapped the EAP683LR back to my EAP660HD. Right away, all problems disappeared. My feeling tells me that the problem is with the latest firmware version of the EAP683LR. Can you provide me with the first firmware 1.0.0 version of the AP? I remember that the changelog mentioned something about PPSK.

See changelog: https://static.tp-link.com/upload/firmware/2024/202401/20240102/EAP683%20LR%20v1%20Release%20Note.pdf

  @MPDI 

Out of curiosity, have you tried testing performance of a static VLAN tagged SSID on the 683?

Hi  @sonaric,

Thanks for your reply! Same problem unfortunately. 😞

Hi  @Hank21,

Using VLAN-1 and PPSK:

Using VLAN-30 no PPSK:

MPDI wrote

Hi  @sonaric,

Thanks for your reply! Same problem unfortunately. 😞

 

 

  @MPDI 

If it happens on a fresh dedicated SSID with an assigned VLAN (static tag) then at least that eliminates PPSK as the problem. Either the EAP683 has some bug with tagged traffic period, you've got a lemon of some kind, or there is something else wrong/misconfigured with your network. I don't have the EAP683 so I can't test the hardware specifically, and I know you said you had a 650-outdoor the issue didn't appear on, but my next steps would still be to quickly try to double check and eliminate other variables. I'd start by disconnecting the 683, tagging that same port with that VLAN and then connecting directly with ethernet (WiFi turned off entirely) and testing again. And/or connect with it accepting all and tag it on your client. If the problem doesn't repeat then that narrows it down to the WAP, if it does though the issue isn't even the WAP at all it's the switch/router. You could try deleting all SSIDs except for a single static tagged test one, do a fresh vlan, and so on to really confirm.

If the 683 and plain tagged traffic is the issue and they can't get that bug squashed asap then RMA it or just return it and replace it with something older and better polished because that's just silly.

  Hi @sonaric,

At my the previous posts, I ran some of the test you did mention. Here a summery:

- Vlan tag on port and connecting pc at it  = No Problem

- PPSK with vlan-tag on a EAP660HD and EAP650-outdoor: No problem.
- SSID with VLAN tag on EAP683LR = Problem

- PPSK with default vlan on EAP683 LR = No problem

- PPSK with vlan tag on EAP683LR = Problem

Conclusion: using my EAP683 LR with a VLAN tag causes problems. 

Thank you guys for helping me troubleshooting this problem. When I recieve more information about this problem, I shall post it bellow. 

Lastest update:

I just contacted TP-Link NL. A technical support member will escilate this isue at TP-Link. 

The problem is exists using hardware controller (OC300) using version 15.12.9 and software controller (Docker) 15.13.22.