[SOLVED] Dpinger not starting after upgrade

[andbrazil]

After the upgrade to 19.1 my Gateways are been detected as Offline as the Dpinger service don't start. (I use Apinger before)

I don't look further because I am afraid to lost connection with this OPNsense box as I upgrade this server remotely.

Anyway I see that if I removed the information in the advanced section of the gateway, in the case of the secondary gateway the Probe Interval, the Dpinger service started normally.

I use two gateways in a Failover configuration, and temporarily I set up the gateway with the primary connection as always online setting the box "Disable Gateway Monitoring".

In the primary gateway, that I don't test as I don't want to risk lose connection and that I leave the monitoring disabled I have several options in the advanced section customized, like Latency thresholds, Packet Loss thresholds, and Probe Interval. Probably these are the reasons that the service Dpinger are not starting.

Any idea if these advanced configurations are not working with Dpinger or this is a problem caused by the upgrade and I need to reinstall and load the configuration files?

[Northguy]

FYI: There is already a thread on this subject here: https://forum.opnsense.org/index.php?topic=11430.0

[marjohn56]

Can you tell me what settings you have for dpinger?


It's possible that a value you had for Apinger is not valid with dpinger and it's being transferred across. Perhaps we should have put a validation routine in there to check the values. Post them anyway and I'll put them into my  test unit and see if that's what the issue is.

[andbrazil]

Here are the values I use for the first Gateway:
Latency thresholds From: 400 To: 700
Packet Loss thresholds From:20 To: 40
Probe Interval: 30

Value for the second Gateway:
Probe Interval: 30

[marjohn56]

Do you really want it to only send an ICMP packet once every 30 seconds?


If so then you need to increase the Time Period from the default 60 to more than twice the probe interval... 63 works... 62 doesn't. There's obviously some sort of maths going on there but I'm not going to try and work out what it is at present.


It doesn't say much in the dpinger manual ( err what manual? ), and the command line help is not of much help either.


I've just tried a few variables and worked out that this appears to be the case.


When you set a long period like that it will show offline for quite a while until it's received a few pings.

[andbrazil]

Do you really want it to only send an ICMP packet once every 30 seconds?

Thanks! I changed the Probe Interval from 30 to 20 and both Dpinger services started now.

[marjohn56]

Great. Can you edit the subject and add [SOLVED], it makes it quicker for others looking for solutions.

[franco]

Changed topic. Shall we record this issue in a ticket?


Cheers,
Franco

[marjohn56]

I guess we should. Then we could at least add a warning or add a validation check.