Messages

Ok so I found the config in /usr/local/etc/monitrc and that helped me understand a little more.

I see that file is auto generated by opnsense - it looks like what I would want to do is replace "then alert" with "then exec ..." on each of the items which is less than ideal.  How would I do this so it gets auto generated each time instead of just in this text file?

I'm trying to figure out how to get pushover working on my opnsense system.

I installed curl with pkg

I have followed the instructions here and a created .monitrc but updated it to reflect that pushover.sh is in /root
https://mmonit.com/wiki/MMonit/PushoverNotification
I create /root/.monitrc
and
/root/pushover.sh

I update the location of curl to be correct and confirm the script runs with blank data when I run it manually.
I can't find check_mysql.sh on the filesystem, nor am I certain this implementation is using mysql.   

Anyone have ideas for next steps? 
I would really like to get away from SMTP

I'm running Wireguard on clients (raspbian, Windows, iOS) connecting to a remote server in a hub and spoke configuration.

I'm running 23.7.12 on amd64 .

If I loose my WAN connection for a bit or move to a different WAN connection (cellular modem) - while on the cell connection and when I move back to the cable modem the Wireguard tunnels don't come back. 
I can make them come back by:
    Stopping and starting the wireguard service on the client
     Changing the listen port on the client without stopping/starting
    Manually clearing the entire state table on the firewall

Do folks have suggestions on tuning this so that manual intervention is not required?

What else can I check?

Is there a way to configure Monit to send alerts on dynamic DNS update failure?
It currently sends me interface alterts, but I'm not sure how to go about adding an alert for when dynamic DNS updates fail.