Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 15 replies
  • Subscribers 8 subscribers
  • Views 47003 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Opening Port to Public IP

eholyst

I am trying to make my camera server accessible from the internet. I have followed all of the port forwarding guides but I must have missed something. If I try to access the server internally on the port I opened "8081" works fine. Anything from the outside no luck. I have my dnat rule setup as this "Traffic From-Any" to "Using Service-8081" to "Going to-External(WAN Address)". Actions are "Change the destination to-Camera Server" to "and the service to-8081". I have checked the automatic firewall rule as well. Any help is much appreciated thank you.



This thread was automatically locked due to age.
Parents
  • 0
    I can't see the screenshot, but from your description DNAT rule looks fine (except that you don't need to change service to 8081 as rfcat_vk mentioned).

    Did you set UTM internal IP address as a default gateway in IP configuration on your camera server ?
  • 0 in reply to vilic
    @khardeveld- You are correct with that log packets option turned on I do not see any traffic coming from outside to in on the port I specified.

    @vilic- Yes the gateway address is the address of the utm. I have followed all the steps in the blueiris software which is the software I am using to set this camera server up but do not see what I am missing.
  • 0 in reply to eholyst
    Just to double-double check :)

    What IP adresses are shown in Interfaces and routing -> interfaces
    What IP adddress is shown if you go to http://whatismyipaddress.com/ from a system behind the UTM?
  • 0 in reply to khardeveld
    @ -That is correct it is residential. That is a possibility. I know I have setup an ftp server before just used an odd numbered port instead of 21. I did try more than one port number though just to make sure it wasn't that or at least make sure it wasn't that port.

    @khardeveld- The IP addresses match up the public listed in the utm is the same as whatismyip. I know at least with comcast equip which I do not have though that they used to do this weird thing where the gateway was actually your ip and your ip was your gateway although I think that was for the business router box I don't know if that applies now.
Reply
  • 0 in reply to khardeveld
    @ -That is correct it is residential. That is a possibility. I know I have setup an ftp server before just used an odd numbered port instead of 21. I did try more than one port number though just to make sure it wasn't that or at least make sure it wasn't that port.

    @khardeveld- The IP addresses match up the public listed in the utm is the same as whatismyip. I know at least with comcast equip which I do not have though that they used to do this weird thing where the gateway was actually your ip and your ip was your gateway although I think that was for the business router box I don't know if that applies now.
Children
  • 0 in reply to eholyst

    So, now you have confirmation that your IP adresses are what they should be: if external traffic does not reach your UTM (your NAT rule is not triggered), then the cause is external to your UTM. I would agree with Scott_Klassen that the most likely cause is your ISP blocking incoming traffic. I would advise to check with them.

  • 0 in reply to khardeveld
    I tried just changing it to port 80 and translate to 8081 but I get the same thing. I would think that should have at least got me to the utm since I doubt they would be filtering it out from there.