[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5AQtL1BNk2sm2v=c5fLbukkZSi6HSJXexp4QB4JjAyw-g@mail.gmail.com>
Date: Tue, 16 May 2023 15:10:00 -0300
From: Fabio Estevam <festevam@...il.com>
To: Tobias Waldekranz <tobias@...dekranz.com>
Cc: Andrew Lunn <andrew@...n.ch>, 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
Hi Tobias,
On Thu, May 11, 2023 at 8:56 AM Tobias Waldekranz <tobias@...dekranz.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.
Thanks a lot!
Fabio Estevam
Powered by blists - more mailing lists