RE: CHAP authentication failed For CHAP identification it is sometimes necessary to replace LoginName with provider/LoginName inder Linux For example if your provider is BIZMAIL, then try: BIZMAIL/LoginName MarvS On 7/31/07, YH <yh@xxxxxxxxxxxxxx> wrote: > Hi Jacques, > > > Great, Jim. > > So if I understand you correctly you compiled the source file and your > > modem works , right? > > Yes, I compiled the source file and the modem works. But the connection > is not stable, it sometime failed at authentication (please see > following log message). Like today, I actually tried 5 reconnections > before it was connected. Not sure if following wvdial.conf caused the > problem? Or should I change asyncmap to FFFFFFFF next time? > > [Dialer Defaults] > Modem = /dev/modem > Baud = 115200 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > Phone = 0198331600 > Username = hce@xxxxxxxxxxxxxx > Password = xxxxxxx > Auto DNS = on > Abort = on > Stupid Mode = yes > > Log message: > > Jul 31 20:06:45 Jupiter kernel: PPP generic driver version 2.4.2 > Jul 31 20:06:45 Jupiter pppd[2366]: pppd 2.4.1 started by root, uid 0 > Jul 31 20:06:46 Jupiter pppd[2366]: Using interface ppp0 > Jul 31 20:06:46 Jupiter pppd[2366]: Connect: ppp0 <--> /dev/ttyLT0 > Jul 31 20:06:46 Jupiter /etc/hotplug/net.agent: assuming ppp0 is already up > Jul 31 20:07:07 Jupiter pppd[2366]: Remote message: Authentication failed > Jul 31 20:07:07 Jupiter pppd[2366]: CHAP authentication failed > Jul 31 20:07:07 Jupiter pppd[2366]: Hangup (SIGHUP) > Jul 31 20:07:07 Jupiter pppd[2366]: Modem hangup > Jul 31 20:07:07 Jupiter pppd[2366]: Connection terminated. > Jul 31 20:07:07 Jupiter pppd[2366]: Exit. > > > > >
