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

    Dipnger logging with multiple gateways

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    6 Posts 6 Posters 1.2k 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.
    • G
      grandrivers
      last edited by

      when theres multiple gateways logs don't indicate problem gateway

      Dec 14 14:57:40 dpinger Clear: latency 24576us loss 4%
      Dec 14 14:57:16 dpinger Alarm: latency 25834us loss 22%

      is it possible to have dpinger monitor more than one ip/gateway ??

      pfsense plus 25.03 super micro A1SRM-2558F
      C2558 32gig ECC  60gig SSD

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

        I noticed that re: logging as I was testing various scenarios with dpinger today, that could make troubleshooting a real PITA. We'll get some kind of identifier there.
        https://redmine.pfsense.org/issues/5645

        For 2.3(.0 at least), you'll still be limited to a single monitor IP. Use IPs that are anycasted so should always reply reliably, like Google DNS, 4.2.2.2, 4.2.2.1, OpenDNS, etc. and you should be fine.

        1 Reply Last reply Reply Quote 0
        • JeGrJ
          JeGr LAYER 8 Moderator
          last edited by

          Just as a side note (won't go OT), AFAIK you shouldn't use 4.2.2.x as DNS/Ping checks if you don't have a connection to Level3. Their old DNS Anycast Servers 4.2.2.1-6 are serving, allright, but other than Googles public DNS they were never meant for public usage and they discourage use of it. (http://www.tummy.com/articles/famous-dns-server/)
          Also at some point they were intercepting wrong/failing dns calls and redirecting.

          Don't forget to upvote 👍 those who kindly offered their time and brainpower to help you!

          If you're interested, I'm available to discuss details of German-speaking paid support (for companies) if needed.

          1 Reply Last reply Reply Quote 0
          • J
            jwt Netgate
            last edited by

            @cmb:

            I noticed that re: logging as I was testing various scenarios with dpinger today, that could make troubleshooting a real PITA. We'll get some kind of identifier there.
            https://redmine.pfsense.org/issues/5645

            For 2.3(.0 at least), you'll still be limited to a single monitor IP. Use IPs that are anycasted so should always reply reliably, like Google DNS, 4.2.2.2, 4.2.2.1, OpenDNS, etc. and you should be fine.

            just needs integration now.

            https://github.com/dennypage/dpinger/commit/bfed5112c2060071e39417a2a3db3b1824aa6b15

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

              Dpinger was updated a couple days ago to include the target information in syslog entries. And again today to introduce a arbitrary identifier. Either will address this issue. It just takes a bit of time for the changes to flow through.

              @grandrivers:

              when theres multiple gateways logs don't indicate problem gateway

              Dec 14 14:57:40 dpinger Clear: latency 24576us loss 4%
              Dec 14 14:57:16 dpinger Alarm: latency 25834us loss 22%

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

                @JeGr:

                Just as a side note (won't go OT), AFAIK you shouldn't use 4.2.2.x as DNS/Ping checks if you don't have a connection to Level3. Their old DNS Anycast Servers 4.2.2.1-6 are serving, allright, but other than Googles public DNS they were never meant for public usage and they discourage use of it. (http://www.tummy.com/articles/famous-dns-server/)
                Also at some point they were intercepting wrong/failing dns calls and redirecting.

                What if your ISP uses Level 3?  8)

                tracert 4.2.2.2

                Tracing route to b.resolvers.Level3.net [4.2.2.2]
                over a maximum of 30 hops:

                1    1 ms    1 ms    1 ms  pfsense.localdomain [192.168.1.1]
                  2    2 ms    2 ms    1 ms  xxx
                  3    15 ms    14 ms    14 ms  xe-10-0-0.bar2.Minneapolis2.Level3.net [4.59.66.5]
                  4    *        *        *    Request timed out.
                  5    15 ms    15 ms    14 ms  b.resolvers.Level3.net [4.2.2.2]

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