640

I need to upgrade my existing wireless infrastructure and this time I want 2 access points to cover my house, since I get blind spots no matter what with a single AP. I have physical cabling to my central network available for both access points.

I would really like these two to interoperate seamlessly as a single SSID. How do I do this? What are the features that the new access points I'm buying would need to support?

1

5 Answers 5

897
+50

Multi-AP Roaming Network Background

There is no magic to making multiple-AP (roaming) 802.11 networks work. Wireless clients just assume that all APs with the same SSID are configured similarly and are all just different points of access to the same underlying wired network. A client will scan all channels looking for APs publishing the SSID it wants, and will pick whichever one suits its needs best (usually that means whichever one shows the highest signal strength).

Once on the network, clients stay with the same AP as long as it is meeting the client's needs (i.e. as long as its signal strength is above a "good enough" threshold). If the client later thinks it could be better off with another AP on that network, it will do periodic scans of all channels looking for other APs publishing that SSID. If a scan turns up a candidate AP that is enough better than the AP it is currently on, it will automatically roam to the other AP, without dropping connections.


One roaming caveat: As another commenter pointed out, there are definitely poorly engineered clients out there with poor roaming algorithms or thresholds, which don't actually roam when they should, and thus end up being too "sticky", staying on the first AP they joined well after they could have been getting better performance and reliability with another AP that they are now closer to. Sometimes it helps to force the client's Wi-Fi interface to rejoin the network when you notice that a client has stuck to the wrong AP. If you have a lot of these buggy clients, then using the same SSID for multiple APs might not work well for you; you might want to use different SSIDs so you can more easily monitor and control which AP your client is associated to.*


Assuming both APs are configured similarly and are connected to the same underlying network, roaming is seamless and invisible to the user (except nerds like me who run tools to watch for these things). Roaming events are invisible to applications using the network, although some low-level parts of the network stack might be notified of the event, so that, for example, your DHCP client can double-check that this new AP really is connected to the same network, so it can be sure your DHCP lease is still valid on this network.

Some other users' Answers and Comments on this question erroneously suggested that wireless protocols or features like wireless relay or WDS might be needed for roaming, but that is absolutely incorrect. Those features are just ways to replace a wired Ethernet backhaul with a wireless one.

For the sake of completeness, I should mention that there have been a number of addenda to 802.11 over the years, such as 802.11F, k, r, u, and v, that have created mechanisms that allow coordinated multi-AP systems to help clients roam appropriately and quickly by doing things like keeping clients well-informed about their roaming options, and optimizing re-authentication when roaming, especially when tricky enterprise-class security is in use. But please note that none of those addenda are necessary for roaming to work. The roaming decisions are still ultimately up to the client, and the coordination among the APs does not require wireless relay, WDS, or mesh.

Configuration Suggestions

Give both APs the same network name (SSID), the same security type (WPA2/WPA3-PSK recommended; do not leave original WPA (TKIP) enabled or available in any way), and the same wireless security passphrase. Many clients assume that these kinds of settings will be the same across all APs with the same SSID.

Since you already have the cabling in place, use wired Ethernet as your backhaul. This saves your wireless bandwidth for your portable/mobile devices that actually need it, instead of wasting in on stationary devices like APs that could reasonably be cabled up.

If you have another device on the network, such as a broadband home gateway, providing NAT and DHCP service, then put both APs in bridge mode (turn off NAT and DHCP service). You generally only want one box on your network acting as a NAT gateway or serving DHCP. If you don't already have another device on your network doing NAT and DHCP, and you need those services, then you can have one of your APs do it. Have the more "upstream" AP (the one that's closer, topologically, to your broadband modem) do NAT and DHCP, and make sure that the wired Ethernet connection to the other AP comes from the first AP's LAN port. Also make sure that the "downstream" AP is in bridge mode. I call this out because I have seen people make the mistake of leaving NAT and DHCP enabled on both of their APs, and I have seen clients that are not smart enough to realize that, say, the 192.168.1.x/24 network they are on now is not the same 192.168.1.x/24 network they were on a moment ago in the other room. I have also seen users get confused in this situation where two laptops in the same house had 192.168.1.x addresses, but could not ping each other because they were really on two separate IP networks behind two separate NATs.

Channel is one key setting you do want to vary from AP to AP in a roaming (multiple AP) 802.11 network. To maximize bandwidth, leave your APs to automatically select the channel to use, or you can manually pick different, non-overlapping, and hopefully unoccupied channels to use. You don't want transmissions to/from one AP to compete for bandwidth with transmissions to/from the other AP.

