Guest wireless network running out of IP addresses.

[David Byers]

Currently our guest network is running out of IP addresses. It looks like every device that comes into radio range is being assigned an IP address no matter if someone is using that device or not. Example would be someone with a smart phone entering the building and has the phone setting on Wireless would automatically connect and burn an IP address and they not be actively using the device. I noticed in WCS that there are different types of options to redirect to a splash screen and so forth but when I enabled this option it seemed not to help. Is there a preferred way to limit DHCP addresses only be handed out to users that request it? If so can someone please point me to the appropriate documentation to assist.

Thanks,

Sent from Cisco Technical Support iPad App

[Scott Fella]

Currently there is no way to limit the dhcp. Since WebAuth is a layer 3 authentication, the device needs to have an IP address in order I continue. What I have done and others, is to increase the subnet size and reduce the lease.

Sent from Cisco Technical Support iPhone App

[David Byers]

Scott,

Thanks so much for the assistance. Currently the way we are set up the VLAN we are using is full and we can't expand it. We are in the process of creating a new DHCP scope and VLAN for guest access. We thought this was the best way to fix the current issue but I needed confirmation we were heading in the right direction. Thanks again for the help,

David

Sent from Cisco Technical Support iPad App

[Scott Fella]

Well depending on the code you are running on the anchor, you can maybe use interface groups also known as vlan select and add an additional subnet to the existing subnet you have for guest.

Sent from Cisco Technical Support iPhone App

[Saravanan Lakshmanan]

No solution for open network yet. You could use WEP/WPA encryption, share the key at lobby or whereever required in the building.

Client idle timeout will kick the client, however it doesn't sync with dhcp server to remove the lease. Even that implemented, it works only for client that left, accidentally existing client would do dhcp over and over.

[mscherting]

I feel your pain.  I've had to create additional bigger subnets for the same issue.

Good thing you're addressing it now!  Come December 26, you'll likely get hammered by new gadgets coming into your air space.