Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!quanta.com!rsww From: rsww@quanta.com (Ross S. W. Walker) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Killing Idling SLIP sessions Date: 4 Dec 1995 17:29:57 GMT Organization: Quanta Communications, Inc. Lines: 33 Message-ID: <49vb6l$ipa@tempis.quanta.com> References: <492q06$9ln@nic.wat.hookup.net> NNTP-Posting-Host: quanta.quanta.com X-Newsreader: TIN [version 1.2 PL2] Thomas Schroecker (thomas@canadian-agra.com) wrote: : Any quick way to kill people who establish a slip session, and then not : do anything. The only way I can tell that tehir idling is that when I : type netstat -i, and number of in packets, and number of outpackets don't : change for a while. So is there a way to see the traffic throught the : slip port, and kill the session if there isn't any for a specified amount : of time?!? : Thanks in advance. : TS. It might be possible to catch some if you can set it so ICMP doesn't count as traffic and outgoing packets don't count as traffic. Otherwise you can set a maximum connect time per session. There is a daemon utility out there which can account for online time for a session, warn the user when they are near they're limit and then log them off when they reach it. I don't like the second one, but if it is what is required. The best deterent is to give an allowance of say 180/hours a month connect time, if you go over that then you will be billed $1 or $2 an hour. 180/hours a month is a decent amount of time for a dial-up account. Cheers, Ross Walker -- ------------------------------------------------------------------------------ | /\/ | Ross S. W. Walker (rsww@quanta.com) | \/\ | | | |\ | finger rsww@quanta.com for PGP key _____________________________ | |___|/ | | Quanta Communications, Inc. ------------------------------------------------------------------------------