One of the big things that people don't realize is that bandwidth of wireless is split between every device on that channel. So if you are streaming to your TV/roku/xbox/etc over wifi, you are killing the bandwidth for your laptop and phone as well. Plus, if you live in a city your wireless bandwidth is pretty much guaranteed to suck because every ISP includes wifi with their modems, destroying the noise floor. Comcast modems are a particularly notable example, as they have a "public" 2.4 ghz network in addition to the "private" 2.5 and 5 ghz networks. There are no fewer than 30 wifi networks available inside my house when I check on my phone, and I live in a row house with metal lathe under the plaster, which greatly attenuates wifi signals.
I think the biggest barrier to wiring things is that patch cables are incredibly expensive if you buy them at Best Buy, etc. Most non-technical people I know only own the patch cable that came with their modem. Once I get them wired up, they are astounded by how much faster their internet is. They don't have buffering issues, the internet doesn't drop randomly, and it just seems "faster" (which I attribute to lower latency). I toss extra patch cables in my Monoprice orders now and sell them to my friends at-cost. To be honest, it's partially for my own sanity as well, because watching Netflix at 480p on a 50/15 connection drives me nuts.
Yes. Same here. Ethernet is an oddly underrated technology. And Monoprice is one of these things that nerds know about and no one else does. There may be other companies like that—someone above mentioned an enterprise router company that sells better stuff than most consumer companies. Yet I've already forgotten its name.
Ubiquiti also makes a great series of wireless APs that are worth checking out.
My network right now is a Edgerouter lite, 2 Unifi AP AC Lites, and a used Dell 2816 managed switch.
Don't do that. Instead get a ethernet powerline adapter:
https://www.cnet.com/topics/networking/best-networking-devic...
This is like an engineer not knowing the mains voltage is 230V, or a baker not knowing about standard grades of flour.
Apparently I was grossly wrong, and I still don't understand why I was wrong and why the changes made such a large difference. Something to do with network protocols and response to packet loss or something, I guess.
I'm always posting latency numbers every programmer should know: https://gist.github.com/jboner/2841832
I had no idea that WiFi was that much better than Ethernet!
( this is why units matter, kids ;)
This is also shitty news because I had very high confidence that an Apple router would not ship with any kind of malware or other crap I don't need. Now, I have to find something better, comparable in price, and works well with Mac household.. Sad face.
That being said, the Apple APs are the fastest consumer-grade APs out there. If you are going to hit the theoretical maximum, an Apple AP is your best bet. I don't think streaming is where people notice issues with their internet though. In my experience people tend to notice issues in video games, skype, facetime, and other applications where there isn't a buffer to hide issues with dropped packets first.
However, I get ~950 mbps over the wire (on a 1 gbps connection), so I still plug in when I'm sitting at my desk and need to transmit large files.
I max out my cable modem's connection. I pay for 50mb/s, and 802.11n on a 5Ghz channel is more than sufficient.
At work however, yes, that gigabit wired ethernet connection is really nice. :)
I'm not thrilled about the autoupdate feature of Google WiFi. I wouldn't be surprised if it's leveraged to benefit Google's analytics, or for government snooping. But the greater risk at this point is from criminal hackers. And I prefer running my WiFi routers in bridging mode, anyhow, making it less likely Google will bother tracking my family's browsing from the LAN.
Maintaining my own homegrown router isn't appealing, though. For one thing, all the hardware available for that is sub-par. Solid support for MIMO and beamforming is mostly non-existent except for proprietary stacks; even simultaneous multi-channel is iffy using open source solutions. AirPort always shipped with better than average support for the latest tech, and I'm not keen on going backward in that regard, especially for what should be a performance upgrade.
https://support.google.com/wifi/answer/6246642 has a tl;dr version: "Importantly, the Google Wifi app and your Wifi points do not track the websites you visit or collect the content of any traffic on your network. However, your Wifi points does collect data such as Wi-Fi channel, signal strength, and device types that are relevant to optimize your Wi-Fi performance." and a full explanation of everything it does (or does not) collect, and why.
Apart from Apple's and Google's idiotic antics, what routers require anything more than a browser to configure?
As annoying as it is for some, the configuration interface for Apple AirPort used a simple SNMP interface. Now, lots of SNMP software has had bugs and remote exploits, but all things being equal it's a much simpler interface to export and requires shipping less code, not least because it doesn't have to support a GUI, directly or indirectly.
That said, I always configure my WiFi router (AirPort or w'ever) in bridging mode and put them behind my gateway. And I try to disable any web GUI entirely if at all possible. People who use the built-in WiFi capabilities of their Cable or DSL modems are begging to be hacked.
Not really, CGI can be written in anything, shell scripting, C, whatever. But security-wise, it doesn't much matter the language because the programmers working on the web interfaces of such embedded devices rarely do a good job.
Considering the amount of crappy C most routers have, that's probably the least of your concerns.
Good luck configuring that with a mac....
However most apartments let you 'hang pictures'; anything that leaves so small of a hole that painting over it effectively patches it.
In my apartment, the biggest issue I face is interference from other wireless routers. Because of this, the powerline performance is about 40% faster on my desktop (right above the router one floor) and much more consistent. It also does help with wireless congestion, and really helps with using my desktop as a PLEX server. Before, higher bitrates would cause serious issues, and now it just works.
I'm not sure if the tech has matured recently or I just had a good use-case for it, but it's miles better than WiFi. I'm using TP-Link's product.
For testing, I plugged them into AC outlets along the same wall in the same room, with ~14 feet separating them. After getting them linked up (very simple), I connected laptops to each unit, manually assigned IP addresses to the laptops, and used iPerf [1] to run throughput tests.
I'll spare you my rant about them but peak speeds were extremely disappointing, just shy of 50 Mbps. I honestly didn't expect anywhere near the advertised 1200 Mbps but I was expecting speeds relatively close to what I can get over my existing wireless. 50 Mbps may be quite acceptable to some, especially if one's Internet connection isn't that fast, but it was far from acceptable for me. They would also randomly "freeze" or "pause" for 20-30 seconds at a time but I didn't really investigate that issue.
[0]: https://www.netgear.com/home/products/networking/powerline/P...
[1]: https://iperf.fr
Also the idea of willingly putting noise in the electrical grid seems sketchy to me. I used to live in a house where I could not get good noise-free audio because the line was not a pure sine wave and most consumer PSUs were crappy to let noise through.
... they don't particularly want to lift floorboards, and drill through floors and ceilings if the wireless solution is 'good enough'.