netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: "Arun.Ramadoss@microchip.com" <Arun.Ramadoss@microchip.com>
Cc: "martin.blumenstingl@googlemail.com" 
	<martin.blumenstingl@googlemail.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
	"andrew@lunn.ch" <andrew@lunn.ch>,
	"vivien.didelot@gmail.com" <vivien.didelot@gmail.com>,
	"petrm@nvidia.com" <petrm@nvidia.com>,
	"idosch@nvidia.com" <idosch@nvidia.com>,
	"linux@rempel-privat.de" <linux@rempel-privat.de>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"hauke@hauke-m.de" <hauke@hauke-m.de>,
	Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Woojung.Huh@microchip.com" <Woojung.Huh@microchip.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [RFC PATCH net-next 3/3] net: dsa: never skip VLAN configuration
Date: Thu, 14 Jul 2022 15:12:10 +0000	[thread overview]
Message-ID: <20220714151210.himfkljfrho57v6e@skbuf> (raw)
In-Reply-To: <f19a09b67d503fa149bd5a607a7fc880a980dccb.camel@microchip.com>

Hi Arun,

On Thu, Jul 14, 2022 at 10:46:02AM +0000, Arun.Ramadoss@microchip.com wrote:
> Hi Vladimir,
> We couldn't able to setup the selftests and failed during installation
> of packages. In the mean time, We tried the following things
> 
> Setup - Host1 --> lan1 --> lan2 --> Host2. Packet transmitted from
> Host1 and received by Host2.
> 
> Scenario-1: Vlan aware system and both lan1 & lan2 are in same vid
> ip link set dev br0 type bridge vlan_filtering 1
> bridge vlan add dev lan2 vid 10 pvid untagged
> bridge vlan add dev lan1 vid 10 pvid untagged
> 
> Packet transmitted from Host1 with vid 10 is received by the Host2.
> Packet transmitted from Host1 with vid 5 is not received by the Host2.
> 
> Scenario-2: Vlan unaware system 
> ip link set dev br0 type bridge vlan_filtering 0
> 
> Now, irrespective of the vid, the packets are received by Host2
> Packet transmitted from Host1 with vid 10 is received by the Host2.
> Packet transmitted from Host1 with vid 5 is  received by the Host2.
> 
> Whether the above approach is correct or do we need to test anything
> further.
> 
> Thanks
> Arun 

The above is correct to the extent that it is a valid configuration,
but isn't what my pvid_change() selftest was intended to capture.

The pvid_change() selftest from patch 1/3
https://patchwork.kernel.org/project/netdevbpf/patch/20220705173114.2004386-2-vladimir.oltean@nxp.com/
checks that VLAN-unaware forwarding still takes place after this array
of operations:

ip link add br0 type bridge vlan_filtering 0 # notice the 0 instead of 1
ip link set $swp1 master br0
ip link set $swp2 master br0
bridge vlan add vid 3 dev $swp1 pvid untagged # notice how VID 3 is absent on $swp2

If you let me know if this works, I can continue and resend this patch
set while you figure out the kselftest setup issues.

  reply	other threads:[~2022-07-14 15:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:31 [RFC PATCH net-next 0/3] Delete ds->configure_vlan_while_not_filtering Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 1/3] selftests: forwarding: add a vlan_deletion test to bridge_vlan_unaware Vladimir Oltean
2022-07-07 12:13   ` Ido Schimmel
2022-07-07 13:34   ` Martin Blumenstingl
2022-07-07 13:45     ` Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 2/3] net: dsa: ar9331: remove ds->configure_vlan_while_not_filtering Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 3/3] net: dsa: never skip VLAN configuration Vladimir Oltean
2022-07-06 10:51   ` Arun.Ramadoss
2022-07-06 11:12     ` Vladimir Oltean
2022-07-06 16:33   ` Martin Blumenstingl
2022-07-06 16:45     ` Vladimir Oltean
2022-07-06 19:57       ` Martin Blumenstingl
2022-07-07 22:31         ` Vladimir Oltean
2022-07-08 10:00           ` Martin Blumenstingl
2022-07-08 12:09             ` Vladimir Oltean
2022-07-08 22:27               ` Martin Blumenstingl
2022-07-14 10:46                 ` Arun.Ramadoss
2022-07-14 15:12                   ` Vladimir Oltean [this message]
2022-07-15  9:23                     ` Arun.Ramadoss
2022-07-15 15:26                       ` Vladimir Oltean
2022-07-18 14:34                         ` Arun.Ramadoss
2022-07-18 16:24                           ` Vladimir Oltean
2022-07-26 15:10                             ` Arun.Ramadoss
2022-07-26 17:21                               ` Vladimir Oltean
2022-09-12 15:30                                 ` Arun.Ramadoss
2022-09-12 15:42                                   ` Vladimir Oltean
2022-09-13 10:57                                     ` Arun.Ramadoss
2022-09-13 15:09                                       ` Vladimir Oltean
2022-07-06 20:04       ` Hauke Mehrtens
2022-07-07 22:54         ` Vladimir Oltean

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220714151210.himfkljfrho57v6e@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=Arun.Ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=vivien.didelot@gmail.com \
    --cc=xiaoliang.yang_1@nxp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).