Bug 745728

Summary: Discovery endless loop on broadcast PADI packets
Product: Red Hat Enterprise Linux 5 Reporter: Alexandr A. Panko <a.panko>
Component: rp-pppoeAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.7CC: a.panko, pknirsch
Target Milestone: rcFlags: pm-rhel: needinfo? (a.panko)
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-02 13:17:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Prevent endless discovery loop none

Description Alexandr A. Panko 2011-10-13 08:38:43 UTC 
Created attachment 527887 [details]
Prevent endless discovery loop

Description of problem:
Timeout is ignored for broadcast type packets and some other type packets.
Package rp-pppoe-3.5-32.1 and previous and newer versions.
File discovery.c
Function waitForPADS(PPPoEConnection *conn, int timeout)
Hope the issue is seen in patch file (attached).

Version-Release number of selected component (if applicable):
Package rp-pppoe-3.5-32.1 think all newer had not fixed the bug too.

How reproducible:
Put client machine in the environment where there are PADI broadcast packets send by other machines.
So usual discovery request like "pppoe -A -d" will loop endless (at list much more then timeout).

Steps to Reproduce:
For example:
1. On machine "B-client":
while true; do pppoe -I eth1 -A -d -T2; done;

2. On machine "A-client":
pppoe -A -d -I eth1 -T2
will loop much much more then 2 seconds...


Actual results:
Loop forever in discovery cycle.


Expected results:
Return access concentrators on timeout measures.


Additional info:
First I put this bug description at http://bugs.centos.org/view.php?id=5043
Comment 1 Alexandr A. Panko 2011-11-21 09:12:03 UTC 
Why there is no activity with this bug?
Does anything unclear?
Should I give more info?
Is patch understandable?
Comment 2 RHEL Program Management 2013-05-01 07:16:58 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 3 RHEL Program Management 2014-03-07 13:42:57 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 4 RHEL Program Management 2014-06-02 13:17:32 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).