<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hey there,<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 11/02/2021 12:20, Piotr Misiak
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:fe012dc2-e266-3d07-e500-461aa53405e3@gmail.com">
<blockquote type="cite" style="color: #007cff;">
<pre class="moz-quote-pre" wrap="">So in order to use a globally-reachable IPv6 address you should use a
port from a provider network in the instance.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Thanks Brian for the prompt response.
Does this mean that the only functional IPv6 scenario in Neutron/OVN is
where VMs are directly connected to an IPv6 GUA provider network?</pre>
</blockquote>
<p>I ran into a similar question a while back:
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015682.html">http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015682.html</a><br>
But there I was wondering / discussing if requesting a prefix
larger than /64 was possible to allow using that routed prefix to
host i.e. a VPN solution.<br>
</p>
<p>Prefix delegation of GUA prefixes implemented in Neutron
apparently:
<a class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/neutron/+spec/ipv6-prefix-delegation">https://blueprints.launchpad.net/neutron/+spec/ipv6-prefix-delegation</a><br>
And to me prefix delegation of a global unicast address prefix
(GUA) seems like the cleanest solution.</p>
<p><br>
</p>
<p>Regards</p>
<p><br>
</p>
<p>Christian<br>
</p>
</body>
</html>