From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f43.google.com ([74.125.83.43]:41913 "EHLO mail-pg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932240AbeCLU0T (ORCPT ); Mon, 12 Mar 2018 16:26:19 -0400 Received: by mail-pg0-f43.google.com with SMTP id w17so2925637pgq.8 for ; Mon, 12 Mar 2018 13:26:18 -0700 (PDT) Subject: Re: "wrong" ifindex on received VLAN tagged packet? To: Lawrence Kreeger Cc: netdev@vger.kernel.org References: From: David Ahern Message-ID: <0448b3dd-d60f-b5f2-f833-fa63476f4a80@gmail.com> Date: Mon, 12 Mar 2018 13:26:15 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: On 3/6/18 5:27 PM, Lawrence Kreeger wrote: > Using ETH_P_ALL instead of ETH_P_802_2, is causing mstpd to get 3 > copies of the same BPDU. One from eth0, one from eth0.100, and > another from vlan100 (the bridge). > mstpd will drop the one from vlan100, but since there is also an > instance of spanning tree running on the native VLAN, there is now no > way to differentiate BPDUs coming in > tagged vs untagged because they all show up with eth0. So, there > isn't some kernel knob to get the BPDUs to only come from eth0.100? not that I am aware of. You could bind your socket or program to eth0.100, but I suspect you actually have more than the one vlan interface coming into the bridge that you want to snoop.