Simon Oakes soakes

Be sure to replace the Mikrotik IP & the DHCP network (see line 8, "network set #")

Mikrot IP: 192.168.88.1/24 DHCP network: 0

/tool fetch url="https://boot.netboot.xyz/ipxe/netboot.xyz.kpxe"
/ip tftp add ip-addresses=192.168.88.0/24 req-filename=netboot.xyz.kpxe real-filename=netboot.xyz.kpxe allow=yes read-only=yes
/ip dhcp-server network set 0 next-server=192.168.88.1 boot-file-name=netboot.xyz.kpxe

UniFi Network Application on MikroTik RB5009

Self-hosted UniFi Network controller and MongoDB running as two RouterOS containers on a MikroTik RB5009UPr+S+, backed by a USB stick split into swap and ext4 data partitions.

Part of a larger home-network build — full write-up with topology, VLANs, IPv6-over-WireGuard, and rationale: https://blog.homestack.space/mikrotik-home-network

Hardware

Router: MikroTik RB5009UPr+S+
- CPU: Marvell Armada A72 (Cortex-A72), ARMv8.0-A, 4 cores @ 1.4 GHz

In the machine.config file under these 2 folders:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config

Add this configuration in the bottom (before the last closing tag):

<system.net>

On the host

Ensure these modules are loaded

cat /proc/sys/net/bridge/bridge-nf-call-iptables

Disable swap

sysctl vm.swappiness=0
swapoff -a

Proxmox Assign Bind Mount To Unprivileged Container

In order for the LXC container to have full access the proxmox host directory, a subgid is set as owner of a host directory, and an ACL is used to ensure permissions.

Bind Mount dataset to LXC

Add the following line to /etc/pve/lxc/<CT_ID>.conf

mp0:/mount/point/on/host,mp=/mount/point/on/lxc

Create group on host

In the default Proxmox configuration, unpriviliged container subgids will have the prefix "10" followed by the expected 4-digit gid.

Haproxy conditions

Since I keep forgetting them I've put them here.

To form a condition, you can use the following syntax after the rule that it applies to:

<HAProxy action statement> if|unless [!]acl1 <AND|OR|or|'||'> [!]acl2 ...

if - the condition is TRUE if the result of the ACLs is TRUE.

Proxmox VE Installation on Hetzner Server via Rescue System

Follow these steps to install Proxmox VE on a Hetzner server via the Rescue System. The Rescue System is a Linux-based environment that can be booted into to perform system recovery tasks. We'll be using it to install Proxmox VE.

In order to complete the process, it is indeed necessary to first boot into the Rescue System and then connect to it via SSH. This will allow you to run the commands for installing Proxmox VE. Here are the steps:

Starting the Rescue System

Log into the Hetzner Robot.
Under "Main Functions; Server" select the desired server and then open the tab "Rescue".

	# should works on any cloud-init enabled hypervisor (openstack.. )

	# start from a normal ubuntu 20.04 install as minimal was not available for ARM64
	# Since ARM64 machines has higher RAM, Shrinking is desired but not necessary. Instead we will increase tmpfs to 1700MB

	# Getting root (if sudo -i doesn't work then set a root password beforehand using 'sudo passwd root'

	sudo -i

	# make sure we are on the highest kernel, so we can delete all the others ...

	#!/bin/sh
	#
	# Perform certificate updates in Vault.

	set -eo pipefail

	if ! vault token lookup > /dev/null; then
	echo "Login to Vault first."
	exit 1
	fi