81–90 of 137 posts
Installed OpenWRT, no bug. Posted on their (the company, ubiquity) forum, reply is "we don't support that and if you install it, you're on your own, we won't fix bugs!"
Oh the irony. Whoever wrote that probably didn't even realize what he just did.
I completely agree with Jeff's conclusion as well - commodity hardware + FOSS = potentially unbeatable. FOSS that has had a chance to literally evolve on the same platform for almost a decade, assuming it hasn't been abandoned, can really demonstrate the power of software evolution, for lack of better term.
1. http://www.newegg.com/Product/Product.aspx?Item=N82E16833124...
2. http://www.amazon.com/Cisco-Linksys-WRT54GL-Wireless-G-Broad...
3. http://touristinparadise.blogspot.com/2008/04/linksys-wrt54g...
I ended up chosing dd-wrt. I had some security concerns (such a technical forum stores passwords in plain text!! Does this imply anything the security of the project?) which I voiced on their forum.
Their responses shocked me: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=681593
I'm probably not going to install dd-wrt.
I disagree with the router recommendation. The Asus RT-N16 uses a Broadcom chipset which isn't well-supported by OpenWRT. Better choices would be something with an Atheros chipset, like the Netgear WNDR3700v2 or WNDR3800. Buffalo also has some nice models. Even if you don't plan to use OpenWRT itself, it's a base used by other firmware projects, so you might want to run a derivative of it in the future. http://wiki.o…
https://forum.openwrt.org/viewtopic.php?id=37069
By the way, I think most TP-Link products are using an Atheros chipset. Very affordable and really well supported by OpenWrt.
Earlier quoted context omitted.
One of the guys did answer you with: [We do sell this but] We limit the number of offices in a minimum order to 10. This was a hard lesson. We started off dreamy-eyed with onesies and twosies but were rapidly buried under a sea of "and it also has to...". Pretty much says it all. Also over here in the UK you get a free wi-fi router when you sign up for broadband from the major providers. No QoS, but auto-updating. Do…
In the US, it depends on the provider. The two giant cable telecoms I've dealt with charged ~$5/month for a wifi router which is really highway robbery - especially considering the quality of the routers they provided. Their provided cablemodems were pretty much universally awful too, so you were better off buying both your own modem and router - but they obviously didn't advertise that you could do this, if you were…
Hm. I'm kind of amazed leasing a router from TW wasn't written into the contract.
One thing Jeff didn't mention is that due to the high CPU and RAM in that ASUS router, you can be downloading several different torrents and the internet experience in general won't be degraded. With my Verizon FIOS's router, if I try to torrent anything it gets throttled down to less than 10KB/s, and on my old Linksys, attempting to torrent would make browsing the internet nearly impossible.
Wait a minute. Is it the CPU and memory factor on the router that causes the "internet is slow, somebody close your torrents" nuisance? I always thought it was the bandwidth getting choked. Could someone expand on this topic?
There are ways to mitigate that kind of thing. the simplest being keeping upstream bandwidth levels limited to slightly less than your upstream connection speed. Traffic prioritization schemes also exist letting you have some say in the buffer order ( always putting acks, icmp, and ssh first in line for instance ).
A few months ago I researched how to install open-source router firmware. I ended up chosing dd-wrt. I had some security concerns (such a technical forum stores passwords in plain text!! Does this imply anything the security of the project?) which I voiced on their forum. Their responses shocked me: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=681593 I'm probably not going to install dd-wrt.
Earlier quoted context omitted.
Wait a minute. Is it the CPU and memory factor on the router that causes the "internet is slow, somebody close your torrents" nuisance? I always thought it was the bandwidth getting choked. Could someone expand on this topic?
This is actually a two part problem. oz captured half of it (maintaining hundred of connections in the NAT state table). It can also be caused by saturating your upstream bandwidth, which causes your devices send buffer to fill. When that buffer is full you end up with your packets waiting in the buffer (which is normally fifo). What makes this very noticeable most of the time is the ack part of the tcp connection ge…