Actually I'm also adding the instance IPs into ndp_proxy.
However, this seems to be not sufficient as we also need NDP resolution for the reply from the instance to the outside world.
So we would need another entry in ndp_proxy for the next-hop of the instance.
I tested that with an instance on a provider network and the BGP driver (not modified) in use, while ARP for IPv4 works fine, NDP for IPv6 does not.
Furthermore, I saw in the code [1] that NDP entries are only created for specific port types, not for VM_VIF ports.
Do we require a special instance configuration to make this work?
If not, maybe you can confirm that behavior in your environment?
Hey Tomas, thanks for your reply.
Actually I'm also adding the instance IPs into ndp_proxy.
However, this seems to be not sufficient as we also need NDP resolution for the reply from the instance to the outside world.
So we would need another entry in ndp_proxy for the next-hop of the instance.
I tested that with an instance on a provider network and the BGP driver (not modified) in use, while ARP for IPv4 works fine, NDP for IPv6 does not.
Furthermore, I saw in the code [1] that NDP entries are only created for specific port types, not for VM_VIF ports.
Do we require a special instance configuration to make this work?
If not, maybe you can confirm that behavior in your environment?
[1] https:/ /opendev. org/openstack/ ovn-bgp- agent/src/ commit/ e697e350af158de 68fbc4f52e784d8 d4a8c922ab/ ovn_bgp_ agent/drivers/ openstack/ ovn_bgp_ driver. py#L567