Hello,
I tried to create a mesh network but using my eth1 port: I need a mesh cloud in my warehouse.
I created mesh interface with eth1+wlan1.
Ip is on mesh interface. When I done this on the second RB I lost access to the firs RB751.

Why mesh not working with ethernet port ?

Thanks.

Looking at your diagram, all access points are wired to the switch - where does mesh fit in then?

TheWiFiGuy I can't use wired interfaces to transport mesh traffic ?

HWMP+ help please
Wireless WDS setup, cannot see LAN network ..

I can't see why you need Mesh.

Just set up each wired node as an access point, running the same ssid on a different channel - assuming all access points are running on the same network which your diagrams kind of suggests it is.

I need only one SSID on warehouse, not 4 or 7 different or the same.
Now I have 4 AP, but in plan to by more to cover all warehouse area.

This can be done using separate L2 zone ?

i haven't done it yet, maybe you could create wds like network and put the ether interface connected to the switch to those bridge.

jackman, maybe I will try to do this.
But in this topology I will have one point of failure.

This is my first planed topology, but as more I search the answer then more I convinced that on Mikrotik I can't do this.

I this topology I can't access WAP and WAPSw2 via Winbox MAC to setup them.

With last setup I can see all my 6 SSID, but should only one.
What can be wrong ?

Thats correct. Your devices will only see one ssid as they are all on the same channel. You will never just see 1 when scanning with mikrotik or any other scanner

Hello, I have the same topology like you. Did you solve your problem please?
Solution with bridged wifi and ethernet on each RB751 doesn't connect clients to AP with the most strenght signal
...even If I create ACL for signals i.e. -70-120

Any guesses please?

I too am curious about this.
I have Groove's at a site. Setting them same SSID different channels same security works, but this location has a lot of tablets running around... sales people... when they jump from AP to AP they disconnect just long enough to time out their hosted web sales app.. i want to use mesh with AP's all connected to same LAN via ethernet so they stay connected when running around site. thanks

i'm curious about this too, any good news or any configuration on how to do this.

Transparent transition between APs is not possible. This is not what WDS Mesh means. And this is not specified in the 802.11 standards.

Some vendors (e.g., Cisco) implement this possibility I think using proprietary extensions and wireless controllers, but at great cost.

I'm hoping someday the MikroTik new CAPsMAN service can implement this.

[...]

Transparent transition between APs is not possible. This is not what WDS Mesh means. And this is not specified in the 802.11 standards.
Some vendors (e.g., Cisco) implement this possibility I think using proprietary extensions and wireless controllers, but at great cost.
I'm hoping someday the MikroTik new CAPsMAN service can implement this.

I disagree. Transparent transition between APs is normal behavior. It is implemented in client's wireless card. When signal from AP is falling below defined level (usually bellow -80dBm) client starts searching for another AP with same SSID and better signal. Then associates to better AP. Only thing that is noticeable is about 1 second gap (depending on client's wireless card, but all devices I tested lost no more then two pings).

This is required to accomplish this:
- same SSID for all APs
- different channels on overlapping APs
- all APs connecting clients to the same network (same DHCP server)
- identical security settings on all APs
This is exactly what CAPsMAN does - it is a wireless controller.

Some vendors developed accelerated roaming between APs. For example: APs communicate with each other and exchange association data to speed up client's connection to new AP (this is done by controller). Client's authentication on target AP is quicker. Gap is reduced. That's all. There is 802.11r (fast roaming) for example. Maybe MikroTik will implement it in the future but it is only needed for voice communication. Everything else will work fine without fast roaming.

See this post by mcdebugger:
http://forum.mikrotik.com/viewtopic.php ... 84#p437484

That's all well and good, but it is not transparent handoff like one would expect when using that term. Think 3G/4G handoff. That is not possible with standard 802.11. The decision to switch is the client's, and there is no coordination.

That's all well and good, but it is not transparent handoff like one would expect when using that term. Think 3G/4G handoff. It is not possible with standard 802.11. The decision to switch is the client's, and there is no coordination.

It is transparent. Application running on station will not notice that AP has changed. Wireless interface is constantly connected. You are confusing it with "seamless" - term used by some wireless vendors. Roaming of stations is based on 802.11 standard and 802.11r is also part of 802.11 standard. And also, this is very good that it is the client's decision to switch, because every client has different requirements and roaming strategies.

Ok, seamless then. User wokinit wants seamless handoff, and that is not possible. TCP sessions will be disrupted and the application will have to reestablish.

Ok, seamless then. User wokinit wants seamless handoff, and that is not possible. TCP sessions will be disrupted and the application will have to reestablish.

Once again you are wrong. TCP sessions are not disrupted and do not have to be reestablished. File downloads (TCP) are not interrupted and console sessions (TCP also) are not interrupted. Read or test by yourself before you post anything, please.

Maybe you're using some WiFi client I've never used, but in my experience with mobiles and computers, when the WiFi client jumps from one AP to another AP on the same network and with same SSID, the interface flaps and TCP connections are dropped.

I'll play around with this sometime in the next week or two, using Windows, Linux, and Android as clients, just to make sure things haven't changed in the years since I last tried this.

But I wouldn't count on it working...

I have only seen this when there isn't enough overlap between access points coverage or if you cause a Layer 3 roam to happen. Assuming all your access points wifi interface are connected to the same L2 domain no L3 roam should be happening. I have also seen this when say you are in a warehouse and there isn't enough signal down the row because there is no AP in line of sight. It may be worth walking around with some site survey software and confirming your coverage.

As has been said already 802.11 wifi roaming is up to the client. It is a break before make type roaming but it doesn't make the interface flap if there is enough coverage. Cell phone roaming is make before break and is dictated by the cell network not the device.