Bug 782098 - Simultaneous redistribution of IPv4 and IPv6 connected and static routes in bgpd.conf does not work
Summary: Simultaneous redistribution of IPv4 and IPv6 connected and static routes in b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: quagga
Version: 6.2
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1356047
TreeView+ depends on / blocked
 
Reported: 2012-01-16 14:21 UTC by Vesselin Kolev
Modified: 2017-10-04 14:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-04 14:32:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vesselin Kolev 2012-01-16 14:21:43 UTC
Description of problem:

If one try to redistribute simultaneously IPv4 and IPv6 static or (and) connected routes by declaring "redistribute static|connected" in bgpd.conf, only IPv4 protocol routes become subject to redistribution in BGP. For example, the bgpd.conf configuration structure:

...
router bgp 65002
   ...
   redistribute connected
   ...
address-family ipv6
   ...
   redistribute connected
   ...

does not work properly.


Version-Release number of selected component (if applicable): All quagga-0.99.x shipped with RHEL 4/5/6


How reproducible:always


Steps to Reproduce:
1. Enter the bgpd configuration terminal console:
$ telnet localhost bgpd
2. Switch to enable mode:
>en
3. Enter the configuration mode
# configuration terminal
4. Enter the router description and set the redistribution of the connected (ot static) and static routes into BGP:
# router bgp 65002
# redistribute connected
# redistribute static
# address-family ipv6
# redistribute connected
# redistribute static

  
Actual results: BGP process redistributes only the IPv4 static and connected routes

Expected results: BGP must redistribute static and connected routes simultaneously regardless the address protocol.

Additional info:

There is a patch which is trying to solve the problem:
http://www.gossamer-threads.com/lists/engine?do=post_attachment;postatt_id=1645;list=quagga
It can be backported to the current quagga package version shipped with RHEL5/6.

Comment 2 Jiri Skala 2012-01-17 15:21:28 UTC
Yes, the patch can be backported as is. The patch was sent to upstream in September 2011 but I don't find it in upstream git. See:

http://marc.info/?l=quagga-dev&m=131620867113463&w=2

Comment 3 Jiri Skala 2012-01-26 14:21:24 UTC
I've asked about the status of this patch on quagga-dev mailing list. The mail was addressed to author of the patch too. I have no reaction till today. AFAIK the patch is not applied by upstream.

Comment 4 Vesselin Kolev 2012-01-26 14:46:39 UTC
It's a strange silence though, but in fact the patch works fine without any visible problems. For example, the patched version of bgpd works in production in AS5421 (Sofia University) uninterrupted for a month. In addition the patch could be successfully applied against quagga-0.99.20-x shipped with Fedora 15/16.

Comment 6 Suzanne Logcher 2012-02-14 23:28:14 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 unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 7 Michal Sekletar 2016-07-22 09:34:10 UTC
Already works with newer versions.

Comment 8 Vesselin Kolev 2017-03-06 01:09:46 UTC
Note that the same problem appears with the latest version of quagga in Fedora Rawhide - 26. The version there is 1.1.1. I tested it - the same problem with the redistribution of IPv6.

Comment 9 Vesselin Kolev 2017-03-21 07:13:17 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1429275

The bug has been submitted to Fedora Rawhide team. Hope they could solve it soon.

Comment 10 Tomáš Hozza 2017-10-04 14:32:02 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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