I’m writing my own novice guide to setting up a home server, the stuff I wish I’d been told when I started. Would love feedback from beginners on how useful this is, as well as feedback from veteran self-hosters on how accurate this is, and I welcome suggestions from anyone about what I should add next.
update: tweaked the introduction a bit, corrected title to match header, added note about podman-compose v1.0.6 incompatibility.
I would like a very small segment on IPv4, the implications of NAT and why NAT reflection should be turned on- why uPnP should never be turned on in residential networks and only if you know what you’re doing in any other networks, and maybe how IPv6 solves some of these issues.
These are the issues I’ve struggled with. Even now I curse under my breath whenever I have to deal with NAT.
You’d need to log into your router to see if it’s enabled. Assuming you’ve got standard consumer grade stuff, it’s likely on by default because it makes things like console multiplayer 'just work’s without needing someone to go in and port forward stuff.
Before I built my home network, any Linksys/Netgear/etc router I used had that disabled when I was doing my initial setup.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
I would like a very small segment on IPv4, the implications of NAT and why NAT reflection should be turned on- why uPnP should never be turned on in residential networks and only if you know what you’re doing in any other networks, and maybe how IPv6 solves some of these issues.
These are the issues I’ve struggled with. Even now I curse under my breath whenever I have to deal with NAT.
updated post here, includes section on networking! let me know if this looks good? https://lemmy.world/post/2444639
I wish I had a better guide on that myself! I’ve been using this guide for the time being, it covers the basics of how to set up a firewall: https://www.raspberrypi.com/documentation/computers/configuration.html#securing-your-raspberry-pi
actually, could you tell me more? not only are those new solutions to me, those are new problems. I don’t even know how to tell if uPnP is turned on.
edit: oh! I have actually dealt with NAT reflection before, the guide I used called it Hairpin NAT. https://help.mikrotik.com/docs/display/ROS/NAT#NAT-HairpinNAT
You’d need to log into your router to see if it’s enabled. Assuming you’ve got standard consumer grade stuff, it’s likely on by default because it makes things like console multiplayer 'just work’s without needing someone to go in and port forward stuff.
Before I built my home network, any Linksys/Netgear/etc router I used had that disabled when I was doing my initial setup.
Your page links 404 out, but if you reduce it to https://klay.gay/self-host/ it works and shows v.0.9.2 so you may want to edit your post. :)
ah, thank you! it’s actually been long enough that I created a new post here: https://lemmy.world/post/2444639