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)

50 Reply
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
Friday

Hi  @Artur.Aragao 

 

Thank you so much for your love of our product. Your support means a great deal to us.

 

We can store logs or other files on USB sticks.

The configuration options should be on under Global View, Settings > Maintenance.  

 

As for the  TCP SYN attack concern, you may learn something from the following posts:

https://community.tp-link.com/en/business/forum/topic/649386

 

  2  
  2  
#44
Options
Re:Omada SDN Controller_V5.14.32.2 Pre-release (Updated on Oct 28th, 2024)
Friday

  @Vincent-TP

 

Hmmmmm! Really.
Thank you very much for the tip.

 

  1  
  1  
#45
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
Monday

  @Vincent-TP 

I'm running

 


Your version numbers have me a little confused. Why is the pre-release a lower version minor number 14 and updated on nov 8th? So what is this 5.15 im running? What exactly is going on here lol. 

I am running on debian  very happy to be running it on my proxmox virtual environment behiond my my PFSense VM.   on a debian production homelab vm

  0  
  0  
#46
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
Tuesday

Hi  @n0izee 

 

You are running software controller, which has a beta version 5.15.6.4.

 

This post is mainly discussing beta software for hardware controllers.  Hardware controller updates are a little slower than software controllers.

  1  
  1  
#47
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
Yesterday

  @Vincent-TP 

 

This latest version on OC200 v1 left my ER8411 in a "Disconnected" state and requiring a power cycle.

 

All other switches and EAPs were re-adopted normally.

 

No WAN settings being wiped this time.

  1  
  1  
#48
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
Yesterday

  @GRL Happens to me for the remote ERs each time there is an update. Seems to be a problem with this router, read many posts on this. Operating a SW controller, had an OC 300 before.

  0  
  0  
#49
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
Yesterday

  @Vincent-TP 

 

OK, thank you.  I did have a HW controller however.... in the world of hypervisors, containers docker docker-compose VM's etc. and of course TP Links releasing a software version of the controller, it's just easier to use the SW version. Although I might've kept the HW controller if it didn't give me so much trouble with losing access to the management interface. Mind you, I am using a Jetstream l2 managed switch. I have opted not to use the cloud SDN features on the switch, I am managing my EAPS with the SDN though. 

I do all this in my home lab and I have deployed a couple of these setups to clients. I don't know whose in charge of what over there, but if you guys could kinda tech illiterate proof the hotspot manager so that it's easier for the employees at sites where I deploy setups for them to give out Wi-Fi access codes. That'd be so great.

  0  
  0  
#50
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
Yesterday

  @GRL 

 

Thanks for the feedback. 

  0  
  0  
#51
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
8 hours ago

Eg64 wrote

  @GRL Happens to me for the remote ERs each time there is an update. Seems to be a problem with this router, read many posts on this. Operating a SW controller, had an OC 300 before.

  @Eg64 

I wanted an OC300 but ended up with the OC200, which is fine for a home lab. It's great to have a built-in backup boot mode with a recovery management interface and process for the HW controller. Honestly, a RESET button would have been much nicer. It is a huge PAIN to have to go through that process on anything other than a rare occasion for a true failed firmware update. With the SW I do this.



Yes, not best practices being logged into as root I know. But it's my home lab production mock up, still no excuse. don't sudo passwd on as fresh install, it's bad security hygiene.

I included the version info but anyway ssh has its benefits and convenience, and I'd been ok with a hard RESET button on the OC200, I wonder why they left it out? From a security standpoint, physical access is supposed to be locked in a secure area for a production network stack, so I can't imagine they were preventing malicious or mischievous pushes of said button. But still I wonder.

  0  
  0  
#52
Options
Re:Omada SDN Controller_V5.14.32 Pre-release (Updated on Nov 8th, 2024)
5 hours ago - last edited 5 hours ago

  @n0izee 

 

I have my OC 200 on its very own, basic TPlink "easy smart" poe switch (SG105PE) with POE recovery set so that if the switch cant ping the IP of the controller on its port, it waits a minute then power cycles the POE on that port.  I havent actually had any issues with being unable to access the controller, but i have tested my solution by temporarily changing my controller IP address and it works as i expected it to by hard resetting the controller. The other benefit is that if the controller is still responding to pings, but otherwise inaccessible for some reason, i can just reboot that switch from its web gui completely independantly of omada and therefore the controller would reboot too.

  0  
  0  
#53
Options