Date: Tue, 8 Jul 1997 01:13:12 GMT From: Adam David <adam@veda.is> To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/4051: pppd connect 'chat ...' broken Message-ID: <199707080113.BAA03939@ubiq.veda.is> Resent-Message-ID: <199707080120.SAA19954@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 4051
>Category: kern
>Synopsis: pppd connect 'chat ...' broken
>Confidential: no
>Severity: non-critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jul 7 18:20:01 PDT 1997
>Last-Modified:
>Originator: Adam David
>Organization:
Veda Internet
>Release: FreeBSD 3.0-CURRENT i386
>Environment:
-current or 2.2
>Description:
pppd(8) doesn't pass a valid terminal to chat(1) so the connect script
fails with ENODEV ('man ioctl' does not mention this as a possible
error either). The sequence is this:
pppd: open the tty device
pppd: TCGETA the open tty to store previous state before continuing
pppd: set the tty state according to options
pppd: fork and continue in the child
pppd: dup2 to associate the opened tty with stdin/stdout
pppd: exec a shell to run the script
(/bin/sh is assumed to work correctly)
chat: TCGETA stdin to store previous state before continuing,
oops ENODEV (huh????)
Theoretically this should work, but it fails.
>How-To-Repeat:
try to get pppd to chat to the modem using chat(1) in a connect script.
This is documented to be the correct approach, but it doesn't work.
>Fix:
It looks like people have been using chat or cu,tip,kermit or whatever
(getty?) to talk to the modem and hold open the port before invoking
pppd.
It's really ugly but reputed to work.
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707080113.BAA03939>