Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 82630 - PPOE_TIMEOUT in /sbin/adsl-setup is seriously wrong
PPOE_TIMEOUT in /sbin/adsl-setup is seriously wrong
Product: Red Hat Linux
Classification: Retired
Component: rp-pppoe (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Ngo Than
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-01-24 02:25 EST by Bertil Askelid
Modified: 2015-01-07 19:03 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-06-03 09:50:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bertil Askelid 2003-01-24 02:25:38 EST
Description of problem:

According to rp-pppoe documentation, PPPOE_TIMEOUT better be at least 4 times
the LCP_INTERVAL. So, it should be 80, not 20. With 3 LCP_FAILURE counts and
20 seconds LCP_INTERVAL, the PPPOE_TIMEOUT of 20 gices PPPoE no chance to stay
up, it detects a timeout before it even has had a chance to send its LCP pings.
So, it dicsonnects about once a minute and then reconnects again. New IP address
som time, and a complete waste of CPU cycles.

Took me a while to figure this out, reading docs and experimenting with DSL.
Learned a lot, but I don't think that was the intention. The value 80 solves
the problem! DSL has now been up for 12 hours without a single disconnect.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1. adls-setup
2. edit /etc/sysconfig/network-scripts/ifcfg-ppp0 with USER
3. adls-start
Actual results:

drops connection once a minute and the reconnects

Expected results:

should stay up without dropping connection so frequently

Additional info:

By the way, adls-stop is having a " " (blank) between the "#" and "!/bin/bash"
on the first line, making it impossible to run it as a script.
Comment 1 Ngo Than 2003-06-03 09:50:55 EDT
oh, this's a typo bug. It's fixed now in 3.5-4, which is available in rawhide.
Thanks for your report

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