Please help on this PPP CHAP question?

I recently got a new Compaq computer with Windows XP (yuk) and also
purchased a copy of SuSE Linux 9.0 to dual boot. That part is working fine.

But SuSE 9 has changed its PPP dialer from KPPP (which worked great in
SuSE 6.4) to one called Kinternet. Kinternet (after being configured by
Yast) dials in ok and connects, but during the user authentication it is
sending a bad password after sending my correct user name. It fails on
a CHAP error as the ppp-log below shows. I noticed WVDIAL was used in
the log, so I also tried using WMDIAL directly after reading the
documentation. It failed the same way.

The password is correct - it is the same as I use here in XP and used in
SuSE 6.4.

The ISP help center suggested their own ppp script (which had nothing
about CHAP in it), but it failed too. See the second ppp log below.

The SuSE Help Center suggested putting my password in the CHAP-SECRETS
file, which I did - same result - it failed on the same CHAP error.

Has anyone else seen this error in SuSE 9 and found a solution? Do any
experts out there have any suggestions?

Don

------------------------
Here is the log from Kinternet:

SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux.
Status is: disconnected
trying to connect to smpppd
connect to smpppd
Status is: disconnected
Status is: connecting
pppd[0]: Plugin passwordfd.so loaded.
pppd[0]: Perms of /dev/ttyS0 are ok, no 'mesg n' neccesary.
pppd[0]: --> WvDial: Internet dialer version 1.42
pppd[0]: --> Initializing modem.
pppd[0]: --> Sending: ATZ
pppd[0]: ATZ
pppd[0]: OK
pppd[0]: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
pppd[0]: OK
pppd[0]: --> Sending: ATM0
pppd[0]: ATM0
pppd[0]: OK
pppd[0]: --> Modem initialized.
pppd[0]: --> Sending: ATDT7242851019
pppd[0]: --> Waiting for carrier.
pppd[0]: ATDT7242851019
pppd[0]: CONNECT 115200
pppd[0]: --> Carrier detected. Waiting for prompt.
pppd[0]: UQKT2 tnt4.phl1.da.uu.net
pppd[0]: Login:
pppd[0]: --> Looks like a login prompt.
pppd[0]: --> Sending: dfgrbac
pppd[0]: dfgrbac
pppd[0]: Password:
pppd[0]: --> Looks like a password prompt.
pppd[0]: --> Sending: (password)
pppd[0]: ** Bad Password
pppd[0]: Login:
pppd[0]: --> Looks like a login prompt.
pppd[0]: --> Sending: dfgrbac
pppd[0]: dfgrbac
pppd[0]: Password:
pppd[0]: --> Looks like a password prompt.
pppd[0]: --> Sending: (password)
pppd[0]: ** Bad Password
pppd[0]: Login:
pppd[0]: --> Looks like a login prompt.
pppd[0]: --> Sending: dfgrbac
pppd[0]: --> Don't know what to do! Starting pppd and hoping for the best.
pppd[0]: Serial connection established.
pppd[0]: using channel 4
pppd[0]: Using interface ppp0
pppd[0]: Connect: ppp0 <--> /dev/ttyS0
pppd[0]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6d8c5aec>
<pcomp> <accomp>]
pppd[0]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6d8c5aec>
<pcomp> <accomp>]
pppd[0]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00> <mru 1524> <asyncmap
0x0> <auth chap MD5> <pcomp> <accomp> <mrru 1524> <endpoint
[MAC:00:c0:7b:7b:f8:ee]>]
pppd[0]: sent [LCP ConfRej id=0x1 < 00 04 00 00> <mrru 1524>]
pppd[0]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x6d8c5aec>
<pcomp> <accomp>]
pppd[0]: rcvd [LCP ConfReq id=0x2 <mru 1524> <asyncmap 0x0> <auth chap
MD5> <pcomp> <accomp> <endpoint [MAC:00:c0:7b:7b:f8:ee]>]
pppd[0]: sent [LCP ConfAck id=0x2 <mru 1524> <asyncmap 0x0> <auth chap
MD5> <pcomp> <accomp> <endpoint [MAC:00:c0:7b:7b:f8:ee]>]
pppd[0]: sent [LCP EchoReq id=0x0 magic=0x6d8c5aec]
pppd[0]: cbcp_lowerup
pppd[0]: want: 2
pppd[0]: rcvd [CHAP Challenge id=0x1 <9f0637d9027e012973348e0721a99beb>,
name = "tnt4.phl1"]
pppd[0]: sent [CHAP Response id=0x1 <040a246e29469d511b6471d053d97a8d>,
name = "dfgrbac"]
pppd[0]: rcvd [LCP EchoRep id=0x0 magic=0x0]
pppd[0]: rcvd [CHAP Failure id=0x1 "\000"]
pppd[0]: Remote message: ^@
pppd[0]: CHAP authentication failed
Authentication error. Maybe bad account or password.
pppd[0]: cbcp_lowerdown
pppd[0]: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves to
peer"]
pppd[0]: rcvd [LCP TermAck id=0x2]
pppd[0]: Connection terminated.
pppd[0]: Hangup (SIGHUP)
Status is: disconnected
pppd[0] died: Authentication error (exit code 19)

