Watchcat and luci-app-watchcat update

I certainly think that can be added

Any ETA about ipv6 support. would be perfect for me cause my ipv6 Preffix fails so often and my VPN server stopped working without working IPV6

I agree with all of your ideas. However, I recently noticed the need to be able to run a custom shell script as the modemmanager interface for watchcat, such as a shell script to restart the specific wifi radio that stopped working on the router.

If possible, I'd like to be able to restart the openvpn client service, as sometimes the far end seems to just go quiet so I need to manually stop and start the openvpn service...either by calling a shell script, or by having watchcat restart the service itself.

I've tried to stop the tun0 interface but that doesn't fix the problem, and if I try to ping a remote site via wan it can't connect (presumably because the firewall is denying any outbound connection that isn't via tun0.)

Thanks for this. Question on how I thought it worked vs. what I'm seeing happening though.

With this as the config:

config watchcat
	option mode 'restart_iface'
	option period '3m'
	option pinghosts '192.168.100.1'
	option pingperiod '30s'
	option pingsize 'standard'
	option interface 'eth0.2'

And the condition being met, would you expect the interface to be restarted every 30 seconds? Because that's what happens, as confirmed by the log. I was thinking 3 mins. It even says "after 180 seconds" in the log, but the timestamps say otherwise.

A snippet of the log showing that:

Sat Jul  2 15:43:18 2022 daemon.info watchcat[3727]: Could not reach 192.168.100.1 via "eth0.2" for "10392" seconds. Restarting "eth0.2" after reaching "180" seconds
Sat Jul  2 15:43:18 2022 user.notice INFO: Restarting network interface: "eth0.2".

[other stuff cut out for brevity]

Sat Jul  2 15:43:47 2022 daemon.info watchcat[3727]: Could not reach 192.168.100.1 via "eth0.2" for "10422" seconds. Restarting "eth0.2" after reaching "180" seconds
Sat Jul  2 15:43:47 2022 user.notice INFO: Restarting network interface: "eth0.2".

is it possible to run a n EXEC command based on a ping timeout?

(Example: wget -O- -q http://192.168.100.1:80/reset.htm?reset_modem=Restart+Cable+Modem)

There's an important feature i miss:

ping multiple targets, and perform action only, if all of the target's aren't reachable anymore.
Only having one target allows the scenario, that the target goes offline for whatever reason.

You can try over app pingcontrol