Jump to content

Recommended Posts

Posted
One would think that controller host name in dns would help, but it did not.

If discovery function did not work, it should now thanks to option 43. Will wait and see.

You may already know/realise this, but make sure you're using correct domain name suffix (DHCP option 15).

 

The APs aren't joined to the domain, so when they try and reach "unifi" they don't know which domain suffix/lookup zone to use.

 

I was happily pinging "unifi" from my PC, which I hadn't consciously realised was automatically resolving to unifi.my.lan

 

I was trying all sorts of ways of adding . to my DNS server, so that unifi (ie unifi.) would resolve.

 

I was eventually pointed at DHCP option 15 which tells the APs that they should use .my.lan when looking for unifi, ie unifi.my.lan, and that sorted me out.

 

Peter

Posted

Ive just updated to the latest firmware (4.0.80.10875) and one on them is emailing me the error event: {"event_string":"EVT_conntrack_full"} now.

 

No disconnects for the past 4 hours.

  • 2 months later...
Posted

Thought Id resurrect this thread.

I bought a new lovely USW-16-POE switch which played happily for a few weeks but disconnected last Friday and did the same last night.

 

I can't ping it but I when I go over all the lights are flashing and the POE is powering the access points.

 

Can't be under heavy use for obvious reasons, was looking at buying a few more of these but waste of time if they have the same issues as the APs

 

Latest firmware too, very annoying

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...