On Monday 06 February 2006 16:25, Dennis Skinner wrote:
Guy Fraser wrote:
there. I looked into it briefly for Cisco 5248 and determined
that by setting the interface administratively down would boot
the user, then setting it back to up would allow it to accept
access again. The tricky
Hi,
Thanks for the answers. Well after testing a while and checking the dusty
radkill script, I´d like to comment, for the mailing list archive, about
what I tested/found:
- For the record: Freeradius can´t kick a logged user. There's no
configuration option on radiusd.conf or something to kick
Hi,
I´ve been searching a while about how to kick a logged user or force
terminate it´s session. It seems that this has been asked before on the
list, but I didn´t find an answer different from radius can´t do that. The
only answer that I´ve found is that it´s required an external script
On Mon, Feb 06, 2006 at 11:47:38AM -0500, Eduardo Bejar wrote:
Hi,
I?ve been searching a while about how to kick a logged user or force
terminate it?s session. It seems that this has been asked before on the
list, but I didn?t find an answer different from radius can?t do that. The
only
On Mon, 2006-06-02 at 11:47 -0500, Eduardo Bejar wrote:
Hi,
I´ve been searching a while about how to kick a logged user or force
terminate it´s session. It seems that this has been asked before on the
list, but I didn´t find an answer different from radius can´t do that. The
only answer
Guy Fraser wrote:
there. I looked into it briefly for Cisco 5248 and determined
that by setting the interface administratively down would boot
the user, then setting it back to up would allow it to accept
access again. The tricky part was matching the user to the
interface so you would
6 matches
Mail list logo
