Dpinger detail level



  • i am getting duplicate echo reply's but can't tell which wan it is for sure but guessing its the cable modem

    Dec 20 05:31:48 dpinger CABLEMODEM_DHCP 8.8.8.8: Clear latency 25192us stddev 2800us loss 0%
    Dec 20 05:31:48 dpinger CABLEMODEM_DHCP 8.8.8.8: Clear latency 24674us stddev 1571us loss 0%
    Dec 20 05:31:28 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 4580083us stddev 5026014us loss 0%
    Dec 20 05:31:28 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 4729943us stddev 5001589us loss 0%
    Dec 20 05:31:19 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 11670949us stddev 7243863us loss 0%
    Dec 20 05:31:19 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 12068467us stddev 6945560us loss 0%
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:18 dpinger duplicate echo reply received
    Dec 20 05:31:01 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 24696us stddev 826us loss 26%
    Dec 20 05:31:00 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 24251us stddev 793us loss 25%
    Dec 20 01:54:13 dpinger DSL_DHCP 8.8.4.4: Clear latency 98522us stddev 232079us loss 0%
    Dec 20 01:54:12 dpinger DSL_DHCP 8.8.4.4: Clear latency 118783us stddev 280385us loss 0%
    Dec 20 01:51:21 dpinger DSL_DHCP 8.8.4.4: Alarm latency 514530us stddev 468126us loss 0%
    Dec 20 01:51:21 dpinger DSL_DHCP 8.8.4.4: Alarm latency 513464us stddev 467076us loss 0%
    Dec 20 01:51:21 dpinger CABLEMODEM_DHCP 8.8.8.8: Clear latency 24997us stddev 2002us loss 0%
    Dec 20 01:51:20 dpinger CABLEMODEM_DHCP 8.8.8.8: Clear latency 25036us stddev 1706us loss 0%
    Dec 20 01:50:46 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 522634us stddev 1096653us loss 0%
    Dec 20 01:50:46 dpinger CABLEMODEM_DHCP 8.8.8.8: Alarm latency 510188us stddev 1071301us loss 0%
    Dec 20 00:50:11 dpinger DSL_DHCP 8.8.4.4: Clear latency 122287us stddev 282883us loss 0%
    Dec 20 00:50:11 dpinger DSL_DHCP 8.8.4.4: Clear latency 107269us stddev 253374us loss 0%
    Dec 20 00:49:23 dpinger CABLEMODEM_DHCP 8.8.8.8: Clear latency 24284us stddev 555us loss 0%
    Dec 20 00:49:22 dpinger CABLEMODEM_DHCP 8.8.8.8: Clear latency 24419us stddev 503us loss 0%



  • A change like this to the dpinger code should help with that:
    https://github.com/dennypage/dpinger/pull/14



  • Denny sorted out a version of this https://github.com/dennypage/dpinger/commit/dcf1d2232259c00f4aae05095f91103b5da7ff7c
    I guess somebody is taking the latest dpinger code from there, testing and putting it into the pfSense repo?



  • I emailed Renato.



  • Hi all!

    When I have packetloss, dpinger does not report it in log.
    However this is in the log:
    Jan 9 21:54:09 dpinger WAN_DHCP 85.XX.XX.X: sendto error: 55

    Is there a reason why loss not reported, maybe cosmetic bug somwhere?

    Thanks!



  • Dpinger will report loss in the system log only if alerts have been defined. If you do a ps you can see the parameters dpinger has been started with. The alert parameters are -D (delay time) and -L (loss pct).

    Looking to the underlying issue: https://doc.pfsense.org/index.php/No_buffer_space_available



  • Gateway status turned yellow with packetloss text in it ..


Log in to reply