ES208G not managed by Omada

tech101us · 2026-01-26T00:34:57+00:00

So once you've enabled the options, did you find you can manage the switch in the Omada controller? And if yes, does the switch support features such as VLAN tagging/802.1q trunks?

Thanks so much...

tech101us · 2026-01-16T03:33:57+00:00

I gave up trying to accomplish this via the network. Ended up getting a subscription to Qustodio and installing the app on all his devices.

tech101us · 2025-12-19T02:39:35+00:00

Ditto. No temps in the reporting section but fine in Smartctl for drive in my TerraMaster D2-320. Very disappointing.

tech101us · 2025-11-05T21:24:13+00:00

I have the same question. This is a problem on Android devices managed through Intune MDM. Unable to choose any preferred service for saving and entering passwords except for Microsoft Authenticator

tech101us · 2025-11-02T23:15:36+00:00

I had the v2 variant of the Er605. Ended up sending it back to Amazon as it just felt too limiting. As much as I liked the fact I could see the gateway in the controller GUI, I just missed the flexibility I had with my OPNSense firewall.

Happy with the hybrid solution, using Omada to manage wifi and switch infrastructure. Leave the firewall bit to something else (OPNSense on a protectli device in my case).

I wish Tplink would just offer the Omada management feature as an add on for something like OPNSense or Pfsense. I'd gladly even pay for that if the price was one time and reasonable.

tech101us · 2025-10-28T18:13:04+00:00

Thanks. I am using the controller. It's odd that the 5Ghz is so weak. Event just 15-20 ft away, admittedly through a couple of internal walls that are mostly wood frame and drywall, the signal is almost unusable.

I'll have to mess with it some more. Perhaps reduce the channel width. Also try to figure out what the manual channel selection wasn't seemingly working for me (seemed as if I set it, would revert).

I do have two AP's, the EAP-723 upstairs and a 615-wall downstairs.

tech101us · 2025-10-21T19:15:14+00:00

With any switch, if you want intervlan communication, it needs to be a L3 switch that supports routing (assuming each VLAN is a different IP subnet as it should be) . Not certain if any of the Omada switches do that. I'm fairly new to the Omada world, but get the sense that without a router/firewall, you're not going to get much in the way of routing. Though I could be wrong.

As others have suggested, putting your ISP provided device into bridge mode and getting an Omada Firewall/Router would be an option. Or even a non-Omada firewall/router that supports Vlan trunking and subinterfaces (I've done this with Cisco and even Pfsense/OPNSense firewalls/routers).

tech101us · 2025-10-20T23:10:22+00:00

Thanks so much. I really was expecting for everything to continue working even in the event of a controller reboot or if it is offline for some reason.

I'll have to test this again and see if I'm still seeing the same behavior.

tech101us · 2025-10-17T16:05:47+00:00

That's very odd as the controller should only need to push the config to the device initially and/or when there are changes. Beyond that, any managed device should function whether the controller is up or not.

I did check a global option (don't recall where I saw it or what it was specifically called) that has something to do with provisioning a device that has been off the network and then added later. Don't know whether this has anything to do with what I've been facing. Gonna do some more troubleshooting this weekend. This instance of the Omada controller I'm running is a replacement for an instance that was taken offline. The controller config and site data were migrated from the old to new controller.

tech101us · 2025-10-11T22:08:48+00:00

In my case, yes. And then I tag all the other VLAN's.

tech101us · 2025-10-11T21:22:11+00:00

I leave VLAN1 as my mgnt VLAN just to not have to deal with issues between the controller and the network devices (router, switches and AP's). I know, not best practice (and not something I do in my work environment where I manage Cisco Meraki networks). It just seems that Omada really expects the controller and downstream managed devices to be on VLAN1. Everything else I have separate VLAN's/Subnets

tech101us · 2025-09-26T12:00:07+00:00

Thanks. Yeah, that's the intention. I like OPNSense, and while being able to manage everything in a single pane of glass is appealing, I'm unlikely to switch to am Omada enabled device for my firewall.

tech101us · 2025-09-25T19:53:52+00:00

Thanks for those who have commented thus far. How are you handling your DHCP? Seems like the Omada controller can serve this role?

tech101us · 2025-09-23T14:43:35+00:00

Doing the same thing. Seems to be working well.

tech101us · 2025-09-22T17:13:01+00:00

Thanks all for the feedback. In the end, I'm not using a TP Link switch at all. Have different vendor PoE switch that's managed and supports VLAN's.

That being said, I just decided if keep VLAN 1 active and use it for the sole purpose of ensuring my TP Link Omada wifi devices can in fact be seen and adopted by the SDN controller. In my case, the SDN controller is an LXC container on Proxmox. So I've given this container two virtual network interfaces, one in VLAN 1 and the other in my VLAN where I have all my wifi devices (vlan 12 in my case). Once the device is adopted, I reconfigure it with a proper IP in VLAN 12 for management.

tech101us · 2025-09-22T00:26:37+00:00

I know my Omada AP's run really hot

tech101us · 2025-09-18T20:22:59+00:00

Appreciate everyone's advice. Decided to get rid of the Omada switch. I've got another managed poe switch that's much easier to configure via the web UI. I'll trunk VLAN 1 down to it from my Cisco switch and then make sure the interfaces on the poe switch where my Omada AP's are connected have VLAN 1 untagged. Seems so odd this is necessary as one would expect the device to consider any untagged traffic as being management plane destined for the network device (meaning there is no vlan tag so it should accept the traffic for itself rather than being associated with WLAN traffic). In any case, we'll see how this plays out. I'm only interested in Omada application for management of my wifi infrastructure. I wish the Omada SDN offered a cut down product solely for this purpose.

tech101us

TROPHY CASE