Issue with Spectrum Sagemcom Router's port forwarding feature Glitch affecting configuration and connectivity
Issue with Spectrum Sagemcom Router's port forwarding feature Glitch affecting configuration and connectivity
I'm working on moving forward ports for my servers (SSH, 9091, Apache2) but the router blocks them. I suspect the ports are still active from my previous server and haven't been cleared. My last server stopped working while I was using SSH, and I worry it might still be locked in the DMZ with IP and port bindings. Since the device is old and hasn't been maintained, I'm unsure if removing the DMZ restriction is possible without resetting everything. P.S.: I'm using a Segemcom F@st5260 router.
80 will be available when external web portal access is active. Disabling it allows forwarding of TCP 80 and port 22. If SSH access is enabled on the router, it may also allow you to change the port. For a 2020 modem/router, using port 9091 might be better if a rule prevents overwriting. Just reset the router and start over. Sagem modems/routers are really problematic. Good luck!
It seems there’s a major concern about security with the router’s port configuration. If it’s opening WAN ports unnecessarily, it could indicate a serious issue and might require replacing the device or contacting your ISP. I’m puzzled why you’d expect it to recall old settings—check the port forwarding page for details. Also, DMZ and port forwarding are different concepts; it’s unclear why they’re being discussed together. Were you using either DMZ or port forwarding for the old server?
I’m dealing with roughly four Sagem F@st units about 20 yards away from me in a cluttered network area filled with outdated networking gear. I can confirm these items are among the worst components, running the most unstable firmware you’ll find. I’m not implying they’re letting you connect to the WAN side since their built-in firewall will drop any external attempts. The devices will only accept connections from local IPs, using TCP 80/443 for web access and TCP 22 for SSH—so remote SSH is possible but limited. Forwarding functionality here is weak, which is why I’m giving you a tough break. It would be smarter to swap them out for something more reliable with real-world experience and a better interface.
Consider giving him a fresh start by resetting the device. This should erase any incorrect settings and provide a clean slate for him to work from. I’ve had similar experiences with these products, so I’m sharing what I’ve learned from using them before. It’s unlikely you’ve encountered anything worse, but they’re essentially basic modem/router bundles sold in large quantities by ISPs.
I've done everything possible, but the only solution was to fully reset the router. Appreciate your assistance.