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

    Floating Rules order

    Scheduled Pinned Locked Moved General pfSense Questions
    19 Posts 3 Posters 1.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.
    • S
      Shan lapierre @stephenw10
      last edited by

      @stephenw10 ,Here what's say blocked rule:

      fbf98406-ebea-4367-b9ef-5e8976ac8197-image.png

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        That looks like it's hitting the WAN address? Unless the VoIP device has a public IP (routed) I expect a NAT rule to be forwarding that to some internal address.

        What is in the Audiocodes_MP112 alias?

        S 1 Reply Last reply Reply Quote 0
        • S
          Shan lapierre @stephenw10
          last edited by

          @stephenw10 exactly. AudiocodesMP alias is 192.168.1.20. So what's wrong in my configuration?

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Whatever port forward you have is not catching the incoming RTP traffic.

            But the forward you have for SIP is.

            S 1 Reply Last reply Reply Quote 0
            • S
              Shan lapierre @stephenw10
              last edited by

              @stephenw10 Ok ..that is clear 😃. I cannot understand why SIP port is matching and RTP not. Rules are done in same way . Is there some specific log to understand better ? And is there such a way to see a matched rule in some logs?

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Show us your NAT rules for that traffic.

                S 1 Reply Last reply Reply Quote 0
                • S
                  Shan lapierre @stephenw10
                  last edited by

                  @stephenw10 8fa3e9fb-ab47-4520-9101-31bde2e2395b-image.png
                  IP_Audiocodes_ACS = src public IP
                  Audiocodes_MP112 = internal device where RTP flow should be redirected

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, I'd expect that to match assuming the source and destination addresses match what's redacted above.

                    Especially since the SIP forward appears to work. I'd check the states though and make sure it actually is.

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      Shan lapierre @stephenw10
                      last edited by

                      @stephenw10 Sorry but "it actually is" what?

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        Make sure the NAT rule for SIP is actually working. The states will show the translation.

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