Gateway monitoring not working post-2.3 upgrade? Read here



  • If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

    Verify advanced options are sane

    Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

    Set ping payload size

    Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.



  • Hello all,

    dont be confused with

    Set ping payload size

    Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

    When you reboot unit payload size goes to "0", so you need to re-set it to work again.

    Cheers!



  • @ha11oga11o:

    Hello all,

    dont be confused with

    Set ping payload size

    Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

    When you reboot unit payload size goes to "0", so you need to re-set it to work again.

    Cheers!

    I couldn't reproduce that in my test VM. I set the payload to 1, it stuck in real-time, then I rebooted (a few times) and it starts dpinger with payload (data_len) 1 OK.

    If you have a way to reproduce the problem, then start a new thread in this forum and we can look into it.



  • @phil.davis:

    I couldn't reproduce that in my test VM. I set the payload to 1, it stuck in real-time, then I rebooted (a few times) and it starts dpinger with payload (data_len) 1 OK.

    If you have a way to reproduce the problem, then start a new thread in this forum and we can look into it.

    Yes, please. It definitely sticks. Many have configured it.



  • I can't make any changes to the settings on those pages. If I attempt to make that change (or any change, or no changes) and hit submit, it gives me…

    The following input errors were detected:
    The gateway name "WAN1_PPPOE" already exists.

    2.3-RELEASE (amd64)
    built on Mon Apr 11 18:28:29 CDT 2016
    FreeBSD 10.3-RELEASE

    --
    Ross



  • @agentdesign:

    I can't make any changes to the settings on those pages. If I attempt to make that change (or any change, or no changes) and hit submit, it gives me…

    The following input errors were detected:
    The gateway name "WAN1_PPPOE" already exists.

    You're hitting the duplicate button rather than the edit button in that case.



  • Myst say i was wrong. Was sure it was not sticks first three reboots for me cause mine gateway was always offline at a time. So i did it over and over again. Today i tried it couple of times just to confirm and i cannot reproduce it anymore.

    Mine sincerely apologies for false statement.



  • @cmb:

    If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

    Verify advanced options are sane

    Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

    Set ping payload size

    Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

    :o - Hooo De Hooo, this worked and seems to keep working.  Thank You Very Much. Verizon Actiontec modem seems to be the culprit.



  • Yes!! it works!! thax

    "Set ping payload size"

    From Colombia :)



  • It won't work for me :/

    EDIT: I have to put manually the gateway IP, now it works!



  • Hi all

    I changed my payload to 1 a while back and every thing seem to be working fine, but recently i keep getting these messeges in the log again and my upload seems terrible every now and then very flakey. Can anyone offer any help with this or to why this maybe happening. I have a home virgin media cable connection 200 down and 12 up and this is only part of the log it goes on and on.

    ![Capture gateway.PNG](/public/imported_attachments/1/Capture gateway.PNG)
    ![Capture gateway.PNG_thumb](/public/imported_attachments/1/Capture gateway.PNG_thumb)



  • Error 55 ENOBUFS: No buffer space available.  An operation on a socket or pipe was not performed because the system lacked sufficient buffer space or because a queue was full.

    https://doc.pfsense.org/index.php/No_buffer_space_available



  • @cmb:

    If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

    Verify advanced options are sane

    Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

    Set ping payload size

    Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

    This worked for me after soooo long, I had to disable gateway monitoring for a while  8)



  • If my post is not the same problem that is being discussed, please let me know. Thanks!

    2.4.0-BETA (arm)
    built on Sun Apr 09 20:40:03 CDT 2017
    FreeBSD 11.0-RELEASE-p8

    When I got to Status > Monitoring I get this error: Error: JSON not returned. Check to make sure you have an active session.  Tried the "verify advanced options are sane" and " set ping payload size" suggestions.

    Here is the crash report:
    arm
    11.0-RELEASE-p8
    FreeBSD 11.0-RELEASE-p8 #0 f7e03ae750f(RELENG_2_4): Sun Apr  9 20:53:07 CDT 2017    root@buildbot2.netgate.com:/xbuilder/pfsense-crossbuild/work/obj-ufw-armv6/arm.armv6/builder/factory/tmp/FreeBSD-src/sys/pfSense-uFW

    Crash report details:

    PHP Errors:
    [10-Apr-2017 17:23:28 America/Denver] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/rrd.so' - Shared object "libiconv.so.2" not found, required by "libglib-2.0.so.0" in Unknown on line 0
    [10-Apr-2017 17:23:36 America/Denver] PHP Warning:  PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/rrd.so' - Shared object "libiconv.so.2" not found, required by "libglib-2.0.so.0" in Unknown on line 0

    No FreeBSD crash data found.



  • Your issue is not related and should go to the 2.4 beta forum.

    @jano23:

    If my post is not the same problem that is being discussed, please let me know. Thanks!

    2.4.0-BETA (arm)
    built on Sun Apr 09 20:40:03 CDT 2017
    FreeBSD 11.0-RELEASE-p8

    When I got to Status > Monitoring I get this error: Error: JSON not returned. Check to make sure you have an active session.  Tried the "verify advanced options are sane" and " set ping payload size" suggestions.



  • Thanks!!



  • @cmb:

    If your gateway monitoring isn't working post-2.3 upgrade, it's likely one of two things.

    Verify advanced options are sane

    Browse to System>Routing and edit the gateway that's down. Then click Save. That will trigger the input validation that makes sure the configuration is valid, especially the advanced options. You may have had options set for apinger that are not valid for dpinger. If you get any errors upon saving, fix them, save, and apply changes.

    Set ping payload size

    Some modems have a bug that makes them drop pings with 0 byte payloads. dpinger uses a 0 byte payload by default because there isn't a need to include one and unnecessarily chew up bandwidth. If you have such a buggy upstream device, you'll need to set the payload to something greater than 0. System>Routing, edit the gateway, go to Advanced, and set payload to 1. Save and apply changes.

    Yes, it works again  ;D



  • I have this same issue. I opend a new thread to this but no one seems to care, so my hopes are on this old thread. (I also have an old thread I have this issue for over year. My internet connection is faulty. It breaks more than 5 times a day. Now it is nearly unusable. I have tried the solutions on top of this thread but they don' t work for me.
    My IPv4 connection is now lost. I can't ping via IPV4 anywhere directly from the pfsense but I can ping with IPv6.

    These are a short part of my logs

    Sep 27 23:05:21 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18942us stddev 11004us loss 20%
    Sep 27 23:05:01 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 22870us stddev 37951us loss 21%
    Sep 27 22:58:56 	dpinger 		WAN_DHCP 192.168.178.1: Alarm latency 0us stddev 0us loss 100%
    Sep 27 22:58:54 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.178.1 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 22:58:54 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 22:58:20 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.178.1 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 22:52:02 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:44:36 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:44:26 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 0us stddev 0us loss 100%
    Sep 27 22:44:24 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:44:24 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 22:42:22 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 23531us stddev 37799us loss 21%
    Sep 27 22:42:18 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 23398us stddev 36773us loss 15%
    Sep 27 22:42:07 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 21876us stddev 31405us loss 21%
    Sep 27 22:42:06 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 21977us stddev 31212us loss 20%
    Sep 27 22:41:13 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 30288us stddev 74835us loss 21%
    Sep 27 22:41:07 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 29223us stddev 72964us loss 20%
    Sep 27 22:40:52 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 31160us stddev 75441us loss 21%
    Sep 27 22:40:24 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 19065us stddev 17514us loss 10%
    Sep 27 22:39:56 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 17123us stddev 12837us loss 21%
    Sep 27 22:39:46 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16339us stddev 9660us loss 13%
    Sep 27 22:39:16 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18434us stddev 13582us loss 22%
    Sep 27 22:39:12 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18434us stddev 13582us loss 17%
    Sep 27 22:38:36 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 24315us stddev 24142us loss 29%
    Sep 27 22:38:28 	dpinger 		WAN_DHCP 90.187.254.174: Alarm latency 0us stddev 0us loss 100%
    Sep 27 22:38:26 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:38:26 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 22:38:26 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 90.187.254.174 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 22:37:55 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 12971us stddev 1020us loss 33%
    Sep 27 22:37:54 	dpinger 		WAN_DHCP 90.187.254.174: Alarm latency 0us stddev 0us loss 100%
    Sep 27 22:37:52 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:37:52 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 22:37:52 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 90.187.254.174 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 22:37:49 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 65898us stddev 129437us loss 8%
    Sep 27 22:37:39 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 109812us stddev 140017us loss 25%
    Sep 27 22:37:39 	dpinger 		WAN_DHCP 90.187.254.174: Alarm latency 0us stddev 0us loss 100%
    Sep 27 22:37:37 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:37:37 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 22:37:37 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 90.187.254.174 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 22:37:20 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18179us stddev 17994us loss 21%
    Sep 27 22:37:09 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 17043us stddev 11430us loss 14%
    Sep 27 22:36:43 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 21232us stddev 26477us loss 21%
    Sep 27 22:36:30 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 23360us stddev 36920us loss 10%
    Sep 27 22:36:02 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 24629us stddev 40607us loss 22%
    Sep 27 22:33:31 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 19039us stddev 13784us loss 19%
    Sep 27 22:32:21 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18912us stddev 20095us loss 22%
    Sep 27 22:30:11 	dpinger 		WAN_DHCP 90.187.254.174: Alarm latency 0us stddev 0us loss 100%
    Sep 27 22:30:09 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 22:30:09 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 22:30:09 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 90.187.254.174 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 22:25:40 	dpinger 		WAN_DHCP 90.187.254.174: Alarm latency 17381us stddev 14238us loss 22%
    Sep 27 22:18:29 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18394us stddev 19253us loss 15%
    Sep 27 22:18:01 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15133us stddev 6938us loss 21%
    Sep 27 22:16:45 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15888us stddev 8962us loss 14%
    Sep 27 22:16:17 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 21889us stddev 41423us loss 21%
    Sep 27 22:16:11 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20384us stddev 39470us loss 11%
    Sep 27 22:15:40 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 19342us stddev 41124us loss 21%
    Sep 27 22:15:36 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 17577us stddev 34716us loss 16%
    Sep 27 22:15:09 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15073us stddev 13839us loss 21%
    Sep 27 22:13:51 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 21922us stddev 55519us loss 14%
    Sep 27 22:13:39 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 20312us stddev 54497us loss 21%
    Sep 27 22:10:14 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20150us stddev 46425us loss 14%
    Sep 27 22:09:31 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 23338us stddev 53801us loss 21%
    Sep 27 22:08:52 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20520us stddev 48077us loss 7%
    Sep 27 22:08:38 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 20059us stddev 45499us loss 21%
    Sep 27 22:08:30 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 19498us stddev 44054us loss 16%
    Sep 27 22:07:22 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 16980us stddev 20510us loss 21%
    Sep 27 22:07:06 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14885us stddev 12362us loss 10%
    Sep 27 22:06:53 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15103us stddev 13185us loss 22%
    Sep 27 22:06:42 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14509us stddev 11471us loss 15%
    Sep 27 22:06:02 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14737us stddev 9092us loss 22%
    Sep 27 22:05:59 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14999us stddev 10003us loss 17%
    Sep 27 22:05:33 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15163us stddev 10104us loss 22%
    Sep 27 22:03:53 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 21864us stddev 49705us loss 10%
    Sep 27 22:03:28 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15839us stddev 11636us loss 21%
    Sep 27 22:03:14 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16156us stddev 14060us loss 15%
    Sep 27 22:02:46 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15623us stddev 12889us loss 21%
    Sep 27 22:01:07 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 17234us stddev 13466us loss 13%
    Sep 27 22:00:42 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 16622us stddev 15238us loss 22%
    Sep 27 21:56:45 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20371us stddev 48010us loss 15%
    Sep 27 21:56:11 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 30801us stddev 86485us loss 22%
    Sep 27 21:56:01 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 28535us stddev 81819us loss 15%
    Sep 27 21:55:41 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 30860us stddev 85799us loss 21%
    Sep 27 21:51:31 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16817us stddev 18189us loss 12%
    Sep 27 21:51:20 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15149us stddev 11201us loss 21%
    Sep 27 21:50:42 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 17327us stddev 26100us loss 11%
    Sep 27 21:50:27 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18395us stddev 27503us loss 21%
    Sep 27 21:49:53 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16282us stddev 17789us loss 10%
    Sep 27 21:49:39 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 20627us stddev 52865us loss 21%
    Sep 27 21:47:54 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15004us stddev 12733us loss 20%
    Sep 27 21:47:31 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15555us stddev 12269us loss 21%
    Sep 27 21:47:26 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15729us stddev 12387us loss 20%
    Sep 27 21:47:13 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 17488us stddev 21772us loss 21%
    Sep 27 21:43:24 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 13421us stddev 9593us loss 13%
    Sep 27 21:43:06 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 13677us stddev 9139us loss 21%
    Sep 27 21:39:25 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14495us stddev 10067us loss 13%
    Sep 27 21:38:56 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14193us stddev 9780us loss 22%
    Sep 27 21:38:48 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14216us stddev 9355us loss 12%
    Sep 27 21:38:18 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 21578us stddev 59549us loss 22%
    Sep 27 21:38:12 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20280us stddev 56051us loss 14%
    Sep 27 21:37:42 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18879us stddev 55041us loss 22%
    Sep 27 21:30:23 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18373us stddev 27209us loss 13%
    Sep 27 21:30:02 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 17953us stddev 23472us loss 21%
    Sep 27 21:29:34 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15713us stddev 10394us loss 12%
    Sep 27 21:29:17 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15561us stddev 9260us loss 21%
    Sep 27 21:26:29 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20604us stddev 34894us loss 14%
    Sep 27 21:26:11 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18945us stddev 24912us loss 21%
    Sep 27 21:26:00 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16437us stddev 17621us loss 11%
    Sep 27 21:23:52 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 19156us stddev 55120us loss 22%
    Sep 27 21:19:36 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 21:19:36 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 21:19:36 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 90.187.254.174 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 21:19:24 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 192.168.10.1 bind_addr 192.168.10.1 identifier "OPENVPN_VPNV4 "
    Sep 27 21:19:24 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr fe80::1%igb2 bind_addr fe80::ec4:7aff:fead:bce%igb2 identifier "WAN_DHCP6 "
    Sep 27 21:19:24 	dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 90.187.254.174 bind_addr 90.187.254.173 identifier "WAN_DHCP "
    Sep 27 21:19:21 	dpinger 		WAN_DHCP 90.187.254.174: sendto error: 65
    Sep 27 21:19:20 	dpinger 		WAN_DHCP 90.187.254.174: sendto error: 65
    Sep 27 21:19:20 	dpinger 		WAN_DHCP 90.187.254.174: sendto error: 65
    Sep 27 21:18:14 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15229us stddev 13348us loss 13%
    Sep 27 21:17:48 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14866us stddev 12896us loss 21%
    Sep 27 21:15:40 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14922us stddev 17024us loss 10%
    Sep 27 21:15:14 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 15972us stddev 12052us loss 21%
    Sep 27 21:14:19 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 13902us stddev 9274us loss 19%
    Sep 27 21:12:02 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 19716us stddev 40677us loss 21%
    Sep 27 21:08:59 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 19812us stddev 50929us loss 17%
    Sep 27 21:08:37 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14609us stddev 8636us loss 21%
    Sep 27 21:08:13 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14654us stddev 9832us loss 20%
    Sep 27 21:06:43 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 16390us stddev 13537us loss 21%
    Sep 27 21:05:48 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18581us stddev 37369us loss 13%
    Sep 27 21:05:20 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 16746us stddev 20929us loss 22%
    Sep 27 21:02:47 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15256us stddev 11394us loss 12%
    Sep 27 21:02:16 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 20611us stddev 53514us loss 21%
    Sep 27 21:02:09 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 19400us stddev 50163us loss 13%
    Sep 27 21:01:41 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 22054us stddev 61990us loss 21%
    Sep 27 21:01:27 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16267us stddev 32759us loss 10%
    Sep 27 21:01:03 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14230us stddev 8298us loss 21%
    Sep 27 21:00:44 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18140us stddev 37817us loss 14%
    Sep 27 21:00:24 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18862us stddev 39509us loss 21%
    Sep 27 20:57:11 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 17529us stddev 31807us loss 10%
    Sep 27 20:56:47 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14498us stddev 11949us loss 21%
    Sep 27 20:56:26 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14494us stddev 16001us loss 13%
    Sep 27 20:56:07 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 16520us stddev 21655us loss 21%
    Sep 27 20:55:32 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14250us stddev 15845us loss 17%
    Sep 27 20:55:20 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 13415us stddev 9317us loss 21%
    Sep 27 20:53:15 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15464us stddev 7394us loss 14%
    Sep 27 20:52:04 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18328us stddev 28551us loss 21%
    Sep 27 20:51:49 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15860us stddev 12591us loss 16%
    Sep 27 20:51:37 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 20252us stddev 33449us loss 22%
    Sep 27 20:50:56 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 18891us stddev 30745us loss 12%
    Sep 27 20:50:41 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 17990us stddev 25289us loss 21%
    Sep 27 20:50:38 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 15509us stddev 9187us loss 16%
    Sep 27 20:47:32 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 22687us stddev 44383us loss 21%
    Sep 27 20:47:06 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 17325us stddev 11087us loss 16%
    Sep 27 20:46:48 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 16877us stddev 9718us loss 21%
    Sep 27 20:46:44 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20273us stddev 35513us loss 15%
    Sep 27 20:45:38 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 19943us stddev 37216us loss 21%
    Sep 27 20:42:43 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 28508us stddev 71614us loss 10%
    Sep 27 20:42:17 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 27694us stddev 63256us loss 22%
    Sep 27 20:42:03 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 24082us stddev 56903us loss 13%
    Sep 27 20:41:38 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 19029us stddev 30785us loss 21%
    Sep 27 20:41:15 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 19635us stddev 21161us loss 11%
    Sep 27 20:40:58 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 21759us stddev 22155us loss 21%
    Sep 27 20:40:28 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 20761us stddev 33837us loss 10%
    Sep 27 20:40:12 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 20822us stddev 35510us loss 21%
    Sep 27 20:33:41 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16756us stddev 24790us loss 10%
    Sep 27 20:33:18 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14270us stddev 8980us loss 21%
    Sep 27 20:31:49 	dpinger 		WAN_DHCP 90.187.254.174: Alarm latency 15270us stddev 8250us loss 22%
    Sep 27 20:25:18 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 13638us stddev 8796us loss 14%
    Sep 27 20:24:44 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 18884us stddev 54552us loss 22%
    Sep 27 20:20:41 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 16169us stddev 22932us loss 10%
    Sep 27 20:20:28 	dpinger 		WAN_DHCP6 fe80::1%igb2: Alarm latency 14317us stddev 11945us loss 21%
    Sep 27 20:20:16 	dpinger 		WAN_DHCP6 fe80::1%igb2: Clear latency 14147us stddev 12071us loss 14%
    

    Does someone has a clue or a solution, please?



  • You don't have this issue, this issue is over three years old and relates to the changes in 2.3.
    You don't have an issue with monitoring, you have an issue with packet loss through your fritzbox.
    You opened that one this morning and now you're reviving an old post because no one has jumped in to give you a solution yet? Give it some time, I expect your issue is specific to the fritzbox, and most of the users in the English forums are not familiar with this configuration.



  • @dotdash I must admit that you are absolutely right. I am a very impatient person. ;)
    A couple of minutes ago I finally changed the Payload of the ping (I did it not right at the beginning). Also I inserted a monitoring IP on the interfaces. Now it seems to work but I have absolutely no clue why.


Log in to reply