How to Configure DHCP for Busy Hotspots with Execute Command
Busy Wi-Fi hotspots need a sufficient number of DHCP leases for guests who connect to the network. However the growth of Wi-Fi enabled smartphones, tablets and other mobile devices has dramatically increased the number of "ambient" Wi-Fi connections that also request DHCP leases - even though they might never actually authenticate onto the network. In SputnikNet, these ambient requests show up as unauthenticated sessions.
It is important to ensure that routers in busy hotspots are set up with large, frequently refreshed DHCP lease pools to keep up with this demand.
Here's how to configure your Sputnik-powered router for high-demand sites, from the cloud.
Check DHCP settings via menu.
Or check DHCP settings via command line.
View DHCP settings.
Set the DHCP lease pool to 100 (or more).
Set the DHCP expiration to a few hours.
Confirm your DHCP settings.
The DHCP lease pool is now 100 leases with a 6-hour expiration. You can try different values to see what gives you the best performance at your site, but we've found 100/360 to work in most locations unless the hotspot is is an extremely high traffic area, in which case you could set the pool even larger.