Bug 109049 - Interface not enabled for RIP
Interface not enabled for RIP
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: quagga (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Fenlason
Depends On:
  Show dependency treegraph
Reported: 2003-11-04 12:07 EST by Jos Vos
Modified: 2014-08-31 19:25 EDT (History)
1 user (show)

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

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2003:349 normal SHIPPED_LIVE Updated quagga packages fix RIPv1 protocol 2003-11-14 00:00:00 EST

  None (edit)
Description Jos Vos 2003-11-04 12:07:27 EST
Description of problem:
When using ripd (same config files as with zebra 0.93a), incoming RIP
packets seemed to be ignored.  After turning on "debug rip events",
the log file says "RIP is not enabled on interface eth0" when
receiving a RIP packet on eth0.  According to
this is a known bug in ripd.

Version-Release number of selected component (if applicable):
(own rebuild of the RHEL 3 src.rpm, not tested on original RHEL 3)

I upgraded to quagga 0.96.4 and that solved the problem.  RPM build
hints: the libcap patch is not necessary anymore and the warnings
patch needs to be adapted, for the rest the 0.96.2-4.3E src.rpm works
fine with 0.96.4.
Comment 1 Jay Turner 2004-01-16 12:14:09 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.


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