this post was submitted on 13 Jul 2023
118 points (95.4% liked)

Selfhosted

40415 readers
388 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

The question above for the most part, been reading up on it. Also want to it for learning purposes.

you are viewing a single comment's thread
view the rest of the comments
[–] MeanEYE@lemmy.world 1 points 1 year ago (1 children)

There's no "should in theory". It's only a possibility due to sheer number of possible combinations. No one was ever going to make every device public. It makes absolutely no sense. Why would your company's printer be online or isolated networks or VPNs? There's no point.

[–] orangeboats@lemmy.world 2 points 1 year ago

IP addressing is just a way to give a globally unique number to each device. It's just a number.

And there wasn't a real public/private distinction when the Internet was still in its infancy. Printers were indeed given "public" addresses because people needed a number for it.

If you don't want your printer to be reachable by the public Internet, use a firewall to block outside connections. If you can use NAT, you certainly can use a firewall. Heck, they are almost the same thing if you have been using the Linux kernel (iptables/nftables handle firewalling and masquerading with the same tool!)

Routability is not the same as reachability. With NAT transversal you can reach my "private" hosts all the same, although you can't route to me because I don't have a public address.