dpinger Needs Frequent Manual Restarts - Multi-WAN

[AK_Astro]

Hello, running latest OPNsense 23.1.1_2-amd64 on a dedicated mini-PC router with two WAN gateways configured for failover Tier 1 and 2 according to the documentation.

I've been having this issue for several weeks that dpinger needs to be frequently restarted from the dashboard manually or it won't detect that the Tier 1 network is back up. Sometimes dpinger appears green and sometimes it's fully stopped and red. My Tier 1 is starlink which is rather spotty (frequent 1-10s interruptions here in Alaska).

Is there anywhere I can tune dpinger to be more aggressive in rechecking for good gateway?

An easy band aid fix would be a cron job that resets dpinger every 5 min or so but that's not ideal and not an option under the cron menu.

Any help or pointers would be greatly appreciated. Please let me know if I need more info to be able to be helped.

[AK_Astro]

Any possible ideas why dpinger appears to get stuck "offline"? I just had a 45 min outage on my Tier 1 and had to manually restart it (totally off and red) and it immediately recognized as online. Very frustrating.

[Kaeltis]

This has happened to me as well when I still had fail over set up.
Since my main connection only failed rarely, I "solved" the issue by rebooting the firewall every night, but yeah, very annoying and would love to see a solution.

[axsdenied]

It sounds like you're experiencing the same issue I have described here:

https://forum.opnsense.org/index.php?topic=32490.msg157169#msg157169

I brought this up awhile ago and there have been no responses from the community or devs unfortunately.  Would love to identify the root cause as either a bug, configuration issue or maybe my stupidity.  Whichever confirmation would help :)

[AK_Astro]

Hmm that looks like a similar situation but I don't need to reboot the whole router, just the dpinger service. If I had the skillset to write a script to restart it on a certain time frequency that would be a workable bandaid for myself. Or even knowing how to add it to the list of cron jobs.

[Greelan]

This may help you: https://forum.opnsense.org/index.php?topic=18745.msg97953#msg97953

[AK_Astro]

This may help you: https://forum.opnsense.org/index.php?topic=18745.msg97953#msg97953

Thanks, I'll take a look.

[lzamel]

I was observing similar (if not exactly the same) behavior. It all stopped after I correctly set System: Settings: General: DNS servers
By correct I mean each GW is listed and uses same DNS server as one used to monitor status.
I didn't debug why this helped on my setup, but I haven't seen dpinger stuck since.

[AK_Astro]

Interesting, they have been the same (different monitor source for each gateway, but matched in both settings pages) already.