No info after wifi
I just upgraded to 2.20.1 Build 20200630 Rel. 41064 from 2.7.0 Build 20200113 Rel. 38287.
Ever since then I get no information from the APs. They appear to work as they should and I can reboot/locate from the controller but no idea what is going on with them. I have 3, I upgraded 2 as you can see in the screenshot.
any ideas?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I upgraded the contorller to Version: 3.2.10 running on a Ubuntu server box in my house. I installed 4.1 but it would not start so I downgraded back to 3.2.10
I have "forgoten" an AP and rejoined it.. nothig I do will get them to report clients, channels or bandwidth.
Any help would be appreciated!
- Copy Link
- Report Inappropriate Content
and I'm an idiot.. I went to downgrade the firmware and noticed the 2.20 firware requires Contorller version 4.1.
I will leave my humilitation here to try and help someoneelse from making the same mistake.
- Copy Link
- Report Inappropriate Content
Hi @N0INF0,
No worries, I was just going to mention that the newer versions of EAP firmware (e.g. 2.2.0.x) require the new SDN version of Omada.
Might I recommend the OC-200. Definitely worth the ~$90 in my mind. Just plug it in, no OS/compiling/package management to worry about.
https://www.amazon.com/TP-Link-OC200-Omada-Network-Controller/dp/B07GX6GVB6/ref=sr_1_1?dchild=1&keywords=oc-200&qid=1602025756&sr=8-1
-Jonathan
- Copy Link
- Report Inappropriate Content
@JSchnee21 Thanks for the reply. I have the Ubuntu box running several things in my house so this is normaly pretty convient. I am not sure how ready for prime time 4.1.deb is since it isn't on the controller page... I had to hunt all over to find it.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
N0INF0 wrote
I have the Ubuntu box running several things in my house so this is normaly pretty convient.
In this case it has many advantages to use Omada SW Controller on your existing Linux server:
- It saves you energy compared to running an additional OC200/OC300.
- A server-based Linux is magnitudes faster than the embedded Linux running on a hardware controller's SoC.
- Required SW packages such as JRE, mogodb, curl can be updated independently from the controller software (security fixes!).
- Auto-backup works out of the box, no USB stick/PoE power supply needed.
- Nearly unlimited storage for client log entries introduced in v3.2.10 (OC200: can exhaust the internal flash memory over time).
- Direct access to the mongodb database using the mongo utility or libraries for PHP, C etc.
- Database backups can be managed using mongodump/mongorestore on the cmdline. Even allows scheduled backups using cron(8).
- Kernel scheduling priority for Omada Controller can be changed (even on the fly).
- You can install different versions of Omada Controller at the same time, this allows for easy upgrades/downgrades.
Take a look at the community versions of Omada SW Controller for Linux in this forum (pinned at top) and in the SDN forum.
As for Omada SW Controller V4.1.5: it runs fine, but still has some bugs, but OC200/OC300 have the same and even some more bugs (e.g. password reset function not working).
If you're an early adopter and have fun hunting bugs, you can switch over to V4.1.5 now. All basic functions needed for EAP management work fine, though. But if you prefer a stable version I recommend to stay with V3.2.10 until next SDN version will be released which probably will be v4.2.x.
- Copy Link
- Report Inappropriate Content
@R1D2 Thanks for the info. I am absolutly swamped at work so I will wait for a stable version.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 838
Replies: 7
Voters 0
No one has voted for it yet.