Dipnger logging with multiple gateways



  • 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 ??



  • 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.


  • LAYER 8 Moderator

    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.


  • Netgate

    @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



  • 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%



  • @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]


Log in to reply