running 05.03.107 hiper code is there any magical thing to do to make the radius idle timeout work? (up to this point, we have been relying on the old program called TSMON, but the boss doesn't want the headaches of linux any more). monitoring the radius traffic, it does send the 15 min idle, 2 hour session limits correctly. the session disconnect does work just fine, but the idle goes from not working at all, to being right at 15 min up to the session timeout. I dial in with a laptop, and leave it sitting at the desktop. If I watch the connection through maxstat, the byte count of the connection goes up. Could that be whats blowing the idle, and how do I stop it? if this is some kind of keep-alive, is that configurable? (the laptop is a blissfully stupid win95 machine) If the idle timeout is un-reliable, is there any better way to catch the idle'ers on a consistent basis? Being an isp, this is one of the most important things to us. thanks Jeffrey Bland Computer Central www.ccia.com
Jeff Bland said:
I dial in with a laptop, and leave it sitting at the desktop. If I watch the connection through maxstat, the byte count of the connection goes up. Could that be whats blowing the idle, and how do I stop it? if this is some kind of keep-alive, is that configurable? (the laptop is a blissfully stupid win95 machine)
If the idle timeout is un-reliable, is there any better way to catch the idle'ers on a consistent basis? Being an isp, this is one of the most important things to us. It appears that linux isn't the only hassle you have. You have the hassle of understanding your TC box. Idle means "no bits of traffic passing through this interface". If you have one bit go through it isn't idle by definition. If you want to test it properly you are going to have to use a machine you can restrict from sending any packets from. I would suggest linux but that would seem to be to much. Barring that, I would suggest a firewall on that machine and lock it down. Other than that, make sure you only have TCP/IP checked under your protocols for the dialup. It sounds like your machine is looking for a windows or IPX network. -- Lewis Bergman Texas Communications 4309 Maple ST. Abilene, TX 79602 325-695-6962 ext 115
What does your default user look like in your users config file? -Brent -----Original Message----- From: usr-tc-bounces+brentc=netnet.net@mailman.xmission.com [mailto:usr-tc-bounces+brentc=netnet.net@mailman.xmission.com] On Behalf Of Jeff Bland Sent: Wednesday, March 31, 2004 4:52 PM To: usr-tc@mailman.xmission.com Subject: [USR-TC] radius issue running 05.03.107 hiper code is there any magical thing to do to make the radius idle timeout work? (up to this point, we have been relying on the old program called TSMON, but the boss doesn't want the headaches of linux any more). monitoring the radius traffic, it does send the 15 min idle, 2 hour session limits correctly. the session disconnect does work just fine, but the idle goes from not working at all, to being right at 15 min up to the session timeout. I dial in with a laptop, and leave it sitting at the desktop. If I watch the connection through maxstat, the byte count of the connection goes up. Could that be whats blowing the idle, and how do I stop it? if this is some kind of keep-alive, is that configurable? (the laptop is a blissfully stupid win95 machine) If the idle timeout is un-reliable, is there any better way to catch the idle'ers on a consistent basis? Being an isp, this is one of the most important things to us. thanks Jeffrey Bland Computer Central www.ccia.com _______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc
participants (3)
-
Brent Crier -
Jeff Bland -
Lewis Bergman