From an outside network I have no issues getting to it. From an inside network I can’t reach it. For instance I go to http://url.com:8101 and nothing. Everything I have seen on here is hairpin rules for port to port. Since I am changing the devices port on the external URL, what do I change in the nat rule so that it nat’s back to 443?
I have tried creating this rule, both with port 443 and 8101 (internal port of camera, external port of camera) and moving the rules from the bottom of the list to the top of the list. Still nothing. No packets even hit the rule. Here is the export:
I am an idiot and didn’t do the first rule of the Hairpin right. But this example isn’t going to work with what I have because:
-I have a dynamic IP
-I will have 6 cameras with port 443 and port 554 coming from each re-directing to 8101-8106, 8201-8206.
With that said, It doesn’t seem the hairpin rules are allowing me to change ports like this to allow all 6 cameras to be accessible by the viewing software.
Dynamic IP: There are plenty of scripts in this forum that will automatically change the IP addresses in the rules when your IP address changes. That isn’t a problem.
Redirection: There is no reason this shouldn’t work. Clear your counters and see if your correct rules are getting hit.