It's also amazing how prevalent Ethernet still is, even when wireless is a competitor. The other day I left this comment: http://news.ycombinator.com/item?id=5052448 on HN, because in some circumstances running a cheap ethernet cable from a router to a desk, couch, or other work station can still be a real win, especially given how inexpensive even very long ethernet cables are from Monoprice.com.
They last forever, aren't subject to the level of interference wireless is, and, in many conditions, have faster data transfer speeds. Ethernet is still great.
Take away "in many conditions" and replace with "always, without exception" and replace "faster" with a "at least a magnitude faster" and we are in agreement.
If you need performance and reliability (like for instance for iScsi) there is really nothing which even compares to wired ethernet.
Note that in most cases wireless systems are far slower than theoretical speed, but 100Mbit wired ethernet is good for 90+ in both directions simultaneously, so in most cases it'll be faster than 802.11n, and with better and more consistent latency.
Someone measured the difference in transmissivity for different materials at 2 and 5 GHz (http://www.ko4bb.com/Manuals/05)_GPS_Timing/E10589_Propagati...) - the difference is quite large for brick and cinder block; unfortunately, they didn't measure insulation foil, which I expect would be quite a good RF shield, especially if earthed.
So if everyone switched to 5 GHz, the interference situation might still be better than if everyone was on 2.4 GHz.
Of course, being an early adopter of 5GHz probably helps with the other problem in apartment buildings, the 'prisoners dilemma' type problem where everyone who knows how ups their transmit power because of the noise, making the problem worse for everyone else but temporarily better for them, when if everyone lowered their power, everyone would get better speeds (exactly analogous to how everyone ends up shouting when having a conversation with the person next to them at a party, when if everyone talked quietly instead communication would be more successful).
Increase the beacon period of your router/AP to the fastest it will go, usually 20 microseconds. I think this is the best solution of anything you could try.
Maybe play around with the DTIM interval but I'm not sure what a good number for that is; too low supposedly drains batteries of wireless devices and too high causes other problems.
Max out RTS/CTS but you may lose overall throughput but that's no loss if it suck already, in for a lamb in for a sheep.
There are other settings too most explained in the help section of the AP/router help menu. They can be obscure but fiddling with them can help your AP signal a lot.
That's my unofficial educated guess theory.
The best bet it to switch to 5GHz, but that isn't practical for use with mobile devices.
Option B is to turn off the higher speed modes like 802.11n. Just try to stick with 11g. If you are still having connection problems, maybe switch down to 11b, but that will be real slow even when it works.
If you use an access point with detatchable antennas (which is actually most of them if you open the cover), then maybe replace the omni-directional antenna with a high-gain directional antenna (also known as a patch antenna). Then you'll need to point the antenna at where you sit.
Another (probably lousy) option to try (but very quick and cheap) is to move off of the commonly used WiFi channels (1, 6, 11). They are commonly used because they don't overlap with each other. So maybe try 4 or 9. The downside is that you will get interference from two commonly used channels, but the overall situation may be better than what you've got now.
Although I do agree with your advice about channels I often get relatives to do that as they first step in troubleshooting problems with their home wireless network.
People have all those adjustable router options they may as well try something rather than default settings. You don't have to design wireless devices for a living to fiddle with a few settings.
You say "switch to 5GHz, but that isn't practical for use with mobile devices" -- is the reasoning that the 5GHz signal doesn't penetrate the walls enough as you walk around with the device?
The short version is that, depending on your usage, you may run out of NVRAM before RAM and may lose your settings. For reference see [1] and [2].
[1] http://www.dd-wrt.com/wiki/index.php/Asus_RT-N16#Current_Kno... [2] http://www.dd-wrt.com/phpBB2/viewtopic.php?p=506126
I have 32MB NVRAM to play with and that has served me well enough, but I see plenty of consumer-routers which can be "upgraded to dd-wrt" but which doesn't even have enough NVRAM to do an ipkg update.
You're sure about that? I've had an rt-n16 sitting on a shelf for over a year waiting for OpenWrt support. Your message caused me to go check their website, and all it says is:
"The Asus RT-N16 has early support in Barrier Breaker (trunk) only!"
http://www.dd-wrt.com/wiki/index.php/Asus_RT-N16
there is support for dd-wrt, apparently since late 2010. You understand that Barrier Breaker is pre-release, right?
I am uninterested in dd-wrt, which is why I didn't mention it.
When I was in the market for something like that one or two years back, I was recommended a specific type of Buffalo Router [1]. While I see my particular model has been superceeded by newer ones, I still thought I'd mention it because:
1. It was recommended to me by someone who had been served it extremely well by it in the past. It has now served me extremely well for years. It will probably do you good as well.
2. It's OK to support more than the top 3 vendors in the world with your money. This leads to more competition, more diversity and better products.
3. Putting stock dd-wrt or openwrt on it can be done all in browser and doesn't seem to involve brick risking procedures like bootloader updates, like I see you may have to go through for the Asus router.
The one thing I'm worried about though is whether that setting of 63 is worse for shorter distances. From my limited experience with building a simple radio transmitter/receiver and amplifiers, if your received signal is too strong it'll just saturate and turn to crap, and as it happens my bedroom is right next to the room with the router in it, so boosting the signal might screw up reception on my phone. But at least now I know that there's room to play around here, thanks for letting me know!
I used to do this until something happened at my ISP and my router can no longer authenticate against my ISP's PPPoE server. Now I have my modem providing NAT and DHCP, and my router is just a dumb access point. The only problem is my modem has an externally accessible administration page running on port 4567, and telnet on port 1111 that I can't turn off, even when all remote management configuration options are turned off. I've had to set up a cronscript to attempt to telnet into the thing continuously, and if successful it will kill the httpd server and telnet daemon.
It's absolutely ridiculous how insecure home network equipment is.
But remember not to leave your wireless access open to passers-by. That helps hackers, and Al-Qaeda, and pedophiles, and drug dealers! /sarcasm
There is a good reason why reverse shells exist.
Cable companies might still ship modems (they did the last time I had cable internet, but that was probably 8 years ago).
Amusingly, they always set the SSID to 'insight_wifi_XXXX' and their formula for WPA keys is `firstname[0] + lastname + housenumber`.
That coupled with a router/wireless ap running tomato or the like should work well from what I understand. I, however, never have used DSL so I'm not an expert.
There's nothing to return, I get DD-WRT instead of whatever garbage they're running, and usually measurably faster in both internet speed (usually lower latency) and wifi speed. In particular, I've never had a bundled device get within 50% of what 802.11n is capable of, especially when you have 4 or more devices. All my dedicated routers have done just fine.
It's a free firmware and great other than QoS but who am I to complain :/
The other router mentioned in this article, the Linksys EA2700, doesn't seem compatible with third party firmware. And apparently the Cisco firmware is buggy, no surprise there. It is an awfully cheap Dual-Band 802.11n router, but if you can't put working software on it it's useless.
I don't understand why some major router manufacturer doesn't just sell routers pre-installed with Tomato. It's easy to use, stable, and works way better than any crap the router companies cobble together. Flashing new firmware on a stock ASUS router is too complex for ordinary consumers.