dpinger needs gateway identification in logs
dpinger's logs currently have no identification of which gateway or which process they came from. The log output needs to contain something identifying the gateway.
Maybe the best way to do it would be adding a command argument for an identifier that it inserts into all its log messages. eg "dpinger ... -x GW_WAN ..." would include GW_WAN in all log output (replacing 'x' with whatever's available and makes sense).
As is, it can be difficult to troubleshoot multi-WAN and dual stack single WAN environments.