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

    Pfsense blocking portforwarded traffic on OPT interface

    Scheduled Pinned Locked Moved Firewalling
    7 Posts 2 Posters 1.1k 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.
    • M Offline
      Maarten90
      last edited by

      Hi all,

      Yesterday I made a new DMZ interface on Pfsense 2.2.5. Added a Default allow any rule for testing, portforwarded the needed port. But it is still being blocked by Pfsense. I can access the internet just fine from the server where the ports should be redirected to.

      I tested the portforward via canyouseeme.org . This method works just fine for checking portforwards on lan.

      Port forwards to the LAN interface work just fine. Tried to create a new one, and it worked immediately.

      Why does my portforward not work?

      1 Reply Last reply Reply Quote 0
      • H Offline
        hda
        last edited by

        @Maarten90:

        Why does my portforward not work?

        In Firewall Rules WAN you need:  IPv4* * * 192.168.3.10 9987 * none

        1 Reply Last reply Reply Quote 0
        • M Offline
          Maarten90
          last edited by

          @hda:

          @Maarten90:

          Why does my portforward not work?

          In Firewall Rules WAN you need:  IPv4* * * 192.168.3.10 9987 * none

          Thanks for your reply. That rule was automatically created by creating a NAT rule. I added a screenshot with the rule now :) .

          1 Reply Last reply Reply Quote 0
          • H Offline
            hda
            last edited by

            What do you need (ports, protocol)? UDP ? TCP ?

            1 Reply Last reply Reply Quote 0
            • M Offline
              Maarten90
              last edited by

              @hda:

              What do you need (ports, protocol)? UDP ? TCP ?

              I only need port 9987, UDP for Teamspeak

              1 Reply Last reply Reply Quote 0
              • H Offline
                hda
                last edited by

                The blocks show TCP…? Testing: start off broad (IPv4*), then narrow down (UDP and/or TCP, port(s)).

                1 Reply Last reply Reply Quote 0
                • M Offline
                  Maarten90
                  last edited by

                  @hda:

                  The blocks show TCP…? Testing: start off broad (IPv4*), then narrow down (UDP and/or TCP, port(s)).

                  Feeling very stupid now. Checked my rules and saw an old rule matching my old teamspeak server on LAN… Removed and it works now. Sorry!

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