I’m a guy on the internet. Nothing to see here.
The problem looks to be your subnet specification. /24 is 256 addresses. So for your 192.168.0.10/24 export, you’re exposing it to 0.10 and the following 255 IPs.
The closest thing to what you want to achieve would be a /29, which would expose it to the given IP and the following 7 IPs.
The real benefit of PBS is it does not store the backup as just a 1:1 dump of the VM disk, it’s incremental - if the VM you’re backing up for say the 3rd or 4th or 20th time doesn’t have much new or changed data, it’s not a linearly increasing amount of storage on your backup server, the new backup is actually trivially small. This really helps you have longer backup retention if files aren’t actually changing all that often.
I got tired of stressing about whether my backup host might be down when my primary Proxmox host dies, even if they’re in different data centers - well, as far as I know anyway! Now I just use BackBlaze B2 storage for the PBS off-site backup (compatible with Amazon S3), albeit it’s a little finnicky to set up and working 100%. Yes it’s still ‘just someone else’s computer’, but for the ~12 bucks it’s costing me for almost 2TB of backup data I am not stressing about it.
Well aside from the obvious giveaways in the presentation format of the README.md, and .gitignore, the very first question of its FAQ is:
“You use LLMs? 🤯”
Yes. Heavily. Claude and GLM-5.2 wrote a lot of this repo.
No, if you mean 192.168.0.0 - 192.168.255.255, that is a /16 192.168.0.0 - 192.168.0.255 is a /24 192.168.0.0 - 192.168.0.7 is a /29
I was a little glib in my initial response. You really don’t want to start your definition in the middle of a subnet.
I would set it up so your first group of /29 would be 192.168.0.0 - 192.168.0.7
Second would be 192.168.0.8 - 192.168.0.15 (192.168.0.8/29)
Third would be 192.168.0.16 - 192.168.0.23 (192.168.0.16/29)
And so on.