lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7b8243a3-9976-484c-a0d0-d4f3debbe979@lunn.ch>
Date: Thu, 4 May 2023 21:21:58 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Fabio Estevam <festevam@...il.com>
Cc: Vladimir Oltean <olteanv@...il.com>,
	Florian Fainelli <f.fainelli@...il.com>,
	Steffen Bätz <steffen@...osonix.de>,
	netdev <netdev@...r.kernel.org>
Subject: Re: mv88e6320: Failed to forward PTP multicast

On Thu, May 04, 2023 at 03:39:17PM -0300, Fabio Estevam wrote:
> Hi,
> 
> We are running kernel 6.1.26 on an imx8mn-based board with a Marvell
> mv88e6320 switch.



> 
> eth1 and eth2 are the mv88e6320 ports. We connect a PTP sync source to eth1
> and we notice that after setting up vlan_filtering on a bridge, the PTP
> packets are no longer forwarded by the switch.
> 
> Below is the networking setup.
> 
> It does not matter if we assign an IP and sniff on the br0 or on the veth2,
> PTP multicast is not appearing. Some multicast like ARP does come through.
> Flags on br0: multicast_snooping = 1, mcast_flood  =1, mcast_router = 1

Do you see the PTP traffic on eth1?

What MAC address is the PTP traffic using? Is it a link local MAC
address? There are some range of MAC addresses which you are not
supposed to forward across a bridge. e.g. you don't forward BPDUs.
Take a look at br_handle_frame(). Maybe you can play with
group_fwd_mask.

	 Andrew


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