------------------------
Here is the log from using the pppscript for chat:

Jan 28 18:10:32 linux pppd[3413]: pppd 2.4.1 started by dfgrbac, uid 0
Jan 28 18:10:32 linux pppd[3413]: Perms of /dev/modem are ok, no 'mesg
n' neccesary.
Jan 28 18:11:07 linux pppd[3413]: Serial connection established.
Jan 28 18:11:07 linux pppd[3413]: using channel 9
Jan 28 18:11:07 linux pppd[3413]: Using interface ppp0
Jan 28 18:11:07 linux pppd[3413]: Connect: ppp0 <--> /dev/modem
Jan 28 18:11:08 linux pppd[3413]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x3659e6be> <pcomp> <accomp>]
Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x3659e6be> <pcomp> <accomp>]
Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x1 < 00 04 00
00> <mru 1524> <asyncmap 0x0> <auth chap MD5> <pcomp> <accomp> <mrru
1524> <endpoint [MAC:00:c0:7b:7b:f8:ee]>]
Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x1 < 00 04 00
00> <auth chap MD5> <mrru 1524>]
Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfAck id=0x1 <asyncmap
0x0> <magic 0x3659e6be> <pcomp> <accomp>]
Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x2 <mru 1524>
<asyncmap 0x0> <auth pap> <pcomp> <accomp> <endpoint
[MAC:00:c0:7b:7b:f8:ee]>]
Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x2 <auth pap>]
Jan 28 18:11:11 linux pppd[3413]: rcvd [LCP TermReq id=0x3]
Jan 28 18:11:11 linux pppd[3413]: sent [LCP TermAck id=0x3]
Jan 28 18:11:12 linux pppd[3413]: sent [LCP ConfReq id=0x1 <asyncmap
0x0> <magic 0x3659e6be> <pcomp> <accomp>]
Jan 28 18:11:44 linux last message repeated 16 times
Jan 28 18:11:50 linux last message repeated 3 times
Jan 28 18:11:51 linux pppd[3413]: Terminating on signal 2.
Jan 28 18:11:51 linux pppd[3413]: sent [LCP TermReq id=0x2 "User request"]
Jan 28 18:11:53 linux pppd[3413]: sent [LCP TermReq id=0x3 "User request"]
Jan 28 18:11:55 linux pppd[3413]: Connection terminated.
Jan 28 18:11:56 linux pppd[3413]: Exit.
linux:~ #

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Has anyone else seen this error in SuSE 9 and found a solution? Do
> any experts out there have any suggestions?

hi, i've never run SuSE or kinternet, but just taking a guess here,
the problem is likely that your ISP authenticates using PAP and not
CHAP. PAP does not use encryption to send the password, whereas CHAP
uses a hash to authenticate. If the server expects to see a plaintext
password, but receives some form of hash, it won't know what to do
and it will fail. is there any way for you to set your authentication
mode to PAP?

Oliver

>
> Don
>
> ------------------------
> Here is the log from Kinternet:
>
> SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux.
> Status is: disconnected
> trying to connect to smpppd
> connect to smpppd
> Status is: disconnected
> Status is: connecting
> pppd[0]: Plugin passwordfd.so loaded.
> pppd[0]: Perms of /dev/ttyS0 are ok, no 'mesg n' neccesary.
> pppd[0]: --> WvDial: Internet dialer version 1.42
> pppd[0]: --> Initializing modem.
> pppd[0]: --> Sending: ATZ
> pppd[0]: ATZ
> pppd[0]: OK
> pppd[0]: --> Sending: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> pppd[0]: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
> pppd[0]: OK
> pppd[0]: --> Sending: ATM0
> pppd[0]: ATM0
> pppd[0]: OK
> pppd[0]: --> Modem initialized.
> pppd[0]: --> Sending: ATDT7242851019
> pppd[0]: --> Waiting for carrier.
> pppd[0]: ATDT7242851019
> pppd[0]: CONNECT 115200
> pppd[0]: --> Carrier detected. Waiting for prompt.
> pppd[0]: UQKT2 tnt4.phl1.da.uu.net
> pppd[0]: Login:
> pppd[0]: --> Looks like a login prompt.
> pppd[0]: --> Sending: dfgrbac
> pppd[0]: dfgrbac
> pppd[0]: Password:
> pppd[0]: --> Looks like a password prompt.
> pppd[0]: --> Sending: (password)
> pppd[0]: ** Bad Password
> pppd[0]: Login:
> pppd[0]: --> Looks like a login prompt.
> pppd[0]: --> Sending: dfgrbac
> pppd[0]: dfgrbac
> pppd[0]: Password:
> pppd[0]: --> Looks like a password prompt.
> pppd[0]: --> Sending: (password)
> pppd[0]: ** Bad Password
> pppd[0]: Login:
> pppd[0]: --> Looks like a login prompt.
> pppd[0]: --> Sending: dfgrbac
> pppd[0]: --> Don't know what to do! Starting pppd and hoping for
> the best. pppd[0]: Serial connection established.
> pppd[0]: using channel 4
> pppd[0]: Using interface ppp0
> pppd[0]: Connect: ppp0 <--> /dev/ttyS0
> pppd[0]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6d8c5aec>
> <pcomp> <accomp>]
> pppd[0]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x6d8c5aec>
> <pcomp> <accomp>]
> pppd[0]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00> <mru 1524>
> <asyncmap 0x0> <auth chap MD5> <pcomp> <accomp> <mrru 1524>
> <endpoint
> [MAC:00:c0:7b:7b:f8:ee]>]
> pppd[0]: sent [LCP ConfRej id=0x1 < 00 04 00 00> <mrru 1524>]
> pppd[0]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x6d8c5aec>
> <pcomp> <accomp>]
> pppd[0]: rcvd [LCP ConfReq id=0x2 <mru 1524> <asyncmap 0x0> <auth
> chap MD5> <pcomp> <accomp> <endpoint [MAC:00:c0:7b:7b:f8:ee]>]
> pppd[0]: sent [LCP ConfAck id=0x2 <mru 1524> <asyncmap 0x0> <auth
> chap MD5> <pcomp> <accomp> <endpoint [MAC:00:c0:7b:7b:f8:ee]>]
> pppd[0]: sent [LCP EchoReq id=0x0 magic=0x6d8c5aec]
> pppd[0]: cbcp_lowerup
> pppd[0]: want: 2
> pppd[0]: rcvd [CHAP Challenge id=0x1
> <9f0637d9027e012973348e0721a99beb>, name = "tnt4.phl1"]
> pppd[0]: sent [CHAP Response id=0x1
> <040a246e29469d511b6471d053d97a8d>, name = "dfgrbac"]
> pppd[0]: rcvd [LCP EchoRep id=0x0 magic=0x0]
> pppd[0]: rcvd [CHAP Failure id=0x1 "\000"]
> pppd[0]: Remote message: ^@
> pppd[0]: CHAP authentication failed
> Authentication error. Maybe bad account or password.
> pppd[0]: cbcp_lowerdown
> pppd[0]: sent [LCP TermReq id=0x2 "Failed to authenticate ourselves
> to peer"]
> pppd[0]: rcvd [LCP TermAck id=0x2]
> pppd[0]: Connection terminated.
> pppd[0]: Hangup (SIGHUP)
> Status is: disconnected
> pppd[0] died: Authentication error (exit code 19)
>
> ------------------------
> Here is the log from using the pppscript for chat:
>
> Jan 28 18:10:32 linux pppd[3413]: pppd 2.4.1 started by dfgrbac,
> uid 0 Jan 28 18:10:32 linux pppd[3413]: Perms of /dev/modem are ok,
> no 'mesg n' neccesary.
> Jan 28 18:11:07 linux pppd[3413]: Serial connection established.
> Jan 28 18:11:07 linux pppd[3413]: using channel 9
> Jan 28 18:11:07 linux pppd[3413]: Using interface ppp0
> Jan 28 18:11:07 linux pppd[3413]: Connect: ppp0 <--> /dev/modem
> Jan 28 18:11:08 linux pppd[3413]: sent [LCP ConfReq id=0x1
> <asyncmap 0x0> <magic 0x3659e6be> <pcomp> <accomp>]
> Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfReq id=0x1
> <asyncmap 0x0> <magic 0x3659e6be> <pcomp> <accomp>]
> Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x1 < 00 04
> 00 00> <mru 1524> <asyncmap 0x0> <auth chap MD5> <pcomp> <accomp>
> <mrru 1524> <endpoint [MAC:00:c0:7b:7b:f8:ee]>]
> Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x1 < 00 04
> 00 00> <auth chap MD5> <mrru 1524>]
> Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfAck id=0x1
> <asyncmap 0x0> <magic 0x3659e6be> <pcomp> <accomp>]
> Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x2 <mru
> 1524> <asyncmap 0x0> <auth pap> <pcomp> <accomp> <endpoint
> [MAC:00:c0:7b:7b:f8:ee]>]
> Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x2 <auth
> pap>] Jan 28 18:11:11 linux pppd[3413]: rcvd [LCP TermReq id=0x3]
> Jan 28 18:11:11 linux pppd[3413]: sent [LCP TermAck id=0x3]
> Jan 28 18:11:12 linux pppd[3413]: sent [LCP ConfReq id=0x1
> <asyncmap 0x0> <magic 0x3659e6be> <pcomp> <accomp>]
> Jan 28 18:11:44 linux last message repeated 16 times
> Jan 28 18:11:50 linux last message repeated 3 times
> Jan 28 18:11:51 linux pppd[3413]: Terminating on signal 2.
> Jan 28 18:11:51 linux pppd[3413]: sent [LCP TermReq id=0x2 "User
> request"] Jan 28 18:11:53 linux pppd[3413]: sent [LCP TermReq
> id=0x3 "User request"] Jan 28 18:11:55 linux pppd[3413]: Connection
> terminated.
> Jan 28 18:11:56 linux pppd[3413]: Exit.
> linux:~ #

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQBq89LcoUT0UavXJEQIn0QCggI9O/bjBNz1vmkYrZPfNE+d86IEAoLNL
hxT8Pi5lLzadp9zJdf41RW7E
=UB9X
-----END PGP SIGNATURE-----

