> -----Original Message----- > From: Intel-wired-lan <[email protected]> On Behalf Of > Simon Horman > Sent: Thursday, February 20, 2025 3:58 PM > To: Zaremba, Larysa <[email protected]> > Cc: Nguyen, Anthony L <[email protected]>; intel-wired- > [email protected]; Kitszel, Przemyslaw <[email protected]>; > Andrew Lunn <[email protected]>; David S. Miller > <[email protected]>; Eric Dumazet <[email protected]>; Jakub > Kicinski <[email protected]>; Paolo Abeni <[email protected]>; > [email protected]; [email protected]; Michal Swiatkowski > <[email protected]>; Pacuszka, MateuszX > <[email protected]> > 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 <[email protected]> > > > > 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 <[email protected]> > > Co-developed-by: Larysa Zaremba <[email protected]> > > Signed-off-by: Larysa Zaremba <[email protected]> > > Reviewed-by: Michal Swiatkowski <[email protected]> > > Reviewed-by: Simon Horman <[email protected]>
Tested-by: Rafal Romanowski <[email protected]>
