Jeff Kramer says:
> 
> I've seen this asked before, but I'll ask it again:  Has anybody actually
> gotten PPP to work?

I finally got it to work.  Not elegantly, though.  For the moment
I'm doing it by hand.  Warning: this is probably more work than
most people need to do.  First I get my modem dialing.  I can't get
cu to talk to my modem in command mode (it gives me a read/write error),
so I (insanely) let a dummy pppd process do the work.

pppd tty00 19200 connect 'chat "" ATMW1 OK ATDT6848771'

and once it starts dialing, then I figure what the pppd and chat
PIDs are, and kill them (a total of three processes).

Once the modem connects (I look at the carrier detect light), *then* I
can use:

cu -l tty00

and do my login, password stuff.  When I start up PPP on the remote
end, and it starts giving me packets, I type ~z to exit from cu, kill
the cu process, and then type:

pppd tty00 19200 modem defaultroute

Then everything works/connects nicely.

All of the above should theoretically happen when I do:

pppd tty00 19200 connect 'chat "" ATMW1 OK ATDT6848771 CONNECT "" ogin:
<login> sword: <password> emo: ppp \n' modem defaultroute

But for some reason 'chat' doesn't like me, I guess.

-syam

----
Syam Gadde....................LSRC D339..................(O) (919)660-6594
Department of Computer Science, Duke University, Durham, NC 27708-0129
email==>  gadde@cs.duke.edu           http://www.cs.duke.edu/~gadde <==WWW