Different behavior wrt VRF and no VRF - packet Tx

2021-04-15 Thread Bala Sajja
When interfaces are not part of VRF and below ip address config is done on these interfaces, ping with -I (interface) option, we see packets transmitting out of the right interfaces. ip addr add 2.2.2.100 peer 1.1.1.100/32 dev enp0s3 ip addr add 2.2.2.100 peer 1.1.1.100/32 dev enp0s8 ping 1.

Re: Different behavior wrt VRF and no VRF - packet Tx

2021-04-15 Thread Bala Sajja
Forgot to mention Linux version: Linux DR1 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux On Thu, Apr 15, 2021 at 12:45 PM Bala Sajja wrote: > > When interfaces are not part of VRF and below ip address config is > done on these interfaces, ping with -I (interface) option,

Re: Different behavior wrt VRF and no VRF - packet Tx

2021-04-15 Thread David Ahern
On 4/15/21 12:15 AM, Bala Sajja wrote: > When interfaces are not part of VRF and below ip address config is > done on these interfaces, ping with -I (interface) option, we see > packets transmitting out of the right interfaces. > > ip addr add 2.2.2.100 peer 1.1.1.100/32 dev enp0s3 > ip addr ad

Re: Different behavior wrt VRF and no VRF - packet Tx

2021-04-15 Thread Bala Sajja
Hi David, please find the ip link show output(for ifindex) and ping and its corresponding perf fib events output. OIF seems MGMT(ifindex 5) always, not enslaved interfaces ? ip link show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00

Re: Different behavior wrt VRF and no VRF - packet Tx

2021-04-18 Thread David Ahern
On 4/15/21 8:57 PM, Bala Sajja wrote: >please find the ip link show output(for ifindex) and ping and > its corresponding perf fib events output. OIF seems MGMT(ifindex 5) > always, not enslaved interfaces ? that is the reason it does not work.