Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)

Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)

55 Reply
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
2024-10-30 15:29:31
I have a couple questions about the removal of 5.14.32.2. Wasn't the version 5.14.32.2 not just pre-release/beta/trial? It was posted to the download pages. Just wanted to make sure that was clear. Is there somewhere in which some of the reasons 5.14.32.2 was taken down is referenced? It would be good to know in case users of the container image I publish start to have issues so I can point them to a reference as I can't take down the 5.14.32.2 image because of how many people have already upgraded and changing references to older images would prevent their controllers from starting.
  0  
  0  
#33
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
2024-10-30 19:47:29

  @mbentley 

 

I would imagine the reason it was taken down entirely was due to the reasons myself and a few others have reported - under some circumstances, it is deleting and resetting WAN port settings killing internet connectivity - especially on remote managed sites

  0  
  0  
#34
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
2024-10-31 02:50:42

  @ceejaybassist 

 

Possible. Before downgrading, please make sure you have the backup file.

 

  0  
  0  
#35
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
2024-10-31 02:56:27

  @Vincent-TP Aren't the two firmwares incompatible? So backing up the config files will be useless?

  0  
  0  
#36
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)----Temporary Suspension
2024-11-06 06:45:06

  @Vincent-TP 

 

Quick question: is the FW still suspended or safe to use now? Controller shows me this version as update but have not seen any unblock notification in the forum (perhaps overlooked).

Thanks & Br's

  0  
  0  
#37
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)----Temporary Suspension
2024-11-06 06:50:48

Hi  @Eg64 

 

You may have a look at the solution of this post:

  0  
  0  
#38
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)----Temporary Suspension
2024-11-06 09:37:51

  @Vincent-TP Is there an estimated date for when the firmware will be available to download again?

  0  
  0  
#40
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)----Temporary Suspension
2024-11-06 09:55:47

  @Vincent-TP 

Thanks! Was unsure due the problem mentioned re. ISP login credentials on different sites. Exactly my use case. 
Will give it a try then.

  1  
  1  
#41
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
2024-11-08 04:25:11

  @Vincent-TP

 

So far I haven't encountered any problems since I applied the firmware.

 

I must admit that I'm really enjoying this new experience.

 

I decided to abandon the software on my computer to use an OC200 controller. When I realized that it didn't have what was in the software, I was very disappointed and even tried to understand.

 

I saw a post that made my eyes shine and my hope was greatly rekindled when I saw someone from TP-Link respond that they were working internally to make one of the features available, DPI.

 

When I was browsing the forum a little after 10/28, I came across this post and in the notes I saw a bunch of new features including DPI. Ask me how I felt? Like a child and super happy with TP-Link's competence.

 

I didn't have much time to assess the wonders introduced in the product, but I really must congratulate them.

 

I would like to make two suggestions for the OC200:

1- Storing logs on a USB flash drive - I see that the product saves logs locally and that this ends up being somewhat limited due to space constraints. Is it possible to enable the storage of logs on a USB flash drive?

 

2- I see in the logs that the TCP SYN attack blocks are effective. However, I cannot identify the device that is generating these attacks.

Ex.: 2024-11-07 17:11:13      DEVICE           WARNING          [gateway:ROUTER:00-00-00-00-00-00] Detected TCP SYN packets attack and dropped 101 packets.

 

Is it possible to do something to identify the source in the log itself? I would really like TP-Link to provide this information in the logs.

 

 

Now I have a question.

What are these Webhooks? I still don't understand what they are for, but the idea sounds very similar to APIs.

  0  
  0  
#42
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
2024-11-08 06:27:33

  @Vincent-TP  OC200(UN)_V2 upgradation successfully done, without any error.

 

  1  
  1  
#43
Options