Skip to main content

Travel Routers Part 6 - KissLink

The KissLink router is probably the easiest router reviewed so far but not without it's challenges.

The connection process is pretty simple, just touch your NFC device to the KissLink and you're just about there. If you have a static device like a laptop it's almost as easy to connect. There is no fileserver; but who cares really? The Android application is OK but far from rock solid. Depending on the connected WiFi network the app get's lost. Also updating the firmware requires that the "device" is the admin device before the messages make any sense.

  • router(requires ethernet) and repeater/bridge mode
  • Clone MAC but who cares
  • white and black list
  • no logging
  • what does the "zen" button do?
  • no VPN
  • too big to be a travel modem
  • uses USB power
  • no QoS
  • Since the documentation talks about "static" devices like laptops I'm not sure whether the Chromecast setup is going to work. 
  • hidden SSID
I'd like to say that the KissLink application is useful and unique but it's not. They tried to look like OnHub or vice versa but wins the close but no cigar. The more error paths I went down the more I realized that the basic documentation was incomplete or popup error messages were just wrong.

There is something to be said for being able to add devices on the fly based on NFC. Considering how often we travel vs how often we have no devices. It is also interesting as a way to let guests into my network and in bridge mode I can locate it in more accessible location.

Popular posts from this blog

Prometheus vs Bosun

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


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…