WiFi expert needed

I don't think you understand mesh

If you have one cabled mesh AP, and 20 wireless mesh APs, all 20 wireless APs routing to the one cabled AP, you will have throughput issues, especially if some APs are more than one jump from AP to AP.
 
If you have one cabled mesh AP, and 20 wireless mesh APs, all 20 wireless APs routing to the one cabled AP, you will have throughput issues, especially if some APs are more than one jump from AP to AP.
And what if all your nodes are cabled?
 
Then you get much better throughput. The LAN usually has much higher throughput/lower latency than Wifi.
Yes. But you said they shouldn't mesh, they should use cables. Why not use mesh with cables between the nodes?
 
Yes. But you said they shouldn't mesh, they should use cables. Why not use mesh with cables between the nodes?

Then it is not meshing. If every AP just immediately forwards its traffic to the wired LAN, then there's no difference to non-meshing APs.
 
Then it is not meshing. If every AP just immediately forwards its traffic to the wired LAN, then there's no difference to non-meshing APs.
Which brings me back to my initial comment, I don't think you understand mesh
 
I have to disagree. Roaming is not what makes it a mesh.

What is a mesh?​

In a sentence, a mesh consists of multiple centrally managed Wi-Fi broadcasters working together to form a unified Wi-Fi network. Among them, there’s one primary router that handles routing, network settings/features, and Internet connectivity. The rest only expand the network’s coverage.

Initially, “mesh” meant using multiple centrally managed Wi-Fi broadcasters wirelessly linked together to create a single network. Nowadays, using network cables as the backhaul links is commonplace—it’s the only way to get the best-performing system, as described below.
Still, some online “experts”—there are a lot of them these days—have mocked me, privately or publicly, that using network cables negates the mesh notion. “It’s not a mesh anymore!” they say, and they might be right. But in my real-world experience, wired backhauling is the best way to build a network, including a (mesh) Wi-Fi system. Ultimately, it’s about getting things connected, not a nerding contest.

Source:
 

What is a mesh?​

In a sentence, a mesh consists of multiple centrally managed Wi-Fi broadcasters working together to form a unified Wi-Fi network. Among them, there’s one primary router that handles routing, network settings/features, and Internet connectivity. The rest only expand the network’s coverage.

Initially, “mesh” meant using multiple centrally managed Wi-Fi broadcasters wirelessly linked together to create a single network. Nowadays, using network cables as the backhaul links is commonplace—it’s the only way to get the best-performing system, as described below.
Still, some online “experts”—there are a lot of them these days—have mocked me, privately or publicly, that using network cables negates the mesh notion. “It’s not a mesh anymore!” they say, and they might be right. But in my real-world experience, wired backhauling is the best way to build a network, including a (mesh) Wi-Fi system. Ultimately, it’s about getting things connected, not a nerding contest.

Source:

Agree 100%
 

What is a mesh?​

In a sentence, a mesh consists of multiple centrally managed Wi-Fi broadcasters working together to form a unified Wi-Fi network. Among them, there’s one primary router that handles routing, network settings/features, and Internet connectivity. The rest only expand the network’s coverage.

Initially, “mesh” meant using multiple centrally managed Wi-Fi broadcasters wirelessly linked together to create a single network. Nowadays, using network cables as the backhaul links is commonplace—it’s the only way to get the best-performing system, as described below.
Still, some online “experts”—there are a lot of them these days—have mocked me, privately or publicly, that using network cables negates the mesh notion. “It’s not a mesh anymore!” they say, and they might be right. But in my real-world experience, wired backhauling is the best way to build a network, including a (mesh) Wi-Fi system. Ultimately, it’s about getting things connected, not a nerding contest.

Source:
There is no way that cabling the nodes negates the mesh notion. That is a ridiculous take
 
If you want to discuss mesh then go look at a proper technical description

Mesh describes a network configured using the mesh protocol (Hybrid Wireless Mesh Protocol (HWMP) from IEEE 802.11s draft standard)
There are 2 seperate technical things in play here

Any links to interconnect all the ap's together using the mesh protocol.
This is what is creating the actual mesh and it is just one of a few ways to implement a AP network.
Not my favourite at all to be honest as wifi links ( where it is commonly used) esp for carrying core traffic have limitations in speed and latency.
Mesh protocol can be used on wifi or wired links in the Mikrotik implementation
There is another way of doing something similar without using the mesh protocol on wired links

The handoff of clients between the different ap's as you move arround.
This is not specific to mesh but can be implemeted completely seperate as well.


Long story short, from a networking perspective, imo , this is a lazy way of doing a AP implementation.
 
Last edited:
If you want to discuss mesh then go look at a proper technical description

Mesh describes a network configured using the mesh protocol (Hybrid Wireless Mesh Protocol (HWMP) from IEEE 802.11s draft standard)
There are 2 seperate technical things in play here

Any links to interconnect all the ap's together using the mesh protocol.
This is what is creating the actual mesh and it is just one of a few ways to implement a AP network.
Not my favourite at all to be honest as wifi links ( where it is commonly used) esp for carrying core traffic have limitations in speed and latency.
Mesh protocol can be used on wifi or wired links in the Mikrotik implementation
There is another way of doing something similar without using the mesh protocol on wired links

The handoff of clients between the different ap's as you move arround.
This is not specific to mesh but can be implemeted completely seperate as well.


Long story short, from a networking perspective, imo , this is a lazy way of doing a AP implementation.
What would you call a, for example, TP-Link Deco system with all the nodes connected via cable?
 
What would you call a, for example, TP-Link Deco system with all the nodes connected via cable?
If this is their extent of their "Mesh" then I think they are taking liberties in calling it a mesh
Can you confirm what protocol they use ?
Also can you show me a design where they show a wired mesh

1713187363310.png

VS a Mikrotik mesh implementation

1713187416648.png
 
If this is their extent of their "Mesh" then I think they are taking liberties in calling it a mesh
Can you confirm what protocol they use ?
Also can you show me a design where they show a wired mesh

View attachment 1691611

VS a Mikrotik mesh implementation

View attachment 1691613
I have no clue. The point is it has a single SSID with seamless handover between them which is obviously very different to legacy APs
 
I have 3 Unifi Ap's connected to a single switch all connected with cables, but they share the same 2 SSID's and do seamless handover no matter where I am in my house, I would consider that a mesh.
 
I have no clue. The point is it has a single SSID with seamless handover between them which is obviously very different to legacy APs
Wrong

You can use a single ssid on multiple AP's regardless of teh backhaul
The trick is in configuring the way the handoff works.
That doesnt make it a mesh if teh mesh protocol is not being used
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X