Feature requests for Omada Controller
Dear @forrest,
I have some feature request for Omada Controller collected over time from our Omada customers and from Omada users here in the forum. I would appreciate very much if you could consider those features in a future version of Omada controller.
1. Statistics page
It would be helpful if the statistics page would allow to select a pie chart for showing numbers of users/guests per EAP, not only per SSID. Often, sites have only one SSID at all and the current pie chart always shows 100% users for this SSID. I know, it's already in Omada App, but sysadmins would like to see this in Omada software controller and OC200, too.
2. Client hostnames
If WiFi hostnames are empty (device shows up as »Unknown«), Omada Controller should query the DNS server for the hostname. DNS servers in small SOHO networks keep track of the hostname sent by DHCP automatically. Business users often use a full-fledged DNS server. Additionally, the client's hostname should be allowed to be set manually – you have accepted the latter suggestion of a manual settings for home users already as far as I know. But DNS names should be queried for power (business) users, too, and it would be beneficial even for SOHO users.
3. Proxying capabilities
It would be helpful to allow use of web proxys such as the nginx or apache web server, which can forward requests to Omada controller. This would just require the ability to bind Omada controller to specific IP addresses set in the properties, thus preventing the controller to listen to all IP addresses of the server. Business class servers often have web front-ends and load-balancing while the software runs on a back-end server. Those load balancing functions of a proxy could be used easily for Omada controller with only small changes in the Java code which allow binding to certain IP adresses.
4. mongod database
Sysadmins should be able to use a system-provided mongodb instance alternatively to the built-in one. Currently Omada controller always starts an own mongod instance. If it would be possible to prevent this start, Omada controller could use an existing (already installed) mongod by just changing the port in the properties. So please make start of the built-in mongod optional for those users who run an own mongod already. No need to run DB servers twice on the same system.
5. Make Java code platform-independent again
In version 2.x Omada controller's Java code was platform-independent. Java classes for Windows could be used on Linux and FreeBSD UNIX without any change. Starting with version 3 Omada controller introduced platform dependency, which isn't really needed (Java has been designed to be platform-independent). Only change required in V3 Omada controller would be to not query for the platform the controller is running on, but instead querying for the existance of platform-dependend helper commands such as ps (then it's running on Linux or FreeBSD) or tasklist (then it is running on Windows).
By querying for the existance of helper commands instead of querying the platform you would have to support only one version of Omada controller's Java code for every platform. No more differences in Java code for Windows, Linux and FreeBSD – just one Java code base like it was in versions 2.4 to 2.7. You only would need to package different software packages versions for distribution of built-in binaries such as mongod, but the Omada community version, which avoids any built-in binary, could run on any platform, whether it's 32 bit, 64 bit or x86, mips or arm architecture.
If R&D doesn't want to unite the Java code base, then please remove at least the platform checks in Java method »com.tp_link.eap.start.EapLinuxMain« and consider removal of the platform checks in the Linux version of Omada controller. For example, if you remove those platform checks, the Linux version could be made easily to run also on FreeBSD, which is often used as an Internet server. And I'm sure, no-one would download the Linux version anyway if he runs Windows.
6. SSL certificates
While it is possible to change SSL certificates in the Linux version easily, it isn't possible at all on OC200. Please consider an upload mechanism for OC200 either through the web UI or maybe through the optional USB stick, which can be added to OC200. There is a lot of space on USB sticks used for auto-backups. Why not use it for other things, too?
7. Client isolation
Please consider to add a setting for »Client Isolation« again. It would be not necessary to change the current existing setting »Guest Network«, which still could co-exist and which could enable client isolation, too. But it would be beneficial to only enable client isolation without the invisible ACLs being set when using »Guest Network« setting. This would also simplify access from guest users to the OC200 portal when OC200 is the only device in the (wired) LAN.
These are the feature requests I'm often asked for by our customers and by users here in the forum. It would definitely improve Omada Controller.
Thanks very much for your consideration.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks, ASCII . There are many wrappers, but advantage of start-stop-daemon is that it is included in the dpkg package already, thus it is available on every Linux which can install stand-alone deb packages. Since it just starts the daemon and then quits, this advantage weights more than any other IMO.
A stand-alone deb package should not have too many dependencies since in contrast to apt it does not resolve dependencies automatically.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Please add my vote also for #1, #2, and #7. Thanks!
- Copy Link
- Report Inappropriate Content
R1D2 wrote
7. Client isolation
Please consider to add a setting for »Client Isolation« again. It would be not necessary to change the current existing setting »Guest Network«, which still could co-exist and which could enable client isolation, too. But it would be beneficial to only enable client isolation without the invisible ACLs being set when using »Guest Network« setting. This would also simplify access from guest users to the OC200 portal when OC200 is the only device in the (wired) LAN.
I too would like more granular controls for client isolation. The guest network setting is too restrictive because it blocks all internal network communications. I would like to have a way to only block traffic on the same subnet so clients can't talk to each other, but they can still access other internal systems that I allow from my firewall.
Is that what you mean by client isolation vs. Gues Network, or is it something else?
- Copy Link
- Report Inappropriate Content
rockin, yes that's it exactly.
A »Client Isolation« setting was there already until »Guest Network« setting had been introduced.
It's no issue for me when features are being introduced for unexperienced users (simple-to-configure guest networks have been requested many times in the past).
But it's becoming an issue for me when basic features for experienced users needing fine-grained control over their setups just disappear.
- Copy Link
- Report Inappropriate Content
Add my votes for @R1D2 's suggestions and controller redundancy
- Copy Link
- Report Inappropriate Content
Hello!
I would like to propose the implementation of an SNMP function (protocol).
This will help to collect statistics, track emergency situations. And will help in further network optimization.
Thank!
- Copy Link
- Report Inappropriate Content
I'm sure i voted on some of these on another topic before.
Being able to query DNS or manually specify names for unknown devices should be a default feature.
While this gets some love, please can you add hostnames to; Access points, <pick one> go to user or guests tab. Here it shows MAC and SSID, but it would be much better if it too shown a hostname (or manually entered name). I'm not sure i understand why MAC address and SSID are the only options here when it shows on other parts of Omada just fine.
Often on the users tab i can see a number, let's say 4 users (including any guests), but if i switch to the statistics page, i can see 5 clients - why is this, is this related to a handover taking place? If not, why do the two pages conflict each other. If i look at each AP under the users tab, they toal the 4 shown under users.
When doing batch FW upgrades it seems to do them all at once for each WLAN group and model, is there a way to stagger this without relying on manual upgrades so all APs don't reboot at once or specify how many APs in a given WLAN group can reboot at once - keeping clients connected at all times. I have only updated FW twice and only have 3 APs in use at home - so this may already be the case.
The ability to run reports on AP, User/Device for a given timeframe would be nice - a usage report if you like.
Portal enhancements;
I would love to see an option for the portal, where an admin can pre-register a user based on their email address, specifying a date range the user can have access, and if applicaable times during the day, for example, M-F 8am-6pm.
The user would recieve an email confirming the dates their access would be availble, which SSID they would connect to and and include a voucher code specifically for that time - on arriving on-site the user would login to the portal with their email address and voucher code - verifying their access.
As they are nearing the end of their day or remaining time on the voucher itself, they are prompted with a notice informing them access will soon expire.
Pre-registering users by email is somegthing we can do at work using Ruckus APs, and it's a feature i love, no running around generating codes, and while the ability to set users up does exist, having this as an email address means once set, the client will get a notification of their details for when they arrive in case the person they are visiting is not about to confirm the Wi-Fi code/voucher for them.
- Copy Link
- Report Inappropriate Content
Rod-IT wrote
While this gets some love, please can you add hostnames to; Access points, <pick one> go to user or guests tab. Here it shows MAC and SSID, but it would be much better if it too shown a hostname (or manually entered name). I'm not sure i understand why MAC address and SSID are the only options here when it shows on other parts of Omada just fine.
Hostname assignment has been added in the new Omada SDN controller, which – according to TP-Link – should be released very soon.
Often on the users tab i can see a number, let's say 4 users (including any guests), but if i switch to the statistics page, i can see 5 clients - why is this, is this related to a handover taking place? If not, why do the two pages conflict each other. If i look at each AP under the users tab, they toal the 4 shown under users.
You mean »Clients« vs. »Insight« pages? The »Clients« page lists currently active clients only while the »Insight« page lists all clients over the period over which statistics are being collected (can be defined in Data Retention settings). You can even display a »Connection History« of a single (user) device by clicking on the device name/MAC.
When doing batch FW upgrades it seems to do them all at once for each WLAN group and model, is there a way to stagger this without relying on manual upgrades so all APs don't reboot at once or specify how many APs in a given WLAN group can reboot at once - keeping clients connected at all times.
You can update each EAP alone w/o relying on manual upgrades if you mean »uploading a firmware file« with »manual upgrades«. Just have the controller check for updates in »Site Settings«, then go back to »Access Points« and click the update icon on the right to have just this EAP updated w/o needing to upload the firmware file.
But I consider this a work-around and I would also prefer a serial batch upgrade instead of a batch upgrade running the upgrades on all EAPs in parallel. That's what the term »batch« really means: having the system execute an action one after another instead of in parallel.
- Copy Link
- Report Inappropriate Content
R1D2 wrote
Often on the users tab i can see a number, let's say 4 users (including any guests), but if i switch to the statistics page, i can see 5 clients - why is this, is this related to a handover taking place? If not, why do the two pages conflict each other. If i look at each AP under the users tab, they toal the 4 shown under users.
You mean »Clients« vs. »Insight« pages? The »Clients« page lists currently active clients only while the »Insight« page lists all clients over the period statistics being collected (time-span can be defined in Data Retention settings). You can even display a »Connection History« of a single (user) device by clicking on the device name/MAC.
No, not quite.
Users (top right side of the page) vs clients on the statistics page
For example, right now i have 3 APs connected, top right says Stations: Users 4 Guests 0
On the statistics page, first tab on the left side, under current usage, top APs, it shows me 5 clients connected over the 3 APs
Now if i go to the Acces Points tab, pick one of the APs and look under Users and Guests tabs, adding them up over the 3 APs, they total the 4 shown in the top right side as expected.
So why is my statistics page showing 5 clients and not 4. This number varies during the day when there are more clients.
FYI i am currently on the version prior to the latest release, but this has been the case for the last 2 updates that i remember - not a huge deal, just dont get it.
I am not using any MESH networks either.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 8
Views: 13441
Replies: 39