Qnap [ TPLink Omada ] [ 5.9.31 ] configuring and managing your Omada EAPs

QoolBox

Représentant QNAP
2 Janvier 2014
10 559
163
153
49
France
www.qnap.com
qpkg_icon_80.gif


Source : https://www.tp-link.com/ca/business-networking/omada-eap/

Download :


About :

Omada Controller is a management software for TP-Link EAPs. With this software, you can centrally manage your EAPs, such as configure EAPs in batches and conduct real-time monitoring of EAPslocally or remotely through Omada Cloud service.

TP-Link Omada. Omada app is used for configuring and managing your Omada EAPs. You can change settings, monitor the network status and manage clients, all from the convenience of a smart phone or tablet. Standalone mode is designed for managing EAPs right away without having to spend time configuring a controller.

Centralized Software Controller

EAP Controller
Monitor and manage hundreds of EAPs in a single or multiple sites
Free cloud access to manage from anywhere, anytime
Configure and automatically synchronize unified wireless settings to all EAPs in the network
Free to use, no license fee or extra cost required
Secure Guest Network with Facebook Wi-Fi and SMS Authentication
Rate Limit and Load Balance ensure the network stability and efficiency
Access Control and Rogue AP Detection protect the network from threats

Note

Apache82 as dependency

user guide : https://www.tp-link.com/ca/support/download/eap-controller/

EAP-Controller.png
 
Dernière édition:
  • J'aime
Réactions: giopas
bump to 4.3.5

Code:
Some new functions of the Controller require device firmware support, and the supporting firmware for routers and switches will be released soon.

Supported device models and firmware:
EAP:
EAP110_V4 3.20.0 Build 20200525 Rel. 36899 and above
EAP115_V4 3.20.0 Build 20200525 Rel.36931 and above
EAP225_V3 2.20.0 Build 20200422 Rel. 70513 and above
EAP245_V3 2.20.0 Build 20200423 Rel. 36779 and above
EAP115-Wall_V1 1.20.0 Build 20200509 Rel. 63986 and above
EAP225-Wall_V2 1.20.0 Build 20200422 Rel. 70504 and above
EAP110-Outdoor_V3 3.20.0 Build 20200511 Rel. 33388 and above
EAP225-Outdoor_V1 1.20.0 Build 20200422 Rel. 70543 and above
EAP265 HD, EAP230-Wall, EAP235-Wall, EAP660 HD, EAP620 HD
Switch:
TL_SG3428MP, TL_SG3428, SG3428X, TL_SG3428XMP, TL-SG3452P, TL-SG3452, 
TL-SG3210XHP-M2, TL-SG3210_V3, TL-SX3008F,
TL-SG2428P, TL-SL2428P_V4.2, TL-SG2210MP, TL-SG2210P_V3.20, TL-SG2218, 
TL-SG2008P, TL-SG2008
Gateway:
ER605, ER7206

New Feature/Enhancement:
1. Add daylight saving time function.
2. Portal supports multiple entries. Local user accounts and voucher codes support binding to different portal entries.
3. Add daily/weekly/monthly limit in Voucher/Local User traffic limit function.
4. Add rate limit templates for SSID and Client rate limit modules.
5. Cancel the site administrator's authority for global configuration, such as controller general and maintenance settings.
For Router:
6. Add IPv6 function.
7. Add L2TP/PPTP interface in the static routing and policy routing function.
8. Add Firewall-State timeout at Settings-Network Security.
9. Add Router Table, Dynamic DNS, VPN Status, Port Forwarding Status in the Insight list.
10. Add ISP Load card and VPNs card in the Dashboard.
For Switch:
11. Add layer-3 function for L2+ switches.
12. Add ethertype value for switch ACL.
13. Add Switch Status in the Insight list.
14. Optimize the configuration logic for Switch STP and loopback detection function.
15. Add PoE utilization card in the Dashboard.
16. Add switch S/N information at Devices-Details-Overview
For EAP:
17. Add AI-Roaming function.
18. Add RADIUS DM function in portal RADIUS authentication.
19. Add dynamic VLAN feature in RADIUS profile.
20. Add OFDMA switch button for AX EAP.

