Hi Murty, ARP works the same way even when using MH-BGP :)
Your peer is not directly connected, therefore you ARP for the nexthop, that's the target address. The source address comes from the interface on which the nexthop is attached, I.e the one on which the ARP is sent. this is not the loopback (no peers are ever attached to a loopback). The source address is therefore the one applied to the physical interface through which the nexthop is attached, hence to the receiving peer it is always an address within the interface's connected subnet. I would suggest you experiment with how you are adding the static route to see if it changes the way the ARPs are generated. /neale tpyed by my fat tumhbs ________________________________ From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> on behalf of Satya Murthy <satyamurthy1...@gmail.com> Sent: Friday, August 21, 2020 7:52:28 AM To: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] ARP resolution from non-connected IP Neale /Ben, We already have a static route to reach the peer. Even after that, we are getting this error. And this error is as per the VPP's ARP code. It's not allowing the ARP-REQUEST from a non-connected source IP. If we dont know allow this, I am not 100% sure how multihop-BGP peering kind of scenarios really work. In MH-BGP, the peer will be running on a loopback address and will try to reach a peer loopback. In this scenario, the ARP request can have the BGP-loopback address as the source address. How will it really work ? Any inputs pls. -- Thanks & Regards, Murthy
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17279): https://lists.fd.io/g/vpp-dev/message/17279 Mute This Topic: https://lists.fd.io/mt/76285682/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
