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?

  • 9,037
  • 14
  • 59
  • 71
  • 6,777
  • 4
  • 21
  • 17
  • 6
    You've said you get blind spots no matter what, but for people who doesn't, this is an interesting related link: http://superuser.com/questions/17897/how-to-extend-wi-fi-signal-across-rooms – cregox Mar 31 '10 at 22:26

5 Answers5


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, usually without so much as a missed frame.

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 is a set of technologies, some proprietary, some standardized in IEEE 802.11F, known generally as Inter-Access Point Protocol. IAPP is a method by which generally enterprise-class APs can communicate with each other over the backhaul to optimize client roaming. But that's just an optimization, not a prerequisite for roaming. Roaming works "well enough" on networks both small and large without any IAPP going on.

Configuration Suggestions

Give both APs the same network name (SSID), the same security type (WPA2-PSK recommended), 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.

Additional Considerations

The rest of this answer is just a bunch of general "how to maximize your home 802.11 network bandwidth" tips, not specific to your question of two APs with the same SSID.

Consider taking this opportunity to fully modernize

If you are already buying a new AP and taking the time to reconfigure things, I recommend using this opportunity to replace your existing AP as well, by buying two of the latest APs that support simultaneous dual-band 802.11ac technology. That way you can support both the 2.4GHz band for older clients that are 2.4GHz only, as well as the less busy 5GHz band for more bandwidth. It is becoming a "best practice" to set your 2.4GHz 802.11n radio to 20MHz (HT20) channels so that it leaves some of the band free for things like Bluetooth to use. This limits your 802.11n transmission rates in the 2.4GHz band to ~130mbps instead of 300mbps, but allows other non-802.11 2.4GHz devices to still work okay. In 5GHz, where there are many more channels available and they are all generally much less busy, you are encouraged to use 80MHz (VHT80) channels to get maximum throughput.

Apple's latest 2013 AirPort Extreme and Time Capsule are simultaneous dual-band 802.11ac, and they also support 3 spatial stream (a.k.a. "3x3", "3SS") 802.11ac, for transmission rates up to 1300 megabits/sec if you have 3-stream 802.11ac clients that can do it. All of Apple's Mac products introduced in 2013 or later have 802.11ac. The MacBook Airs are only 2SS (867 megabits/sec max signaling rate), the iMacs are 2SS on transmit and 3SS on receive, but I believe the Retina MacBook Pros and Mac Pro are 3SS on both transmit and receive.

Note that the industry has been slow to roll out good 802.11ac APs and clients. A lot of the stuff that came out in 2012 or even early 2013 was often buggy bleeding-edge first-generation junk. Starting in June 2013 the much more reliable second-generation 802.11ac stuff started coming out. Besides the Apple products, the ASUS RT-AC66U is a decent simultaneous dual-band, 3SS 802.11ac AP.

If you're stuck with older single-band-at-a-time APs

If you don't need to support any older 2.4GHz-only devices, use the 5GHz band since it is generally less busy, and you can use HT40 without starving Bluetooth and other uses.

