Not sure if this is helpful in any way, but it might give you some clue.

100./8 addresses are reserved for CG-NAT.

This is probably the IPv4 address your modem/router is receiving from the ISP.

https://en.wikipedia.org/wiki/Carrier-grade_NAT

I might pick it back up some day but at the moment I have other projects going on at the moment.

I’m still using Proxmox myself but unfortunately it’s all fairly manually configured.

I started writing a Terraform provider for Proxmox a while ago.

Unfortunately, the API is a massive mess and the documentation is not very helpful either. It was a nightmare and I eventually gave up.

https://github.com/c10l/terraform-provider-proxmoxve

K3s is k8s

lol at the downvote. K3s is k8s. The very first 2 words in its website are Lightweight Kubernetes. https://k3s-io.github.io/

On macOS I’ve been using Ollama. It’s very easy to setup, can run as a service and expose an API.

You can talk to it directly from the CLI (ollama run ) or via applications and plugins (like https://continue.dev ) that consume the API.

It can run on Linux but I haven’t personally tried it.

https://ollama.ai/

It’s pretty easy with Ollama. Install it, then ollama run mistral-7b (or another model, there’s a few available ootb). https://ollama.ai/

Another option is Llamafile. https://github.com/Mozilla-Ocho/llamafile

I run it on my router which has the CG-NAT IP address.

Whilst you’re right that it could clash, it’s very unlikely (a 1 in 4194302 chance), I imagine Tailscale would detect the clash and change IPs though I could be wrong as it never happened to me (and probably never will - though in all fairness it will eventually happen to someone).

Been using Tailscale behind CG-NAT for years. It works wonderfully and very rarely needs to route through the DERP infrastructure - it’s almost always a P2P connection.

You’re not wrong that the storage itself is undoubtedly more robust on any cloud provider than a cheap consumer NAS box.

However, there are other factors to consider.

A NAS or any storage solution is only useful if you can access it if you need and if the network speed and stability match your expectations.

A cloud solution will be inaccessible if your internet is down. It may also suffer tremendously if your connection is unstable or slow.

In that sense, even a laptop’s drive connected to your switch could prove more robust than any cloud solution.

You don’t have to use the registrar’s DNS system.

I use LuaDNS. They even offer a fully functional free tier that might be enough for your needs.

They have an API that can be used with certbot, and you can manage your zones with git.

£35 for symmetrical 1gbps. In practice, I get fairly stable ~850mbps either way but I reckon my router is the bottleneck rather than the actual line.

Just to add an option to some of these services. LuaDNS are located in the EU (Romania), can be wholly managed via git (including webhooks for auto-build upon a push), and also do email forwarding.

http://www.luadns.com/