Had the problem on DN42 (a distributed overlay network, that is sperated from the internet), that my FreeBSD servers couldn't update without hacky firewall tricks (NAT etc.)
Did now finally solve that cleanly with a single caching Nginx server that is dual-homed (internet+dn42) and that enables me to use freebsd-update AND pkg from systems that only have DN42 connectivity :-)
Also add that to the DN42 wiki and offer others to use it as infrastructure!
bsdmirror.chofstede.dn42 (IPv6-only by design)
I'm not sure me learning about #DN42 was a good thing.
I'm not a network engineer, and I don't really plan to become one.
But holy shit if community-based darknets sounds like a thing I want to participate in.
And as a side bonus I got enough inspiration to run my own DNS server for my home network so I don't necessarily have to remember all the IP addresses by heart and edit hosts files by hand anymore...
Since I run my #dn42 nodes on a *different* VPS than where my blog is running now, (and I don't want to copy my blog in two places!) I now employ socat.
Also, since I run dn42 inside a Linux network namespace, I also had to utilize NAT.
It's messy and I hate it.
AI agent tried to join the DN42 hobbyist network to perform a network scan, uncontrolled #AI requests resulted in USD 6531.30 #AWS bill, to the extent that they are begging for donations from the #DN42 community
https://lantian.pub/en/article/fun/ai-agent-bankrupted-their-operator-scan-dn42lantian.lantian/
There are people who want to delete the dn42 article on Wikipedia. How creepy and unfortunate.
https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Dn42
Amusing - and I learned about DN42.
#AI Agent Bankrupted Their Operator While Trying to Scan #DN42 - https://lantian.pub/en/article/fun/ai-agent-bankrupted-their-operator-scan-dn42lantian.lantian/