Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1430333 - libnetfilter_conntrack does not support Ipv6 NAT
libnetfilter_conntrack does not support Ipv6 NAT
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libnetfilter_conntrack (Show other bugs)
7.3
Unspecified Unspecified
urgent Severity unspecified
: rc
: ---
Assigned To: Thomas Woerner
Tomas Dolezal
: ZStream
Depends On: 1426412
Blocks:
  Show dependency treegraph
 
Reported: 2017-03-08 06:50 EST by Jaroslav Reznik
Modified: 2017-06-07 08:23 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
The libnetfilter_conntrack packages have been upgraded to upstream version 1.0.6, which provides a number of bug fixes and enhancements over the previous version. Notably, this update adds support of IPv6 Network Address Translation (NAT) to the libnetfilter_conntrack library. As a result, libnetfilter_conntrack can now create connection tracking for IPv6 NAT entries.
Story Points: ---
Clone Of: 1426412
Environment:
Last Closed: 2017-05-25 11:35:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
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-2017:1301 normal SHIPPED_LIVE libnetfilter_conntrack bug fix and enhancement update 2017-05-25 15:31:52 EDT

  None (edit)
Description Jaroslav Reznik 2017-03-08 06:50:42 EST
This bug has been copied from bug #1426412 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 12 errata-xmlrpc 2017-05-25 11:35:55 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1301

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