Locally hosting an internet-connected server
mjg59.dreamwidth.org
Locally hosting an internet-connected server
1–10 of 183 posts
Re: Locally hosting an internet-connected server
#2Why not use a dynamic DNS service instead? I’ve been using dyn.com (now oci.dyn.com) for years and it has worked great. A bonus is many home routers have support built in.
Re: Locally hosting an internet-connected server
#3This is an interesting solution and wouldn't mind using one of my existing servers as a gateway or proxy (?).
Is there a way to be selective about what ports are exposed from the host to the target? The target could handle it but fine grained control is nice.
Re: Locally hosting an internet-connected server
#4Why not use a dynamic DNS service instead? I’ve been using dyn.com (now oci.dyn.com) for years and it has worked great. A bonus is many home routers have support built in.
I have multiple devices on my internal network that I want to exist outside, and dynamic DNS is only going to let me expose one of them
Re: Locally hosting an internet-connected server
#5This is an interesting solution and wouldn't mind using one of my existing servers as a gateway or proxy (?). Is there a way to be selective about what ports are exposed from the host to the target? The target could handle it but fine grained control is nice.
You could just set a default deny iptables policy for forwarding to that host, and then explicitly open the ports you want
Re: Locally hosting an internet-connected server
#6you can also run a proxy on the vps instead of the nat.
Re: Locally hosting an internet-connected server
#7Why not use a dynamic DNS service instead? I’ve been using dyn.com (now oci.dyn.com) for years and it has worked great. A bonus is many home routers have support built in.
I have multiple devices on my internal network that I want to exist outside, and dynamic DNS is only going to let me expose one of them
If they don't all need distinct external IP addresses of their own, port forwarding is a typical approach.
Re: Locally hosting an internet-connected server
#8Earlier quoted context omitted.
I have multiple devices on my internal network that I want to exist outside, and dynamic DNS is only going to let me expose one of them
If they don't all need distinct external IP addresses of their own, port forwarding is a typical approach.
That doesn't work well if you want to run the same service on multiple machines. For some you can proxy that (eg, for web you can just run nginx to proxy everything based on either the host header or SNI data), but for others you can't - you're only going to be able to have one machine accepting port 22 traffic for ssh.
Re: Locally hosting an internet-connected server
#9you can also run a proxy on the vps instead of the nat.
Depends on the protocol. For web, sure - for ssh, nope, since the protocol doesn't indicate which machine it's trying to connect to and so you don't know where to proxy it to.
Re: Locally hosting an internet-connected server
#10Earlier quoted context omitted.
If they don't all need distinct external IP addresses of their own, port forwarding is a typical approach.
That doesn't work well if you want to run the same service on multiple machines. For some you can proxy that (eg, for web you can just run nginx to proxy everything based on either the host header or SNI data), but for others you can't - you're only going to be able to have one machine accepting port 22 traffic for ssh.
Select an isp that gives you multiple ip v4 addresses. Or host on ipv6.