Re:Ask HN: How would you expose local Raspberry PI to Intern...
by DataWraith on Saturday July 13, 2019 @11:47AM
(#20428597)
The obvious way to do it would be to forward a port in your router and then keep a dynamic DNS service (DuckDNS, for example) updated with your external IP address.
As for networks, I personally use the Yggdrasil Network [1] to connect to my homeserver. Since it is a self-contained network, a blog hosted on there wouldn't be visible to the web, but it's very, very convenient for private access. It traverses NAT without any hassle once you connect to other peers.
If you do connect to the network, you probably want to also set a whitelist of peers that are allowed to access your machine, otherwise it is open to the entire network.
As for networks, I personally use the Yggdrasil Network [1] to connect to my homeserver. Since it is a self-contained network, a blog hosted on there wouldn't be visible to the web, but it's very, very convenient for private access. It traverses NAT without any hassle once you connect to other peers.
If you do connect to the network, you probably want to also set a whitelist of peers that are allowed to access your machine, otherwise it is open to the entire network.
[1] https://yggdrasil-network.github.io/