KEA DHCP: Android Stops Working on UniFi
-
Are they still pulling a lease?
What does the Android device show when you try to connect out?
-
@stephenw10 yes, they get a lease just fine and the odd thing is once you query something like DNS, Android realizes it has Internet and starts working. Does not make any sense as I would think once the device gets a lease, the DHCP server is out of the picture, but apparently not.
-
Are you using IPv6? There have been issues with Android and IPv6 previously.
-
@kx93 said in KEA DHCP: Android Stops Working on UniFi:
DHCP server is out of the picture, but apparently not.
Once a device gets a lease - the dhcp server is for sure out of the picture, not until the client wants to renew, or do another discover does the client give any care to if the dhcp server is on or off or answering requests.
How your client determines if it has internet would be up to the client - maybe it does an dns query, maybe it does a ping to something.. But that has zero to do with the dhcp server.
-
@stephenw10 said in KEA DHCP: Android Stops Working on UniFi:
Are you using IPv6? There have been issues with Android and IPv6 previously.
Those issues are with DHCPv6 and Android. It works fine with SLAAC. Is the network configured to use DHCPv6?
-
-
Indeed it pretty much has to be something that Kea is not passing to the client. Or perhaps is passing something incorrectly.
Try running a pcap for dhcp exchange from each server and compare them.
Do you have any custom options set in ISC?
-
@stephenw10 no custom DHCP options, but have gateway, domain and lease time specified. Not a bad idea on comparing packet captures. I'll give that a shot.
-
For problems like this, it helps to know what's on the wire. You can run Packet Capture on pfSense to see what's happening. You can examine the packet captures in Wireshark.
-
Maybe we should just pin this somewhere ;)
-
Ha
