From nobody@FreeBSD.ORG  Mon Dec 20 08:17:07 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id DEAB91536F; Mon, 20 Dec 1999 08:17:00 -0800 (PST)
Message-Id: <19991220161700.DEAB91536F@hub.freebsd.org>
Date: Mon, 20 Dec 1999 08:17:00 -0800 (PST)
From: poortom@apmisc.ibm.co.jp
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: userland ppp dialup fail with AtermIT
X-Send-Pr-Version: www-1.0

>Number:         15582
>Category:       bin
>Synopsis:       userland ppp dialup fail with AtermIT
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 20 08:20:01 PST 1999
>Closed-Date:    Mon Dec 20 14:45:05 PST 1999
>Last-Modified:  Mon Dec 20 14:46:01 PST 1999
>Originator:     Tomoyuki Niijima
>Release:        3.3
>Organization:
IBM Japan
>Environment:
FreeBSD ajisaiso 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Thu Sep 16 23:40:35 GMT 1999     jkh@highwing.cdrom.com:/usr/src/sys/compile/GENERIC  i386

>Description:
I don't know this is a really a bug of ppp, but it
seems that the program send AT commands to quick after
opens serial port while my TA is not ready to receive
AT commands.

>How-To-Repeat:
Using default /etc/ppp/ppp.conf, change and add device,
phone, authname, authkey entries, then start userland
ppp to dialup.  My TA returns ERROR just after ppp
sends ATD command to dial.  With the same environment,
it works with MODEM (Microcom V.34 ES II).

>Fix:
One thing I found to workaround this problem is to
add \\d before the first AT command in dial string to
wait for a while after ppp opens serial port.

set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" \\dAT OK-AT-OK ATE1Q0 OK
 \\dATDT\\T TIMEOUT 40 CONNECT"


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: brian 
State-Changed-When: Mon Dec 20 14:45:05 PST 1999 
State-Changed-Why:  
The fix mentioned is the correct fix (a configuration change). 
>Unformatted:
