Setup is as follows:
Modem <-> RouterA (RB2011) <-> RouterB (hAP)
RouterA and RouterB both have wired devices attached (computers, IPTV boxes, ...)
他们还提供无线网络。什么I want now is both of these access points to provide "the same" wireless network. As in, when you move from away from RouterA and closer to RouterB (and it looses signal of RouterA), the client swaps over without any visible downtime to him (or as low as possible).
From looking at the wiki and other threads so far, it seems as the correct way would be to set "wds mode" to "dynamic" and run RouterB as a "wds slave" while RouterA is an "ap bridge". The default WDS bridge would then be set to "br-lan" (the bridge powering all devices on RouterA and RouterB, including the other wired devices and wireless devices).
Is this correct?
Re: Correct setup for wireless client roaming
I did this at my home once, and was very unhappy with the instability of things - I had a 951 acting as the wds slave.... it was constantly losing connection to the master or to my devices, but when I returned it to being just a bridge client, it was stable again. Remember that when you use such a configuration, the bandwidth of the wds slave is cut in half because it has to spend half its time being an access point and half its time being a client to the primary AP.....
如果你有同轴电缆在家里,得到一双MOCA 2.0 devices to be the backbone ethernet connection between the two access points, and then configure the second one to be a CAPS client.
http://www.bhphotovideo.com/bnh/control ... &A=details
These devices don't even have to be working in pairs - if you have 3, then you basically have just turned the coax wiring in your home into a 3-port ethernet switch.
如果你有同轴电缆在家里,得到一双MOCA 2.0 devices to be the backbone ethernet connection between the two access points, and then configure the second one to be a CAPS client.
http://www.bhphotovideo.com/bnh/control ... &A=details
These devices don't even have to be working in pairs - if you have 3, then you basically have just turned the coax wiring in your home into a 3-port ethernet switch.
Last edited byZeroByteon Tue Dec 15, 2015 12:59 am, edited 1 time in total.
Re: Correct setup for wireless client roaming
Both APs are connected directly via a wire (CAT5e, 100MBit/s ports). Does this mean I don't use WDS and something else? If so, what else?I did this at my home once, and was very unhappy with the instability of things - I had a 951 acting as the wds slave.... it was constantly losing connection to the master or to my devices, but when I returned it to being just a bridge client, it was stable again. Remember that when you use such a configuration, the bandwidth of the wds slave is cut in half because it has to spend half its time being an access point and half its time being a client to the primary AP.....
如果你有同轴电缆在家里,得到一双MOCA 2.0 devices to be the backbone ethernet connection between the two access points, and then configure the second one to be a CAPS client.
Re: Correct setup for wireless client roaming
Good. (And you don't need the MOCA devices I linked above.)Both APs are connected directly via a wire (CAT5e, 100MBit/s ports). Does this mean I don't use WDS and something else? If so, what else?
You'll want to set up both as AP-Bridge with the same SSID and same encryption, etc.
The secondary device will just operate as a bridge - with wlan1 and ether1 connected to bridge1 (and ports ether2-ether5 set to use master=ether1)
For roaming to work best, I'd imagine that CAPsMan is the way to go - I haven't ever messed with CAPsMan though, but there are videos on YouTube and Wiki articles about how to set it up.
Re: Correct setup for wireless client roaming
Same channel or different channel? I would assume different channels?You'll want to set up both as AP-Bridge with the same SSID and same encryption, etc.
Re: Correct setup for wireless client roaming
I was reading an article about this subject recently where the author recommended using the same frequency and lower power - because if they're on different channels, the client has to handle the roaming, and using the same BSSID and frequency hid the fact from the client that it was even roaming......Same channel or different channel? I would assume different channels?You'll want to set up both as AP-Bridge with the same SSID and same encryption, etc.
I don't remember if this was a Mikrotik solution or someone else's product, or what.... the article also mentioned that a controller-based platform is able to basically force the client to roam to the best AP, and I was more interested in controller-based anyway (e.g. CAPsMan / UniFi / Aruba / etc)
That's how I'm going to set up my second AP at my house.
Re: Correct setup for wireless client roaming
Different channels, same SSID & security settings, and roaming will be automatic.Same channel or different channel? I would assume different channels?You'll want to set up both as AP-Bridge with the same SSID and same encryption, etc.
But roaming is usually decided by the client device so you have no real control over it, however you can try to force roaming by putting access-lists (i.e kicking clients with low signal, hoping that they will reconnect to the other AP).
For example here, limit is -76dB
Code:Select all
/interface wireless access-list add forwarding=no signal-range=-75..120 add authentication=no forwarding=no signal-range=-120..-76Re: Correct setup for wireless client roaming
Thanks for that, works perfectly.
Only thing I wish RB could do was "zero-downtime" roaming, so that one access point can "seamlessly" hand off clients to another. I have no idea how other things implement such feature but Ubiquiti claims to have such feature for example.
The forced disconnect is pretty straight on and works fast with reconnecting to the correct AP but of course it still causes some slight interference.
Who is online
Users browsing this forum:Semrush [Bot]and 7 guests