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

    2.3 Quality monitoring not working

    Scheduled Pinned Locked Moved webGUI
    32 Posts 4 Posters 7.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.
    • A
      Apathia
      last edited by

      Still nothing. After I updated the Monitor IP, I checked the gateway status and it briefly said online though, but restarting the dpinger service did nothing after that.

      1 Reply Last reply Reply Quote 0
      • M
        Mikki-10
        last edited by

        If it was up to me i will backup my config and then re-install pfsense

        1 Reply Last reply Reply Quote 0
        • A
          Apathia
          last edited by

          I guess this is an issue that'll be addressed in a future update but for now I'll probably have to do a fresh install of 2.2.x since I need that feature to work.

          1 Reply Last reply Reply Quote 0
          • dennypageD
            dennypage
            last edited by

            Have you confirmed the ability to ping the address with the ping command? Assuming that works, try ping with size zero (-s 0) to see if that fails. If ping with size zero fails, you can set a data payload size in the advanced options in System/Routing/Gateways/Edit.

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              More than likely it's the 0 byte ping payload that's triggering a bug in something upstream of you (that is supposed to work, but doesn't in some cases). If you go to System>Routing, edit your gateway, set the payload to 1, it'll probably work. That may bring up the other possibility, combinations of advanced options that are no longer valid.

              1 Reply Last reply Reply Quote 0
              • A
                Apathia
                last edited by

                @cmb:

                More than likely it's the 0 byte ping payload that's triggering a bug in something upstream of you (that is supposed to work, but doesn't in some cases). If you go to System>Routing, edit your gateway, set the payload to 1, it'll probably work. That may bring up the other possibility, combinations of advanced options that are no longer valid.

                @dennypage:

                Have you confirmed the ability to ping the address with the ping command? Assuming that works, try ping with size zero (-s 0) to see if that fails. If ping with size zero fails, you can set a data payload size in the advanced options in System/Routing/Gateways/Edit.

                Looks like this was the issue, at least for ipv4. I set the payload to 1 and the gateway showed as online but the quality RRD graph still isn't showing anything.

                I also did a fresh install of 2.3 and it still doesn't work.

                1 Reply Last reply Reply Quote 0
                • A
                  Apathia
                  last edited by

                  I've been playing around with the quality graphs when I have time and have found that it works if I set the Monitor IP as my external IP, but if I try and use my ISPs DNS server (which worked before), it no longer works, regardless of whether "Use non-local gateway" under System > Routing is toggled or not.

                  Any help on this would be appreciated, these graphs are the easiest way to monitor packet loss and high pings from within my network as they come directly from the PC (PFSense box) connected to the modem rather than using my main PC connected to my PFSense box due to my ISP arguing that it's my router causing the issues.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    @Apathia:

                    I've been playing around with the quality graphs when I have time and have found that it works if I set the Monitor IP as my external IP, but if I try and use my ISPs DNS server (which worked before), it no longer works, regardless of whether "Use non-local gateway" under System > Routing is toggled or not.

                    Sounds like you probably need to set a payload, as I noted above in this thread, and here.
                    https://forum.pfsense.org/index.php?topic=110043.0

                    1 Reply Last reply Reply Quote 0
                    • A
                      Apathia
                      last edited by

                      @cmb:

                      @Apathia:

                      I've been playing around with the quality graphs when I have time and have found that it works if I set the Monitor IP as my external IP, but if I try and use my ISPs DNS server (which worked before), it no longer works, regardless of whether "Use non-local gateway" under System > Routing is toggled or not.

                      Sounds like you probably need to set a payload, as I noted above in this thread, and here.
                      https://forum.pfsense.org/index.php?topic=110043.0

                      Yes I've done this and all it did was make my Gateways show as online rather than offline, had no effect on the quality monitor though.

                      Here's a pic of the settings: http://i.imgur.com/dT88vQw.png

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        @Apathia:

                        Yes I've done this and all it did was make my Gateways show as online rather than offline, had no effect on the quality monitor though.

                        Here's a pic of the settings: http://i.imgur.com/dT88vQw.png

                        Uncheck "use non-local gateway", that's not applicable. Also looks like maybe you have your monitor IP set to your WAN IP, set that to 8.8.8.8 or something other than your own IP.

                        1 Reply Last reply Reply Quote 0
                        • A
                          Apathia
                          last edited by

                          @cmb:

                          @Apathia:

                          Yes I've done this and all it did was make my Gateways show as online rather than offline, had no effect on the quality monitor though.

                          Here's a pic of the settings: http://i.imgur.com/dT88vQw.png

                          Uncheck "use non-local gateway", that's not applicable. Also looks like maybe you have your monitor IP set to your WAN IP, set that to 8.8.8.8 or something other than your own IP.

                          It's set to monitor my isps dns server (prevents them from saying the issue is outside of their network), and it doesn't work regardless of whether or not "use non-local gateway" is checked. And yes, their dns server is pingable both from within pfsense and another pc on the network. I've also tried google dns server and it doesn't work either.

                          The only way I've actually gotten it to work is if I do actually set it to my own wan IP, but that defeats the whole purpose of it.

                          1 Reply Last reply Reply Quote 0
                          • C
                            cmb
                            last edited by

                            If it pings from Diag>Ping with WAN chosen as the source, then the only difference between that and what dpinger is doing for gateway monitoring is the payload size. 1 is still considerably smaller than what typical ping utilities use. Granted I've yet to hear of anything having issues at a 1 byte payload, it was just no payload that triggers bugs in other things dropping valid traffic. Try setting the payload to 56, which is the default of ping. That makes it the same as what Diag>Ping does.

                            That IP doesn't ping at all from here, but maybe it does within your ISP's network.

                            1 Reply Last reply Reply Quote 0
                            • dennypageD
                              dennypage
                              last edited by

                              To match the default behavior of ping, you need to use a data payload of 56 bytes. When ping reports that it received 64 bytes, the ICMP header (8 bytes) is included in the count.

                              1 Reply Last reply Reply Quote 0
                              • A
                                Apathia
                                last edited by

                                Works just fine in Diag > Ping but still nothing in the quality graphs even with the increased payload.

                                My ISP has a total of 4 DNS servers (64.71.255.204, 64.71.255.198, 2607:f798:18:10:0:640:7125:5204, and 2607:f798:18:10:0:640:7125:5198) and I've tried using them all to no avail.

                                screencapture-10-10-10-1-diag_ping-php-1461699716368.png
                                screencapture-10-10-10-1-diag_ping-php-1461699716368.png_thumb

                                1 Reply Last reply Reply Quote 0
                                • dennypageD
                                  dennypage
                                  last edited by

                                  Can you share a screenshot of your gateway status page (Status / Gateways)?

                                  And a screenshot of the config page for the gateway (System / Routing / Gateways / Edit)?

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    Apathia
                                    last edited by

                                    Yep.

                                    screencapture-10-10-10-1-status_gateways-php-1461710588853.png
                                    screencapture-10-10-10-1-status_gateways-php-1461710588853.png_thumb
                                    screencapture-10-10-10-1-system_gateways_edit-php-1461710610636.png
                                    screencapture-10-10-10-1-system_gateways_edit-php-1461710610636.png_thumb

                                    1 Reply Last reply Reply Quote 0
                                    • C
                                      cmb
                                      last edited by

                                      Thanks for the correction, Denny.

                                      So that screenshot of the status screen confirms it's working fine. What does a screenshot of the graph look like?

                                      1 Reply Last reply Reply Quote 0
                                      • A
                                        Apathia
                                        last edited by

                                        This

                                        screencapture-10-10-10-1-status_monitoring-php-1461711282614.png
                                        screencapture-10-10-10-1-status_monitoring-php-1461711282614.png_thumb

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          cmb
                                          last edited by

                                          Are all your other monitoring graphs fine? Any gateway names in the Graphs drop down other than those two? Seem to match up to the status page.

                                          1 Reply Last reply Reply Quote 0
                                          • A
                                            Apathia
                                            last edited by

                                            Everything else works fine (except for Queues/Queuedrops but I don't have any traffic shaping so it's not broken). Nothing else in the drop down menu.

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