DateSeverityProcessLine 2024-05-24T08:59:51 Warning dpinger send_interval 1000ms loss_interval 4000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms dest_addr 100.64.0.1 bind_addr 100.109.13.234 identifier "WANGW " 2024-05-24T08:59:51 Warning dpinger exiting on signal 15 2024-05-24T08:59:51 Warning dpinger exiting on signal 15 2024-05-24T08:59:51 Warning dpinger exiting on signal 15 2024-05-24T08:50:04 Warning dpinger send_interval 1000ms loss_interval 4000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms dest_addr 100.109.13.234 bind_addr 100.109.13.234 identifier "WANGW " 2024-05-24T08:50:04 Warning dpinger exiting on signal 15 2024-05-24T08:50:03 Warning dpinger WANGW 100.109.13.234: sendto error: 65 2024-05-24T08:50:02 Warning dpinger WANGW 100.109.13.234: sendto error: 65 2024-05-24T08:50:01 Warning dpinger WANGW 100.109.13.234: sendto error: 65 2024-05-24T08:35:47 Warning dpinger send_interval 1000ms loss_interval 4000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 0ms loss_alarm 0% alarm_hold 10000ms dest_addr 100.109.13.234 bind_addr 100.109.13.234 identifier "WANGW " 2024-05-24T08:35:47 Warning dpinger exiting on signal 15 2024-05-24T08:35:46 Warning dpinger WANGW 100.109.13.234: sendto error: 65 2024-05-24T08:35:45 Warning dpinger WANGW 100.109.13.234: sendto error: 65
I can confirm this issue on StarLink WAN: https://forum.opnsense.org/index.php?topic=40613.0As temporary workaround I deactivated gateway monitoring for SL WAN
A couple of things:1. What thresholds do you have set to fail over with? i.e. Packetloss high/low or Latency high/low?2. The graphs you showed looked like RRDtool graph? Is that smokeping you're using? The default for it is 20 pings every 300 seconds, so it not showing wouldn't be a surprise. if it's not that, how often is the pinger used for those graphs going off?