Bug Fixed:
1. Fixed the bug that the local user can still access the Internet after re-authenticating, though it has reached the upper traffic limit.
2. Fixed the bug that the PoE scheduler may not take effect.
3. Fixed the bug that the Omada Controller frequently prints roaming logs in the log list.
4. Fixed the bug that the settings of PAP and CHAP authentication mode are inverse in the Controller.
5. Fixed the bug that we may not be able to configure or disable the portal authentication (with general error occurs) sometimes.
6. Fixed the bug that we can¡¯t set VPN servers in different Controller sites in the meantime.
7. Fixed the bug that the SDN Controller does not support spaces character and Nordic script.
8. Fixed the bug that the Controller may not restore the backup file successfully if the backup file is too large (80MB or above).

Notes:
1. Omada SDN Controller can configure and manage only certain devices with supported firmware. You need to make sure your device is compatible with Omada SDN Controller.
2. If you are using Omada Controller and plan to upgrade to this version, please follow the procedure of Omada Controller Upgrade Guide.
3. Once upgraded to this version of Omada Controller, you will be NOT able to downgrade to an earlier version. 
4. This version of the controller is applied to Omada APP of version 3.0.X or above.
5. Controller needs Java 8 and MongoDB 3.0-3.6 environment for running. 
6. Support 64-bit Linux operating system including Ubuntu 14.04/16.04/17.04/18.04, CentOS 6.x/7.x and Fedora 20 or above, Debian.
7. You may need to save the backup file and uninstall the old Omada Controller before installing this software.
 
Hello, I bought your Apache81 qpkg to be working with your Omada(Apache81) but nothing is working. Do you provide support or setup configuration somewhere ? Thanks.
 
effectivement, avec ce firmware j'ai des erreurs de segmentation sur mongodb... va falloir que je comprenne pourquoi

