Red Hat Bugzilla – Bug 119280
pppd: invalid numeric parameter 'yes' for idle option, ADSL Dial on Demand can not start
Last modified: 2015-01-07 19:07:38 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.4) Gecko/20030922
Description of problem:
If you want use ADSL with Dial on Demand the pppd can not start.
pppd version 2.4.1 -> segmentation fault (see Bug #116927)
pppd version 2.4.2 (I build my own RPM) -> pppd: invalid
numeric parameter 'yes' for idle option
You can also see the false idle parameter in backtrace in Bug #116927.
The mistace is in /sbin/adsl-connect script.
# line 198 and after
# Backward config file compatibility
if test "$DEMAND" = "" ; then
if test "$DEMAND" = "no" ; then
DEMAND="demand persist idle $DEMAND \
10.112.112.112:10.112.112.113 ipcp-accept-remote ipcp-accept-local\
connect true noipdefault ktune"
What is configured in the ADSL config file?
Here is the mistace:
DEMAND="demand persist idle $DEMAND ....
$DEMAND has the value "yes".
I see this in /var/log/messages:
invalid numeric parameter 'yes' for idle option
The adsl-connect script do not use the CONNECT_TIMEOUT=60 and set this
value as the idle time in the variable DEMAND.
Version-Release number of selected component (if applicable):
rp-pppoe-3.5-4 and rp-pppoe-3.5-11 (fix for #114875 by Than)
Steps to Reproduce:
1. configure ADSL with Dial on Demand
2. start ADSL
Actual Results: pppd can not start because the idle parameter ist set
Expected Results: idle $CONNECT_TIMEOUT should use
many thank for your report. it's fixed in rp-pppoe-3.5-12, which is
available in rawhide on on people.redhat.com/than.
perhaps i will make errata soon.
Reopened so we can track this for QU3.
You mean QU2 for RHEL3?
If not, then we need the rp-pppoe-3.5-13 (yes there was another fix
in this rpm from Than, I found an old mistace during test the first
new rpm) as errata soon.
it's for RHEL3 QU3
i have build rp-pppoe-3.5-4.1 for U3, which includes this patch.
rp-pppoe-3.5-4.1 works correct and can distribute in U3.
Closing out based on feedback from original reporter.
An errata has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.