Hi Nikhil,
I suspect the table-d/fib-index is a red herring. From the trace, this is the
echo response sent back from VPP:
03:50:52:603867: VirtualFuncEthernet0/6/0-output
VirtualFuncEthernet0/6/0.900
IP4: fa:16:3e:78:ca:96 -> fa:16:3e:08:4c:1d 802.1q vlan 900
ICMP: 50.50.50.50 -> 20.20.14
Hi Nikhil
Share me all CLI commands which you have triggered to vpp. I am sure you
forgot to set your interface to your IP table.
*"set interface ip table "*
Use this and enjoy the weekend
*//MJ*
*Regards*,
Mrityunjay Kumar.
Mobile: +91 - 9731528504
On Thu, Mar 11, 2021 at 11:43 PM ni
hI Nikhil,
I don't know why the VM did not receive icmp reply packet, But I am sure it is not caused by fib because icmp reply, because the packet will not go through the ip4-lookup again.The reason you see "fib 0" is because the value of sw_if_index[VLIB_RX] was set to vnet_
Hi Nikhil,
If your client and server are attached to the same vpp instance, data/segments
never make it into vpp. Instead, during the connect, after vpp detects that the
two endpoints are both attached locally it sets up the session buffers (fifos)
in a piece of shared memory that’s mapped by
