Early Access Omada SDN Controller_V5.12 (Updated on Sep 20th, 2023) [Thread Closed]
Update as of Sep 20, 2023:
Thank you all for your valuable feedback on the Omada SDN Controller V5.12 Beta!
The 5.12 beta has been updated to official release, and this early access post is locked for further replies.
Omada Software Controller_V5.12.7 (Released on Sep 20th, 2023)
Omada Hardware Controller_V5.12.9 (Released on Sep 19th, 2023)
Any further questions or assistance needed with Omada SDN Controller, please feel free to contact TP-Link Tech Support by submitting a support ticket or connect with community by clicking Start a New Thread in the Business Community forums.
This Article Applies to
Omada_SDN_Controller_v5.12.7_Windows (Windows 7/8/10/11/Server, 64bit Recommended)
Omada_SDN_Controller_v5.12.7_Linux_x64.tar.gz (Ubuntu 16.04/18.04/20.04, Debian 8/9/10, CentOS 6/7)
Omada_SDN_Controller_v5.12.7_Linux_x64.deb (Ubuntu 16.04/18.04/20.04, Debian 8/9/10)
OC200(UN)_V1_1.26.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
OC200(UN)_V2_2.11.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
OC300(UN)_V1_1.19.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
Overview
We hope to offer you with a chance to experience the new features added in the Controller v5.12 in advance, and also give us TP-Link the opportunity to fully test the firmware in your real network environment and scenarios before the official release. All feedback is welcome, including lettings us know about successful upgrades.
Release Notes
Notice: If you are using Web API, please take note that Cookie name has been changed from TPEAP_SESSIONID to TPOMADA_SESSIONID.
New Feature
1. Facebook Wi-Fi Removal: Due to changes implemented by Facebook, the Facebook Wi-Fi function has been removed.
2. Expanded Device Support: Added support for wireless router ER706W.
3. Managed Service Provider (MSP) Mode: The Omada Controller now (except the OC200 and OC300) includes an MSP mode, allowing you to monitor the overall status of your customers and manage customers within the Omada platform. To use this mode, enable it first in Global view > ⋮ icon in the top-right corner > Enable MSP mode, you can also disable it from the same location. In MSP mode, you could auto back up settings of all sites under one customer account.
4. Expanded Language Support: Added support for Deutsch, العربية, Polski, Čeština, Slovenčina and Magyar. Please note that the content of some pages has not yet been fully adapted to العربية, and will be improved subsequently.
5. Open API: Omada Controller now supports Open API integration. You can access it through Global view > Settings > Platform Integration, which allows you to utilize the REST API of most Controller services. This feature enables you to develop custom applications, embed APIs, or combine your own applications. Refer to the Online API Document for guidance on usage, and view more by toggling the drop-down menu in the upper left corner.
6. Multi-language Voucher Code Print: Added support for printing voucher codes in multiple languages. You could choose your preferred language to be displayed on vouchers. The available language choices include English, Čeština, Deutsch, Français, Español, Nederlands, Italiano, Polski, Português, Русский, Türkçe, ﺔﻴﺑﺮﻌﻟا, 日本語, 中文(繁體), 한국어, Slovenčina and Magyar.
7. Intrusion Detection and Prevention System (IDS/IPS): IDS/IPS feature has been introduced to monitor network intrusions. Firmware update is required to use this feature. Once updated, you could access it in Site view > Settings > Network Security. Please refer to the release note of the device firmware for details on which Omada devices support this feature.
8. Port Schedule: Added support for schedules applied to ports of switch in Site View > Settings > Services > Port Schedule, allowing you to make schedule of when PoE or Port works for desired ports.
9. MAC Group Export: Added support for exporting MAC groups, making it easier to migrate MAC groups or edit MAC addresses.
10. Hotspot Operator Role: Added Role Admin/Viewer for Hotspot operator in Hotspot Manager, allowing you to assign write or read only privileges for different users according to demand.
11. Switch ACL Bingding with VLAN on Desired Switches: Added support for applying VLAN bound ACL to switches as your needs.
12. CHAP and LDAP in Portal: Added support for CHAP encryption in portal, allowing for secure authentication when used in conjunction with External Portal functionality; added support for LDAP (Lightweight Directory Access Protocol), enabling seamless integration with LDAP server for user authentication.
13. Account Permission Transfer: Added support for transferring account permissions. This feature is available in Global view > Account, and it allows you to change the Main Administrator account.
14. Multiple Upgrade Schedules: Added support for creating more schedules on upgrade plan.
15. Built-in RADIUS Server: A built-in RADIUS server has been added in Global > Settings > Server Settings, which can be used for WPA-Enterprise, Portal RADIUS Server and 802.1X.
16. Public IP Address Display: Remotely managed devices now show their public IP addresses in Devices > PUBLIC IP ADDRESS column.
17. Voucher Group and Voucher Statistics: Introduced Voucher Group and Voucher Statistics in the Hotspot Manager, which enables you to manage and monitor vouchers by group.
18. Omada Gateway New Features: Several new features have been made to the Omada Gateway, requiring firmware update:
- IPv6 Support in Gateway ACL
You could now block IPv6 traffic through Gateway ACL settings.
- IPv6 RA (Router Advertisement)
Added support to configure IPv6 RA for the Omada Gateway.
- MAC Filtering
Added support for MAC filter in Site view > Settings > Network Security > MAC Filtering.
- Session Limit Monitoring
Introduced support for monitoring session limits in Site view > Insight. This feature displays the number of sessions being used by a single IP address.
- MSS Clamping
Added support for MSS (Maximum Segment Size) clamping in Site view > Settings > Wired Networks > Internet > PPPoE > Advanced Settings. MSS Clamping allows you to specify the upper limit for the value of the MSS field negotiated during TPC connection establishment, preventing IP fragmentation.
- DNS Cache
Added support for DNS cache in Site view > Settings > Services. DNS cache improves domain name resolution speed by handling recent address resolutions locally before sending request to Internet.
- Gateway Tools
Added Ping, Traceroute and Terminal tools to the Gateway.
- Device Info Download
Introduced the ability to download device info of the Gateway. To access the feature, open the sidebar of Gateway, navigate to Config > Manage Device, and click Download. Omada Controller uses TCP port 29815 to receive device info.
- IPsec Algorithm Enhancements
Added support for AES256, dh 14, dh 15 of IPsec algorithms.
- IPsec Client-to Site VPN
Added support for 0.0.0.0/0 IP range of local network when using IPsec for Client-to Site VPN.
- Internet VLAN
Added support for tagging the same VLAN ID on different Internet networks.
- WAN IP Alias
Added support for WAN IP Alias in Site view > Settings > Wired Networks > Internet. This feature allows you to configure multiple IP addresses on a single WAN port and use these IP addresses for port forwarding.
- Location Group in Gateway ACL
Introduced Location Group support in Gateway ACL, allowing you to block data from or to specific locations.
- Log Enhancements
Logs now show the source IP address of TCP no-Flag /ping of death attacks and changes in ISP network during link backup. Besides, added support for more logs of Gateway, which helps to manage and maintain the network.
- Flow Control
Added support for Flow Control in Devices > Ports of Omada Gateways.
- Custom Update Interval for DDNS
Added support for changing update interval of DDNS to 1~60 minutes.
19. Client Idle Threshold: Added the Client Idle Threshold option in Global view > Settings > Controller Settings. This allows you to specify the interval after which Omada Controller will claim a client is disconnected if it fails to report its status within that timeframe.
20. Map Enhancements: Added support for exportation of topology, Heat Map report and search box in Map. Added display of RSSI of EAP in Heat Map.
21. Release Note Display: You can now view release note directly in Omada Controller when clicking the device upgrade mark. This provides easier access to information about changes in new firmware versions.
22. Wireless Mode Configuration: Added support for changing the wireless mode of EAP in Devices > Config > Radios, which allows you to select the desired 802.11 mode for Omada EAP.
23. Device search in Statistics: Introduced the ability to search for devices in Statistics. This feature enables you to quickly find statistical results of specific devices.
24. Cloud Access Data Export: Added support for exporting data through cloud access.
25. System Logging level: Added support for changing System Logging level in Global view > Settings > System Settings. This feature facilitates debug log collection by allowing you to set the Logging Level Type to "custom" and select the desired debug level for the logs you need.
Enhancement
1. Site Limit: Expaneded the limit of sites to 5, 000.
2. Voucher Usage Calculation: Voucher now could calculate the usage time based on the user's actual online time.
3. AI WLAN optimization: Improved algorithm for better optimization results.
4. MAC Group: Added support for Add by Range when importing MAC address, which allows you to add multiple continuous MAC addresses through their range.
5. IP Address Input: Verification rule of input IP addresses has been updated to allow you to add legitimate IP address with 0 in the last segment.
6. Invitation E-mail: Added inviter username and Controller Name into e-mail body.
7. Client: Added support for showing SNR (Signal to Noise Ratio) in Clinet page.
8. Backup & Restore: Settings only backup will not include device information.
9. DHCP Reservation: Added support for search box and batch delete in DHCP reservation items, which helps you manage these items conveniently.
10. NTP Configuration: Moved NTP configuration from Global view to Site view, which makes you possible to manage sites with different timezones.
11. SMTP Server Location: Moved SMTP server from Global view > Settings > Controller Settings to Global view > Settings > Server Settings.
12. Alert E-mail: Added Controller and site name into title of alert e-mail.
13. Portal Profile Background: Background picture of portal profile could adapt to different screen sizes of laptops and mobiles.
14. Update Notification: Added choice of Controller/Device Update notification in Quick Setup process.
15. Client Page Illustration: Added illustration of icons in Clients Page, such as in Connection Type and Wireless Connection.
Notes
1. This version of the Controller is fully applied to the Omada APP of version 4.10 or above.
2. Omada SDN Controller can only manage certain devices running the supported firmware. Please confirm that your device is compatible with the SDN Controller.
3. For Windows OS, Java 8 (or OpenJDK-8) and above are required. How to install Java Runtime Environment (JRE) for Omada SDN Controller on Windows?
4. If you are upgrading from controller v3.x, it's highly recommended to upgrade 3.x to v4.1.5 first, then v4.1.5 to the latest 5.x. Please follow the Omada Controller Upgrade Guide in the installation package before upgrading.
Firmware Download
Before the Upgrade
(1) Please be sure you have read the Beta Test Agreement before upgrading the Beta firmware!
(2) For the sake of insurance, it's always recommended to save a copy of the controller Backup Config file before upgrade or downgrade.
(3) You may follow the following guide to upgrade your Omada Controller. How to Upgrade or Downgrade Omada SDN Controller
(4) The following beta firmware cannot be upgraded via TP-Link cloud access, please access the controller through the local IP for the manual upgrade option. And you can continue to access your controller via TP-Link cloud after you install the following 5.12 firmware.
Firmware Download Link
-
Direct Download
Omada_SDN_Controller_V5.12.6_Windows (Beta)
Omada_SDN_Controller_v5.12.6_Linux_x64.deb (Beta)
Omada_SDN_Controller_v5.12.6_Linux_x64.tar.gz (Beta)
Omada_SDN_Controller_V5.12.7_Windows
Omada_SDN_Controller_v5.12.7_Linux_x64.deb
Omada_SDN_Controller_v5.12.7_Linux_x64.tar.gz
OC200(UN)_V1_1.26.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
OC200(UN)_V2_2.11.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
OC300(UN)_V1_1.19.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
OC200(UN)_V1_1.26.3_Build 20230906 (Beta) > Built-in Omada SDN Controller 5.12.9
OC200(UN)_V2_2.11.3_Build 20230906 (Beta) > Built-in Omada SDN Controller 5.12.9
OC300(UN)_V1_1.19.3_Build 20230906 (Beta) > Built-in Omada SDN Controller 5.12.9
OC200(UN)_V1_1.26.3_Build 20230906 > Built-in Omada SDN Controller 5.12.9
OC200(UN)_V2_2.11.3_Build 20230906 > Built-in Omada SDN Controller 5.12.9
OC300(UN)_V1_1.19.3_Build 20230906 > Built-in Omada SDN Controller 5.12.9
-
Download From TP-Link Global "EN" Website:
Omada Controller_Windows/Linux: https://www.tp-link.com/en/support/download/omada-software-controller
OC200 v1/v1.6: https://www.tp-link.com/en/support/download/oc200/v1/#Firmware
OC200 v2/v2.6: https://www.tp-link.com/en/support/download/oc200/v2/#Firmware
OC300 v1/v1.6: https://www.tp-link.com/en/support/download/oc300/#Firmware
Additional Information
If somehow you encounter an issue during or after the controller upgrade, it's suggested to contact us with the following info:
- Omada Controller version (previous and current)
- Device Model(s), Hardware and Firmware versions
- (if possible) A copy of the Log file and Backup Config file
If you decide to downgrade the controller before reporting the issue to TP-Link, it's suggested to save a copy of the current Log file and Backup Config file before you do that, which could help to investigate and address the issue quickly.
>> How to get the Log file and Backup Config file for Omada SDN Controller:
-
If your windows software controller failed to get launched, please locate to the controller installation path for the Log file.
-
If it's not a launch issue, you can export the Log file and Backup Config file in the local network.
-
For Omada Controller v5.8 or later version,
In the Global View, go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.
-
For Omada Controller v5.6 or v5.7,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file. On the same page, scroll down for Export for Support, click Export Running Logs for desensitized Log file.
-
For Omada Controller v5.5 or previous version,
Go to Settings > Maintenance > Backup & Restore > Retained Data Backup, select Settings Only, then click Export for the Backup Config file . Go to Settings > Services > Export Data > Running Log to export the Log file.
-
Update Log
Sep 20th, 2023:
Update the Omada Software Controller beta version to official release.
-
Before
Omada_SDN_Controller_V5.12.6_Windows (Beta)
Omada_SDN_Controller_v5.12.6_Linux_x64.deb (Beta)
Omada_SDN_Controller_v5.12.6_Linux_x64.tar.gz (Beta)
-
After
Omada_SDN_Controller_V5.12.7_Windows
Omada_SDN_Controller_v5.12.7_Linux_x64.deb
Omada_SDN_Controller_v5.12.7_Linux_x64.tar.gz
Sep 19th, 2023:
Update the OC200 v1/v2 and OC300 v1 beta firmware to official release.
-
Before
OC200(UN)_V1_1.26.3_Build 20230906 (Beta) > Built-in Omada SDN Controller 5.12.9
OC200(UN)_V2_2.11.3_Build 20230906 (Beta) > Built-in Omada SDN Controller 5.12.9
OC300(UN)_V1_1.19.3_Build 20230906 (Beta) > Built-in Omada SDN Controller 5.12.9
-
After
OC200(UN)_V1_1.26.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
OC200(UN)_V2_2.11.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
OC300(UN)_V1_1.19.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
Sep 13th, 2023:
Update the OC200 v1/v2 and OC300 v1 controller firmware, which fixed some issues.
-
Before
OC200(UN)_V1_1.26.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
OC200(UN)_V2_2.11.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
OC300(UN)_V1_1.19.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
-
After
OC200(UN)_V1_1.26.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
OC200(UN)_V2_2.11.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
OC300(UN)_V1_1.19.3_Build 20230906 (Built-in Omada SDN Controller 5.12.9)
Sep 4th, 2023:
Add the following controller firmware for early access.
- Omada_SDN_Controller_v5.12.6_Linux_x64.deb (Beta)
- Omada_SDN_Controller_v5.12.6_Linux_x64.tar.gz (Beta)
Aug 21st, 2023:
Add the following controller firmware for early access.
- OC200(UN)_V1_1.26.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
- OC200(UN)_V2_2.11.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
- OC300(UN)_V1_1.19.2_Build 20230817 (Beta) > Built-in Omada SDN Controller 5.12.8
Aug 18th, 2023:
Provide the following controller firmware for early access.
- Omada_SDN_Controller_V5.12.6_Windows (Beta)
Recommended Threads
Get the Latest Omada SDN Controller Releases Here - Subscribe for Updates
Experience the Latest Omada EAP Firmware - Trial Available Here, Subscribe for Updates!
Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
using 5.12 cloud or hardware controller 6ghz is no longer usuable. Channel can be set but it reports 33 always and no devices can connect to it.
- Copy Link
- Report Inappropriate Content
Hello everyone and @Fae!
Running an ER7206 with the latest firmware (1.4.0 build 20230828 Rel.58568) and Omada SDN Controller v5.12.6 beta in a Debian LXC. I've got a pair of PowerEdge servers in a co-lo I've been managing this setup (to pair with an identical setup back at home), and my networking setup has a couple of peculiarities that have me scratching my head.
WAN IP Aliasing
I've got two separate /28 public IP subnets on one physical connection—no VLANs. Was pretty stoked about the WAN IP aliasing feature. But when I tried setting it up, the UI threw me for a loop. It asks for a 'subnet', yet it seems like it only wants an IP address. When I punched in the IP, tried to swap out 1:1 NAT and routed ports 80 and 443, nothing got through to my Nginx proxy manager. Worked like a charm with 1:1 NAT, so what gives?
Questions:
- How does WAN IP aliasing work with single physical connections and multiple /28s or other subnets?
- Does this feature jive with subnets that are spatially apart in the addressing?
- Anything specific I need to do differently versus 1:1 NAT?
Threat Alerts and Block Lists
Switching gears, I enabled some of the newer threat prevention features. Now I'm swamped with DShield IP alerts. That's fine and dandy as I love me some alerts, but when I try to blacklist these suckers, I hit a wall before even reaching 100 entries. Seems pretty limited IMO.
Questions:
- What's the cap on this block list?
- Can it support Regex or be extended with lists like PiHole or PFBlockerNG?
- How do I manage or remove IPs from the threat analysis if I can't add 'em to the block list?
Would appreciate any tips, tricks, or insights. This isn't just about solving my problems; I'm pretty sure this could help others stuck in similar spots.
Cheers!
- Copy Link
- Report Inappropriate Content
I am running OC200(UN)_V1_1.26.2_Build 20230817. I am getting many, "Router/Gateway detected TCP SYN-and-FIN packets attack and dropped xx packets" and "Router/Gateway detected TCP no-Flag attack and dropped xx packets." errors every hour. Avoiding these excessive (and likely false) log entries and warnings was one of the reasons I decided to download and install this beta firmware version. If anything, this version has made the situation worse.
- Copy Link
- Report Inappropriate Content
Hi Fae
I've got 7 AP's hanging off my OC200 v1 and 3 of them (2 x eap225 fw 5.1.0 and 1 x eap235-wall fw 3.1.1) after upgrade to the beta FW they refused to take any clients even though some of the clients are less then a couple of metres from the AP's. The only way I could gets clients to reconnect (some of the clients are fixed to those AP's as well) was to un-adopt them, factory reset them and then re-adopt, after that everything started reconnecting on those AP's.
Lee...
- Copy Link
- Report Inappropriate Content
Hello @IamMurphy,
IamMurphy wrote
using 5.12 cloud or hardware controller 6ghz is no longer usuable. Channel can be set but it reports 33 always and no devices can connect to it.
Do you mean that the 6GHz is working fine before you upgrade to 5.12 controller? If so, what is the previous version of your controller? Are you using OC200 v1/v2 or OC300 v1?
After you manual fix the channel 117 on 6GHz, you may wait for a couple minutes and then refresh the controller page to check whether the channel utilization will report the channel 117.
Regarding the issue that no devices can connect to 6GHz, please ensure that your client device is 6 GHz capable first. And please check whether there is any error message from your client device or controller log when your 6GHz capable client failed to connect to the EAP690E on 6GHz band.
- Copy Link
- Report Inappropriate Content
Hello @gknac,
gknac wrote
WAN IP Aliasing
I've got two separate /28 public IP subnets on one physical connection—no VLANs. Was pretty stoked about the WAN IP aliasing feature. But when I tried setting it up, the UI threw me for a loop. It asks for a 'subnet', yet it seems like it only wants an IP address. When I punched in the IP, tried to swap out 1:1 NAT and routed ports 80 and 443, nothing got through to my Nginx proxy manager. Worked like a charm with 1:1 NAT, so what gives?
Questions:
- How does WAN IP aliasing work with single physical connections and multiple /28s or other subnets?
- Does this feature jive with subnets that are spatially apart in the addressing?
- Anything specific I need to do differently versus 1:1 NAT?
WAN IP Alias supports configuring multiple IP addresses on one WAN port, and these IP addresses can be used to configure virtual server and other functions.
When configuring WAN IP Alias with multiple public IP subnets, you may need to add the IP addresses one by one, just like the example config shown below. (If needed, you can google for IP Subnet Calculator to get the IP addresses.)
Regarding One-to-One NAT, please notice that it only takes effect when the connection type of the corresponding WAN port is Static IP.
How to configure One-to-One NAT
If it doesn't help, please feel free to report back, we may need to check your detailed configuration via email for further investigation.
gknac wrote
Threat Alerts and Block Lists
Switching gears, I enabled some of the newer threat prevention features. Now I'm swamped with DShield IP alerts. That's fine and dandy as I love me some alerts, but when I try to blacklist these suckers, I hit a wall before even reaching 100 entries. Seems pretty limited IMO.
Questions:
- What's the cap on this block list?
- Can it support Regex or be extended with lists like PiHole or PFBlockerNG?
- How do I manage or remove IPs from the threat analysis if I can't add 'em to the block list?
If I didn't get it wrong, you were trying to click the Block icon from the Clients list, and have the questions about the Block list, is that right?
For the cap on the block list, I think you have get the answer when you failed to add more clients into the block list. (I haven't tried to reach the cap yet, so I don't have the exact number for you now.) And I'm afraid that it may not support Regex or be extended with lists like PiHole or PFBlockerNG.
To remove the clients from the blocked list, you may go to Insights > Known Clients > Blocked tab for unblock incon.
- Copy Link
- Report Inappropriate Content
Hello @lflorack,
lflorack wrote
I am running OC200(UN)_V1_1.26.2_Build 20230817. I am getting many, "Router/Gateway detected TCP SYN-and-FIN packets attack and dropped xx packets" and "Router/Gateway detected TCP no-Flag attack and dropped xx packets." errors every hour. Avoiding these excessive (and likely false) log entries and warnings was one of the reasons I decided to download and install this beta firmware version. If anything, this version has made the situation worse.
What's the current firmware version of your ER605 V1 router?
- Copy Link
- Report Inappropriate Content
Hello @MantonL,
MantonL wrote
I've got 7 AP's hanging off my OC200 v1 and 3 of them (2 x eap225 fw 5.1.0 and 1 x eap235-wall fw 3.1.1) after upgrade to the beta FW they refused to take any clients even though some of the clients are less then a couple of metres from the AP's. The only way I could gets clients to reconnect (some of the clients are fixed to those AP's as well) was to un-adopt them, factory reset them and then re-adopt, after that everything started reconnecting on those AP's.
Our support engineers would like to check more details with you to look into the issue further. I've created a support ticket via your registered email address, the ticket ID is TKID230917364, if you're willing to help, please pay attention to this ticket email and respond to the support engineer. Thanks!
- Copy Link
- Report Inappropriate Content
Hello @RigpaCastanon,
RigpaCastanon wrote
Caption@RigpaCastanon now what i dow
Upon your screenshot, it seems that your ER605 got into DISCONNECTED state, while the TL-SG2008 v4 was still Connected with a valid IP address. Was your ER605 V2 disconnected right after you install the Controller v5.12? If yes, what's the previous version of your Omada Controller? And what's the current firmware version of your ER605 V2?
If your ER605 V2 is still shown as DISCONNECTED in your Omada Controller, please try the following suggestions and see if it works.
1. Forget the ER605 of "Disconnected" state from the Controller page (it will not actually reset ER605 since it is not managed by the controller now).
2. Try to access the standalone web UI of ER605 via its IP address, go to System Tools > Controller Settings, and configure the Controller Inform URL with the IP address of your Controller host.
3. If it doesn't help, please reset the ER605 and re-adopt it to have a check.
If there is anything new came up, please try to elaborate on the issue so that we can help you further.
We look forward to hearing back from you.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 4
Views: 30392
Replies: 110