From: Vladimir Oltean <olteanv@gmail.com>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Fabio Estevam" <festevam@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Steffen Bätz" <steffen@innosonix.de>,
netdev <netdev@vger.kernel.org>
Subject: Re: mv88e6320: Failed to forward PTP multicast
Date: Wed, 17 May 2023 19:53:35 +0300 [thread overview]
Message-ID: <20230517165335.o2hvnz7ymi3nh7sy@skbuf> (raw)
In-Reply-To: <CAOMZO5AQtL1BNk2sm2v=c5fLbukkZSi6HSJXexp4QB4JjAyw-g@mail.gmail.com>
On Tue, May 16, 2023 at 03:10:00PM -0300, Fabio Estevam wrote:
> Hi Tobias,
>
> On Thu, May 11, 2023 at 8:56 AM Tobias Waldekranz <tobias@waldekranz.com> wrote:
>
> > I imagine that if you were to open a socket and add a membership to the
> > group, the packets would reach the CPU. What happens if you run:
> >
> > socat udp-recvfrom:1234,ip-add-membership=224.0.1.129:br0 gopen:/dev/null &
> >
> > Can you see the PTP packets on the CPU now?
>
> Yes, this seems to do the trick!
>
> After adding a membership to the group, I don't see the PTP traffic
> getting blocked anymore on a VLAN-aware configuration.
>
> I will be running more tests, but this seems to be very promising.
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?
next prev parent reply other threads:[~2023-05-17 16:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 18:39 mv88e6320: Failed to forward PTP multicast Fabio Estevam
2023-05-04 19:21 ` Andrew Lunn
2023-05-04 19:40 ` Fabio Estevam
2023-05-04 19:55 ` Andrew Lunn
2023-05-05 11:27 ` Fabio Estevam
2023-05-05 13:02 ` Andrew Lunn
2023-05-05 14:03 ` Fabio Estevam
2023-05-10 14:05 ` Fabio Estevam
2023-05-10 18:28 ` Vladimir Oltean
2023-05-11 11:03 ` Fabio Estevam
2023-05-11 11:46 ` Vladimir Oltean
2023-05-16 14:12 ` Fabio Estevam
2023-05-16 16:29 ` Andrew Lunn
2023-05-17 16:51 ` Vladimir Oltean
2023-05-10 21:34 ` Tobias Waldekranz
2023-05-11 11:16 ` Fabio Estevam
2023-05-11 11:56 ` Tobias Waldekranz
2023-05-16 18:10 ` Fabio Estevam
2023-05-17 16:53 ` Vladimir Oltean [this message]
2023-05-17 17:07 ` Andrew Lunn
2023-05-17 21:42 ` Tobias Waldekranz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230517165335.o2hvnz7ymi3nh7sy@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen@innosonix.de \
--cc=tobias@waldekranz.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox