<div dir="ltr">Hi Stefan<div><br></div><div>The IPv6 design in OpenNebula is basically designed to work with the auto-configuration features of IPv6. An IPv6 capable host will always have link-local addresses for all their interfaces. AFAIK you cannot disable IPv6 stack per interface. So it really does not make sense to have one interface for IPv4 and other for IPv6, as the IPv4 will also have the link local addreses (plus the host multi-cast address).</div>
<div><br></div><div>About the generation of the host-id (the 64 lower bits) can be generated: following the modified EUI-64, based on the IP, or by any other means (usually random generation is accepted as a more secure option). But I see this as part of the guest configuration and probably not for context (although you could generate this through a context variable or using the IPv4 address...) </div>
<div><br></div><div>So the ideal setup is to have a router in your virtual network advertising the IPv6 network prefix (e.g. radvd or zebra) and then let the ICMPv6 protocol autoconfigure the interface. The addresses shown in OpenNebula are supposed to match those obtained by the previous procedure (as long as the prefix advertised is the one configured in the vnet). </div>
<div><br></div><div>Currently, the only way to add more IP addresses is to add more network interfaces to the VM. Probably a nice feature could be a NIC of type "alias" or "virtual" so you get the lease from the vnet, but not an additional nic. The context script can simple "ip addr add" the IP from the virtual NIC through context.</div>
<div><br></div><div>Probably, I am not fully getting your proposal...</div><div><br></div><div>Cheers</div><div><br></div><div>Ruben</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 27, 2014 at 2:09 PM, Stefan Kooman <span dir="ltr"><<a href="mailto:stefan@bit.nl" target="_blank">stefan@bit.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi List,<br>
<br>
While deploying some vm's with IPv4/IPv6 (dual stack) support I ran into<br>
some issues. I would like to be able to choose (switch "on" or "off")<br>
the use of IPv6 in a "dual stack" vnet, i.e. It's possible to enforce<br>
IPv4 address generation in a "IPv6" network but it's not possible (as<br>
far as I can see) to disable IPv6 in a IPv6/IPv4 network (dual stack as<br>
I call it). I would like to avoid having two different vnet's, one for<br>
IPv6 and one for IPv4 just to be able to be able to provide vm's with:<br>
1) IPv4 only, 2) IPv6 only, 3) two different interfaces, one for IPv4<br>
and one for IPv6. Of course there are ways to disable IPv6 on the vm<br>
itself (just not load ipv6 modules for example) but it would be cleaner<br>
to fix this with contextualization.<br>
<br>
With IPv4 vnet it's possible to choose an ip address. With IPv6 vnet<br>
it's automatically generated based on the mac-address. It's currently<br>
not possible to choose your IPv6 address. One common practice is to use<br>
"IPv4" address in "IPv6" address. Example: IPv4 192.0.2.33, IPv6<br>
2001:db8:122:344:192:0:2:33 (note this is not truly mapping ipv4 into<br>
ipv6, as described in rfc4291).<br>
<br>
Some vm's need more that one IP(v4/v6) address. For example webservers<br>
handling multple SSL websites. Currently I can't create an ip "alias"<br>
for a virtual machine. A workaround would be to hold a lease and<br>
manually adding this ip to the vm. It would be nicer to have support for<br>
ip aliases. This feature would complement issue #1818 [1].<br>
<br>
If some of what I described above is already possible please point me<br>
the documentation.<br>
<br>
Gr. Stefan<br>
<br>
[1]: <a href="http://dev.opennebula.org/issues/1818" target="_blank">http://dev.opennebula.org/issues/1818</a><br>
<span><font color="#888888"><br>
<br>
<br>
--<br>
| BIT BV <a href="http://www.bit.nl/" target="_blank">http://www.bit.nl/</a> Kamer van Koophandel 09090351<br>
| GPG: 0xD14839C6 <a href="tel:%2B31%20318%20648%20688" value="+31318648688" target="_blank">+31 318 648 688</a> / <a href="mailto:info@bit.nl" target="_blank">info@bit.nl</a><br>
</font></span><br>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (GNU/Linux)<br>
<br>
iF4EAREIAAYFAlLmWnMACgkQTyGgYdFIOcYP2AD/Y5o9+GTv0U+JO7sJKyz7d9s6<br>
lX16Uc1b2q5O0BfTuFIBAJp9lmu0EXtwXLtgI/ljm3VP8KstnGB+jRo3JivUo6R2<br>
=vBjL<br>
-----END PGP SIGNATURE-----<br>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org" target="_blank">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org<br clear="all"><div><br></div>-- <br></a><div dir="ltr"><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank"><div>
<div>-- <br></div></div>Ruben S. Montero, PhD<br>Project co-Lead and Chief Architect</a><div><a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">OpenNebula - Flexible Enterprise Cloud Made Simple<br>
</a><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:rsmontero@opennebula.org" target="_blank">rsmontero@opennebula.org</a> | @OpenNebula</div></div>
</blockquote></div></div></div>