public inbox for bridge@lists.linux.dev
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: bridge@lists.linux-foundation.org
Subject: Switches which use Linux bridge IGMP/MLD snooping?
Date: Fri, 21 Feb 2025 05:24:51 +0100	[thread overview]
Message-ID: <Z7gAE6vpDVa3Zlt6@sellars> (raw)

Hi,

I would like to get our hackspace more multicast ready. Especially
to do some multicast routing between our hackspace and our
Freifunk wireless mesh network, which thanks to batman-adv and the Linux
bridge is now multicast aware. We do have several donated, older switches
that others outsourced. But I don't trust them to do IGMP/MLD snooping
correctly.

Therefore I'm looking for something that does the multicast
forwarding in hardware but uses the IGMP/MLD snooping from the
Linux bridge in kernelspace and runs on OpenWrt. So I guess I'm
looking for something DSA + switchdev capable, but I guess not
all of them support using IGMP/MLD snooping in kernelspace?
I see some drivers which use DSA's port_mdb_add (b53, bcm_sf2,
lan9303, microchip ksz, mt7530, mv88e6xxx, ocelot felix, qca8k-8xxx,
sja1105) and/or switchdev's switchdev_obj_port_mdb (same as for
DSA plus ksz9477, freescale dpaa2, marvell prestera,
mellanox mlx5/mlxsw, lan966x, sparx5, ti am65-cpsw/icssg).

Does anyone know of specific devices/products which should work for us
and might have some recommendations?

Regards, Linus

PS: Minimum spec would be 8 ports, managed, 1Gbit, ideally with
at least 4 PoE ports. (The hackspace in total also has 46x RJ45
network sockets distributed over three rooms. But I don't think we
need full multicast capabilities on all of them to start with.
especially as that would probably considerably bump the price.)

                 reply	other threads:[~2025-02-21  4:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Z7gAE6vpDVa3Zlt6@sellars \
    --to=linus.luessing@c0d3.blue \
    --cc=bridge@lists.linux-foundation.org \
    /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