[lug] pppd and wvdial troubles

D. Stimits stimits at idcomm.com
Sun Mar 18 12:51:47 MST 2001


Something that happens a lot, I think people new to this often don't
realize that even after you send your pass, many ISP's use PAP or CHAP
authentication too; these occur after login. PAP occurs once (password
authentication protocol), CHAP occurs randmonly many times (challenge
handshake authentication protocol). I would guess that one of them is
required, but I've never set it up for the --chat option. Notice that
the "noauth" is something of the corollary from your side, that it is
saying your end won't summarily drop them if it fails to authenticate,
but it does nothing if the ISP side requires it. To get an idea, check
out "man pppd", and search for "pap-secrets" and "chap-secrets". I see
nothing below that would indicate pap-secrets or chap-secrets is being
used. Open /etc/ppp/pap-secrets and /etc/ppp/chap-secrets with an editor
(they should be readable only by root) and look around. You could also
ask your ISP specifically if they use PAP or CHAP authentication. FYI,
most users would fill in one line of the pap-secrets (and same for
chap-secrets) with:
login_name  *  password

(name and pass for the ISP)

"Mark (Andy) Jolley" wrote:
> 
> I'm trying to get my Red Hat 7.0 to dial on demand, and I'm having trouble
> with the first couple of steps.  My overall goal is to setup ipchains and
> masq and create a "auto dial router/firewall" kind deal.
> 
> Please keep in mind that I'm a Linux newbie, be gentle.  But I'm a geek, I'm
> familiar with routers, firewalls, and dare I say it, NT4.0 server.  (I
> manage all of the above at work).  I have taken some UNIX classes, but that
> information is sketchy at best.
> 
> I have successfully setup wvdial, and can connect using 'wvdial qwest' every
> time(my configs are below)
> 
> but if I try /usr/sbin/pppd file /etc/ppp/options connect 'wvdial --chat
> qwest'  I get a hangup as soon as I connect and authenticate.  I'm wondering
> where the SIGHUP is coming from, and why, I'm not calling it.
> 
> My understanding of how wvdial works as a chat replacement is as follows:
> pppd initializes the modem, calls wvdial for the dialup information, and
> wvdial negotiates the ppp connection and authenticates.
> 
> I have tried just using the standard chat method /etc/ppp/options connect
> 'usr/sbin/chat -v -f /etc/ppp/qwest' and had the identical problem, my
> /var/log/messages looks pretty much the same, but with more output from
> chat.  But it all goes swimmingly until after I'm authenticated.
> 
> Now for the really annoying part, I've had either one of the above work
> about 1/15 or so times, so I'm really banging my head against the wall.
> 
> Here's the conf's and error stuff I have replace my userid with UUUUUUU and
> my password with PPPPPP for obvious reasons.  My pap-secrets and
> chap-secrets are ok.
> 
> And yes I know connecting to the internet as root is a bad thing...but I'm
> debugging now.
> 
> --------/ETC/WVDIAL.CONF
> [Modem0]
> Modem = /dev/ttyS0
> Baud = 115200
> Init1 = ATZ
> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
> 
> [Dialer Defaults]
> Modem = /dev/ttyS0
> Baud = 115200
> Init1 = ATZ
> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
> New PPPD = 1
> 
> [Dialer qwest]
> Username = UUUUUUUUU
> Password = PPPPPPPPP
> Phone = 2541619
> Area Code = 303
> Inherits = Dialer Defaults
> Stupid mode = 0
> 
> ------/ETC/PPP/OPTIONS
> lock
> /dev/ttyS0
> 115200
> crtscts
> modem
> noipdefault
> defaultroute
> idle 120
> noauth
> debug
> 
> ------/ETC/PPP/PEERS/WVDIAL (according to my man pages for wvdial, my
> version of pppd requries this file, these are default entries from Red Hat,
> couldn't find docs on what it means)
> 
> noauth
> name wvdial
> 
> -------/ETC/PPP/QWEST (my chat script if I use the standard method of chat
> instead of wvdial)
> "" atdt3032541619 CONNECT "" Username :UUUUUU sword: PPPPPPP
> 
> -------/var/log/messages snippet of when I run /usr/sbin/pppd file
> /etc/ppp/options connect 'wvdial --chat qwest'
> Mar 18 10:32:30 localhost pppd[1135]: pppd 2.3.11 started by root, uid 0
> Mar 18 10:32:31 localhost WvDial: WvDial: Internet dialer version 1.41
> Mar 18 10:32:31 localhost WvDial: Initializing modem.
> Mar 18 10:32:31 localhost WvDial: Sending: ATZ
> Mar 18 10:32:32 localhost WvDial: ATZ
> Mar 18 10:32:32 localhost WvDial: OK
> Mar 18 10:32:32 localhost WvDial: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55
> +FCLAS
> S=0
> Mar 18 10:32:32 localhost WvDial: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
> Mar 18 10:32:32 localhost WvDial: OK
> Mar 18 10:32:32 localhost WvDial: Modem initialized.
> Mar 18 10:32:32 localhost WvDial: Sending: ATDT 3032541619
> Mar 18 10:32:32 localhost WvDial: Waiting for carrier.
> Mar 18 10:32:32 localhost WvDial: ATDT 3032541619
> Mar 18 10:32:59 localhost WvDial: CONNECT 115200
> Mar 18 10:32:59 localhost WvDial: Carrier detected.  Waiting for prompt.
> Mar 18 10:32:59 localhost WvDial: User Access Verification
> Mar 18 10:32:59 localhost WvDial: Username:
> Mar 18 10:32:59 localhost WvDial: Looks like a login prompt.
> Mar 18 10:32:59 localhost WvDial: Sending: UUUUUU
>  Mar 18 10:32:59 localhost WvDial: UUUUUU
> Mar 18 10:32:59 localhost WvDial: Password:
> Mar 18 10:32:59 localhost WvDial: Looks like a password prompt.
> Mar 18 10:32:59 localhost WvDial: Sending: (password)
> Mar 18 10:33:00 localhost WvDial: Entering PPP mode.
> Mar 18 10:33:00 localhost WvDial: Async interface address is unnumbered
> (Loopbac
> k1)
> Mar 18 10:33:00 localhost WvDial: Your IP address is 207.225.104.93. MTU is
> 1500
>  bytes
> Mar 18 10:33:00 localhost WvDial: Looks like a welcome message.
> Mar 18 10:33:00 localhost pppd[1135]: Serial connection established.
> Mar 18 10:33:00 localhost pppd[1135]: Using interface ppp0
> Mar 18 10:33:00 localhost pppd[1135]: Connect: ppp0 <--> /dev/ttyS0
> Mar 18 10:33:02 localhost pppd[1135]: Hangup (SIGHUP)
> Mar 18 10:33:02 localhost pppd[1135]: Modem hangup
> Mar 18 10:33:02 localhost pppd[1135]: Connection terminated.
> Mar 18 10:33:03 localhost pppd[1135]: Exit.
> 
> TIA
> Mark (Andy) Jolley
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug



More information about the LUG mailing list