I looked at the URL you included for your ISP's Linux info. It's really very
good and clear -- much more specific than I could be in an e-mail message,
especially not knowing what failure modes you experience.
Aside from what the ISP tells you to do, you need to make sure that:
1. /dev/modem is a symlink to the actual device (serial port) that your
modem is connected to. "setserial /dev/modem" will make sure it is a symlink
to some real serial port (look for a UART type in the return message to
ascertain this) but only you can make surethat it is the right serial port
(easiest way is to make sure that minicom can talk to the modem).
2. pppd is in your path, and you are authorized to run it. If you're trying
to connect as root, this should be okay. Check with "which pppd" to be sure.
3. the executable chat is present and runnable, probably in in /usr/sbin .
chat is the dialer that pppd calls (via the /etc/ppp/options model script
that your ISP provides) to make the call. (BTW, your ISP's recommendation to
use "chat" as the script name is confusing in my opinion -- too easy to mix
up the executable /usr/sbin/chat with the script /etc/ppp/chat .)
4. One thing I'd recommend doing differently is adding these two options to
/etc/ppp/options --
debug
kdebug 0
These will cause a lot of diagnostic messages to be written to your logs
(/var/log/messages and /var/log/debug) when you try to connect. Usually,
these messages will tell a knowledgeable user what the problem is if you are
failing to connect.
As to the "map" you want, it's implicit in what the ISP tells you to do and
my amplification of it here. Basically, you are using these files:
/usr/sbin/pppd -- the actual ppp daemon
/usr/sbin/chat -- the dialer
/usr/sbin/ppp-off -- (you may not have this) a script that terminates
a ppp connection when run.
/dev/modem -- a symlink to your modem device
/dev/ttyS* -- the actual modem device (replace * with some number;
S0 = COM1, S1 = COM2, etc.)
/etc/ppp/options -- the text file that tells pppd what options to use
when it is run. "man pppd" gives good, clear explanations
of the options and what they mean.
/etc/ppp/chat -- the script that chat uses to make a connection. Basically
consists of waitfor/send pairs -- wait for the modem to
send some string, then reply with some other string (and
'' means wait for an empty string or, in other words,
don't wait).
The executables pppd and chat will have the usual sorts of dependencies on
shared libraries, and there are a lot of apps (the usual Internet services)
you use once ppp is running, but really that is it.
Hope this helps. If not, please come back with specific questions -- it's
about all I can do as a general guide.
At 08:18 PM 5/6/99 -0400, Koyote wrote:
>Greetings all,
>
> I've been screwing around with trying to get the Linux side on
>line for a while now, I've got a whole bunch of HOWTO's printed and
>have been through the steps outlined in my ISP's other OS page
>(http://support.paonline.com/support/OTHER/LINUX.HTM) and I'm really
>not getting anywhere.
>
> I want to picture what's going on here: can someone give me a map
>of how all the files, scripts, and what have you connect?
>
> This is all just beginning to get a bit old- I have three
>documents with three different suggestions for putting in just the
>login and password under PAP!
> I'm sure I have all the pieces- there's just no order to them
>right now.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
