Bug 107282 - bug report from quagga devel regarding rip not yet in our package
bug report from quagga devel regarding rip not yet in our package
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: quagga (Show other bugs)
3.0
All Linux
high Severity medium
: ---
: ---
Assigned To: Jay Fenlason
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-10-16 11:11 EDT by Neil Horman
Modified: 2014-08-31 19:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-01-16 12:14:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Neil Horman 2003-10-16 11:11:33 EDT
Description of problem:
enabling RIPV1 on an interface leads to error messages in the rip log indicating
that RIP is not enabled on the interface every time a RIP packet is recieved. 
The quagga development group has tracked this down to several problems for which
a patch is available at 
http://lists.quagga.net/pipermail/quagga-dev/2003-September/000226.html




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


How reproducible:
always

Steps to Reproduce:
1.follow the steps in the teh quagga bug report:
http://lists.quagga.net/pipermail/quagga-dev/2003-September/000224.html
    
Actual results:
Error messages generated in log

Expected results:
No error messages

Additional info:
Comment 1 Jay Turner 2004-01-16 12:14:05 EST
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.

http://rhn.redhat.com/errata/RHBA-2003-349.html

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