RESOLVED: incoming connections?
Posted: Mon May 26, 2025 1:18 pm
Whoops! Problem solved: My dynamic DNS client got purged by a server upgrade and the hostname was resolving to a stale IP address.
I got the impression — from "somewhere", so I could be wrong — that Sonic policy allows me to run a low-volume web server for personal use. And now I want to.
I can't have a static IP address, but I've overcome that with dynamic DNS (of course). I've created a "virtual server" in my edge router which forwards incoming traffic to the relevant server on my side of the connection.
It works when I connect to my edge router from the inside. Bounces right off the router and hits the server I want. Because of course it does.
But when I attempt to connect from the outside world, I get no connection. And I get no ping. A traceroute shows me a lot of hops through Sonic's network, so I feel like DNS has told the client to bark up the correct tree. I'm just not reaching the correct branch.
I've crawled around in my edge router settings looking for some measure I've taken but forgotten about which would deny all incoming connections. I've found nothing.
I'm guessing the problem might be in the CPE configuration, but that device doesn't seem to be configurable from my side. Maybe I have to tell Sonic to allow incoming connections because that isn't their default? Other ideas?