Bug 134220 - Invalid parameter for $DEMAND in /sbin/adsl-connect script
Invalid parameter for $DEMAND in /sbin/adsl-connect script
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rp-pppoe (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-09-30 07:04 EDT by Uwe Beck
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 07:12:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
adsl-connect script patch (559 bytes, patch)
2004-09-30 07:07 EDT, Uwe Beck
no flags Details | Diff

  None (edit)
Description Uwe Beck 2004-09-30 07:04:51 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.4.3)

Description of problem:
The /sbin/adsl-connect script in RHEL4_beta1 contains an invalid
parameter in variable $DEMAND if adsl is configured for Dial on Demand.

The interface config file ifcg-ppp0 contains "CONNECT_TIMEOUT=60".
adsl-connect do not know CONNECT_TIMEOUT but IDLETIMEOUT which is not
used in config file. In result the pppd get an invalid value for
parameter idle and do not start.

Fix: Use /sbin/adsl-connect form RHEL3 rp-pppoe-3.5-4.1.i386.rpm
 -> attachment adsl-connect-patch

I also see:
contains "ipchains" should be "iptables".

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

How reproducible:

Steps to Reproduce:
1. configure adsl with Dial on Demand
2. start adsl

Actual Results:  pppd can not start

Expected Results:  adsl with Dial on Demand should work

Additional info:
Comment 1 Uwe Beck 2004-09-30 07:07:58 EDT
Created attachment 104576 [details]
adsl-connect script patch
Comment 2 Ngo Than 2004-09-30 07:12:47 EDT
it's fixed in rp-pppoe-3.5-1, which will show up in rawhide soon.
Thanks for your report.

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