2022-09-24T07:49:36.905+0000 F - [initandlisten] Invalid access at address: 0
2022-09-24T07:49:36.915+0000 F - [initandlisten] Got signal: 11 (Segmentation fault).
0x557cd60a4f21 0x557cd60a453c 0x557cd60a4720 0x7f311537c6f0 0x7f31150f0a06 0x7f3116249ca5 0x7f31161954c1 0x7f3114d6b61b 0x7f3115379deb 0x7f3114a3b6f9 0x7f3114d6b807 0x7f31167fb1b0 0x7f31167b764b 0x557cd603e0fa 0x557cd49df662 0x557cd4582910 0x557cd4584d92 0x557cd4505519 0x7f3114fe9810 0x557cd457fea9
----- BEGIN BACKTRACE -----
{"backtrace":[{"b":"557CD37E5000","o":"28BFF21","s":"_ZN5mongo15printStackTraceERSo"},{"b":"557CD37E5000","o":"28BF53C"},{"b":"557CD37E5000","o":"28BF720"},{"b":"7F311536C000","o":"106F0"},{"b":"7F3114FC9000","o":"127A06"},{"b":"7F3116129000","o":"120CA5","s":"lh_insert"},{"b":"7F3116129000","o":"6C4C1","s":"OBJ_NAME_add"},{"b":"7F3114D34000","o":"3761B"},{"b":"7F311536C000","o":"DDEB"},{"b":"7F3114842000","o":"1F96F9","s":"CRYPTO_THREAD_run_once"},{"b":"7F3114D34000","o":"37807","s":"OPENSSL_init_ssl"},{"b":"7F311679D000","o":"5E1B0"},{"b":"7F311679D000","o":"1A64B"},{"b":"557CD37E5000","o":"28590FA","s":"_ZN5mongo10HttpClient6createEv"},{"b":"557CD37E5000","o":"11FA662","s":"_ZN5mongo19startFreeMonitoringEPNS_14ServiceContextE"},{"b":"557CD37E5000","o":"D9D910"},{"b":"557CD37E5000","o":"D9FD92"},{"b":"557CD37E5000","o":"D20519"},{"b":"7F3114FC9000","o":"20810","s":"__libc_start_main"},{"b":"557CD37E5000","o":"D9AEA9","s":"_start"}],"processInfo":{ "mongodbVersion" : "4.2.8-53-g98a7db0", "gitVersion" : "98a7db0a562b818426c19203e8d16cc93980b279", "compiledModules" : [], "uname" : { "sysname" : "Linux", "release" : "5.10.60-qnap", "version" : "#1 SMP Sat Sep 3 05:21:01 CST 2022", "machine" : "x86_64" }, "somap" : [ { "b" : "557CD37E5000", "elfType" : 3, "buildId" : "85EBF0994B9493E0975A083C40C338972F5176DB" }, { "b" : "7FFCF4F4B000", "path" : "linux-vdso.so.1", "elfType" : 3, "buildId" : "EFB1F67B0D74A0BA369F872980D9A2545F4E8F96" }, { "b" : "7F311679D000", "path" : "/usr/lib/libcurl.so.4", "elfType" : 3 }, { "b" : "7F3116585000", "path" : "/lib/libresolv.so.2", "elfType" : 3 }, { "b" : "7F3116129000", "path" : "/share/CACHEDEV1_DATA/.qpkg/Omada581/lib/libcrypto.so.1.0.0", "elfType" : 3 }, { "b" : "7F3115EB0000", "path" : "/share/CACHEDEV1_DATA/.qpkg/Omada581/lib/libssl.so.1.0.0", "elfType" : 3 }, { "b" : "7F3115CAC000", "path" : "/lib/libdl.so.2", "elfType" : 3 }, { "b" : "7F3115AA4000", "path" : "/lib/librt.so.1", "elfType" : 3 }, { "b" : "7F311579F000", "path" : "/lib/libm.so.6", "elfType" : 3 }, { "b" : "7F3115589000", "path" : "/lib/libgcc_s.so.1", "elfType" : 3 }, { "b" : "7F311536C000", "path" : "/lib/libpthread.so.0", "elfType" : 3 }, { "b" : "7F3114FC9000", "path" : "/lib/libc.so.6", "elfType" : 3 }, { "b" : "7F3116A22000", "path" : "/lib64/ld-linux-x86-64.so.2", "elfType" : 3 }, { "b" : "7F3114D34000", "path" : "/lib/libssl.so.1.1", "elfType" : 3 }, { "b" : "7F3114842000", "path" : "/usr/lib/libcrypto.so.1.1", "elfType" : 3 }, { "b" : "7F3114628000", "path" : "/lib/libz.so.1", "elfType" : 3 }, { "b" : "7F311441C000", "path" : "/usr/lib/libkrb5support.so.0", "elfType" : 3 }, { "b" : "7F3114139000", "path" : "/lib/libiconv.so.2", "elfType" : 3 }, { "b" : "7F3113F07000", "path" : "/usr/lib/libidn.so.11", "elfType" : 3 } ] }}
mongod(_ZN5mongo15printStackTraceERSo+0x41) [0x557cd60a4f21]
mongod(+0x28BF53C) [0x557cd60a453c]
mongod(+0x28BF720) [0x557cd60a4720]
libpthread.so.0(+0x106F0) [0x7f311537c6f0]
libc.so.6(+0x127A06) [0x7f31150f0a06]
libcrypto.so.1.0.0(lh_insert+0x135) [0x7f3116249ca5]
libcrypto.so.1.0.0(OBJ_NAME_add+0x71) [0x7f31161954c1]
libssl.so.1.1(+0x3761B) [0x7f3114d6b61b]
libpthread.so.0(+0xDDEB) [0x7f3115379deb]
libcrypto.so.1.1(CRYPTO_THREAD_run_once+0x9) [0x7f3114a3b6f9]
libssl.so.1.1(OPENSSL_init_ssl+0x67) [0x7f3114d6b807]
libcurl.so.4(+0x5E1B0) [0x7f31167fb1b0]
libcurl.so.4(+0x1A64B) [0x7f31167b764b]
mongod(_ZN5mongo10HttpClient6createEv+0x17A) [0x557cd603e0fa]
mongod(_ZN5mongo19startFreeMonitoringEPNS_14ServiceContextE+0x422) [0x557cd49df662]
mongod(+0xD9D910) [0x557cd4582910]
mongod(+0xD9FD92) [0x557cd4584d92]
mongod(+0xD20519) [0x557cd4505519]
libc.so.6(__libc_start_main+0xF0) [0x7f3114fe9810]
mongod(_start+0x29) [0x557cd457fea9]
----- END BACKTRACE -----
 
effectivement, avec ce firmware j'ai des erreurs de segmentation sur mongodb... va falloir que je comprenne pourquoi
Merci pour le retour. Je vais attendre la mise à jour. J’avais également l’autre version 4.4.8.0 dont tu es à l’origine, mais elle ne fonctionne plus non plus après la maj ?
 
je viens de les supprimer du Repo... il me faut du temps pour un fix... MongoDB fout la m... avec le dernier firmware
je regarderais pour faire un mongoDB séparé non dépendant de Apache8x
 
je viens de les supprimer du Repo... il me faut du temps pour un fix... MongoDB fout la m... avec le dernier firmware
je regarderais pour faire un mongoDB séparé non dépendant de Apache8x
Merci pour la réponse. Tenez-moi au courant dès que c'est dispo, je serai preneur ;)