From owner-freebsd-questions Sun Dec 7 04:56:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08011 for questions-outgoing; Sun, 7 Dec 1997 04:56:39 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from cam.grad.kiev.ua (grad-UTC-28k8.ukrtel.net [195.5.25.54]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08006 for ; Sun, 7 Dec 1997 04:56:26 -0800 (PST) (envelope-from Ruslan@Shevchenko.kiev.ua) Received: from Shevchenko.kiev.ua (localhost [127.0.0.1]) by cam.grad.kiev.ua (8.8.8/8.8.5) with ESMTP id OAA06915; Sat, 6 Dec 1997 14:54:01 GMT Message-ID: <34896708.46F9D6D2@Shevchenko.kiev.ua> Date: Sat, 06 Dec 1997 14:54:00 +0000 From: Ruslan Shevchenko X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE i386) MIME-Version: 1.0 To: Livio Mazzon CC: questions@freebsd.org Subject: Re: User PPP wont release the device References: <1.5.4.32.19971207120534.00933c20@mse.com.au> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Livio Mazzon wrote: > I have just upgraded an existing system from FreeBSD 2.1.6 to 2.2.5. It is > an ISP server that uses user-ppp to accept dial-ins from attached modems. > > Before the upgrade the ppp dial-ins worked fine! > > After the upgrade (finally got the machine going)....I now have a problem > where users can dial in, login and connect, and they properly get a ppp > session running. > > All routing etc is fine > > I use a script on connection to run exec /usr/sbin/ppp -direct. > > However, when the user hangs up, the modem disconnects, DCD drops, but the > PPP process stays attached to the port. The user stays logged onto the > system even though the physical connection has dropped. When the next > person logs in, the modem answers, but they never see the login prompt > (thats because the getty programme never gets the device, ppp is still > holding on to it!). This happens EVERY logon that uses PPP. > > I've checked all the config files, they are the same as before... when they > were working. > > And no, I dont think its a cable problem, or modem config problem because if > the user logs in via a shell, the device is released properly to getty. > > This is now becoming critical for us. Any help would be greatly, greatly > appreciated. > We have the same problem. Our solution is script, which ping other side with period one minute, and if ping -c 2 ADDR return 1 --- kill process. > Thanks > > Livio