Don Grbac <dfgrbac@earthlink.net> writes:

]I recently got a new Compaq computer with Windows XP (yuk) and also
]purchased a copy of SuSE Linux 9.0 to dual boot. That part is working fine.

]But SuSE 9 has changed its PPP dialer from KPPP (which worked great in
]SuSE 6.4) to one called Kinternet. Kinternet (after being configured by
]Yast) dials in ok and connects, but during the user authentication it is
]sending a bad password after sending my correct user name. It fails on
]a CHAP error as the ppp-log below shows. I noticed WVDIAL was used in
]the log, so I also tried using WMDIAL directly after reading the
]documentation. It failed the same way.

]The password is correct - it is the same as I use here in XP and used in
] SuSE 6.4.

]The ISP help center suggested their own ppp script (which had nothing
]about CHAP in it), but it failed too. See the second ppp log below.

]The SuSE Help Center suggested putting my password in the CHAP-SECRETS
]file, which I did - same result - it failed on the same CHAP error.

]Has anyone else seen this error in SuSE 9 and found a solution? Do any
]experts out there have any suggestions?

]Don

]------------------------
]Here is the log from Kinternet:

]pppd[0]: --> Waiting for carrier.
]pppd[0]: ATDT7242851019
]pppd[0]: CONNECT 115200
]pppd[0]: --> Carrier detected. Waiting for prompt.

Idiots. wvdial is falling into a trap it dug for itself. YOu have to
enable the stupid flag to get it to launch immediatly into ppp.


]pppd[0]: UQKT2 tnt4.phl1.da.uu.net
]pppd[0]: Login:
]pppd[0]: --> Looks like a login prompt.
]pppd[0]: --> Sending: dfgrbac
]pppd[0]: dfgrbac
]pppd[0]: Password:
]pppd[0]: --> Looks like a password prompt.
]pppd[0]: --> Sending: (password)
]pppd[0]: ** Bad Password
]pppd[0]: Login:
]pppd[0]: --> Looks like a login prompt.
]pppd[0]: --> Sending: dfgrbac
]pppd[0]: dfgrbac
]pppd[0]: Password:
]pppd[0]: --> Looks like a password prompt.
]pppd[0]: --> Sending: (password)
]pppd[0]: ** Bad Password
]pppd[0]: Login:
]pppd[0]: --> Looks like a login prompt.
]pppd[0]: --> Sending: dfgrbac
]pppd[0]: --> Don't know what to do! Starting pppd and hoping for the best.

This is what it should have done in the first place.

.....
]pppd[0]: rcvd [CHAP Challenge id=0x1 <9f0637d9027e012973348e0721a99beb>,
]name = "tnt4.phl1"]
]pppd[0]: sent [CHAP Response id=0x1 <040a246e29469d511b6471d053d97a8d>,
]name = "dfgrbac"]

Are you shure that is your username? Are you sure that the entry in
/etc/chap-secrets is in the form
dfgrbac * password *

]------------------------
]Here is the log from using the pppscript for chat:

So, use it! but you either really do have a messed up chap-secrets file
or you forgot to put the option
user dfgrbac
into /etc/ppp/options or onto the ppp command line.


....
]Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x1 < 00 04 00
]00> <auth chap MD5> <mrru 1524>]

You reject chap. This happens only because the user option was
forgotten, or there is no entry in chap-secrets starting with that
username.

]Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfAck id=0x1 <asyncmap
]0x0> <magic 0x3659e6be> <pcomp> <accomp>]
]Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x2 <mru 1524>
]<asyncmap 0x0> <auth pap> <pcomp> <accomp> <endpoint
][MAC:00:c0:7b:7b:f8:ee]>]
]Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x2 <auth pap>]

YOu could try also putting that line in pap-secrets but you still need
the user option.


wvdial is stupid. It is broken. You have to go into the script and
enable a flag (stupidflag or something).
Your wvdial is trying to log into the remote computer. ( note the login
prompt). The remote computer is tolerant, but that attempt may have put
it into a bad mood, causing it to reject your following attempts.

"Oliver O'Boyle" <o.oboyle@celerica.ca> writes:


]-----BEGIN PGP SIGNED MESSAGE-----
]Hash: SHA1

]> Has anyone else seen this error in SuSE 9 and found a solution? Do
]> any experts out there have any suggestions?

]hi, i've never run SuSE or kinternet, but just taking a guess here,
]the problem is likely that your ISP authenticates using PAP and not
]CHAP. PAP does not use encryption to send the password, whereas CHAP
]uses a hash to authenticate. If the server expects to see a plaintext

