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

    Port Forwarding doesn't work.

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    10 Posts 6 Posters 2.3k 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.
    • E
      eshield
      last edited by

      Hello,

      I've been testing 2.2 x64 builds for a few weeks till now and noticed that port forwarding still doesn't working (Nobody uses it?  :o).

      FW log has entry about successfull connection, but Diagnostics: Show States has:
      WAN tcp 10.0.0.2:3389 (172.16.20.1:3389) <- 172.16.2.1:61287   CLOSED:SYN_SENT

      In fact, there is no packets are being forwarded to the host. Outbound NAT is working as expected.

      Do I miss something or it's a known problem?

      1 Reply Last reply Reply Quote 0
      • Raul RamosR
        Raul Ramos
        last edited by

        Hi

        Maybe have to do with this? Have you change MTU in the WAN interface? https://redmine.pfsense.org/issues/3666#change-14107.

        I have no problems, but i have not change MTU on any interface.

        pfSense:
        ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
        Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
        NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

        1 Reply Last reply Reply Quote 0
        • E
          eshield
          last edited by

          @mais_um:

          Hi

          Maybe have to do with this? Have you change MTU in the WAN interface? https://redmine.pfsense.org/issues/3666#change-14107.

          I have no problems, but i have not change MTU on any interface.

          Thanks for an answer, but it's not the case. I already played with MTUs on both ifaces. Affects nothing.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            Works fine here on the latest snap.

            WAN tcp 192.168.1.100:8888 (192.168.2.86:8888) <- 192.168.2.32:33375 ESTABLISHED:ESTABLISHED
            LAN tcp 192.168.2.32:33375 -> 192.168.1.100:8888 ESTABLISHED:ESTABLISHED

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • E
              eshield
              last edited by

              Ok, I will double check my conf one more time.

              1 Reply Last reply Reply Quote 0
              • S
                steve72
                last edited by

                Same problems here.

                Upgraded from 2.1.4 to 2.2.

                Running portforwards on both the WAN interface and OPT1 which is a OpenVPN client.

                If I stop the OpenVPN service the portforward on the WAN interface starts working again.
                If i start the OpenVPN service the portforwards stop working on the WAN interface again.

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  That sounds like it could be a config issue, if your OpenVPN client is acting as your default gateway then the behavior you're seeing could be expected if the WAN rules do not get reply-to set (reply-to disabled, no GW selected on Interfaces > WAN, etc)

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • S
                    steve72
                    last edited by

                    I'm pretty sure the WAN was set to the default gateway. But since I reverted back to 2.1.4 I can't check it out.

                    1 Reply Last reply Reply Quote 0
                    • S
                      series_of_tubes
                      last edited by

                      I have the exact same problem.  If the OpenVPN client tunnels are up, port forwarding does not work.  Once they are off, forwarding works as expected.  WAN is set as the default GW. System is 2.2 Beta AMD64 full install.

                      1 Reply Last reply Reply Quote 0
                      • I
                        illizit
                        last edited by

                        I am having the same issue. We use Port forwarding on a DSL WAN connection (MTU of 1492) and we cannot pass traffic.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.