OpenVZ Forum


Today's Messages (off)  | Unanswered Messages (on)

Forum: Support
 Topic: Weird IPv6 Native
Weird IPv6 Native [message #53462] Fri, 09 November 2018 02:13
blackstormy1804 is currently offline  blackstormy1804
Messages: 2
Registered: June 2018
Location: London
Junior Member
From: *vnpt.vn
So lets start with what the HN is etc:

Ubuntu 8.04 64bit server
Kernel = 2.6.24-21-openvz
{EDIT} Forgot to mention I use VENET not VETH interfaces on all OpenVZ machines involved

Symptoms:
Using native IPv6, I cannot allocate addresses out of the same /64 I use on the HN. I find that I have to route a second /64 allocation through the first in order for the VEs to get native connectivity. This smells like IPv6 forwarding is not working correctly, except it does work if there is a static route in place on the router. This is not the case with my CentOS 5.2 based OpenVZ machines, only Ubuntu.

Meaning:
2001:470:0:c8::1/64 is on the router's interface
2001:470:0:c8::2/64 is configured on eth0 on the server
sysctl is configured correctly to allow IPv6 packet forwarding

2001:470:0:c8::3/64 (through the end of the range) cannot be reached when configured on a VE on the Ubuntu system. It can on CentOS.

However when I statically route a second allocation (in this case 2001:470:0:c9::/64) through 2001:470:0:c8::2/64 on my router and I assign 2001:470:0:c9::1/64 (through the end of the range) to a VE, IPv6 forwarding seems to work without issue.

Thanks.



Current Time: Wed Nov 14 15:37:53 GMT 2018