Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-09-07 Thread D'Souza, Nelson
Thanks David and Ido, for finding the root-cause for bridge Rx packets getting dropped, also for coming up with a patch. Regards, Nelson On 9/7/18, 9:09 AM, "David Ahern" wrote: On 9/7/18 9:56 AM, D'Souza, Ne

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-09-05 Thread D'Souza, Nelson
Hi David, Just following up would you be able to confirm that this is a Linux VRF issue? Also, how do I log a VRF related defect to ensure this gets resolved in a subsequent release. Thanks, Nelson On 8/2/18, 4:12 PM, "D'Souza, Nelson" wrote: Hi David, Turns o

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-08-02 Thread D'Souza, Nelson
/27/18, 4:29 PM, "D'Souza, Nelson" wrote: David, With Ubuntu 18.04.1 (kernel 4.15.0-29) pings sent out on test-vrf and br0 are successful. # uname -rv 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 # ping -c 1 -I test-vrf 172.16.2.2 pi

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-27 Thread D'Souza, Nelson
17.10.1 (kernel 4.13.0-21) pings on only test-vrf are successful. Pings on br0 are not successful. So it seems like there maybe a change in versions after 4.13.0-21 that causes pings on br0 to pass. Nelson On 7/25/18, 5:35 PM, "D'Souza, Nelson" wrote: David, I

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-25 Thread D'Souza, Nelson
lable as a text file in the /boot directory." Would you be able to provide this? Nelson On 7/25/18, 5:35 PM, "D'Souza, Nelson" wrote: David, I tried out the commands on an Ubuntu 17.10.1 VM. The pings on test-vrf are successful, but the pings on br0

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-25 Thread D'Souza, Nelson
tistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1022ms Please let me know if I should try a different version. Nelson On 7/24/18, 9:08 AM, "D'Souza, Nelson" wrote: It's strange that enslaving eth1 -> br0 -> test-vrf does not work, but enslaving eth1-

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-24 Thread D'Souza, Nelson
It's strange that enslaving eth1 -> br0 -> test-vrf does not work, but enslaving eth1->test-vrf works fine. Nelson On 7/24/18, 8:58 AM, "D'Souza, Nelson" wrote: Thank you David, really appreciate the help. Most likely something specific to my environment.

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-24 Thread D'Souza, Nelson
On 7/23/18 7:43 PM, D'Souza, Nelson wrote: > I copy and pasted the configs onto my device, but pings on test-vrf do not work in my setup. > I'm essentially seeing the same issue as I reported before. > > In this case, pings sent out on test-vrf (host ns) are

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-23 Thread D'Souza, Nelson
quest, id 19513, seq 0, length 64 18:34:13.205278 IP 172.16.2.2 > 172.16.1.1: ICMP echo reply, id 19513, seq 0, length 64 2 packets captured 2 packets received by filter 0 packets dropped by kernel Thanks, Nelson On 7/23/18, 3:00 PM, "David Ahern" wrote: On 7/20/18 1:03 PM,

Re: [**EXTERNAL**] Re: DNAT with VRF support in Linux Kernel

2018-07-20 Thread D'Souza, Nelson
th dev ==mgmt wouldn't match as well? Nelson On 7/19/18, 8:42 PM, "David Ahern" wrote: On 7/19/18 7:52 PM, D'Souza, Nelson wrote: > Hi, > > > > I'm seeing a VRF/Netfilter related issue on a system running a 4.14.52 > Linux kernel. >

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-20 Thread D'Souza, Nelson
:~# ip link show vrf mgmtvrf 16: mgmtbr0: mtu 1500 qdisc noqueue master mgmtvrf state UP mode DEFAULT group default qlen 1000 link/ether c0:56:27:90:4f:75 brd ff:ff:ff:ff:ff:ff Thanks, Nelson On 7/20/18, 12:11 PM, "David Ahern" wrote: On 7/20/18 1:03 PM, D'Souza, Nelson wrote

Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge

2018-07-20 Thread D'Souza, Nelson
al logs. Thanks, Nelson On 7/19/18, 8:37 PM, "David Ahern" wrote: On 7/19/18 8:19 PM, D'Souza, Nelson wrote: > Hi, > > > > I'm seeing the following issue on a system running a 4.14.52 Linux kernel. > > > > W