on 12/17/99 11:25, David C. Barnhart II at [EMAIL PROTECTED] wrote:
> on 12/17/99 9:02, Mike Jagdis at [EMAIL PROTECTED] wrote:
>
>>> I have been using diald-0.16.5-201 on RedHat 5.1 with PPP 2.3.5
>>> quite successfully with an ISP that used the standard login/
>>> password entry. Now I'm using AT&T that doesn't allow that
>>> method, only CHAP (not PAP). What I need to know is if there is
>>> any way to force PPP to use CHAP before PAP.
>>
>> Try using refuse-pap in your pppd options.
>
> Yeah, I tried that, but that was no better than removing the
> pap-secrets file. It gave me exactly the same trace. Here is
> a new one with PPP debug turned on. Assuming I am reading it
> correctly, it appears my local pppd is refusing to authenticate
> with CHAP. Why would it do that? Any Ideas?
OK, I found the problem. Apparently I needed to add a "user <userid>"
line to /etc/ppp/options for CHAP to work correctly. That works with
both diald and a direct connection. Interestingly, I was unable to
pass in that option using the pppd-options line in diald.conf, or
putting it on one of the lines after pppd-options. Since it works in
the options file itself, it's no big deal, but it does mean that the
options file will have to get swapped out for different functions.
--
David C. Barnhart II KF4KXM
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
