Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Closed)

Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Closed)

44 Reply
Re:Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Update on 30th Apr, 2026)
2 weeks ago

  @Vincent-TP 

The answers are the following : 

1) Version 144.0 (64-bit) FF for Mint

2) I did not notise

3) I used static IP

4) Both : The same browser window, the same sheet and new sheet. And new browser window

0
0
#43
Re:Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Update on 30th Apr, 2026)
2 weeks ago - last edited 2 weeks ago

  @MrLightBlue thanks for the clear cache tip, worked for me too. The issue happened when I updated to 1.40.18.

 

 

@Vincent-TP 

 

1. Firefox 150.0.3

2. I upgrade to 1.40.18. from the previous official version. I think it's 1.39.9

3. Automatically from DHCP

4. At first from the same page, afterwards from a different page.

1
1
#44
Re:Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Update on 30th Apr, 2026)
2 weeks ago

  @Vincent-TP When will the speed test functionality appear on OC400 firmware/controller software?

0
0
#45
Re:Hardware Controllers Omada SDN Controller 6.2.10 Pre-Release Firmware (Update on 30th Apr, 2026)
2 weeks ago - last edited 2 weeks ago

  @MrLightBlue 

MrLightBlue wrote

  @Vincent-TP 

Hi,

I have just updated my oc200 to this firmware today, as one can see :
6.2.10.151.40.15 Build 20260417 Rel.51685

 

However approximately half on button/functionalities does no longer work.
- not even the firmware "button" in the left bar in global view works. - Then it is diffuelt to update the device.

 

Nor is my client list availiable.. Device and Network config also does not work.. This is not good!

 

Is there any work around..

 

Best regards,

Frank

 

Yesterday a update poped up for me in the controller side - which i performed, since then i have the exact same situation, nothing is possible to accese, except the "device" page :-( from my default firefoxfox brwoser. in chrome and edge it worked.

1
1
#46