This bit in whatsnew.txt
[snip]
+ New event type has been added to MIS2 event manager: "IP Blocked". This
event can be executed every time an IP has been blocked by any MIS2
server's auto IP ban configuration.
The purpose of this is to allow you to run a command to create a block rule
at the firewall level so that the IP cannot even reach MIS in the future.
In
Linux "iptables" can be used, and in Windows "netsh" can be used to do
this.
The @IP@ code in the shell command will be replaced with the IP of the banned
account. Mystic will still continue to add the IP to its own blacklist.txt
as well.
The default events in a fresh install now include example events for this.
To create them in an existing environment, create a new event and set the
type of "IP Blocked" and then the Shell command to:
Linux :
Windows :
[snip]
I think it's an oversight at the moment but I would add the syntax for both lines that ship with the default install here:
Linux : iptables -A INPUT -s @IP@ -j DROP
Windows : netsh advfirewall firewall add rule name="IP Block" dir=in interface=any action=block remoteip=@IP@
..and in this bit
[snip]
Managing IP blocking rules:
Show contents of block rules in Firewall:
Linux : iptables -L INPUT -v -n | less
Windows : netsh advfirewall firewall show rule name="IP Block"
Remove a blocked IP rule from Firewall:
Linux :
Windows :
[snip]
I am not an expert at this but can you (for completeness) also add the syntax to use to remove a blocked IP from the Firewall? For me I like to know how to undo something automated if I need to, I won't be the only one I think :)
Oh and in update.txt - don't forget to add the removal of mbbsutil.exe to the list of actions to take when moving to A37. I noticed that was not there as yet.
Best, Paul.
--- Mystic BBS v1.12 A37 2017/12/21 (Windows/32)
* Origin: Agency BBS |
telnet://agency.bbs.geek.nz (21:1/101)