Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
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
Why did you choose Vxlan over regular vlans?
Are you running EVPN-Vxlan at all?
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
Vxlan is way overkill
It would be way more performant to use 802.1q vlan tags
Wouldn't all my consumer grade switches need to support vlan tagging? I'm pretty sure a bunch of them dont
Why the MTU change?
Proxmox requires subtracting 50 from the MTU so it can store it's vxlan information in the packet.
From the docs:
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
Ah, ok, good to know, thanks