From owner-freebsd-isp Thu May 16 07:35:03 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07995 for isp-outgoing; Thu, 16 May 1996 07:35:03 -0700 (PDT) Received: from jennifer.pernet.net (root@jennifer.pernet.net [205.229.0.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA07978 for ; Thu, 16 May 1996 07:34:57 -0700 (PDT) Received: from localhost (neal@localhost) by jennifer.pernet.net (8.7.5/8.6.9) with SMTP id JAA10858; Thu, 16 May 1996 09:29:34 -0500 (CDT) Date: Thu, 16 May 1996 09:29:34 -0500 (CDT) From: Neal Rigney To: Steve Reid cc: Nate Williams , isp@FreeBSD.org Subject: Re: Logging pppd connect & disconnect In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 15 May 1996, Steve Reid wrote: > It's done with a line in /etc/ttys: > > ttyd1 "/usr/sbin/pppd -detach 115200" unknown on secure > > This makes the winsock scripts extremely simple, but it doesn't leave > much opertunity for customized logging. > Out of curiosity, does Win95 work for you without scripting? Anyway, try using ip-up and ip-down for logging. Our machines aer set up to syslog to a master log machine. The ip-up script just does a "logger" command to log the info we want. ip-up gets passed ip address, ppp interface, etc. It also makes debugging a connection better, since it doesn't execute ip-up until after the interface is ready to send/receive packets. Also, I think the newest pppd (in -stable) logs the amount of time pppd was used to syslog. That may do close enough to what you want without any hassle. -- Neal Rigney, PERnet Communications, (409)729-4638 neal@mail.pernet.net My opinions are mine, damnit! PERnet can't have them!