Fixed. Finally. Me happy :-)
Now I know why it worked on one box and did not on the other. I configured
the NIC on the first one by hand and didn't have the default route. In the
second case I had the install configure the NIC for me :-)
I am wondering what was the logic behind this sort of an assumption? I do
not find any benefit in assuming the defaultroute. What is the point of
adding the line defaultroute into the configs of pppd if it does not
override the existing route? Is it bad design or is it me?
Denis Voitenko
----- Original Message -----
From: David L. Gehrt <[EMAIL PROTECTED]>
To: Clifford Kite <[EMAIL PROTECTED]>
Cc: Denis Voitenko <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; Linux
Net <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, November 17, 1999 11:57 AM
Subject: Re: ppp-2.3.10 silly error
> > 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]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
