| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAE_QS3fUAerYjK2FEoigdqyvpezo2XRzjoqAP-a-ETVQJ_rJvg@mail.gmail.com> Date: Thu, 15 Apr 2021 12:47:21 +0530 From: Bala Sajja <bssajja@...il.com> To: netdev@...r.kernel.org Subject: Re: Different behavior wrt VRF and no VRF - packet Tx 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 <bssajja@...il.com> 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 add 2.2.2.100 peer 1.1.1.100/32 dev enp0s8 > > ping 1.1.1.100 -I enp0s3 , packet always goes out of enp0s3 > ping 1.1.1.100 -I enp0s8, packet always goes out of enp0s8 > > When interfaces are enslaved to VRF as below and ip are configured > on these interfaces, packets go out of one interface only. > > ip link add MGMT type vrf table 1 > ip link set dev MGMT up > ip link set dev enp0s3 up > ip link set dev enp0s3 master MGMT > ip link set dev enp0s8 up > ip link set dev enp0s8 master MGMT > ip link set dev enp0s9 up > > 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.1.1.100 -I enp0s3 , packet always goes out of enp0s3 > ping 1.1.1.100 -I enp0s8, packet always goes out of enp0s3 > > > Regards, > Bala.
Powered by blists - more mailing lists