Public bug reported: Hi,
this is both a question and a bug report. Currently, when setting an external gateway on a router by using an external network with both IPv4 and IPv6 subnets, two IPs are assigned - IPv4 and IPv6. However, according to the docs [1] , Openstack Networking does not yet support NAT with IPv6. This makes the IPv6 address on the external gateway both confusing and without any use. I propose to stop assigning IPv6 for router's external gateway to avoid such confusion. If it's not supported yet, then there's no reason to assign it. While Master might yet include such support in the future, stable branches such as Stein or Train do not. The nature of those being stable is that they don't include big features, only bug fixes, which means that they will never support IPv6 with NAT. Therefore, even if you decide to leave this assignment in the Master branch, I think that stable branches should have this removed regardless. Some simple variation of "[v4] if is_gw_port else [v4, v6_stateful]" should suffice - [2] . [1] https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#nat-floating-ips [2] https://opendev.org/openstack/neutron/src/commit/9e2a0ac058305dd16d6dedb883d305cd162f5fe4/neutron/db/ipam_pluggable_backend.py#L279 ** Affects: neutron Importance: Undecided Status: New ** Tags: ext-gw external gateway ipv6 nat router -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1996199 Title: router external gateway assigning unsupported IPv6 Status in neutron: New Bug description: Hi, this is both a question and a bug report. Currently, when setting an external gateway on a router by using an external network with both IPv4 and IPv6 subnets, two IPs are assigned - IPv4 and IPv6. However, according to the docs [1] , Openstack Networking does not yet support NAT with IPv6. This makes the IPv6 address on the external gateway both confusing and without any use. I propose to stop assigning IPv6 for router's external gateway to avoid such confusion. If it's not supported yet, then there's no reason to assign it. While Master might yet include such support in the future, stable branches such as Stein or Train do not. The nature of those being stable is that they don't include big features, only bug fixes, which means that they will never support IPv6 with NAT. Therefore, even if you decide to leave this assignment in the Master branch, I think that stable branches should have this removed regardless. Some simple variation of "[v4] if is_gw_port else [v4, v6_stateful]" should suffice - [2] . [1] https://docs.openstack.org/neutron/latest/admin/config-ipv6.html#nat-floating-ips [2] https://opendev.org/openstack/neutron/src/commit/9e2a0ac058305dd16d6dedb883d305cd162f5fe4/neutron/db/ipam_pluggable_backend.py#L279 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1996199/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
