Omada controller does not update existing client hostnames when DNS names change

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

Omada controller does not update existing client hostnames when DNS names change

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada controller does not update existing client hostnames when DNS names change
Omada controller does not update existing client hostnames when DNS names change
2020-06-08 19:40:16

I had some clients who did not register their hostname properly when obtaining their DHCP lease. In the Omada controller, these clients show up as "Unknown".
I figured out what they were and then configured hostnames on my router, so now the router displays the proper hostname for the DHCP client and puts it into local DNS.

 

On the raspberry pi running the Omada controller software, I can "dig -x 192.168.0.188" and it returns Pixel4XL like it should. Or I can use "arp" and also get the correct new hostname for that MAC. Everything else on the network also knows that MAC 88-54-1F-xx-xx-xx which has IP 192.168.0.188 is "Pixel4XL"

 

But the Omada Controller software still caches the first hostname it saw for that MAC, which is "" or Unknown.

If I look at /opt/tplink/EAPController/logs/mongod.log for this MAC address the name is still shown as name: ""

 

I rebooted the RaspberryPi running the Omada Controller software, no change. DHCP leases have been renewed multiple times since the hostnames were fixed.

 

How can I get the Omada software to relearn/update hostnames for existing clients based upon current DNS entries? Restarting (via reboot) didn't work. Deleting and reinstalling the Omada controller software to get an empty database is a bit extreme.

  0      
  0      
#1
Options
18 Reply
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-08 20:29:48

Hi @nojak,

 

I have a similar issue.  My guess is that Omada uses only the MAC address as the unique client ID rather than the tuple of MAC and Host Name.  As such, new records for the same MAC address are just added as new data rows, whereas the identification / creation of a new user identify (together with their hostname) is tied to finding a new MAC address, only.

 

One would need some sort of function to delete a prior client (and their data) from the log -- or a mechanism in Omada to rename them.  Or you'd need to go into the DB itself and either drop this client (delete the records associated with it) or hand edit the "user table."

 

While I'm not an expert at database design, it would seem to me to be better to use the combination of MAC address and Hostname as the Primary key rather than lumping everything under the same MAC address.  That way, if you reformat, rename a piece of hardware overtime, it's data would be partitioned into separate chunks (by hostname/MAC).

 

I really wish there were more / better user, AP, SSID, and site level reporting features.  Simple questions like:

 

1) How much data is this user using?  Right now, in the past hour, day, week, etc?

2) How much data is flowing through this AP, SSID, site in the past hour, day, week, etc?

3) How much is DL?  How much is UL?

4) What was my peak sustained (AVG over user specied time -- 1min, 15min 60min) data consumption/utilization? -- am I maxing out my uplink?  broad band connection, etc.?

 

Maybe one day (-:

 

-Jonathan

  0  
  0  
#2
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-09 10:41:53

 

nojak wrote

How can I get the Omada software to relearn/update hostnames for existing clients based upon current DNS entries?

 

You can't. Omada controller doesn't use DNS for client names, it rather uses the WiFi hostname reported by the client during negotiation which will show up as »Unknown« if empty.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#3
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-09 14:41:46

@R1D2 Thank you. That makes sense. Bit annoying for devices that don't let you set their hostname (looking at you Google and Amazon products).

  0  
  0  
#4
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-10 02:18:32

Agreed,

 

It would be nice if Omada let you rename clients, or put them in groups, or flag/comment them (e.g. if they are troublemakers) -- (-:

 

-Jonathan

  0  
  0  
#5
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-10 03:16:14

I recall reading somewhere (this forum?) that the upcoming tp-link SDN controller will have this functionality.

:fingerscrossed: smiley

  0  
  0  
#6
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-10 06:15:31

@nojak, yes, SDN controller will let you rename clients.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#7
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-10 12:32:01

So what is the plan for the new SDN?  Will the OC-200 be upgradeable?  With there be a new management device?  Is there an anticipated release date?  I've not seen anything about it in the US media.  Nor is there much on the anticipated 620 and 660HD.

  0  
  0  
#8
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-10 14:23:18 - last edited 2020-06-10 14:24:42

@JSchnee21,

 

yes, OC200 will be upgradeable and there will be versions for Linux and this Winthing as usual.

 

Re: SDN controller:

 

TP-Link International did publish a video some time ago: https://www.youtube.com/watch?v=KW4WPSj2hpA

 

TP-Link UAE did publish a press release: https://www.tp-link.com/ae/press/news/18621/

 

Personally, I don't believe in any release dates, I just wait until the software appears on the support/download page. As for 660HD I will wait until HW V3 at least. ;-)

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#9
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-10 17:19:31

Yeah, it will be interesting to see re: SDN

 

"Omada SDN provides two kinds of SDN controllers: a Cloud-Based Controller (completely in the cloud) and a Hybrid-Cloud Controller (on-premises) with full cloud access. This gives customers maximum choices and full control of the whole network from the cloud to fit their business needs."

 

Whether this will be a subscription service (Cloud only).  I had always assumed that the security gateway would be needed for the hybrid solution to do packet inspection.

 

But if there is a lighter version that works with the OC-200, all the better.

 

-Jonathan

  0  
  0  
#10
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-12 16:40:45

OK got an update notification today on my OC200 it had an update available so  installed it hoping it was the long awaited client naming release but it doesn't appear to be.  If it is the Release Notes don't indicate it. 

 

Couldn't find the relases on the US site but looked around and found the release notes Canada site.) 

 

OC200(UN)_v1_1.2.3 Build 20200430

 

Just Says: Enhance the product stability. 

 

Bundle Omada Controller 3.2.12.
Bundled Firmware:
EAP110_V1, EAP110_V2, EAP110_V4
EAP115_V1, EAP115_V2, EAP115_V4
EAP225_V1, EAP225_V2, EAP225_V3
EAP225-Outdoor_V1
EAP110-Outdoor_V1, EAP110-Outdoor_V3
EAP245_V1 EAP245_V3
EAP115-Wall_V1 (EAP115-Wall is suitable for EU version only)
EAP225-Wall_V2
EAP235-Wall_V1
EAP320_V1 EAP320_V2
EAP330_V1 EAP330_V2

 

New Feature/Enhancement:  Enhance the product stability.

 

Notes:
1. For OC200 (UN) v1.0 only.
2. To use new features of OC200, you need to upgrade your EAP's firmware to the corresponding version.
3. Your device's configuration won't be lost after upgrading.

 

  0  
  0  
#11
Options

Information

Helpful: 0

Views: 5754

Replies: 18