Today I’ve spent a little bit of my time to figure out how to move away from policy-based VPN in favour of a route-based one instead. I was eyeing the concept for a while now and wanted to use it in my home lab to solve a couple of problems I was trying to turn a blind eye to. Without further ado, please follow the guide below to set up a route-based VPN between a StrongSwan-based peer (on RPi 3+) and an OPNSense appliance.
This afternoon was spent on searching for ways to auto-register clients and assign them into different policies based on whether they’re virtual or not and, to my surprise, I couldn’t find an out-of-the-box way of achieving this with Zabbix.
After looking into different Zabbix agent calls and modules, I found a way I could use to reliably tell whether it’s a baremetal machine or not.
It’s a great feeling to have a server! It’s lovely to have it running. It’s nice to know that it’s running. It’s not so nice to come back after few days just to find out our server has, in fact, decided to stop running.
In this article, I’d like to walk you through basic Zabbix installation on a new VM so in future we can set up some alerts that are going to warn us when something funny is happening to our precious website!
Unless the monitoring dies as well, of course…
Since our Debian VM is up and running, let’s do something cool with it! We’re going to get our own WordPress website running on top of a LEMP (Linux, NGINX, MariaDB, PHP) stack. As a bonus, I might also moan a little about my daily commute!
This is the first post of upcoming series of posts about servers – their deployment, automation, load-balancing and configuration. In this introductory bit, we will focus on deploying our first Debian VM.