Adjust dpinger default values to match recent changes in dpinger project
Remove workaround to get dpinger running when interface is in tentative state
Make sure source and target addresses have scope id when they are link-local. It should fix #5695
Add a seatbelt to prevent 2 dpinger instances for same GW
Collect dpinger processes that failed to start and try again after 1 second, this should be enough to fix #5711
No need to return 0 here
Change start_dpinger() to return dpinger return code
Do not overwrite $params
Merge pull request #2332 from dennypage/master
Follow dpinger and change default loss_interval to 4* send_interval
Disable unused stdout reporting thread
update comment for dpinger
Return complete path for dpinger PID filename, it should fix #5686
Be less specific with dpinger PID filename regex, old version was not matching IPv6 addresses, with or without %ifname in case of ll
Rework dpinger related code to new version
- s/-U/-u/- Add i GW_NAME to get this info on logs and make life easier Since i parameter will be send to alert_cmd, remove it from command Add source and target IP addresses on pid/socket filename since status...
Remove all pfSense_MODULE and pfSense_BUILDER_BINARIES definitions, whatever was the reason they were added, it was never finished and it's not being used
Use default values for latencylow and losslow when they are not defined by user. Reported by grandrivers at https://forum.pfsense.org/index.php?topic=103818.msg579069#msg579069
Convert latency to ms before use it to compare with value defined in gateway conf
gwlb array key typo loss_interval
Ticket #5624: Welcome dpinger!
Move main pfSense content to src/