The primary reason for this patch is to be able to export the FIP address information via BGP eVPN. Our BGP eVPN extensions make use of the L2POP framework to export MAC/IP information and this patch ensures that the FIP addresses are included in the exported information. In addition to the BGP eVPN functionality, this patch also avoids broadcast for scenarios when two VM instances, residing on different networks, communicate via their respective FIP addresses. Regards, Allain Allain Legacy, Software Developer, Wind River direct 613.270.2279 fax 613.492.7870 skype allain.legacy 350 Terry Fox Drive, Suite 200, Ottawa, Ontario, K2K 2W5 [WIND]<http://www.windriver.com/> From: Xu, Chenjie [mailto:chenjie.xu@intel.com] Sent: Tuesday, October 23, 2018 4:19 AM To: Peters, Matt Cc: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Request use cases for RFE(patch 9f926a5) for StartlingX upstreaming Hi Matt, For patch 9f926a5, the RFE "Add l2pop support for floating ip resources" has been drafted and is under internal reviewing for now. This RFE adds (host, mac_address, floating_ip_address) to l2pop fdb. 1. For non-DVR floating ip resources, the mac_address belongs to router_gateway port which belongs to the router related to the specific floating ip. As following: mac_address: router_gateway port's mac_address --------------------- router -------- floating ip 2. For DVR floating ip resources, the mac_address belongs to floatingip_agent_gateway port which belongs to the router related to the specific floating ip. As following: mac_address: floatingip_agent_gateway port's mac_address -------- router -------- floating ip I'm wondering in what use case these information will be used to avoid the broadcast in mac learning and ARP resolution . Could you please provide some use cases? Best Regards, Xu, Chenjie