No, it’s garbage because of its approach to case sensitivity.

It’s case insensitive by default (which is a WTF in itself and encourages the same laziness Windows users thrive on with NTFS) but it also has a case sensitive mode.

Except the case sensitive mode is almost entirely useless because of the amount of apps it breaks that assume the default case-insensitive mode. It also means that you as a programmer have to add extra crap to your file handling code for case insensitive string comparisons if you want to support both modes

Wouldn’t all my consumer grade switches need to support vlan tagging? I’m pretty sure a bunch of them dont

My proxmox “cluster” is a bunch of old laptops with a single consumer grade NIC in each. I wanted to isolate the VM network from my main home network (have it on a different range) while still allowing all the VM’s to transparently talk to each other regardless of which physical host they happen to be on.

Could I have achieved this with normal vlans? I wanted an overlay network on the VM side but they still need to use my main home network to get internet and I only have a single physical interface on each host which is plugged into my main home network (addresses assigned via my home router).

The OPNsense VM routes between the two networks (the virtual vxlan within Proxmox + my physical home network) and does DHCP / DNS for the VM network

Proxmox requires subtracting 50 from the MTU so it can store it’s vxlan information in the packet.

From the docs:

Because VXLAN encapsulation uses 50 bytes, the MTU needs to be 50 bytes lower than the outgoing physical interface.

It’s super annoying but I couldn’t see another way of having vms be able to talk to each other transparently regardless of which node they are on

I just attached the host NIC to OPNSense and then have a vxlan in proxmox to make the VM network separate from the rest of my home network. Both the host NIC and the vxlan virtual NIC are attached to the VM.

The OPNsense VM acts as a router between the two networks. I host all my shit on the VM network under *.internal.legit.tld and use LetsEncrypt + Traefik to issue SSL certs which work without having to load a CA cert everywhere because I own legit.tld

The only bastard was having to adjust the MTU everywhere within the VM network, that caught me out a couple of times

Yep this for me too. Thankfully VSCode allows comments in its settings.json / launch.json files but most programs use strict JSON which doesn’t allow comments

I used to think that until I figured out yaml and now yaml isn’t so bad.

It helps that text editors know what yaml is now so insert spaces when you hit tab etc

I guess Caddy has been stealing its market share