Equivalent connection as a static IP address

I run an AllStarLink node on a Linode Debian Linux virtual computer that acts like a hub where stations can each connect, the equivalent of a Internet IP repeater station. The Linode Debian virtual computer has a public static IP address.

I would like to be able to run the AllStarLink hub from my home location, but I don't have a static IP address from my home location. I only have a DHCP public IP address. I tried to setup an AllStarLink hub at my home location, and there are connection problems from stations when my DHCP IP address changes. To get a static IP address at my home, I would have to change my internet service to much more expensive business internet service. Is there a way that I can run an AllStarLink hub from my home location that's equivalent to having a public IP address, so that the incomming AllStarLink connections can connect to my AllStarLink hub when my public DHCP IP address changes?

Use 44net. That will get you a public static IP address.

···

On Oct 28, 2026, at 13:26, David Borchard [email protected] wrote:

Someone replied to a topic you are Watching.

| KY0L
October 28 |

  • | - |

I run an AllStarLink node on a Linode Debian Linux virtual computer that acts like a hub where stations can each connect, the equivalent of a Internet IP repeater station. The Linode Debian virtual computer has a public static IP address.

I would like to be able to run the AllStarLink hub from my home location, but I don't have a static IP address from my home location. I only have a DHCP public IP address. I tried to setup an AllStarLink hub at my home location, and there are connection problems from stations when my DHCP IP address changes. To get a static IP address at my home, I would have to change my internet service to much more expensive business internet service. Is there a way that I can run an AllStarLink hub from my home location that's equivalent to having a public IP address, so that the incomming AllStarLink connections can connect to my AllStarLink hub when my public DHCP IP address changes?


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

You do not need a static IP address. But, you do need a consistent public IP address (not a CGNAT'd IP).

When your node registers with the AllStarLink network we capture the current IP address of your server. That IP address is made available to other nodes so that they can connect to your node.

For a home network, the registered IP would be the DHCP address provided by your ISP. If that DHCP address ever changes then the next time your node updates its registration the new IP would be captured.

What is your "WAN IP" of your home router? Does it start with 10, 172.16-31, 192.168, or 100? If so, then you're on CGN. Provide the output of asl-node-auth-check. That will flag if you're behind a CGN that will cause you problems. If you just have a DHCP IPv4 address that's publicly routable, the worst-case time to propagate a change across the AllStarLink system would be 480 seconds. And your public IPv4 address shouldn't change unless you restart your router or change out the hardware in most cases.