Most routers come with the same default SSID. Example: (Dlink, Linksys, etc..).

So what happens if I have a router with SSID "Dude", and my neighbour has a router with SSID "Dude".

Assume both routers have WPA2PSK encryption, but different passwords. Will our devices be able to connect to the "correct" network without confusion or interference of service?

  • 4
    More than a year further... when will you accept an answer? I don't care if you don't select my answer, but you should mark it as answered if that is the case.
    – LPChip
    Oct 26, 2015 at 15:36
  • 1
    @LPChip: I don't think he is active here anymore to accept your answer. His profile says last seen is Last seen Aug 10 '15 May 18, 2016 at 9:03

5 Answers 5


As far as a standard 802.11 (Wi-Fi) client is concerned, the same SSID means it's the same network. This is how you set up multi-AP wireless networks that allow roaming between APs; you set them all up to publish the same SSID, so the clients know those APs are all part of the same network and the clients can roam between them as needed.

Some client implementations try to be smart about the potential problem you've raised (neighbors using non-unique default SSIDs), but you shouldn't assume that all clients will handle it gracefully and securely.

Having WPA2-PSK enabled on your AP will make sure that your neighbor's clients can't join your AP, but it won't keep them from trying (and possibly causing authentication error events on your router's system log). By the way, WPA2-PSK does not require the AP or the client to reveal the password to the other devices; that would be exceedingly lame. Modern authentication schemes use mathematical tricks that allow each end to prove to the other that they know something, without revealing to an impostor or eavesdropper what it is they know.

Having WPA2-PSK on your own AP won't necessarily keep your clients from trying to join your neighbor's same-SSID network. Your clients may prompt you for a new password for the network if they accidentally try to join your neighbor's AP, and the join fails because of the bad password. If your neighbor turns off security on his network your clients may actually successfully join without prompting. That is to say, I've seen 802.11 clients that were susceptible to security downgrade attacks, where just because they knew a WPA2-PSK password for a given SSID, didn't mean they felt compelled to always require that network to use WPA2-PSK; if they saw the same SSID without security, they might just join it and not bother with security. This is, of course, insecure and buggy behavior, and I would hope that the Wi-Fi Alliance's Wi-Fi certification testing tests to make sure that devices that pass certification don't do this, but you never know.

  • 1
    Lets say your network is open (no password) and the neighbours network has a password (e.g. WPA2-PSK). Will the neighbours' client devices connect to your open network, or will the client see that the network now does not require a password and realise something is wrong and not connect?
    – Robert
    May 27, 2015 at 15:34
  • what you exactly mean by (and possibly causing authentication error events on your router's system log).? can u explain a bit technically pls?
    – Abhinav
    May 1, 2017 at 17:08
  • @Abhinav If your neighbor's clients keep trying and failing to authenticate to your router, and if your router is configured to log those errors, you will see those errors reported in your router's logs.
    – Spiff
    May 1, 2017 at 17:13

This can cause problems. Because there are 2 networks with the same name, you will only see one wifi network. Depending on which of the two networks is closer at the moment of connecting, thats the network that your device is trying to connect to using the password. If it is closer to your neighbours network, it will simply fails to connect and likely asks you to type in your password.

Do note that if you make a connection and then move closer to your neighbours wifi, things will keep working until you actually get out of range of your own wifi, in which case it will try to switch and fail then, prompting you with an enter password dialog.

I would strongly suggest to use a unique SSID for your network. Bear in mind that others can read this name, so it should not be an indication of to where you live, so burgulars won't have a clue where people live that have computers.

Also, Dlink, linksys etc routers often do use their name, but always have a small additive, such as Linksys-15326 which is unique.

  • You should see both network. They're both differencied by the BSSID (MAC address ; or similar) they have, even if the SSID (name) is the same. But yes, the network manager software would then be confused about which network to connect since it relies generally on the SSID (to be able to connect to all AP in a school with same settings for exemple).
    – piernov
    Apr 6, 2014 at 15:48
  • 1
    @piernov: No, there are way too many large-scale ESS network out there. If your connection manager had to display all BSSes, you would see many AP with the same SSID in a large WLAN deployment. And your device will typically transparently roam between APs in the ESS.
    – BatchyX
    Apr 6, 2014 at 16:18
  • 1
    But what happens when my laptop tries to connect to his router ? Will he see my network password ? (Even if both our networks use WPA2PSK) Apr 7, 2014 at 3:34

Each of the SSID have a unique BSSID - so your device knows the difference once you are associated. Your issues will only be in the authentication phase. If they share a DS (Distribution System) - they will usually be managed by the same entity - hence your credentials would be shared. If they are unrelated, then your device may mistakenly try to join the wrong one depending on signal strength and it could fail unless it is open. This is a common “honey pot” strategy.

If they are on different channels, if you associate with the right one, it will not matter - what’s in a name. An SSID with a different BSSID is not the same.


On Windows, use WifiInfoView to select the right Wifi. It can tell the difference between two networks with same SSID.


Often a hacker will deploy a same SSID network (without security) in an attempt to capture the operated device of the password - protected network being mimicked. The resultant exchange places the mimicked device under the control of the operator of the unsecured network long enough for its operator, the hacker, to glean important security information from the password protected network, which is not all that secure.

  • This doesn't answer the question
    – Toto
    Mar 15 at 15:45
  • As it’s currently written, your answer is unclear. Please edit to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers in the help center.
    – Community Bot
    Mar 15 at 16:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.