Have RH 6.1. Updated PPP to latest RH 6.1 patch ppp-2.3.10-3.i386.rpm.
PPP stops working with the following error:
/usr/sbin/pppd: The remote system is required to authenticate itself but I
/usr/sbin/pppd: couldn't find any suitable secret (password) for it to use
Reverted back to RH6.0 ppp distribution (ppp-2.3.7-2) and all works ok. No
changes to script files in either case.
Version: Linux version 2.2.12-20smp (firstname.lastname@example.org) (gcc
version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 SMP
Anyone have any ideas?
I believe if you add 'noauth' in an appropriate spot in the
PPP options (either globally or for that system), this will
stop. Pppd apparently now insists on PAP/CHAP authentication
in some situations where it didn't used to.
This solved the problem. Thanks.
You probably already have a default route set up on your machine and
you then ask pppd to set up a default route as well (with PPP, to do
so is the default, so you wouldn't need to do so explicitly). pppd
won't do it.
The next revision of our initscripts package will solve the problem
completely by deleting the default route before trying to install a
Yes, I too received the same problem. I can reproduce it easily. Also, I
tried reinstalling my system (for various reasons, mainly experimental),
downloaded all available patches for 6.1, and after updating my PPP to the
latest version (2.3.10-3.i386), I got the same problem.
I will remove this package and place the old one back.
I had the same problem, that is I lost my ppp connectivity after upgrading to
the latest initscripts package. It seems that if the variable GATEWAYDEV is
blank the /etc/sysconfig/network-scripts/if-up script put a defaultroute on
every interface it mounts. On my system I solved putting a line
in /etc/sysconfig/network. Now PPP works well and the route table is OK.
As I understand it, this should be fixed in the latest errata release of the
initscripts package (http://www.redhat.com/support/errata/RHSA1999052-04.html).
Please reopen this bug if it does not solve this problem.
*** Bug 9764 has been marked as a duplicate of this bug. ***
*** Bug 9730 has been marked as a duplicate of this bug. ***
*** Bug 10204 has been marked as a duplicate of this bug. ***