OpenVZ Forum


Home » General » Support » VZ7 routed IPv6
VZ7 routed IPv6 [message #52889] Wed, 12 July 2017 12:53
wyckaoo is currently offline  wyckaoo
Messages: 4
Registered: November 2016
Junior Member
From: *iv.lt
Hi,

Im trying to set up routed IPv6 with VZ7 VMs. Everything works fine while network in node is configured with one physical interface. If network works in bonding, NDP proxy is added not to bond0 interface but to physical interfaces.

E.g:
Node has two physical intefaces "enp2s0f0" and "enp2s0f1", interfaces are bonded into bond0, node IP adresses are binded to bond0, adding IPv6 to VM:
prlctl set test.vm --device-set net0 --ipadd 2a02:1234:4321:6f1a::9

VZ adds proxy to physical interfaces but not to bond interface:
ip neigh show proxy:
2a02:1234:4321:6f1a::9 dev enp2s0f1 proxy
2a02:1234:4321:6f1a::9 dev enp2s0f0 proxy

So VMs IP can not be resolved via NDP query. To fix VM IPv6 connectivity, we have to add proxy on bond interafce manualy:
ip -6 neigh add proxy 2a02:1234:4321:6f1a::9 dev bond0

ip neigh show proxy:
2a02:1234:4321:6f1a::9 dev bond0 proxy
2a02:1234:4321:6f1a::9 dev enp2s0f1 proxy
2a02:1234:4321:6f1a::9 dev enp2s0f0 proxy


But this is workaround for problem, VZ should automaticaly add proxy to bon0 interface.

Is there any option to change prlctl behavior? Or it is VZ7 bug?


[Updated on: Thu, 13 July 2017 05:43]

Report message to a moderator

Previous Topic: OpenVZ 7 - Problem with ipv6 default route after starting routed VM
Next Topic: Unable to start init, probably incorrect template
Goto Forum:
  


Current Time: Mon Sep 25 00:43:14 GMT 2017