This question is regarding DHCP required and mobile supplicants in an LWAPP architecture environment. Assume DHCP required is set to true. Assume the supplicant is powered on and receives its IP address. The client then roams to a new BSS (BSS2) in the same subnet and does a DHCP request and receives notification it can continue using the one it has leased (assume it has not expired).
Question: If the client has a BSS table and roams back to the first BSS (BSS1). The client determines that it currently has an IP from BSS2 that is in the same subnet as the previous IP it was provided from BSS1 and so chooses to use the existing IP... and not do a DHCP request.
How do the controllers and APs handle this client that they have seen on this AP before and provided it an address before?
But when the session starts or ends, the client must re-DHCP as the WLC is serving as the proxy. Packets will not be forwarded to/from the client until then. This is not recommended for voice deployments, but you can enable this for your data SSIDs. If enabled for voice, then the potential for no way voice could occur if the session is ended via deauth or timeout.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...