this post was submitted on 30 Jul 2024
5 points (100.0% liked)

Hardware

764 readers
125 users here now

All things related to technology hardware, with a focus on computing hardware.


Rules (Click to Expand):

  1. Follow the Lemmy.world Rules - https://mastodon.world/about

  2. Be kind. No bullying, harassment, racism, sexism etc. against other users.

  3. No Spam, illegal content, or NSFW content.

  4. Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.

  5. Please try and post original sources when possible (as opposed to summaries).

  6. If posting an archived version of the article, please include a URL link to the original article in the body of the post.


Some other hardware communities across Lemmy:

Icon by "icon lauk" under CC BY 3.0

founded 2 years ago
MODERATORS
 

In all of my recent wifi cards, none of them seem to support 802.11s mesh mode. Is that standard "dead", or do I just need to look for better/specific-brands of wifi adapter? Or perhaps have Linux drivers just not kept up with the latest wifi chipsets?

I've been wanting to revive the B.A.T.M.A.N mesh project I've toyed with off-and-on for the last few years, but I'm having a hard time finding wireless cards that support native meshing. Seems like nothing above Wifi 4 (11n) supports it, or at least none of my devices with Wifi 5 or 6 support that mode.

IBSS/ad-hoc mode is available, but getting different brands (or even different models of the same card) to work and with WPA3 encryption has been an ongoing nightmare, but 802.11s always "just worked".

Curious if I just missed a memo along the way or if it's something more mundane like mesh mode not being a priority for the latest chipset drivers.

Edit: Looking at the output of iw phy on one of my devices, it does list mesh point in the Supported TX/RX frame types but not in the supported interface modes. So I'm leaning toward driver support, but would love to hear a more educated voice chime in.

you are viewing a single comment's thread
view the rest of the comments
[–] doczombie 3 points 4 months ago

It was never much use to enterprise so never got wide adoption.

It relied on a lot of different hardware and drivers all working nicely together as both client and host, which is a lot more difficult than a WAP-client relationship in practice.

Companies make the stuff, if no one uses it, no market, no money for development or maintenance.