Re: pppd 2.3 oddity. Help me, dammit! :)
>> "DH" == Dale Harrison <dth@cnsit.com.au> writes:
DH> I dialin to a provider and authenticate via PAP. This was fine up until I
DH> upgraded ppp. It doesn't authenticate anymore. I've tried it on other
DH> providers and the same story... except when I dial into another hamm box.
DH> Everything's fine then. It works like a charm.
DH> # dpkg -l |grep ppp
DH> ii ppp 2.3.5-2 Point-to-Point Protocol (PPP) daemon.
DH> ii ppp-pam 2.3.5-2 Point-to-Point Protocol (PPP) daemon
DH> Jun 25 14:25:55 apathy pppd[837]: sent [PAP AuthReq id=0x1 user="username" password="password"]
DH> Jun 25 14:25:55 apathy pppd[837]: rcvd [LCP EchoRep id=0x0 magic=0x49bd1d10]
DH> Jun 25 14:25:58 apathy pppd[837]: rcvd [PAP AuthAck id=0x1 ""]
AuthAck, so Authentication worked all right.
DH> Jun 25 14:25:58 apathy pppd[837]: Remote message:
DH> Jun 25 14:26:25 apathy pppd[837]: sent [LCP EchoReq id=0x1 magic=0xffff084d]
DH> Jun 25 14:26:25 apathy pppd[837]: rcvd [LCP EchoRep id=0x1 magic=0x49bd1d10]
Looks like it is sending the wrong "magic". Sorry, don't know what this
is. Maybe you could deinstall ppp-pam and retry.
Ciao,
Martin
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: