This update of shorewall-monitor for Xymon fixes an undetected state-error.

The shorewall status command returns 2 states. In the following example everything is fine — is stopped and State:Cleared are in sync:

# shorewall status
Shorewall-4.5.5.3 Status at my-host - Sun Nov 12 13:30:03 CET 2017

Shorewall is stopped
State:Cleared (Sun Nov 12 13:29:54 CET 2017)

The following output might be returned after a reboot:

# shorewall status
Shorewall-4.5.5.3 Status at my-host - Sun Nov 12 13:30:15 CET 2017

Shorewall is stopped
State:Started (Sun Nov 12 13:29:38 CET 2017) from /etc/shorewall/

Note that is stopped and State:Started are not consistent. The latter is fetched from a state-file, that is not removed/reliably updated.

This behaviour was discoverd in Debian Wheezy with the shorewall-lite packages from the official Debian repository.

Prior to v0.7 shorewall-monitor exclusively checked the State:xxx-line. Starting with v0.7 the status goes red in case the two states are not in sync.

For more details see the project-page: shorewall-monitor for Xymon.