[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YewoABDa0/u1f6tg@lunn.ch>
Date: Sat, 22 Jan 2022 16:51:28 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Luiz Angelo Daros de Luca <luizluca@...il.com>
Cc: Vladimir Oltean <olteanv@...il.com>,
Frank Wunderlich <frank-w@...lic-files.de>,
Alvin Šipraga <ALSI@...g-olufsen.dk>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"vivien.didelot@...il.com" <vivien.didelot@...il.com>,
"f.fainelli@...il.com" <f.fainelli@...il.com>,
"arinc.unal@...nc9.com" <arinc.unal@...nc9.com>
Subject: Re: [PATCH net-next v4 11/11] net: dsa: realtek: rtl8365mb: multiple
cpu ports, non cpu extint
> trap_port seems to be where the switch will send any packet captured
> from LAN ports. There are a couple of situations it will be used like:
> 1) untagged or unmatched vlan packets (if configured to do so)
> 2) some multicasting packets (Reserved Multicast Address), for some
> cases like capturing STP or LACP
> 3) IGMP and 802.1X EAPOL packets
> 4) Switch ACL rules that could match a packet and send it to the trap port.
>
> In my early tests, I only saw some IGMP packets trapped to CPU. I also
> do not know how important they are.
STP is important for detecting loops in the ethernet traffic and
blocking ports. The linux software bridge will want to see these
packets.
IGMP will become important when you implement multicast support in the
switch. It will allow you to optimize the distribution of multicast to
only ports which have expressed an interest in receiving the group.
Currently we don't have any switch driver making use of 802.1x. It is
something which many switches have, but so far nobody has spent the
time to implement an interface to wpa_supplicant etc.
Andrew
Powered by blists - more mailing lists