Today the new logo for Finit3 was added to the GitHub repo and the homepage

Finit3 logo

Gorgeous, isn’t it?! :sunglasses:

This fancy artwork means we’re nearing the end of a long and agonizing release cycle where a lot of the internals of Finit have been rewritten and new exciting features have been added! More on this in an upcoming post :smiley:


OK, so here’s the general idea: take one teaspoon of a well equipped SBC with Marvell chips you know well, add an awesome WiFi hotspot with USB connection, stir feverishly for several weekends in a row, then sprinkle some AlpineLinux and a custom kernel on top. Enjoy!

I have no clue if this will actually work, may even try porting my own little thing called TroglOS to the ClearFog first, I don’t know, but it will definitely be awesome! :smiley:


With the new servers and my server room shaping up, I’ve been working on setting up ALL THE THINGS! I just managed to set up live migration of the KVM virtual machines I use for testing my FLOSS projects. Here is a short writeup of that, just as a reminder for myself.

Checklist

  1. Make sure the libvirt versions are the same. I tried setting up migration between CentOS 7.2 and and Ubuntu LTS 16.04 which turned out to be a mess of insurmountable incompatibilities. I’ve now gone back to run Ubuntu on everything and it all works fine.
  2. Set up NFS for the backend store of /var/lib/libvirt/images. Make sure to export the share properly, I tried first with my ReadyNAS, but couldn’t set up root access (defaulted to nobody).
  3. Set up VM disk caching=none
  4. Set up VM processor model=default
  5. Profit

Good Luck! :)


The other day I got my geeky hands on two old SuperMicro X8STI-F 1U servers. I plan to use them as build and embedded target emulation servers for my open source projects as well as Minecraft server for my kids :)


GRE tunnels are useful in many ways. This blog post shows how to set up multicast routing with pimd over a GRE tunnel. To achieve this we will also set up OSPF over GRE with Quagga, because PIM, unlike DVMRP (mrouted), require unicast routing rules to be established.

        .----{ Intranet }----.
       /    192.168.1.0/24    \
      /                        \
 .10 /                          \.20
 +--'---+.1   GRE Tunnel   .2+---`--+
 |      |====================|      |
 |  R1  |   172.16.16.0/30   |  R2  |
 |      |                    |      |
 +--.---+                    +------+
    | .1                        | .1 
    |    10.0.1.0/24            |    10.0.2.0/24
    | .2                        | .2 
 +--'---+                    +--'---+
 |      |                    |      |
 |  C1  |                    |  C2  |
 |      |                    |      |
 +------+                    +------+

In this post we are using the home WiFi network, 192.168.1.0/24, to hook up the GRE tunnel. It is just as easy to extend this to a big corporate Intranet with more routers between R1 and R2. As long as that IT department takes care of the unicast routing between R1 and R2 so that the GRE tunnel can be established.