Sorry, four of the power to ethernet plugs. You put one near your router to essentially supply internet to your house's electrical circuits, then distribute the others where you need them, such as office, living room if you want to connect a TV or console, etc.
OminousOrange
joined 1 year ago
I had a set of four for getting ethernet around the few places I rented. There was maybe the odd quality decrease when there was a lot of electrical load, but they worked great otherwise.
Oh man, I remember a Philips mp3 player I had for the longest time as a kid. You could hear the little clicks of the hard drive. Lost it on a hike, unfortunately.
And also that many contracts to improve on IT are performed by the lowest bidder.
I remember there being tube polo as an intramural sport at my university. I never played but it's another option to avoid mostly just drowning the whole time.
I recently went this route after dabbling with other options. I had a wireguard VPN through my Unifi router, with rules to limit access to only the resources I wanted to share, but it can be a struggle for non savvy users, and even more so if they want to use Jellyfin on their TV. Tried Twingate too and would recommend if it fits your usecase, but Cloudflare Tunnels were more applicable to me.
About $11M USD.
This is mostly my reasoning too. I've got a bit more juice than a NUC, but I prefer the way resources are managed with an LXC for the certain apps that I run. I still have VMs for other things, like HAOS and a BlueIris NVR. It's only a local homelab with no external users so avoiding additional complexity is often in my best interest.
Why would one prefer a VM over an LXC for Docker?
I might have found the issue, see updates above. I have a separate Docker LXC that was behaving normally too, so was good to cross-check with that.
Docker is installed on a Debian container with Proxmox as the hypervisor. I believe as far as Docker knows, it's just running on normal Debian. The Debian LXC has its own local ip.
I'll take a look at those resources though, thanks.
I'm definitely not a network pro, but it sounds like you're looking to do something similar to what I have.
I've got nginx proxy manager as my reverse proxy with pi-hole for local DNS. All traffic goes through the pi-hole and anything going to mydomain.com has DNS entries pointing to nginx. I've set nginx up so service.lan.mydomain.com is for anything local and just service.mydomain.com for anything external with wildcard SSL certs for both (*.domain doesn't seem to cover *.lan.domain so add certs for both - probably because it's a sub-subdomain).
The Cloudflare tunnel can then just get directed to service.mydomain.com instead of the IP of the service.