| Re: IPv6 auto-configuration issue with virtual Ethernet [message #41306 is a reply to message #41222] |
Mon, 27 December 2010 03:16  |
lars.bailey
Messages: 38
Registered: April 2010
|
Member |
|
|
After performing other IPv6 configurations on a test OVZ IPv6 network,my final solution for IPv4 RedHat containers pulling auto-config IPv6 addresses,did not sit well with me,as I knew this issue could be fixed without much effort.
Then I realized,the solution lied on the Node server.
All Node servers,use this configuration now,in "/etc/sysconfig/network" file.
NETWORKING=yes
HOSTNAME=stooge.lan.intranet
NETWORKING_IPV6=yes
IPV6FORWARDING=yes
IPV6_AUTOCONF=no
IPV6_AUTOTUNNEL=no
By adding this to an IPv4 RedHat container;
NETWORKING_IPV6=yes
IPV6_AUTOCONF=no
it no longer pulls auto-configured IPv6 addresses.
This of course,if you bridge both IPv4 and IPv6 containers,and you are advertising a "/64" on the bridge interface.
Why it effects RedHat containers only,without proper IPv6 configurations,I can only conclude it has to do with using
bridged Ethernet.
Since,the IPv4 VETH interface is bound to the bridge,and a container has a link-local address,this seems to be the only
correct answer.
If anybody has any other ideas,post it,as I'm still a little
curious as to why.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
