Re: pppd does not set ppp0 interface

From: Walt R (wmreinemer_at_tns.net)
Date: 10/02/04 

Date: 1 Oct 2004 15:27:35 -0700

miguelk@konsultex.com.br (miguelk) wrote in message news:<ee4420aa.0410010546.7dc8fec5@posting.google.com>...
> Clifford;
>
> Thanks for your suggestions. Here are the results:
>
> >
> > I'm a Slackware fan but that script should be taken out and shot.
> > ...
>
> I used it for the initial setup of the scripts but it seems to do the
> job. :-) I later abandoned it.
>
> > Instead of the above line I'd suggest
> >
> > "" ATZ&F OK
> >
> > unless there is a good reason for ignoring the dial-tone (ATX3).
>
> I found it helps sometimes, so it's really out of habit.
>
> > > "atdt0,33550168"
> > > TIMEOUT 75
> > > CONNECT
> >
> > This is very likely the problem. CONNECT followed by only a newline
> > will cause chat to send a carriage-return and often, but not always,
> > this is a signal to the ISP that a login is desired.
> >
> > Use
> >
> > CONNECT \d\c
>
> I now have this chat script:
>
> root@cigar:/etc/ppp# cat pppscript
> TIMEOUT 30
> ABORT ERROR
> ABORT BUSY
> ABORT "NO CARRIER"
> ABORT "NO DIALTONE"
> "" ATZ&F OK
> "atdt0,33550168"
> CONNECT \d\c
>
> and this options file:
>
> root@cigar:/etc/ppp# cat options
> lock
> defaultroute
> noipdefault
> modem
> /dev/ttyS1
> 57600
> crtscts
> debug
> noauth
> passive
> asyncmap 0
> name "catbert_ktex"
>
>
> > Here the ISP starts pppd and expects it's client to do the same.
> > If I'm right then the carriage-return sent by pppd causes the ISP to
> > present a prompt and it does not respond to any PPP link negotiations
> > it receives from pppd or send any itself. Stalemate, and timeout on
> > one side or the other.
>
> I now stopped using "ppp-go" and start the pppd like this:
>
> /usr/sbin/pppd -detach file /etc/ppp/options connect "/usr/sbin/chat
> -v -f /etc/ppp/pppscript"
>
> The output I get in the log file (/var/log/ppp) is:
>
> Sep 20 16:12:25 cigar pppd[1008]: pppd 2.4.1 started by root, uid 0
> Sep 20 16:12:26 cigar chat[1010]: timeout set to 30 seconds
> Sep 20 16:12:26 cigar chat[1010]: abort on (ERROR)
> Sep 20 16:12:26 cigar chat[1010]: abort on (BUSY)
> Sep 20 16:12:26 cigar chat[1010]: abort on (NO CARRIER)
> Sep 20 16:12:26 cigar chat[1010]: abort on (NO DIALTONE)
> Sep 20 16:12:26 cigar chat[1010]: send (ATZ&F^M)
> Sep 20 16:12:26 cigar chat[1010]: expect (OK)
> Sep 20 16:12:26 cigar chat[1010]: ATZ&F^M^M
> Sep 20 16:12:26 cigar chat[1010]: OK
> Sep 20 16:12:26 cigar chat[1010]: -- got it
> Sep 20 16:12:26 cigar chat[1010]: send (atdt0,33550168^M)
> Sep 20 16:12:27 cigar chat[1010]: expect (CONNECT)
> Sep 20 16:12:27 cigar chat[1010]: ^M
> Sep 20 16:12:49 cigar chat[1010]: atdt0,33550168^M^M
> Sep 20 16:12:49 cigar chat[1010]: CONNECT
> Sep 20 16:12:49 cigar chat[1010]: -- got it
> Sep 20 16:12:49 cigar chat[1010]: send (\d)
> Sep 20 16:12:50 cigar pppd[1008]: Serial connection established.
> Sep 20 16:12:50 cigar pppd[1008]: using channel 3
> Sep 20 16:12:50 cigar pppd[1008]: Using interface ppp0
> Sep 20 16:12:50 cigar pppd[1008]: Connect: ppp0 <--> /dev/ttyS1
> Sep 20 16:12:51 cigar pppd[1008]: sent [LCP ConfReq id=0x1 <asyncmap
> 0x0> <magic 0xb75677cd> <pcomp> <accomp>]
> Sep 20 16:13:19 cigar last message repeated 9 times
> Sep 20 16:13:22 cigar pppd[1008]: LCP: timeout sending Config-Requests
> Sep 20 16:13:26 cigar pppd[1008]: Terminating on signal 2.
> Sep 20 16:13:26 cigar pppd[1008]: Connection terminated.
> Sep 20 16:13:27 cigar pppd[1008]: Exit.
>
> Where it says "Terminating..." is where I gave the console a
> [crtl][c].
> ]
>
> So it looks like the remote host is not recognising or refusing to
> send information.
>
> I also did another test like this:
>
> /usr/sbin/pppd /dev/ttyS1 57600 debug connect "/usr/sbin/chat -v ''
> ATDT0,33655000 CONNECT '\d\c'"
>
> and this is the log:
>
> Sep 20 16:35:36 cigar pppd[1054]: pppd 2.4.1 started by root, uid 0
> Sep 20 16:35:37 cigar chat[1055]: send (ATDT0,33655000^M)
> Sep 20 16:35:37 cigar chat[1055]: expect (CONNECT)
> Sep 20 16:36:00 cigar chat[1055]: ATDT0,33655000^M^M
> Sep 20 16:36:00 cigar chat[1055]: CONNECT
> Sep 20 16:36:00 cigar chat[1055]: -- got it
> Sep 20 16:36:00 cigar chat[1055]: send (\d)
> Sep 20 16:36:01 cigar pppd[1054]: Serial connection established.
> Sep 20 16:36:01 cigar pppd[1054]: using channel 4
> Sep 20 16:36:01 cigar pppd[1054]: Using interface ppp0
> Sep 20 16:36:02 cigar pppd[1054]: Connect: ppp0 <--> /dev/ttyS1
> Sep 20 16:36:03 cigar pppd[1054]: sent [LCP ConfReq id=0x1 <asyncmap
> 0x0> <magic 0x244ee6f0> <pcomp> <accomp>]
> Sep 20 16:36:30 cigar last message repeated 9 times
> Sep 20 16:36:33 cigar pppd[1054]: LCP: timeout sending Config-Requests
> Sep 20 16:36:49 cigar pppd[1054]: Terminating on signal 15.
> Sep 20 16:36:49 cigar pppd[1054]: Connection terminated.
> Sep 20 16:36:49 cigar pppd[1054]: Hangup (SIGHUP)
> Sep 20 16:36:49 cigar pppd[1054]: Exit.
>
> Terribly frustrating. 4 years ago I set this up with diald on Suse 5.3
> and Red Hat 6.0 without any problems at all (except figuring out how
> it works the first time). However then I was also controlling the
> other end (Win NT RAS).
>
> Do you have any comments or clues?
>
> Miguel
**
I had a difficult time getting an external Supra modem to dial and
connect in Slackwre9.1. My config files ar as follows:

# The following four files are configured to dial
# a modem in Slackware9.1. I use an external modem
# /dev/modem is a symbolic link to the actual device.
#
#-rw------- 1 root root 556 Jan 14 23:01 options
#-rw------- 1 root root 656 Jan 14 17:31
options.demand
#-rw------- 1 root root 212 Jan 14 17:31 pap-secrets
#-rw------- 1 root root 123 Jan 14 20:12 pppscript
#
#
# lrwxrwxrwx 1 root root 5 Jan 13 02:39 /dev/modem
-> ttyS0
#
# execute as root to dial /usr/sbin/ppp-on
# execute as root to hanup /usr/sbin/ppp-off
#
#
#**************************

# /etc/ppp/options

# General configuration options for PPPD:
lock
defaultroute
noipdefault
modem
/dev/modem
115200
crtscts
# Uncomment the line below for more verbose error reporting:
#
# debug
#
# If you have a default route already, pppd may require the other side
# to authenticate itself, which most ISPs will not do. To work around
this,
# uncomment the line below. Note that this may have negative side
effects
# on system security if you allow PPP dialins. See the docs in
/usr/doc/ppp*
# for more information.
#
# noauth
passive
asyncmap 0
name "wmreinemer"
 
#*******************************************
# /etc/ppp/options.demand lines 1-23/24 92%

# General configuration options for PPPD:
lock
defaultroute
noipdefault
modem
/dev/modem
115200
crtscts
# Uncomment the line below for more verbose error reporting:
#debug
# If you have a default route already, pppd may require the other side
# to authenticate itself, which most ISPs will not do. To work around
this,
# uncomment the line below. Note that this may have negative side
effects
# on system security if you allow PPP dialins. See the docs in
/usr/doc/ppp*
# for more information.
#noauth
passive
asyncmap 0
name "wmreinemer"
ipcp-accept-local
ipcp-accept-remote
0.0.0.0:10.10.10.10
demand
connect "/usr/sbin/chat -v -f /etc/ppp/pppscript"

#***********************************

# /etc/ppp/pap-secrets

# PAP authentication file: /etc/ppp/pap-secrets
# This file should have a permission of 600.
# ~# chmod 600 /etc/ppp/pap-secrets
# Username Server Password IP addresses
"wmreinemer" * "password"

#************************************

# /etc/ppp/pppscript

TIMEOUT 60
ABORT ERROR
ABORT BUSY
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
"" "AT&FH0"
OK "atdt8631945"
TIMEOUT 75
CONNECT

# *****
Walt R.

Relevant Pages

  • Re: modem question
    ... > been authenticated, or if pppd is handling the authentication, it will ... > take over after the dial-up connection has been established. ... > So when pppd says the connect script failed, ... > Whatever process is used to dial your ISP is failing with that modem. ...
    (RedHat)
  • Re: Dial on demand
    ... is for a US Robotics modem, ... This script is based on Bill Unruh's web page at ... ahead of the line that starts pppd in demand mode. ...
    (comp.os.linux.setup)
  • [opensuse] Verizon UMW190 wireless broadband modem
    ... I just got a Verizon UMW190 USB modem for my ASUS 1000HE netbook. ... They both said to connect with pppd and gave the scripts to do so. ... ABORT '\nNO CARRIER\r' ...
    (SuSE)
  • Re: modem question
    ... >>been authenticated, or if pppd is handling the authentication, it will ... >>So when pppd says the connect script failed, ... >>Whatever process is used to dial your ISP is failing with that modem. ... in the last line after 'CONNECTION'. ...
    (RedHat)
  • Re: pppd not responding to carrier lost
    ... one that required carrier, and one that blocked access when carrier ... but maybe the chat is used to initialize the modem. ... I now using a script to ping the remote host when pppd is active. ...
    (alt.os.linux)