Very Computer

Main problem, using pppd as described in NAG and the Network HOWTO,
the command immediatly returns to the command line with no apparent
serial io.

Breaking down the command to just chat, yields data output to the
screen.  Does PPPD redirect stdin/stdout to the chat command or is
there a method for specifying serial device to chat ?  The man pages
don't indicate either.

Note:
        echo atdt > /dev/cua3
works.

My pppd command line :
pppd connect 'chat -v "" ATDT*70,5555555 CONNECT "" ogin: mylogin
word: mypass /dev/cua3 38400 debug crtscts modem

I've tried w/ and w/o default route (this shouldn't matter at this
stage).

Jim

Quote:>Main problem, using pppd as described in NAG and the Network HOWTO,
>the command immediatly returns to the command line with no apparent
>serial io.
>Breaking down the command to just chat, yields data output to the
>screen.  Does PPPD redirect stdin/stdout to the chat command or is
>there a method for specifying serial device to chat ?  The man pages
>don't indicate either.
>Note:
>    echo atdt > /dev/cua3
>works.
>My pppd command line :
>pppd connect 'chat -v "" ATDT*70,5555555 CONNECT "" ogin: mylogin
>word: mypass /dev/cua3 38400 debug crtscts modem

Hint: pppd uses the command: /bin/sh -c chat -v "" ATDT*70,5555555 CONNECT ...
to do the connection sequence. In my book, the "*" character means something
to the shell. Did you try removing it?

If you wish to keep the "*70," sequence then change the dial command to
be

"ATDT*70,5555555"

(don't forget to _include_ the quote characters.)

It also is probably a typo, but you forgot the closing ' character.

Quote:>I've tried w/ and w/o default route (this shouldn't matter at this
>stage).

--

See the sample ppp-on script that comes with the pppd package. It shows
how to redirect the i/o to a serial port.

Regards,

Paul