X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=c4566a20138daf035145ae2c50f79f4c01eb165d;hb=8b89a9f5ce05bee89e83d68a75da9e73f560ee67;hp=a0ab7558bfe0c648b190768e12b954bc2e7692d2;hpb=d2c1a8cb2a31725e3b9084aee3ec43e585e3273f;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index a0ab7558..c4566a20 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,6 @@ - The DXSpider Administration Manual v1.48 - Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 1.48 August 2001 revision 1.1 + The DXSpider Administration Manual v1.50 + Ian Maude, G0VGS, (g0vgs@gb7mbc.net) + July 2002 revision 0.1 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -109,161 +109,195 @@ 6. Information, files and useful programs 6.1 MOTD - 6.2 Downtime message - 6.3 Other text messages - 6.4 The Aliases file - 6.5 Console.pl - 6.6 Updating kepler data - 6.7 The QRZ callbook - - 7. CVS - - 8. The DXSpider command set - - 8.1 accept/announce (0) - 8.2 accept/announce (extended for sysops) (8) - 8.3 accept/route (8) - 8.4 accept/spots (0) - 8.5 accept/spots (extended for sysops) (8) - 8.6 accept/wcy (0) - 8.7 accept/wcy (extended for sysops) (8) - 8.8 accept/wwv (0) - 8.9 accept/wwv (extended for sysops) (8) - 8.10 announce (0) - 8.11 announce full (0) - 8.12 announce sysop (5) - 8.13 apropos (0) - 8.14 bye (0) - 8.15 catchup (5) - 8.16 clear/spots (0) - 8.17 connect (5) - 8.18 dbavail (0) - 8.19 dbcreate (9) - 8.20 dbimport (9) - 8.21 dbremove (9) - 8.22 dbshow (0) - 8.23 debug (9) - 8.24 directory (0) - 8.25 directory (extended for sysops) (5) - 8.26 disconnect (8) - 8.27 dx (0) - 8.28 export (9) - 8.29 export_users (9) - 8.30 forward/latlong (8) - 8.31 forward/opername (1) - 8.32 help (0) - 8.33 init (5) - 8.34 kill (0) - 8.35 kill (5) - 8.36 kill full (5) - 8.37 links (0) - 8.38 load/aliases (9) - 8.39 load/badmsg (9) - 8.40 load/bands (9) - 8.41 load/cmd_cache (9) - 8.42 load/forward (9) - 8.43 load/messages (9) - 8.44 load/prefixes (9) - 8.45 merge (5) - 8.46 msg (9) - 8.47 pc (8) - 8.48 ping (1) - 8.49 rcmd (1) - 8.50 read (0) - 8.51 read (extended for sysops) (5) - 8.52 reject/announce - 8.53 reject/announce (extended for sysops) (8) - 8.54 reject/route (8) - 8.55 reject/spots (0) - 8.56 reject/spots (extended for sysops) (8) - 8.57 reject/wcy (0) - 8.58 reject/wcy (extended for sysops) (8) - 8.59 reject/wwv (0) - 8.60 reject/wwv (extended for sysops) (8) - 8.61 reply (0) - 8.62 send (0) - 8.63 set/address (0) - 8.64 set/announce (0) - 8.65 set/arcluster (5) - 8.66 set/baddx (8) - 8.67 set/badnode (6) - 8.68 set/badspotter (8) - 8.69 set/beep (0) - 8.70 set/bbs (5) - 8.71 set/clx (5) - 8.72 set/debug (9) - 8.73 set/dx (0) - 8.74 set/dxgrid (0) - 8.75 set/dxnet (5) - 8.76 set/echo (0) - 8.77 set/here (0) - 8.78 set/homenode (0) - 8.79 set/hops (8) - 8.80 set/isolate (9) - 8.81 set/language (0) - 8.82 set/location (0) - 8.83 set/sys_location (9) - 8.84 set/logininfo (0) - 8.85 set/lockout (9) - 8.86 set/name (0) - 8.87 set/node (9) - 8.88 set/obscount (9) - 8.89 set/page (0) - 8.90 set/password (9) - 8.91 set/pinginterval (9) - 8.92 set/privilege (9) - 8.93 set/spider (5) - 8.94 set/sys_qra (9) - 8.95 set/qra (0) - 8.96 set/qth (0) - 8.97 set/talk (0) - 8.98 set/wcy (0) - 8.99 set/wwv (0) - 8.100 set/wx (0) - 8.101 show/baddx (1) - 8.102 show/badnode (6) - 8.103 show/badspotter (1) - 8.104 show/configuration (0) - 8.105 show/configuration/node (0) - 8.106 show/connect (1) - 8.107 show/date (0) - 8.108 show/debug (9) - 8.109 show/dx (0) - 8.110 show/dxcc (0) - 8.111 show/files (0) - 8.112 show/filter (0) - 8.113 show/filter (extended for sysops) (5) - 8.114 show/hops (8) - 8.115 show/isolate (1) - 8.116 show/lockout (9) - 8.117 show/log (8) - 8.118 show/moon (0) - 8.119 show/muf (0) - 8.120 show/node (1) - 8.121 show/prefix (0) - 8.122 show/program (5) - 8.123 show/qra (0) - 8.124 show/qrz (0) - 8.125 show/route (0) - 8.126 show/satellite (0) - 8.127 show/sun (0) - 8.128 show/time (0) - 8.129 show/wcy (0) - 8.130 show/wwv (0) - 8.131 shutdown (5) - 8.132 spoof (9) - 8.133 stat/db (5) - 8.134 stat/channel (5) - 8.135 stat/msg (5) - 8.136 stat/route_node (5) - 8.137 stat/route_user (5) - 8.138 stat/user (5) - 8.139 sysop (0) - 8.140 talk (0) - 8.141 type (0) - 8.142 who (0) - 8.143 wx (0) - 8.144 wx (enhanced for sysops) (5) + 6.2 MOTD_NOR + 6.3 Downtime message + 6.4 Other text messages + 6.5 The Aliases file + 6.6 Console.pl + 6.7 Updating kepler data + 6.8 The QRZ callbook + 6.9 Connecting logging programs + + 7. Java Web applet + + 8. Security + + 8.1 Registration + 8.2 Passwords + + 9. CVS + + 10. The DXSpider command set + + 10.1 accept/announce (0) + 10.2 accept/announce (extended for sysops) (8) + 10.3 accept/route (8) + 10.4 accept/spots (0) + 10.5 accept/spots (extended for sysops) (8) + 10.6 accept/wcy (0) + 10.7 accept/wcy (extended for sysops) (8) + 10.8 accept/wwv (0) + 10.9 accept/wwv (extended for sysops) (8) + 10.10 announce (0) + 10.11 announce full (0) + 10.12 announce sysop (5) + 10.13 apropos (0) + 10.14 bye (0) + 10.15 catchup (5) + 10.16 clear/announce (8) + 10.17 clear/route (8) + 10.18 clear/spots (0) + 10.19 clear/spots (extended for sysops) (8) + 10.20 clear/wcy (0) + 10.21 clear/wcy (extended for sysops) (8) + 10.22 clear/wwv (0) + 10.23 clear/wwv (extended for sysops) (8) + 10.24 connect (5) + 10.25 dbavail (0) + 10.26 dbcreate (9) + 10.27 dbimport (9) + 10.28 dbremove (9) + 10.29 dbshow (0) + 10.30 debug (9) + 10.31 delete/user (9) + 10.32 demonstrate (9) + 10.33 directory (0) + 10.34 directory (extended for sysops) (5) + 10.35 disconnect (8) + 10.36 dx (0) + 10.37 export (9) + 10.38 export_users (9) + 10.39 filtering (0) + 10.40 forward/latlong (8) + 10.41 forward/opername (1) + 10.42 help (0) + 10.43 init (5) + 10.44 kill (0) + 10.45 kill (5) + 10.46 kill full (5) + 10.47 kill/expunge (6) + 10.48 links (0) + 10.49 load/aliases (9) + 10.50 load/badmsg (9) + 10.51 load/badwords (9) + 10.52 load/bands (9) + 10.53 load/cmd_cache (9) + 10.54 load/forward (9) + 10.55 load/messages (9) + 10.56 load/prefixes (9) + 10.57 merge (5) + 10.58 msg (9) + 10.59 pc (8) + 10.60 ping (1) + 10.61 rcmd (1) + 10.62 read (0) + 10.63 read (extended for sysops) (5) + 10.64 reject/announce + 10.65 reject/announce (extended for sysops) (8) + 10.66 reject/route (8) + 10.67 reject/spots (0) + 10.68 reject/spots (extended for sysops) (8) + 10.69 reject/wcy (0) + 10.70 reject/wcy (extended for sysops) (8) + 10.71 reject/wwv (0) + 10.72 reject/wwv (extended for sysops) (8) + 10.73 reply (0) + 10.74 send (0) + 10.75 set/address (0) + 10.76 set/announce (0) + 10.77 set/arcluster (5) + 10.78 set/baddx (8) + 10.79 set/badnode (6) + 10.80 set/badspotter (8) + 10.81 set/badword (8) + 10.82 set/beep (0) + 10.83 set/bbs (5) + 10.84 set/clx (5) + 10.85 set/debug (9) + 10.86 set/dx (0) + 10.87 set/dxgrid (0) + 10.88 set/dxnet (5) + 10.89 set/echo (0) + 10.90 set/email (0) + 10.91 set/here (0) + 10.92 set/homenode (0) + 10.93 set/hops (8) + 10.94 set/isolate (9) + 10.95 set/language (0) + 10.96 set/location (0) + 10.97 set/sys_location (9) + 10.98 set/logininfo (0) + 10.99 set/lockout (9) + 10.100 set/name (0) + 10.101 set/node (9) + 10.102 set/obscount (9) + 10.103 set/page (0) + 10.104 set/password (0) + 10.105 set/password (9) + 10.106 set/pinginterval (9) + 10.107 set/privilege (9) + 10.108 set/spider (5) + 10.109 set/sys_qra (9) + 10.110 set/qra (0) + 10.111 set/qth (0) + 10.112 set/register (9) + 10.113 set/talk (0) + 10.114 set/wcy (0) + 10.115 set/wwv (0) + 10.116 set/wx (0) + 10.117 show/baddx (1) + 10.118 show/badnode (6) + 10.119 show/badspotter (1) + 10.120 show/badword (1) + 10.121 show/configuration (0) + 10.122 show/configuration/node (0) + 10.123 show/connect (1) + 10.124 show/date (0) + 10.125 show/debug (9) + 10.126 show/dx (0) + 10.127 show/dxcc (0) + 10.128 sh/dxstats (0) + 10.129 show/files (0) + 10.130 show/filter (0) + 10.131 show/filter (extended for sysops) (5) + 10.132 show/hfstats (0) + 10.133 show/hftable (0) + 10.134 show/hops (8) + 10.135 show/isolate (1) + 10.136 show/lockout (9) + 10.137 show/log (8) + 10.138 show/moon (0) + 10.139 show/muf (0) + 10.140 show/newconfiguration (0) + 10.141 show/newconfiguration/node (0) + 10.142 show/node (1) + 10.143 show/prefix (0) + 10.144 show/program (5) + 10.145 show/qra (0) + 10.146 show/qrz (0) + 10.147 show/registered (9) + 10.148 show/route (0) + 10.149 show/satellite (0) + 10.150 show/sun (0) + 10.151 show/time (0) + 10.152 show/vhfstats (0) + 10.153 show/vhftable (0) + 10.154 show/wcy (0) + 10.155 show/wwv (0) + 10.156 shutdown (5) + 10.157 spoof (9) + 10.158 stat/db (5) + 10.159 stat/channel (5) + 10.160 stat/msg (5) + 10.161 stat/route_node (5) + 10.162 stat/route_user (5) + 10.163 stat/user (5) + 10.164 sysop (0) + 10.165 talk (0) + 10.166 type (0) + 10.167 who (0) + 10.168 wx (0) + 10.169 wx (enhanced for sysops) (5) ______________________________________________________________________ @@ -287,21 +321,22 @@ In fact DXSpider has had a simple system for some time which is called - isolation. This is similar to what, in other systems such as clx, is + isolation. This is similar to what in other systems such as clx, is called passive mode. A more detailed explanation of isolation is given further below. This system is still available and, for simple networks, is probably all that you need. - The new functionality introduced in version 1.48 is filtering the node - and user protocol frames on a "per interface" basis. We call this + + The new functionality introduced in version 1.48 allows filtering the + node and user protocol frames on a "per interface" basis. We call this route filtering. This is used instead of isolation. What this really means is that you can control more or less completely - which PC protocol frames, to do with user and node management, pass to - each of your partner nodes. You can also limit what comes into your - node from your partners. You can even control the settings that your + which user and node management PC protocol frames pass to each of your + partner nodes. You can also limit what comes into your node from your + partners. It is even possible to control the settings that your partner node has for the routing information that it sends to you (using the rcmd command). @@ -315,7 +350,7 @@ explained further on. - The first thing that you must do is determine whether you need to do + The first thing that you must do is determine whether you need to use route filtering at all. If you are a "normal" node with two or three partners and you arranged in an "official" non-looping tree type network, then you do not need to do route filtering and you will feel @@ -323,6 +358,14 @@ isolation then you also probably don't need to use route filtering. + To put it simply, you should not mix Isolation and Route Filtering. + It will work, of sorts, but you will not get the expected results. If + you are using Isolation sucessfully at the moment, do not get involved + in Route Filtering unless you have a good supply of aspirin! Once you + have started down the road of Route Filtering, do not use Isolation + either. Use one or the other, not both. + + You will only require this functionality if you are "well-connected". What that means is that you are connected to several different parts of (say) the EU cluster and, at the same time, also connected to two @@ -351,9 +394,6 @@ "national" network. Here in the UK that means nodes from the UK and Eire, in EU it is more complex as the networks there grew up in a more intertwined way. - - - The generic commands are:- @@ -384,7 +424,8 @@ Please be careful if you alter this setting, it will affect ALL your - links! + links! Remember, this is a default filter for node connections, not a + per link default. For the default routing filter then you have two real choices: either @@ -393,9 +434,8 @@ - - acc/route node_default call_dxcc 61,38 - acc/route node_default call gb7djk + acc/route node_default call_dxcc 61,38 + acc/route node_default call gb7djk @@ -420,8 +460,6 @@ rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38 - - What this does is accept node and user information for our national network from nodes that are in our national network, but rejects such information from anyone else. Although it doesn't explicitly say so, @@ -457,14 +495,11 @@ + reject/route + or - - reject/route - - or - - accept/route + accept/route @@ -474,8 +509,8 @@ - rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) - rej/route all (equiv to [very] restricted mode) + rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes) + rej/route all (equiv to [very] restricted mode) acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE) @@ -491,8 +526,6 @@ acc/route gb7baa input all - - or restricting it quite a lot, in fact making it very nearly like an isolated node, like this:- @@ -509,7 +542,7 @@ PC16s for my local users). - It is possible to do much more complex rules, there are up to 10 + It is possible to write much more complex rules, there are up to 10 accept/reject pairs per callsign per filter. For more information see the next section. @@ -525,7 +558,6 @@ will be renamed as you update. - There are 3 basic commands involved in setting and manipulating filters. These are accept, reject and clear. First we will look generally at filtering. There are a number of things you can filter in @@ -657,7 +689,6 @@ on VHF which don't either originate or spot someone in Europe. - This is an example where you would use a line number (1 and 2 in this case), if you leave the digit out, the system assumes '1'. Digits '0'-'9' are available. This make it easier to see just what filters @@ -693,9 +724,6 @@ reject/spots 1 on hf/ssb - - - would redefine our earlier example, or @@ -721,9 +749,6 @@ the various helpfiles for accept, reject and filter. - - - 1.8. Default filters Sometimes all that is needed is a general rule for node connects. @@ -765,9 +790,6 @@ acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16) - - - Note that the first filter has not been specified with a number. This will automatically be assumed to be number 1. In this case, we have said reject all HF spots in the CW section of the bands but accept all @@ -796,55 +818,93 @@ - # - # hop table construction - # - package DXProt; - # default hopcount to use - $def_hopcount = 5; - # some variable hop counts based on message type - %hopcount = - ( - 11 => 10, - 16 => 10, - 17 => 10, - 19 => 10, - 21 => 10, - ); - # the per node hop control thingy - %nodehops = - GB7ADX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - GB7UDX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - GB7BAA => { - 11 => 5, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - }; + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + # + # hop table construction + # + + package DXProt; + + # default hopcount to use + $def_hopcount = 5; + + # some variable hop counts based on message type + %hopcount = + ( + 11 => 10, + 16 => 10, + 17 => 10, + 19 => 10, + 21 => 10, + ); + + + # the per node hop control thingy + + + %nodehops = + + GB7ADX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + + GB7UDX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + GB7BAA => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + }; @@ -856,6 +916,28 @@ how the file works. + SHould any of the nodecalls include an ssid, it is important to wrap + the whole call in single quotes, like this ... + + + + + 'DB0FHF-15' => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + + + + + If you do not do this, you will get errors and the file will not work + as expected. + + You can alter this file at any time, including whilst the cluster is running. If you alter the file during runtime, the command load/hops will bring your changes into effect. @@ -881,7 +963,7 @@ The set/hops command overrides any hops that you have set otherwise. - You can set what hops have been set using the show/hops command. + You can show what hops have been set using the show/hops command. 1.12. Isolating networks @@ -909,7 +991,7 @@ any information back to the isolated node. There are times when you would like to forward only spots across a link (maybe during a contest for example). To do this, isolate the node in the normal way and use - an acc/spot >call< allilter in the to override the isolate. + an acc/spot >call< all filter to override the isolate. 2. Other filters @@ -922,34 +1004,35 @@ - # the list of regexes for messages that we won't store having - # received them (bear in mind that we must receive them fully before - # we can bin them) + # the list of regexes for messages that we won't store having + # received them (bear in mind that we must receive them fully before + # we can bin them) - # The format of each line is as follows - # type source pattern - # P/B/F T/F/O/S regex + # The format of each line is as follows - # type: P - private, B - bulletin (msg), F - file (ak1a bull) - # source: T - to field, F - from field, O - origin, S - subject - # pattern: a perl regex on the field requested + # type source pattern + # P/B/F T/F/O/S regex - # Currently only type B and P msgs are affected by this code. - # - # The list is read from the top down, the first pattern that matches - # causes the action to be taken. + # type: P - private, B - bulletin (msg), F - file (ak1a bull) + # source: T - to field, F - from field, O - origin, S - subject + # pattern: a perl regex on the field requested - # The pattern can be undef or 0 in which case it will always be selected - # for the action specified + # Currently only type B and P msgs are affected by this code. + # + # The list is read from the top down, the first pattern that matches + # causes the action to be taken. + # The pattern can be undef or 0 in which case it will always be selected + # for the action specified - package DXMsg; - @badmsg = ( - ); + package DXMsg; + + @badmsg = ( + ); @@ -983,9 +1066,9 @@ any further by regarding it as "bad" in some way. - A DX Spot has a number of fields which can checked to see whether they - contain "bad" values, they are: the DX callsign itself, the Spotter - and the Originating Node. + A DX Spot has a number of fields which can be checked to see whether + they contain "bad" values, they are: the DX callsign itself, the + Spotter and the Originating Node. There are a set of commands which allow the sysop to control whether a @@ -1034,6 +1117,9 @@ of show/baddx, show/badspotter and show/badnode. + + + 3. Mail DXSpider deals seamlessly with standard AK1A type mail. It supports @@ -1054,6 +1140,8 @@ default method of sending mail and so a simple s for send will do. A full list of the send commands and options is in the command set section, so I will not duplicate them here. + + 3.2. Bulletin mail Bulletin mail is sent by using the sb command. This is one of the @@ -1081,41 +1169,58 @@ - # - # this is an example message forwarding file for the system - # - # The format of each line is as follows - # - # type to/from/at pattern action destinations - # P/B/F T/F/A regex I/F [ call [, call ...] ] - # - # type: P - private, B - bulletin (msg), F - file (ak1a bull) - # to/from/at: T - to field, F - from field, A - home bbs, O - origin - # pattern: a perl regex on the field requested - # action: I - ignore, F - forward - # destinations: a reference to an array containing node callsigns - # - # if it is non-private and isn't in here then it won't get forwarded - # - # Currently only type B msgs are affected by this code. - # - # The list is read from the top down, the first pattern that matches - # causes the action to be taken. - # - # The pattern can be undef or 0 in which case it will always be selected - # for the action specified - # - # If the BBS list is undef or 0 and the action is 'F' (and it matches the - # pattern) then it will always be forwarded to every node that doesn't have - # it (I strongly recommend you don't use this unless you REALLY mean it, if - # you allow a new link with this on EVERY bull will be forwarded immediately - # on first connection) - # - package DXMsg; - @forward = ( - ); + + + + + + + + + + + + + + + + # + # this is an example message forwarding file for the system + # + # The format of each line is as follows + # + # type to/from/at pattern action destinations + # P/B/F T/F/A regex I/F [ call [, call ...] ] + # + # type: P - private, B - bulletin (msg), F - file (ak1a bull) + # to/from/at: T - to field, F - from field, A - home bbs, O - origin + # pattern: a perl regex on the field requested + # action: I - ignore, F - forward + # destinations: a reference to an array containing node callsigns + # + # if it is non-private and isn't in here then it won't get forwarded + # + # Currently only type B msgs are affected by this code. + # + # The list is read from the top down, the first pattern that matches + # causes the action to be taken. + # + # The pattern can be undef or 0 in which case it will always be selected + # for the action specified + # + # If the BBS list is undef or 0 and the action is 'F' (and it matches the + # pattern) then it will always be forwarded to every node that doesn't have + # it (I strongly recommend you don't use this unless you REALLY mean it, if + # you allow a new link with this on EVERY bull will be forwarded immediately + # on first connection) + # + + package DXMsg; + + @forward = ( + ); @@ -1128,6 +1233,9 @@ To force the cluster to reread the file use load/forward + NB: If a user tries to send mail to a bulletin address that does not + exist in this file, they will get an error. + 3.4. The msg command @@ -1139,20 +1247,25 @@ - MSG TO - change TO callsign to - MSG FRom - change FROM callsign to - MSG PRrivate - set private flag - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waiting time for this message - MSG NOREad - mark message as unread - MSG REad - mark message as read - MSG QUeue - queue any outstanding bulletins - MSG QUeue 1 - queue any outstanding private messages + + + + + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waiting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages @@ -1186,6 +1299,10 @@ Times read: 0 G0VGS de GB7MBC 28-Jan-2001 1308Z > + + + + 3.6. Filtering mail This is described in the section on Other filters so I will not @@ -1201,7 +1318,6 @@ SYSOP.pl that caters for the UK sysops. - qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH GB7DXK GB7DXI GB7DXS) @@ -1232,46 +1348,84 @@ DXSpider's operation with scripts of various kinds. - In the first instance, in 1.48, the sysop can create, with their - favorite text editor, files in the directory /spider/scripts which - contain any legal command for a callsign or class of connection which - will be executed at logon. + The directory /spider/scripts is where it all happens and is used for + several things. Firstly it contains a file called startup that can be + used to call in any changes to the cluster from the default settings + on startup. This script is executed immediately after all + initialisation of the node is done but before any connections are + possible. Examples of this include how many spots it is possible to + get with the sh/dx command, whether you want registration/passwords to + be permanently on etc. An example file is shown below and is included + in the distribution as startup.issue. - The filename are the callsign of the connection that you want the - script to operate on, eg: /spider/scripts/g1tlh. The filenames are - always in lower case on those architectures where this makes a - difference. + # + # startup script example + # + # set maximum no of spots allowed to 100 + # set/var $Spot::maxspots = 100 + # + # Set registration on + # set/var $main::reqreg = 1 + # + # Set passwords on + # set/var $main::passwdreq = 1 + # - In addition to the callsign specific scripts there are three others:- + As usual, any text behind a # is treated as a comment and not read. + To use this file, simply rename it from startup.issue to startup. In + our example above there are three options. The first option is the + amount of spots that a user can request with the sh/dx command. + Normally the default is to give 10 spots unless the user specifies + more. Without this line enabled, the maximum a user can request is + 100 spots. Depending on your link quality you may wish to enable more + or less by specifying the number. + The other 2 options are dealt with more fully in the security section. - startup - user_default - node_default + Secondly, it is used to store the login scripts for users and nodes. + Currently this can only be done by the sysop but it is envisaged that + eventually users will be able to set their own. An example is + included in the distibution but here is a further example. - The startup script is executed immediately after all initialisation of - the node is done, but before any connections are possible. + # + # G0FYD + # + blank + + sh/wwv 3 + blank + + sh/dx + blank + + t g0jhc You abt? + blank + - The user_default script is executed for every user that does NOT - already have a specific script. - The node_default script is executed for every node that doesn't have a - specific script. + The lines in between commands can simply insert a blank line or a + character such as a + sign to make the output easier to read. Simply + create this script with your favourite editor and save it with the + callsign of the user as the filename. Filenames should always be in + lower case. - There are a couple of examples in the /spider/scripts directory. + Commands can be inserted in the same way for nodes. A node may wish a + series of commands to be issued on login, such as a merge command for + example. + + + Thirdly, there are 2 default scripts for users and nodes who do not + have a specifically defined script. These are user_default and + node_default 5. Databases @@ -1296,8 +1450,6 @@ dbcreate - - To simply create a database locally, you just tell the command the name of the database. This does not create the actual database, it simply defines it to say that it exists. @@ -1318,6 +1470,7 @@ + This creates a remote entry. the first name field is the database name at the remote node, then the remote switch, then the actual node_call of the remote node, for example... @@ -1361,12 +1514,14 @@ - dbavail - DB Name Location Chain - qsl Local - buck GB7ADX - hftest GB7DXM - G0VGS de GB7MBC 3-Feb-2001 1925Z > + + + dbavail + DB Name Location Chain + qsl Local + buck GB7ADX + hftest GB7DXM + G0VGS de GB7MBC 3-Feb-2001 1925Z > @@ -1427,9 +1582,14 @@ /spider/data called motd and edit it to say whatever you want. It is purely a text file and will be sent automatically to anyone logging in to the cluster. + 6.2. MOTD_NOR + This message of the day file lives in the same directory as the + standard motd file but is only sent to non-registered users. Once + registered they will receive the same message as any other user. - 6.2. Downtime message + + 6.3. Downtime message If for any reason the cluster is down, maybe for upgrade or maintenance but the machine is still running, a message can be sent to @@ -1440,7 +1600,7 @@ actually running. - 6.3. Other text messages + 6.4. Other text messages You can set other text messages to be read by the user if they input the file name. This could be for news items or maybe information for @@ -1450,6 +1610,7 @@ like. These can be listed by the user with the command .... + show/files @@ -1487,8 +1648,6 @@ An example would look like this .... - - sh/files bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z @@ -1513,24 +1672,21 @@ - - - - show/files bulletin - opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z - opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z - opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z - opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z - opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z - opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z - opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z - opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z - opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z - opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z - opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z - opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z - opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z - Press Enter to continue, A to abort (16 lines) > + show/files bulletin + opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z + opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z + opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z + opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z + opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z + opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z + opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z + opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z + opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z + opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z + opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z + opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z + opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z + Press Enter to continue, A to abort (16 lines) > @@ -1557,174 +1713,91 @@ - The page length will of course depend on what you have it set to! - - - 6.4. The Aliases file - - You will find a file in /spider/cmd/ called Aliases. First, copy this - file to /spider/local_cmd/Aliases and edit this file. You will see - something like this ... - + The page length will of course depend on what you have it set to! + 6.5. The Aliases file + You will find a file in /spider/cmd/ called Aliases. This is the file + that controls what a user gets when issuing a command. It is also + possible to create your own aliases for databases and files you create + locally. + You should not alter the original file in /spider/cmd/ but create a + new file with the same name in /spider/local_cmd. This means that any + new Aliases files that is downloaded will not overwrite your self + created Aliases and also that you do not override any new Aliases with + your copy in /spider/local_cmd/. You must remember that any files you + store in /spider/local/ or /spider/local_cmd override the originals if + the same lines are used in both files. + The best way of dealing with all this then is to only put your own + locally created Aliases in the copy in /spider/local_cmd. The example + below is currently in use at GB7MBC. + # + # Local Aliases File + # + package CmdAlias; + %alias = ( + 'n' => [ + '^news$', 'type news', 'type', + ], + 's' => [ + '^sh\w*/buck$', 'show/qrz', 'show', + '^sh\w*/hftest$', 'dbshow hftest', 'dbshow', + '^sh\w*/qsl$', 'dbshow qsl', 'dbshow', + '^sh\w*/vhf$', 'dbshow vhf', 'dbshow', + '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow', + ], + ) - #!/usr/bin/perl - # provide some standard aliases for commands for terminally - # helpless ak1a user (helpless in the sense that they never - # read nor understand help files) - # This file is automagically reloaded if its modification time is - # later than the one stored in CmdAlias.pm - # PLEASE make this file consistant with reality! (the patterns MUST - # match the filenames!) + Each alphabetical section should be preceded by the initial letter and + the section should be wrapped in square brackets as you can see. The + syntax is straightforward. The first section on each line is the new + command that will be allowed once the alias is included. The second + section is the command it is replacing and the last section is the + actual command that is being used. - # Don't alter this file, copy it into the local_cmd tree and modify it. - # This file will be replaced everytime I issue a new release. - # You only need to put aliases in here for commands that don't work as - # you desire naturally, e.g sh/dx on its own just works as you expect - # so you need not add it as an alias. + The eagle-eyed amongst you will have noticed that in the first + section, the new alias command has a '^' at the start and a '$' at the + end. Basically these force a perfect match on the alias. The '^' + says match the beginning exactly and the with similar commands. - - package CmdAlias; - - %alias = ( - '?' => [ - '^\?', 'apropos', 'apropos', - ], - 'a' => [ - '^ann.*/full', 'announce full', 'announce', - '^ann.*/sysop', 'announce sysop', 'announce', - '^ann.*/(.*)$', 'announce $1', 'announce', - ], - 'b' => [ - ], - 'c' => [ - ], - 'd' => [ - '^del', 'kill', 'kill', - '^del\w*/fu', 'kill full', 'kill', - '^di\w*/a\w*', 'directory all', 'directory', - '^di\w*/b\w*', 'directory bulletins', 'directory', - '^di\w*/n\w*', 'directory new', 'directory', - '^di\w*/o\w*', 'directory own', 'directory', - '^di\w*/s\w*', 'directory subject', 'directory', - '^di\w*/t\w*', 'directory to', 'directory', - '^di\w*/f\w*', 'directory from', 'directory', - '^di\w*/(\d+)', 'directory $1', 'directory', - ], - 'e' => [ - ], - 'f' => [ - ], - 'g' => [ - ], - 'h' => [ - ], - 'i' => [ - ], - 'j' => [ - ], - 'k' => [ - ], - 'l' => [ - '^l$', 'directory', 'directory', - '^ll$', 'directory', 'directory', - '^ll/(\d+)', 'directory $1', 'directory', - ], - 'm' => [ - ], - 'n' => [ - '^news', 'type news', 'type', - ], - 'o' => [ - ], - 'p' => [ - ], - 'q' => [ - '^q', 'bye', 'bye', - ], - 'r' => [ - '^r$', 'read', 'read', - '^rcmd/(\S+)', 'rcmd $1', 'rcmd', - ], - 's' => [ - '^s/p$', 'send', 'send', - '^sb$', 'send noprivate', 'send', - '^set/home$', 'set/homenode', 'set/homenode', - '^set/nobe', 'unset/beep', 'unset/beep', - '^set/nohe', 'unset/here', 'unset/here', - '^set/noan', 'unset/announce', 'unset/announce', - '^set/nodx', 'unset/dx', 'unset/dx', - '^set/nota', 'unset/talk', 'unset/talk', - '^set/noww', 'unset/wwv', 'unset/wwv', - '^set/nowx', 'unset/wx', 'unset/wx', - '^sh$', 'show', 'show', - '^sh\w*/buck', 'dbshow buck', 'dbshow', - '^sh\w*/bu', 'show/files bulletins', 'show/files', - '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration', - '^sh\w*/c$', 'show/configuration', 'show/configuration', - '^sh\w*/com', 'dbavail', 'dbavail', - '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx', - '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx', - '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx', - '^sh\w*/email', 'dbshow email', 'dbshow', - '^sh\w*/hftest', 'dbshow hftest', 'dbshow', - '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow', - '^sh\w*/qsl', 'dbshow qsl', 'dbshow', - '^sh\w*/tnc', 'who', 'who', - '^sh\w*/up', 'show/cluster', 'show/cluster', - '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv', - '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv', - '^sp$', 'send', 'send', - - ], - 't' => [ - '^ta$', 'talk', 'talk', - '^t$', 'talk', 'talk', - ], - 'u' => [ - ], - 'v' => [ - ], - 'w' => [ - '^wx/full', 'wx full', 'wx', - '^wx/sysop', 'wx sysop', 'wx', - ], - 'x' => [ - ], - 'y' => [ - ], - 'z' => [ - ], - ) - + I have 3 different types of alias in this file. At the top is an + alias for 'news'. This is a file I have created in the + /spider/packclus/ directory where I can inform users of new + developments or points of interest. In it's initial form a user would + have to use the command type news. The alias allows them to simply + type news to get the info. Second is an alias for the show/qrz + command so that those users used to the original show/buck command in + AK1A will not get an error, and the rest of the lines are for locally + created databases so that a user can type show/hftest instead of + having to use the command dbshow hftest which is not as intuitive. + This file is just an example and you should edit it to your own + requirements. Once created, simply issue the command load/alias at + the cluster prompt as the sysop user and the aliases should be + available. - You can create aliases for commands at will. Beware though, these may - not always turn out as you think. Care is needed and you need to test - the results once you have set an alias. - 6.5. Console.pl + 6.6. Console.pl In later versions of Spider a simple console program is provided for the sysop. This has a type ahead buffer with line editing facilities @@ -1736,7 +1809,7 @@ edit the file with your favourite editor. - 6.6. Updating kepler data + 6.7. Updating kepler data Spider has a powerful and flexible show/satellite command. In order for this to be accurate, the kepler data has to be updated regularly. @@ -1752,9 +1825,11 @@ + would export message number 5467 as a file called keps.in in the /spider/perl directory. + Now login to a VT as sysop and cd /spider/perl. There is a command in the perl directory called convkeps.pl. All we need to do now is convert the file like so ... @@ -1766,21 +1841,21 @@ - Now go back to the cluster and issue the command ... + Now go back to the cluster and issue the command ... - load/keps + load/keps - That is it! the kepler data has been updated. + That is it! the kepler data has been updated. - 6.7. The QRZ callbook + 6.8. The QRZ callbook The command sh/qrz will only work once you have followed a few simple steps. First you need to get a user ID and password from qrz.com. @@ -1791,7 +1866,208 @@ proprieter of qrz.com for allowing this access. - 7. CVS + 6.9. Connecting logging programs + + There appear to be very few logging programs out there that support + telnet especially the popular ones like LogEQF, Turbolog etc. This + can make it difficult to connect to your own cluster! The way to do + it is to make the logging program think it has a TNC attached to a com + port on the logging PC and 'push' a linux login out to it. This is + achieved very simply by the use of agetty. + + + All that is required is to add a line in /etc/inittab to have the + client ready for a connection on the com port of your choice. + Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1 + for com2 etc. + + + + c4:2345:respawn:/sbin/agetty -L 9600 ttyS1 + + + + + + Add this after the standard runlevel lines in /etc/inittab. The above + line works on ttyS1 (com2). Now as root, issue the command telinit q + and it should be ready for connection. All that is required is a 3 + wire serial lead (tx, rx and signal ground). Tell you logging program + to use 8n1 at 9600 baud and you should see a Linux login prompt. + Login as normal and then telnet from there to the cluster. + + + 7. Java Web applet + + In the spider tree will be a directory spider-web. This is a neat + little java web applet that can be run from a website. The applet + must run on the same machine as the cluster. The included README file + is shown below. + + + I should comment here that the applet is precompiled, that is, ready + to go. It was compiled using JDK1.3.1. If your version is earlier + than this then it may not work. Should that be the case you need to + recompile or update your JDK. To recompile do the following ... + + + + cd /spider/spider-web + rm *.class + /usr/bin/javac spiderclient.java + + + + + + I have used /usr/bin/javac as an example, your path to javac may be + different. + + + Spider-WEB v0.6b + + Completely based on a clx web client written in Java by dl6dbh + (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz) + + The webserver has to run on the same machine as your DxSpider software! + + It is assumed that you have Java installed. You need JDK1.3.1 at least. + + Installation instructions (Performed as root): + + Put all the files in the spider-web directory into a newly created directory + under the DocumentRoot of your websever for instance 'client'. In my case + this is: /home/httpd/html/client/ although ymmv. For Suse the correct + path should be /usr/local/httpd/htdocs/client/ for example. + + Move spider.cgi to the cgi-bin directory of your webserver, in my case that is + /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be + /usr/local/httpd/cgi-bin/ for example. + + Change the permissions of the files to ensure they are correct, obviously you + will need to use the correct path the the files according to your system: + + chmod 755 /home/httpd/html/cgi-bin/spider.cgi + chmod -R 755 /home/httpd/html/client/ + + By default the spider.cgi script should pick up your hostname (As long as this + is set correctly). If it does not or your hostname differs from the name that + you attach to the public address that you are using, then edit spider.cgi : + + # Uncomment and set the hostname manually here if the above fails. + # $HOSTNAME = "gb7mbc.spoo.org" ; + $PORT = "8000" ; + + + telnet (see Listeners.pm) + + NOTE: If you can start the console but cannot connect to the cluster from it, + then it is possible that the machine you are on cannot resolve the hostname of + your cluster machine. If this is the case, you need to set your hostname + manually as above. + + You also need to set the $NODECALL variable. This prints the name of your + choosing (probably your cluster callsign) on the html page. + + You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi + + + + + 8. Security + + From version 1.49 DXSpider has some additional security features. + These are not by any means meant to be exhaustive, however they do + afford some security against piracy. These two new features can be + used independently of each other or in concert to tighten the + security. + + + 8.1. Registration + + The basic principle of registration is simple. If a user is not + registered by the sysop, then they have read-only access to the + cluster. The only thing they can actually send is a talk or a message + to the sysop. In order for them to be able to spot, send announces or + talks etc the sysop must register them with the set/register command, + like this ... + + + + set/register g0vgs + + + + + The user g0vgs can now fully use the cluster. In order to enable + registration, you can issue the command ... + + + + set/var $main::reqreg = 1 + + + + + Any users that are not registered will now see the motd_nor file + rather than the motd file as discussed in the Information, files and + useful programs section. + + + Entering this line at the prompt will only last for the time the + cluster is running of course and would not be present on a restart. + To make the change permanent, add the above line to + /spider/scripts/startup. To read more on the startup file, see the + section on Information, files and useful programs. + + + To unregister a user use unset/register and to show the list of + registered users, use the command show/register. + + + 8.2. Passwords + + At the moment, passwords only affect users who login to a DXSpider + cluster node via telnet. If a user requires a password, they can + either set it themselves or have the sysop enter it for them by using + the set/password command. Any users who already have passwords, such + as remote sysops, will be asked for their passwords automatically by + the cluster. Using passwords in this way means that the user has a + choice on whether to have a password or not. To force the use of + passwords at login, issue the command ... + + + + set/var $main::passwdreq = 1 + + + + + + at the cluster prompt. This can also be added to the + /spider/scripts/startup file as above to make the change permanent. + + + Of course, if you do this you will have to assign a password for each + of your users. If you were asking them to register, it is anticipated + that you would ask them to send you a message both to ask to be + registered and to give you the password they wish to use. + + + Should a user forget their password, it can be reset by the sysop by + first removing the existing password and then setting a new one like + so ... + + + + unset/password g0vgs + set/password g0vgs new_password + + + + + + 9. CVS CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your @@ -1799,14 +2075,9 @@ commands. - THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST - INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! THIS - MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! YOU - HAVE BEEN WARNED!!! - - - DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE - CONSEQUENCES!!! + Please be aware that if you update your system using CVS, it is + possible that you could be running code that is very beta and not + fully tested. There is a possibility that it could be unstable. I am of course assuming that you have a machine with both DXSpider and @@ -1845,7 +2116,6 @@ If you are wanting to update Spider then cd to /tmp - The next step will create a brand new 'spider' directory in your current directory. @@ -1906,16 +2176,16 @@ - and your files will be updated. As above, remember to recompile the "C" client if it has been updated (CVS will tell you) and restart if any of the perl scripts have been altered or added, again, CVS will tell you. + You will find any changes documented in the /spider/Changes file. - 8. The DXSpider command set + 10. The DXSpider command set Below is a complete list of commands available from the cluster prompt. Most maintenance tasks are automatic but there are some @@ -1924,7 +2194,7 @@ is the permissions level needed to use the command. - 8.1. accept/announce (0) + 10.1. accept/announce (0) accept/announce [0-9] Set an accept filter line for announce @@ -1971,13 +2241,17 @@ - acc/ann by G,M,2 + + acc/ann by G,M,2 This filter would only allow announces that were posted buy UK stations. You can use the tag 'all' to accept everything eg: + + + acc/ann all @@ -1986,7 +2260,7 @@ but this probably for advanced users... - 8.2. accept/announce (extended for sysops) (8) + 10.2. accept/announce (extended for sysops) (8) accept/announce [input] [0-9] Announce filter sysop version @@ -2005,7 +2279,7 @@ - 8.3. accept/route (8) + 10.3. accept/route (8) accept/route [0-9] Set an 'accept' filter line for routing @@ -2034,9 +2308,6 @@ origin_zone - - - some examples:- @@ -2044,6 +2315,10 @@ acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE) + + + + You can use the tag 'all' to accept everything eg: @@ -2054,9 +2329,9 @@ - 8.4. accept/spots (0) + 10.4. accept/spots (0) - accept/announce [0-9] Set an accept filter line for spots + accept/spots [0-9] Set an accept filter line for spots Create an 'accept this spot' line for a filter. @@ -2098,8 +2373,9 @@ - acc/spot 1 on hf/cw - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + + acc/spot 1 on hf/cw + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) @@ -2110,10 +2386,13 @@ acc/spot 3 all + + + but this probably for advanced users... - 8.5. accept/spots (extended for sysops) (8) + 10.5. accept/spots (extended for sysops) (8) accept/spots [input] [0-9] Spot filter sysop version @@ -2133,7 +2412,7 @@ - 8.6. accept/wcy (0) + 10.6. accept/wcy (0) accept/wcy [0-9] set an accept WCY filter @@ -2166,7 +2445,7 @@ See HELP FILTER for information. - 8.7. accept/wcy (extended for sysops) (8) + 10.7. accept/wcy (extended for sysops) (8) accept/wcy [input] [0-9] WCY filter sysop version @@ -2176,14 +2455,14 @@ - accept/wcy node_default all - set/hops node_default 10 + accept/wcy node_default all + set/hops node_default 10 - 8.8. accept/wwv (0) + 10.8. accept/wwv (0) accept/wwv [0-9] Set an accept WWV filter @@ -2221,11 +2500,12 @@ See HELP FILTER for information. - 8.9. accept/wwv (extended for sysops) (8) + 10.9. accept/wwv (extended for sysops) (8) accept/wwv [input] [0-9] WWV filter sysop version + This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:- @@ -2241,8 +2521,7 @@ - - 8.10. announce (0) + 10.10. announce (0) announce Send an announcement to local users @@ -2253,7 +2532,7 @@ sysop will override set/noannounce. - 8.11. announce full (0) + 10.11. announce full (0) announce full Send an announcement cluster wide @@ -2263,7 +2542,7 @@ - 8.12. announce sysop (5) + 10.12. announce sysop (5) announce sysop @@ -2271,7 +2550,7 @@ Send an announcement to Sysops only - 8.13. apropos (0) + 10.13. apropos (0) apropos Search the help database @@ -2280,7 +2559,7 @@ print the names of all the commands that may be relevant. - 8.14. bye (0) + 10.14. bye (0) bye Exit from the cluster @@ -2288,7 +2567,7 @@ This will disconnect you from the cluster - 8.15. catchup (5) + 10.15. catchup (5) catchup All|[ ...] Mark a message as sent @@ -2323,7 +2602,31 @@ Order is not important. - 8.16. clear/spots (0) + 10.16. clear/announce (8) + + clear/announce [input] [0-9|all] Clear an announce filter + line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 10.17. clear/route (8) + + clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line + + + This command allows you to clear (remove) a line in a route filter or + to remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 10.18. clear/spots (0) clear/spots [1|all] Clear a spot filter line @@ -2335,8 +2638,8 @@ - acc/spot 1 on hf/cw - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + acc/spot 1 on hf/cw + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) @@ -2371,10 +2674,57 @@ the filter will be completely removed. + 10.19. clear/spots (extended for sysops) (8) + + clear/spots [input] [0-9|all] Clear a spot filter line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + 10.20. clear/wcy (0) - 8.17. connect (5) + clear/wcy [1|all] Clear a WCY filter line + + + This command allows you to clear (remove) a line in a WCY filter or to + remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. + + + 10.21. clear/wcy (extended for sysops) (8) + + clear/wcy [input] [0-9|all] Clear a WCY filter line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + + 10.22. clear/wwv (0) + + clear/wwv [1|all] Clear a WWV filter line + + + This command allows you to clear (remove) a line in a WWV filter or to + remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. + + + 10.23. clear/wwv (extended for sysops) (8) + + clear/wwv [input] [0-9|all] Clear a WWV filter line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 10.24. connect (5) connect Start a connection to another DX Cluster @@ -2386,7 +2736,7 @@ cluster . - 8.18. dbavail (0) + 10.25. dbavail (0) dbavail Show a list of all the databases in the system @@ -2395,7 +2745,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. - 8.19. dbcreate (9) + 10.26. dbcreate (9) dbcreate Create a database entry dbcreate chain [..] Create a chained database @@ -2419,6 +2769,7 @@ DBCREATE sdx_qsl chain sql_ad + No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. @@ -2440,6 +2791,9 @@ It would be normal for you to add an entry into your local Aliases file to allow people to use the 'SHOW/' style syntax. So you would need to add a line like:- + + + 's' => [ .. .. @@ -2461,7 +2815,7 @@ databases. See DBSHOW for generic database enquiry - 8.20. dbimport (9) + 10.27. dbimport (9) dbimport Import AK1A data into a database @@ -2476,11 +2830,12 @@ oblast database held locally. - 8.21. dbremove (9) + 10.28. dbremove (9) dbremove Delete a database + DBREMOVE will completely remove a database entry and also delete any data file that is associated with it. @@ -2500,12 +2855,11 @@ You have been warned. - 8.22. dbshow (0) + 10.29. dbshow (0) dbshow Display an entry, if it exists, in a database - This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of @@ -2518,38 +2872,73 @@ - but if he hasn't and the database really does exist (use DBAVAIL or - SHOW/COMMAND to find out) you can do the same thing with: + but if he hasn't and the database really does exist (use DBAVAIL or + SHOW/COMMAND to find out) you can do the same thing with: + + + + DBSHOW buck G1TLH + + + + + + + 10.30. debug (9) + + debug Set the cluster program into debug mode + + + Executing this command will only have an effect if you are running the + cluster in debug mode i.e. + + + + perl -d cluster.pl + + + + It will interrupt the cluster just after the debug command has + finished. + 10.31. delete/user (9) - DBSHOW buck G1TLH + delete/user Delete a user from the User Database + This command will completely remove a one or more users from the + database. + There is NO SECOND CHANCE. + It goes without saying that you should use this command CAREFULLY! - 8.23. debug (9) + 10.32. demonstrate (9) - debug Set the cluster program into debug mode + demonstrate Demonstrate a command to another user - Executing this command will only have an effect if you are running the - cluster in debug mode i.e. + This command is provided so that sysops can demonstrate commands to + other users. It runs a command as though that user had typed it in and + then sends the output to that user, together with the command that + caused it. - perl -d cluster.pl + DEMO g7brn sh/dx iota oc209 + DEMO g1tlh set/here - It will interrupt the cluster just after the debug command has - finished. + Note that this command is similar to SPOOF and will have the same side + effects. Commands are run at the privilege of the user which is being + demonstrated to. - 8.24. directory (0) + 10.33. directory (0) directory List messages directory own List your own messages @@ -2572,13 +2961,13 @@ You can combine some of the various directory commands together eg:- + DIR TO G1TLH 5 or DIR SUBJECT IOTA 200-250 - You can abbreviate all the commands to one letter and use ak1a syntax:- @@ -2592,13 +2981,13 @@ - 8.25. directory (extended for sysops) (5) + 10.34. directory (extended for sysops) (5) Works just like the user command except that sysops can see ALL messages. - 8.26. disconnect (8) + 10.35. disconnect (8) disconnect [ ...] Disconnect a user or node @@ -2606,7 +2995,7 @@ Disconnect any connected locally - 8.27. dx (0) + 10.36. dx (0) dx [by ] Send a DX spot @@ -2637,8 +3026,7 @@ - - DX by G1TLH FR0G 144.600 he isn't on the cluster + DX by G1TLH FR0G 144.600 he isn't on the cluster @@ -2646,8 +3034,7 @@ The is compared against the available bands set up in the cluster. See SHOW/BANDS for more information. - - 8.28. export (9) + 10.37. export (9) export Export a message to a file @@ -2665,7 +3052,7 @@ EXPORT 2345 /tmp/a - 8.29. export_users (9) + 10.38. export_users (9) export_users [] Export the users database to ascii @@ -2681,7 +3068,139 @@ check is made on the filename (if any) that you specify. - 8.30. forward/latlong (8) + 10.39. filtering (0) + + filtering Filtering things in DXSpider + + + There are a number of things you can filter in the DXSpider system. + They all use the same general mechanism. + + In general terms you can create a 'reject' or an 'accept' filter which + can have up to 10 lines in it. You do this using, for example:- + + accept/spots ..... reject/spots ..... + + where ..... are the specific commands for that type of filter. There + are filters for spots, wwv, announce, wcy and (for sysops) connects. + See each different accept or reject command reference for more + details. + + There is also a command to clear out one or more lines in a filter and + one to show you what you have set. They are:- + + clear/spots 1 clear/spots all + + and + + show/filter + + There is clear/xxxx command for each type of filter. + + For now we are going to use spots for the examples, but you can apply + the principles to all types of filter. + + There are two main types of filter 'accept' or 'reject'; which you use + depends entirely on how you look at the world and what is least + writing to achieve what you want. Each filter has 10 lines (of any + length) which are tried in order. If a line matches then the action + you have specified is taken (ie reject means ignore it and accept + means gimme it). + + The important thing to remember is that if you specify a 'reject' + filter (all the lines in it say 'reject/spots' (for instance) then if + a spot comes in that doesn't match any of the lines then you will get + it BUT if you specify an 'accept' filter then any spots that don't + match are dumped. For example if I have a one line accept filter:- + + accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + + then automatically you will ONLY get VHF spots from or to CQ zones 14 + 15 and 16. If you set a reject filter like: + + reject/spots on hf/cw + + Then you will get everything EXCEPT HF CW spots, If you am interested + in IOTA and will work it even on CW then you could say:- + + reject/spots on hf/cw and not info iota + + But in that case you might only be interested in iota and say:- + + accept/spots not on hf/cw or info iota + + which is exactly the same. You should choose one or the other until + you are confortable with the way it works. Yes, you can mix them + (actually you can have an accept AND a reject on the same line) but + don't try this at home until you can analyse the results that you get + without ringing up the sysop for help. + + You can arrange your filter lines into logical units, either for your + own understanding or simply convenience. I have one set frequently:- + + reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone + 14,15,16 or call_zone 14,15,16) + + What this does is to ignore all HF CW spots (being a class B I can't + read any CW and couldn't possibly be interested in HF :-) and also + rejects any spots on VHF which don't either originate or spot someone + in Europe. + + This is an exmaple where you would use the line number (1 and 2 in + this case), if you leave the digit out, the system assumes '1'. Digits + + You can leave the word 'and' out if you want, it is implied. You can + use any number of brackets to make the 'expression' as you want it. + There are things called precedence rules working here which mean that + you will NEED brackets in a situation like line 2 because, without it, + will assume:- + + (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 + + annoying, but that is the way it is. If you use OR - use brackets. + Whilst we are here CASE is not important. 'And BY_Zone' is just 'and + by_zone'. + + If you want to alter your filter you can just redefine one or more + lines of it or clear out one line. For example:- + + reject/spots 1 on hf/ssb + + or + + clear/spots 1 + + To remove the filter in its entirty:- + + clear/spots all + + There are similar CLEAR commands for the other filters:- + + clear/announce clear/wcy clear/wwv + + ADVANCED USERS:- + + Once you are happy with the results you get, you may like to + experiment. + + my example that filters hf/cw spots and accepts vhf/uhf spots from EU + can be written with a mixed filter, eg: + + rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and + (by_zone 14,15,16 or call_zone 14,15,16) + + each filter slot actually has a 'reject' slot and an 'accept' slot. + The reject slot is executed BEFORE the accept slot. + + It was mentioned earlier that after a reject test that doesn't match, + the default for following tests is 'accept', the reverse is true for + first, any non hf/cw spot is passed to the accept line, which lets + thru everything else on HF. + + The next filter line lets through just VHF/UHF spots from EU. + + + 10.40. forward/latlong (8) forward/latlong Send latitude and longitude information to another cluster @@ -2695,7 +3214,7 @@ so it is not recommended on slow links. - 8.31. forward/opername (1) + 10.41. forward/opername (1) forward/opername Send out information on this to all clusters @@ -2707,11 +3226,12 @@ available. - 8.32. help (0) + 10.42. help (0) help Get help on a command + All commands can be abbreviated, so SHOW/DX can be abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on. @@ -2720,7 +3240,7 @@ commands to look at with HELP. - 8.33. init (5) + 10.43. init (5) init Re-initialise a link to an AK1A compatible node @@ -2734,7 +3254,7 @@ Best of luck - you will need it. - 8.34. kill (0) + 10.44. kill (0) kill [ ..] Delete a message from the local system @@ -2744,7 +3264,7 @@ the sysop). - 8.35. kill (5) + 10.45. kill (5) kill [ ...] Remove or erase a message from the system kill from Remove all messages from a callsign @@ -2757,7 +3277,7 @@ As a sysop you can kill any message on the system. - 8.36. kill full (5) + 10.46. kill full (5) kill full [] Delete a message from the whole cluster @@ -2768,9 +3288,24 @@ same subject will be deleted. Beware! + 10.47. kill/expunge (6) + + kill/expunge [..]Expunge a message + + + Deleting a message using the normal KILL commands only marks that + message for deletion. The actual deletion only happens later (usually + two days later). + + The KILL EXPUNGE command causes the message to be truly deleted more + or less immediately. - 8.37. links (0) + It otherwise is used in the same way as the KILL command. + + + + 10.48. links (0) links Show which nodes are physically connected @@ -2780,7 +3315,7 @@ - 8.38. load/aliases (9) + 10.49. load/aliases (9) load/aliases Reload the command alias table @@ -2790,7 +3325,7 @@ running in order for the changes to take effect. - 8.39. load/badmsg (9) + 10.50. load/badmsg (9) load/badmsg Reload the bad message table @@ -2802,7 +3337,21 @@ deleted on receipt. - 8.40. load/bands (9) + 10.51. load/badwords (9) + + load/badwords Reload the bad words table + + + Reload the /spider/data/badwords file if you have changed it manually + whilst the cluster is running. This file contains a list of words + which, if found on certain text portions of PC protocol, will cause + those protocol frames to be rejected. It will all put out a message if + any of these words are used on the announce, dx and talk commands. The + words can be one or more on a line, lines starting with '#' are + ignored. + + + 10.52. load/bands (9) load/bands Reload the band limits table @@ -2811,11 +3360,10 @@ whilst the cluster is running. - 8.41. load/cmd_cache (9) + 10.53. load/cmd_cache (9) load/cmd_cache Reload the automatic command cache - Normally, if you change a command file in the cmd or local_cmd tree it will automatially be picked up by the cluster program. Sometimes it can get confused if you are doing a lot of moving commands about or @@ -2824,7 +3372,7 @@ was just after a cluster restart. - 8.42. load/forward (9) + 10.54. load/forward (9) load/forward Reload the msg forwarding routing table @@ -2832,10 +3380,11 @@ whilst the cluster is running. - 8.43. load/messages (9) + 10.55. load/messages (9) load/messages Reload the system messages file + If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne commands) you can have them take effect during a cluster session by executing this command. You need to do this if get @@ -2844,7 +3393,7 @@ unknown message 'xxxx' in lang 'en' - 8.44. load/prefixes (9) + 10.56. load/prefixes (9) load/prefixes Reload the prefix table @@ -2853,7 +3402,7 @@ manually whilst the cluster is running. - 8.45. merge (5) + 10.57. merge (5) merge [/] Ask for the latest spots and WWV @@ -2868,7 +3417,7 @@ data). - 8.46. msg (9) + 10.58. msg (9) msg [data ...] Alter various message parameters @@ -2879,20 +3428,22 @@ - MSG TO - change TO callsign to - MSG FRom - change FROM callsign to - MSG PRrivate - set private flag - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waitting time for this message - MSG NOREad - mark message as unread - MSG REad - mark message as read - MSG QUeue - queue any outstanding bulletins - MSG QUeue 1 - queue any outstanding private messages + + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waitting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages @@ -2901,11 +3452,10 @@ STAT/MSG - This will display more information on the message than DIR does. - 8.47. pc (8) + 10.59. pc (8) pc Send text (eg PC Protocol) to @@ -2924,7 +3474,7 @@ pc G1TLH Try doing that properly!!! - 8.48. ping (1) + 10.60. ping (1) ping Check the link quality between nodes @@ -2937,7 +3487,7 @@ - 8.49. rcmd (1) + 10.61. rcmd (1) rcmd Send a command to another DX cluster @@ -2945,13 +3495,14 @@ This command allows you to send nearly any command to another DX Cluster node that is connected to the system. + Whether you get any output is dependant on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all. - 8.50. read (0) + 10.62. read (0) read Read the next unread personal message addressed to you read Read the specified message @@ -2962,16 +3513,15 @@ - 8.51. read (extended for sysops) (5) + 10.63. read (extended for sysops) (5) read Read a message on the system - As a sysop you may read any message on the system - 8.52. reject/announce + 10.64. reject/announce reject/announce [0-9] Set a reject filter for announce @@ -3024,7 +3574,7 @@ but this probably for advanced users... - 8.53. reject/announce (extended for sysops) (8) + 10.65. reject/announce (extended for sysops) (8) reject/announce [input] [0-9] Announce filter sysop version @@ -3034,6 +3584,7 @@ the default for nodes and users eg:- + reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2 @@ -3042,7 +3593,7 @@ - 8.54. reject/route (8) + 10.66. reject/route (8) reject/route [0-9] Set an 'reject' filter line for routing @@ -3076,7 +3627,8 @@ - rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) + + rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) @@ -3092,14 +3644,13 @@ - 8.55. reject/spots (0) + 10.67. reject/spots (0) reject/spots [0-9] Set a reject filter line for spots Create a 'reject this spot' line for a filter. - A reject filter line means that if the spot matches this filter it is dumped (not passed on). See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief @@ -3142,6 +3693,7 @@ + You can use the tag 'all' to reject everything eg: @@ -3154,7 +3706,7 @@ but this probably for advanced users... - 8.56. reject/spots (extended for sysops) (8) + 10.68. reject/spots (extended for sysops) (8) reject/spots [input] [0-9] Reject spot filter sysop version @@ -3165,18 +3717,17 @@ + reject/spot db0sue-7 1 by_zone 14,15,16 + reject/spot node_default all + set/hops node_default 10 - reject/spot db0sue-7 1 by_zone 14,15,16 - reject/spot node_default all - set/hops node_default 10 - - reject/spot user_default by G,M,2 + reject/spot user_default by G,M,2 - 8.57. reject/wcy (0) + 10.69. reject/wcy (0) reject/wcy [0-9] Set a reject WCY filter @@ -3208,7 +3759,8 @@ See HELP FILTER for information. - 8.58. reject/wcy (extended for sysops) (8) + + 10.70. reject/wcy (extended for sysops) (8) reject/wcy [input] [0-9] WCY reject filter sysop version @@ -3220,7 +3772,7 @@ reject/wcy gb7djk all - 8.59. reject/wwv (0) + 10.71. reject/wwv (0) reject/wwv [0-9] Set a reject WWV filter @@ -3230,17 +3782,15 @@ - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -3260,7 +3810,7 @@ See HELP FILTER for information. - 8.60. reject/wwv (extended for sysops) (8) + 10.72. reject/wwv (extended for sysops) (8) reject/wwv [input] [0-9] WWV reject filter sysop version @@ -3276,11 +3826,7 @@ reject/wwv user_default by W - - - - - 8.61. reply (0) + 10.73. reply (0) reply Reply (privately) to the last message that you have read reply Reply (privately) to the specified message @@ -3297,8 +3843,7 @@ further details) - - 8.62. send (0) + 10.74. send (0) send [ ...] Send a message to one or more callsigns send RR Send a message and ask for a read receipt @@ -3332,7 +3877,7 @@ is an alias for SEND PRIVATE - 8.63. set/address (0) + 10.75. set/address (0) set/address Record your postal address @@ -3340,15 +3885,14 @@ Literally, record your address details on the cluster. - 8.64. set/announce (0) + 10.76. set/announce (0) set/announce Allow announce messages Allow announce messages to arrive at your terminal. - - 8.65. set/arcluster (5) + 10.77. set/arcluster (5) set/arcluster [ ...] Make the node_call an AR- Cluster type node @@ -3357,13 +3901,12 @@ Set the node_call as an AR-Cluster type node - 8.66. set/baddx (8) + 10.78. set/baddx (8) set/baddx Stop words we do not wish to see in the callsign field of a dx spot being propagated - Setting a word as 'baddx' will prevent spots with that word in the callsign field of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes. @@ -3387,7 +3930,7 @@ - 8.67. set/badnode (6) + 10.79. set/badnode (6) set/badnode Stop spots from this node_call being propagated @@ -3421,7 +3964,7 @@ FILTERing. - 8.68. set/badspotter (8) + 10.80. set/badspotter (8) set/badspotter Stop spots from this callsign being propagated @@ -3455,20 +3998,41 @@ FILTERing. - 8.69. set/beep (0) + 10.81. set/badword (8) - set/beep Add beeps to terminal messages + set/badword Stop things with this word being propogated + + + Setting a word as a 'badword' will prevent things like spots, + announces or talks with this word in the the text part from going any + further. They will not be displayed and they will not be sent onto + other nodes. + + The word must be written in full, no wild cards are allowed eg:- + + set/badword annihilate annihilated annihilation + + will stop anything with these words in the text. + + unset/badword annihilated + + will allow text with this word again. + + 10.82. set/beep (0) + + set/beep Add beeps to terminal messages + Add a beep to DX and other terminal messages. - 8.70. set/bbs (5) + 10.83. set/bbs (5) set/bbs [..]Make a BBS - 8.71. set/clx (5) + 10.84. set/clx (5) set/clx [ ...] Make the node_call a CLX type node @@ -3477,7 +4041,7 @@ Set the node_call as a CLX type node - 8.72. set/debug (9) + 10.85. set/debug (9) set/debug Add a debug level to the debug set @@ -3491,7 +4055,7 @@ You can remove a debug level with unset/debug - 8.73. set/dx (0) + 10.86. set/dx (0) set/dxAllow DX messages to arrive at your terminal @@ -3499,7 +4063,7 @@ You can stop DX messages with the unset/dx command - 8.74. set/dxgrid (0) + 10.87. set/dxgrid (0) set/dxgridAllow grid squares on the end of DX messages @@ -3509,7 +4073,7 @@ to remove the grid squares. - 8.75. set/dxnet (5) + 10.88. set/dxnet (5) set/dxnet [ ...] Make the node_call a DXNet type node @@ -3518,7 +4082,7 @@ Set the node_call as a DXNet type node - 8.76. set/echo (0) + 10.89. set/echo (0) set/echo Make the cluster echo your input @@ -3535,7 +4099,27 @@ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 8.77. set/here (0) + 10.90. set/email (0) + + set/email Set email address(es) and forward your + personals + + + If any personal messages come in for your callsign then you can use + these commands to control whether they are forwarded onto your email + address. To enable the forwarding do something like:- + + SET/EMAIL mike.tubby@somewhere.com + + You can have more than one email address (each one separated by a + space). Emails are forwarded to all the email addresses you specify. + + You can disable forwarding by:- + + UNSET/EMAIL + + + 10.91. set/here (0) set/here Set the here flag @@ -3546,7 +4130,7 @@ brackets around your callsign to indicate you are not available. - 8.78. set/homenode (0) + 10.92. set/homenode (0) set/homenode Set your home cluster @@ -3562,7 +4146,8 @@ - 8.79. set/hops (8) + + 10.93. set/hops (8) set/hops ann|spots|wwv|wcy Set hop count @@ -3571,9 +4156,6 @@ This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts. - - - eg: set/hops gb7djk ann 10 set/hops gb7mbc spots 20 @@ -3585,7 +4167,7 @@ creates a filter and works in conjunction with the filter system. - 8.80. set/isolate (9) + 10.94. set/isolate (9) set/isolate Isolate a node from the rest of the network @@ -3603,7 +4185,7 @@ You can remove the isolation with the command unset/isolate. - 8.81. set/language (0) + 10.95. set/language (0) set/language Set the language you wish to use @@ -3612,7 +4194,7 @@ Currently the languages available are en (English) and nl (Dutch). - 8.82. set/location (0) + 10.96. set/location (0) set/location Set your latitude and longitude @@ -3628,7 +4210,8 @@ - 8.83. set/sys_location (9) + + 10.97. set/sys_location (9) set/sys_location Set your cluster latitude and longitude @@ -3639,14 +4222,13 @@ example:- - SET/LOCATION 52 22 N 0 57 E - 8.84. set/logininfo (0) + 10.98. set/logininfo (0) set/logininfo Show logins and logouts of nodes and users @@ -3656,7 +4238,7 @@ - 8.85. set/lockout (9) + 10.99. set/lockout (9) set/lockout Stop a callsign connecting to the cluster @@ -3665,7 +4247,7 @@ allow the user to connect again, use the unset/lockout command. - 8.86. set/name (0) + 10.100. set/name (0) set/name Set your name @@ -3680,7 +4262,7 @@ - 8.87. set/node (9) + 10.101. set/node (9) set/node [ ...] Make the callsign an AK1A cluster @@ -3692,20 +4274,21 @@ + set/spider + set/dxnet + set/clx + set/arcluster + - set/spider - set/dxnet - set/clx - set/arcluster + To see what your nodes are set to, use the show/nodes command. - To see what your nodes are set to, use the show/nodes command. - 8.88. set/obscount (9) + 10.102. set/obscount (9) set/obscount Set the 'pump-up' obsolescence counter @@ -3726,7 +4309,7 @@ minutes, it is disconnected. - 8.89. set/page (0) + 10.103. set/page (0) set/page Set the number of lines per page @@ -3746,21 +4329,48 @@ The setting is stored in your user profile. + 10.104. set/password (0) + + set/password Set your own password + - 8.90. set/password (9) + This command only works for a 'telnet' user (currently). It will only + work if you have a password already set. This initial password can + only be set by the sysop. + + When you execute this command it will ask you for your old password, + then ask you to type in your new password twice (to make sure you get + it right). You may or may not see the data echoed on the screen as you + type, depending on the type of telnet client you have. + + + 10.105. set/password (9) set/password Set a users password The password for a user can only be set by a full sysop. The string - can contain any characters but any spaces are removed (you can type in - spaces - but they won't appear in the password). You can see the - result with STAT/USER. The password is the usual 30 character baycom - type password. + can contain any characters. + + The way this field is used depends on context. If it is being used in + the SYSOP command context then you are offered 5 random numbers and + you have to supply the corresponding letters. This is now mainly for + ax25 connections. + If it is being used on incoming telnet connections then, if a password + is set or the: + set/var $main::passwdreq = 1 - 8.91. set/pinginterval (9) + command is executed in the startup script, then a password prompt is + given after the normal 'login: ' prompt. + + The command "unset/password" is provided to allow a sysop to remove a + users password completely in case a user forgets or loses their + password. + + + 10.106. set/pinginterval (9) set/pinginterval