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

    pfsense blocking TCP:S when port forwarding for Plex

    Scheduled Pinned Locked Moved Firewalling
    9 Posts 3 Posters 4.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.
    • U
      Username_1
      last edited by

      I am running 2.4.4-RELEASE-p2.

      I have a NAT rule set up to pass traffic over port 32400 to my internal Plex server.

      When I go to the application to configure the remote access it appears to work initially and then dies.

      Afterwards I see blocks in my firewall logs blocking TCP:S trying to communicate to this server.

      If I enable 1:1 NAT with the firewall rules it works, but if I disable 1:1 it doesn't.

      Here is the log entry showing the TCP:S block
      pfsense_tcp_s_block.PNG

      The following are my NAT and FW rules.

      NAT.PNG
      firewall_rule.PNG
      firewall_rule_details_1.PNG
      firewall_rule_details_2.PNG

      I am not entirely sure what I am missing here.

      1 Reply Last reply Reply Quote 0
      • U
        Username_1
        last edited by

        Just realized I used slightly older screenshots. Source port range is any/any

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by Derelict

          Show us where it shows it's blocking it.

          Show the NAT rule.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

            Is the destination address shown in your block log entry the WAN IP address? Or a VIP? Try setting it specifically on the NAT rule instead of using the interface address macro.

            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 1
            • U
              Username_1 @Derelict
              last edited by

              @Derelict It's being blocked in the first image.

              Here is the expanded NAT rule

              NAT_Rule.PNG

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Yeah NAT is obviously not happening there for some reason so something is not matching in the NAT rule. Since 1:1 works it is probably something to do with the ports.

                If that logged block was from when a source port was configured that would certainly cause that.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate
                  last edited by

                  Your destination host needs to be the outside address. The target IP is the inside address.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

                  U 1 Reply Last reply Reply Quote 0
                  • U
                    Username_1 @Derelict
                    last edited by

                    @Derelict That was exactly it.

                    Thanks for catching that!

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      Port forwarding 101, man.

                      https://www.netgate.com/docs/pfsense/nat/forwarding-ports-with-pfsense.html

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

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