> -----Original Message----- > From: Intel-wired-lan <intel-wired-lan-boun...@osuosl.org> On Behalf Of > Simon Horman > Sent: Thursday, February 20, 2025 3:58 PM > To: Zaremba, Larysa <larysa.zare...@intel.com> > Cc: Nguyen, Anthony L <anthony.l.ngu...@intel.com>; intel-wired- > l...@lists.osuosl.org; Kitszel, Przemyslaw <przemyslaw.kits...@intel.com>; > Andrew Lunn <andrew+net...@lunn.ch>; David S. Miller > <da...@davemloft.net>; Eric Dumazet <eduma...@google.com>; Jakub > Kicinski <k...@kernel.org>; Paolo Abeni <pab...@redhat.com>; > net...@vger.kernel.org; linux-ker...@vger.kernel.org; Michal Swiatkowski > <michal.swiatkow...@linux.intel.com>; Pacuszka, MateuszX > <mateuszx.pacus...@intel.com> > Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 3/6] ice: receive LLDP on > trusted VFs > > On Fri, Feb 14, 2025 at 09:50:37AM +0100, Larysa Zaremba wrote: > > From: Mateusz Pacuszka <mateuszx.pacus...@intel.com> > > > > When a trusted VF tries to configure an LLDP multicast address, > > configure a rule that would mirror the traffic to this VF, untrusted > > VFs are not allowed to receive LLDP at all, so the request to add LLDP > > MAC address will always fail for them. > > > > Add a forwarding LLDP filter to a trusted VF when it tries to add an > > LLDP multicast MAC address. The MAC address has to be added after > > enabling trust (through restarting the LLDP service). > > > > Signed-off-by: Mateusz Pacuszka <mateuszx.pacus...@intel.com> > > Co-developed-by: Larysa Zaremba <larysa.zare...@intel.com> > > Signed-off-by: Larysa Zaremba <larysa.zare...@intel.com> > > Reviewed-by: Michal Swiatkowski <michal.swiatkow...@linux.intel.com> > > Reviewed-by: Simon Horman <ho...@kernel.org>
Tested-by: Rafal Romanowski <rafal.romanow...@intel.com>
