r/TPLink_Omada

We recently installed Omada Access Point, the installation guy didnt share any password, we repeatedly asked for it so that I can my student something more about Networking & Access Points. Is there any way to find out id and password without factory reset?

My "best practice" has been to use the same SSID name on both 2.4GHz and 5GHz, each with the same setting on both and then use the band steering to prioritize 5GHz. It's worked great for as long as I can remember.

This my first WiFi 7 enabled AP with MLO

I already have a Guest Network setup that uses both 2.4GHz & 5GHZ named "SSID-GST".

When I try to set up an MLO SSID, it complains that "SSID-GST already exists"

My assumption is that I need to delete the existing 2.4GHz "SSID-GST" and "SSID-GST" 5GHz and then create a new "SSID-GST" MLO (checking both 2.4GHz & 5GHz).

My question is basically: Will band steering still prioritize 5GHz for non-WiFi 7 clients that support 5GHz?

I've had this issue for probably around a year. I have gig internet and generally get those speeds, and then all of the sudden I get only a few Kb/s and have to reboot the switch. All is good for another 5ish days, and then the process has to be repeated. I do use the L2+ feature and route from an 8211 to the 3428X and then let the switch take care of the inside L3 work.

I see there is a new firmware update with a fix that seems to be geared toward this problem. Does anyone from TP-Link have any more information on the bug fix in this list?

Thanks in advance! I will be giving it a try as soon as I can.

Release Note
Version Info: 
1. Firmware Version: 1.20.26 Build 20260804 Rel.2730
2. Applied Model: 
a) SG3428X-M2(UN) 1.20
b) SG3428X-M2(UN) 1.26
3. Recommended Omada Controller version: 6.2.10.
4. Recommended Omada App version: N/A
5. For downloading any firmware version, please refer to Omada Download Center.
Bug Fixed: 
1. Fixed an issue that caused reduced Layer 3 forwarding throughput.

I have 4 vlans. One i setup to a single port with Internet access only. ACLs block inter VLAN traffic from that single vlan to rest. I setup a vpn client for that single vlan. All that works. Now I want to setup a kill switch so if the VPN gets disconnected no Internet wan traffic can happen to just that vlan.

Using policy based routing, I can only select wan ports not the VPN as the interface.

I planned on using ACLs to permit the VPN interface and deny all others so if that interface goes down the Internet stops.

Any suggestions?

The network is working properly. Everything was fine. I sorted up cable issues. Then I bumped the power off and on real quick and the controller never connected to the cloud again. It still had my subnet address and I was unable to reset the account or delete the user or anything on the cloud . I went through all troubleshooting steps in different methods of powering it on and resetting it. It just wouldn’t connect and it was hopping on and off of the app. It was unstable. I even tried different cables. Hopefully it’s just a bad piece of equipment. Please let me know.

Thanks

I am new to the omada platform. Generally liking everything I bought. However I am really let down by the eap775 wifi apps. Comming from a 10 year old linksys velop system. 3 velop nodes covered 2 buildings about 5000 sq ft easily. Reception was great on devices in and near by. I bought 3 eap775 assuming I would get similar performance but there are some very weak connections. Do any other aps have better performance? The form factor and poe are selling point but would prefer better coverage over all else

I'm troubleshooting an issue with my Omada setup where most wired clients on an ES216G show CONNECTED status but have blank IP addresses in the controller UI. I'd like to understand whether this is expected behavior or a defect.

Setup:

- Omada Software Controller 6.2.14.11 (self-hosted)

- ER605 v2.2 (fw 2.4.5) + ES216G (fw 1.0.1) + ES206GP

- DHCP pool: 192.168.1.2–.99

Displays IP correctly:

- Wireless clients on EAP225 (connected to ES216G)

- All wired clients on ES206GP

- VIGI NVR at .200 (static, outside pool, no reservation)

Blank IP (–):

- pve1–3 at .101–103 (static, Debian Linux, have default gateway, continuous outbound traffic)

- 7 VIGI cameras at .201–207 (static)

- NGTeco TC2 access controller (static)

All devices are reachable and functioning normally — ARP scan confirms they're all on 192.168.1.0/24. Rolled back ES216G firmware 1.0.0, no change. Enabled ARP Detection, no change.

TP-Link support's explanation: Device discovery mechanisms (ONVIF, etc.). "Easy Managed switches rely on device discovery to obtain and display IP addresses. Devices that support these protocols display correctly; others may not."

The issue with that explanation: Wireless clients (phones, laptops) don't support ONVIF and display fine. Linux servers with a default gateway and continuous traffic don't display. The inconsistency makes me think there's something else going on.

