Bug 6324 - Very unstable PPP setup
Summary: Very unstable PPP setup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 6.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-10-25 07:50 UTC by Redacted 003 IBM
Modified: 2019-10-02 18:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-11-22 23:03:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Redacted 003 IBM 1999-10-25 07:50:14 UTC
Hello Bugzilla,

I've installed RH 6.1 on my test partition, and it shows a
very unstable PPP dial setup. I've configured the PPP items
just like the production RH 6.0 system, using netconf. I've
repeatedly checked all settings but the problem remains. The
RH 6.1 system fails to connect to my ISP, restarting the
pppd daemon incessantly. In the /var/log/messages file I see
 complaints about pppd not being able to find a suitable
secret to authenticate the link. Occasionally it does
connect (odd) but most of the time netconf says after 15
seconds that the ifup-watch program has failed and asks me
to kill it. I believe this is caused by the new initscripts,
but I haven't demonstrated that.

Kind regards,

Comment 1 Anonymous 1999-11-16 15:56:59 UTC
I have the same problem.
A workaround to this is to add
noauth
to PPP options (there is an option for this in netconf)
After this workaround pppd usually works more or less OK.

Comment 2 Michael K. Johnson 1999-11-19 20:15:59 UTC
The next release of initscripts will fix this problem by using "noauth"
automatically in this case.  For now, you can add noauth to the extra
PPP options as ... suggests.

The problem is that pppd's behaviour regarding CHAP authentication appears
to have changed.

Comment 3 Michael K. Johnson 1999-11-22 23:03:59 UTC
In the process of releasing initscripts-4.67, which will fix this.


Note You need to log in before you can comment on or make changes to this bug.