Bug 64903

Summary: Bad default values for PPPoE timeout
Product: [Retired] Red Hat Linux Reporter: Graham Cole <koujiacheng>
Component: rp-pppoeAssignee: Than Ngo <than>
Status: CLOSED RAWHIDE QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-14 07:35:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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