Since I started using my Surface Pro 3, I’ve been wondering if my home Wi-Fi setup was partly to blame for my connectivity frustrations. In this post I share some of the lessons I’ve learned while trying to get the most out of my mobile devices and my home network.
I can remember buying my first Wi-Fi router back in 1998. I spent about $500 for a Linksys 802.11b device. Back then I was one of about 40 people in my city that had residential broadband as part of a pilot project. Since then I’ve had at least a half a dozen different access points at least three from Linksys but also others from Netgear, TrendNet, D-Link, Belkin, Asus etc.
I’ve never had any real problems with my Wi-Fi network until last few years. Probably due to the proliferation of Wi-Fi in all sorts of consumer devices creating congestion in the 2.4GHz band. Add to that my stable of Microsoft Surface devices with flakey Marvell Wi-Fi drivers and it’s a recipe for frustration with something that I had come to rely on and taken for granted for over a decade.
As my family has grown I’ve had to give up my dedicated home office space and move my networking gear into a utility room in the basement. Another side effect of a growing family is a proliferation of wireless gadgets (Six Tablets, three laptops, three MP3 players, four mobile phones, two Xboxes, three eReaders, etc. – well I guess I’m the major cause of that but let’s blame the wife and kids just a little.
So what have I done to reduce my Wi-Fi headaches?
Repeater – I added a Cisco repeater on the main floor to help get signal to the far flung reaches of the estate. I’m Cisco Linksys RE100 Range Extender. I configured it to use the same SSID as by WAP. Although this works I may have created some issues for myself:
- When devices first connect to the network they select an access point based on signal strength. This may not be optimal as the repeater introduces some delay and selecting the base station might provide better performance even with a weaker signal.
- When roaming the client devices may not release the original access point at the optimal time/location when mobile. They will typically hold on to the current access point until the signal is excessively weak.
- SSID – I’ve been hiding (not broadcasting my) SSID for as long as I’ve had an access point that supported the feature. At one point I had even configured an old WAP as a honeypot (I stopped when the number of visible SSIDs on my street topped 2 dozen. It turns out I may have been creating some additional problems for myself. I have recently learned the SSIDs were never designed to be hidden and the security through obscurity effect is minimal if present at all. Long story short: I no longer hide my SSID.
- 2.4GHz vs. 5GHz – Similarly to the repeater configuration, I had been configuring both my 5GHz network and my 2.4GHz network to use the same SSID. Again, while this is supported, it can be sub-optimal. It turns out that most wireless devices do not prioritize 5GHz over 2.4GHz so it will select one network over the other based on which beacon it sees first. I now use a different SSID for each frequency.
I don’t actually use a repeater/extender anymore. Since I’ve moved to an ASUS AC1900 RT68u I’ve found that the range is more than adequate for our manse.
So what are the lessons learned?
- Avoid using the same SSID for a range extender and a WAP
- Avoid blocking the broadcast of the SSID
- Avoid using the same SSID for both 2.4GHz and 5GHz networks.
I’m not a networking expert but I know enough to get myself into trouble. I hope these tips can help you stay out of trouble and get the most out of your Surface and other wireless devices.