Re: IPv6 and OVZ part deux [message #41436 is a reply to message #41423] |
Thu, 20 January 2011 18:12 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
lars.bailey
Messages: 38 Registered: April 2010
|
Member |
|
|
I was getting ready to post my final conclusion to an issue in another thread,on using Ethernet bridging with IPv6.
Your example confirmed my thinking,into a proper way of using IPv6 with bridged Ethernet.
My thread here,mainly dealt with IPv6/OVZ,using non-bridged virtual Ethernet,and this type of setup is clean and simple.
I have experimented with IPv6/OVZ/Ethernet bridging,and also ran into issues,using IPv6 with parallel bridges vs. source-route.
Using an interface other than source-route,for a IPv6 Ethernet bridge,caused link-local breakdowns.
It's not uncommon to use a parallel interface,for a IPv4 Ethernet bridge.
Proxy_ARP,is only needed for the bridge.
In using this type setup with IPv6,sans Proxy_ARP,the VE was reachable,but not the other way around.
Once I try to "ping6" the Node source-route interface from a VE,link-local is lost on all bridged interfaces,including Ethernet bridge.
This may be due to my part,in the way the network configurations was setup.
The network daemon,did not initialize the VETH interfaces.
They were set to;
ONBOOT=no
This kept the bogus "boot error" messages off the Node,where the VETH interface was not found,and was initialized by the vz daemon.
This presented no problems with IPv4.
Once I set this back to;
ONBOOT=yes
and let the network daemon initialize the interface,link-local would come back on the VETH interfaces.
Removing the physical interface from the bridge,and restarting
the interface(s),I would have link-local back on the bridge and
physical interface.
These,was always set to ONBOOT=yes.
Why link-local is lost,is a mystery to me.
Since IPv4 uses ARP and IPv6 uses NDP,enabling Proxy_NDP,did not
help in this type of bridge setup.
I simply removed the parallel bridge configuration,and created a Ethernet bridge using the source-route interface,and IPv6 over bridged Ethernet works perfect
And as you stated,we do use DHCP for IPv4,to provide routing
info and DNS,and this will be added later via DHCPv6.
I'm going to try a couple of things from your post,on our test network.
I'll let you know how it went.
Thanks for your post.
Regards
Lars Bailey
|
|
|