I've been noticing some inconsistencies and weird behavior in my home wifi setup. I'm starting to suspect some kind of serious security issue.
Periodically, the router (netgear wnr3500) will become unresponsive and not allow anyone to connect, requiring a reboot of the router. I assumed this was typical death by summer heat.
Recently, I've started noticing that my laptop is connecting to a similarly named wireless network that's unsecured. So, if my ssid is "bobsmith" this would be identified in windows as "bobsmith 2". I thought this was a windows bug, but I suspect windows is automatically connecting to a name and not a sensible unique identifier, despite it being aware that "bobsmith 2" is different so as to rename it.
Today, I was wrestling with my wireless bridge and determined that it wasn't connecting to anything. Refreshing the available ssids, it found "bobsmith 2" (unsecured) instead of "bobsmith" (wpa) - which it is set to connect to.
A reboot of my router eliminated this "bobsmith 2" unsecured network and brought back the "bobsmith" wpa-protected one. Once again.
Does anyone recognize this phenomena?
Periodically, the router (netgear wnr3500) will become unresponsive and not allow anyone to connect, requiring a reboot of the router. I assumed this was typical death by summer heat.
Recently, I've started noticing that my laptop is connecting to a similarly named wireless network that's unsecured. So, if my ssid is "bobsmith" this would be identified in windows as "bobsmith 2". I thought this was a windows bug, but I suspect windows is automatically connecting to a name and not a sensible unique identifier, despite it being aware that "bobsmith 2" is different so as to rename it.
Today, I was wrestling with my wireless bridge and determined that it wasn't connecting to anything. Refreshing the available ssids, it found "bobsmith 2" (unsecured) instead of "bobsmith" (wpa) - which it is set to connect to.
A reboot of my router eliminated this "bobsmith 2" unsecured network and brought back the "bobsmith" wpa-protected one. Once again.
Does anyone recognize this phenomena?
Last edited: