Open Stack

Hi Steve!

I don’t remember if when I did all configurations here this combination was available (dhcpv6-stateful and dhcpv6-stateful). Anyway, I can tell I couldn't do dhcpv6 work well. I`m using Mitaka and dhcpv6-stateless - dhcpv6-stateless. 

Everything works when configuring manually. The addresses works well here because I'm using prefix delegation and slaac generates them. However, the dhcpv6 options didn`t work because virtual machines never ask for them. If I run dhcpv6 request manually, yes, it works. I`ve asked for help in a topic about cloud-init but no fix, just another member with the same problem. 

https://ask.openstack.org/en/question/107308/how-to-use-ipv6_ra_mode-dhcpv6-stateless-ipv6_address_mode-dhcpv6-stateless/

Test if your VMs are really asking for something! Maybe you have to use tcpdump inside "net ns ... namespace ... exec ... tcpdump <interface qr ou qv> etc” … Or not, because you are using linuxbridge. 

Regards.

> On 26 Sep 2017, at 20:58, Sterdnot Shaken <sterdnotshaken at gmail.com> wrote:
> 
> Openstack version: Ocata
> Mech driver: OVS
> Security: Linuxbridge
> 
> Hello! 
> 
> Anyone have any idea why DHCP for IPv4 works fine but DHCP for IPv6 doesn't? With Stateless or just SLAAC, the VM's calculate a correct IPv6 address from the IPv6 prefix I've assigned, but (for stateless) the instances doesn't get any of the options, like DNS, etc...  Stateful doesn't work at all. I configure a stateful network using a command like this:
> 
> openstack subnet create --allocation-pool start=2604:ffff:ffff:ffff::2,end=2604:ffff:ffff:ffff:ffff:ffff:ffff:ffff --ip-version 6 --ipv6-address-mode dhcpv6-stateful --ipv6-ra-mode dhcpv6-stateful --dns-nameserver 2620:0:ccc::2 --network cust01-v6_net0 --subnet-range 2604:ffff:ffff:ffff::/64 cust01-v6_sub0 
> 
> But none of the instances added to that network acquire a v6 address ever. I can statically assign the selected IPv6 address to the respective instance and it can then ping out using v6 just fine. I can also add IPv6 DNS addresses to resolv.conf and the instance can correctly resolve as well. This issue happens on both Linux and Windows instances...
> 
> Any ideas?
> 
> Thanks in advance!
> 
> Steve
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack