Skip to content

Conversation

@bonki
Copy link
Contributor

@bonki bonki commented Apr 25, 2017

…of checked data (currently only does IPSec tunnel names). This resolves #21.

…of checked data (currently only does IPSec tunnel names). This resolves riskersen#21.
@bonki
Copy link
Contributor Author

bonki commented Apr 25, 2017

Also did some refactoring alongside (that part is a bit more idiomatic now) so we don't have to run get_snmp_value for each and every tunnel.

@bonki
Copy link
Contributor Author

bonki commented Apr 25, 2017

The whitelist comes first, the blacklist filters on the result set which has been included by the whitelist.

E.g. --whitelist "^vpn_customer_" --blacklist "temp" includes all tunnels matching /^vpn_customer_/ except tunnels which also match /temp/.

Copy link
Owner

@riskersen riskersen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the usage of perl magic :-)

@riskersen riskersen merged commit 9c3f437 into riskersen:master May 31, 2017
@riskersen
Copy link
Owner

Many thanks for the contribution.

Could you please also add your changelog into the header of the file? I missed that part..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

check_fortigate.pl: add option to ex/include VPNs

2 participants