In your packet capture I cannot see any NA messages following the NS messages.
Which routes are configured in the instance itself?
Do you know from where your instances gets their L2 resolution?
Can you share your proxy_ndp configuration?
14: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
link/ether 7e:e8:52:8b:44:4b brd ff:ff:ff:ff:ff:ff
inet 169.254.0.1/32 scope global br-ex
valid_lft forever preferred_lft forever
inet6 fd53:d91e:400:7f17::1/128 scope global
valid_lft forever preferred_lft forever
To test with the BGP driver I had reconfigured a single node, I will now try to reconfigure the whole cluster. Should not make any difference, but who knows...
That's interesting.
In your packet capture I cannot see any NA messages following the NS messages.
Which routes are configured in the instance itself?
Do you know from where your instances gets their L2 resolution?
Can you share your proxy_ndp configuration?
In my scenario proxy_arp/ndp is enabled:
net.ipv4.ip_forward = 1 conf.all. forwarding = 1 conf.br- ex.proxy_ arp = 1 conf.br- ex.proxy_ ndp = 1
net.ipv6.
net.ipv4.
net.ipv6.
br-ex has addresses assigned:
14: br-ex: <BROADCAST, MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 400:7f17: :1/128 scope global
link/ether 7e:e8:52:8b:44:4b brd ff:ff:ff:ff:ff:ff
inet 169.254.0.1/32 scope global br-ex
valid_lft forever preferred_lft forever
inet6 fd53:d91e:
valid_lft forever preferred_lft forever
To test with the BGP driver I had reconfigured a single node, I will now try to reconfigure the whole cluster. Should not make any difference, but who knows...