New answers tagged filter
Your failregex is missing the special string <HOST> which you must insert in the place where the IP address will appear in the log entry. This is required so that fail2ban will know what IP address it should act on.
It sounds very much like you want to use what was some-time-ago known as 'port knocking' (thankfully it seems to have been a short-lived fashion). I believe there is google-able software for that, now that you know what you need to do. ... I would suggest though that it would be better to use something like a VPN or a client-side SSL certificate (preferably ...
Just configure mysql to use port 41020 for networking while usual 3306 is still blocked.
SSDP is implemented as a protocol that runs on top of HTTP-over-UDP, so the filter "http" will match SSDP packets. The filter "http and not udp" should eliminate SSDP packets; it will also, obviously, eliminate other HTTP-over-UDP packets, but I'm not sure there will ever be any HTTP-over-UDP packets that aren't SSDP packets.
So, I finally took a few minutes to edit the switch's configuration file to remove the unwanted filters, then re-upload it to the switch. Installed tftpd on one of the Linux servers (the last machine I had a handy non-critical tftp server running on was decommissioned a while back) Pushed the startup-config from the switch to a "switch0-config" file on the ...
I just used the functionality in the tool, by right clicking one of the packets that was problematic, then selected the sub-menu "Apply as Filter" > then selected ".. and not Selected" (under the "Not Selected" grouping). It then changed the expression to look like this. (http) && !(ip.dst == 188.8.131.52) So with using the Expression popup, it ...
Top 50 recent answers are included