EAP683-LR Poor network performance with tagged vlans on SSID
Hooked up my new EAP683-LR wifi access point and configured it to match my previous AP configuration (ubiquiti) via a OC200. Network looks like this:
mikrotik router -> eth7 -> trunk port with default vlan1 untagged, vlans 11,20,30 tagged.
EAP683-LR configured with 3 SSIDs, each one tags a vlan (11,20,30).
When a device connected to the SSID tries to connect to a local resource on the same vlan, the device receives duplicate TCP ACKs and TCP Retransmissions but will never connect to the backing TCP service. In this case it affects multiple services but I'm primarily testing with plex.
If, for instance, I configure the trunk port on the mikrotik router to set untagged on vlan11 and tagged vlan1 (and then remove the vlan tag on the SSID), everything works as expected.
I also tested upgrading the OC200 to the latest beta firmware to try with PPSK and that also did not work as expected.
Is there any advice to setup the access point to work correctly when connected with tagged vlans with 3rd party routers?
Thank you.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@rumblpak did you try to configure a switch port in the same VLAN as the SSID you are trying and see if it worked that way?
Also, please give details on how the Plex server is connected to the network. I assume wired. What is the config on the switchport it is connected to, how is it getting it's IP (DHCP or Static)? What is the mask? (255.255.255.0?)
How are the clients connected (I assume Wi-Fi). I also assume DHCP, and that it is pulling an address in the correct scope. What is the mask?
What are the VLAN Default Gateway IP's, and the DHCP range for each VLAN? I assume 24 bit masks (255.255.255.0), but please confirm.
What is the topology of the network?
Is this the topology for Clients?
Modem -> Router -> Switch -> AP -> Client
Server?
Modem -> Router -> Switch -> Server
What make/model of switch and router?
At this point I feel like I must be missing something obvious, but I don't know enough details to know what that obious thing is.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@rumblpak I can't help without details. Happy to help though. Work through my last post and answer those questions, and I can take a look at it. I don't need public IP's, just stuff within your local LAN. Screen shots are always helpful too. IE: for the port configs on the switch ports, and VLAN definitions.
- Copy Link
- Report Inappropriate Content
Answers in line below
muzicman0 wrote
@rumblpak did you try to configure a switch port in the same VLAN as the SSID you are trying and see if it worked that way?
Also, please give details on how the Plex server is connected to the network. I assume wired. What is the config on the switchport it is connected to, how is it getting it's IP (DHCP or Static)? What is the mask? (255.255.255.0?)
> Everything is DHCP and is setup into multiple /16s (255.255.0.0)
How are the clients connected (I assume Wi-Fi). I also assume DHCP, and that it is pulling an address in the correct scope. What is the mask?
> Everything wired works as expected. Everything wireless connects through the new AP. Clients do get IPs in the correct scope and netmask (255.255.0.0).
What are the VLAN Default Gateway IP's, and the DHCP range for each VLAN? I assume 24 bit masks (255.255.255.0), but please confirm.
> GW: 10.0.0.1
> DHCP RANGE: 10.0.1.0-10.0.100.254
> Repeat for 10.1.0,0/16 and 10.2.0.0/16
What is the topology of the network?
Is this the topology for Clients?
> Modem -> Router/Switch -> AP -> Client
Server?
> Modem -> Router/Switch -> Server
What make/model of switch and router?
> Mikrotik RB5009UG+S+IN
At this point I feel like I must be missing something obvious, but I don't know enough details to know what that obious thing is.
for the port configs on the switch ports, and VLAN definitions.
> Nothing really of note here, before making changes, the port defaulted to vlan1 untagged and required vlan11 to be tagged (which should have been done by the setting on the AP). Changing it to be vlan11 untagged and require vlan1 to be tagged and setting the AP to have a management vlan does fix that but it should still work the other way.
- Copy Link
- Report Inappropriate Content
@rumblpak You'll probably want to reach out to Omada support. Assuming everything is configured as you say, I see no reason it shouldn't work. I don't know much about the Micotik router, but I have used Omada AP's with Cisco (Enterprise and SMB), Omada, and Ubiquity hardware with no issues. Even used them with Zyxel at one point.
- Copy Link
- Report Inappropriate Content
@rumblpak Got back from vacation and saw a new firmware got released, based on the release notes: https://static.tp-link.com/upload/firmware/2024/202401/20240102/EAP683%20LR%20v1%20Release%20Note.pdf it probably fixes the issues I'm running into, gonna update it and will report back (may take a few days as I'm also moving).
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1984
Replies: 28
Voters 0
No one has voted for it yet.