Member Avatar for kevsam

Hello Folks,

I am forwarding some ports on a cisco linksys ea 6500 router to view surveillance cameras. I checked on canyouseeme.org and port 80 was open. Then I checked back within 5 minutes and it was closed. Since then I am unable to get that port open. However that port is not blocked by the ISP cause I work with them and I have used that port already on other camera systems.

This router is one of cisco's smart routers I am wondering if something in the router might be causing this. Any assistance will be greatly appreciated. Thanks.

  • 2 Contributors
  • 3 Replies
  • 216 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by rubberman

Dani AI

Generated

Short, practical checklist to narrow this down (building on ’s suggestion to check logs).

First confirm the camera actually has an HTTP listener when the external test is run. From inside the LAN open the camera URL or run a quick check:

# Linux/macOS
curl -I http://192.168.1.10/

# Windows PowerShell
Test-NetConnection -ComputerName 192.168.1.10 -Port 80

canyouseeme.org only reports what it sees at the moment it probes; if the camera’s server is not up, the port will show closed even if the forward exists.

Router / forwarding checklist

  • Verify the forward maps external TCP 80 to the camera’s current IP and port. Use a DHCP reservation or a static IP so the target does not change.
  • Confirm the rule uses TCP (HTTP) and there are no conflicting rules or port-triggering entries.
  • Check remote administration settings: some routers use/hold port 80 for the web GUI or remote admin — disable remote admin or move it to a different port.
  • Check the router WAN address: if it’s a private address (10.x.x.x, 172.16.x.x–172.31.x.x, or 192.168.x.x) the router is behind another NAT (double NAT) and external forwards won’t reach the camera unless the upstream device forwards too.

Logs and targeted tests

  • As suggested, enable/collect firewall logs and look for denies, drops, RSTs, or events around port 80 and for router reboots. Correlate an external canyouseeme check with the router log timestamp.
  • For a quick isolation test, run a temporary HTTP server on a PC inside the LAN and forward port 80 to it (or place it briefly in the DMZ) to see whether the issue is the camera or the router mapping. (DMZ testing is only for troubleshooting; it exposes the device.)

Other points

  • Keep firmware up to date and backup settings before upgrades. Consider using a nonstandard WAN port or a VPN/secure tunnel rather than exposing cameras on port 80, and ensure strong passwords and up-to-date camera firmware.

Recommended Answers

All 3 Replies

Member Avatar for rubberman

Have you looked at the router security logs? That may provide some indication of what is going on. It is possible that it is so "smart" that it thinks you are trying to hack in? Sort of a Catch-22?

Member Avatar for kevsam

Actually I didn't check the logs. Is there anything specific that i should look for?

Member Avatar for rubberman

Possibly for stuff like attemts to access the management port (not sure what it would be - read the manufacturer's documentation about remote management), port scanning (common, but may be helpful to know). If you can download the logs to your system, post them here so we can look at what is going on.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.