Daily Archives: 1/3/2018

A brief review: Google WiFi

Over the last year or so, more and more of the video content that I consume is coming by way of streaming over the Internet. Very nearly every device that I have (TV, phones, Google Chromecast, Amazon Fire TV stick, and even my completely unremarkable Blu Ray player) has the ability to use WiFi and stream content from Netflix and YouTube. A little more than a year ago, we shifted from Comcast (boo!) to Sonic (yeah!) and the Dish, which also opens up some On Demand streaming.

So, it’s fair to say that we are placing a bit higher demands on our WiFi network. Sonic actually repackages ATT U-verse (DSL) in my neighborhood and gave us the usual modem/wifi access point. On paper, it wasn’t that bad a device: it had both 2.4Ghz and 5.0Ghz radios, in addition to four ethernet ports. It also serves as a VOIP server, and handles all my landline phone.

I really like Sonic, and mostly like The Dish Network, but early on, I began to be pretty dissatisfied with the quality of the WiFi network. Our modem was in an upstairs bedroom, it was clear that throughout the house, we had some dead spots where coverage was pretty mediocre. Sometimes the 2.4Ghz band seemed to penetrate better and give better performance than the 5.0Ghz band, even though the 5.0Ghz band had greater bandwidth and better theoretical performance. What was annoying was that the access point presented two different SSIDs, and if you found one better than the other, you had to manually switch. That wasn’t such a bad deal for your phone or laptop, but it was annoying with the various TV devices that didn’t store common configurations and allow you to switch between them. Additionally, my neighbors seemed to be going WiFi mad as well, judging by the number of new SSIDs that appeared in lists when I tried to connect. I wondered if they were causing contention. I could have tried to optimize the placement of my access point, or added additional repeaters, or bridge networks…

All this seemed like a lot of work. I’m not an idiot when it comes to this kind of stuff, but neither do I really want to spend a lot of time developing a complex network plan. I already have enough things that I’m not getting to: spending my time working on fixing my WiFi network seemed no more fun to me than it would be to lay new telephone and electric wires to my house. I just wanted to get something that would improve my network connectivity throughout my house, and not generate a whole lot of new “opportunities for learning.”

I spent a bit of time thinking about it, and since I had some spare bucks in my Amazon account, decided that spending some money might be in order. I thought that overall the reliability of the base network to my house was fine (a quick survey of speed tests with my laptop plugged directly into the Ethernet of the access point seemed to confirm this) but I needed a better WiFi solution.

I could pretend that I did a lot of research, but really all that I did was go on Amazon and look for highly rated solutions. I came up with Google WiFi as being a highly rated solution, which included nodes which combined to form a mesh network which promised easy configuration, better coverage and higher performance. Knowing that Amazon was very good about returns, I rolled the dice and bought it. Two days later, a box arrived at my front door.

First impressions out of the box were excellent. The quality of the packaging was very high. There were three “nodes” which are all identical in the box. Each is powered by a provided AC adapter which uses USB-C connectors. Each node also contains a pair of Ethernet ports. The box included one Ethernet cable as well. The nodes and cabling are all physically high quality.

Most routers that I’ve had before were configured using an on-device web server. The Google WiFi system takes a different approach: it requires the use of an app on either your iPhone or Android device. It I have an iPhone, so a quick download from the App Store, and I was good to go.

The first thing I did was disable the WiFi on my existing access point. I logged into the device (maybe for the last time) and disabled both the 2.4Ghz and 5.0Ghz radios. I then fired up the app on my phone, which started setup.

It was very clear and easy to follow. Basically I plugged the Ethernet cable into my existing access point and into one of the three nodes. I then powered it on. The app contacted the new node, and then asked me to scan the Q-code which is on the bottom of the device. It tried to contact the Internet… and failed. It rebooted both the access point, and the new node and… still didn’t connect to the Internet.

I then had some dim recollection that the old access point had some differentiation among the four Ethernet ports on the back. I had plugged it into the third port (it was open) but decided that maybe it should be in the first slot. I changed it, and voila! Network access achieved. It asked me for a new SSID, spent a few minutes configuring, and then it was up.

It then asked me if I wanted to install any additional nodes. I had two, so I said yes. I put one at the other end of the house, and one downstairs. It was easy, you just plug in the nodes, the app finds them, adds them to the network and configures them. It basically creates a single, bridged virtual network, all of which is accessed by a single SSID.

Once all the nodes were added, it informed me that they were doing an update to get the latest software from Google, and that it would inform me when the update is complete. It took about five and a half minutes to complete.

And… it was like the clouds opened up (or at least the tubes of the Internet did).

So. Much. Better.

There were times when I was lucky to get 1.5Mbps to my devices. Starting On Demand streaming required a couple of minutes wait, and you might expect to hit pauses while watching it because the buffering was unable to keep up with the device. The idea of streaming 4K content from netflix to my cheap (but remarkably good) $400 Hisense television was impossible.

But not now. Every device in my house seems to be able to access at least 20Mbps, and often 30Mbps or even higher.

Dead zones? Gone. I can sit anywhere on the couch I want, and with good connections! Huzzah!

Total time to setup the network was well under 30 minutes.

I was a bit leery about relying on an app to control the network, but I must say: the app is great. It is much more responsive than the typical web based controls that most routers offer. You can check network health even when away from your home network. It lists all the active devices and access points, and can tell you of any outages. You can share network configuration privileges with others by providing their email address, which is kind of nice. You can easily configure a few of the most important settings, and can easily add port forwarding or configure IP addresses to individual devices. You can also set priorities between devices, or configure “family off times”.

If you like spending time configuring networks and firmware, and think that flashing new firmware like DDwrt or Tomato to your routers is fun (I’ve been there) then this may not be the product for you. But if you just want a network that works, with a minimum of fuss and a reasonable set of features, then I can recommend Google WiFi.

Addendum: Here’s another review from Forbes, with more screenshots..

On the allure of Quora and plans for a new brainwagon future.

For several years, this blog was my major creative outlet on the Internet.  Facebook was founded in February of 2004.  Twitter was founded in March of 2006.  But I was already using WordPress to scribble down random bits of flotsam and jetsam as early as July 21, 2002.    Over the next fifteen years, I’d write 4,211 posts about random stuff of interest.  At my peak I’d get maybe 300 views of my stuff per week.  The topics were wide ranging and eclectic, which basically matched the way my brain works.  I concentrated mostly on geeky stuff.  For a while there was a lot about podcasting (and I recorded 100 episodes of my own “brainwagon radio” mostly while commuting).  I posted a lot about amateur radio.  I wrote little bits of code.  I tinkered with Arduinos.   I talked about cryptography and computer graphics.  I scribbled notes to myself about things that I thought I’d need to remember, like how to use ssh to do tunnels through my firewall.  I read and passed on notes about people who built their own CPUs.  I took photographs.  Occassionally, I’d write a little about politics, or announce the release of a movie that I had worked on.

You never knew what you were going to get.

Some 300 or so people a month visited my blog.  Those were the real viewers: WordPress was pretty good at getting rid of the 760,000 (and counting) attempts to inject content spam onto my blog.

But in 2015 I suffered an injury to my neck that laid me up for a few weeks with terrible back pain and arm weakness.  It recurred in 2016, even worse.  I ended up having to have two different injections in my C6/C7 vertebrae, and was in constant pain through my left arm, which became really weak.  I was out of work for 60 days.   As I sat around recovering, I discovered Quora.

Quora is a question and answer website. Anyone can create an account and ask and answer questions on a wide variety of topics. I was stuck at home. Injured, bored, and unable to do very much without making myself ache, I started to read and answer questions. At first, it was mostly about stuff I knew about: computer graphics, astronomy, and telescopes. But since I was sitting at home, I was also watching a lot of political news of the day, so I started answering questions about that as well. The run up to the election in 2016 gave me lots to think about, and I had lots of time.

I didn’t think too much of it at first. Then I had my first answer that received one thousand views. Pretty soon, I had answers which received one thousand upvotes. People started to follow me. I reached one hundred followers. Then one thousand. Then five thousand. As of today I’ve got about 7,200 followers, and over nineteen million views, and written around one million words spread out over 6,785 answers.

It was obvious to me that Quora was a much more powerful platform than my blog ever was. I received Top Writer status for both 2016 and 2017, and they sent me a nice laptop bag to proclaim my status.

I have to say that this appealed to my ego, and as a result, it began to dig into my time that I normally would have spent on my blog, which slowed to a trickle over the last six months. It’s not that I haven’t done anything interesting and Quora is taking 100% of my time. I upgraded my soldering equipment to include a hot air rework station and a better soldering iron. I started to import lots of cool modules and stuff from China and play with them. I ordered a kit for a 3D printer and built it.

But I had stopped writing about the things that I do, and instead spent that time answering questions about stuff which mattered less to me, but which were (apparently) interesting to more people.

Over the holiday break, I began to consider where this state of affairs had led me.

Yes, it’s flattering to get comments and followers. It’s easy to add your voice in the form of opinion or indignation, and in a political environment where you feel like you need an outlet, it can be quite attractive to use easy outlets like Facebook, Twitter or Quora to vent.

But it’s not really what I want to be doing. Or at the very least, the amount of effort that I am placing in that area is out of proportion to its importance.

My blog was about stuff that I liked and stuff I was doing. It was intended to be half documentation and half inspiration. The documentation was often for me: to remind me of the stuff I had learned and might need again. The inspiration was to get others to look into the same sort of things that I like, and to come talk to me about them.

Quora doesn’t serve either of those purposes, but it is taking all of my time. So, I’m trying something new in 2018.

I’m trying to dedicate just thirty minutes of my day to do something and write about it on my blog. It doesn’t matter what it is. It might be a recommendation for a book I enjoyed. It might be projects I’m working on. It might be a review of some tech product that I found especially useful. It actually doesn’t matter what it is. It will begin with something I’m doing or thinking about, and something which I think might be worth sharing. If any of my old readers (or any new ones) find anything interesting, I’ll hope that you’ll follow my blog and comment. I’ll probably work on ways to make sure that it is as easy as possible to do so, and I might even start thinking about using a platform like YouTube to do interesting and engaging stuff. But my goal is to get back to discussing the stuff that I find fun and interesting.

I hope that you will find it so too, and come back again soon.

brainwagon.org should now redirect to use HTTPS

I set up a plugin so that trying to access http://brainwagon.org should now automatically redirect to use https and the HTTPS protocol.   If anybody has any difficulty with pages, drop me a quick comment here, or a note via twitter (@brainwagon) and I’ll try to see what’s up.

Coming soon: my review of Google WiFi, plus my experiences with the Anet A8 3D printer.

Happy New Year!

Well, I have decided to do a little well needed maintenance on the blog.  I installed an SSL certificate so my blog will now be available via HTTPS, and played around a bit with a U2F Zero dual factor authentication key.   My goal for the New Year is to try to spend 30 minutes every day working on my blog, which I am going to take from the entirely too much time I’ve spent on Quora.   Stay tuned for more stuff to come.