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

    pfSense+ MultiWAN False reporting of Monitor IP down

    Scheduled Pinned Locked Moved Routing and Multi WAN
    8 Posts 4 Posters 637 Views 4 Watching
    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.
    • K Offline
      KB8DOA
      last edited by

      pfSense+
      I have a SG-5100 (running v25.07.1) where:
      MultiWAN

      WAN2
      Status: Danger, Packetloss

      Even though I can go to
      Diagnostics,PING
      Select that interface (WAN2)
      and am able to Ping everything okay
      including the Monitor IP Address for that Gateway...

      I have to now set
      Disable Gateway Monitoring Action
      so that I can use that interface

      Have tried restarting dpinger service
      still having problem

      Can anyone advise on what this could be?

      w0wW T 2 Replies Last reply Reply Quote 0
      • w0wW Offline
        w0w @KB8DOA
        last edited by w0w

        @KB8DOA
        Did you set monitoring IP under Routes WAN2 gateway?

        K 1 Reply Last reply Reply Quote 0
        • K Offline
          KB8DOA @w0w
          last edited by

          @w0w
          Yes I did:
          dbc0f13a-fd3b-4e0b-8a69-503467caf918-image.png

          Bob.DigB 1 Reply Last reply Reply Quote 1
          • Bob.DigB Offline
            Bob.Dig LAYER 8 @KB8DOA
            last edited by

            @KB8DOA Maybe it is already used or whatever. Try a different IP-address.

            K 1 Reply Last reply Reply Quote 1
            • K Offline
              KB8DOA @Bob.Dig
              last edited by

              @Bob.Dig

              Does not matter which PINGable IP Address I use, same problem.

              w0wW 1 Reply Last reply Reply Quote 0
              • w0wW Offline
                w0w @KB8DOA
                last edited by

                @KB8DOA
                Has this configuration ever worked properly at all? And what was done that made it stop working?

                K 1 Reply Last reply Reply Quote 0
                • T Offline
                  tman222 @KB8DOA
                  last edited by tman222

                  Hi @KB8DOA - From the screenshot you posted above, I assume you have T-Mobile 5G Home Internet running on WAN2? If so, I ran into similar issues recently. Under Advanced settings for your WAN2 gateway, try increasing the Data Payload parameter from the default value of 1. For T-Mobile Home Internet I believe 4 was the minimum value that worked for me, but you can choose a larger size as well. This is likely also the reason that regular pings succeeded through Diagnostics/Ping as these ping probes use 56 bytes of data by default vs. dpinger's 1.

                  https://docs.netgate.com/pfsense/en/latest/routing/gateway-configure.html#advanced-gateway-settings

                  Hope this helps.

                  1 Reply Last reply Reply Quote 1
                  • K Offline
                    KB8DOA @w0w
                    last edited by

                    @w0w said in pfSense+ MultiWAN False reporting of Monitor IP down:

                    @KB8DOA
                    Has this configuration ever worked properly at all? And what was done that made it stop working?

                    It works sometimes,
                    then all the sudden stops working.

                    I have just tried increasing the "weight" to 4,
                    per @tman222 suggestion.

                    I hope this resolves it...

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