Homebrew router faces better tests, tougher competition
arstechnica.com
arstechnica.com
Sure, I could build something x86 that uses more power and costs 2-3x the price, but it's nice to have a single box that "just works".
Every year or so I look to see if there's anything better, and for the past 2-3 years I have yet to find anything. I had been using the ERL, then bought an ERX when they came out, switched all my stuff (including ipsec VPN tunnels) over to it to "test" for a while.. and then a year later, I've not had a driving reason to switch back to the ERL yet. The ERX is flat-out amazing for ~$50.
I have a system on the "outside" (static IP, hosted server) and then all my "internal" stuff is behind the EdgeRouter's NAT. Hence, the desire to have near-gigabit for when I'm transferring stuff to the server on the "outside".
I like Ubiquiti gear; in fact today I set up a UAP-AC-LR access point to test against the performance of my Google OnHub, which is a year old and seems to be kinda flakey lately..
Anyway, great little boxes. I'm also very happy with the AC lite APs.
Btw, I originally started with Vyatta years ago on a spare PC after outgrowing a SOHO router. I was very happy when Ubiquiti forked off from that.
http://www.pcengines.ch/apu2.htm
It also isn't reliant on binary kernel blob drivers to obtain full speeds, so you arn't stuck on old kernel versions in the future with known exploits.
Also, if this list ever does grow to be more than two screens long, please add actual filtering rather than just sorting; some of us are only interested in routers that don't need proprietary wifi drivers.
As for the C2600, I do not believe it is stable yet, and still being worked on. I deliberately don't put "trunk" only builds on the page because not everyone is sufficiently technical to deal with them. It should show up soon though by the looks of things (will be stable soon-ish).
If this is really aimed at the less technical/experienced crowd that can't cope with the command line, then you need a lot more background information explained: the hardware revision bait and switch business model, what the benefits actually are of open-source router firmware, the major differences between DD-WRT and OpenWRT (and LEDE). Explain that Broadcom WiFi is about as open-source friendly as NVidia graphics, and that DD-WRT can do very little to help with WiFi issues on those hardware platforms.
It would be great if you could offer guidance for what constitutes fast enough, ie. that "tri-band" routers won't help anything, client WiFi devices don't support more than 3 streams, and an ARM processor isn't necessary if your WAN is only 100Mbps. Also add warnings for devices that only support 100Mb Ethernet on the WAN port or all ports, and make sure to cap the amount that their WiFi speeds can contribute to the performance score.
Alternatively, if your target audience is people who know generally what kind of hardware they need and just need to know which product currently delivers that at the best price and with third-party OS support, then add filters on major categories like NIC vendor (BRCM/QCA/MTK), built-in flash quantity (because 8MB isn't always enough), and radio MIMO class.
More generally, it doesn't serve the public good if your chart is just abstract bragging rights that can be gamed by things like including more RAM than necessary or a useless extra radio for a 150% price increase. The market should be discouraged from producing overpriced overpowered devices that have no real-world use, even if they are to some extent hackable.
https://www.reddit.com/r/Ubiquiti/comments/4owurp/erl_vs_erx...
> The newer firmware certainly delivered higher peak throughput: up to 800mbps or so, if you click your mouse just fast enough at just the right point of one of the easiest tests. I'm not sure that's an "upgrade." The improved peak throughput comes at the cost of stalled connections, peaky and unpredictable ceilings, and tremendously degraded throughput in the more demanding 10K tests. This would be a downgrade for someone with 100mbps or 200mbps cable, in my opinion.
[0] - http://openvswitch.org/
I should probably do some testing to see its real throughput, to see if my efforts were worth it. I should blog about it too, because it's likely a unique setup that would be interesting to others.