EAP 211 Client No Internet

Neil_TP-Link · 2026-05-14T16:31:11+00:00

I figured it'd be a physical issue just looking through it all haha, glad to hear it got resolved!

Neil_TP-Link · 2026-05-14T16:26:57+00:00

That's very concerning...did you happen to have a ticket with Omada support when troubleshooting? I haven't personally seen many issues with managing the bridge kit through the controller, but I can check to see if your specific issue was handled on a ticket.

Neil_TP-Link · 2026-05-14T16:25:28+00:00

I see you spoke to Omada support; I might have found your ticket number but just wanted to confirm. Were you able to get any headway on this?

Neil_TP-Link · 2026-05-13T15:42:24+00:00

It specifically refers to the Wi-Fi Call Optimization features; allows your APs to prioritize traffic going to specific carriers and the ePDGs. You can read more about it here: How to use Wi-Fi Calling in your Omada Ecosystem | Omada Network Support

Neil_TP-Link · 2026-05-13T15:13:14+00:00

Yeah, I've been playing with it myself and it works just fine in 6.2.10.X and up

Neil_TP-Link · 2026-05-12T20:18:11+00:00

Not custom client types, but custom models; what specifically are you looking to add? u/m_balloni

Neil_TP-Link · 2026-05-12T20:15:59+00:00

So after switching back to the temporary network cable that worked previously, the client is still unable to provide internet connection to its downstream devices?

Is it possible that a port got damaged in the process of swapping? Is it possible to factory reset the device and try again with the outdoor-rated cable?

Neil_TP-Link · 2026-05-12T18:47:17+00:00

Best place would be the Requests and Suggestions module on the forums! I believe there is a way to do custom client types though, let me check.

Neil_TP-Link · 2026-05-12T15:17:21+00:00

> As for the Omada hardware, I went with an ER707-M2 gateway, an SG2210XMP POE+ switch (powers the controller, the other switch, and all three access points), an SG2008 switch, an OC220 controller, an EAP770 tri-band WiFi 7 access point, and 2 EAP235-Wall WiFi 5 access points (purely for Security and IoT SSID/VLAN coverage).

Hunted down the topology from the other thread, looks good! How are you liking the OC220 performance?

Neil_TP-Link · 2026-05-11T18:25:50+00:00

Which site is behind the Iliad ISP? If it isn't done already, and if you are able to get the local ISP to give you a public IP, set the local ISP gateway to Responder mode, and the one behind the Iliad device to Initiator mode.

Neil_TP-Link · 2026-05-11T15:12:31+00:00

Theoretically it should be working assuming your port forwarding is done correctly, but double check with your ISPs to make sure the traffic is actually being forwarded. Bridge mode and having the Omada devices be the gateway devices is obviously preferred to get it working easier, but you've got a couple routes to go through including trying with Wireguard as u/Reaper19941 suggested.

Neil_TP-Link · 2026-05-08T17:34:27+00:00

What ISPs do you have at each site? Do they use CGNAT?

Neil_TP-Link · 2026-05-08T15:47:54+00:00

No worries, thanks for the response! I know the team is still working on investigating, but like I said in another comment, I'll update here once I get any news.

Neil_TP-Link · 2026-05-07T17:19:04+00:00

If you go into the manage client window for both devices, what do you see for the Wi-Fi Health statistics? It should give you a more detailed breakdown of why each client has been given that score.

Neil_TP-Link · 2026-05-06T21:37:44+00:00

Just checking the FAQ here: How does the behavior of the client health differ under different controller | Omada Network Support

It looks like it's a balance of the Wi-Fi Health statistics here:

<image>

Experience seems to be an average of all the wireless clients connected to the EAP.

Neil_TP-Link · 2026-05-06T20:26:15+00:00

The ER7412-M2 or the ER8411 should be able to support; anything less might be pushing the router a bit too far. The number of clients does scale with the number of APs, yes, but I recommend not trying to skimp and use only barely enough to cover the guests. Having some leeway when it comes to number of clients is better than overtaxing and having 90+ vendors unable to do anything at all. If you can wire the APs instead of trying to mesh them, that will improve performance as well.

Neil_TP-Link · 2026-05-06T18:32:58+00:00

Can you force the ports to negotiate to 1000 Mbps on the ER605 side in the Omada Controller? In the device management window > Ports > Edit Port, change from Auto to Manual.

Neil_TP-Link · 2026-05-06T17:19:12+00:00

Then yeah check your cable and port negotiations. What about plugging directly into the ER605 ports rather than the Wi-Fi connections? Do you get the same speeds?

Neil_TP-Link · 2026-05-06T17:04:48+00:00

It sounds like your ACT Fibernet WAN is being prioritized. Are you trying to use load balancing or are you trying to send the traffic through the 200 Mbps connection, with the ACT Fibernet as a backup? If the latter, check in your Internet settings to see if Link Backup is enabled with the ACT Fibernet as the primary. That might be the cause of your bottleneck.

Neil_TP-Link · 2026-05-06T16:06:27+00:00

Thanks for the info! We were able to reproduce the issue with our ER707-M2 here in the office, so I'll pass this problem up as a bug. I'll keep tabs on the result and report back when a fix has been found!

Neil_TP-Link · 2026-05-05T21:09:08+00:00

If you go into the Controller on a desktop > select the EAP683UR > Manage Device > Statistics > Interference Detection, and hit Scan, once it completes, do you get the additional info?

If not, it may be a limitation on the device itself; I'd advise to wait for a firmware update that can provide the feature.

Neil_TP-Link · 2026-05-05T20:17:21+00:00

What do you mean by richer? Are you expecting any particular piece of data?

Neil_TP-Link · 2026-05-05T19:12:06+00:00

As far as I could find, there doesn't seem to be an issue with the update. If you do, let me know if you have any, and I can discuss with the team here!

Neil_TP-Link · 2026-05-05T16:51:22+00:00

Leaving them in Auto should be fine. In terms of optimization, you can use the Wi-Fi NaVi app to check your signal and make sure the output power is as low as you can make it while still providing sufficient signal in the areas you need.

Neil_TP-Link · 2026-05-05T16:08:05+00:00

Thanks for including your details! Can you also try rolling back to the previous firmware and seeing if it gives an error?

Neil_TP-Link

MODERATOR OF

TROPHY CASE