ISP uses PAP, but not always??

ISP uses PAP, but not always??

Post by Paul Winkle » Tue, 20 Jul 1999 04:00:00



Hi,

I'm finding that about half the time, seemingly at random, I can't get a
connection to my ISP. Some days it's fine, some days it's inconsistent,
some days it takes so many calls to get a connection that I just give
up. The ISP uses PAP, but I've determined through my logs and through
minicom sessions that when things aren't working, for no apparent
reason, I get a shell account login prompt instead, in which case I
never get PAP authenticated and chat & pppd eventually give up. (I don't
have a shell account at the ISP!)

I've written to the ISP, but all they will tell me is "you need to make
sure you are using PAP in order to log in successfully. try forcing pppd
to use PAP."

I don't understand how to do this. I've gone through the PPP-HOWTO, the
pppd FAQ, man pppd, and man chat. I've seen occasional mention of
situations like this, with no instructions on how to deal with it.

I promise to post a summary of anything that works. Please help!

I already tried adding the "require-pap" option to /etc/ppp/options,
but that's not what's needed: it makes it impossible to connect. From
the pppd manpage,

       require-pap
              Require the peer to authenticate itself  using  PAP
                          ^^^^
              [Password  Authentication Protocol] authentication.

And from the example scripts provided with pppd:

  # This requires TWO WAY authentication - do NOT use this for a
standard
  # PAP authenticated link to an ISP as this will require the ISP
machine
  # to authenticate itself to your machine (and it will not be able to).
  require-chap

So all that does is try to get my ISP to authenticate itself to my
machine, which it cannot do. I want the opposite: to force the ISP to
request MY machine to authenticate using PAP. Is there a way I can do
that?

I'm experimenting with a few things, but so far nothing seems to
produce consistent results. Today I'm connecting OK pretty often, but
I still sometimes get the shell login stuff.

Following are two log files: one from a failed connection, one from a
successful connection. You can see that in the failed connection, it
gets to the point where I would expect to see "garbage" from ppp
(starting with a tilde), but instead I get: "Annex Command Line
Interpreter   *   Copyright (C) 1988, 1996 Xylogics, Inc."
When that happens, ppp never seems to start on the server, so chat
doesn't exit on my system, and no ppp connection ever gets made.

Here's the log from a failed connection. (Produced by giving pppd the
"debug" option, and chat the "-v" flag.)
(Sorry this is a long message. I thought it best to include as much
information as possible. At the end I've included my /etc/ppp/options
and chat scripts.)

Jul 19 00:18:41 slink chat[516]: timeout set to 10 seconds
Jul 19 00:18:41 slink chat[516]: expect (OK)
Jul 19 00:18:41 slink chat[516]: ^M
Jul 19 00:18:41 slink chat[516]: AT&F2S7=45S0=0L1V1&c1E1Q0^M^M
Jul 19 00:18:41 slink chat[516]: OK
Jul 19 00:18:41 slink chat[516]:  -- got it
Jul 19 00:18:41 slink chat[516]: send (ATDT3390138^M)
Jul 19 00:18:41 slink chat[516]: timeout set to 60 seconds
Jul 19 00:18:41 slink chat[516]: expect (CONNECT)
Jul 19 00:18:41 slink chat[516]: ^M
Jul 19 00:18:58 slink chat[516]: ^MATDT3390138^M^M
Jul 19 00:18:58 slink chat[516]: CONNECT
Jul 19 00:18:58 slink chat[516]:  -- got it
Jul 19 00:18:58 slink chat[516]: send (^M)
Jul 19 00:18:58 slink chat[516]: expect (~)
Jul 19 00:18:58 slink chat[516]:  38400^M
Jul 19 00:19:02 slink chat[516]: ^M
Jul 19 00:19:02 slink chat[516]: ^M
Jul 19 00:19:02 slink chat[516]: Annex Command Line Interpreter   *  
Copyright (C) 1988, 1996 Xylogics, Inc.^M
Jul 19 00:19:02 slink chat[516]: ^M
Jul 19 00:19:02 slink chat[516]:                            
ULSTERNet                                        
Jul 19 00:19:02 slink chat[516]:                   1)     Log onto Shell
account and new BBS                  
Jul 19 00:19:02 slink chat[516]:                     2)     Exit -
Hangup                                        
Jul 19 00:19:02 slink chat[516]:  
Jul 19 00:19:02 slink chat[516]:              ^[[1mEnter command: ^[[m
Jul 19 00:19:58 slink chat[516]: alarm
Jul 19 00:19:58 slink chat[516]: send (\K)
Jul 19 00:19:58 slink chat[516]: expect (~)
Jul 19 00:19:59 slink chat[516]:                            
ULSTERNet                                        
Jul 19 00:19:59 slink chat[516]:                   1)     Log onto Shell
account and new BBS                  
Jul 19 00:19:59 slink chat[516]:                     2)     Exit -
Hangup                                        
Jul 19 00:19:59 slink chat[516]:  
Jul 19 00:19:59 slink chat[516]:              ^[[1mEnter command: ^[[m
Jul 19 00:20:58 slink chat[516]: alarm
Jul 19 00:20:58 slink pppd[513]: Connect script failed
Jul 19 00:20:58 slink chat[516]: Failed
Jul 19 00:20:59 slink pppd[513]: Exit.

#######################################################

For comparison, here is a log from a successful ppp session:

Jul 19 00:26:12 slink pppd[562]: pppd 2.3.5 started by root, uid 0
Jul 19 00:26:13 slink chat[565]: report (CONNECT)
Jul 19 00:26:13 slink chat[565]: abort on (NO\sDIALTONE)
Jul 19 00:26:13 slink chat[565]: abort on (BUSY)
Jul 19 00:26:13 slink chat[565]: abort on (NO\sANSWER)
Jul 19 00:26:13 slink chat[565]: send (^MAT^M)
Jul 19 00:26:13 slink chat[565]: expect (OK)
Jul 19 00:26:13 slink chat[565]: ^MAT^M^M
Jul 19 00:26:13 slink chat[565]: OK
Jul 19 00:26:13 slink chat[565]:  -- got it
Jul 19 00:26:13 slink chat[565]: send (ATH0^M)
Jul 19 00:26:13 slink chat[565]: timeout set to 10 seconds
Jul 19 00:26:13 slink chat[565]: expect (OK)
Jul 19 00:26:13 slink chat[565]: ^M
Jul 19 00:26:13 slink chat[565]: ATH0^M^M
Jul 19 00:26:13 slink chat[565]: OK
Jul 19 00:26:13 slink chat[565]:  -- got it
Jul 19 00:26:13 slink chat[565]: send (AT&F2S7=45S0=0L1V1&c1E1Q0^M^M)
Jul 19 00:26:14 slink chat[565]: timeout set to 10 seconds
Jul 19 00:26:14 slink chat[565]: expect (OK)
Jul 19 00:26:14 slink chat[565]: ^M
Jul 19 00:26:14 slink chat[565]: AT&F2S7=45S0=0L1V1&c1E1Q0^M^M
Jul 19 00:26:14 slink chat[565]: OK
Jul 19 00:26:14 slink chat[565]:  -- got it
Jul 19 00:26:14 slink chat[565]: send (ATDT3390138^M)
Jul 19 00:26:14 slink chat[565]: timeout set to 60 seconds
Jul 19 00:26:14 slink chat[565]: expect (CONNECT)
Jul 19 00:26:14 slink chat[565]: ^M
Jul 19 00:26:31 slink chat[565]: ^MATDT3390138^M^M
Jul 19 00:26:31 slink chat[565]: CONNECT
Jul 19 00:26:31 slink chat[565]:  -- got it
Jul 19 00:26:31 slink chat[565]: send (^M)
Jul 19 00:26:31 slink chat[565]: expect (~)
Jul 19 00:26:31 slink chat[565]:  38400^M
Jul 19 00:26:32 slink chat[565]: ~
Jul 19 00:26:32 slink chat[565]:  -- got it
Jul 19 00:26:32 slink chat[565]: send (^M)
Jul 19 00:26:32 slink pppd[562]: Serial connection established.
Jul 19 00:26:33 slink pppd[562]: Using interface ppp0
Jul 19 00:26:33 slink pppd[562]: Connect: ppp0 <--> /dev/ttyS1
Jul 19 00:26:33 slink pppd[562]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
<magic 0xbe75febd> <pcomp> <accomp>]
Jul 19 00:26:33 slink pppd[562]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
<magic 0xbe75febd> <pcomp> <accomp>]
Jul 19 00:26:35 slink pppd[562]: rcvd [LCP ConfReq id=0x2 <asyncmap 0x0>
<auth pap> <magic 0xfe48127> <pcomp> <accomp>]
Jul 19 00:26:35 slink pppd[562]: sent [LCP ConfAck id=0x2 <asyncmap 0x0>
<auth pap> <magic 0xfe48127> <pcomp> <accomp>]
Jul 19 00:26:35 slink pppd[562]: sent [PAP AuthReq id=0x1 user="*******"
password="********"]
Jul 19 00:26:38 slink pppd[562]: sent [PAP AuthReq id=0x2 user="*******"
password="********"]
Jul 19 00:26:38 slink pppd[562]: rcvd [PAP AuthAck id=0x2 ""]
Jul 19 00:26:38 slink pppd[562]: Remote message:
Jul 19 00:26:38 slink pppd[562]: sent [IPCP ConfReq id=0x1 <addr
0.0.0.0> <compress VJ 0f 01>]
Jul 19 00:26:39 slink pppd[562]: rcvd [IPCP ConfReq id=0x3 <compress VJ
0f 01> <addr 208.148.73.3>]
Jul 19 00:26:39 slink pppd[562]: sent [IPCP ConfAck id=0x3 <compress VJ
0f 01> <addr 208.148.73.3>]
Jul 19 00:26:42 slink pppd[562]: sent [IPCP ConfReq id=0x1 <addr
0.0.0.0> <compress VJ 0f 01>]
Jul 19 00:26:42 slink pppd[562]: rcvd [IPCP ConfNak id=0x1 <addr
208.133.193.43>]
Jul 19 00:26:42 slink pppd[562]: sent [IPCP ConfReq id=0x2 <addr
208.133.193.43> <compress VJ 0f 01>]
Jul 19 00:26:42 slink pppd[562]: rcvd [IPCP ConfAck id=0x2 <addr
208.133.193.43> <compress VJ 0f 01>]
Jul 19 00:26:42 slink pppd[562]: local  IP address 208.133.193.43
Jul 19 00:26:42 slink pppd[562]: remote IP address 208.148.73.3

####################################################################

Following are the relevant config files. I run these scripts with this
command:
pppd call ulsternet1
(or: pppd call ulsternet2)

##############################

# Filename: /etc/ppp/options

 debug
 crtscts
 asyncmap 0
 modem
 defaultroute

 /dev/ttyS1
 0.0.0.0:0.0.0.0
 noipdefault
 ipcp-accept-remote
 ipcp-accept-local
 auth
# is ppp slow to start on remote machine? Try this. HOWTO suggests 30.
lcp-max-configure 60

# must give name for PAP or CHAP to work.
name abigoo
# End of file.

#####################
# Here is my /etc/ppp/pap-secrets (well, sort of.)

# Secrets for authentication using PAP
# client        server  secret                  IP addresses
<USERNAME>       *     <PASSWORD>               *
# End of file.

########################################################

# Here is my main chatscript.

# Filename: /etc/ppp/chat-ulsternet
ECHO            OFF
REPORT          CONNECT
ABORT           NO\sDIALTONE
ABORT           BUSY
ABORT           NO\sANSWER
''              \rAT
'OK-+++\c-OK'   ATH0
TIMEOUT         10
SAY 'Modem initialization.\n'
OK              AT&F2S7=45S0=0L1V1&c1E1Q0^M
# dialing Ulsternet.
TIMEOUT         10
SAY 'Dialing Ulsternet.\n'
# \T gets number from -T flag to chat.
OK              ATDT\T
TIMEOUT         60
CONNECT ""
SAY 'Connected, trying to log in.\n'
#
# From the PPP howto:
# "When your chat script completes, pppd starts on your PC. However, if
# you have not completed the log in process to the server (including
# ...

read more »

 
 
 

ISP uses PAP, but not always??

Post by Clifford Ki » Tue, 20 Jul 1999 04:00:00


[edited]

: I already tried adding the "require-pap" option to /etc/ppp/options,
: but that's not what's needed: it makes it impossible to connect. From

Yep, as I said in a reply to another post:  an ISP that will authenticate
itself is rarer than a hen's tooth.

[edited]

: So all that does is try to get my ISP to authenticate itself to my
: machine, which it cannot do. I want the opposite: to force the ISP to
: request MY machine to authenticate using PAP. Is there a way I can do
: that?

No, there's no way to force the ISP peer to request anything.  Either
one of the two peers in a PPP link negotiation can _request_ something
directly or through a configure-nak but neither one can force the other
to accept a particular option.  In the case where a proper connection
was made the peer requests PAP and pppd agrees.

[edited]

: Here's the log from a failed connection. (Produced by giving pppd the
: "debug" option, and chat the "-v" flag.)

[edited]

: Jul 19 00:18:58 slink chat[516]: CONNECT
: Jul 19 00:18:58 slink chat[516]:  -- got it
: Jul 19 00:18:58 slink chat[516]: send (^M)
: Jul 19 00:18:58 slink chat[516]: expect (~)
: Jul 19 00:18:58 slink chat[516]:  38400^M
: Jul 19 00:19:02 slink chat[516]: ^M
: Jul 19 00:19:02 slink chat[516]: ^M
: Jul 19 00:19:02 slink chat[516]: Annex Command Line Interpreter   *  

Compare this with the similar lines below from the successful session.

One of the ^Ms that follow 38400 is from the  CONNECT ""  chat expect/send
and this is very likely what confuses the ISP into presenting a menu
rather than skipping the menu and starting PPP instead.  The ^Ms are
carriage returns, one from the CONNECT "" and one from the ISP as a
spacer to begin the menu.

Note that in the messages below no ^M is seen arriving, only that two
are sent.  In this instance the carriage return from  CONNECT "" is
not sent until after the `~' is found that marks the start of PPP at
the ISP and after chat has yielded to pppd.  It comes too late to be
picked up and logged by chat and to late to affect the ISP.  So whether
you connect or not depends on whether the carriage return is sent before
or after the ISP starts PPP .

Sometimes the ISP is slow to start PPP and is confused by the carriage
return.  Sometimes it is quick to start PPP and the carriage return
problem is avoided.

A solution is to not send a carriage return.  You can do this by replacing
  CONNECT ""  with CONNECT \d\c .  The new CONNECT expect/send inserts a
one-second delay and doesn't send a carriage return.  The \d shouldn't
be necessary but sometimes it seems to help.  The  ~  ''  expect/send
probably isn't necessary but it shouldn't hurt either.

[edited]

: For comparison, here is a log from a successful ppp session:

[edited]

: Jul 19 00:26:31 slink chat[565]: CONNECT
: Jul 19 00:26:31 slink chat[565]:  -- got it
: Jul 19 00:26:31 slink chat[565]: send (^M)
: Jul 19 00:26:31 slink chat[565]: expect (~)
: Jul 19 00:26:31 slink chat[565]:  38400^M
: Jul 19 00:26:32 slink chat[565]: ~
: Jul 19 00:26:32 slink chat[565]:  -- got it
: Jul 19 00:26:32 slink chat[565]: send (^M)

--

/* My confidence in this answer (X), on a scale of 1 to 10:
   |----|----|----|----|----|----|----|----|----|X---|
   0----1----2----3----4----5----6----7----8----9----10 */

 
 
 

ISP uses PAP, but not always??

Post by Cowles, Stev » Tue, 20 Jul 1999 04:00:00


I don't know if you have tried this combination, but this is straight out of
my /etc/ppp/options file.

<cut/paste from /etc/ppp/options>
# authentication can either be pap or chap. As most people only want to
# use pap, you can also disable chap:
require-pap
refuse-chap

#################################################

Paul Winkler <zarmz...@hotmail.com> wrote in message

news:379392A6.BE3A7A1E@hotmail.com...
> Hi,

> I'm finding that about half the time, seemingly at random, I can't get a
> connection to my ISP. Some days it's fine, some days it's inconsistent,
> some days it takes so many calls to get a connection that I just give
> up. The ISP uses PAP, but I've determined through my logs and through
> minicom sessions that when things aren't working, for no apparent
> reason, I get a shell account login prompt instead, in which case I
> never get PAP authenticated and chat & pppd eventually give up. (I don't
> have a shell account at the ISP!)

> I've written to the ISP, but all they will tell me is "you need to make
> sure you are using PAP in order to log in successfully. try forcing pppd
> to use PAP."

> I don't understand how to do this. I've gone through the PPP-HOWTO, the
> pppd FAQ, man pppd, and man chat. I've seen occasional mention of
> situations like this, with no instructions on how to deal with it.

> I promise to post a summary of anything that works. Please help!

> I already tried adding the "require-pap" option to /etc/ppp/options,
> but that's not what's needed: it makes it impossible to connect. From
> the pppd manpage,

>        require-pap
>               Require the peer to authenticate itself  using  PAP
>                           ^^^^
>               [Password  Authentication Protocol] authentication.

> And from the example scripts provided with pppd:

>   # This requires TWO WAY authentication - do NOT use this for a
> standard
>   # PAP authenticated link to an ISP as this will require the ISP
> machine
>   # to authenticate itself to your machine (and it will not be able to).
>   require-chap

> So all that does is try to get my ISP to authenticate itself to my
> machine, which it cannot do. I want the opposite: to force the ISP to
> request MY machine to authenticate using PAP. Is there a way I can do
> that?

> I'm experimenting with a few things, but so far nothing seems to
> produce consistent results. Today I'm connecting OK pretty often, but
> I still sometimes get the shell login stuff.

> Following are two log files: one from a failed connection, one from a
> successful connection. You can see that in the failed connection, it
> gets to the point where I would expect to see "garbage" from ppp
> (starting with a tilde), but instead I get: "Annex Command Line
> Interpreter   *   Copyright (C) 1988, 1996 Xylogics, Inc."
> When that happens, ppp never seems to start on the server, so chat
> doesn't exit on my system, and no ppp connection ever gets made.

> Here's the log from a failed connection. (Produced by giving pppd the
> "debug" option, and chat the "-v" flag.)
> (Sorry this is a long message. I thought it best to include as much
> information as possible. At the end I've included my /etc/ppp/options
> and chat scripts.)

> Jul 19 00:18:41 slink chat[516]: timeout set to 10 seconds
> Jul 19 00:18:41 slink chat[516]: expect (OK)
> Jul 19 00:18:41 slink chat[516]: ^M
> Jul 19 00:18:41 slink chat[516]: AT&F2S7=45S0=0L1V1&c1E1Q0^M^M
> Jul 19 00:18:41 slink chat[516]: OK
> Jul 19 00:18:41 slink chat[516]:  -- got it
> Jul 19 00:18:41 slink chat[516]: send (ATDT3390138^M)
> Jul 19 00:18:41 slink chat[516]: timeout set to 60 seconds
> Jul 19 00:18:41 slink chat[516]: expect (CONNECT)
> Jul 19 00:18:41 slink chat[516]: ^M
> Jul 19 00:18:58 slink chat[516]: ^MATDT3390138^M^M
> Jul 19 00:18:58 slink chat[516]: CONNECT
> Jul 19 00:18:58 slink chat[516]:  -- got it
> Jul 19 00:18:58 slink chat[516]: send (^M)
> Jul 19 00:18:58 slink chat[516]: expect (~)
> Jul 19 00:18:58 slink chat[516]:  38400^M
> Jul 19 00:19:02 slink chat[516]: ^M
> Jul 19 00:19:02 slink chat[516]: ^M
> Jul 19 00:19:02 slink chat[516]: Annex Command Line Interpreter   *
> Copyright (C) 1988, 1996 Xylogics, Inc.^M
> Jul 19 00:19:02 slink chat[516]: ^M
> Jul 19 00:19:02 slink chat[516]:
> ULSTERNet
> Jul 19 00:19:02 slink chat[516]:                   1)     Log onto Shell
> account and new BBS
> Jul 19 00:19:02 slink chat[516]:                     2)     Exit -
> Hangup
> Jul 19 00:19:02 slink chat[516]:
> Jul 19 00:19:02 slink chat[516]:              ^[[1mEnter command: ^[[m
> Jul 19 00:19:58 slink chat[516]: alarm
> Jul 19 00:19:58 slink chat[516]: send (\K)
> Jul 19 00:19:58 slink chat[516]: expect (~)
> Jul 19 00:19:59 slink chat[516]:
> ULSTERNet
> Jul 19 00:19:59 slink chat[516]:                   1)     Log onto Shell
> account and new BBS
> Jul 19 00:19:59 slink chat[516]:                     2)     Exit -
> Hangup
> Jul 19 00:19:59 slink chat[516]:
> Jul 19 00:19:59 slink chat[516]:              ^[[1mEnter command: ^[[m
> Jul 19 00:20:58 slink chat[516]: alarm
> Jul 19 00:20:58 slink pppd[513]: Connect script failed
> Jul 19 00:20:58 slink chat[516]: Failed
> Jul 19 00:20:59 slink pppd[513]: Exit.

> #######################################################

> For comparison, here is a log from a successful ppp session:

> Jul 19 00:26:12 slink pppd[562]: pppd 2.3.5 started by root, uid 0
> Jul 19 00:26:13 slink chat[565]: report (CONNECT)
> Jul 19 00:26:13 slink chat[565]: abort on (NO\sDIALTONE)
> Jul 19 00:26:13 slink chat[565]: abort on (BUSY)
> Jul 19 00:26:13 slink chat[565]: abort on (NO\sANSWER)
> Jul 19 00:26:13 slink chat[565]: send (^MAT^M)
> Jul 19 00:26:13 slink chat[565]: expect (OK)
> Jul 19 00:26:13 slink chat[565]: ^MAT^M^M
> Jul 19 00:26:13 slink chat[565]: OK
> Jul 19 00:26:13 slink chat[565]:  -- got it
> Jul 19 00:26:13 slink chat[565]: send (ATH0^M)
> Jul 19 00:26:13 slink chat[565]: timeout set to 10 seconds
> Jul 19 00:26:13 slink chat[565]: expect (OK)
> Jul 19 00:26:13 slink chat[565]: ^M
> Jul 19 00:26:13 slink chat[565]: ATH0^M^M
> Jul 19 00:26:13 slink chat[565]: OK
> Jul 19 00:26:13 slink chat[565]:  -- got it
> Jul 19 00:26:13 slink chat[565]: send (AT&F2S7=45S0=0L1V1&c1E1Q0^M^M)
> Jul 19 00:26:14 slink chat[565]: timeout set to 10 seconds
> Jul 19 00:26:14 slink chat[565]: expect (OK)
> Jul 19 00:26:14 slink chat[565]: ^M
> Jul 19 00:26:14 slink chat[565]: AT&F2S7=45S0=0L1V1&c1E1Q0^M^M
> Jul 19 00:26:14 slink chat[565]: OK
> Jul 19 00:26:14 slink chat[565]:  -- got it
> Jul 19 00:26:14 slink chat[565]: send (ATDT3390138^M)
> Jul 19 00:26:14 slink chat[565]: timeout set to 60 seconds
> Jul 19 00:26:14 slink chat[565]: expect (CONNECT)
> Jul 19 00:26:14 slink chat[565]: ^M
> Jul 19 00:26:31 slink chat[565]: ^MATDT3390138^M^M
> Jul 19 00:26:31 slink chat[565]: CONNECT
> Jul 19 00:26:31 slink chat[565]:  -- got it
> Jul 19 00:26:31 slink chat[565]: send (^M)
> Jul 19 00:26:31 slink chat[565]: expect (~)
> Jul 19 00:26:31 slink chat[565]:  38400^M
> Jul 19 00:26:32 slink chat[565]: ~
> Jul 19 00:26:32 slink chat[565]:  -- got it
> Jul 19 00:26:32 slink chat[565]: send (^M)
> Jul 19 00:26:32 slink pppd[562]: Serial connection established.
> Jul 19 00:26:33 slink pppd[562]: Using interface ppp0
> Jul 19 00:26:33 slink pppd[562]: Connect: ppp0 <--> /dev/ttyS1
> Jul 19 00:26:33 slink pppd[562]: sent [LCP ConfReq id=0x1 <asyncmap 0x0>
> <magic 0xbe75febd> <pcomp> <accomp>]
> Jul 19 00:26:33 slink pppd[562]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0>
> <magic 0xbe75febd> <pcomp> <accomp>]
> Jul 19 00:26:35 slink pppd[562]: rcvd [LCP ConfReq id=0x2 <asyncmap 0x0>
> <auth pap> <magic 0xfe48127> <pcomp> <accomp>]
> Jul 19 00:26:35 slink pppd[562]: sent [LCP ConfAck id=0x2 <asyncmap 0x0>
> <auth pap> <magic 0xfe48127> <pcomp> <accomp>]
> Jul 19 00:26:35 slink pppd[562]: sent [PAP AuthReq id=0x1 user="*******"
> password="********"]
> Jul 19 00:26:38 slink pppd[562]: sent [PAP AuthReq id=0x2 user="*******"
> password="********"]
> Jul 19 00:26:38 slink pppd[562]: rcvd [PAP AuthAck id=0x2 ""]
> Jul 19 00:26:38 slink pppd[562]: Remote message:
> Jul 19 00:26:38 slink pppd[562]: sent [IPCP ConfReq id=0x1 <addr
> 0.0.0.0> <compress VJ 0f 01>]
> Jul 19 00:26:39 slink pppd[562]: rcvd [IPCP ConfReq id=0x3 <compress VJ
> 0f 01> <addr 208.148.73.3>]
> Jul 19 00:26:39 slink pppd[562]: sent [IPCP ConfAck id=0x3 <compress VJ
> 0f 01> <addr 208.148.73.3>]
> Jul 19 00:26:42 slink pppd[562]: sent [IPCP ConfReq id=0x1 <addr
> 0.0.0.0> <compress VJ 0f 01>]
> Jul 19 00:26:42 slink pppd[562]: rcvd [IPCP ConfNak id=0x1 <addr
> 208.133.193.43>]
> Jul 19 00:26:42 slink pppd[562]: sent [IPCP ConfReq id=0x2 <addr
> 208.133.193.43> <compress VJ 0f 01>]
> Jul 19 00:26:42 slink pppd[562]: rcvd [IPCP ConfAck id=0x2 <addr
> 208.133.193.43> <compress VJ 0f 01>]
> Jul 19 00:26:42 slink pppd[562]: local  IP address 208.133.193.43
> Jul 19 00:26:42 slink pppd[562]: remote IP address 208.148.73.3

> ####################################################################

> Following are the relevant config files. I run these scripts with this
> command:
> pppd call ulsternet1
> (or: pppd call ulsternet2)

> ##############################

> # Filename: /etc/ppp/options

>  debug
>  crtscts
>  asyncmap 0
>  modem
>  defaultroute

>  /dev/ttyS1
>  0.0.0.0:0.0.0.0
>  noipdefault
>  ipcp-accept-remote
>  ipcp-accept-local
>  auth
> # is ppp slow to start on remote machine? Try this. HOWTO suggests 30.
> lcp-max-configure 60

> # must give name for PAP or CHAP to work.
> name abigoo
> # End of file.

> #####################
> # Here is my /etc/ppp/pap-secrets (well, sort of.)

> # Secrets for authentication using PAP
> # client        server  secret                  IP addresses
> <USERNAME>       *     <PASSWORD>               *
> # End of file.

> ########################################################

> # Here is my main chatscript.

> # Filename: /etc/ppp/chat-ulsternet
> ECHO OFF
> REPORT

...

read more »

 
 
 

ISP uses PAP, but not always??

Post by Paul Winkle » Wed, 21 Jul 1999 04:00:00



> I don't know if you have tried this combination, but this is straight out of
> my /etc/ppp/options file.

> <cut/paste from /etc/ppp/options>
> # authentication can either be pap or chap. As most people only want to
> # use pap, you can also disable chap:
> require-pap
> refuse-chap

Thanks for the effort. That was covered in my original post: require-pap
is an option for servers, not clients. It does not have the intended
effect, it makes it impossible to connect _ever_.

--

----------------    paul winkler    ------------------

 
 
 

ISP uses PAP, but not always??

Post by Paul Winkle » Wed, 21 Jul 1999 04:00:00



> One of the ^Ms that follow 38400 is from the  CONNECT ""  chat expect/send
> and this is very likely what confuses the ISP into presenting a menu
> rather than skipping the menu and starting PPP instead.  The ^Ms are
> carriage returns, one from the CONNECT "" and one from the ISP as a
> spacer to begin the menu.
(snip)
> A solution is to not send a carriage return.  You can do this by replacing
>   CONNECT ""  with CONNECT \d\c .  The new CONNECT expect/send inserts a
> one-second delay and doesn't send a carriage return.  The \d shouldn't
> be necessary but sometimes it seems to help.  The  ~  ''  expect/send
> probably isn't necessary but it shouldn't hurt either.

Drat. That sounded like a really good explanation. Sadly, it doesn't
seem to help... I edited my chatscript as per your suggestions and found
no difference, I'm still getting annoyingly frequent "annex command line
blah blah blah." (It took me seven attempts to get in here to reply!)

Any other ideas?

Thanks anyway,

PW

 
 
 

ISP uses PAP, but not always??

Post by Frank Waarsenbur » Wed, 21 Jul 1999 04:00:00


I'm still convinced that this causes the problem. Either the CR's, or there is
too much time between the actual connect and the LCP negotiation. You could try
the 'silent' or 'quiet' options. They cause pppd to send a REQ only once, or not
at all, waiting for the ISP to start negotiation. I had a similar problem and it
turned out to be a timing issue..

Frank



> > One of the ^Ms that follow 38400 is from the  CONNECT ""  chat expect/send
> > and this is very likely what confuses the ISP into presenting a menu
> > rather than skipping the menu and starting PPP instead.  The ^Ms are
> > carriage returns, one from the CONNECT "" and one from the ISP as a
> > spacer to begin the menu.
> (snip)
> > A solution is to not send a carriage return.  You can do this by replacing
> >   CONNECT ""  with CONNECT \d\c .  The new CONNECT expect/send inserts a
> > one-second delay and doesn't send a carriage return.  The \d shouldn't
> > be necessary but sometimes it seems to help.  The  ~  ''  expect/send
> > probably isn't necessary but it shouldn't hurt either.

> Drat. That sounded like a really good explanation. Sadly, it doesn't
> seem to help... I edited my chatscript as per your suggestions and found
> no difference, I'm still getting annoyingly frequent "annex command line
> blah blah blah." (It took me seven attempts to get in here to reply!)

> Any other ideas?

> Thanks anyway,

> PW

 
 
 

ISP uses PAP, but not always??

Post by Clifford Ki » Wed, 21 Jul 1999 04:00:00


: Drat. That sounded like a really good explanation. Sadly, it doesn't
: seem to help... I edited my chatscript as per your suggestions and found
: no difference, I'm still getting annoyingly frequent "annex command line
: blah blah blah." (It took me seven attempts to get in here to reply!)

: Any other ideas?

Show us the chat messages that appear when it fails with these changes.

I'm still convinced that what I described is what happened.

--

/* To extract lines:  View file with "vi -R".  Move cursor to first line.
   Press "v".  Move cursor to mark lines (Esc unmarks).  Write lines to
   fubar with ":w fubar <Enter>".  Exit with ":q <Enter>". */

 
 
 

ISP uses PAP, but not always??

Post by Paul Winkle » Thu, 22 Jul 1999 04:00:00



> Show us the chat messages that appear when it fails with these changes.

> I'm still convinced that what I described is what happened.

Well, since you and Frank are both convinced that it's the carriage
returns and/or timing, I simplified my chatscript somewhat--took out
comments and SAY strings--just so I could read it more easily. It now
(right now, anyway) seems to be working perfectly. I hope it lasts!
Chatscript now looks like this:

# Filename: /etc/ppp/chat-ulsternet
ECHO            OFF
REPORT          CONNECT
ABORT           NO\sDIALTONE
ABORT           BUSY
ABORT           NO\sANSWER
''              \rAT
'OK-+++\c-OK'   ATH0
TIMEOUT         10
OK              AT&F2S7=45S0=0L1V1&c1E1Q0^M
TIMEOUT         10
OK              ATDT\T
TIMEOUT         60
CONNECT         \c
# end of file.

If you're curious, here's part of the log from the failed session you
asked about. The carriage returns still seem to be there, don't know
why. It's possible my previous edit of the chatscript was bogus.

Here's the log excerpt:
Jul 19 00:18:41 slink chat[516]: send (ATDT3390138^M)
Jul 19 00:18:41 slink chat[516]: timeout set to 60 seconds
Jul 19 00:18:41 slink chat[516]: expect (CONNECT)
Jul 19 00:18:41 slink chat[516]: ^M
Jul 19 00:18:58 slink chat[516]: ^MATDT3390138^M^M
Jul 19 00:18:58 slink chat[516]: CONNECT
Jul 19 00:18:58 slink chat[516]:  -- got it
Jul 19 00:18:58 slink chat[516]: send (^M)
                                 ^^^^^^^^^ This is the culprit? I can't
                                           find the line in the
                                           chatscript that does this,
                                           but whatever...
Jul 19 00:18:58 slink chat[516]: expect (~)
Jul 19 00:18:58 slink chat[516]:  38400^M
Jul 19 00:19:02 slink chat[516]: ^M
Jul 19 00:19:02 slink chat[516]: ^M
Jul 19 00:19:02 slink chat[516]: Annex Command Line Interpreter   *  
Copyright
(C) 1988, 1996 Xylogics, Inc.^M
Jul 19 00:19:02 slink chat[516]: ^M
Jul 19 00:19:02 slink chat[516]:                            
ULSTERNet        
....etc. etc. etc.

And here's an excerpt of the log from my current ppp session:
Jul 20 23:58:41 slink chat[923]: send (ATDT3390520^M)
Jul 20 23:58:42 slink chat[923]: timeout set to 60 seconds
Jul 20 23:58:42 slink chat[923]: expect (CONNECT)
Jul 20 23:58:42 slink chat[923]: ^M
Jul 20 23:59:02 slink chat[923]: ^MATDT3390520^M^M
Jul 20 23:59:02 slink pppd[920]: Serial connection established.
Jul 20 23:59:02 slink chat[923]: CONNECT
Jul 20 23:59:02 slink chat[923]:  -- got it
Jul 20 23:59:02 slink chat[923]: send ()
Jul 20 23:59:03 slink pppd[920]: Using interface ppp0
Jul 20 23:59:03 slink pppd[920]: Connect: ppp0 <--> /dev/ttyS1
Jul 20 23:59:06 slink pppd[920]: rcvd [LCP ConfReq id=0x18 <asyncmap
0xa0000> <auth pap> <magic 0x6606bd84> <pcomp> <accomp>]
....etc. etc...

----------------    paul winkler    ------------------
slinkP arts:  music, sound, illustration, design, etc.


http://www.ulster.net/~abigoo/
======================================================

 
 
 

ISP uses PAP, but not always??

Post by Clifford Ki » Thu, 22 Jul 1999 04:00:00


: And here's an excerpt of the log from my current ppp session:
: Jul 20 23:58:41 slink chat[923]: send (ATDT3390520^M)
: Jul 20 23:58:42 slink chat[923]: timeout set to 60 seconds

: Jul 20 23:58:42 slink chat[923]: expect (CONNECT)
: Jul 20 23:58:42 slink chat[923]: ^M
: Jul 20 23:59:02 slink chat[923]: ^MATDT3390520^M^M
: Jul 20 23:59:02 slink pppd[920]: Serial connection established.
: Jul 20 23:59:02 slink chat[923]: CONNECT
: Jul 20 23:59:02 slink chat[923]:  -- got it
: Jul 20 23:59:02 slink chat[923]: send ()

Right.  Now no carriage return is sent:  send () rather than send(^M).
The \c in the new   CONNECT \c   supresses it and you connect.  If you're
still uncertain, man chat will confirm this.

--

/* Better is the enemy of good enough. */

 
 
 

ISP uses PAP, but not always??

Post by bill davids » Thu, 22 Jul 1999 04:00:00




| I'm finding that about half the time, seemingly at random, I can't get a
| connection to my ISP. Some days it's fine, some days it's inconsistent,
| some days it takes so many calls to get a connection that I just give
| up. The ISP uses PAP, but I've determined through my logs and through
| minicom sessions that when things aren't working, for no apparent
| reason, I get a shell account login prompt instead, in which case I
| never get PAP authenticated and chat & pppd eventually give up. (I don't
| have a shell account at the ISP!)

There's a high probability that your chat script is hosed and has an
extra RETURN at the end. On many types of dialing which support both PPP
and shell, if it sees a RETURN it switches to shell login.

Check your chat script.

--

  The Internet is not the fountain of youth, but some days it feels like
the fountain of immaturity.

 
 
 

1. ppp not working (ISP uses PAP)

I've been trying for a few days now to create a script that will allow me
to connect to my ISP via PPP. I used an example script that I downloaded,
but it doesn't work. My ISP runs a Linux BBS that auto-detects whether a
user is dialing up using a PPP, ANSI or RIP terminal. When my script runs,
my provider defaults to ANSI. My ISP said that I need to enable PAP in
order to connect. How do you do this? I've searched the Linux Software
Map, Yahoo and Alta-Vista and have found nothing that helps. Can someone
help me with this? Email would be most appreciated...
--
----------------------------------------

Member: Team OS/2
----------------------------------------

2. New: Linux Slackware 3.3 on CD-ROM only US$19.51

3. ISP using PAP connection problem

4. AutoReBoot in FreeBSD?

5. Dail into a ISP (PPP) using PAP authentication

6. printk

7. Connecting via PPP witn a PnP modem to an ISP using PAP

8. Jaton Video Driver

9. Problem with failing to establish route table if ISP uses PAP or CHAP

10. Using PAP with kernel PPP to connect to ISP

11. Help getting PPP with my ISP using PAP

12. PPPD w/ PAP not working, works fine w/o PAP

13. PPP using CHAP not PAP