• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

[SOLVED] Port Forwarding IP Camera

Scheduled Pinned Locked Moved NAT
21 Posts 2 Posters 22.0k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    danswartz
    last edited by Jul 13, 2010, 11:46 AM

    well, if you get a connection HTTP or whatever error, you are getting to the camera.  the failure to connect at all via the public IP from inside is presumably because you have nat reflection disabled.  this is weird then, it is almost like the camera is disallowing connections from IPs other than inside the LAN.

    1 Reply Last reply Reply Quote 0
    • B
      bczeon27
      last edited by Jul 13, 2010, 3:08 PM Jul 13, 2010, 3:04 PM

      Thank You for trying to help.

      I think the connection was established.  But, the camera can't sent any information out.

      So, Set the Outbound then reset the router.

      The problem has been resolved.

      1 Reply Last reply Reply Quote 0
      • D
        danswartz
        last edited by Jul 13, 2010, 3:06 PM

        What does 'set the outbound' mean?

        1 Reply Last reply Reply Quote 0
        • B
          bczeon27
          last edited by Jul 13, 2010, 3:08 PM

          NAT:Outbound

          • Manual Outbound NAT rule generation

          This is weird.  Doesn't the NAT (Port Forward) automatic address the outbound and inbound issue?

          1 Reply Last reply Reply Quote 0
          • D
            danswartz
            last edited by Jul 13, 2010, 3:11 PM

            No, port forwarding only deals with inbound.  Also, you shouldn't have need to manually set outbound NAT unless you were doing something non-standard.  If you set manual NAT (AON) but didn't actually change anything, that was most likely a red herring, and the router reboot is what "fixed" this.

            1 Reply Last reply Reply Quote 0
            • B
              bczeon27
              last edited by Jul 13, 2010, 3:20 PM Jul 13, 2010, 3:14 PM

              I did add a rule in the outbound of creating a static port 9082.

              This is interesting.  I would changed that back and find out.

              1 Reply Last reply Reply Quote 0
              • D
                danswartz
                last edited by Jul 13, 2010, 3:16 PM

                where did you get that port number from?

                1 Reply Last reply Reply Quote 0
                • B
                  bczeon27
                  last edited by Jul 13, 2010, 3:17 PM

                  That's the http port that the IP camera uses.

                  1 Reply Last reply Reply Quote 0
                  • D
                    danswartz
                    last edited by Jul 13, 2010, 3:24 PM

                    But that is for inbound (port forwarding.)  That has nothing to do with the port numbers in the outbound NAT settings.  What specifically did you set for the outbound NAT entry?

                    1 Reply Last reply Reply Quote 0
                    • B
                      bczeon27
                      last edited by Jul 13, 2010, 3:44 PM

                      Interface      Source        S. Port                            Static Port
                      WAN    192.168.1.0/24    9082    *    *    *    *    Yes
                      WAN    192.168.1.0/24    9002    *    *    *    *    Yes
                      WAN    192.168.1.0/24      *        *    *    *    *    No

                      1 Reply Last reply Reply Quote 0
                      • D
                        danswartz
                        last edited by Jul 13, 2010, 3:52 PM

                        Outbound NAT should only be for new connections initiated from inside.  Have you tried deleting them and rebooting pfsense?

                        1 Reply Last reply Reply Quote 0
                        • B
                          bczeon27
                          last edited by Jul 13, 2010, 4:40 PM

                          Just disabled the whole Outbound NAT.

                          You are right.  A simple Firewall State Reset was all it is needed.

                          thanks.

                          1 Reply Last reply Reply Quote 0
                          21 out of 21
                          • First post
                            21/21
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                            This community forum collects and processes your personal information.
                            consent.not_received