Is someone here who has experience in WLAN mesh protos ?
Which will be the best mesh proto nowadays ?
Where are the difference in these three ? (hope there is an easy answer for this )
I know three WLAN mesh possibilities:
Thanks for your help
"Best" is a personal opinion and depends a lot on both your objectives and your hardware.
My objectives were
- Seamless client transitions from one AP to another -- fast enough to prevent FaceTime drops (with 802.11r)
- No need to re-acquire DHCP lease on transition
- No dropped "persistent" connections due to IP address changes
- Ability to segregate traffic on multiple VLANs
I use 802.11s with gretap (Layer 2) tunneling of VLANs over the mesh. My hardware and its drivers support it. It works well for my application. I have not looked into routing with 802.11s mesh gateways at this time. Such routing, at first glance, seems "challenging" as my end points are not 802.11s nodes.
B.A.T.M.A.N. seems like a good option as well. I have not looked into it in depth. From what I understand, it requires a Layer 2 mesh to be set up (such as with IBSS) that the B.A.T.M.A.N. rides on top of.
Thanks for your knowledge
Are you really the only one who played around with mesh in openwrt ?
cant believe - hope other people will share their experience
BATMAN-adv on top of 802.11s seems to be popular with several open projects and commercial devices.
- More wifi drivers support 802.11s than IBSS (adhoc). Driver development pointed more to 802.11s since it is a current IEEE standard.
- BATMAN will wrap and transport VLAN tagged packets natively, no need for tunnels. Raw or routed 802.11s radio drivers cannot handle VLANs.
Client performance during roaming between APs is almost entirely a client issue. The backhaul routes between the APs-- be it wired, mesh, or AP-STA, will be up constantly as clients roam.
The main downside of BATMAN is that different versions are not intended to be compatible, in fact packets tagged with a different version number will be ignored. Since it is part of the kernel, this means that all your mesh devices must be running approximately the same kernel version.
Wow that was an answer I was looking for
with 11s and IEEE i didnt recognized it: seems to be 11s will be the chosen one ?
and BATMAN-adv on top if VLAN is needed...
Thanks for that in deepth answer
Is somebody in 11s developing and know if 11s is stable for production ? or still under heavy development ?
EDIT: Is there any Device (that can run Openwrt) and has tri-band wifi ?
I want to the following setup one 2.4 and 5ghz band for all clients (like any setup) and second 5ghz band for mesh internal (only for all wifi APs)...
There are only very few devices supporting that, while there seems to be a tag for devices like that, it doesn't really appear to be used consistently for such devices.
In general there are only very few devices with three independent radios, even less with OpenWrt support, you probably might find best support for devices that offer 3+ mini-PCIe ports (e.g. Turris Omnia, I think the PCEngines APU2 range of devices), the Netgear r8000 might also fit the bill - maybe the Linksys EA8300, but that one isn't quite supported yet.
IEEE 802.11s has been standardized since 2012 and seems very stable within the same OS family.
Thanks for the activity
@slh I see - but thanks for thei hint for mini-PCIe devices. Didnt have in mind
One question anyway: If I will setup Mesh like in 11s - Do I need to setup every AP device on another wifi channel (like oldscool access point setups and to minimize signal interference) or all AP devices on same wifi channel ?
Or: no need for setup wifi channels in 11s ? (didnt setup it yet)
The mesh routing has to all be on the same channel, otherwise none of the stations can communicate with each other. So unless you have a separate radio device, then the corresponding AP (should you choose to provide both mesh routing and AP) will be on the same channel.
With radio device you ment another wifi band ?
Yes. Most routers use different chipsets to handle the different bands simultaneously.
Client devices switch between bands so they can have an all in one setup.
I specifically used radio device, because on a custom setup (and some existing routers) you might have multiple radio devices on the same band, to increase the device throughout or handling of more clients on a band (at different frequencies).
Good to know. This will really help me out on a first mesh setup