<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello ZhaoBo,<br>
<br>
The short summary of the BP [1] is that when a network contains an
IPv6 SLAAC/dhcpv6-stateless subnet, we use RADVD daemon to advertise
the prefix. RADVD deamon periodically advertises the prefix info
which is a "multicast message" received by all the hosts/VMs on the
network. When an ipv6-capable host/VM receives this Router
Advertisement message, it would generate and configure an EUI-64
IPv6 address (derived via the prefix and interface MAC address) to
its interface. <br>
<br>
I understand your concern saying that you only specified an IPv4
address for the port but you got IPv6 address as well. <br>
This is because..<br>
1. You have IPv6 subnets as part of the same network<br>
2. The nature in which SLAAC works and is implemented in Neutron.<br>
<br>
Basically, even if Neutron does not include the IPv6 address in the
port information, the VM port would be having the IPv6 address
configured on its interface. Since the port would anyway have the
IPv6 address, Neutron includes the IPv6 addresses (i.e.,
SLAAC/DHCPv6-Stateless) for the user to be aware of the list of
addresses on the port. <br>
<br>
Please note that this behavior is only for IPv6 subnets configured
with SLAAC/DHCPv6-Stateless and not for DHCPv6 Stateful subnets.<br>
<br>
Regarding the floating-ip behavior, the issue is recently fixed with
the following patch - <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/198908/">https://review.openstack.org/#/c/198908/</a><br>
[1]
<a class="moz-txt-link-freetext" href="http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html#proposed-change">http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html#proposed-change</a><br>
<br>
Regards,<br>
--Sridhar.<br>
<br>
<div class="moz-cite-prefix">On 07/22/2015 04:35 PM, zhaobo wrote:<br>
</div>
<blockquote
cite="mid:4381744a.1dd06.14eb5707498.Coremail.zb4515@163.com"
type="cite">
<div
style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">
<div
style="line-height:1.7;color:#000000;font-size:14px;font-family:Arial">
<div>Hi ,</div>
<div>Could anyone please check the bug below? I had received
message from some kind people, but I didn't get the answer
which i want.</div>
<div><span style="color: rgb(255, 0, 0);">The key point is why
the created port with specify ipv4 subnet as fixed-ip get
an ipv6 addr when there are some ipv6 slaac/dhcpstateful
subnets.</span></div>
<div><span style="color: rgb(255, 0, 0);">And I know the slaac
subnet will automatic allocate an ipv6 addr. <span
style="color: rgb(255, 0, 0); line-height: 1.7;">Users
may be confused about this behavior.</span></span></div>
<div><span style="color: rgb(0, 0, 255);"><a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/neutron/+bug/1467791">https://bugs.launchpad.net/neutron/+bug/1467791</a></span></div>
<div><br>
</div>
<div>This bug description:</div>
<div>When the created network contains one ipv4 subnet and an
ipv6 subnet which turned on slaac or stateless.</div>
<div>When I create a port use cmd like:</div>
<div>neutron port-create --fixed-ip
subnet_id=$[ipv4_subnet_id] $[network_id/name]</div>
<div>The specified fixed-ip is ipv4_subnet, but the returned
port contained the ipv6 subnet.</div>
<div><br>
</div>
<div><br>
</div>
<div>If user just want a port with ipv4 , why returned port
had allocated an ipv6 address.</div>
<div>And I know this is an design behavior from
<a class="moz-txt-link-freetext" href="http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html#proposed-change">http://specs.openstack.org/openstack/neutron-specs/specs/kilo/multiple-ipv6-prefixes.html#proposed-change</a></div>
<div>But we are still confused about this operation.</div>
<div><br>
</div>
<div>And when we create floatingip and the external network
just contained an ipv6 slaac subnet, the port will contained
the ipv6 addr . Are there some issues ? </div>
<div><br>
</div>
<div>Thank you anyone could help for confirm this issue , and
wish you return the message asap.</div>
<div><br>
</div>
<div>ZhaoBo</div>
</div>
<br>
<br>
<span title="neteasefooter"><span id="netease_mail_footer"></span></span></div>
<br>
<br>
<span title="neteasefooter"><span id="netease_mail_footer"></span></span><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>