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

Re: New to pfsense need help on port forwarding

Scheduled Pinned Locked Moved NAT
20 Posts 4 Posters 8.6k 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.
  • T
    Tib
    last edited by Nov 3, 2008, 3:18 PM

    Otherwise the nat is work, if WAN ip is doesn't changed

    nat.JPG
    nat.JPG_thumb

    1 Reply Last reply Reply Quote 0
    • J
      jahonix
      last edited by Nov 3, 2008, 7:02 PM

      The field for "External address" should be set to 'interface IP' on all rules. Most of your entries don't show anything (colum: NAT IP:  (ext.: 66.77.88.99) )
      And delete the last rule, it is double.

      1 Reply Last reply Reply Quote 0
      • N
        nocer
        last edited by Nov 3, 2008, 10:19 PM

        Hi.

        Oh well, indeed. The rules for port forwarding, you must need to set EXT IP for your WAN interface as jahonix pointed out.

        cheers,

        1 Reply Last reply Reply Quote 0
        • T
          Tib
          last edited by Nov 4, 2008, 11:02 AM

          Hi

          But, i don't set external ip, becoulse that is always changing by ISP.

          1 Reply Last reply Reply Quote 0
          • J
            jahonix
            last edited by Nov 4, 2008, 1:37 PM

            @Tib:

            But, i don't set external ip, becoulse that is always changing by ISP.

            Isn't THAT exactly your problem?  ???
            When editing the rule you have to set the field to the drop down entry "External address". Then the IP change is handled for you. Automagically…

            1 Reply Last reply Reply Quote 0
            • T
              Tib
              last edited by Nov 4, 2008, 2:38 PM

              My problem is

              If  the PPPoE connction is renew externalWAN ip of  my system, then the ALL forwarding rules is doesn't work.

              I sent the screenshot, and what to do?

              nat2.JPG
              nat2.JPG_thumb

              1 Reply Last reply Reply Quote 0
              • J
                jahonix
                last edited by Nov 4, 2008, 3:53 PM

                As you see in the first picture you posted, in the NAT IP column there were no entries for (ext.: )
                or wrong entries (ext.: any)

                Set them to 'interface address' and it should work for you as well.
                In the overview page the brackets must be automatically filled with your currently assigned IP then.

                1 Reply Last reply Reply Quote 0
                • T
                  Tib
                  last edited by Nov 4, 2008, 7:08 PM

                  The wan ip is changing automaticaly, it's ok, but doesn't in the rules, although it has to….

                  thanks for help

                  1 Reply Last reply Reply Quote 0
                  • J
                    jahonix
                    last edited by Nov 5, 2008, 8:19 AM

                    Which version of pfSense are you using?
                    Embedded or full install?

                    1 Reply Last reply Reply Quote 0
                    • T
                      Tib
                      last edited by Nov 6, 2008, 7:31 AM

                      I use pfSense-1.2-BETA-1 with full install, not embedded

                      1 Reply Last reply Reply Quote 0
                      • N
                        nocer
                        last edited by Nov 6, 2008, 9:43 AM

                        There's much more decent version(s) available.

                        1 Reply Last reply Reply Quote 0
                        • J
                          jahonix
                          last edited by Nov 6, 2008, 10:56 AM

                          I seem to remember that there were PPPoE problems in an early 1.2 version.
                          Update to 1.2-release or one of the 1.2.1RCs and see if your problem goes away is my best bet.

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