gooeyglob
@gooeyglob@lemmy.world
I’m a guy on the internet. Nothing to see here.
- Comment on I self-hosted a fully autonomous business on one laptop: public data API + zero-KYC crypto store + on-chain payment detection, run end-to-end by an AI agent (free data sample inside) 4 weeks ago:
You can definitely generate real downvotes! This looks like it fills up the entire Fediverse downvote Bingo card.
- Comment on DigitalOcean contributes 3 million and joins the Omacom (Omarchy) Foundation 4 weeks ago:
Same same, sucks as they seemed neutral but boy do they not seem to care about appearances.
- Comment on Means to privately connect to my home server other than Tailscale? 1 month ago:
Big Netbird fan, and they support a fully self hosted version.
- Comment on Visibility of NFS exports 2 months ago:
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 subnet in the middle of a boundary.
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.6/29)
And so on.
- Comment on Visibility of NFS exports 2 months ago:
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 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.