1 The DXSpider Administration Manual v1.48
2 Ian Maude, G0VGS, (ianmaude@btinternet.com)
3 Version 1.48 August 2001 revision 1.1
5 A reference for SysOps of the DXSpider DXCluster program.
6 ______________________________________________________________________
67 1. Routing and Filtering
71 1.3 The default_node filter
72 1.4 General route filtering
73 1.5 General filter rules
77 1.9 Advanced filtering
78 1.10 Basic hop control
79 1.11 Isolating networks
84 2.2 Filtering DX callouts (Depricated)
85 2.3 Filtering words from text fields in Announce, Talk and DX spots
95 3.7 Distribution lists
100 4.1 Creating databases
101 4.2 Importing databases
102 4.3 Checking available databases
103 4.4 Looking up databases
104 4.5 Removing databases
106 5. Information, files and useful programs
110 5.3 Other text messages
113 5.6 Updating kepler data
118 7. The DXSpider command set
120 7.1 accept/announce (0)
121 7.2 accept/announce (extended for sysops) (8)
124 7.5 accept/spots (extended for sysops) (8)
126 7.7 accept/wcy (extended for sysops) (8)
128 7.9 accept/wwv (extended for sysops) (8)
130 7.11 announce full (0)
131 7.12 announce sysop (5)
144 7.25 directory (extended for sysops) (5)
148 7.29 export_users (9)
149 7.30 forward/latlong (8)
150 7.31 forward/opername (1)
157 7.38 load/aliases (9)
160 7.41 load/badwords (9)
162 7.43 load/cmd_cache (9)
163 7.44 load/forward (9)
164 7.45 load/messages (9)
165 7.46 load/prefixes (9)
172 7.53 read (extended for sysops) (5)
174 7.55 reject/announce (extended for sysops) (8)
175 7.56 reject/route (8)
176 7.57 reject/spots (0)
177 7.58 reject/spots (extended for sysops) (8)
179 7.60 reject/wcy (extended for sysops) (8)
181 7.62 reject/wwv (extended for sysops) (8)
185 7.66 set/announce (0)
186 7.67 set/arcluster (5)
189 7.70 set/badspotter (8)
199 7.80 set/homenode (0)
202 7.83 set/language (0)
203 7.84 set/location (0)
204 7.85 set/sys_location (9)
205 7.86 set/logininfo (0)
209 7.90 set/obscount (9)
211 7.92 set/password (9)
212 7.93 set/pinginterval (9)
213 7.94 set/privilege (9)
223 7.104 show/badnode (6)
224 7.105 show/badspotter (1)
225 7.106 show/configuration (0)
226 7.107 show/configuration/node (0)
227 7.108 show/connect (1)
233 7.114 show/filter (0)
234 7.115 show/filter (extended for sysops) (5)
236 7.117 show/isolate (1)
237 7.118 show/lockout (9)
242 7.123 show/prefix (0)
243 7.124 show/program (5)
247 7.128 show/satellite (0)
255 7.136 stat/channel (5)
257 7.138 stat/route_node (5)
258 7.139 stat/route_user (5)
265 7.146 wx (enhanced for sysops) (5)
268 ______________________________________________________________________
270 1. Routing and Filtering
274 From DXSpider version 1.48, major changes were introduced to the way
275 node connections are treated. This is part of an ongoing process to
276 remove problems with loops and to enable talk and other functions to
277 propagate across the whole of the worldwide cluster network. In fact,
278 in a Spider network, it would be useful, perhaps even necessary to
279 have loops. This would give real resilience to the network, meaning
280 that if a link dropped, the information flow would simply come in and
281 go out via a different route. Of course, we do not have a complete
282 network of Spider nodes, there are other programs out there. Some of
283 these do not have any protection from loops. Certainly AK1A does not
284 handle loops well at all. It is therefore necessary to have some form
285 of protection for these nodes.
288 This is achieved by using filtering on a route basis. There is a
289 default setting to help to protect the network, especially useful for
290 new and inexperienced SysOps. The idea is simple. When Spider is
291 started for the first time and a connection is made to or from another
292 node, the default is to only send the nodes you already have that are
293 in your own zone. For example, in the UK the default setting would be
294 to send only UK nodes to any connection. This can be filtered further
295 (down to a single node if needed) or expanded as required.
301 As mentioned in the introduction, a default setting exists. If this
302 is all you want to use then that is fine, you have nothing else to do.
303 However, if you want to make any alterations then you need to know a
307 It is possible to reset the default setting for node connections
308 should you wish to do so, however this can be dangerous to the network
309 unless you have some experience in how all this works.... be careful!
310 It is also possible to change settings for one connection only. You
311 can, therefore, have many different filters set dependent on the
312 amount of node links you have.
315 I should at this stage give a little bit of background on filters.
316 All the filters in Spider work in basically the same way. You can
317 either accept or reject various options in order to create the filter
318 rules you wish to achieve. Some filters are user settable, others can
319 only be altered by the sysop. Route filtering can only be done by the
323 1.3. The default_node filter
325 As discussed previously, a default setting exists that only sends
326 nodes from your own zone. This can be overridden by using the
327 default_node filter option like this ...
331 reject/route default_node <filter_option>
335 accept/route default_node <filter_option>
341 where filter_option is one of the following ...
350 origin_dxcc <numbers>
352 origin_zone <numbers>
358 Please be careful if you alter this setting, it will affect ALL your
362 1.4. General route filtering
364 Exactly the same rules apply for general route filtering. You would
365 use either an accept filter or a reject filter like this ...
369 reject/route <node_call> <filter_option>
373 accept/route <node_call> <filter_option>
379 where filter_option is one of the following ...
388 origin_dxcc <numbers>
390 origin_zone <numbers>
397 Here are some examples of route filters ...
401 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
402 rej/route all (equiv to [very] restricted mode)
403 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
404 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
410 1.5. General filter rules
412 Upto v1.44 it was not possible for the user to set their own filters.
413 From v1.45 though that has all changed. It is now possible to set
414 filters for just about anything you wish. If you have just updated
415 from an older version of DXSpider you will need to update your new
416 filters. You do not need to do anything with your old filters, they
417 will be renamed as you update.
420 There are 3 basic commands involved in setting and manipulating
421 filters. These are accept, reject and clear. First we will look
422 generally at filtering. There are a number of things you can filter in
423 the DXSpider system. They all use the same general mechanism.
426 In general terms you can create a 'reject' or an 'accept' filter which
427 can have up to 10 lines in it. You do this using, for example ...
438 where ..... are the specific commands for that type of filter. There
439 are filters for spots, wwv, announce, wcy and (for sysops) connects.
440 See each different accept or reject command reference for more
443 There is also a command to clear out one or more lines in a filter.
454 There is clear/xxxx command for each type of filter.
457 and you can check that your filters have worked by the command ...
469 For now we are going to use spots for the examples, but you can apply
470 the same principles to all types of filter.
475 There are two main types of filter, accept or reject. You can use
476 either to achieve the result you want dependent on your own preference
477 and which is more simple to do. It is pointless writing 8 lines of
478 reject filters when 1 accept filter would do the same thing! Each
479 filter has 10 lines (of any length) which are tried in order. If a
480 line matches then the action you have specified is taken (ie reject
481 means ignore it and accept means take it)
484 If you specify reject filters, then any lines that arrive that match
485 the filter will be dumped but all else will be accepted. If you use
486 an accept filter, then ONLY the lines in the filter will be accepted
487 and all else will be dumped. For example if you have a single line
492 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
497 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
500 If you set a reject filter like this ...
504 reject/spots on hf/cw
509 Then you will get everything EXCEPT HF CW spots. You could make this
510 single filter even more flexible. For example, if you are interested
511 in IOTA and will work it even on CW even though normally you are not
512 interested in CW, then you could say ...
516 reject/spots on hf/cw and not info iota
521 But in that case you might only be interested in iota and say:-
525 accept/spots not on hf/cw or info iota
529 which achieves exactly the same thing. You should choose one or the
530 other until you are comfortable with the way it works. You can mix
531 them if you wish (actually you can have an accept AND a reject on the
532 same line) but don't attempt this until you are sure you know what you
536 You can arrange your filter lines into logical units, either for your
537 own understanding or simply convenience. Here is an example ...
541 reject/spots 1 on hf/cw
542 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
547 What this does is to ignore all HF CW spots and also rejects any spots
548 on VHF which don't either originate or spot someone in Europe.
551 This is an example where you would use a line number (1 and 2 in this
552 case), if you leave the digit out, the system assumes '1'. Digits
553 '0'-'9' are available. This make it easier to see just what filters
554 you have set. It also makes it more simple to remove individual
555 filters, during a contest for example.
558 You will notice in the above example that the second line has
559 brackets. Look at the line logically. You can see there are 2
560 separate sections to it. We are saying reject spots that are VHF or
561 above APART from those in zones 14, 15 and 16 (either spotted there or
562 originated there). If you did not have the brackets to separate the 2
563 sections, then Spider would read it logically from the front and see a
564 different expression entirely ...
568 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
573 The simple way to remember this is, if you use OR - use brackets.
574 Whilst we are here CASE is not important. 'And BY_Zone' is just the
575 same as 'and by_zone'.
577 As mentioned earlier, setting several filters can be more flexible
578 than simply setting one complex one. Doing it in this way means that
579 if you want to alter your filter you can just redefine or remove one
580 or more lines of it or one line. For example ...
584 reject/spots 1 on hf/ssb
589 would redefine our earlier example, or
595 To remove all the filter lines in the spot filter ...
607 You can filter in several different ways. The options are listed in
608 the various helpfiles for accept, reject and filter.
613 Sometimes all that is needed is a general rule for node connects.
614 This can be done with a node_default filter. This rule will always be
615 followed, even if the link is isolated, unless another filter is set
616 specifically. Default rules can be set for nodes and users. They can
617 be set for spots, announces, WWV and WCY. They can also be used for
618 hops. An example might look like this ...
622 accept/spot node_default by_zone 14,15,16,20,33
623 set/hops node_default spot 50
628 This filter is for spots only, you could set others for announce, WWV
629 and WCY. This filter would work for ALL nodes unless a specific
630 filter is written to override it for a particular node. You can also
631 set a user_default should you require. It is important to note that
632 default filters should be considered to be "connected". By this I
633 mean that should you override the default filter for spots, you need
634 to add a rule for the hops for spots also.
637 1.9. Advanced filtering
639 Once you are happy with the results you get, you may like to
643 The previous example that filters hf/cw spots and accepts vhf/uhf
644 spots from EU can be written with a mixed filter, for example ...
650 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
655 Note that the first filter has not been specified with a number. This
656 will automatically be assumed to be number 1. In this case, we have
657 said reject all HF spots in the CW section of the bands but accept all
658 others at HF. Also accept anything in VHF and above spotted in or by
659 operators in the zones 14, 15 and 16. Each filter slot actually has a
660 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
664 It was mentioned earlier that after a reject test that doesn't match,
665 the default for following tests is 'accept', the reverse is true for
666 'accept'. In the example what happens is that the reject is executed
667 first, any non hf/cw spot is passed to the accept line, which lets
668 through everything else on HF. The next filter line lets through just
669 VHF/UHF spots from EU.
672 1.10. Basic hop control
674 In /spider/data you will find a file called hop_table.pl. This is the
675 file that controls your hop count settings. It has a set of default
676 hops on the various PC frames and also a set for each node you want to
677 alter the hops for. You may be happy with the default settings of
678 course, but this powerful tool can help to protect and improve the
679 network. The file will look something like this ...
728 # hop table construction
733 # default hopcount to use
736 # some variable hop counts based on message type
747 # the per node hop control thingy
781 Each set of hops is contained within a pair of curly braces and
782 contains a series of PC frame types. PC11 for example is a DX spot.
783 The figures here are not exhaustive but should give you a good idea of
787 You can alter this file at any time, including whilst the cluster is
788 running. If you alter the file during runtime, the command load/hops
789 will bring your changes into effect.
793 1.11. Isolating networks
795 It is possible to isolate networks from each other on a "gateway" node
796 using the set/isolate <node_call> command.
799 The effect of this is to partition an isolated network completely from
800 another node connected to your node. Your node will appear on and
801 otherwise behave normally on every network to which you are connected,
802 but data from an isolated network will not cross onto any other
803 network or vice versa. However all the spot, announce and WWV traffic
804 and personal messages will still be handled locally (because you are a
805 real node on all connected networks), that is locally connected users
806 will appear on all networks and will be able to access and receive
807 information from all networks transparently. All routed messages will
808 be sent as normal, so if a user on one network knows that you are a
809 gateway for another network, he can still still send a talk/announce
810 etc message via your node and it will be routed across.
813 The only limitation currently is that non-private messages cannot be
814 passed down isolated links regardless of whether they are generated
815 locally. This will change when the bulletin routing facility is added.
818 If you use isolate on a node connection you will continue to receive
819 all information from the isolated partner, however you will not pass
820 any information back to the isolated node. There are times when you
821 would like to forward only spots across a link (maybe during a contest
822 for example). To do this, isolate the node in the normal way and put
823 in a filter in the /spider/filter/spots directory to override the
824 isolate. This filter can be very simple and consists of just one line
830 [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
841 In the /spider/msg directory you will find a file called
842 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
843 original looks something like this ....
859 # the list of regexes for messages that we won't store having
860 # received them (bear in mind that we must receive them fully before
864 # The format of each line is as follows
866 # type source pattern
867 # P/B/F T/F/O/S regex
869 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
870 # source: T - to field, F - from field, O - origin, S - subject
871 # pattern: a perl regex on the field requested
873 # Currently only type B and P msgs are affected by this code.
875 # The list is read from the top down, the first pattern that matches
876 # causes the action to be taken.
878 # The pattern can be undef or 0 in which case it will always be selected
879 # for the action specified
892 I think this is fairly self explanatory. It is simply a list of
893 subject headers that we do not want to pass on to either the users of
894 the cluster or the other cluster nodes that we are linked to. This is
895 usually because of rules and regulations pertaining to items for sale
896 etc in a particular country.
899 2.2. Filtering DX callouts (Depricated)
901 From version 1.47, this method is replaced by the command set/baddx
904 In the same way as mail, there are some types of spot we do not wish
905 to pass on to users or linked cluster nodes. In the /spider/data
906 directory you will find a file called baddx.pl.issue. Rename this to
907 baddx.pl and edit the file. The original looks like this ....
925 # the list of dx spot addresses that we don't store and don't pass on
948 Again, this is simply a list of names we do not want to see in the
949 spotted field of a DX callout.
953 2.3. Filtering words from text fields in Announce, Talk and DX spots
955 Create a file in /spider/data called badwords. The format is quite
956 simple. Lines beginning with # are ignored so comments can be added.
957 An example file is below ...
961 # Below is a list of words we do not wish to see on the cluster
962 grunge grunged grunging
963 splodge splodger splodging
970 Multiple words can be used on the same line as shown. Obviously these
971 are just examples :-)
974 You can reload the file from the cluster prompt as sysop with
980 DXSpider deals seamlessly with standard AK1A type mail. It supports
981 both personal and bulletin mail and the sysop has additional commands
982 to ensure that mail gets to where it is meant. DXSpider will send
983 mail almost immediately, assuming that the target is on line.
984 However, only one mail message is dealt with at any one time. If a
985 mail message is already being sent or recieved, then the new message
986 will be queued until it has finished.
988 The cluster mail is automatically deleted after 30 days unless the
989 sysop sets the "keep" flag using the msg command.
993 Personal mail is sent using the sp command. This is actually the
994 default method of sending mail and so a simple s for send will do. A
995 full list of the send commands and options is in the command set
996 section, so I will not duplicate them here.
1001 Bulletin mail is sent by using the sb command. This is one of the
1002 most common mistakes users make when sending mail. They send a
1003 bulletin mail with s or sp instead of sb and of course the message
1004 never leaves the cluster. This can be rectified by the sysop by using
1008 Bulletin addresses can be set using the Forward.pl file.
1013 DXSpider receives all and any mail sent to it without any alterations
1014 needed in files. Because personal and bulletin mail are treated
1015 differently, there is no need for a list of accepted bulletin
1016 addresses. It is necessary, however, to tell the program which links
1017 accept which bulletins. For example, it is pointless sending
1018 bulletins addresses to "UK" to any links other than UK ones. The file
1019 that does this is called forward.pl and lives in /spider/msg. At
1020 default, like other spider files it is named forward.pl.issue. Rename
1021 it to forward.pl and edit the file to match your requirements. The
1058 # this is an example message forwarding file for the system
1060 # The format of each line is as follows
1062 # type to/from/at pattern action destinations
1063 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1065 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1066 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1067 # pattern: a perl regex on the field requested
1068 # action: I - ignore, F - forward
1069 # destinations: a reference to an array containing node callsigns
1071 # if it is non-private and isn't in here then it won't get forwarded
1073 # Currently only type B msgs are affected by this code.
1075 # The list is read from the top down, the first pattern that matches
1076 # causes the action to be taken.
1078 # The pattern can be undef or 0 in which case it will always be selected
1079 # for the action specified
1081 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1082 # pattern) then it will always be forwarded to every node that doesn't have
1083 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1084 # you allow a new link with this on EVERY bull will be forwarded immediately
1085 # on first connection)
1096 Simply insert a bulletin address and state in the brackets where you
1097 wish that mail to go. For example, you can see here that mail sent to
1098 "UK" will only be sent to the UK links and not to PA4AB-14.
1101 To force the cluster to reread the file use load/forward
1105 3.4. The msg command
1107 The msg command is a very powerful and flexible tool for the sysop.
1108 It allows the sysop to alter to and from fields and make other changes
1109 to manage the cluster mail.
1111 Here is a full list of the various options ...
1123 MSG TO <msgno> <call> - change TO callsign to <call>
1124 MSG FRom <msgno> <call> - change FROM callsign to <call>
1125 MSG PRrivate <msgno> - set private flag
1126 MSG NOPRrivate <msgno> - unset private flag
1127 MSG RR <msgno> - set RR flag
1128 MSG NORR <msgno> - unset RR flag
1129 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1130 MSG NOKEep <msgno> - unset the keep flag
1131 MSG SUbject <msgno> <new> - change the subject to <new>
1132 MSG WAittime <msgno> - remove any waiting time for this message
1133 MSG NOREad <msgno> - mark message as unread
1134 MSG REad <msgno> - mark message as read
1135 MSG QUeue - queue any outstanding bulletins
1136 MSG QUeue 1 - queue any outstanding private messages
1141 These commands are simply typed from within the cluster as the sysop
1147 You can check on a message from within the cluster by using the
1148 command stat/msg. This will give you additional information on the
1149 message number including which nodes have received it, which node it
1150 was received from and when etc. Here is an example of the output of
1155 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1158 Msg Time: 26-Jan-2001 1302Z
1162 Subject: AMSAT 2line KEPS 01025.AMSAT
1164 Got it Nodes: GB7BAA, GB7ADX
1168 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1176 This is described in the section on Other filters so I will not
1180 3.7. Distribution lists
1182 Distribution lists are simply a list of users to send certain types of
1183 mail to. An example of this is mail you only wish to send to other
1184 sysops. In /spider/msg there is a directory called distro. You put
1185 any distibution lists in here. For example, here is a file called
1186 SYSOP.pl that caters for the UK sysops.
1189 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1190 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1191 GB7DXK GB7DXI GB7DXS)
1196 Any mail sent to "sysop" would only be sent to the callsigns in this
1202 Spider provides a simple BBS interface. No input is required from the
1203 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1204 and pushes any required mail to the cluster. No mail can flow from
1205 Spider to the BBS, the interface is one-way.
1208 Please be careful not to flood the cluster network with unnecessary
1209 mail. Make sure you only send mail to the clusters that want it by
1210 using the Forward.pl file very carefully.
1215 Spider allows the creation of local or remote databases. It supports
1216 chained databases, allowing several different databases to be scanned
1217 with one simple command. Importing of databases is limited at present
1218 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1219 database but will expand with time.
1222 4.1. Creating databases
1224 Creating a database could not be more simple. All the commands are
1225 sent from the cluster prompt as the sysop user.
1227 To create a database you use the command dbcreate. It can be used in
1228 3 different ways like so ..
1237 To simply create a database locally, you just tell the command the
1238 name of the database. This does not create the actual database, it
1239 simply defines it to say that it exists.
1243 dbcreate <name> chain <name> [<name>...]
1248 This creates a chained database entry. The first database will be
1249 scanned, then the second, the third etc...
1253 dbcreate <name> remote <name>
1255 This creates a remote entry. the first name field is the database
1256 name at the remote node, then the remote switch, then the actual
1257 node_call of the remote node, for example...
1261 dbcreate buckmaster remote gb7dxc
1266 Remote databases cannot be chained, however, the last database in a
1267 chain can be a remote database.
1270 4.2. Importing databases
1272 The only databases that Spider can currently import are the standard
1273 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1274 This will be added to with time.
1276 To import such a database, first put the file somewhere useful like
1277 /tmp and then issue the following command ...
1281 dbimport oblast /tmp/OBLAST.FUL
1286 This will update the existing local oblast database or create it if it
1290 4.3. Checking available databases
1292 Once a database is created, you will want to check that it has been
1293 added. To do this use the dbavail command. This will output the
1294 available databases. For example ...
1299 DB Name Location Chain
1303 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1309 4.4. Looking up databases
1311 To look for information in a defined database, simply use the dbshow
1312 command, for example ...
1316 dbshow buckmaster G0YLM
1321 will show the information for the callsign G0YLM from the buckmaster
1322 database if it exists. To make things more standard for the users you
1323 can add an entry in the Aliases file so that it looks like a standard
1324 show command like this ...
1332 Now you can simply use show/buckmaster or an abreviation.
1335 4.5. Removing databases
1337 To delete an existing database you use the dbremove command. For
1347 would remove the oblast database and its associated datafile from the
1348 system. There are no warnings or recovery possible from this command.
1349 If you remove a database it ceases to exist and would have to be
1350 created from scratch if you still required it.
1353 5. Information, files and useful programs
1357 One of the more important things a cluster sysop needs to do is to get
1358 information to his users. The simplest way to do this is to have a
1359 banner that is sent to the user on login. This is know as a "message
1360 of the day" or "motd". To set this up, simply create a file in
1361 /spider/data called motd and edit it to say whatever you want. It is
1362 purely a text file and will be sent automatically to anyone logging in
1366 5.2. Downtime message
1368 If for any reason the cluster is down, maybe for upgrade or
1369 maintenance but the machine is still running, a message can be sent to
1370 the user advising them of the fact. This message lives in the
1371 /spider/data directory and is called "offline". Simply create the
1372 file and edit it to say whatever you wish. This file will be sent to
1373 a user attempting to log into the cluster when DXSpider is not
1377 5.3. Other text messages
1379 You can set other text messages to be read by the user if they input
1380 the file name. This could be for news items or maybe information for
1381 new users. To set this up, make a directory under /spider called
1382 packclus. Under this directory you can create files called news or
1383 newuser for example. In fact you can create files with any names you
1384 like. These can be listed by the user with the command ....
1392 They can be read by the user by typing the command ....
1401 If the file they want to read is called news. You could also set an
1402 alias for this in the Alias file to allow them just to type news
1405 You can also store other information in this directory, either
1406 directly or nested under directories. One use for this would be to
1407 store DX bulletins such as the OPDX bulletins. These can be listed
1408 and read by the user. To keep things tidy, make a directory under
1409 /spider/packclus called bulletin. Now copy any OPDX or similar
1410 bulletins into it. These can be listed by the user in the same way as
1411 above using the show/files command with an extension for the bulletin
1412 directory you have just created, like this ....
1422 An example would look like this ....
1427 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1432 You can see that in the files area (basically the packclus directory)
1433 there is a file called news and a directory called bulletin. You can
1434 also see that dates they were created. In the case of the file news,
1435 you can also see the time it was last modified, a good clue as to
1436 whether the file has been updated since you last read it. To read the
1437 file called news you would simply issue the command ....
1446 To look what is in the bulletin directory you issue the command ....
1454 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1455 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1456 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1457 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1458 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1459 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1460 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1461 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1462 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1463 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1464 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1465 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1466 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1467 Press Enter to continue, A to abort (16 lines) >
1472 You can now read any file in this directory using the type command,
1477 type bulletin/opdx391
1478 Ohio/Penn DX Bulletin No. 391
1479 The Ohio/Penn Dx PacketCluster
1483 Editor Tedd Mirgliotta, KB8NW
1484 Provided by BARF-80 BBS Cleveland, Ohio
1485 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1486 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1487 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1488 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1489 Press Enter to continue, A to abort (508 lines) >
1494 The page length will of course depend on what you have it set to!
1497 5.4. The Aliases file
1499 You will find a file in /spider/cmd/ called Aliases. First, copy this
1500 file to /spider/local_cmd/Aliases and edit this file. You will see
1501 something like this ...
1521 # provide some standard aliases for commands for terminally
1522 # helpless ak1a user (helpless in the sense that they never
1523 # read nor understand help files)
1525 # This file is automagically reloaded if its modification time is
1526 # later than the one stored in CmdAlias.pm
1528 # PLEASE make this file consistant with reality! (the patterns MUST
1529 # match the filenames!)
1531 # Don't alter this file, copy it into the local_cmd tree and modify it.
1532 # This file will be replaced everytime I issue a new release.
1534 # You only need to put aliases in here for commands that don't work as
1535 # you desire naturally, e.g sh/dx on its own just works as you expect
1536 # so you need not add it as an alias.
1544 '^\?', 'apropos', 'apropos',
1547 '^ann.*/full', 'announce full', 'announce',
1548 '^ann.*/sysop', 'announce sysop', 'announce',
1549 '^ann.*/(.*)$', 'announce $1', 'announce',
1556 '^del', 'kill', 'kill',
1557 '^del\w*/fu', 'kill full', 'kill',
1558 '^di\w*/a\w*', 'directory all', 'directory',
1559 '^di\w*/b\w*', 'directory bulletins', 'directory',
1560 '^di\w*/n\w*', 'directory new', 'directory',
1561 '^di\w*/o\w*', 'directory own', 'directory',
1562 '^di\w*/s\w*', 'directory subject', 'directory',
1563 '^di\w*/t\w*', 'directory to', 'directory',
1564 '^di\w*/f\w*', 'directory from', 'directory',
1565 '^di\w*/(\d+)', 'directory $1', 'directory',
1582 '^l$', 'directory', 'directory',
1583 '^ll$', 'directory', 'directory',
1584 '^ll/(\d+)', 'directory $1', 'directory',
1589 '^news', 'type news', 'type',
1599 '^r$', 'read', 'read',
1600 '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
1603 '^s/p$', 'send', 'send',
1604 '^sb$', 'send noprivate', 'send',
1605 '^set/home$', 'set/homenode', 'set/homenode',
1606 '^set/nobe', 'unset/beep', 'unset/beep',
1607 '^set/nohe', 'unset/here', 'unset/here',
1608 '^set/noan', 'unset/announce', 'unset/announce',
1609 '^set/nodx', 'unset/dx', 'unset/dx',
1610 '^set/nota', 'unset/talk', 'unset/talk',
1611 '^set/noww', 'unset/wwv', 'unset/wwv',
1612 '^set/nowx', 'unset/wx', 'unset/wx',
1613 '^sh$', 'show', 'show',
1614 '^sh\w*/buck', 'dbshow buck', 'dbshow',
1615 '^sh\w*/bu', 'show/files bulletins', 'show/files',
1616 '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
1617 '^sh\w*/c$', 'show/configuration', 'show/configuration',
1618 '^sh\w*/com', 'dbavail', 'dbavail',
1619 '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
1620 '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
1621 '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
1622 '^sh\w*/email', 'dbshow email', 'dbshow',
1623 '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
1624 '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
1625 '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
1626 '^sh\w*/tnc', 'who', 'who',
1627 '^sh\w*/up', 'show/cluster', 'show/cluster',
1628 '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
1629 '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
1630 '^sp$', 'send', 'send',
1634 '^ta$', 'talk', 'talk',
1635 '^t$', 'talk', 'talk',
1642 '^wx/full', 'wx full', 'wx',
1643 '^wx/sysop', 'wx sysop', 'wx',
1656 You can create aliases for commands at will. Beware though, these may
1657 not always turn out as you think. Care is needed and you need to test
1658 the results once you have set an alias.
1663 In later versions of Spider a simple console program is provided for
1664 the sysop. This has a type ahead buffer with line editing facilities
1665 and colour for spots, announces etc. To use this program, simply use
1666 console.pl instead of client.
1669 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1670 edit the file with your favourite editor.
1673 5.6. Updating kepler data
1675 Spider has a powerful and flexible show/satellite command. In order
1676 for this to be accurate, the kepler data has to be updated regularly.
1677 In general, this data is available as an email or via cluster mail.
1678 Updating it is simple. First you need to export the mail message as a
1679 file. You do this with the export command from the cluster prompt as
1680 the sysop. For example ...
1684 export 5467 /spider/perl/keps.in
1689 would export message number 5467 as a file called keps.in in the
1690 /spider/perl directory.
1692 Now login to a VT as sysop and cd /spider/perl. There is a command in
1693 the perl directory called convkeps.pl. All we need to do now is
1694 convert the file like so ...
1698 ./convkeps.pl keps.in
1703 Now go back to the cluster and issue the command ...
1712 That is it! the kepler data has been updated.
1717 5.7. The QRZ callbook
1719 The command sh/qrz will only work once you have followed a few simple
1720 steps. First you need to get a user ID and password from qrz.com.
1721 Simply go to the site and create one. Secondly you need to copy the
1722 file /spider/perl/Internet.pm to /spider/local and alter it to match
1723 your user ID and password. You also at this point need to set
1724 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1725 proprieter of qrz.com for allowing this access.
1730 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
1731 is held at Sourceforge. This means that it is possible to update your
1732 DXSpider installation to the latest sources by using a few simple
1736 THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
1737 INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! THIS
1738 MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! YOU
1742 DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
1746 I am of course assuming that you have a machine with both DXSpider and
1747 Internet access running.
1750 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
1751 ENTIRE SPIDER TREE!!
1754 Assuming you are connected to the Internet, you need to login to the
1755 CVS repository and then update your Spider source. There are several
1756 steps which are listed below ...
1759 First login as the user sysop. Next you need to connect to the CVS
1760 repository. You do this with the command below ...
1763 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
1767 You will get a password prompt. Simply hit return here and your
1768 machine should return to a normal linux prompt.
1771 What happens next depends on whether you have an existing installation
1772 that you want to update with the latest and greatest or whether you
1773 just want to see what is there and/or run it on a new machine for
1776 If you are installing Spider from CVS then change directory to
1779 If you are wanting to update Spider then cd to /tmp
1783 The next step will create a brand new 'spider' directory in your
1787 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
1791 This command is all on one line.
1794 Hopefully your screen should show you downloading files. The -z3
1795 simply compresses the download to improve speed. When this has
1796 finished, you will have exactly the same as if you had untarred a full
1797 tarball PLUS some extra directories and files that CVS needs to do the
1801 Now if you are doing a new installation, that's it. Carry on as if
1802 you have just downloaded and untarred the lastest tarball.
1805 If you want to upgrade your current installation then do this ...
1809 tar cvfz /tmp/s.tgz spider
1811 tar xvfzp /tmp/s.tgz
1816 This is assuming you downloaded to the /tmp directory of course.
1819 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
1820 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
1823 Remember to recompile the C client (cd /spider/src; make)
1826 At this point the files have been upgraded. You can (usually) restart
1827 the cluster in your own time. However, if you attempt to use any new
1828 commands or features expect it to be fatal! At least your cluster
1829 will have been restarted then so it will be too late to worry about
1833 Now the magic part! From now on when you want to update, simply
1834 connect to the Internet and then, as the user sysop ...
1844 and your files will be updated. As above, remember to recompile the
1845 "C" client if it has been updated (CVS will tell you) and restart if
1846 any of the perl scripts have been altered or added, again, CVS will
1849 You will find any changes documented in the /spider/Changes file.
1852 7. The DXSpider command set
1854 Below is a complete list of commands available from the cluster
1855 prompt. Most maintenance tasks are automatic but there are some
1856 commands that are useful for a sysop. These are listed below in
1857 alphabetical order. The number in brackets following the command name
1858 is the permissions level needed to use the command.
1861 7.1. accept/announce (0)
1863 accept/announce [0-9] <pattern> Set an accept filter line for announce
1866 Create an 'accept this announce' line for a filter.
1868 An accept filter line means that if the announce matches this filter
1869 it is passed onto the user. See HELP FILTERS for more info. Please
1870 read this to understand how filters work - it will save a lot of grief
1873 You can use any of the following things in this line:-
1877 info <string> eg: iota or qsl
1878 by <prefixes> eg: G,M,2
1880 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1881 origin_itu <numbers>
1882 origin_zone <numbers>
1887 wx 1 filter WX announces
1888 dest <prefixes> eg: 6MUK,WDX (distros)
1898 acc/ann 2 by_zone 14,15,16
1899 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1913 This filter would only allow announces that were posted buy UK
1914 stations. You can use the tag 'all' to accept everything eg:
1920 but this probably for advanced users...
1923 7.2. accept/announce (extended for sysops) (8)
1925 accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
1929 This version allows a sysop to set a filter for a callsign as well as
1930 the default for nodes and users eg:-
1935 accept/ann input node_default by G,M,2
1936 accept/ann user_default by G,M,2
1942 7.3. accept/route (8)
1944 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
1948 Create an 'accept this routing PC Protocol' line for a filter.
1951 An accept filter line means that if a PC16/17/19/21/24/41/50 matches
1952 this filter it is passed thru that interface. See HELP FILTERING for
1953 more info. Please read this to understand how filters work - it will
1954 save a lot of grief later on.
1957 You can use any of the following things in this line:-
1961 call <prefixes> the callsign of the thingy
1962 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1965 origin <prefixes> really the interface it came in on
1966 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1967 origin_itu <numbers>
1968 origin_zone <numbers>
1978 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
1979 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
1981 You can use the tag 'all' to accept everything eg:
1991 7.4. accept/spots (0)
1993 accept/announce [0-9] <pattern> Set an accept filter line for spots
1996 Create an 'accept this spot' line for a filter.
1999 An accept filter line means that if the spot matches this filter it is
2000 passed onto the user. See HELP FILTERS for more info. Please read this
2001 to understand how filters work - it will save a lot of grief later on.
2003 You can use any of the following things in this line:-
2007 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2008 on <range> same as 'freq'
2009 call <prefixes> eg: G,PA,HB9
2010 info <string> eg: iota or qsl
2012 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2025 For frequencies, you can use any of the band names defined in
2026 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2027 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2028 this is more efficient than saying simply: freq HF (but don't get too
2036 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2041 You can use the tag 'all' to accept everything, eg:
2047 but this probably for advanced users...
2050 7.5. accept/spots (extended for sysops) (8)
2052 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2055 This version allows a sysop to set a filter for a callsign as well as
2056 the default for nodes and users eg:-
2060 accept/spot db0sue-7 1 by_zone 14,15,16
2061 accept/spot node_default all
2062 set/hops node_default 10
2064 accept/spot user_default by G,M,2
2072 accept/wcy [0-9] <pattern> set an accept WCY filter
2075 It is unlikely that you will want to do this, but if you do then you
2076 can filter on the following fields:-
2080 by <prefixes> eg: G,M,2
2082 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2083 origin_itu <numbers>
2084 origin_zone <numbers>
2094 There are no examples because WCY Broadcasts only come from one place
2095 and you either want them or not (see UNSET/WCY if you don't want
2098 This command is really provided for future use.
2100 See HELP FILTER for information.
2103 7.7. accept/wcy (extended for sysops) (8)
2105 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2108 This version allows a sysop to set a filter for a callsign as well as
2109 the default for nodes and users eg:-
2113 accept/wcy node_default all
2114 set/hops node_default 10
2122 accept/wwv [0-9] <pattern> Set an accept WWV filter
2125 It is unlikely that you will want to do this, but if you do then you
2126 can filter on the following fields:-
2130 by <prefixes> eg: G,M,2
2132 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2133 origin_itu <numbers>
2134 origin_zone <numbers>
2147 accept/wwv by_zone 4
2152 is probably the only useful thing to do (which will only show WWV
2153 broadcasts by stations in the US).
2155 See HELP FILTER for information.
2158 7.9. accept/wwv (extended for sysops) (8)
2160 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2163 This version allows a sysop to set a filter for a callsign as well as
2164 the default for nodes and users eg:-
2168 accept/wwv db0sue-7 1 by_zone 4
2169 accept/wwv node_default all
2170 set/hops node_default 10
2172 accept/wwv user_default by W,K
2181 announce <text> Send an announcement to local users
2184 Send an announcement to LOCAL users only, where <text> is the text of
2185 the announcement you wish to broadcast. If you do not wish to receive
2186 announces, use the set/noannounce command. Any announces made by a
2187 sysop will override set/noannounce.
2190 7.11. announce full (0)
2192 announce full <text> Send an announcement cluster wide
2195 This command will send your announcement across the whole cluster
2200 7.12. announce sysop (5)
2202 announce sysop <text>
2205 Send an announcement to Sysops only
2210 apropos <string> Search the help database
2213 Search the help database for <string> (it isn't case sensitive), and
2214 print the names of all the commands that may be relevant.
2219 bye Exit from the cluster
2222 This will disconnect you from the cluster
2227 catchup <node_call> All|[<msgno> ...] Mark a message as sent
2230 When you send messages the fact that you have forwarded it to another
2231 node is remembered so that it isn't sent again. When you have a new
2232 partner node and you add their callsign to your /spider/msg/forward.pl
2233 file, all outstanding non-private messages will be forwarded to them.
2234 This may well be ALL the non-private messages. You can prevent this by
2235 using these commmands:-
2240 catchup GB7DJK 300 301 302 303 500-510
2245 and to undo what you have just done:-
2249 uncatchup GB7DJK all
2250 uncatchup GB7DJK 300 301 302 303 500-510
2255 which will arrange for them to be forward candidates again.
2257 Order is not important.
2260 7.16. clear/spots (0)
2262 clear/spots [1|all] Clear a spot filter line
2265 This command allows you to clear (remove) a line in a spot filter or
2266 to remove the whole filter.
2268 If you have a filter:-
2273 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2287 you will be left with:-
2291 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2305 the filter will be completely removed.
2313 connect <callsign> Start a connection to another DX Cluster
2316 Start a connection process that will culminate in a new connection to
2317 the DX cluster <callsign>. This process creates a new 'client' process
2318 which will use the script in /spider/connect/<callsign> to effect the
2319 'chat' exchange necessary to traverse the network(s) to logon to the
2325 dbavail Show a list of all the databases in the system
2328 The title says it all really, this command lists all the databases
2329 defined in the system. It is also aliased to SHOW/COMMAND.
2334 dbcreate <name> Create a database entry
2335 dbcreate <name> chain <name> [<name>..] Create a chained database
2337 dbcreate <name> remote <node> Create a remote database entry
2340 DBCREATE allows you to define a database in the system. It doesn't
2341 actually create anything, just defines it.
2343 The databases that are created are simple DB_File hash databases, they
2344 are therefore already 'indexed'.
2346 You can define a local database with the first form of the command eg:
2350 You can also chain databases with the addition of the 'chain' keyword.
2351 This will search each database one after the other. A typical example
2354 DBCREATE sdx_qsl chain sql_ad
2356 No checking is done to see if the any of the chained databases exist,
2357 in fact it is usually better to do the above statement first then do
2358 each of the chained databases.
2360 Databases can exist offsite. To define a database that lives on
2363 DBCREATE buckmaster remote gb7dxc
2365 Remote databases cannot be chained; however, the last database in a a
2366 chain can be a remote database eg:
2368 DBCREATE qsl chain gb7dxc
2370 To see what databases have been defined do:
2372 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2374 It would be normal for you to add an entry into your local Aliases
2375 file to allow people to use the 'SHOW/<dbname>' style syntax. So you
2376 would need to add a line like:-
2380 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
2392 to work as they may be used to.
2394 See DBIMPORT for the importing of existing AK1A format data to
2395 databases. See DBSHOW for generic database enquiry
2400 dbimport <dbname> Import AK1A data into a database
2403 If you want to import or update data in bulk to a database you can use
2404 this command. It will either create or update entries into an existing
2405 database. For example:-
2407 DBIMPORT oblast /tmp/OBLAST.FUL
2409 will import the standard OBLAST database that comes with AK1A into the
2410 oblast database held locally.
2415 dbremove <dbname> Delete a database
2418 DBREMOVE will completely remove a database entry and also delete any
2419 data file that is associated with it.
2421 There is no warning, no comeback, no safety net.
2427 will remove the oblast database from the system and it will also
2428 remove the associated datafile.
2432 There is no warning, no comeback, no safety net.
2434 You have been warned.
2439 dbshow <dbname> <key> Display an entry, if it exists, in a database
2443 This is the generic user interface to the database to the database
2444 system. It is expected that the sysop will add an entry to the local
2445 Aliases file so that users can use the more familiar AK1A style of
2455 but if he hasn't and the database really does exist (use DBAVAIL or
2456 SHOW/COMMAND to find out) you can do the same thing with:
2469 debug Set the cluster program into debug mode
2472 Executing this command will only have an effect if you are running the
2473 cluster in debug mode i.e.
2482 It will interrupt the cluster just after the debug command has
2488 directory List messages
2489 directory own List your own messages
2490 directory new List all new messages
2491 directory to <call> List all messages to <call>
2492 directory from <call> List all messages from <call>
2493 directory subject <string> List all messages with <string> in subject
2494 directory <nn> List last <nn> messages
2495 directory <from>-<to> List messages <from> message <to> message
2498 List the messages in the messages directory.
2500 If there is a 'p' one space after the message number then it is a
2501 personal message. If there is a '-' between the message number and the
2503 You can use shell escape characters such as '*' and '?' in the <call>
2506 You can combine some of the various directory commands together eg:-
2511 DIR SUBJECT IOTA 200-250
2516 You can abbreviate all the commands to one letter and use ak1a
2529 7.25. directory (extended for sysops) (5)
2531 Works just like the user command except that sysops can see ALL
2535 7.26. disconnect (8)
2537 disconnect <call> [<call> ...] Disconnect a user or node
2540 Disconnect any <call> connected locally
2545 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2548 This is how you send a DX Spot to other users. You can, in fact, now
2549 enter the <freq> and the <call> either way round.
2560 will all give the same result. You can add some remarks to the end of
2561 the command and they will be added to the spot.
2565 DX FR0G 144600 this is a test
2570 You can credit someone else by saying:-
2575 DX by G1TLH FR0G 144.600 he isn't on the cluster
2580 The <freq> is compared against the available bands set up in the
2581 cluster. See SHOW/BANDS for more information.
2586 export <msgno> <filename> Export a message to a file
2589 Export a message to a file. This command can only be executed on a
2590 local console with a fully privileged user. The file produced will be
2591 in a form ready to be imported back into the cluster by placing it in
2592 the import directory (/spider/msg/import).
2594 This command cannot overwrite an existing file. This is to provide
2595 some measure of security. Any files written will owned by the same
2596 user as the main cluster, otherwise you can put the new files anywhere
2597 the cluster can access. For example:-
2602 7.29. export_users (9)
2604 export_users [<filename>] Export the users database to ascii
2607 Export the users database to a file in ascii format. If no filename is
2608 given then it will export the file to /spider/data/user_asc.
2610 If the file already exists it will be renamed to <filename>.o. In fact
2611 up to 5 generations of the file can be kept each one with an extra 'o'
2614 BE WARNED: this will write to any file you have write access to. No
2615 check is made on the filename (if any) that you specify.
2618 7.30. forward/latlong (8)
2620 forward/latlong <node_call> Send latitude and longitude information to
2624 This command sends all the latitude and longitude information that
2625 your cluster is holding against callsigns. One advantage of recieving
2626 this information is that more locator information is held by you.
2627 This means that more locators are given on the DX line assuming you
2628 have set/dxgrid enabled. This could be a LOT of information though,
2629 so it is not recommended on slow links.
2632 7.31. forward/opername (1)
2634 forward/opername <call> Send out information on this <call> to all
2638 This command sends out any information held in the user file which can
2639 be broadcast in PC41 protocol packets. This information is Name, QTH,
2640 Location and Homenode. PC41s are only sent for the information that is
2646 help <cmd> Get help on a command
2649 All commands can be abbreviated, so SHOW/DX can be abbreviated to
2650 SH/DX, ANNOUNCE can be shortened to AN and so on.
2652 Look at the APROPOS <string> command which will search the help
2653 database for the <string> you specify and give you a list of likely
2654 commands to look at with HELP.
2659 init <node call> Re-initialise a link to an AK1A compatible node
2662 This command attempts to re-initialise a link to a (usually) AK1A node
2663 that has got confused, usually by a protocol loop of some kind. It may
2664 work - but you usually will be better off simply disconnecting it (or
2665 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
2668 Best of luck - you will need it.
2673 kill <msgno> [<msgno> ..] Delete a message from the local system
2676 Delete a message from the local system. You will only be able to
2677 delete messages that you have originated or been sent (unless you are
2683 kill <msgno> [<msgno> ...] Remove or erase a message from the system
2684 kill from <call> Remove all messages from a callsign
2685 kill to <call> Remove all messages to a callsign
2688 You can get rid of any message to or originating from your callsign
2689 using this command. You can remove more than one message at a time.
2691 As a sysop you can kill any message on the system.
2696 kill full <msgno> [<msgno>] Delete a message from the whole cluster
2699 Delete a message (usually a 'bulletin') from the whole cluster system.
2701 This uses the subject field, so any messages that have exactly the
2702 same subject will be deleted. Beware!
2709 links Show which nodes are physically connected
2712 This is a quick listing that shows which links are connected and some
2713 information about them. See WHO for a list of all connections.
2717 7.38. load/aliases (9)
2719 load/aliases Reload the command alias table
2722 Reload the /spider/cmd/Aliases file after you have editted it. You
2723 will need to do this if you change this file whilst the cluster is
2724 running in order for the changes to take effect.
2728 7.39. load/baddx (9)
2730 load/baddx Reload the bad DX table
2733 Reload the /spider/data/baddx.pl file if you have changed it manually
2734 whilst the cluster is running. This table contains the DX Calls that,
2735 if spotted, will not be passed on. FR0G and TEST are classic examples.
2738 7.40. load/badmsg (9)
2740 load/badmsg Reload the bad message table
2743 Reload the /spider/msg/badmsg.pl file if you have changed it manually
2744 whilst the cluster is running. This table contains a number of perl
2745 regular expressions which are searched for in the fields targetted of
2746 each message. If any of them match then that message is immediately
2750 7.41. load/badwords (9)
2752 load/badwords Reload the badwords file
2755 Reload the /spider/data/badwords file if you have changed it manually
2756 whilst the cluster is running. This file contains a list of words
2757 which, if found on certain text portions of PC protocol, will cause
2758 those protocol frames to be rejected. It will all put out a message if
2759 any of these words are used on the announce, dx and talk commands. The
2760 words can be one or more on a line, lines starting with '#' are
2764 7.42. load/bands (9)
2766 load/bands Reload the band limits table
2769 Reload the /spider/data/bands.pl file if you have changed it manually
2770 whilst the cluster is running.
2773 7.43. load/cmd_cache (9)
2775 load/cmd_cache Reload the automatic command cache
2778 Normally, if you change a command file in the cmd or local_cmd tree it
2779 will automatially be picked up by the cluster program. Sometimes it
2780 can get confused if you are doing a lot of moving commands about or
2781 delete a command in the local_cmd tree and want to use the normal one
2782 again. Execute this command to reset everything back to the state it
2783 was just after a cluster restart.
2786 7.44. load/forward (9)
2788 load/forward Reload the msg forwarding routing table
2790 Reload the /spider/msg/forward.pl file if you have changed it manually
2791 whilst the cluster is running.
2794 7.45. load/messages (9)
2796 load/messages Reload the system messages file
2799 If you change the /spider/perl/Messages file (usually whilst
2800 fiddling/writing ne commands) you can have them take effect during a
2801 cluster session by executing this command. You need to do this if get
2804 unknown message 'xxxx' in lang 'en'
2807 7.46. load/prefixes (9)
2809 load/prefixes Reload the prefix table
2812 Reload the /spider/data/prefix_data.pl file if you have changed it
2813 manually whilst the cluster is running.
2818 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
2821 MERGE allows you to bring your spot and wwv database up to date. By
2822 default it will request the last 10 spots and 5 WWVs from the node you
2823 select. The node must be connected locally.
2825 You can request any number of spots or wwv and although they will be
2826 appended to your databases they will not duplicate any that have
2827 recently been added (the last 2 days for spots and last month for WWV
2833 msg <cmd> <msgno> [data ...] Alter various message parameters
2836 Alter message parameters like To, From, Subject, whether private or
2837 bulletin or return receipt (RR) is required or whether to keep this
2838 message from timing out.
2839 MSG TO <msgno> <call> - change TO callsign to <call>
2840 MSG FRom <msgno> <call> - change FROM callsign to <call>
2841 MSG PRrivate <msgno> - set private flag
2842 MSG NOPRrivate <msgno> - unset private flag
2843 MSG RR <msgno> - set RR flag
2844 MSG NORR <msgno> - unset RR flag
2845 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
2846 MSG NOKEep <msgno> - unset the keep flag
2847 MSG SUbject <msgno> <new> - change the subject to <new>
2848 MSG WAittime <msgno> - remove any waitting time for this message
2849 MSG NOREad <msgno> - mark message as unread
2850 MSG REad <msgno> - mark message as read
2851 MSG QUeue - queue any outstanding bulletins
2852 MSG QUeue 1 - queue any outstanding private messages
2857 You can look at the status of a message by using:-
2861 This will display more information on the message than DIR does.
2866 pc <call> <text> Send text (eg PC Protocol) to <call>
2869 Send some arbitrary text to a locally connected callsign. No
2870 processing is done on the text. This command allows you to send PC
2871 Protocol to unstick things if problems arise (messages get stuck etc).
2874 pc gb7djk PC33^GB7TLH^GB7DJK^400^
2876 You can also use in the same way as a talk command to a connected user
2877 but without any processing, added of "from <blah> to <blah>" or
2880 pc G1TLH Try doing that properly!!!
2885 ping <node> Check the link quality between nodes
2888 his command allows you to send a frame to another cluster node on the
2889 network and get a return frame. The time it takes to do this is a
2890 good indication of the quality of the link. The actual time it takes
2891 is output to the console in seconds. Any visible cluster node can be
2898 rcmd <node call> <cmd> Send a command to another DX cluster
2901 This command allows you to send nearly any command to another DX
2902 Cluster node that is connected to the system.
2905 Whether you get any output is dependant on a) whether the other system
2906 knows that the node callsign of this cluster is in fact a node b)
2907 whether the other system is allowing RCMDs from this node and c)
2908 whether you have permission to send this command at all.
2913 read Read the next unread personal message addressed to you
2914 read <msgno> Read the specified message
2917 You can read any messages that are sent as 'non-personal' and also any
2918 message either sent by or sent to your callsign.
2922 7.53. read (extended for sysops) (5)
2924 read <msgno> Read a message on the system
2927 As a sysop you may read any message on the system
2930 7.54. reject/announce
2932 reject/announce [0-9] <pattern> Set a reject filter for announce
2935 Create an 'reject this announce' line for a filter.
2937 An reject filter line means that if the announce matches this filter
2938 it is passed onto the user. See HELP FILTERS for more info. Please
2939 read this to understand how filters work - it will save a lot of grief
2942 You can use any of the following things in this line:-
2946 info <string> eg: iota or qsl
2947 by <prefixes> eg: G,M,2
2949 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2950 origin_itu <numbers>
2951 origin_zone <numbers>
2956 wx 1 filter WX announces
2957 dest <prefixes> eg: 6MUK,WDX (distros)
2966 rej/ann by_zone 14,15,16 and not by G,M,2
2971 You can use the tag 'all' to reject everything eg:
2980 but this probably for advanced users...
2983 7.55. reject/announce (extended for sysops) (8)
2985 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
2989 This version allows a sysop to set a filter for a callsign as well as
2990 the default for nodes and users eg:-
2995 reject/ann input node_default by G,M,2
2996 reject/ann user_default by G,M,2
3002 7.56. reject/route (8)
3004 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3008 Create an 'reject this routing PC Protocol' line for a filter.
3011 An reject filter line means that if a PC16/17/19/21/24/41/50 matches
3012 this filter it is NOT passed thru that interface. See HELP FILTERING
3013 for more info. Please read this to understand how filters work - it
3014 will save a lot of grief later on. You can use any of the following
3015 things in this line:-
3019 call <prefixes> the callsign of the thingy
3020 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3023 origin <prefixes> really the interface it came in on
3024 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3025 origin_itu <numbers>
3026 origin_zone <numbers>
3037 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3043 You can use the tag 'all' to reject everything eg:
3047 rej/route all (equiv to [very] restricted mode)
3053 7.57. reject/spots (0)
3055 reject/spots [0-9] <pattern> Set a reject filter line for spots
3058 Create a 'reject this spot' line for a filter.
3060 A reject filter line means that if the spot matches this filter it is
3061 dumped (not passed on). See HELP FILTERS for more info. Please read
3062 this to understand how filters work - it will save a lot of grief
3065 You can use any of the following things in this line:-
3069 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
3070 on <range> same as 'freq'
3071 call <prefixes> eg: G,PA,HB9
3072 info <string> eg: iota or qsl
3074 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3086 For frequencies, you can use any of the band names defined in
3087 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
3088 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
3089 this is more efficient than saying simply: on HF (but don't get too
3097 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3103 You can use the tag 'all' to reject everything eg:
3112 but this probably for advanced users...
3115 7.58. reject/spots (extended for sysops) (8)
3117 reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
3121 This version allows a sysop to set a filter for a callsign as well as
3122 the default for nodes and users eg:-
3126 reject/spot db0sue-7 1 by_zone 14,15,16
3127 reject/spot node_default all
3128 set/hops node_default 10
3130 reject/spot user_default by G,M,2
3136 7.59. reject/wcy (0)
3138 reject/wcy [0-9] <pattern> Set a reject WCY filter
3141 It is unlikely that you will want to do this, but if you do then you
3142 can filter on the following fields:-
3146 by <prefixes> eg: G,M,2
3148 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3149 origin_itu <numbers>
3150 origin_zone <numbers>
3159 There are no examples because WCY Broadcasts only come from one place
3160 and you either want them or not (see UNSET/WCY if you don't want
3163 This command is really provided for future use.
3165 See HELP FILTER for information.
3169 7.60. reject/wcy (extended for sysops) (8)
3171 reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
3175 This version allows a sysop to set a filter for a callsign as well as
3176 the default for nodes and users eg:-
3178 reject/wcy gb7djk all
3181 7.61. reject/wwv (0)
3183 reject/wwv [0-9] <pattern> Set a reject WWV filter
3186 It is unlikely that you will want to do this, but if you do then you
3187 can filter on the following fields:-
3191 by <prefixes> eg: G,M,2
3193 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3194 origin_itu <numbers>
3195 origin_zone <numbers>
3208 reject/wwv by_zone 14,15,16
3213 is probably the only useful thing to do (which will only show WWV
3214 broadcasts by stations in the US).
3216 See HELP FILTER for information.
3219 7.62. reject/wwv (extended for sysops) (8)
3221 reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
3225 This version allows a sysop to set a filter for a callsign as well as
3226 the default for nodes and users eg:-
3230 reject/wwv db0sue-7 1 by_zone 4
3231 reject/wwv node_default all
3233 reject/wwv user_default by W
3237 reply Reply (privately) to the last message that you have read
3238 reply <msgno> Reply (privately) to the specified message
3239 reply B <msgno> Reply as a Bulletin to the specified message
3240 reply NOPrivate <msgno> Reply as a Bulletin to the specified message
3241 reply RR <msgno> Reply to the specified message with read receipt
3244 You can reply to a message and the subject will automatically have
3245 "Re:" inserted in front of it, if it isn't already present.
3247 You can also use all the extra qualifiers such as RR, PRIVATE,
3248 NOPRIVATE, B that you can use with the SEND command (see SEND for
3254 send <call> [<call> ...] Send a message to one or more callsigns
3255 send RR <call> Send a message and ask for a read receipt
3256 send COPY <msgno> <call> Send a copy of a message to someone
3257 send PRIVATE <call> Send a personal message
3258 send NOPRIVATE <call> Send a message to all stations
3261 All the SEND commands will create a message which will be sent either
3262 to an individual callsign or to one of the 'bulletin' addresses.
3264 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
3265 is it will mark the message as personal and send it to the cluster
3266 node that that callsign is connected to.
3268 You can have more than one callsign in all of the SEND commands.
3270 You can have multiple qualifiers so that you can have for example:-
3274 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3279 which should send a copy of message 123 to G1TLH and G0RDI and you
3280 will receive a read receipt when they have read the message.
3282 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
3283 is an alias for SEND PRIVATE
3286 7.65. set/address (0)
3288 set/address <your_address> Record your postal address
3291 Literally, record your address details on the cluster.
3294 7.66. set/announce (0)
3296 set/announce Allow announce messages
3299 Allow announce messages to arrive at your terminal.
3301 7.67. set/arcluster (5)
3303 set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
3307 Set the node_call as an AR-Cluster type node
3312 set/baddx <call> Stop words we do not wish to see in the callsign
3313 field of a dx spot being propagated
3316 Setting a word as 'baddx' will prevent spots with that word in the
3317 callsign field of a DX spot from going any further. They will not be
3318 displayed and they will not be sent onto other nodes.
3320 The word must be wriiten in full, no wild cards are allowed eg:-
3324 set/baddx FORSALE VIDEO FR0G
3329 To allow a word again, use the following command ...
3339 7.69. set/badnode (6)
3341 set/badnode <node_call> Stop spots from this node_call being
3345 Setting a callsign as a 'badnode' will prevent spots from that node
3346 going any further. They will not be displayed and they will not be
3347 sent onto other nodes.
3349 The call can be a full or partial call (or a prefix), eg:-
3358 will stop anything from K1TTT (including any SSID's)
3367 will allow spots from him again.
3369 Use with extreme care. This command may well be superceded by
3373 7.70. set/badspotter (8)
3375 set/badspotter <call> Stop spots from this callsign being propagated
3378 Setting a callsign as a 'badspotter' will prevent spots from this
3379 callsign going any further. They will not be displayed and they will
3380 not be sent onto other nodes.
3382 The call must be written in full, no wild cards are allowed eg:-
3386 set/badspotter VE2STN
3391 will stop anything from VE2STN. If you want SSIDs as well then you
3392 must enter them specifically.
3396 unset/badspotter VE2STN
3401 will allow spots from him again.
3403 Use with extreme care. This command may well be superceded by
3409 set/beep Add beeps to terminal messages
3412 Add a beep to DX and other terminal messages.
3417 set/bbs <call> [<call>..]Make <call> a BBS
3422 set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
3426 Set the node_call as a CLX type node
3431 set/debug <name> Add a debug level to the debug set
3433 You can choose to log several different levels. The levels are
3435 chan state msg cron connect
3437 You can show what levels you are logging with the show/debug command.
3439 You can remove a debug level with unset/debug <name>
3444 set/dxAllow DX messages to arrive at your terminal
3447 You can stop DX messages with the unset/dx command
3450 7.76. set/dxgrid (0)
3452 set/dxgridAllow grid squares on the end of DX messages
3455 Some logging programs do not like the additional information at the
3456 end of a DX spot. If this is the case, use the unset/dxgrid command
3457 to remove the grid squares.
3462 set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
3466 Set the node_call as a DXNet type node
3471 set/echo Make the cluster echo your input
3474 If you are connected via a telnet session, different implimentations
3475 of telnet handle echo differently depending on whether you are
3476 connected via port 23 or some other port. You can use this command to
3477 change the setting appropriately.
3479 You can remove the echo with the unset/echo command
3481 The setting is stored in your user profile.
3483 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
3488 set/here Set the here flag
3491 Let others on the cluster know you are here by only displaying your
3492 callsign. If you are away from your terminal you can use the
3493 unset/here command to let people know you are away. This simply puts
3494 brackets around your callsign to indicate you are not available.
3499 7.80. set/homenode (0)
3501 set/homenode <node_call> Set your home cluster
3504 Tell the cluster system where you normally connect to. Any Messages
3505 sent to you will normally find their way there should you not be
3518 set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
3521 Set the hop count for a particular type of broadcast for a node.
3523 This command allows you to set up special hop counts for a node for
3524 currently: announce, spots, wwv and wcy broadcasts.
3529 set/hops gb7djk ann 10
3530 set/hops gb7mbc spots 20
3535 Set SHOW/HOPS for information on what is already set. This command
3536 creates a filter and works in conjunction with the filter system.
3539 7.82. set/isolate (9)
3541 set/isolate <node call> Isolate a node from the rest of the network
3544 Connect a node to your system in such a way that you are a full
3545 protocol member of its network and can see all spots on it, but
3546 nothing either leaks out from it nor goes back into from the rest of
3547 the nodes connected to you.
3549 You can potentially connect several nodes in this way.
3551 You can see which nodes are isolated with the show/isolate (1)
3554 You can remove the isolation with the command unset/isolate.
3557 7.83. set/language (0)
3559 set/language <language> Set the language you wish to use
3562 You can select the language that you want the cluster to use.
3563 Currently the languages available are en (English) and nl (Dutch).
3565 7.84. set/location (0)
3567 set/location <lat and long> Set your latitude and longitude
3570 You can set your latitude and longitude manually or alternatively use
3571 the set/qra command which will do the conversion for you.
3575 set/location 54 04 N 2 02 E
3582 7.85. set/sys_location (9)
3584 set/sys_location <lat & long> Set your cluster latitude and longitude
3587 In order to get accurate headings and such like you must tell the
3588 system what your latitude and longitude is. If you have not yet done a
3589 SET/QRA then this command will set your QRA locator for you. For
3594 SET/LOCATION 52 22 N 0 57 E
3600 7.86. set/logininfo (0)
3602 set/logininfo Show logins and logouts of nodes and users
3605 Show users and nodes when they log in and out of the local cluster.
3606 You can stop these messages by using the unset/logininfo command.
3610 7.87. set/lockout (9)
3612 set/lockout <call> Stop a callsign connecting to the cluster
3615 You can show who is locked out with the show/lockout command. To
3616 allow the user to connect again, use the unset/lockout command.
3621 set/name <your_name> Set your name
3624 Tell the cluster what your name is, eg:-
3633 set/node <call> [<call> ...] Make the callsign an AK1A cluster
3636 Tell the system that the call(s) are to be treated as AK1A cluster and
3637 fed PC Protocol rather normal user commands.
3639 From version 1.41 you can also set the following types of cluster
3651 To see what your nodes are set to, use the show/nodes command.
3654 7.90. set/obscount (9)
3656 set/obscount <count> <node call> Set the 'pump-up' obsolescence
3660 From version 1.35 onwards neighbouring nodes are pinged at regular
3661 intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes.
3662 There is a 'pump-up' counter which is decremented on every outgoing
3663 ping and then reset to the 'obscount' value on every incoming ping.
3664 The default value of this parameter is 2.
3666 What this means is that a neighbouring node will be pinged twice at
3667 (default) 300 second intervals and if no reply has been heard just
3668 before what would be the third attempt, that node is disconnected.
3670 If a ping is heard then the obscount is reset to the full value. Using
3671 default values, if a node has not responded to a ping within 15
3672 minutes, it is disconnected.
3677 set/page <n> Set the number of lines per page
3680 Tell the system how many lines you wish on a page when the number of
3681 lines of output from a command is more than this. The default is 20.
3682 Setting it explicitly to 0 will disable paging.
3692 The setting is stored in your user profile.
3697 7.92. set/password (9)
3699 set/password <callsign> <string> Set a users password
3702 The password for a user can only be set by a full sysop. The string
3703 can contain any characters but any spaces are removed (you can type in
3704 spaces - but they won't appear in the password). You can see the
3705 result with STAT/USER. The password is the usual 30 character baycom
3709 7.93. set/pinginterval (9)
3711 set/pinginterval <time> <node call> Set the ping time to neighbouring
3715 As from version 1.35 all neighbouring nodes are pinged at regular
3716 intervals in order to determine the rolling quality of the link and,
3717 in future, to affect routing decisions. The default interval is 300
3720 You can use this command to set a different interval. Please don't.
3722 But if you do the value you enter is treated as minutes up 60 and
3723 seconds for numbers greater than that.
3725 This is used also to help determine when a link is down at the far end
3726 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
3727 for more information.
3730 7.94. set/privilege (9)
3732 set/privilege <n> <call> [<call> ...] Set the privilege level on a
3736 Set the privilege level on a callsign. The privilege levels that
3737 pertain to commands are as default:-
3742 1 - allow remote nodes normal user RCMDs
3743 5 - various privileged commands (including shutdown, but not disc-
3744 connect), the normal level for another node.
3745 8 - more privileged commands (including disconnect)
3746 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
3752 If you are a sysop and you come in as a normal user on a remote
3753 connection your privilege will automatically be set to 0.
3756 7.95. set/spider (5)
3758 set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
3763 Set the node_call as a DXSpider type node
3766 7.96. set/sys_qra (9)
3768 set/sys_qra <locator> Set your cluster QRA locator
3773 set/qra <locator> Set your QRA locator
3776 Tell the system what your QRA (or Maidenhead) locator is. If you have
3777 not done a SET/LOCATION then your latitude and longitude will be set
3778 roughly correctly (assuming your locator is correct ;-). For example:-
3790 set/qth <your QTH> Set your QTH
3793 Tell the system where your are. For example:-
3797 set/qth East Dereham, Norfolk
3805 set/talk Allow talk messages to be seen at your console
3808 Allow talk messages to arrive at your console. You can switch off
3809 talks with the unset/talk command.
3814 set/wcy Allow WCY messages to be seen at your console
3817 Allow WCY information to be seen at your console. You can switch off
3818 WCY messages with the unset/wcy command.
3823 set/wwv Allow WWV messages to be seen at your console
3826 Allow WWV information to be seen at your console. You can switch off
3827 WWV messages with the unset/wwv command.
3831 set/wx Allow WX messages to be seen at your console
3834 Allow WX information to be seen at your console. You can switch off
3835 WX messages with the unset/wx command.
3838 7.103. show/baddx (1)
3840 show/baddxShow all the bad dx calls in the system
3843 Display all the bad dx callsigns in the system, see SET/BADDX for more
3847 7.104. show/badnode (6)
3849 show/badnode Show all the bad nodes in the system
3852 Display all the bad node callsigns in the system, see SET/BADNODE for
3856 7.105. show/badspotter (1)
3858 show/badspotter Show all the bad spotters in the system
3861 Display all the bad spotter's callsigns in the system, see
3862 SET/BADSPOTTER for more information.
3865 7.106. show/configuration (0)
3867 show/configuration [<node>] Show all visible nodes and their users
3870 This command allows you to see all the users that can be seen and the
3871 nodes to which they are connected. With the optional node, you can
3872 specify a particular node to look at.
3874 This command is normally abbreviated to: sh/c
3876 BE WARNED: the list that is returned can be VERY long
3879 7.107. show/configuration/node (0)
3881 show/configuration/node Show all the nodes connected
3884 Show all the nodes connected locally and the nodes they have
3888 7.108. show/connect (1)
3890 show/connect Show all the active connections
3893 This command shows information on all the active connections known to
3894 the node. This command gives slightly more information than WHO.
3895 7.109. show/date (0)
3897 show/date [<prefix>|<callsign>] Show the local time
3900 This is very nearly the same as SHOW/TIME, the only difference the
3901 format of the date string if no arguments are given.
3903 If no prefixes or callsigns are given then this command returns the
3904 local time and UTC as the computer has it right now. If you give some
3905 prefixes then it will show UTC and UTC + the local offset (not
3906 including DST) at the prefixes or callsigns that you specify.
3909 7.110. show/debug (9)
3911 show/debug Show what levels of debug you are logging
3914 The levels can be set with set/debug
3919 show/dx [options] interrogate the spot database
3922 If you just type SHOW/DX you will get the last so many spots (sysop
3923 configurable, but usually 10).
3925 In addition you can add any number of these options in very nearly any
3926 order to the basic SHOW/DX command, they are:-
3931 on <band> - eg 160m 20m 2m 23cm 6mm
3932 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
3934 <number> - the number of spots you want
3935 <from>-<to> - <from> spot no <to> spot no in
3938 <prefix> - for a spotted callsign beginning with <prefix>
3939 *<suffix> - for a spotted callsign ending in <suffix>
3940 *<string>* - for a spotted callsign containing <string>
3942 day <number> - starting <number> days ago
3943 day <from>-<to> - <from> days <to> days ago
3945 info <text> - any spots containing <text> in the info or remarks
3947 by <call> - any spots spotted by <call> (spotter <call>
3950 qsl - this automatically looks for any qsl info on the call
3951 held in the spot database.
3953 iota [<iota>] - If the iota island number is missing it will
3954 look for the string iota and anything which looks like
3955 an iota island number. If you specify then it will look
3958 qra [<locator>] - this will look for the specific locator if
3959 you specify one or else anything that looks like a locator.
3967 SH/DX on 20m info iota
3968 SH/DX 9a on vhf day 30
3978 7.112. show/dxcc (0)
3980 show/dxcc <prefix> Interrogate the spot database by country
3983 This command takes the <prefix> (which can be a full or partial
3984 callsign if desired), looks up which internal country number it is and
3985 then displays all the spots as per SH/DX for that country.
3987 The options for SHOW/DX also apply to this command. e.g.
3993 SH/DXCC W on 20m info iota
3999 7.113. show/files (0)
4001 show/files [<filearea> [<string>]] List the contents of a filearea
4004 SHOW/FILES on its own will show you a list of the various fileareas
4005 available on the system. To see the contents of a particular file area
4015 where <filearea> is the name of the filearea you want to see the
4018 You can also use shell globbing characters like '*' and '?' in a
4019 string to see a selection of files in a filearea eg:-
4023 SH/FILES bulletins arld*
4027 See also TYPE - to see the contents of a file.
4030 7.114. show/filter (0)
4032 show/filter Show the filters you have set
4035 Show the contents of all the filters that are set by you. This command
4036 displays all the filters set - for all the various categories.
4039 7.115. show/filter (extended for sysops) (5)
4041 show/filter <callsign> Show the filters set by <callsign>
4044 A sysop can look at any filters that have been set.
4047 7.116. show/hops (8)
4049 show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
4053 This command shows the hop counts set up for a node. You can specify
4054 which category you want to see. If you leave the category out then all
4055 the categories will be listed.
4058 7.117. show/isolate (1)
4060 show/isolate Show a list of isolated nodes
4063 Show which nodes are currently set to be isolated.
4066 7.118. show/lockout (9)
4068 show/lockout Show a list of excluded callsigns
4071 Show a list of callsigns that have been excluded (locked out) of the
4072 cluster locally with the set/lockout command
4077 show/log [<callsign>] Show excerpts from the system log
4080 This command outputs a short section of the system log. On its own it
4081 will output a general logfile. With the optional callsign it will
4082 show output from the log associated with that callsign.
4085 7.120. show/moon (0)
4087 show/moon [<prefix>|<callsign>] Show moon rise and set times
4090 Show the Moon rise and set times for a (list of) prefixes or
4091 callsigns, together with the azimuth and elevation of the sun
4092 currently at those locations.
4093 If you don't specify any prefixes or callsigns, it will show the times
4094 for your QTH (assuming you have set it with either SET/LOCATION or
4095 SET/QRA), together with the current azimuth and elevation.
4097 In addition, it will show the gain or loss dB relative to the nominal
4098 distance of 385,000Km due to the ellipsoidal nature of the orbit.
4100 If all else fails it will show the Moonrise and set times for the node
4101 that you are connected to.
4116 show/muf <prefix> [<hours>][long] Show the likely propagation to
4120 This command allow you to estimate the likelihood of you contacting a
4121 station with the prefix you have specified. The output assumes a
4122 modest power of 20dBW and receiver sensitivity of -123dBm (about
4125 The result predicts the most likely operating frequencies and signal
4126 levels for high frequency (shortwave) radio propagation paths on
4127 specified days of the year and hours of the day. It is most useful for
4128 paths between 250 km and 6000 km, but can be used with reduced
4129 accuracy for paths shorter or longer than this.
4131 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
4132 used to predict the MUF given the predicted flux, day of the year,
4133 hour of the day and geographic coordinates of the transmitter and
4134 receiver. This routine is reasonably accurate for the purposes here,
4135 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
4136 than the programs used by major shortwave broadcasting organizations,
4137 such as the Voice of America.
4139 The command will display some header information detailing its
4140 assumptions, together with the locations, latitude and longitudes and
4141 bearings. It will then show UTC (UT), local time at the other end
4142 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
4143 (Zen) and the likely signal strengths. Then for each frequency for
4144 which the system thinks there is a likelihood of a circuit it prints a
4147 The value is currently a likely S meter reading based on the
4148 conventional 6dB / S point scale. If the value has a '+' appended it
4149 means that it is 1/2 an S point stronger. If the value is preceeded by
4150 an 'm' it means that there is likely to be much fading and by an 's'
4151 that the signal is likely to be noisy.
4153 By default SHOW/MUF will show the next two hours worth of data. You
4154 can specify anything up to 24 hours worth of data by appending the no
4155 of hours required after the prefix. For example:-
4168 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
4169 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
4170 Location Lat / Long Azim
4171 East Dereham, Norfolk 52 41 N 0 57 E 47
4172 United-States-W 43 0 N 87 54 W 299
4173 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
4174 18 23 11.5 -35 mS0+ mS2 S3
4175 19 0 11.2 -41 mS0+ mS2 S3
4180 indicating that you will have weak, fading circuits on top band and
4181 80m but usable signals on 40m (about S3).
4192 will get you the above display, but with the next 24 hours worth of
4203 Gives you an estimate of the long path propagation characterics. It
4204 should be noted that the figures will probably not be very useful, nor
4205 terrible accurate, but it is included for completeness.
4208 7.122. show/node (1)
4210 show/node [<node_call> ...] Show the type and version number of nodes
4213 Show the type and version (if connected) of the nodes specified on the
4214 command line. If no callsigns are specified then a sorted list of all
4215 the non-user callsigns known to the system will be displayed.
4218 7.123. show/prefix (0)
4220 show/prefix <callsign> Interrogate the prefix database
4223 This command takes the <callsign> (which can be a full or partial
4224 callsign or a prefix), looks up which internal country number it is
4225 and then displays all the relevant prefixes for that country together
4226 with the internal country no, the CQ and ITU regions.
4232 7.124. show/program (5)
4234 show/program Show the locations of all the included program modules
4237 Show the name and location where every program module was load from.
4238 This is useful for checking where you think you have loaded a .pm file
4244 show/qra <locator> [<locator>] Show the distance between locators
4245 show/qra <lat> <long> Convert latitude and longitude to a locator
4248 This is a multipurpose command that allows you either to calculate the
4249 distance and bearing between two locators or (if only one locator is
4250 given on the command line) the distance and beraing from your station
4251 to the locator. For example:-
4261 The first example will show the distance and bearing to the locator
4262 from yourself, the second example will calculate the distance and
4263 bearing from the first locator to the second. You can use 4 or 6
4266 It is also possible to convert a latitude and longitude to a locator
4267 by using this command with a latitude and longitude as an argument,
4272 SH/QRA 52 41 N 0 58 E
4280 show/qrz <callsign> Show any callbook details on a callsign
4283 This command queries the QRZ callbook server on the internet and
4284 returns any information available for that callsign. This service is
4285 provided for users of this software by http://www.qrz.com
4291 7.127. show/route (0)
4293 show/route <callsign> Show the route to <callsign>
4296 This command allows you to see to which node the callsigns specified
4297 are connected. It is a sort of inverse sh/config.
4307 7.128. show/satellite (0)
4309 show/satellite <name> [<hours> <interval>] Show satellite tracking
4313 Show the tracking data from your location to the satellite of your
4314 choice from now on for the next few hours.
4316 If you use this command without a satellite name it will display a
4317 list of all the satellites known currently to the system.
4319 If you give a name then you can obtain tracking data of all the passes
4320 that start and finish 5 degrees below the horizon. As default it will
4321 give information for the next three hours for every five minute
4324 You can alter the number of hours and the step size, within certain
4327 Each pass in a period is separated with a row of '-----' characters
4334 SH/SAT FENGYUN1 12 2
4342 show/sun [<prefix>|<callsign>] Show sun rise and set times
4345 Show the sun rise and set times for a (list of) prefixes or callsigns,
4346 together with the azimuth and elevation of the sun currently at those
4349 If you don't specify any prefixes or callsigns, it will show the times
4350 for your QTH (assuming you have set it with either SET/LOCATION or
4351 SET/QRA), together with the current azimuth and elevation.
4353 If all else fails it will show the sunrise and set times for the node
4354 that you are connected to.
4362 SH/SUN G1TLH K9CW ZS
4368 7.130. show/time (0)
4370 show/time [<prefix>|<callsign>] Show the local time
4373 If no prefixes or callsigns are given then this command returns the
4374 local time and UTC as the computer has it right now. If you give some
4375 prefixes then it will show UTC and UTC + the local offset (not
4376 including DST) at the prefixes or callsigns that you specify.
4381 show/wcy Show the last 10 WCY broadcasts
4382 show/wcy <n> Show the last <n> WCY broadcasts
4385 Display the most recent WCY information that has been received by the
4391 show/wwv Show the last 10 WWV broadcasts
4392 show/wwv <n> Show the last <n> WWV broadcasts
4395 Display the most recent WWV information that has been received by the
4402 shutdown Shutdown the cluster
4405 Shutdown the cluster and disconnect all the users. If you have Spider
4406 set to respawn in /etc/inittab it will of course restart.
4411 spoof <callsign> <command> Run commands as another user
4414 This is a very simple yet powerful command for the sysop. It allows
4415 you to issue commands as if you were a different user. This is very
4416 useful for the kind of things that users seem to always get wrong..
4417 like home_node for example.
4425 stat/db <dbname> Show the status of a database
4428 Show the internal status of a database descriptor.
4430 Depending on your privilege level you will see more or less
4431 information. This command is unlikely to be of much use to anyone
4435 7.136. stat/channel (5)
4437 stat/channel <callsign> Show the status of a channel on the cluster
4440 Show the internal status of the channel object either for the channel
4441 that you are on or else for the callsign that you asked for.
4443 Only the fields that are defined (in perl term) will be displayed.
4448 stat/msg <msgno> Show the status of a message
4451 This command shows the internal status of a message and includes
4452 information such as to whom it has been forwarded, its size, origin
4456 If no message number is given then the status of the message system is
4460 7.138. stat/route_node (5)
4462 stat/route_node <callsign> Show the data in a Route::Node object
4465 7.139. stat/route_user (5)
4467 stat/route_user <callsign> Show the data in a Route::User object
4470 7.140. stat/user (5)
4472 stat/user <callsign> Show the full status of a user
4475 Shows the full contents of a user record including all the secret
4478 Only the fields that are defined (in perl term) will be displayed.
4483 sysop Regain your privileges if you login remotely
4486 The system automatically reduces your privilege level to that of a
4487 normal user if you login in remotely. This command allows you to
4488 regain your normal privilege level. It uses the normal system: five
4489 numbers are returned that are indexes into the character array that is
4490 your assigned password (see SET/PASSWORD). The indexes start from
4493 You are expected to return a string which contains the characters
4494 required in the correct order. You may intersperse those characters
4495 with others to obscure your reply for any watchers. For example (and
4496 these values are for explanation :-):
4500 password = 012345678901234567890123456789
4511 aa2bbbb0ccc5ddd7xxx3n
4518 They will all match. If there is no password you will still be offered
4519 numbers but nothing will happen when you input a string. Any match is
4525 talk <callsign> Enter talk mode with <callsign>
4526 talk <callsign> <text> Send a text message to <callsign>
4527 talk <callsign> > <node_call> [<text>] Send a text message to
4528 <callsign> via <node_call>
4531 Send a short message to any other station that is visible on the
4532 cluster system. You can send it to anyone you can see with a
4533 SHOW/CONFIGURATION command, they don't have to be connected locally.
4535 The second form of TALK is used when other cluster nodes are connected
4536 with restricted information. This usually means that they don't send
4537 the user information usually associated with logging on and off the
4540 If you know that G3JNB is likely to be present on GB7TLH, but you can
4541 only see GB7TLH in the SH/C list but with no users, then you would use
4542 the second form of the talk message.
4544 If you want to have a ragchew with someone you can leave the text
4545 message out and the system will go into 'Talk' mode. What this means
4546 is that a short message is sent to the recipient telling them that you
4547 are in a 'Talking' frame of mind and then you just type - everything
4548 you send will go to the station that you asked for.
4550 All the usual announcements, spots and so on will still come out on
4553 If you want to do something (such as send a spot) you precede the
4554 normal command with a '/' character, eg:-
4555 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
4561 To leave talk mode type:
4573 type <filearea>/<name> Look at a file in one of the fileareas
4576 Type out the contents of a file in a filearea. So, for example, in
4577 filearea 'bulletins' you want to look at file 'arld051' you would
4582 TYPE bulletins/arld051
4587 See also SHOW/FILES to see what fileareas are available and a list of
4593 who Show who is physically connected locally
4596 This is a quick listing that shows which callsigns are connected and
4597 what sort of connection they have
4602 wx <text> Send a weather message to local users
4603 wx full <text> Send a weather message to all cluster users
4606 Weather messages can sometimes be useful if you are experiencing an
4607 extreme that may indicate enhanced conditions
4610 7.146. wx (enhanced for sysops) (5)
4612 wx sysop <text> Send a weather message to other clusters only
4615 Send a weather message only to other cluster nodes and not to general
projects / spider.git / blob