1
24.1 Legacy Series / Dpinger make a mess on latest release
« on: May 24, 2024, 09:10:07 am »
Hello,
Since a couple of days I have a problem with Dpinger and the gateway moniroting.
I have OPNsense 24.1.7_4-amd64 and I have a gateway group with 2 tiers:
• My Starlink connection is in Tier 1
• My ADSL connection is in Tier 2 for backup purposes.
Since I've got back from the holidays, I've noticed that Opnsense disconnects my starlink every 10 to 20 minutes.
The fact is that the starlink isn't disconnecting at all.
I also have monitoring of both my gateways on a LibreNMS instance locally, and it doesn't see these packet drops (Those showing are because a Starlink modem restart), see attachment.
And if I force all my internet to go through starlink, internal and external monitoring (I also self-host some things behind my starlink with some checks from OVH) doesn't see anything never ...
Same when I play online, I don't see any lag or get disconnected, but in the logs, the OPNSense says the gateway is lost.
Any idea of what may be going on?
Thank you
Since a couple of days I have a problem with Dpinger and the gateway moniroting.
I have OPNsense 24.1.7_4-amd64 and I have a gateway group with 2 tiers:
• My Starlink connection is in Tier 1
• My ADSL connection is in Tier 2 for backup purposes.
Since I've got back from the holidays, I've noticed that Opnsense disconnects my starlink every 10 to 20 minutes.
Code: [Select]
Date
Severity
Process
Line
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
The fact is that the starlink isn't disconnecting at all.
I also have monitoring of both my gateways on a LibreNMS instance locally, and it doesn't see these packet drops (Those showing are because a Starlink modem restart), see attachment.
And if I force all my internet to go through starlink, internal and external monitoring (I also self-host some things behind my starlink with some checks from OVH) doesn't see anything never ...
Same when I play online, I don't see any lag or get disconnected, but in the logs, the OPNSense says the gateway is lost.
Any idea of what may be going on?
Thank you