How to resolve APIPA addresses for clients connected to Wi-Fi?
If clients are receiving APIPA addresses, it likely indicates that they cannot obtain an IP address from the DHCP server.
Start by checking the DHCP server logs in Nebula under Monitor > WiFi Aid & Connection log.
If the logs show that the DHCP pool is full like below:
DHCP server (Firewall/AP NAT) Cannot find any lease for this client - B2:67:4B:CC:BB:AA, DHCP pool full!
DHCP client [WiFi Aid] B2:67:4B:CC:BB:AA failed to receive an IP address due to DHCP failure/timeout (No response after discover), SSID: Studios.
It stands for the DHCP server not being able to allocate IP addresses to some clients due to a full DHCP pool. Specifically, the log entry shows that the DHCP server is unable to find a lease for the client.
When the DHCP pool is full, new devices trying to connect may not receive an IP address and end up with an APIPA address.
You could follow these steps to resolve:
1. Increase the DHCP Pool Size: Expand the DHCP pool to accommodate more devices.
2. Review Lease Times: Shorten the DHCP lease time to free up IP addresses more quickly.
These adjustments should help in resolving connectivity issues for your clients.
Categories
- All Categories
- 414 Beta Program
- 2.3K Nebula
- 134 Nebula Ideas
- 92 Nebula Status and Incidents
- 5.5K Security
- 190 USG FLEX H Series
- 262 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1K Wireless
- 40 Wireless Ideas
- 6.2K Consumer Product
- 238 Service & License
- 376 News and Release
- 80 Security Advisories
- 24 Education Center
- 5 [Campaign] Zyxel Network Detective
- 3K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 80 About Community
- 70 Security Highlight