If you're stuck supporting 2.4GHz-only devices with single-band-at-a-time APs, be careful of your channel selection. In the 2.4GHz band, the channels overlap to a great degree. However, channels 1, 6, and 11 don't overlap at all, so those are good choices to pick manually. You could use a Wi-Fi network scanner like inSSIDer, NetStumbler, iStumbler, many "war driving" tools, etc. to see which channels are in use by other APs visible from where you are. If you suspect you have non-802.11 2.4GHz interferers in your area, such as Bluetooth, microwave ovens, and many (but not all) cordless phones, baby monitors, wireless webcams, and wireless room-to-room A/V senders, you could go all-out and get a spectrum analyzer like a Metageek Wi-Spy to find which channels are the least noisy where you are.

  • 101,729
  • 17
  • 175
  • 229
  • 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 '10 at 22:51
  • 47
    @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 '10 at 23:50
  • Nice. As for the DHCP: my broadband modem/router/AP uses different IP address ranges for ethernet and wireless, so hooking up the second AP to an ethernet port of such modem/router/AP might still make the APs be in different networks. I guess that can only be solved by getting standalone APs. – Arjan Mar 22 '10 at 07:47
  • @BartvanHeukelom see my answer over here: http://superuser.com/questions/367564/multiple-access-point-with-same-ssid-but-all-connections-goes-to-only-one-access/367626#367626 – Spiff Dec 14 '11 at 02:15
  • @Spiff , What tool do you use to monitor monitor wireless roaming? (Not to resurrect an old question or anything... ;) ) – Usta Feb 13 '13 at 02:29
  • @Usta On my Mac running OS X v10.8.x "Mountain Lion", I run `/usr/libexec/airpord debug +AllVendor +AllDriver +AllUserland`, then watch the "All Messages" log stream in Console.app. – Spiff Feb 13 '13 at 06:59
  • 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)? – David Miller Apr 07 '14 at 10:45
  • @DavidMiller Some cheap APs don't let you disable NAT and DHCP service, so the best you can do is cripple the DHCP server by giving it a zero-length pool of IP addresses to serve, and use a LAN port to connect it to the network. This has a downside of making it harder to give that box an IP address on your subnet so you can talk to it again later when you want to make changes. – Spiff Apr 07 '14 at 17:10
  • 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 06 '14 at 13:05
  • @Halfgaar1 When one AP goes down, all clients should treat it like it's suddenly out of range and automatically, seamlessly roam to other in-range APs. Were the other APs really in range of those devices? The Wi-Fi systems on phones and tablets is often more constrained than that of laptops. Otherwise, it sounds like your clients' Wi-Fi implementations suck. Is that a problem with Android in general or just the Wi-Fi chipsets/drivers supplied by those two vendors? – Spiff Jun 06 '14 at 14:30
  • For my expirience, for smoth roaming is important to have better AP on same frequency. But when client disconnected, it reconnect to best AP in about 1 second or less. – Mikhail Moskalev Dec 24 '14 at 22:23
  • @Spiff maybe you can add an explanation what the difference is between 802.11f, 802.11r and ESSID. – mgutt Mar 30 '15 at 15:18
  • Is this also appliable on new 2G + 5G wifi's? – Manuel Oct 18 '15 at 13:01
  • @Manuel Yes, this applies. There's nothing new about simultaneous dual-band APs. They've been around since 802.11a hit the market in 2002. Clients scan all the bands and channels they're capable of using, so they will find all APs on either band. – Spiff Oct 18 '15 at 14:51
  • @Manuel Did you see the caveat I wrote (back when I first wrote this years ago) about sticky clients? Did you see the part where I explained that WDS has nothing to do with roaming? It has nothing to do with fairness either. – Spiff Jan 12 '16 at 14:49
  • @Spiff, Thx rewrote comment ;) I can confirm handoff problems if 2 APs are in the same range as described in the following answer by MRC below. Macs (2010&2014) are sticking pretty long to the old ap even though transmission is resulting in lost packages in reason of thick walls. Thus I was wondering whether there is a more intelligent solution than just using same ssid without or switching channels manually? W-LAN Roaming? Radius? Wired-WDS? Are there any access points supporting it for fair budget? Is Fritz!W-LAN Repeater 1750E capable of this?Settings on devices? – Manuel Jan 12 '16 at 15:15
  • @spiff Does this hold true if I have one Wireless Router (Asus RT-AC87U) with one Access Point wired downstream (Asus RT-AC5300)? Both with the same SSID, the upstream in Router Mode, and the downstream in Access Point Mode. Would this all serve as one network i.e. allow a group of iPads to behave as if on the same network - sharing app access via the same Wifi, just the same SSID for a router and access point connected by a LAN cable? – ATSiem Mar 09 '16 at 06:36
  • 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 09 '16 at 07:35
  • Re: the "One roaming caveat", that some badly designed devices stick to whichever access point they first connected to... Does that problem go away if you are using a 'mesh' network? – callum Apr 19 '18 at 10:34
  • @callum “Mesh” is an overbroad term, but applied to real world 802.11 WLANs, it’s generally used as a way for APs to have wireless AP-to-AP links that can roam. But even if you have great mesh roaming algorithms for your AP-to-AP links, that doesn’t do anything for your client-to-AP links, which will still suffer from buggy/sticky client roaming implementations. So it usually falls into the “WDS has nothing to do with [client] roaming” case, which I covered. – Spiff Apr 19 '18 at 18:01

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"

  • 361
  • 3
  • 2
  • 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. –  Nov 02 '11 at 06:07
  • 8
    While I've found this to be true, the same problem occurs when using 2 SSIDs – Bart van Heukelom Dec 13 '11 at 23:55
  • 5
    @BartvanHeukelom Yes, the same problem occurs with two SSIDs, but it it _much_ easier to change AP when they have different SSIDs. – Mr. Flibble Sep 26 '13 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 08 '15 at 20:06

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 (1, 6, 11)
  • 251
  • 3
  • 9

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.

Josh K
  • 12,747
  • 7
  • 41
  • 58
  • 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 '10 at 23:52

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

  • 34,203
  • 26
  • 108
  • 137
  • 15
    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. – WheresAlice Mar 21 '10 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 '10 at 20:00