Bug 1429275
| Summary: | Quagga bgpd does not redistribute IPv6 prefixes from underlying protocols (connected, kernel, static, etc) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vesselin Kolev <vlk> |
| Component: | quagga | Assignee: | Michal Ruprich <mruprich> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 27 | CC: | balajig81, mruprich, msekleta, vlk |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-30 18:11:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vesselin Kolev
2017-03-06 01:17:59 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. I tried to reproduce this problem on older versions of Quagga and both ipv4 and ipv6 connected routes are redistributed just fine. When I look at the steps to reproduce in the original RHEL-6 bug, there is on command missing without which the ipv6 redistribution doesn't work (but of course the reproducer might not be complete so perhaps the user set this right as well): In the address-family ipv6 environment you need to activate the neighbour if you use ipv4 connection for BGP with command 'neighbor X.X.X.X activate'. After issuing this command the ipv6 routes were successfully exchanged. The problem with the reproducer is that it lacks a lot of thing that might influence the outcome like route-maps etc. The bug dealing with this on upstream is in UNCONFIRMED status and the upstream doesn't seem to be doing anything about that. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |