From nobody  Fri Dec 20 06:18:50 1996
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id GAA21474;
          Fri, 20 Dec 1996 06:18:50 -0800 (PST)
Message-Id: <199612201418.GAA21474@freefall.freebsd.org>
Date: Fri, 20 Dec 1996 06:18:50 -0800 (PST)
From: greg@gcsl.co.uk
To: freebsd-gnats-submit@freebsd.org
Subject: PPP process on port will not close when an NT user has diconnected after a session.
X-Send-Pr-Version: www-1.0

>Number:         2256
>Category:       bin
>Synopsis:       PPP process on port will not close when an NT user has diconnected after a session.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    brian
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 20 06:20:01 PST 1996
>Closed-Date:    Mon Sep 29 17:07:44 PDT 1997
>Last-Modified:  Mon Sep 29 17:13:48 PDT 1997
>Originator:     Greg Bedrossian
>Release:        FreeBSD 4.4
>Organization:
General Computer Systems
>Environment:
FreeBSD popeye.gcsl.co.uk 2.1.5 RELEASE FreeBSD 2.1.5 RELEASE #0:
Thu Nov 21 16:05:56 1996 root@popeye.gcsl.co.uk:/usr/src/sys/compile/
POPEYE
>Description:
POPEYE is a pop server running several serial ports on PPP. When a 
customer dials in from an NT machine to get a PPP connection, after he
has finished and signs off, the particular PPP port stays open with the 
pppd-x process still running. It has to be killed manually otherwise the
next caller is confronted with a security violation and can enter the 
system without a login and password. This does not happen with Win95 or 
other type of OS dialing in.
>How-To-Repeat:
Well - as above!
>Fix:
Unknown as of yet. Several attempts to re program the modems has not so
far yielded fruit. The problem is consistant. It happens every time an
NT user dials in.

WE ARE STUMPED! ANY SUGGESTIONS???
>Release-Note:
>Audit-Trail:

From: J Wunsch <j@uriah.heep.sax.de>
To: greg@gcsl.co.uk
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: ports/2256: PPP process on port will not close when an NT user has diconnected after a session.
Date: Fri, 20 Dec 1996 19:11:32 +0100 (MET)

 As greg@gcsl.co.uk wrote:
 
 > POPEYE is a pop server running several serial ports on PPP. When a 
 > customer dials in from an NT machine to get a PPP connection, after he
 > has finished and signs off, the particular PPP port stays open with the 
 > pppd-x process still running. It has to be killed manually otherwise the
 > next caller is confronted with a security violation and can enter the 
 > system without a login and password. This does not happen with Win95 or 
 > other type of OS dialing in.
 
 Even if the PPP layers aren't correctly closed by POPEYE, your tty
 device or modem seems to be misconfigured.  The modem is support to
 drop the DCD signal when the carrier vanishes, and this should in turn
 send a SIGHUP to the process.  This will eventually terminate the
 process even though the PPP layers haven't been shut down correctly.
 
 (Apparently, your other client's PPP implementations do shut down the
 layers properly, so your PPP volunteerely drops the connection
 itself.)
 
 -- 
 cheers, J"org
 
 joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
 Never trust an operating system you don't have sources for. ;-)
Responsible-Changed-From-To: freebsd-ports->freebsd-bugs 
Responsible-Changed-By: max 
Responsible-Changed-When: Wed Dec 25 21:25:39 PST 1996 
Responsible-Changed-Why:  
This PR is about serial port, not about the ports collection. 

