ML2: Consider enabling arp_responder
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Neutron API Charm |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Enabling arp_responder would allow OVS to avoid sending broadcast traffic across the whole overlay L2 for ARP requests.
Using VIPs on the overlay with allowed-
arp_responder is disabled by default:
https:/
Using L2 population does not enable it:
https:/
# ...
Linux bridge-related note:
https:/
"The responder is now disabled to improve compatibility with the allowed-
ARP tables to make note of:
* VM ARP tables;
* qrouter (legacy, l3ha, non-distributed) namespace ARP table;
* qrouter namespace (dvr);
* snat namespace (dvr).
ARP tables in network namespaces will be used for ARP resolution when traffic arrives from a different subnet (i.e. multiple networks attached to one router or traffic coming from a provider network or fip namespace).
With DVR, PERMANENT ARP table entries are used which also needs to be considered:
https:/
https:/
Changed in charm-neutron-api: | |
status: | New → Triaged |
importance: | Undecided → Medium |
importance: | Medium → Wishlist |