X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=5320002a69d6c1b2a3bcaad8a9b2dbb3fc367e81;hb=cbbf83baa54e859c382de79954607923cbb1b653;hp=7f5f3dbb825691e00d3ef011b6e3ec492b64828b;hpb=606b9690c7bb9e293cb4a03507f0280eea05d9ce;p=spider.git

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index 7f5f3dbb..5320002a 100644
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -995,6 +995,21 @@ running in order for the changes to take effect.
 Reload the /spider/data/bands.pl file if you have changed it manually whilst
 the cluster is running. 
 
+=== 6^LOAD/BADIP^Reload the bad IP address table
+Reload the badip address file(s) if you have changed any of them  manually
+whilst the cluster is running.
+
+You can edit the badip.* files manually in local_data or (for instance)
+obtain some bad IP addresses from the web to replace badip.base for TOR
+IP addresses (this filename may change).
+
+There is (currently) no UNSET/BADIP command so you will need to edit
+the badip.local file to remove IP addresses.
+
+After modification, you can reload the database with:
+
+  LOAD/BADIP
+
 === 9^LOAD/BADMSG^Reload the bad msg table
 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
 the cluster is running. This table contains a number of perl regular 
@@ -1598,6 +1613,13 @@ To allow a word again, use the following command ...
 
   unset/baddx VIDEO
 
+=== 6^SET/BADIP <ip address>..^Stop logins and spots with this IP address
+This command will prevent logins to this node from this IP address.
+It will also drop spots (PC61) from this address thus preventing them
+from being propagated.
+
+  set/badip 217.61.58.23
+
 === 6^SET/BADNODE <call>..^Stop spots from this node being propagated
 === 6^UNSET/BADNODE <call>..^Allow spots from this node again
 Setting a callsign as a 'badnode' will prevent spots from that node 
@@ -1660,14 +1682,18 @@ like this:
 
 but it will also stop things like this:
 
-  anihilate annni11ihhh ii lllattt eee ddd
+  anihilate annni11ihhh ii lllattt eee
 
 A few common 'leet' substitutions are automatically matched:
 
-  b0ll0cks bo0lll0ccckks fr1iig
+  b0ll0cks bo0lll0ccckks fr1iigging
 
 and so on
 
+It will not stop some things like:
+
+  The base word FRIG will stop 'friiigging' but not 'friiig ging'
+
 === 6^UNSET/BADWORD <word>..^Propagate things like this word again
 This is the opposite of set/badword <word>
 
@@ -2173,10 +2199,19 @@ for more information.
 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
 for more information.
 
-=== 1^SHOW/BADWORD^Show all the bad words in the system
+=== 6^SHOW/BADWORD^Show all the bad words in the system
+=== 6^SHOW/BADWORD full^Show all badwords with their Regex
+=== 6^SHOW/BADWORD <word> ...^Show all badwords with their Regex
 Display all the bad words in the system, see SET/BADWORD
 for more information.
 
+The first form shows all the base words that are stored in a simple list.
+
+The second form list all words with their associated perl regex.
+
+The third form shows just the regexes for the words asked for. If no
+answer for a word is given then it is not defined.
+
 === 0^SHOW/BANDS [band|region names]^Show the list of bands and regions
 Display the bands and regions (collections of bands) known to
 the system. If you supply band or region names to SHOW/BANDS,