From: Vladimir Oltean <olteanv@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
tobias@waldekranz.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, 10 May 2023 21:28:26 +0300 [thread overview]
Message-ID: <20230510182826.pxwiauia334vwvlh@skbuf> (raw)
In-Reply-To: <CAOMZO5DSSQY5fa5vTmDbCxu1x2ZRdyB2kTqrkw5bRg94_-34zg@mail.gmail.com>
Hi Fabio,
On Wed, May 10, 2023 at 11:05:46AM -0300, Fabio Estevam wrote:
> On Fri, May 5, 2023 at 10:02 AM Andrew Lunn <andrew@lunn.ch> wrote:
>
> > I'm not too familiar with all this VLAN stuff. So i could be telling
> > your wrong information.... 'self' is also importing in way's i don't
> > really understand. Vladimir and Tobias are the experts here.
>
> Vladimir and Tobias,
>
> Would you have any suggestions as to how to allow PTP multicast to be
> forwarded when
> vlan_filtering is active?
>
> The whole thread is at:
> https://lore.kernel.org/netdev/5cd6a70c-ea13-4547-958f-5806f86bfa10@lunn.ch/T/#m6453e569a98478bf5bddf09895393c3a52b91727
>
> Thanks,
>
> Fabio Estevam
I checked out the v6.1.26 tag from linux-stable and I was able to
synchronize 2 stations attached to my Turris MOX (Marvell 6190) with
this commands: sudo ptp4l -i eth0 -4 -m
(also I was able to synchronize a third station behind a mvneta bridge
port foreign to the MV88E6190, using software forwarding)
My bridge configuration is VLAN-aware. FWIW, I'm using vlan_default_pvid
1000, but it should not make a difference.
In a bridging configuration where there are only 2 ports in the bridge
PVID (1 source and 1 destination), could you please run the following
command from a station attached to one of the Marvell switch ports:
board # ethtool -S lanX | grep -v ': 0'
station # mausezahn eth0 -B 224.0.1.129 -c 1000 -t udp "dp=319"
board # ethtool -S lanX | grep -v ': 0'
and tell me which counters increment?
I am also curious whether there is any difference to your setup between:
ip link add br0 type bridge
ip link set br0 type bridge vlan_filtering 1 # dynamic toggling of VLAN awareness
and:
ip link add br0 type bridge vlan_filtering 1 # static creation of VLAN-aware bridge
I've tested both forms on my setup, and both work. Who knows, maybe
something happens differently on your particular kernel, or with your
particular switch model.
Is it vanilla v6.1.26 or something else?
next prev parent reply other threads:[~2023-05-10 18:28 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 [this message]
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
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=20230510182826.pxwiauia334vwvlh@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