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.