Skip to main content

Travel Routers Part 2 - ZyXEL NBG2105

Diving into my ZyXEL travel router I had one mission and that was to get my Chromecast v2 to setup in a hotel. Since I'm no longer in a hotel some features are intellectual only.

  • The initial boot took about 1:12 but shortly thereafter it seemed to reboot. Since it was not connected to the internet it's unclear what just happened.
  • In a hotel I'm likely to be in the WISP+UR mode so I had to change the rocker switch and reboot again.
  • Search as I might the manual was very unclear how I was supposed to connect the router to the existing access point. But then I found the magic: Wireless LAN > Site Survey. From the site survey you select the SSID of the node you want to bridge to and enter the password. The router will immediately reboot and a timer will start.(**)
** The timer is insufficient and the local WiFi will likely redirect to the preferred or one that is locally available so when the travel router completes the reboot you'll have to reconnect to the ZyXEL.

Before I take this router to a hotel I need to change the SSID, default username and password. Since I'm experimenting I'm not sure whether or not I want to name them all the same or if each should be different.

As for the Chromecast, my expectation is that once the travel router is online and ready for normal operation (estimated 7 minutes) the setup will be uneventful.

UPDATE: I should add that the UI is OK but VERY old school.

UPDATE: can not auto detect firmware updates. (latest firmware here) The latest seems to be 06-25-2013 however the info is pretty unclear.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…