24
  • 2
    But then what if one takes a laptop from one room to another? I'm no expert, but I'd assume WDS would take care of switching access points without ever loosing connectivity.
    – Arjan
    Mar 21, 2010 at 22:51
  • 48
    @Arjan I've updated my answer to address your questions. The short answer is that clients will roam just fine no matter what backhaul you use between your APs, and WDS is just a way to do a wireless backhaul in situations where using a wired backhaul is cost-prohibitive. WDS has absolutely nothing to do with roaming.
    – Spiff
    Mar 21, 2010 at 23:50
  • 2
    A very useful answer, thank you. You mention putting the 'downstream' (further from the internet) access points(s) in bridge mode (and disabling NAT and DHCP). Is there a difference between bridge mode and connecting the upstream device using a LAN port rather than its WAN port (as I've seen as a suggested solution for extending a wireless network with a wired backbone elsewhere)? Apr 7, 2014 at 10:45
  • 1
    So what is supposed to happen when you unplug one of the AP's? All my applications lose their connection when I do. Reconnection to the other AP takes about 20 seconds. Even the roaming bit hardly works; they stick to the slow far away AP. I've tested with a Samsung Galaxy 10.1 tab and HTC Desire Z phone.
    – Halfgaar
    Jun 6, 2014 at 13:05
  • 1
    @ATSiem Yes, see my sentence that begins "If you don't already have…" and the rest of that paragraph; I describe exactly what you're asking about.
    – Spiff
    Mar 9, 2016 at 7:35
37

Good article, however the handover between multiple APs on same SSID often causes problems as the client will stick with the original AP even if the signal is well below the "good enough" threshold. E.g. if you move your laptop from one end of the house to the other it will not switch simply to the new AP when it finds the AP with the much stronger signal, rather it will stick with the original AP until the signal is so weak and erratic (<5mb) that it can non longer be used. In many cases the signal may bet so weak that the laptop can not surf the net or communicate with network devises but laptop will still use original AP as it can still see a very weak signal. To fix this requires a manual intervention to force AP switch (eg repair or reset of wireless connection on laptop)

In short the following statement is questionable: "Once on the network, clients stay with the same AP as long as it's meeting the client's needs (i.e. as long as it's signal strength is above a "good enough" threshold). If the client later thinks it could be better off with another AP on that network, it'll do periodic scans of all channels looking for other APs publishing that SSID. If a scan turns up a candidate AP that's enough better than the AP it's currently on, it'll automatically roam to the other AP, usually without so much as a missed frame"

4
  • 3
    @MRC- Agreed. This is an informative article, but with your basic wireless client, I don't see it switching seamlessly as needed. Typically some network disruption is necessary to force the handoff. Depending on the wireless client, radios, and software running, this is possible, but it would require some testing with your own devices. Some might roam fine, others may not. Still a workable setup though.
    – user103803
    Nov 2, 2011 at 6:07
  • 8
    While I've found this to be true, the same problem occurs when using 2 SSIDs Dec 13, 2011 at 23:55
  • 6
    @BartvanHeukelom Yes, the same problem occurs with two SSIDs, but it it much easier to change AP when they have different SSIDs. Sep 26, 2013 at 20:27
  • It works pretty well on my Mac and on my PC laptop (but only on Linux, the Intel Win7 driver seems to be stickier). So the roaming algorithm can work well but it seems to be quite driver dependent.
    – Huygens
    Aug 8, 2015 at 20:06
9

To make it short, these are the most important things to do:

  • Same SSID, passphrase and security settings on all APs
  • Different channel for each AP, ideally non-overlapping, e.g. in case of 2.4 GHz: (1, 6, 11)
4

If you use something like an Airport Express it has an option to extend another WDS network. I would assume that other routers have a similar feature accessible through their respective configuration panels.

It's difficult to provide a working solution without knowing more about your network setup.

1
  • 9
    Like @kaerast commented on another answer, the original question states that he has cabling in place already to do a wired backhaul, so the suggestion of doing WDS would just be a waste of wireless bandwidth.
    – Spiff
    Mar 21, 2010 at 23:52
0

I believe that you are looking for wlan/wifi repeaters. Here is a tutorial: Extend WLAN Range with Repeaters

2
  • 17
    The original question states that wired network is available throughout the house. Therefore a repeater is not necessary, simply a second access point operating on a different channel but with the same ssid and key. Mar 21, 2010 at 19:32
  • @kaerast, didn't you just give an answer? Just configure the 2 wireless routers to have the same ssid and other settings but work on different channels.. possibly have to do some sorta work with dhcp (two different ranges) but should work..
    – Earlz
    Mar 21, 2010 at 20:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .