Skip to main content

Travel Routers Part 5 - early pro/con

After doing some testing I have made some early observations.

ZyXEL - pro
  • small and light
  • several modes
  • WPS button which I have NEVER used
  • no battery - nothing to recharge or discharge
  • supports DDNS
  • firmware is current suggesting it's stable (2013)
  • some logging
ZyXEL - con
  • no battery therefore impossible to be mobile
  • many tasks require reboot and it's not clear from the menu
  • no users per se
  • no VPN
  • rebooting can require multiple reboots
The biggest hindrance to the ZyXEL seems to be speedtest.net and QoS. I tried a speedtest with QoS disabled and the performance varied widely. I suppose there could have been some spectrum competition with my neighbors but the results were consistent and so I think it's the device. When I enabled QoS the device took a dump. The GUI indicates that the QoS bandwidth is measured in kpbs, however, never really go there.

FileHub - pro
  • speedtest was normal and nearly full speed.
  • supported hidden SSID (great for hotels)
  • GUI auto detected and displayed a popup when I inserted a USD drive
  • into my second hour and the battery indicator is still on 3. It must be a curved scale so that 4 is 100% and 3 is not 75% (25% per indicator) so that 76% is not considered full. Correction, the documentation says 4 LEDs is 75-100%. I guess the factory change was just over 75%.
  • confirms in the DOC that Chromecast is supported
FileHub - con
  • there is an option to change the hostname. I suppose that the hostname must be an indicator to the upstream network device but it's not crystal clear. I'm not sure I want to identify myself either.
  • Changing the SSID caused the GUI to appear to hang which only meant that the SSID changed and I had to update the connection; not so obvious but not unusual
  • no file download feature but I can upload. Samba support would normally be a pro, however, since I can already upload but not download samba is just a curiosity. 
  • SECURITY - the guest user was ON by default. 
  • SECURITY - the samba service was ON by default.
  • disabling samba displayed a curious warning message, however, disabling the guest user did not.
  • no VPN
  • only the admin and guest user; which is not a strong 'con' but it is not immediately clear what a user can do
  • removing a mounted USB flash drive meant navigating to the "information" menu. This was completely counter intuitive.
  • not certain what happened when I tried my USB HDD. Since the drive was a MacOS filesystem it should not have been readable, however, an error would have been nice.
  • upgrading the firmware caused some features to be reversed...(check those security settings)
  • no logging at all. How am I to know if I'm under attack while traveling. The Router is the first point of attack and if penetrated could leak everything.
One thing I learned from the Sandisk Connect and Sandisk Media Drive is that one can conserve a lot of battery if you download the media instead of playing over the air. Granted the FileHub has a big battery but then things get complicated when the battery is empty and you try to use your laptop's battery to prime the device just to get a few files from it. On the otherhand the media is portable itself so if you are out of battery you can move the media to your laptop. But then why use it in first place.

** I should try one of those media sticks that has a USB and micro-USB. But it's not part of this review.

UPDATE: in a small benchmark I copied a file from my laptop to a USB HDD in 1:05 and to a USB flash drive in 7:36. I was able to download the same file from the FileHub USB flash drive in just under 3:30.

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…