Since there is a workaround, and this is only regarding the Linux Bridge agent, which is not actively maintained, I'm closing this since it doesn't seem like it will be fixed.
** Changed in: neutron Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1661717 Title: [linuxbridge agent] vm can't communicate with router with l2pop Status in neutron: Won't Fix Bug description: When both l2pop and arp_responder enabled for linuxbridge agent, vxlan device is created in "proxy" mode. In this mode, ARP entry must be statically added by linuxbridge agent. Because of [1], l2pop driver won't notify HA router port, so linuxbridge agent can't add ARP entry for router port. As there is no router ARP entry, vxlan device is dropping ARP request packets from vm(destined to router), making vm unable to communicate with router. This issue is only on linuxbridge agent and not on ovs agent. Temporary solution for vm to communicate with HA router is to disable arp_responder when l2pop is enabled. If the users need both arp_responder and l2pop features for linuxbridge agent, we need an implementation which decouples them i.e https://bugs.launchpad.net/neutron/+bug/1518392 [1] https://review.openstack.org/#/c/255237/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1661717/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp