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

    Rp_filter

    Routing and Multi WAN
    3
    6
    5.9k
    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
      MAuVE
      last edited by

      Please let me know whether rp_filter is used by default in pfsense and if yes, how can I disable it.

      1 Reply Last reply Reply Quote 0
      • B
        billm
        last edited by

        @MAuVE:

        Please let me know whether rp_filter is used by default in pfsense and if yes, how can I disable it.

        A google search for that term turns up lots of linux hits.  pfSense runs on FreeBSD, not linux.  Maybe if you can give us more information on what rp_filter does in linux we could tell you if the equivalent is enabled or disabled on our platform.

        –Bill

        pfSense core developer
        blog - http://www.ucsecurity.com/
        twitter - billmarquette

        1 Reply Last reply Reply Quote 0
        • M
          MAuVE
          last edited by

          It may have another name in FreeBSD.

          For example in IOS it is called "unicast Reverse Path Forwarding (uRPF)"

          It is an anti-spoofing measure and most firewalls employ it.

          It checks the reverse path of a packet being as expected by the routing table.

          Suppose you have a box with two WAN interfaces and you send a ping to an ip address via interface A.

          If the routing is asymmetric the response may come through interface B.

          If an rp_filter function is active it will drop the response  packet, creating a "black hole".

          I am facing such a situation and wanted to see if there is a function like this activated by default in pfSense.

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by

            I think that should be handled by the created states just fine as they are created per interface.

            1 Reply Last reply Reply Quote 0
            • B
              billm
              last edited by

              OK, now I understand what you're looking for.  The pf version in FreeBSD doesn't support this at this time, the closest we have is the ability to do interface bound state.  But due to the likelyhood of users having carp pairs with different NICs, we're using a box-wide state table instead of interface bound.  So I think what you want is already our default.

              –Bill

              pfSense core developer
              blog - http://www.ucsecurity.com/
              twitter - billmarquette

              1 Reply Last reply Reply Quote 0
              • M
                MAuVE
                last edited by

                Thanks to all responders

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