I hereby claim:
- I am mitchya1 on github.
- I am mitchya1 (https://keybase.io/mitchya1) on keybase.
- I have a public key whose fingerprint is 8266 53C6 86AD 723B 9B3C 4240 2C51 8DCB EA0F 759E
To claim this, I am signing this object:
#!/usr/bin/env bash | |
# I've spent too much time banging my head against the wall trying to do this to not document it | |
cd /etc/td-agent/plugin/ && sudo wget https://raw.githubusercontent.com/emsearcy/fluent-plugin-gelf/master/lib/fluent/plugin/out_gelf.rb | |
sudo /usr/sbin/td-agent-gem install gelf | |
echo "Installed td-agent GELF plugin" | |
exit 0 |
Rate limiting specific traffic/services on WatchGuard | |
Firewall > Traffic Management > Add Policy | |
Name Policy | |
Set 'Type' to 'Per Policy' | |
Set bandwidth limitations |
Monitoring a WatchGuard with Zabbix via SNMP isn't as well documented as you'd hope, but it's also not difficult. | |
Step 1) Install this template into Zabbix: https://share.zabbix.com/network_devices/watchguard/firebox-watchguard-m400 | |
Step 2) In your WatchGuard, go to System > SNMP. Select SNMP v1/v2c. Create a community string. | |
Step 3) In your WatchGuard, go to Firewall > Firewall Policies. Create a new policy allowing SNMP from your Zabbix server. | |
Step 4) Create the host in Zabbix. Remove the Zabbix agent entry. Add an SNMP entry. Leave port 161. Assign the WatchGuard to a group. | |
Add the "Halley Firewall Watchguard M400" template (unless you renamed it). Go to "Macros". Add "{$SNMP_COMMUNITY}" and |
protocol: | |
(tcp|udp) | |
srcIP: | |
(?:tcp|udp)\s(\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}) | |
dstIP: | |
(?:\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}\s(\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3})) | |
insideInterface: |
#!/bin/bash | |
TARGETS=( | |
'example.com' | |
'example.net' | |
'example.org' | |
) | |
SLACK_URL='Your incoming webhook'. # 'https://hooks.slack.com/services/SOMETHING/SOMETHING ELSE' | |
emoji=":terminator:" | |
uname="CERT CHECKER" | |
channel="#alerts" |
I hereby claim:
To claim this, I am signing this object: