I'm using Cisco Access Registrar to issue IP addresses to clients on a wireless network.
Everything was working fine (sessions created and destroyed as expected) but when I joined the AP to WDS all hell broke loose.
It seems that when the AP is not a WDS member the "NAS-Port" attribute is the same for Access-Requests and Accounting-Requests but when it's a member I get a different "NAS-Port".
This is a problem because the CAR creates a session when the Access-Request is accepted but destroys it whent it receives an Accounting-Request with an Acct-Status-Type = Stop. The session key is NAS:NAS-Port and if the port doesn't match the session isn't destroyed.
Has anyone had a similar problem or know a possible solution?
I added a second AP to the WDS domain and it confirmed my fear... The Access-Requests are coming from the WDS master but the Acccounting-Requests are coming from the AP that the client commects to, which explains the different NAS-ports.
We are moving! Please use WLCCA Forum for updates and discussions
[toc:faq] Wireless LAN Controller (WLC) Config Analyzer Download Click
here to Download To request access, send an e-mail to
firstname.lastname@example.org. Please include your Cisco.com userna...
[toc:faq] IntroductionHere is the step by step process that we have to
take care of while converting LWAPP to IOS and then vice versa..LWAPP to
IOSThe hardware used = 1141 AP (make sure we are using the right
[toc:faq] Introduction AnyConnect Secure Mobility Client 3.0: Network
Access Manager & Profile Editor on Windows Summary Use the Cisco
AnyConnect Network Access Manager Profile Editor to build custom
profiles for the AnyConnect Secure Mobility Client. App...