next »

[sullrich]

Look in /var/db/pingstatus

Each monitored item will appear there.  Simply look for DOWN in the files.  You could easily parse each file looking for DOWN and then resolve the IP back to the interface.

[ilko]

That directory is empty, same as pingmsstatus. No such files in /var/db.

[ilko]

Try pfctl -F all -i {$interface_that_goes_down}
Is better and should avoid running it twice.

Using
#!/bin/sh
sleep 5
/sbin/pfctl -F all

causes no new states created- Diagnostics: Show States- "No states were found."

back to

#!/bin/sh
sleep 60
/sbin/pfctl -F state
sleep 40
/sbin/pfctl -F state

This also makes when WAN or OPT1 are back online, all connections to use their preferred gateway again, which is good.
If we reset states on the failed gateway only, the above will not happen.
Need more time to study the negative effect of reseting states.

[ilko]

Since I've added this for 3 weeks it's working fine, however OPT1 has failed just a few times during office hours. No complains about loss of internet or failed PAP2T device for now. I will stick with this workaround until better solution comes up.

In short:

Change /conf/config.xml

Code:

<system>
...
....
<afterfilterchangeshellcmd>/usr/local/bin/reset_states.sh</afterfilterchangeshellcmd>

Create /usr/local/bin/reset_states.sh

Code:

#!/bin/sh
sleep 60
/sbin/pfctl -F state
sleep 40
/sbin/pfctl -F state

chmod 755 /usr/local/bin/reset_states.sh