The ISP uses chap.
See the logs.

]password, but receives some form of hash, it won't know what to do
]and it will fail. is there any way for you to set your authentication
]mode to PAP?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The ISP uses chap.
> > See the logs.

i see that now. i didn't actually see his log post because my viewing
window is really small, i thought it was part of his signature so i
ignored it!



-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQBrW/rcoUT0UavXJEQLcrACg+FEdv2rnA0Ap18c1uszOlIvGhdAAoPk P
veawGd73scDthyF+6Z+bA9Cw
=qSdt
-----END PGP SIGNATURE-----

Bill Unruh wrote:
> ...
> You reject chap. This happens only because the user option was
> forgotten, or there is no entry in chap-secrets starting with that
> username.
>
> ]Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfAck id=0x1 <asyncmap
> ]0x0> <magic 0x3659e6be> <pcomp> <accomp>]
> ]Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x2 <mru 1524>
> ]<asyncmap 0x0> <auth pap> <pcomp> <accomp> <endpoint
> ][MAC:00:c0:7b:7b:f8:ee]>]
> ]Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x2 <auth pap>]
>
> YOu could try also putting that line in pap-secrets but you still need
> the user option.
> ...

I appreciate all your comments. Thanks for replying.

I just got a message from Earthlink that they require PAP rather than
CHAP, although their server seems to be asking for CHAP according to the
log. You gentlemen have given me ideas to try. Thanks again.

I will follow up to this thread when I have the results - for completness.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> I just got a message from Earthlink that they require PAP rather
> than CHAP, although their server seems to be asking for CHAP
> according to the log. You gentlemen have given me ideas to try.
> Thanks again.

i'm not surprised. most ISPs use PAP. i used to work for one. :)

>
> I will follow up to this thread when I have the results - for
> completness.
>

thanks

oliver

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQBrpnLcoUT0UavXJEQL1BgCg2YpaaJ/on8nrIUyv5br7PHcH7EgAniMt
+kBeWyAHVVtS1W2b4eDK9RKv
=fgav
-----END PGP SIGNATURE-----

Don Grbac <dfgrbac@earthlink.net> writes:

[...]

>Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x1 < 00 04 00
>00> <auth chap MD5> <mrru 1524>]

Well, at least here you're actually rejecting CHAP, so you'd have
to setup PAP instead...

>Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfAck id=0x1 <asyncmap
>0x0> <magic 0x3659e6be> <pcomp> <accomp>]
>Jan 28 18:11:10 linux pppd[3413]: rcvd [LCP ConfReq id=0x2 <mru 1524>
><asyncmap 0x0> <auth pap> <pcomp> <accomp> <endpoint
>[MAC:00:c0:7b:7b:f8:ee]>]
>Jan 28 18:11:10 linux pppd[3413]: sent [LCP ConfRej id=0x2 <auth pap>]

[...]

....which you obviously didn't, so it's failing.

I can't tell why the CHAP authentication with Kinternet failed;
assuming you're indeed using the correct syntax in your chap-secrets
file, this looks like a bug on the ISP's side.

Michael
--
Michael Buchenrieder * mibu@scrum.greenie.muc.de * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.

I am really embarrassed to admit this, but the problem was mine. Most
people would just ignore this and go away, but I feel I owe everyone an
explanation.

I have had three ISPs in my life. I used the same username always. But
the first two ISPs simply required the simple username fo login
(dfgrbac). Earthlink requires the full email address of the login user.
In Windows XP, all this is transparent to the user when signing up on
Earthlink.

They told me this originally when I set up SuSE 6.4, but since then I
forgot. I did a ppplog of a successful login on my old computer and
noticed the login name had the email address.

SuSE Linux 9.0 and it's Kinternet utility for logging in work fine.

My face is red!