>You've sent us too little information to get a definitive answer. My best
>guess is that you set +pap in the line that invokes pppd, which means *your*
>system is trying to demand that the *ISP* authenticate itself. But that's
>only a guess.

        Well... the ISP is using PAP.  That, and the DNS IP - these are the only
pieces of information I could get from them.

>Another guess is that the ISP requires pap authentication but you are asking
>pppd/chat to use userid/password authentication. Or maybe you have
>pap-secrets set up wrong.

        I did, some time ago.  But I got over this.

>For a better answer, send us:
>a. the line that invokes pppd

        I invoke pppd with /etc/ppp/ppp-on

>b. the contents of the ppp-on-dialer chat script

#!/bin/sh
#/etc/ppp/ppp-on script
TELEPHONE=224-4179
ACCOUNT=raider
PASSWORD=mypassword
LOCAL_IP=0.0.0.0
REMOTE_IP=0.0.0.0
NETMASK=255.255.255.0
export TELEPHONE ACCOUNT PASSWORD
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
exec pppd /dev/ttyS1 57600 \
        $LOCAL_IP:$REMOTE_IP \
        connect $DIALER_SCRIPT
#57600 because I use a 14.4K modem

#!/bin/sh
#/etc/ppp/ppp-on-dialer script
chat -v \
        TIMEOUT 5       \
        ABORT '\nBUSY\r'        \
        ABORT '\nNO ANSWER\r'   \
        ''      \rAT    \
        OK-+++\c-OK     ATH0    \
        TIMEOUT 30      \
        OK      ATDP$TELEPHONE  \
        CONNECT ''      \

# /etc/ppp/options file
asyncmap 0
crtscts
defaultroute
lock
modem
# the mru value was set to maximum; than I reduced it just in case
mru 256
netmask 255.255.255.0
noipdefault
passive
name raider
user raider
ipcp-accept-local
ipcp-accept-remote
+pap

debug
kdebug 7
lcp-echo-failure 1000
lcp-echo-interval 1

>c. the contents of pap-secrets

# Secrets for authentication using PAP
# client        server  secret                  IP addresses
raider  *       mypassword

        I even simplified the problem: I have the same account with the same
password on my Linux box.  Maybe this helps.

>d. the complete set of log entries from *one* failed attempt (should be only
>about 8 lines)

        As you could see I use both debug and kdebug 7.  That can generate a lot
of trash.  But it's useful trash.  Sadly, I don't own the knowledge to
understand it.

Jan  9 18:45:40 redbull chat[488]: ATDP224-4179^M^M 
Jan  9 18:45:40 redbull chat[488]: CONNECT -- got it 
Jan  9 18:45:40 redbull chat[488]: send (^M) 
Jan  9 18:45:40 redbull pppd[486]: Serial connection established.
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set flags to 70000
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set flags to 70000
Jan  9 18:45:41 redbull pppd[486]: Using interface ppp0
Jan  9 18:45:41 redbull pppd[486]: Connect: ppp0 <--> /dev/ttyS1
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set xasyncmap
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set flags to 70000
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set mru to 5dc
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set flags to 70010
Jan  9 18:45:41 redbull kernel: ppp: frame with bad fcs, excess = be02
Jan  9 18:45:41 redbull kernel: ppp: successfully queued 20 bytes, flags =
f070010
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set mru to 5dc
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan  9 18:45:41 redbull kernel: ppp_tty_ioctl: set flags to f070000
Jan  9 18:45:44 redbull kernel: ppp: successfully queued 30 bytes, flags =
f070000
Jan  9 18:45:44 redbull kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan  9 18:45:44 redbull kernel: ppp_tty_ioctl: set flags to f070003
Jan  9 18:45:44 redbull kernel: ppp_tty_ioctl: set mru to 100
Jan  9 18:45:44 redbull kernel: ppp: channel ppp0 mtu = 1500, mru = 256
Jan  9 18:45:44 redbull kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan  9 18:45:44 redbull pppd[486]: Remote message: Login ok
Jan  9 18:45:44 redbull kernel: ppp_tty_ioctl: set flags to f070003
Jan  9 18:45:44 redbull kernel: ppp_tty_ioctl: read demand dial info
Jan  9 18:45:44 redbull kernel: ppp: successfully queued 10 bytes, flags =
f070003
Jan  9 18:45:44 redbull kernel: ppp: successfully queued 15 bytes, flags =
f070003
Jan  9 18:45:45 redbull kernel: ppp_tty_ioctl: read demand dial info
Jan  9 18:45:45 redbull kernel: ppp: successfully queued 10 bytes, flags =
f070003
Jan  9 18:45:46 redbull kernel: ppp_tty_ioctl: read demand dial info
Jan  9 18:45:46 redbull kernel: ppp: successfully queued 10 bytes, flags =
f070003
Jan  9 18:45:47 redbull kernel: ppp: successfully queued 22 bytes, flags =
f070003
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Jan  9 18:45:47 redbull pppd[486]: PAP authentication failure for
box.mailbox.ro
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set flags to f070000
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set mru to 5dc
Jan  9 18:45:47 redbull kernel: ppp: channel ppp0 mtu = 1500, mru = 1500
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set rcv asyncmap 0
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set flags to f070010
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set flags to f070010
Jan  9 18:45:47 redbull kernel: ppp: successfully queued 6 bytes, flags =
f070010
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: get debug level 7
Jan  9 18:45:47 redbull kernel: ppp_tty_ioctl: set flags to f000010
Jan  9 18:45:47 redbull pppd[486]: Connection terminated.

        Raider
--
                ``Liberate tu-temet ex inferis''

Reply via email to