Business Community > Controllers > MongoDB that isn't ancient?
< Controllers

MongoDB that isn't ancient?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

MongoDB that isn't ancient?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
MongoDB that isn't ancient?
MongoDB that isn't ancient?
2021-09-02 05:41:06
Model: Omada Software Controller (Linux)  
Hardware Version: V4
Firmware Version:

Is there any plan to update the controller to support a version of MongoDB that isn't past EOL? Like ideally 5.x, so this doesn't happen again in a year?

I was just about to pull the trigger on some new EAP620s at work, but after attempting to spin up a test Omada controller and seeing this ridiculousness of needing Java 8 and MongoDB 3.x I'm strongly reconsidering this. I shouldn't have to make a custom install of an out-of-date OS to be able to install an out-of-date database to run a "modern" controller.

FWIW this isn't my first dance with TPLink, you may remember me as "DocJones" on the old forums; I helped figure out how to hack an external SSL cert into the software back in the day (when it was still just called "EAP Controller"). I was hoping that in the intervening years TPLink would've made some strides in software development but... I guess not? frown

  0      
 
  0      
 
#1
Options
2 Reply
Re:MongoDB that isn't ancient?
2021-09-17 16:52:19

@JessicaJ Hi, Omada is using the latest version of MongoDB that still supports Windows 7.

  0  
  0  
#2
Options
Re:MongoDB that isn't ancient?
2021-09-17 17:28:09

@MD_DE that's nice for backwards compatibility for major enterprises that have glacially slow upgrade cycles... but
 

  1. I'm not running Windows at all
  2. Windows 7 was EOL'ed over a year and a half ago

 

Trying to get that old a version of Mongo running on a Linux server is a PITA. Either I use an ancient (and thus potentially vulnerable) OS on a dedicated host/VM to get an "appropriate" version of MongoDB, or I have to try to build it myself. I don't like either solution.

 

Why not fork off "Omada Legacy" or something like that, and offer it for those who for whatever byzantine reason need that old of a system (and no longer offer upgrades to it beyond security fixes) and bring the mainline into this decade with support for a more modern software version? It seems silly to me to hobble your entire product because of a few customers' legacy needs. Or at least just develop a translation layer that allows Omada to use newer versions of MongoDB if they're available (though that still leaves much to be desired on the Java front)?

Between this, and Ubiquiti's security atrocities, I'm about to just say eff it and get Netgear access points and manage them manually. Then (hopefully) by the time our office has grown large enough to need more than a handful, where central management becomes more necessary, maybe TP-Link will have sorted this out. Or should I expect that, by 2025 when MongoDB 4.4 is EOL, they'll just be getting around to including support for MongoDB 4?

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 7

Replies: 0

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.