netdev - Re: mv88e6320: Failed to forward PTP multicast

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: <41d7d1e8-19b8-4025-a1eb-0fbb0f54fe15@lunn.ch>
Date: Wed, 17 May 2023 19:07:28 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Tobias Waldekranz <tobias@...dekranz.com>,
	Fabio Estevam <festevam@...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

> Slightly unrelated to the original topic and probably completely
> unrelated to Fabio's actual issue.
> 
> I'm completely inapt when it comes to IP multicast. Tobias, does the
> fact that br0 have mcast_router 1 mean that the CPU port should be a
> recipient of all multicast traffic, registered or unregistered?

It is a long time since i did much with multicast. But my
understanding is that a multicast router should be taking part in
IGMP. If there is a group member on the other side of the gateway, the
router should indicate it has interest in the group so traffic flows
to it. It can then forward the traffic between its multicast
interfaces, based on that interest.

	Andrew