Let’s ssh in!

You’ll need to ssh into the Flint2. Assuming you have set the ssh port to 22 (under System/Security on the web interface) you just ssh root@x.x.x.x and use your admin password… and boom root it is:

Overlayfs magic

The Flint2 uses Overlayfs to allow persistant file addtions to key directories. The one we care about for this is /usr/sbin… that’s where we’re going to “install” (really just copying an executable script in) muninlite. You’ve got about 8gb of storage built in, plenty for our needs.

Muninlite

Install Muninlite from the admin web interface:

Next, we will edit muninlite to see only relevant interfaces. Sadly I don’t recall if I needed to copy muninlite to /usr/sbin/muninlite or if that’s where the system installed it. Anyway, fire up you faviorite editor named vi, and search for the line containing eth0. You should end up here:

I’ve commented out the original line, which gets you a bunch of redundant graphs. In my case I have one ethernet connection out, one in (from the cable modem), and then the br-lan interface is the flint2 hybrid combo of all lan interfaces. That’s mostly all you need. If you want to verifiy which interfaces are being used, run ifconfig -a and see which have RX/TX data.

Once you’ve modified the line as desired, you’re all done on the Flint2.

Getting Graphs. Running Munin somewhere.

Pulling the node data from some other local machine is beyond the scope of this post. If you’re running Munin on a local machine in the network, it needs to know that this machine exists, can be ssh’ed into, and what to run (muninlite) when it does ssh in.

Something like this:

[router.noip.me]
    address 10.0.0.1

See the readme section of the muninlite github page here: https://github.com/munin-monitoring/muninlite

Assuming you slogged through all of that, you should end up with something wonderful like these graphs:

Pages: 1 2