IPv6 with Global Scope not getting assigned when VM Boots up

asked 2017-06-06 00:33:14 -0600

Anirudh gravatar image

Hi Team,

We are configuring IPv6 Networks on OpenStack Mitaka IPv4 Network, but we are facing the issue that VM after boot up has no IPv6 assigned on the Ethernet port.

We have configured the Networks and configuration following the link

https://docs.openstack.org/mitaka/networking-guide/config-ipv6.html (https://docs.openstack.org/mitaka/net...)

Dibbler server is also being configured for DHCPv6.

Also enabled the flag in /etc/nova/nova.conf


We are able to access the VM via IPv6, by manually assigning the IPv6 by accessing the console using the command

                      ip -6 addr add <IPV6> dev <Interface>

Can you please suggest some steps in order to resolve the concerns.

Regards Anirudh Gupta

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2017-06-06 07:45:54 -0600

correajl gravatar image

Could you show how you configured the subnets? For example, what is the combination of the parameters --ipv6_ra_mode and --ipv6_address_mode?

For example, from docs:

Setting DHCPv6-stateless for ipv6_ra_mode configures the neutron router with radvd agent to send RAs. The table below captures the values set for the address configuration flags in the RA packet in this scenario. Similarly, setting DHCPv6-stateless for ipv6_address_mode configures neutron DHCP implementation to provide the additional network information.

So, you could use tcpdump to see if RA are really being sent from network controller.

I suggest you to create rules in Security Groups to permit all network packets! So, you could debug to define if this really is a configuration problem. Otherwise could be just packets being filtered.


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-06-06 00:33:14 -0600

Seen: 236 times

Last updated: Jun 06 '17