Configurable names for clients show in EAP controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi there
At the moment, it is really difficult to identify WIFI clients shown in the EAP controller / Omada software.
Can we have the ability to give names to clients, like we can for access points, please?
For example, we have a list of clients called "android-xxxxxxxxxxxx" but it would be good to show "Reception TV", "Meeting room TV", and so on.
It should be a single field to edit on the client details pop-up window, stored in the DB.
Without such names, it is not very useful. Adding these names, would be much better!
Thank you,
D
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
It's annoying because it should have been an included feature right in the very first release of Omada Controller ever. Moreover this is a feature that is already present for a while (even forever) in all competitor's systems such as Meraki, Ubiquiti and others. 
I use my Omada system where I have a lot of WiFi IoT devices (automation) where those devices only return "unknown" which make management and reports very annoying to use.
- Copy Link
- Report Inappropriate Content
Not in today's version either. 
Model: OC200 1.0
Firmware Version: 1.2.2 Build 20200424 Rel.58128
Controller Version: 3.2.11
- Copy Link
- Report Inappropriate Content
@JFND, as Jonas wrote this feature will come in Omada SDN Controller, it will not come in Omada EAP Controller (different software).
As I saw accidently, Omada SDN Controller is currently being prepared to be relaesed soon (websites, support sites, etc.).
- Copy Link
- Report Inappropriate Content
Just to be sure, the Omada SDN Controller means the Windows's version and not the small metal box controller sold separately?
R1D2 wrote
@JFND, as Jonas wrote this feature will come in Omada SDN Controller, it will not come in Omada EAP Controller (different software).
As I saw accidently, Omada SDN Controller is currently prepared to be relaesed soon (websites, support sites, etc.).
- Copy Link
- Report Inappropriate Content
SimonC. wrote
Just to be sure, the Omada SDN Controller means the Windows's version and not the small metal box controller sold separately?
No, it will be released as a Windows, a Linux and an OC200 version AFAIK (just like it is with Omada EAP Controller).
- Copy Link
- Report Inappropriate Content
+1 for adding this feature to the regular Omada controller. Cheap basic routers have it, can't imagine how an enterprise grade solution hasn't.
- Copy Link
- Report Inappropriate Content
jbtibor wrote
Cheap basic routers have it, can't imagine how an enterprise grade solution hasn't.
That's correct.
Cheap SOHO routers have it. In a typical enterprise deployment naming cliens is of not much use. For example, we have ~1 million users each month with many different devices. Nobody here would even think of naming them. But I understand that users with a bunch of IoT devices at home need this function, agreed.
The reason why it wasn't there is this: when Omada controller was designed as an enterprise product, there was just no need to name devices in enterprise installations with a large WiFi audience.
- Copy Link
- Report Inappropriate Content
I was able to update hostnames that show "Unknown" by updating the Mongo DB directly.
On Linux (sorry I don't know how to do this on Windows):
-
apt install mongo-tools
-
service tpeap stop
-
mongoexport --port 27217 --pretty --db tpeap --collection client --out client.json
- Edit the client.json file using your favorite text editor.
-
mongoimport --port 27217 --db tpeap --collection client --file client.json --drop
-
service tpeap start
Of course, make a backup first. If you hose your installation, it isn't my fault!
- Copy Link
- Report Inappropriate Content
@kross Thanks for this, it worked perfectly for me. However, I found that you have to have the service running, otherwise the MongoDB isn't running in order to perform the import/export. I also saw no issues doing the import while the controller service is running, but I'm running this at home so the consequences of messing something up are pretty small. I'm sure if I dug into the service configuration lin Linux I could leave the DB up but the rest of the controller down, but I didn't take the time. I wish this worked on more than the "unknown" clients but in my experience their names revert right back to the original names as soon as they controller sees them after the import, pretty much immediately.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 10740
Replies: 44
Voters 6
