In L2 mode, the ethernet interface will be put in promiscuous mode to receive all packets on the wire. In L3 mode, it will only receive packets whose destination MAC is that of the interface. What you observe is the expected behavior. -John
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Yuliang Li Sent: Tuesday, December 05, 2017 9:59 AM To: Neale Ranns (nranns) <nra...@cisco.com> Cc: vpp-dev@lists.fd.io Subject: Re: [vpp-dev] Bug? Actually there is no packet going to int2. When in L3 mode, dpdk-input does not get any packet from int2. But just by changing it to L2 mode, dpdk-input gets exactly the same packet from int2 as from int1. At dpdk-input, whether the interface is L2 or L3 should not affect the packet it gets. The check (e.g., ethernet-input) is after the dpdk-input. That's why I think it may be a bug. (e.g., somehow the memory of the frame at int1 and int2 are the same, so the dpdk-input puts the same packet to the next node twice. Just my guess, may be wrong). On Tue, Dec 5, 2017 at 4:05 AM, Neale Ranns (nranns) <nra...@cisco.com<mailto:nra...@cisco.com>> wrote: By ‘receive’ in this context, I assume you mean it accepts the packet that has arrived on the wire. As opposed to the fact that the packet did indeed arrive at that interface - clearly it is not the receiving device that influences which packets arrive at which interfaces. So, let me bounce this back to you. Under what circumstances do L3 and L2 ports accept a packet? Regards, neale From: <vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>> on behalf of Yuliang Li <yuliang...@yale.edu<mailto:yuliang...@yale.edu>> Date: Tuesday, 5 December 2017 at 04:55 To: "vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>" <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: [vpp-dev] Bug? Hi, I am using vpp v18.01-rc0~160-ge13c799 (show version in vppctl). I feel I find a bug. I have two physical interfaces TenGigabitEthernet5/0/0 (int1) and TenGigabitEthernet5/0/1 (int2). Normally, if I send traffic (from another server) to int1, I expect int2 should NOT receive the traffic. This is true when int2 is in l3 mode. However, if I set int2 to l2 mode (e.g., set interface l2 bridge TenGigabitEthernet5/0/1 2), int2 will receive the same traffic as int1 does. This problem happens no matter int1 is in l2 or l3 mode. I use the trace to confirm that int2 receives the same traffic as int1 does. Does anyone know this problem? Thanks, -- Yuliang Li PhD student Department of Computer Science Yale University -- Yuliang Li PhD student Department of Computer Science Yale University
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
