![](https://lemmy.procrastinati.org/pictrs/image/53aafb94-bd8e-4148-ba86-03fb455cd8e4.jpeg)
![](https://lemmy.world/pictrs/image/e8842a5a-3702-4103-8102-b71875cd9eda.png)
I have this and an Atari 800 in a tote waiting for the day I have somewhere to put them.
Mastodon: @SeeJayEmm@noc.social
I have this and an Atari 800 in a tote waiting for the day I have somewhere to put them.
Enough people have already commented on the “proxy at the vps solution”. Another option is to configure routing and nat on the VPS and have it route over the wg tunnel.
Requires you to have postup/predown scripts that modify your routing tables on the wg endpoint.
I made the plunge about a year ago. Spectrum assigns me a prefix but routing was spotty at best. In the end after all the troubleshooting pointed to the problem being the ISP I gave up and stuck with what works, IPv4.
The whole .zip TLD is really unfortunate.
This is how I learn and half the reason my home lab exists. I need projects to get/stay motivated.
I feel this post so hard. I’m always about 5 seconds from going Office Space on my printer.
I’m fond of Beekeeper Studio and a sqlite DB.
However, if my VPS is compromised, wouldn’t the attacker still be able to access my local network?
That depends on your setup. I terminate my wireguard tunnels on my opnsense router, where I have explicit fw rules for what the vps hosts can talk to.
I’m using CheckMk for pretty much all of that. Personally I found zabbix to have too much overhead.
No but less power hungry than a full desktop. It’s a good trade-off between power and performance.
If you want the small footprint and power costs are a concern, look for a second hand mini computer. Dell, Lenovo, Intel nuc.
Something like this as an example.
You know b2 has multi region replication now, right?
https://www.wireguard.com/protocol/
Looks like wireguard encrypts traffic to me.
Thanks I may give it a try if I’m feeling daring.
Media should exist in its own with a tuned record size of 1mb
Should the vm storage block size also be set to 1MB or just the ZFS record size?
That cheat sheet is getting bookmarked. Thanks.
I’m referring to this.
… using grub to directly boot from ZFS - such setups are in general not safe to run zpool upgrade on!
$ sudo proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
8357-FBD5 is configured with: grub (versions: 6.5.11-7-pve, 6.5.13-5-pve, 6.8.4-2-pve)
Unless I’m misunderstanding the guidance.
Proxmox is using ZFS. Opnsense is using UFS. Regarding the record size I assume you’re referring to the same thing this comment is?
You can always find some settings in your opnsense vm to migrate log files to tmpfs which places them in memory.
I’ll look into this.
I’ve done a bit of research on that and I believe upgrading the zpool would make my system unbootable.
Wiki.js Nginx Proxy Manager.