Bug 64903 - Bad default values for PPPoE timeout
Summary: Bad default values for PPPoE timeout
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rp-pppoe
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-14 07:35 UTC by Graham Cole
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-05-14 07:35:25 UTC
Embargoed:


Attachments (Terms of Use)

Description Graham Cole 2002-05-14 07:35:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408

Description of problem:
PPPOE_TIMEOUT value is set to 20 seconds by default. the LCP_INTERVAL is also
set to 20 seconds
pppoe man page states that the timeout should be about 4 times the
lcp-echo-interval 

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


How reproducible:
Always

Steps to Reproduce:
1. use the network configuration program to set up an xDSL connection
2. activate the connection
3. tail -f /var/log/messages
4. Allow the connection to sit idle and the connection will soon be lost and
restarted.  If there is activity, the link will naturally not go down.
	

Actual Results:  The link will periodically go down and then back up again

Expected Results:  The link shouldn't go down.

Additional info:

I manually set PPPOE_TIMEOUT in
/etc/sysconfig/network-scripts/ifcfg-ppp0 to 80.  This seemed to fix the problem.

Comment 1 Ngo Than 2002-06-07 15:35:00 UTC
it's fixed in 3.4-3. You will find it in the next rawhide release


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