That looks fine to me - other end requested PAP and we NAK'd it and said no,
how about CHAP.
Perfectly normal.
>mail, I read a tidbit that led me to discover that the portmaster
>refuses to do any kind of LCP authentication if a dial script was
>used. I had configured my location entry to use a dial script that
>merely dialed the number and then handed off to PPP.
Wrong info. It allows for PAP/CHAP as long as you don't use a login/password
script. You can only auth with one method. If the location table just dials
and doesn't send a login/password it is legal to just start PPP and use
PAP/CHAP. Of course, you have to configure the chat script to do this too.
> RFE: give some kind of diagnostic when this misconfiguration is
>discovered (maybe best to diagnose this only when "dial locname -x"
Technically that isn't an error, some sites don't need auth at all so that
setup is fine.
>password I had set to do its own magical dial script. However, I was
>unable to find out how to clear the dial script.
Set each line to null.
> It seems that when dialing out on an ISDN line the portmaster wants
>the host it dials to authenticate itself. To paraphrase Livingston
Location tables don't challenge the other end, ISDN or not.
> However, that may not be the problem. The Livingston seems to go
>into the IPCP phase without authenticating itself despite the fact
>that it ACKed the <auth pap>. Weird.
The end that dials must authenticate itself, that trace looked fine.
Of course, you should be sending us the PORTMASTER PPP DEBUGS and NOT the
Linux debugs. Technically that is what we work with, since we don't have
any idea what other stacks may or may not do.
-MZ
-- Livingston Enterprises - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588