View Single Post

  #2 (permalink)  
Old 03-07-2005
Moe Trin
 
Posts: n/a
Default Re: Wolf Linux Disconnect Problem.

In article <20050306103841.27db31b6.nospam@st.com>, nospam@st.com wrote:

>Wolf Linux is disconnecting soon after connect. I setup ppp correctly.


Actually, you did not. The tool you are using (or the book you are
following) is over nine years out of touch with reality.

>Wold Linux uses ppp and the ppp-on command.


Do you mean the 'ppp-on' and 'ppp-on-dialer' garbage that comes with ppp?
I guess you didn't notice the original file dates.

-rwx--x--x 1 root root 967 Aug 8 1995 ppp-2.4.2/scripts/ppp-off
-r-x--x--x 1 root root 1641 Oct 16 1995 ppp-2.4.2/scripts/ppp-on
-rwx------ 1 root root 397 Oct 16 1995 ppp-2.4.2/scripts/ppp-on-dialer

1995 was before microsoft invented the telephone, or whatever. The world has
changed since then (and in ppp-2.4.3, these scripts are not installed by
default anymore).

>Mar 6 05:40:20 localhost local2.info chat[835]: timeout set to 30 seconds
>Mar 6 05:40:20 localhost local2.info chat[835]: expect (OK)
>Mar 6 05:40:20 localhost local2.info chat[835]: ^M
>Mar 6 05:40:21 localhost local2.info chat[835]: ATH0^M^M
>Mar 6 05:40:21 localhost local2.info chat[835]: OK


You want to look at your modem manual. 'AT' (which is what the modem is
responding to) and ATH0 are not the modem init strings you should be using.
For a USR, it's AT&F1 - and nothing else.

>Mar 6 05:40:40 localhost local2.info chat[835]: expect (ogin:)
>Mar 6 05:40:40 localhost local2.info chat[835]: ^M
>Mar 6 05:40:40 localhost local2.info chat[835]: ^M
>Mar 6 05:40:40 localhost local2.info chat[835]: User Access Verification^M


Hello mister Ascend terminal server that is mis-configured by a dumb ISP.

>Mar 6 05:40:40 localhost local2.info chat[835]: expect (assword:)
>Mar 6 05:40:40 localhost local2.info chat[835]: djforgold^M
>Mar 6 05:37:11 localhost local2.info chat[310]: Password:
>Mar 6 05:37:11 localhost local2.info chat[310]: -- got it
>Mar 6 05:37:11 localhost local2.info chat[310]: send (dummy^M)


You mis-entered the log data here - notice the time jumps 3.5 minutes in
the wrong direction.

>Mar 6 05:37:11 localhost daemon.info pppd[308]: Connect: ppp0 -> /dev/ttyS1
>Mar 6 05:37:12 localhost daemon.info pppd[308]: sent [LCP ConfReq id=0x1 syncma
>p 0xa0000> agic 0xffff0e0a> comp> ccomp>]
>Mar 6 05:37:14 localhost daemon.info pppd[308]: Hangup (SIGHUP)


You also butchered the transcription here. Get rid of the 'asyncmap' option.
Notice that the ISP hung up the phone.

Your problem is nine years old. When you use windoze to dial in, you don't
go looking for a login prompt - why start now? The ISP really doesn't know
or care what O/S you are using, but has configured the terminal servers so
that they work with windoze. In doing so, they FAILED to disable the text
mode you have stumbled on, but this doesn't bother windoze cause it never
looks for the login prompt, and thus never sees this problem.

[compton ~]$ cat /usr/local/bin/dialin
#!/bin/bash
exec /usr/sbin/pppd connect "/usr/sbin/chat -f /etc/ppp/dialscript" \
defaultroute lock noipdefault modem nodetach /dev/modem 115200 crtscts \
user djforgold
[compton ~]$

There must not be anything after the \ in those two lines.

[compton ~]$ cat /etc/ppp/dialscript
ABORT BUSY ABORT 'NO CARRIER' "" AT&F1 OK ATDT9337556 CONNECT \d\c
[compton ~]$

A little explanation here. This script sets two abort conditions (the line
is busy, or something Other than a modem answers), then waits for nothing
( "" ) and sends an init string (check your modem manual). When the modem
responds with OK, it dials the phone number, and waits for the modem to
report establishing a connection. The script then waits one second ( \d )
and exits without sending the normal newline character ( \c ). This is the
standard PAP or CHAP setup that micro$oft has forced on the ISPs because
windoze can't script worth beans. Authentication is handled by pppd, by
having /etc/ppp/pap-secrets and/or /etc/ppp/chap-secrets (depending on which
scheme your ISP wants to use) contain something like:

djforgold * p42Sw0rD~

Obviously, you would need to put the correct password in there. Notice
that I've put all the options in the 'dialin' command, and my
/etc/ppp/options file is empty. You could move nearly all of the options
to that file if you chose.

You shouldn't feel bad about being trapped like this - the incompetent
authors of most dialin helper programs haven't discovered this little
fact of life either. But hey, it's only been nine plus years.

Old guy

Reply With Quote