Hi, we'r working on a scenario like this;
Client logs in to an WLAN via dot1x authentication, though we want to be able to disable re-authentication of the client on the radius when the session-timeout is reached. We also need the accounting logs to make sure that we can also kill the session if a certain traffic limit is reached. (WiSM-1 , 7.0.116 code)
The thing is that, whenever the session timeout occurs(that we set manually on the wlan), the client re-authanticates automatically and we can see access-requests and stuff though in terms of status we only see an "interim-update" accounting package in the radius thus unable to take action. The controller also uses PMK lifetime instead of the session-timeout we set which, I suppose, is derived fromt he session-timeout and some other timers as well. How do we get an accouting log when the session-timeout is reached thus the client needs to reauthenticate? (or how do we differentiate it actually, since we already see a log but its just an interim-update log)
WLC fires this when the PMK timeout is triggered.
15:23:35.224: ec:35:86:95:14:5e Initiating 802.1x due to PMK Timeout Event for STA
.....
15:23:35.562: ec:35:86:95:14:5e Setting re-auth timeout to 300 seconds, got from WLAN config.
15:23:35.562: ec:35:86:95:14:5e Station ec:35:86:95:71:5e setting dot1x reauth timeout = 300
...
15:23:35.563: ec:35:86:95:14:5e Disabling re-auth since PMK lifetime can take care of same.
after the negotiation part(which is also not enough to make differentiation); radius gets this.
15:23:35.588: P6231982: Trace of Accounting-Request packet
...
15:23:35.592: P6231982: Acct-Status-Type = Interim-Update
Is there a way to enforce a session-timeout and make sure that the client will not re-auth automatically after this timeout and get and appropriate radius log?. PS: PMK cannot be disabled before 7.2 and WiSM-1 doesn't support that.
Thanks a lot for your responses in advance
Regards,
A.