From: Mike Durkin <mdurkin@tsoft.net>
To: freebsd-gnats-submit@freebsd.org, j@uriah.heep.sax.de
Cc: greg@gcsl.co.uk
Subject: Re: bin/2256: PPP process on port will not close when an NT user has diconnected after a session.
Date: Mon, 10 Feb 1997 19:50:57 -0800

 I've seen the same problem, and modems are definately configured correctly.
 I'm not sure if the bug is in mgetty or the Cyclades driver (I haven't checked
 to see if it exists with sio as well).
 
 My setup: P120, FreeBSD 2.1.6R, Cyclades Ye16 multiport card, mgetty-1.1.0
 
 The root of the problem is thus:
 
 While waiting for a call, mgetty has 'clocal' on the port.
 After the call answers, and Carrier Detect is high, mgetty switches the
    port to '-clocal'.
 When the caller disconnects, pppd does not receive a SIGHUP (so it seems),
    and keeps the port tied up.
 
 It seems that the Cyclades driver won't generate a SIGHUP on an on-to-off
 CD transition if clocal was toggled off while CD was already on/high.
 
 If mgetty is modified to set -clocal while waiting for the call, it works
 fine, but I am only using it for dialin so I don't know if that breaks
 mgetty's fax functions, etc.  A workaroung in mgetty is to change
 the TRUE flag to FALSE in the call to tio_mode_sane() in
 mg_init_device() in mg_m_init.c.  Setting -clocal on the lock-state device
 in /etc/rc.serial would probably also work instead.  Note I believe the
 bug is actually in the Cyclades driver assuming the above behavior wrt
 lack of SIGHUP under the conditions given isn't kosher.
 
 thanks, Mike

From: Mike Pritchard <mpp>
To: freebsd-gnats-submit
Cc:  Subject: Re: bin/2256 PPP doesn't close w/NT client
Date: Tue, 25 Mar 1997 19:25:12 -0800 (PST)

 Feedback from the originator:
 
 Greg Bedrossian wrote:
 > 
 > Hello Mike,
 > 
 > Thank you for following up on this strange issue.
 > 
 > The problem still persists. I have had to set up an NT server to  
 > accommodate NT users who need to dial in.
 > 
 > The version of FreeBSD I am using is 2.1.5.
 > 
 > I have not tried a newer version as of yet. What is available?
 > 
 > To add to my problems,  the scripting tool within Win95 does not  
 > negotiate a correct sequence when loging into our FreeBSD server to  
 > get a ppp connection. It has to be stepped. I overcame this problem  
 > by adding 1sec delays in between the commands. However,  at  
 > "endproc" it will hang there waiting for a response from the FreeBSD  
 > host until you press continue in the dialogue box of the script's  
 > login sequence. I am being told by subscribers that they don't seem  
 > to have this problem using the same script with other ISPs.  It  
 > seems to me that pppd has a timing problem at the I/O side of it.  
 > This could explain why it does not shutdown properly with NT clients  
 > and now this other problem of loging in via a script! Though, I am  
 > not sure of any of it.
 > 
 > This is presenting a serious embarrassment for me as I am losing my  
 > subscribers. Yet I just cannot see where the problem may be, as so  
 > much of it works well, and there are no problems reported by NeXT  
 > users.
 > 
 > 
 > Regards
 > 
 > 
 > kgb

From: Brian Somers <brian@utell.co.uk>
To: greg@gcsl.co.uk, freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: ports/2256: PPP process on port will not close when an NT user 
 has diconnected after a session.
Date: Mon, 23 Jun 1997 18:08:42 +0100

 Can you confirm that pppd is being "exec'd" so that it's the
 only process attached to the tty device after the connection
 is established ?
 
 Thanks.
 -- 
 Brian <brian@awfulhak.org> <brian@freebsd.org>
       <http://www.awfulhak.org>
 Don't _EVER_ lose your sense of humour !
 
 
Responsible-Changed-From-To: freebsd-bugs->brian 
Responsible-Changed-By: brian 
Responsible-Changed-When: Mon Sep 8 14:09:24 PDT 1997 
Responsible-Changed-Why:  
ppp's mine 
State-Changed-From-To: open->closed 
State-Changed-By: brian 
State-Changed-When: Mon Sep 29 17:07:44 PDT 1997 
State-Changed-Why:  
This was recently fixed in 2.2 & -current.  The latest version 
of ppp (including these fixes) is available from 
http://www.freebsd.org/~brian. 
>Unformatted:
