Omada Switch Pre-Release FW Preview for SDN Controller 6.2.X.X (Update on Apr, 1st, 2026)

Omada Switch Pre-Release FW Preview for SDN Controller 6.2.X.X (Update on Apr, 1st, 2026)

32 Reply
Re:Omada Switch Pre-Release FW Preview for SDN Controller 6.2.X.X (Update on Apr, 1st, 2026)
13 hours ago

Hi  @Vincent-TP

 

For few days I was experiencing that the PC that is connected via SG2008 v4.20, firmware 4.20.20 had problems with Ethernet connection.

The Ethernet connection was up for a while and down for a longer time, then up, and down, and...

 

Then I passed by the switch and connected PC directly to the router. All was working normally, as usually.

 

I downgraded the firmware to 4.20.19, connected it back to its original position, between the PC and the router.

Over next hour all was working normally.

  0  
  0  
#33
Options
Re:Omada Switch Pre-Release FW Preview for SDN Controller 6.2.X.X (Update on Apr, 1st, 2026)
2 hours ago - last edited 2 hours ago

  @GRL 

 

The issue I'm having is different. The PC I'm using to access the switch is on the same (management) VLAN as the switch itself. The web interface begins to load (shows graphics, shows the switch name in the title bar) but it either does not fully load (I can see the Omada logo, sometimes the login & password prompt shows up) or it will sometimes eventually load where I can log into it, but I can't navigate the tabs (L2 FEATURES, L3 FEATURES, etc).

 

Last night I was able to painstakingly get to the System Tools-->Boot Config page to roll back to "image1.bin" (1.20.21 Build 20260310 Rel.12599) which was the previous firmware. Once I did this, the issue disappeared. The version that is NOT working is 1.20.22 Build 20260313 Rel.4593.

 

One of the things I noticed in the changelog is "Added support for Private VLAN". I'm not sure what this means, but could it somehow be conflicting with my current 802.11Q VLANs?

 

The gateway issue you're describing would completely prevent / block access to the web interface - it wouldn't just load a little bit, like it did for me. I wouldn't want to specify a default gateway even if I could, because I ONLY want the management VLAN (and no other VLANs) to be able to access the web interface.

 

I should also note that while I was on the "bad" version (1.20.22 Build 20260313 Rel.4593) I could still continuously ping the router with 100% success, and less than 1ms of latency, and the switch config continued to function - so the connection to the switch is/was not the problem either. I simply could not load the web interface fully.

  0  
  0  
#34
Options