> On Tue, 16 Nov 1999, Denis Voitenko wrote:
>
> |I have pppd-2.3.10 running on Slack 7 (2.2.13). The script is correct to
> |my understaning and has worked on a different machine also running Slack
> |7. On the new machine it gives:
> |
> |The remote system is required to authenticate itself but I could not find
> |any suitable secret (password) for it to do so.
>
> It *is* a silly message.
This is a VERY silly message INDEED.
> It means that you have an existing default route to a LAN and pppd now
> assumes that you are going to provide the peer with access to the Internet,
> or at least access to the LAN, and should want to require authentication.
>
> I don't agree with the concept of tying a default route to a default pppd
> authentication requirement. But a solution is to remove the existing
> default route, a network-specific route works fine for a single LAN.
> Alternately, you can add the pppd noauth option.
This problem is not OS version specific. I had the same problem on a fresh
RedHat 6.1 installation. and it drove me crazy for several days. I noted the
old default route and removed it and the start up file line that installed it,
and at the same same I installed the "noauth" option. I am not sure which
REALLY solved the problem. I note in the pppd documentation that pppd will not
replace an existing default route so the "noauth" option by it self may not be
a complete solution.
dlg
<snip>
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
