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.
18 Reply
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-12 19:54:28

Thanks JFND. Also saw that OC200 firmware, released today. :)

 

Those of using running the Omada Software Controller on other servers (like Raspberry PI :) ) need to wait a bit longer. Though given this just seems to be bug fixes, I guess it doesn't really matter that much anyway. 

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

Yeah, I'm hoping for an EAP firmware update soon.

  0  
  0  
#13
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-12 20:23:36 - last edited 2020-06-12 20:24:03

You likely mean so they support DFS for North American units. :D

  0  
  0  
#14
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-12 20:39:08 - last edited 2020-06-12 20:39:34

(-:

 

Yeah, I wish.  Is there any hope of that coming?  I figured development of the 225 series is probably done given the new 620 and 660 on the horizon.  But I haven't scowered the FCC submissions to look for an updated certification / testing report.

 

I'd by a third indoor EAP in a heartbeat if that were the case.

 

-Jonathan

  0  
  0  
#15
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-12 22:21:35 - last edited 2020-06-12 22:23:46

@JSchnee21,

 

IMO, EAP225 is still the top EAP since years now. EAP245 might be even better, but I never tested one nor installed one for customers, so I'm just an observer when it comes to an EAP245. Now, from observation I saw this:

 

EAP120, EAP220, EAP320 and EAP330 became EoL very soon, the former two b/c of technological change (N to AC).

EAP225 replaced EAP220. EAP245 replaced EAP330, but with 150 Mbps fewer WiFi rate.

 

As for the new EAP620 we will see whether it fits into a business scenario.

Personally, I think that EAP225 and EAP245 product line will still stay alive despite availability of an EAP620.

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

 

JSchnee21 wrote

"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."

 

You can easily run the software controller in your own cloud (e.g. an AWS instance, Digital Ocean, own hosting server etc.). The SW controller deos not need to run in the local subnet. EAPs are adopted over L3 links.

 

I think the TP-Link cloud solution is for people w/o own infrastructure and I could imagine that this becomes a subscription service. We will see.

 

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.

 

For deep packet inspection (DPI) you need to analyze the traffic. An OC200 does not see any traffic with foreign sites, just management traffic. So, yes, DPI requires to be done on the router, resp. the OSG. But I don't know whether the OSG supports DPI, still saw no specs.

 

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

@R1D2 I agree that EAP225 and EAP245 will likely continue even with 620/660HD. 
The latter looks to me to be optimized for high density, leaving room to keep the 802.11ac units as a lower priced option. 
Though the present 30% off continuous sale on EAP225 and EAP245 in Canada points to them being discontinued. 

  0  
  0  
#18
Options
Re:Omada controller does not update existing client hostnames when DNS names change
2020-06-13 15:32:07

Sorry, I didn't mean to suggest that the 225 & 245 series would be discontinued (even though the 245 series has always seemed a bit neglected)

 

Rather, I meant that given the many years and hardware versions of the 225 & 245 to date -- none of which support DFS in the USA -- I sincerely doubt this capability is coming to these EAP's

 

-Jonathan

  0  
  0  
#19
Options