Who tried wifi-mesh?

You are really starting to piss me off.

I'm talking about wifi mesh, nothing else because i know

Sorry but my question is:

Who tried wifi-mesh?

For example, i don't need you to advertise your RT3200 which does not use MESH

Any comments outside of this topic are irrelevant.and so delete them


Dude, settle down. :slight_smile:

@Lynx and I will continue the RT3200 WDS discussion elsewhere, no problem. But @Lynx and @slh have both raised excellent points here that many others in the community will surely find beneficial when considering the mesh vs WDS options.

In the spirit of answering your questions (almost feels like you use bold type to "shout" stuff, which isn't cool):

I have tried wifi mesh, specifically 802.11s with and without batman-adv and found it to be extremely underwhelming on the hardware I tested it on.

So to be completely fair, you asked an extremely generic question to begin with and you're going to get a broad range of answers. If you aren't interested in feedback from RT3200 users, you should update your question to a more specific, "Who tried wifi-mesh on hardware XYZ?" On RT3200 hardware at the time of writing this, I would say "No, it does not work well." An Archer C7 or Netgear R7800 user may have a completely different take on it.

1, 2, 3, 42, 834? How is anyone supposed to answer this because you gave no clue as to how much area you are trying to cover, the type of wall materials in your space, what kind of hardware you're considering, 2.4Ghz vs 5Ghz vs 6Ghz, etc, etc.

Generically speaking a "mesh" would consist of 2...N nodes. The basic concept of mesh technology is that it dynamically configures routes between nodes and recalculates as you add/remove more.



I've also tried mesh on Openwrt with and without batman-adv.

I initially had it set up between two routers using 802.11s, one in a shed/workshop to connect to an outdoor IP camera, because its built in wifi kept dropping out.

Not using mesh currently, but I eventually got it working with Batman-adv and setup for both 2.4ghz and 5ghz, so that the router outdoors could connect to either of the two in the house which both have wired LAN connections. Reason for using this setup was neither 2.4 nor 5ghz were reliable due to multiple neighbour's access points frequently switching to whichever 2.4ghz channel I was using, and the lower range of non-dfs 5ghz channels being swamped too.

here's an iperf3: routers are bthub 5s using 802.11s with batman-adv

 Accepted connection from, port 54386
[  5] local port 5201 connected to port 54387
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-1.00   sec  6.21 MBytes  52.1 Mbits/sec
[  5]   1.00-2.00   sec  5.59 MBytes  46.8 Mbits/sec
[  5]   2.00-3.00   sec  5.96 MBytes  50.1 Mbits/sec
[  5]   3.00-4.00   sec  6.65 MBytes  55.8 Mbits/sec
[  5]   4.00-5.00   sec  6.68 MBytes  56.0 Mbits/sec
[  5]   5.00-6.00   sec  6.37 MBytes  53.4 Mbits/sec
[  5]   6.00-7.00   sec  5.49 MBytes  46.1 Mbits/sec
[  5]   7.00-8.00   sec  6.08 MBytes  51.0 Mbits/sec
[  5]   8.00-9.00   sec  6.48 MBytes  54.3 Mbits/sec
[  5]   9.00-10.00  sec  6.71 MBytes  56.4 Mbits/sec
[  5]  10.00-10.03  sec   196 KBytes  55.3 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  5]   0.00-10.03  sec  62.4 MBytes  52.2 Mbits/sec                  receiver
1 Like

Can you share a link to wherever you continue the RT3200 WDS discussion? you are correct that other users would find this useful!


Well, if you want to talk about your RT3200 in relay or WDS, create your request


I have a mesh network over 802.11s+batman-adv+ospfv3, where ospf protocol announces ipv4 addresses over batman-adv


1 Like