When radiator does it's simultaneous use double check, it checks the
username on the router against the one in question... however as we feed
the users through a regex, these will be different (e.g. users logging in
with a capitalised username, etc).

e.g. user logs in as [EMAIL PROTECTED] (which will be what the Cisco shows
up on a who). However radiator will think of them as simply "twit" - hence
they can log in as many times as they like provided they dont log in with
simply "twit"

I'm not sure if this can be classified as a bug, but if it were treated
the same as the username being authenticated it would stop this happening.

Anyone have similar problems?


To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.

Reply via email to