Fletcher Haynes
2013-09-16 15:38:49 UTC
Hi everyone,
Since the transition to 4.0.6, I am seeing an issue where deauthenticating
a client is not removing them from our Cisco WISM2. So, after someone
registers via the the captive portal, they are disconnected, but the WISM2
is not immediately removing their session. The result is that the user is
put back on the registration VLAN, because the WISM never asks PF for their
VLAN unless the client changes SSIDs or stayed disconnected for 5-10
minutes.
I have a case open with Cisco, but since this was working fine with 4.0.5,
I was wondering if there were any changes in 4.0.6 with how RADIUS deauth
works? Or has anyone encountered this issue? I plan to try SNMP
deauthentication to see if that makes a difference...
Thanks!
Since the transition to 4.0.6, I am seeing an issue where deauthenticating
a client is not removing them from our Cisco WISM2. So, after someone
registers via the the captive portal, they are disconnected, but the WISM2
is not immediately removing their session. The result is that the user is
put back on the registration VLAN, because the WISM never asks PF for their
VLAN unless the client changes SSIDs or stayed disconnected for 5-10
minutes.
I have a case open with Cisco, but since this was working fine with 4.0.5,
I was wondering if there were any changes in 4.0.6 with how RADIUS deauth
works? Or has anyone encountered this issue? I plan to try SNMP
deauthentication to see if that makes a difference...
Thanks!
--
Fletcher Haynes <***@willamette.edu>
Systems Administrator/Network Services Consultant
Willamette Integrated Technology Services
Willamette University, Salem, OR
Phone: 503.370.6016
Fletcher Haynes <***@willamette.edu>
Systems Administrator/Network Services Consultant
Willamette Integrated Technology Services
Willamette University, Salem, OR
Phone: 503.370.6016