X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=909c3b7d795612b57bc4eca7bff9bdac0acfcaaf;hb=refs%2Fheads%2Fstaging;hp=ee148a08155c5ed2231dce582afbea1297911393;hpb=6311e8b178d0aeee984865fbd0446885c85b2f53;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index ee148a08..909c3b7d 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 ..^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 ..^Stop spots from this node being propagated === 6^UNSET/BADNODE ..^Allow spots from this node again Setting a callsign as a 'badnode' will prevent spots from that node @@ -2775,6 +2797,18 @@ So for example:- SH/SAT AO-10 SH/SAT FENGYUN1 12 2 +=== 1^SHOW/SPOTSTATS^Show the current Spot statistics +View the current unique spot sentences seen since the last restart. + +It shows the number of PC11 and PC61 sentences and the percentage +of PC11s received of the total of both. It also shows the number +of PC11s that have been promoted to PC61 before being passed on +plus a total percentage of incoming PC11 that have been promoted. + +A PC11 can be promoted to PC61 by a stored IP address in the routing +table or it can be promoted by being delayed to a short for any +passing PC61 from another node. + === 6^SHOW/STARTUP ^View a user startup script === 0^SHOW/STARTUP^View your own startup script View the contents of a startup script created with SET/STARTUP.