Has anyone else seen this? If so, how'd you resolve it? And does anyone know the actual mechanism the controller uses to populate the wired client IP field - ARP table, DHCP leases, switch-observed traffic, or protocol discovery?

Thanks

Hi,

I’m trying to add an SG2428P switch to my Omada Controller. I already have two EAP access points adopted by the same controller without any issues.

The management IP of the switch is in my management VLAN (VLAN ID 10, 192.168.10.0/24), and the Omada Controller is also in the same VLAN.

The switch can ping the Omada Controller successfully, but it looks like the switch is not trying to communicate with the Controller when its management interface is on a non-default VLAN.

The connection to the APs is configured as a trunk, with VLAN 10 untagged (native) SSIDs vlans are tagged. The APs work correctly and are successfully connected to the Omada Controller over this connection.

I have also tried configuring the switch port with VLAN 10 both tagged and untagged, but the situation remains the same.

Is there any additional configuration required on the SG2428P for Omada management traffic when the management VLAN is not the default VLAN?

Thanks!

In a bit of a pickle here: long story short, I was having a printer issue, tried enabling mac filtering, which then resulted in me having to reset my ER605. Once the ER605 was back up and running, adopted, etc, I lost access to the OC200 via the Omada mobile app and entering the IP address in my browser. The Omada mobile app says "Connection failed make sure your controller is online and you are connected to the WLAN of your controller". The browser just constantly shows the Omaha caret ^ with a loading wheel. I regret this now 2 hr headache just to try and get a garbage Epson printer working. Is my only option now factory resetting the controller and establishing the entire network from scratch?

Since I'm one the only 10 IT guys that doesn't have a 3D printer, I'm shopping for a rack mount kit for my gateway and controller. Easy enough to find on line, mostly on Etsy. Most are for the OC200, but I think it and the OC220 have the same dimensions.

I'm just looking for feedback from anyone who's already gone down this road, recommendations, etc.

I've replaced an old N-class TP-Link outdoor router recently to an EAP225-OUTDOOR, because I figured, since I have Omada inside, may as well have it outside.
SO - I setup the AP outside at around 11 feet high on the electrical mast of the house. I know there's bout to be some interference from the electrical, but I'm sure it won't stop the signal from going through.
The AP is setup as PoE from my Omada switch. I figured by installing this there, I'm at about 40 feet from my shed, and there are 2 TP-LINK KASA KP401 operating lights and other equipment. They seem to work well enough on a 2.4GHz network... but bringing our phones or tablets outside completely messes up our summer.

Phones or tablets only work for a few moments after connection is made. After that, 3 bars drop to 2, and very soon 1 bar only. Signal stays weak all the time, and I have no understanding why.

There's a cedar tree right next to the AP; it doesn't hide the AP at all.
The AP is attached with a ziptie to the electrical mast because it's the best spot to hang it in physically, and the wire pops out of the house right underneath this.
The ethernet cable is Cat-6E, rated outdoors with a black plastic sheath.
The AP is set in a way no water comes in.
AP lights are on, all is good.
Omada has registered the AP and integrated it into the OC200 controller.

Is there anything I should be looking at to improve this access point's connections?

ModelFusion 2.5G v2.0

Firmware Version1.0.0 Build 20260611 Rel.70399

Not sure what I'm not getting here, I replaced ER7206 with Fusion Gateway, and everything works great except VPN

OpenVPN and SSL VPN both connect and i get my home IP address. But I'm unable to access devices on the LAN through VPN.

I can access the gateway, but nothing else on the network.

Also, when I try to setup Lightlink VPN it fails:

https://preview.redd.it/knvdxkssdrih1.png?width=1320&format=png&auto=webp&s=7be7a986b95f47b99d0f4a7f0dca07a7b9e2bdc8

Am I missing something?

Hi everyone,

I'm looking for some advice on a future-proof WiFi upgrade within my existing TP-Link Omada setup.

My current network consists of:

• TP-Link Omada TL-SG2428P PoE Switch
• TP-Link Omada OC200 Controller
• 2 × TP-Link Omada EAP610 (indoor)
• 1 × TP-Link Omada EAP610-Outdoor

All access points are powered through PoE and this setup has been running very reliably for several years.

I now need to improve WiFi coverage in my garage for a solar inverter and a heat pump indoor unit. My plan is to move one of the existing EAP610s to the garage and purchase a new AP for the main living area.

Since replacing the entire setup is not an option from a budget perspective, I'm considering introducing a WiFi 7 access point into the current environment as a more future-proof investment.

The models I'm currently considering are:

• TP-Link EAP770
• TP-Link EAP772

However, I'm having difficulty understanding the practical differences between these two models and whether the extra cost of the EAP772 is justified in a home environment.

Some questions:

1. Would you choose an EAP770 or an EAP772 in this situation?
2. What are the real-world differences between the two models?
3. Does it make sense to introduce a single WiFi 7 AP while the rest of the network remains WiFi 6 (EAP610)?
4. Are these APs fully compatible with my existing OC200 controller and TL-SG2428P PoE switch?
5. If you were in my position, would you buy a WiFi 7 AP today or simply add another EAP610/EAP650 and wait a few more years?

For context:

• Typical family home
• Mostly phones, laptops, tablets, smart TVs and IoT devices
• No special high-density or enterprise requirements
• Looking for reliability first, performance second

I'd appreciate any recommendations or real-world experiences.

Thanks!

Has anyone successfully had PiHole setup and working with an ER605 v2 Router and OC200 controller? I'm running out of ideas on what I could potentially be doing wrong.

I have a PiHole instance on an LXC Container on a proxmox machine. It's set up and running.

Under Site -> Device Config -> Gateway -> DNS, I selected DNS Proxy -> DNSSEC -> IP of my pihole and saved.

Under Network Config -> Network Settings -> LAN, I select the one and only VLAN i have on my network for now, edit LAN -> Advanced Settings -> DNS Server to Manual and then enter the IP of my Pihole.

Rebooted everything but ads are not blocked on any devices, neither LAN nor wifi. I have my PiHole browser interface open and do see my network devices showing up and hitting it but all of my devices are still showing ads. I've only used the default blocklist. Is the router looking at another DNS server somewhere else as well?

I've set up pihole before at my house (this is at parents house) but I'm not using the ER605.

UPDATE:

I'm not sure what i did but i finally resolved the issue... I rebooted everything including my omada switches and access points, updated the blocklist on pihole by clicking the gravity update button and it finally worked.

The only placed i changed the DNS was under the VLAN DNS Settings under Network Settings..

(Under Network Config -> Network Settings -> LAN, I select the one and only VLAN i have on my network for now, edit LAN -> Advanced Settings -> DNS Server to Manual and then enter the IP of my Pihole.)

Like many on here, I have ordered the Fusion 2.5 Gateway to replace my OC200 slow, and outdated controller. I have my fibre modem feeding a temparary ASUS router as a gateway now with wifi turned off. This router will be removed. I have two ceiling mounted Eap783's and an outdoor Eap772 connected to the present controller. My question is should I record any settings I have now or just let the Fusion gateway detect and set up my network automatically. It seems from reviews, it does this pretty well. Any tips or suggestions I should know before replacement? Thank you.

• Forescout’s Vedere Labs found 15 flaws in TP‑Link Omada business networking gear, exploitable for RCE when chained with prior CVEs
• Weak trust shortcuts in zero‑touch provisioning exposed devices to client‑side code execution, hijacking, spoofing, and encrypted comms compromise
• TP‑Link released firmware updates; admins should patch immediately, with 1,800+ Omada controllers exposed online

My network is all Omada Access level equipment. I have 3 APs, 2 celling and 1 wall all hardwired to poe switch. The mesh option is not on. The APs insist on joining with a mesh config. I have removed all of them and re-adopted. I have rebooted the controller and APs. The cable runs are solid and test fine.

If I remove and only adopt any 1 AP the uplink is the lan I have them on. If I adopt the celing mounts first, they stay non mesh with the lan uplinks. As soon as I adopt the wall AP, they all join mesh. The wall AP has additional physical ports which stay connected so the cable run is being utilized.

I have turned LLDP on and off with reboots.

What am I doing wrong here?

Everything is on the latest stable firmware.

Hi all, I'm in the final stages of upgrading my home network, from an old ISP provided router, to a new gateway and newly installed access points for better speeds and more consistent wifi throughout the home.

My final decision is on the router / gateway, which I've decided on either:

- Fusion 2.5g which I assume would be a simple setup with controller included to overview my other Omada devices, including switch and ap's.

- Opnsense, runninf on something like a Sophos device, which I expect to be a bit more work to setup, similar price, open source and greater control. I'd need a hardware or selfhosted controller for the Omada management.

I don't mind tinkering, and am happy to learn anything I don't already know regarding the setup of either, that said, I do want a system that is dependable, something that just runs without having to constantly fixing issues. I'd like to think both are fairly stable in that sense. Two things I look forward to that I can't currently do on my ISP provided router are VLAN's for splitting traffic, and VPN to access NAS services remotely, replacing Tailscale.

I'm likely appealing to a small group of people here, but has anyone used both of these, had experience and can offer any insights into which you preferred and why? Thanks.