1 The DXSpider Administration Manual v1.48
2 Ian Maude, G0VGS, (ianmaude@btinternet.com)
3 Version 1.48 September 2001 revision 1.2
5 A reference for SysOps of the DXSpider DXCluster program.
6 ______________________________________________________________________
67 1. Routing and Filtering
71 1.3 The node_default 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 Hop Control on Specific Nodes
80 1.12 Isolating networks
85 2.2 Filtering words from text fields in Announce, Talk and DX spots
86 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
96 3.7 Distribution lists
103 5.1 Creating databases
104 5.2 Importing databases
105 5.3 Checking available databases
106 5.4 Looking up databases
107 5.5 Removing databases
109 6. Information, files and useful programs
113 6.3 Other text messages
116 6.6 Updating kepler data
121 8. The DXSpider command set
123 8.1 accept/announce (0)
124 8.2 accept/announce (extended for sysops) (8)
127 8.5 accept/spots (extended for sysops) (8)
129 8.7 accept/wcy (extended for sysops) (8)
131 8.9 accept/wwv (extended for sysops) (8)
133 8.11 announce full (0)
134 8.12 announce sysop (5)
147 8.25 directory (extended for sysops) (5)
151 8.29 export_users (9)
152 8.30 forward/latlong (8)
153 8.31 forward/opername (1)
160 8.38 load/aliases (9)
163 8.41 load/cmd_cache (9)
164 8.42 load/forward (9)
165 8.43 load/messages (9)
166 8.44 load/prefixes (9)
173 8.51 read (extended for sysops) (5)
175 8.53 reject/announce (extended for sysops) (8)
176 8.54 reject/route (8)
177 8.55 reject/spots (0)
178 8.56 reject/spots (extended for sysops) (8)
180 8.58 reject/wcy (extended for sysops) (8)
182 8.60 reject/wwv (extended for sysops) (8)
186 8.64 set/announce (0)
187 8.65 set/arcluster (5)
190 8.68 set/badspotter (8)
200 8.78 set/homenode (0)
203 8.81 set/language (0)
204 8.82 set/location (0)
205 8.83 set/sys_location (9)
206 8.84 set/logininfo (0)
210 8.88 set/obscount (9)
212 8.90 set/password (9)
213 8.91 set/pinginterval (9)
214 8.92 set/privilege (9)
224 8.102 show/badnode (6)
225 8.103 show/badspotter (1)
226 8.104 show/configuration (0)
227 8.105 show/configuration/node (0)
228 8.106 show/connect (1)
234 8.112 show/filter (0)
235 8.113 show/filter (extended for sysops) (5)
237 8.115 show/isolate (1)
238 8.116 show/lockout (9)
243 8.121 show/prefix (0)
244 8.122 show/program (5)
248 8.126 show/satellite (0)
256 8.134 stat/channel (5)
258 8.136 stat/route_node (5)
259 8.137 stat/route_user (5)
266 8.144 wx (enhanced for sysops) (5)
269 ______________________________________________________________________
271 1. Routing and Filtering
275 From DXSpider version 1.48, major changes were introduced to the way
276 node connections are treated. This is part of an ongoing process to
277 remove problems with loops and to enable talk and other functions to
278 propagate across the whole of the worldwide cluster network. In fact,
279 in a Spider network, it would be useful, perhaps even necessary to
280 have loops. This would give real resilience to the network, meaning
281 that if a link dropped, the information flow would simply come in and
282 go out via a different route. Of course, we do not have a complete
283 network of Spider nodes, there are other programs out there. Some of
284 these do not have any protection from loops. Certainly AK1A does not
285 handle loops well at all. It is therefore necessary to have some form
286 of protection for these nodes.
289 In fact DXSpider has had a simple system for some time which is called
290 isolation. This is similar to what in other systems such as clx, is
291 called passive mode. A more detailed explanation of isolation is given
292 further below. This system is still available and, for simple
293 networks, is probably all that you need.
296 The new functionality introduced in version 1.48 allows filtering the
297 node and user protocol frames on a "per interface" basis. We call this
298 route filtering. This is used instead of isolation.
301 What this really means is that you can control more or less completely
302 which user and node management PC protocol frames pass to each of your
303 partner nodes. You can also limit what comes into your node from your
304 partners. It is even possible to control the settings that your
305 partner node has for the routing information that it sends to you
306 (using the rcmd command).
311 Initially when route filters were being tested we generated a
312 "default" filter. Unfortunately it quickly became apparent that this
313 might suit the UK cluster network but didn't really fit anybody else.
314 However using a default filter is an appropriate thing to do. How, is
315 explained further on.
318 The first thing that you must do is determine whether you need to use
319 route filtering at all. If you are a "normal" node with two or three
320 partners and you arranged in an "official" non-looping tree type
321 network, then you do not need to do route filtering and you will feel
322 a lot better for not getting involved. If you are successfully using
323 isolation then you also probably don't need to use route filtering.
326 To put it simply, you should not mix Isolation and Route Filtering.
327 It will work, of sorts, but you will not get the expected results. If
328 you are using Isolation sucessfully at the moment, do not get involved
329 in Route Filtering unless you have a good supply of aspirin! Once you
330 have started down the road of Route Filtering, do not use Isolation
331 either. Use one or the other, not both.
334 You will only require this functionality if you are "well-connected".
335 What that means is that you are connected to several different parts
336 of (say) the EU cluster and, at the same time, also connected to two
337 or three places in the US which, in turn are connected back to the EU.
338 This is called a "loop" and if you are seriously looped then you need
342 I should at this stage give a little bit of background on filters.
343 All the filters in Spider work in basically the same way. You can
344 either accept or reject various options in order to create the filter
345 rules you wish to achieve. Some filters are user settable, others can
346 only be altered by the sysop. Route filtering can only be done by the
351 Anyway, without further discouragement, let me start the process of
355 1.3. The node_default filter
357 All normal systems should have a default routing filter and it should
358 usually be set to send only the normal, unlooped, view of your
359 "national" network. Here in the UK that means nodes from the UK and
360 Eire, in EU it is more complex as the networks there grew up in a more
365 The generic commands are:-
369 reject/route node_default <filter_option>
373 accept/route node_default <filter_option>
378 where filter_option is one of the following ...
387 channel_dxcc <numbers>
388 channel_itu <numbers>
389 channel_zone <numbers>
394 Please be careful if you alter this setting, it will affect ALL your
395 links! Remember, this is a default filter for node connections, not a
397 For the default routing filter then you have two real choices: either
398 a "national" view or the "safe" option of only your own callsign.
399 Examples of each (for my node: GB7DJK) are:-
403 acc/route node_default call_dxcc 61,38
404 acc/route node_default call gb7djk
409 GB7DJK uses the first of these. The DXCC countries can be obtained
410 from the show/prefix command.
413 The example filters shown control output TO all your partner nodes
414 unless they have a specific filter applied to them (see next section).
417 It is also possible to control the incoming routing information that
418 you are prepared to accept FROM your partner nodes. The reason this is
419 necessary is to make sure that stuff like mail, pings and similar
420 commands a) go down the correct links and b) don't loop around
421 excessively. Again using GB7DJK as an example a typical default input
422 filter would be something like:
426 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
431 What this does is accept node and user information for our national
432 network from nodes that are in our national network, but rejects such
433 information from anyone else. Although it doesn't explicitly say so,
434 by implication, any other node information (not from the UK and Eire)
438 As I imagine it will take a little while to get one's head around all
439 of this you can study the effect of any rules that you try by watching
440 the debug output after having done:-
449 After you have got tired of that, to put it back the way it was:-
459 1.4. General route filtering
461 Exactly the same rules apply for general route filtering. You would
462 use either an accept filter or a reject filter like this ...
463 reject/route <node_call> <filter_option>
467 accept/route <node_call> <filter_option>
473 Here are some examples of route filters ...
477 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
478 rej/route all (equiv to [very] restricted mode)
479 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
480 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
485 In practice you will either be opening the default filter out for a
486 partner by defining a specific filter for that callsign:-
491 acc/route gb7baa input all
496 or restricting it quite a lot, in fact making it very nearly like an
497 isolated node, like this:-
501 acc/route pi4ehv-8 call gb7djk
502 rej/route pi4ehv-8 input call_dxcc 61,38
507 This last example takes everything except UK and Eire from PI4EHV-8
508 but only sends him my local configuration (just a PC19 for GB7DJK and
509 PC16s for my local users).
512 It is possible to write much more complex rules, there are up to 10
513 accept/reject pairs per callsign per filter. For more information see
518 1.5. General filter rules
520 Upto v1.44 it was not possible for the user to set their own filters.
521 From v1.45 though that has all changed. It is now possible to set
522 filters for just about anything you wish. If you have just updated
523 from an older version of DXSpider you will need to update your new
524 filters. You do not need to do anything with your old filters, they
525 will be renamed as you update.
529 There are 3 basic commands involved in setting and manipulating
530 filters. These are accept, reject and clear. First we will look
531 generally at filtering. There are a number of things you can filter in
532 the DXSpider system. They all use the same general mechanism.
535 In general terms you can create a "reject" or an "accept" filter which
536 can have up to 10 lines in it. You do this using, for example ...
547 where ..... are the specific commands for that type of filter. There
548 are filters for spots, wwv, announce, wcy and (for sysops) connects.
549 See each different accept or reject command reference for more
552 There is also a command to clear out one or more lines in a filter.
563 There is clear/xxxx command for each type of filter.
566 and you can check that your filters have worked by the command ...
577 For now we are going to use spots for the examples, but you can apply
578 the same principles to all types of filter.
583 There are two main types of filter, accept or reject. You can use
584 either to achieve the result you want dependent on your own preference
585 and which is more simple to do. It is pointless writing 8 lines of
586 reject filters when 1 accept filter would do the same thing! Each
587 filter has 10 lines (of any length) which are tried in order. If a
588 line matches then the action you have specified is taken (ie reject
589 means ignore it and accept means take it)
592 If you specify reject filters, then any lines that arrive that match
593 the filter will be dumped but all else will be accepted. If you use
594 an accept filter, then ONLY the lines in the filter will be accepted
595 and all else will be dumped. For example if you have a single line
600 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
605 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
608 If you set a reject filter like this ...
612 reject/spots on hf/cw
617 Then you will get everything EXCEPT HF CW spots. You could make this
618 single filter even more flexible. For example, if you are interested
619 in IOTA and will work it even on CW even though normally you are not
620 interested in CW, then you could say ...
624 reject/spots on hf/cw and not info iota
629 But in that case you might only be interested in iota and say:-
633 accept/spots not on hf/cw or info iota
638 which achieves exactly the same thing. You should choose one or the
639 other until you are comfortable with the way it works. You can mix
640 them if you wish (actually you can have an accept AND a reject on the
641 same line) but don't attempt this until you are sure you know what you
645 You can arrange your filter lines into logical units, either for your
646 own understanding or simply convenience. Here is an example ...
650 reject/spots 1 on hf/cw
651 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
656 What this does is to ignore all HF CW spots and also rejects any spots
657 on VHF which don't either originate or spot someone in Europe.
661 This is an example where you would use a line number (1 and 2 in this
662 case), if you leave the digit out, the system assumes '1'. Digits
663 '0'-'9' are available. This make it easier to see just what filters
664 you have set. It also makes it more simple to remove individual
665 filters, during a contest for example.
668 You will notice in the above example that the second line has
669 brackets. Look at the line logically. You can see there are 2
670 separate sections to it. We are saying reject spots that are VHF or
671 above APART from those in zones 14, 15 and 16 (either spotted there or
672 originated there). If you did not have the brackets to separate the 2
673 sections, then Spider would read it logically from the front and see a
674 different expression entirely ...
678 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
683 The simple way to remember this is, if you use OR - use brackets.
684 Whilst we are here CASE is not important. 'And BY_Zone' is just the
685 same as 'and by_zone'.
687 As mentioned earlier, setting several filters can be more flexible
688 than simply setting one complex one. Doing it in this way means that
689 if you want to alter your filter you can just redefine or remove one
690 or more lines of it or one line. For example ...
694 reject/spots 1 on hf/ssb
699 would redefine our earlier example, or
708 To remove all the filter lines in the spot filter ...
720 You can filter in several different ways. The options are listed in
721 the various helpfiles for accept, reject and filter.
729 Sometimes all that is needed is a general rule for node connects.
730 This can be done with a node_default filter. This rule will always be
731 followed, even if the link is isolated, unless another filter is set
732 specifically. Default rules can be set for nodes and users. They can
733 be set for spots, announces, WWV and WCY. They can also be used for
734 hops. An example might look like this ...
738 accept/spot node_default by_zone 14,15,16,20,33
739 set/hops node_default spot 50
744 This filter is for spots only, you could set others for announce, WWV
745 and WCY. This filter would work for ALL nodes unless a specific
746 filter is written to override it for a particular node. You can also
747 set a user_default should you require. It is important to note that
748 default filters should be considered to be "connected". By this I
749 mean that should you override the default filter for spots, you need
750 to add a rule for the hops for spots also.
753 1.9. Advanced filtering
755 Once you are happy with the results you get, you may like to
759 The previous example that filters hf/cw spots and accepts vhf/uhf
760 spots from EU can be written with a mixed filter, for example ...
766 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
771 Note that the first filter has not been specified with a number. This
772 will automatically be assumed to be number 1. In this case, we have
773 said reject all HF spots in the CW section of the bands but accept all
774 others at HF. Also accept anything in VHF and above spotted in or by
775 operators in the zones 14, 15 and 16. Each filter slot actually has a
776 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
780 It was mentioned earlier that after a reject test that doesn't match,
781 the default for following tests is 'accept', the reverse is true for
782 'accept'. In the example what happens is that the reject is executed
783 first, any non hf/cw spot is passed to the accept line, which lets
784 through everything else on HF. The next filter line lets through just
785 VHF/UHF spots from EU.
788 1.10. Basic hop control
790 In /spider/data you will find a file called hop_table.pl. This is the
791 file that controls your hop count settings. It has a set of default
792 hops on the various PC frames and also a set for each node you want to
793 alter the hops for. You may be happy with the default settings of
794 course, but this powerful tool can help to protect and improve the
795 network. The file will look something like this ...
800 # hop table construction
805 # default hopcount to use
808 # some variable hop counts based on message type
819 # the per node hop control thingy
853 Each set of hops is contained within a pair of curly braces and
854 contains a series of PC frame types. PC11 for example is a DX spot.
855 The figures here are not exhaustive but should give you a good idea of
859 You can alter this file at any time, including whilst the cluster is
860 running. If you alter the file during runtime, the command load/hops
861 will bring your changes into effect.
864 1.11. Hop Control on Specific Nodes
866 You can set a callsign specific hop count for any of the standard
871 set/hops gb7djk spot 4
872 set/hops node_default route 10
873 set/hops gb7baa wcy 5
878 all work on their specific area of the protocol.
881 The set/hops command overrides any hops that you have set otherwise.
884 You can set what hops have been set using the show/hops command.
887 1.12. Isolating networks
889 It is possible to isolate networks from each other on a "gateway" node
890 using the set/isolate <node_call> command.
893 The effect of this is to partition an isolated network completely from
894 another node connected to your node. Your node will appear on and
895 otherwise behave normally on every network to which you are connected,
896 but data from an isolated network will not cross onto any other
897 network or vice versa. However all the spot, announce and WWV traffic
898 and personal messages will still be handled locally (because you are a
899 real node on all connected networks), that is locally connected users
900 will appear on all networks and will be able to access and receive
901 information from all networks transparently. All routed messages will
902 be sent as normal, so if a user on one network knows that you are a
903 gateway for another network, he can still still send a talk/announce
904 etc message via your node and it will be routed across.
907 If you use isolate on a node connection you will continue to receive
908 all information from the isolated partner, however you will not pass
909 any information back to the isolated node. There are times when you
910 would like to forward only spots across a link (maybe during a contest
911 for example). To do this, isolate the node in the normal way and use
912 an acc/spot >call< all filter to override the isolate.
919 In the /spider/msg directory you will find a file called
920 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
921 original looks something like this ....
925 # the list of regexes for messages that we won't store having
926 # received them (bear in mind that we must receive them fully before
930 # The format of each line is as follows
932 # type source pattern
933 # P/B/F T/F/O/S regex
935 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
936 # source: T - to field, F - from field, O - origin, S - subject
937 # pattern: a perl regex on the field requested
939 # Currently only type B and P msgs are affected by this code.
941 # The list is read from the top down, the first pattern that matches
942 # causes the action to be taken.
944 # The pattern can be undef or 0 in which case it will always be selected
945 # for the action specified
958 I think this is fairly self explanatory. It is simply a list of
959 subject headers that we do not want to pass on to either the users of
960 the cluster or the other cluster nodes that we are linked to. This is
961 usually because of rules and regulations pertaining to items for sale
962 etc in a particular country.
966 2.2. Filtering words from text fields in Announce, Talk and DX spots
968 From version 1.48 onwards the interface to this has changed. You can
969 now use the commands set/badword to add words that you are not
970 prepared to see on the cluster, unset/badword to allow that word again
971 and show/badword to list the words that you have set.
974 If you have a previous /spider/data/badwords, the first time you start
975 the node, it will read and convert this file to the new commands. The
976 old style file will then be removed.
979 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
982 There are a number of commands that control whether a spot progresses
983 any further by regarding it as "bad" in some way.
986 A DX Spot has a number of fields which can be checked to see whether
987 they contain "bad" values, they are: the DX callsign itself, the
988 Spotter and the Originating Node.
991 There are a set of commands which allow the sysop to control whether a
1003 These work in the same as the set/badword command, you can add any
1004 words or callsigns or whatever to the appropriate database. For
1005 example, to stop a spot from a particular node you do:
1009 set/badnode gb7djk gb7dxc
1018 set/badspotter b0mb p1rat nocall
1027 set/baddx video wsjt
1032 You can remove a word using the appropriate unset command
1033 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1034 of show/baddx, show/badspotter and show/badnode.
1039 DXSpider deals seamlessly with standard AK1A type mail. It supports
1040 both personal and bulletin mail and the sysop has additional commands
1041 to ensure that mail gets to where it is meant. DXSpider will send
1042 mail almost immediately, assuming that the target is on line.
1043 However, only one mail message is dealt with at any one time. If a
1044 mail message is already being sent or recieved, then the new message
1045 will be queued until it has finished.
1047 The cluster mail is automatically deleted after 30 days unless the
1048 sysop sets the "keep" flag using the msg command.
1053 Personal mail is sent using the sp command. This is actually the
1054 default method of sending mail and so a simple s for send will do. A
1055 full list of the send commands and options is in the command set
1056 section, so I will not duplicate them here.
1059 Bulletin mail is sent by using the sb command. This is one of the
1060 most common mistakes users make when sending mail. They send a
1061 bulletin mail with s or sp instead of sb and of course the message
1062 never leaves the cluster. This can be rectified by the sysop by using
1066 Bulletin addresses can be set using the Forward.pl file.
1071 DXSpider receives all and any mail sent to it without any alterations
1072 needed in files. Because personal and bulletin mail are treated
1073 differently, there is no need for a list of accepted bulletin
1074 addresses. It is necessary, however, to tell the program which links
1075 accept which bulletins. For example, it is pointless sending
1076 bulletins addresses to "UK" to any links other than UK ones. The file
1077 that does this is called forward.pl and lives in /spider/msg. At
1078 default, like other spider files it is named forward.pl.issue. Rename
1079 it to forward.pl and edit the file to match your requirements. The
1085 # this is an example message forwarding file for the system
1087 # The format of each line is as follows
1089 # type to/from/at pattern action destinations
1090 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1092 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1093 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1094 # pattern: a perl regex on the field requested
1095 # action: I - ignore, F - forward
1096 # destinations: a reference to an array containing node callsigns
1098 # if it is non-private and isn't in here then it won't get forwarded
1100 # Currently only type B msgs are affected by this code.
1102 # The list is read from the top down, the first pattern that matches
1103 # causes the action to be taken.
1105 # The pattern can be undef or 0 in which case it will always be selected
1106 # for the action specified
1108 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1109 # pattern) then it will always be forwarded to every node that doesn't have
1110 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1111 # you allow a new link with this on EVERY bull will be forwarded immediately
1112 # on first connection)
1123 Simply insert a bulletin address and state in the brackets where you
1124 wish that mail to go. For example, you can see here that mail sent to
1125 "UK" will only be sent to the UK links and not to PA4AB-14.
1128 To force the cluster to reread the file use load/forward
1132 3.4. The msg command
1134 The msg command is a very powerful and flexible tool for the sysop.
1135 It allows the sysop to alter to and from fields and make other changes
1136 to manage the cluster mail.
1138 Here is a full list of the various options ...
1142 MSG TO <msgno> <call> - change TO callsign to <call>
1143 MSG FRom <msgno> <call> - change FROM callsign to <call>
1144 MSG PRrivate <msgno> - set private flag
1145 MSG NOPRrivate <msgno> - unset private flag
1146 MSG RR <msgno> - set RR flag
1147 MSG NORR <msgno> - unset RR flag
1148 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1149 MSG NOKEep <msgno> - unset the keep flag
1150 MSG SUbject <msgno> <new> - change the subject to <new>
1151 MSG WAittime <msgno> - remove any waiting time for this message
1152 MSG NOREad <msgno> - mark message as unread
1153 MSG REad <msgno> - mark message as read
1154 MSG QUeue - queue any outstanding bulletins
1155 MSG QUeue 1 - queue any outstanding private messages
1160 These commands are simply typed from within the cluster as the sysop
1166 You can check on a message from within the cluster by using the
1167 command stat/msg. This will give you additional information on the
1168 message number including which nodes have received it, which node it
1169 was received from and when etc. Here is an example of the output of
1174 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1177 Msg Time: 26-Jan-2001 1302Z
1181 Subject: AMSAT 2line KEPS 01025.AMSAT
1183 Got it Nodes: GB7BAA, GB7ADX
1187 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1191 This is described in the section on Other filters so I will not
1195 3.7. Distribution lists
1197 Distribution lists are simply a list of users to send certain types of
1198 mail to. An example of this is mail you only wish to send to other
1199 sysops. In /spider/msg there is a directory called distro. You put
1200 any distibution lists in here. For example, here is a file called
1201 SYSOP.pl that caters for the UK sysops.
1205 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1206 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1207 GB7DXK GB7DXI GB7DXS)
1212 Any mail sent to "sysop" would only be sent to the callsigns in this
1218 Spider provides a simple BBS interface. No input is required from the
1219 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1220 and pushes any required mail to the cluster. No mail can flow from
1221 Spider to the BBS, the interface is one-way.
1224 Please be careful not to flood the cluster network with unnecessary
1225 mail. Make sure you only send mail to the clusters that want it by
1226 using the Forward.pl file very carefully.
1231 From 1.48 onwards it will become increasingly possible to control
1232 DXSpider's operation with scripts of various kinds.
1235 In the first instance, in 1.48, the sysop can create, with their
1236 favorite text editor, files in the directory /spider/scripts which
1237 contain any legal command for a callsign or class of connection which
1238 will be executed at logon.
1242 The filename is the callsign of the connection that you want the
1243 script to operate on, eg: /spider/scripts/g1tlh. The filenames are
1244 always in lower case on those architectures where this makes a
1248 In addition to the callsign specific scripts there are three others:-
1262 The startup script is executed immediately after all initialisation of
1263 the node is done, but before any connections are possible.
1266 The user_default script is executed for every user that does NOT
1267 already have a specific script.
1270 The node_default script is executed for every node that doesn't have a
1274 There are a couple of examples in the /spider/scripts directory.
1279 Spider allows the creation of local or remote databases. It supports
1280 chained databases, allowing several different databases to be scanned
1281 with one simple command. Importing of databases is limited at present
1282 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1283 database but will expand with time.
1286 5.1. Creating databases
1288 Creating a database could not be more simple. All the commands are
1289 sent from the cluster prompt as the sysop user.
1291 To create a database you use the command dbcreate. It can be used in
1292 3 different ways like so ..
1301 To simply create a database locally, you just tell the command the
1302 name of the database. This does not create the actual database, it
1303 simply defines it to say that it exists.
1307 dbcreate <name> chain <name> [<name>...]
1312 This creates a chained database entry. The first database will be
1313 scanned, then the second, the third etc...
1317 dbcreate <name> remote <name>
1321 This creates a remote entry. the first name field is the database
1322 name at the remote node, then the remote switch, then the actual
1323 node_call of the remote node, for example...
1327 dbcreate buckmaster remote gb7dxc
1332 Remote databases cannot be chained, however, the last database in a
1333 chain can be a remote database.
1336 5.2. Importing databases
1338 The only databases that Spider can currently import are the standard
1339 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1340 This will be added to with time.
1342 To import such a database, first put the file somewhere useful like
1343 /tmp and then issue the following command ...
1347 dbimport oblast /tmp/OBLAST.FUL
1352 This will update the existing local oblast database or create it if it
1356 5.3. Checking available databases
1358 Once a database is created, you will want to check that it has been
1359 added. To do this use the dbavail command. This will output the
1360 available databases. For example ...
1365 DB Name Location Chain
1369 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1375 5.4. Looking up databases
1377 To look for information in a defined database, simply use the dbshow
1378 command, for example ...
1382 dbshow buckmaster G0YLM
1387 will show the information for the callsign G0YLM from the buckmaster
1388 database if it exists. To make things more standard for the users you
1389 can add an entry in the Aliases file so that it looks like a standard
1390 show command like this ...
1398 Now you can simply use show/buckmaster or an abreviation.
1401 5.5. Removing databases
1403 To delete an existing database you use the dbremove command. For
1413 would remove the oblast database and its associated datafile from the
1414 system. There are no warnings or recovery possible from this command.
1415 If you remove a database it ceases to exist and would have to be
1416 created from scratch if you still required it.
1419 6. Information, files and useful programs
1423 One of the more important things a cluster sysop needs to do is to get
1424 information to his users. The simplest way to do this is to have a
1425 banner that is sent to the user on login. This is know as a "message
1426 of the day" or "motd". To set this up, simply create a file in
1427 /spider/data called motd and edit it to say whatever you want. It is
1428 purely a text file and will be sent automatically to anyone logging in
1432 6.2. Downtime message
1434 If for any reason the cluster is down, maybe for upgrade or
1435 maintenance but the machine is still running, a message can be sent to
1436 the user advising them of the fact. This message lives in the
1437 /spider/data directory and is called "offline". Simply create the
1438 file and edit it to say whatever you wish. This file will be sent to
1439 a user attempting to log into the cluster when DXSpider is not
1443 6.3. Other text messages
1445 You can set other text messages to be read by the user if they input
1446 the file name. This could be for news items or maybe information for
1447 new users. To set this up, make a directory under /spider called
1448 packclus. Under this directory you can create files called news or
1449 newuser for example. In fact you can create files with any names you
1450 like. These can be listed by the user with the command ....
1458 They can be read by the user by typing the command ....
1467 If the file they want to read is called news. You could also set an
1468 alias for this in the Alias file to allow them just to type news
1471 You can also store other information in this directory, either
1472 directly or nested under directories. One use for this would be to
1473 store DX bulletins such as the OPDX bulletins. These can be listed
1474 and read by the user. To keep things tidy, make a directory under
1475 /spider/packclus called bulletin. Now copy any OPDX or similar
1476 bulletins into it. These can be listed by the user in the same way as
1477 above using the show/files command with an extension for the bulletin
1478 directory you have just created, like this ....
1488 An example would look like this ....
1493 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1498 You can see that in the files area (basically the packclus directory)
1499 there is a file called news and a directory called bulletin. You can
1500 also see that dates they were created. In the case of the file news,
1501 you can also see the time it was last modified, a good clue as to
1502 whether the file has been updated since you last read it. To read the
1503 file called news you would simply issue the command ....
1512 To look what is in the bulletin directory you issue the command ....
1520 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1521 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1522 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1523 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1524 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1525 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1526 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1527 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1528 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1529 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1530 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1531 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1532 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1533 Press Enter to continue, A to abort (16 lines) >
1538 You can now read any file in this directory using the type command,
1543 type bulletin/opdx391
1544 Ohio/Penn DX Bulletin No. 391
1545 The Ohio/Penn Dx PacketCluster
1549 Editor Tedd Mirgliotta, KB8NW
1550 Provided by BARF-80 BBS Cleveland, Ohio
1551 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1552 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1553 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1554 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1555 Press Enter to continue, A to abort (508 lines) >
1560 The page length will of course depend on what you have it set to!
1563 6.4. The Aliases file
1565 You will find a file in /spider/cmd/ called Aliases. First, copy this
1566 file to /spider/local_cmd/Aliases and edit this file. You will see
1567 something like this ...
1587 # provide some standard aliases for commands for terminally
1588 # helpless ak1a user (helpless in the sense that they never
1589 # read nor understand help files)
1591 # This file is automagically reloaded if its modification time is
1592 # later than the one stored in CmdAlias.pm
1594 # PLEASE make this file consistant with reality! (the patterns MUST
1595 # match the filenames!)
1597 # Don't alter this file, copy it into the local_cmd tree and modify it.
1598 # This file will be replaced everytime I issue a new release.
1600 # You only need to put aliases in here for commands that don't work as
1601 # you desire naturally, e.g sh/dx on its own just works as you expect
1602 # so you need not add it as an alias.
1610 '^\?', 'apropos', 'apropos',
1613 '^ann.*/full', 'announce full', 'announce',
1614 '^ann.*/sysop', 'announce sysop', 'announce',
1615 '^ann.*/(.*)$', 'announce $1', 'announce',
1622 '^del', 'kill', 'kill',
1623 '^del\w*/fu', 'kill full', 'kill',
1624 '^di\w*/a\w*', 'directory all', 'directory',
1625 '^di\w*/b\w*', 'directory bulletins', 'directory',
1626 '^di\w*/n\w*', 'directory new', 'directory',
1627 '^di\w*/o\w*', 'directory own', 'directory',
1628 '^di\w*/s\w*', 'directory subject', 'directory',
1629 '^di\w*/t\w*', 'directory to', 'directory',
1630 '^di\w*/f\w*', 'directory from', 'directory',
1631 '^di\w*/(\d+)', 'directory $1', 'directory',
1648 '^l$', 'directory', 'directory',
1649 '^ll$', 'directory', 'directory',
1650 '^ll/(\d+)', 'directory $1', 'directory',
1655 '^news', 'type news', 'type',
1665 '^r$', 'read', 'read',
1666 '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
1669 '^s/p$', 'send', 'send',
1670 '^sb$', 'send noprivate', 'send',
1671 '^set/home$', 'set/homenode', 'set/homenode',
1672 '^set/nobe', 'unset/beep', 'unset/beep',
1673 '^set/nohe', 'unset/here', 'unset/here',
1674 '^set/noan', 'unset/announce', 'unset/announce',
1675 '^set/nodx', 'unset/dx', 'unset/dx',
1676 '^set/nota', 'unset/talk', 'unset/talk',
1677 '^set/noww', 'unset/wwv', 'unset/wwv',
1678 '^set/nowx', 'unset/wx', 'unset/wx',
1679 '^sh$', 'show', 'show',
1680 '^sh\w*/buck', 'dbshow buck', 'dbshow',
1681 '^sh\w*/bu', 'show/files bulletins', 'show/files',
1682 '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
1683 '^sh\w*/c$', 'show/configuration', 'show/configuration',
1684 '^sh\w*/com', 'dbavail', 'dbavail',
1685 '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
1686 '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
1687 '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
1688 '^sh\w*/email', 'dbshow email', 'dbshow',
1689 '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
1690 '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
1691 '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
1692 '^sh\w*/tnc', 'who', 'who',
1693 '^sh\w*/up', 'show/cluster', 'show/cluster',
1694 '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
1695 '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
1696 '^sp$', 'send', 'send',
1700 '^ta$', 'talk', 'talk',
1701 '^t$', 'talk', 'talk',
1708 '^wx/full', 'wx full', 'wx',
1709 '^wx/sysop', 'wx sysop', 'wx',
1722 You can create aliases for commands at will. Beware though, these may
1723 not always turn out as you think. Care is needed and you need to test
1724 the results once you have set an alias.
1729 In later versions of Spider a simple console program is provided for
1730 the sysop. This has a type ahead buffer with line editing facilities
1731 and colour for spots, announces etc. To use this program, simply use
1732 console.pl instead of client.
1735 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1736 edit the file with your favourite editor.
1739 6.6. Updating kepler data
1741 Spider has a powerful and flexible show/satellite command. In order
1742 for this to be accurate, the kepler data has to be updated regularly.
1743 In general, this data is available as an email or via cluster mail.
1744 Updating it is simple. First you need to export the mail message as a
1745 file. You do this with the export command from the cluster prompt as
1746 the sysop. For example ...
1750 export 5467 /spider/perl/keps.in
1755 would export message number 5467 as a file called keps.in in the
1756 /spider/perl directory.
1758 Now login to a VT as sysop and cd /spider/perl. There is a command in
1759 the perl directory called convkeps.pl. All we need to do now is
1760 convert the file like so ...
1764 ./convkeps.pl keps.in
1769 Now go back to the cluster and issue the command ...
1778 That is it! the kepler data has been updated.
1783 6.7. The QRZ callbook
1785 The command sh/qrz will only work once you have followed a few simple
1786 steps. First you need to get a user ID and password from qrz.com.
1787 Simply go to the site and create one. Secondly you need to copy the
1788 file /spider/perl/Internet.pm to /spider/local and alter it to match
1789 your user ID and password. You also at this point need to set
1790 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1791 proprieter of qrz.com for allowing this access.
1796 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
1797 is held at Sourceforge. This means that it is possible to update your
1798 DXSpider installation to the latest sources by using a few simple
1802 Please be aware that if you update your system using CVS, it is
1803 possible that you could be running code that is very beta and not
1804 fully tested. There is a possibility that it could be unstable.
1807 I am of course assuming that you have a machine with both DXSpider and
1808 Internet access running.
1811 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
1812 ENTIRE SPIDER TREE!!
1815 Assuming you are connected to the Internet, you need to login to the
1816 CVS repository and then update your Spider source. There are several
1817 steps which are listed below ...
1820 First login as the user sysop. Next you need to connect to the CVS
1821 repository. You do this with the command below ...
1824 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
1828 You will get a password prompt. Simply hit return here and your
1829 machine should return to a normal linux prompt.
1832 What happens next depends on whether you have an existing installation
1833 that you want to update with the latest and greatest or whether you
1834 just want to see what is there and/or run it on a new machine for
1837 If you are installing Spider from CVS then change directory to
1840 If you are wanting to update Spider then cd to /tmp
1843 The next step will create a brand new 'spider' directory in your
1847 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
1849 This command is all on one line.
1852 Hopefully your screen should show you downloading files. The -z3
1853 simply compresses the download to improve speed. When this has
1854 finished, you will have exactly the same as if you had untarred a full
1855 tarball PLUS some extra directories and files that CVS needs to do the
1859 Now if you are doing a new installation, that's it. Carry on as if
1860 you have just downloaded and untarred the lastest tarball.
1863 If you want to upgrade your current installation then do this ...
1867 tar cvfz /tmp/s.tgz spider
1869 tar xvfzp /tmp/s.tgz
1874 This is assuming you downloaded to the /tmp directory of course.
1877 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
1878 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
1881 Remember to recompile the C client (cd /spider/src; make)
1884 At this point the files have been upgraded. You can (usually) restart
1885 the cluster in your own time. However, if you attempt to use any new
1886 commands or features expect it to be fatal! At least your cluster
1887 will have been restarted then so it will be too late to worry about
1891 Now the magic part! From now on when you want to update, simply
1892 connect to the Internet and then, as the user sysop ...
1902 and your files will be updated. As above, remember to recompile the
1903 "C" client if it has been updated (CVS will tell you) and restart if
1904 any of the perl scripts have been altered or added, again, CVS will
1908 You will find any changes documented in the /spider/Changes file.
1911 8. The DXSpider command set
1913 Below is a complete list of commands available from the cluster
1914 prompt. Most maintenance tasks are automatic but there are some
1915 commands that are useful for a sysop. These are listed below in
1916 alphabetical order. The number in brackets following the command name
1917 is the permissions level needed to use the command.
1920 8.1. accept/announce (0)
1922 accept/announce [0-9] <pattern> Set an accept filter line for announce
1925 Create an 'accept this announce' line for a filter.
1927 An accept filter line means that if the announce matches this filter
1928 it is passed onto the user. See HELP FILTERS for more info. Please
1929 read this to understand how filters work - it will save a lot of grief
1932 You can use any of the following things in this line:-
1936 info <string> eg: iota or qsl
1937 by <prefixes> eg: G,M,2
1939 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1940 origin_itu <numbers>
1941 origin_zone <numbers>
1946 wx 1 filter WX announces
1947 dest <prefixes> eg: 6MUK,WDX (distros)
1957 acc/ann 2 by_zone 14,15,16
1958 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1972 This filter would only allow announces that were posted buy UK
1973 stations. You can use the tag 'all' to accept everything eg:
1981 but this probably for advanced users...
1984 8.2. accept/announce (extended for sysops) (8)
1986 accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
1990 This version allows a sysop to set a filter for a callsign as well as
1991 the default for nodes and users eg:-
1996 accept/ann input node_default by G,M,2
1997 accept/ann user_default by G,M,2
2003 8.3. accept/route (8)
2005 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2009 Create an 'accept this routing PC Protocol' line for a filter.
2012 An accept filter line means that if a PC16/17/19/21/24/41/50 matches
2013 this filter it is passed thru that interface. See HELP FILTERING for
2014 more info. Please read this to understand how filters work - it will
2015 save a lot of grief later on.
2018 You can use any of the following things in this line:-
2022 call <prefixes> the callsign of the thingy
2023 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2026 origin <prefixes> really the interface it came in on
2027 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2028 origin_itu <numbers>
2029 origin_zone <numbers>
2039 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
2040 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2047 You can use the tag 'all' to accept everything eg:
2057 8.4. accept/spots (0)
2059 accept/announce [0-9] <pattern> Set an accept filter line for spots
2062 Create an 'accept this spot' line for a filter.
2065 An accept filter line means that if the spot matches this filter it is
2066 passed onto the user. See HELP FILTERS for more info. Please read this
2067 to understand how filters work - it will save a lot of grief later on.
2069 You can use any of the following things in this line:-
2073 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2074 on <range> same as 'freq'
2075 call <prefixes> eg: G,PA,HB9
2076 info <string> eg: iota or qsl
2078 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2091 For frequencies, you can use any of the band names defined in
2092 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2093 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2094 this is more efficient than saying simply: freq HF (but don't get too
2102 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2107 You can use the tag 'all' to accept everything, eg:
2113 but this probably for advanced users...
2116 8.5. accept/spots (extended for sysops) (8)
2118 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2121 This version allows a sysop to set a filter for a callsign as well as
2122 the default for nodes and users eg:-
2126 accept/spot db0sue-7 1 by_zone 14,15,16
2127 accept/spot node_default all
2128 set/hops node_default 10
2130 accept/spot user_default by G,M,2
2138 accept/wcy [0-9] <pattern> set an accept WCY filter
2141 It is unlikely that you will want to do this, but if you do then you
2142 can filter on the following fields:-
2146 by <prefixes> eg: G,M,2
2148 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2149 origin_itu <numbers>
2150 origin_zone <numbers>
2160 There are no examples because WCY Broadcasts only come from one place
2161 and you either want them or not (see UNSET/WCY if you don't want
2164 This command is really provided for future use.
2166 See HELP FILTER for information.
2169 8.7. accept/wcy (extended for sysops) (8)
2171 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2174 This version allows a sysop to set a filter for a callsign as well as
2175 the default for nodes and users eg:-
2179 accept/wcy node_default all
2180 set/hops node_default 10
2188 accept/wwv [0-9] <pattern> Set an accept WWV filter
2191 It is unlikely that you will want to do this, but if you do then you
2192 can filter on the following fields:-
2196 by <prefixes> eg: G,M,2
2198 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2199 origin_itu <numbers>
2200 origin_zone <numbers>
2213 accept/wwv by_zone 4
2218 is probably the only useful thing to do (which will only show WWV
2219 broadcasts by stations in the US).
2221 See HELP FILTER for information.
2224 8.9. accept/wwv (extended for sysops) (8)
2226 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2229 This version allows a sysop to set a filter for a callsign as well as
2230 the default for nodes and users eg:-
2234 accept/wwv db0sue-7 1 by_zone 4
2235 accept/wwv node_default all
2236 set/hops node_default 10
2238 accept/wwv user_default by W,K
2247 announce <text> Send an announcement to local users
2250 Send an announcement to LOCAL users only, where <text> is the text of
2251 the announcement you wish to broadcast. If you do not wish to receive
2252 announces, use the set/noannounce command. Any announces made by a
2253 sysop will override set/noannounce.
2256 8.11. announce full (0)
2258 announce full <text> Send an announcement cluster wide
2261 This command will send your announcement across the whole cluster
2266 8.12. announce sysop (5)
2268 announce sysop <text>
2271 Send an announcement to Sysops only
2276 apropos <string> Search the help database
2279 Search the help database for <string> (it isn't case sensitive), and
2280 print the names of all the commands that may be relevant.
2285 bye Exit from the cluster
2288 This will disconnect you from the cluster
2293 catchup <node_call> All|[<msgno> ...] Mark a message as sent
2296 When you send messages the fact that you have forwarded it to another
2297 node is remembered so that it isn't sent again. When you have a new
2298 partner node and you add their callsign to your /spider/msg/forward.pl
2299 file, all outstanding non-private messages will be forwarded to them.
2300 This may well be ALL the non-private messages. You can prevent this by
2301 using these commmands:-
2306 catchup GB7DJK 300 301 302 303 500-510
2311 and to undo what you have just done:-
2315 uncatchup GB7DJK all
2316 uncatchup GB7DJK 300 301 302 303 500-510
2321 which will arrange for them to be forward candidates again.
2323 Order is not important.
2326 8.16. clear/spots (0)
2328 clear/spots [1|all] Clear a spot filter line
2331 This command allows you to clear (remove) a line in a spot filter or
2332 to remove the whole filter.
2334 If you have a filter:-
2339 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2353 you will be left with:-
2357 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2371 the filter will be completely removed.
2379 connect <callsign> Start a connection to another DX Cluster
2382 Start a connection process that will culminate in a new connection to
2383 the DX cluster <callsign>. This process creates a new 'client' process
2384 which will use the script in /spider/connect/<callsign> to effect the
2385 'chat' exchange necessary to traverse the network(s) to logon to the
2391 dbavail Show a list of all the databases in the system
2394 The title says it all really, this command lists all the databases
2395 defined in the system. It is also aliased to SHOW/COMMAND.
2400 dbcreate <name> Create a database entry
2401 dbcreate <name> chain <name> [<name>..] Create a chained database
2403 dbcreate <name> remote <node> Create a remote database entry
2406 DBCREATE allows you to define a database in the system. It doesn't
2407 actually create anything, just defines it.
2409 The databases that are created are simple DB_File hash databases, they
2410 are therefore already 'indexed'.
2412 You can define a local database with the first form of the command eg:
2416 You can also chain databases with the addition of the 'chain' keyword.
2417 This will search each database one after the other. A typical example
2420 DBCREATE sdx_qsl chain sql_ad
2422 No checking is done to see if the any of the chained databases exist,
2423 in fact it is usually better to do the above statement first then do
2424 each of the chained databases.
2426 Databases can exist offsite. To define a database that lives on
2429 DBCREATE buckmaster remote gb7dxc
2431 Remote databases cannot be chained; however, the last database in a a
2432 chain can be a remote database eg:
2434 DBCREATE qsl chain gb7dxc
2436 To see what databases have been defined do:
2438 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2440 It would be normal for you to add an entry into your local Aliases
2441 file to allow people to use the 'SHOW/<dbname>' style syntax. So you
2442 would need to add a line like:-
2446 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
2458 to work as they may be used to.
2460 See DBIMPORT for the importing of existing AK1A format data to
2461 databases. See DBSHOW for generic database enquiry
2466 dbimport <dbname> Import AK1A data into a database
2469 If you want to import or update data in bulk to a database you can use
2470 this command. It will either create or update entries into an existing
2471 database. For example:-
2473 DBIMPORT oblast /tmp/OBLAST.FUL
2475 will import the standard OBLAST database that comes with AK1A into the
2476 oblast database held locally.
2481 dbremove <dbname> Delete a database
2484 DBREMOVE will completely remove a database entry and also delete any
2485 data file that is associated with it.
2487 There is no warning, no comeback, no safety net.
2493 will remove the oblast database from the system and it will also
2494 remove the associated datafile.
2498 There is no warning, no comeback, no safety net.
2500 You have been warned.
2505 dbshow <dbname> <key> Display an entry, if it exists, in a database
2509 This is the generic user interface to the database to the database
2510 system. It is expected that the sysop will add an entry to the local
2511 Aliases file so that users can use the more familiar AK1A style of
2521 but if he hasn't and the database really does exist (use DBAVAIL or
2522 SHOW/COMMAND to find out) you can do the same thing with:
2535 debug Set the cluster program into debug mode
2538 Executing this command will only have an effect if you are running the
2539 cluster in debug mode i.e.
2548 It will interrupt the cluster just after the debug command has
2554 directory List messages
2555 directory own List your own messages
2556 directory new List all new messages
2557 directory to <call> List all messages to <call>
2558 directory from <call> List all messages from <call>
2559 directory subject <string> List all messages with <string> in subject
2560 directory <nn> List last <nn> messages
2561 directory <from>-<to> List messages <from> message <to> message
2564 List the messages in the messages directory.
2566 If there is a 'p' one space after the message number then it is a
2567 personal message. If there is a '-' between the message number and the
2569 You can use shell escape characters such as '*' and '?' in the <call>
2572 You can combine some of the various directory commands together eg:-
2577 DIR SUBJECT IOTA 200-250
2582 You can abbreviate all the commands to one letter and use ak1a
2595 8.25. directory (extended for sysops) (5)
2597 Works just like the user command except that sysops can see ALL
2601 8.26. disconnect (8)
2603 disconnect <call> [<call> ...] Disconnect a user or node
2606 Disconnect any <call> connected locally
2611 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2614 This is how you send a DX Spot to other users. You can, in fact, now
2615 enter the <freq> and the <call> either way round.
2626 will all give the same result. You can add some remarks to the end of
2627 the command and they will be added to the spot.
2631 DX FR0G 144600 this is a test
2636 You can credit someone else by saying:-
2641 DX by G1TLH FR0G 144.600 he isn't on the cluster
2646 The <freq> is compared against the available bands set up in the
2647 cluster. See SHOW/BANDS for more information.
2652 export <msgno> <filename> Export a message to a file
2655 Export a message to a file. This command can only be executed on a
2656 local console with a fully privileged user. The file produced will be
2657 in a form ready to be imported back into the cluster by placing it in
2658 the import directory (/spider/msg/import).
2660 This command cannot overwrite an existing file. This is to provide
2661 some measure of security. Any files written will owned by the same
2662 user as the main cluster, otherwise you can put the new files anywhere
2663 the cluster can access. For example:-
2668 8.29. export_users (9)
2670 export_users [<filename>] Export the users database to ascii
2673 Export the users database to a file in ascii format. If no filename is
2674 given then it will export the file to /spider/data/user_asc.
2676 If the file already exists it will be renamed to <filename>.o. In fact
2677 up to 5 generations of the file can be kept each one with an extra 'o'
2680 BE WARNED: this will write to any file you have write access to. No
2681 check is made on the filename (if any) that you specify.
2684 8.30. forward/latlong (8)
2686 forward/latlong <node_call> Send latitude and longitude information to
2690 This command sends all the latitude and longitude information that
2691 your cluster is holding against callsigns. One advantage of recieving
2692 this information is that more locator information is held by you.
2693 This means that more locators are given on the DX line assuming you
2694 have set/dxgrid enabled. This could be a LOT of information though,
2695 so it is not recommended on slow links.
2698 8.31. forward/opername (1)
2700 forward/opername <call> Send out information on this <call> to all
2704 This command sends out any information held in the user file which can
2705 be broadcast in PC41 protocol packets. This information is Name, QTH,
2706 Location and Homenode. PC41s are only sent for the information that is
2712 help <cmd> Get help on a command
2715 All commands can be abbreviated, so SHOW/DX can be abbreviated to
2716 SH/DX, ANNOUNCE can be shortened to AN and so on.
2718 Look at the APROPOS <string> command which will search the help
2719 database for the <string> you specify and give you a list of likely
2720 commands to look at with HELP.
2725 init <node call> Re-initialise a link to an AK1A compatible node
2728 This command attempts to re-initialise a link to a (usually) AK1A node
2729 that has got confused, usually by a protocol loop of some kind. It may
2730 work - but you usually will be better off simply disconnecting it (or
2731 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
2734 Best of luck - you will need it.
2739 kill <msgno> [<msgno> ..] Delete a message from the local system
2742 Delete a message from the local system. You will only be able to
2743 delete messages that you have originated or been sent (unless you are
2749 kill <msgno> [<msgno> ...] Remove or erase a message from the system
2750 kill from <call> Remove all messages from a callsign
2751 kill to <call> Remove all messages to a callsign
2754 You can get rid of any message to or originating from your callsign
2755 using this command. You can remove more than one message at a time.
2757 As a sysop you can kill any message on the system.
2762 kill full <msgno> [<msgno>] Delete a message from the whole cluster
2765 Delete a message (usually a 'bulletin') from the whole cluster system.
2767 This uses the subject field, so any messages that have exactly the
2768 same subject will be deleted. Beware!
2775 links Show which nodes are physically connected
2778 This is a quick listing that shows which links are connected and some
2779 information about them. See WHO for a list of all connections.
2783 8.38. load/aliases (9)
2785 load/aliases Reload the command alias table
2788 Reload the /spider/cmd/Aliases file after you have editted it. You
2789 will need to do this if you change this file whilst the cluster is
2790 running in order for the changes to take effect.
2793 8.39. load/badmsg (9)
2795 load/badmsg Reload the bad message table
2798 Reload the /spider/msg/badmsg.pl file if you have changed it manually
2799 whilst the cluster is running. This table contains a number of perl
2800 regular expressions which are searched for in the fields targetted of
2801 each message. If any of them match then that message is immediately
2805 8.40. load/bands (9)
2807 load/bands Reload the band limits table
2810 Reload the /spider/data/bands.pl file if you have changed it manually
2811 whilst the cluster is running.
2814 8.41. load/cmd_cache (9)
2816 load/cmd_cache Reload the automatic command cache
2819 Normally, if you change a command file in the cmd or local_cmd tree it
2820 will automatially be picked up by the cluster program. Sometimes it
2821 can get confused if you are doing a lot of moving commands about or
2822 delete a command in the local_cmd tree and want to use the normal one
2823 again. Execute this command to reset everything back to the state it
2824 was just after a cluster restart.
2827 8.42. load/forward (9)
2829 load/forward Reload the msg forwarding routing table
2831 Reload the /spider/msg/forward.pl file if you have changed it manually
2832 whilst the cluster is running.
2835 8.43. load/messages (9)
2837 load/messages Reload the system messages file
2839 If you change the /spider/perl/Messages file (usually whilst
2840 fiddling/writing ne commands) you can have them take effect during a
2841 cluster session by executing this command. You need to do this if get
2844 unknown message 'xxxx' in lang 'en'
2847 8.44. load/prefixes (9)
2849 load/prefixes Reload the prefix table
2852 Reload the /spider/data/prefix_data.pl file if you have changed it
2853 manually whilst the cluster is running.
2858 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
2861 MERGE allows you to bring your spot and wwv database up to date. By
2862 default it will request the last 10 spots and 5 WWVs from the node you
2863 select. The node must be connected locally.
2865 You can request any number of spots or wwv and although they will be
2866 appended to your databases they will not duplicate any that have
2867 recently been added (the last 2 days for spots and last month for WWV
2873 msg <cmd> <msgno> [data ...] Alter various message parameters
2876 Alter message parameters like To, From, Subject, whether private or
2877 bulletin or return receipt (RR) is required or whether to keep this
2878 message from timing out.
2882 MSG TO <msgno> <call> - change TO callsign to <call>
2883 MSG FRom <msgno> <call> - change FROM callsign to <call>
2884 MSG PRrivate <msgno> - set private flag
2885 MSG NOPRrivate <msgno> - unset private flag
2886 MSG RR <msgno> - set RR flag
2887 MSG NORR <msgno> - unset RR flag
2888 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
2889 MSG NOKEep <msgno> - unset the keep flag
2890 MSG SUbject <msgno> <new> - change the subject to <new>
2891 MSG WAittime <msgno> - remove any waitting time for this message
2892 MSG NOREad <msgno> - mark message as unread
2893 MSG REad <msgno> - mark message as read
2894 MSG QUeue - queue any outstanding bulletins
2895 MSG QUeue 1 - queue any outstanding private messages
2900 You can look at the status of a message by using:-
2905 This will display more information on the message than DIR does.
2910 pc <call> <text> Send text (eg PC Protocol) to <call>
2913 Send some arbitrary text to a locally connected callsign. No
2914 processing is done on the text. This command allows you to send PC
2915 Protocol to unstick things if problems arise (messages get stuck etc).
2918 pc gb7djk PC33^GB7TLH^GB7DJK^400^
2920 You can also use in the same way as a talk command to a connected user
2921 but without any processing, added of "from <blah> to <blah>" or
2924 pc G1TLH Try doing that properly!!!
2929 ping <node> Check the link quality between nodes
2932 his command allows you to send a frame to another cluster node on the
2933 network and get a return frame. The time it takes to do this is a
2934 good indication of the quality of the link. The actual time it takes
2935 is output to the console in seconds. Any visible cluster node can be
2942 rcmd <node call> <cmd> Send a command to another DX cluster
2945 This command allows you to send nearly any command to another DX
2946 Cluster node that is connected to the system.
2948 Whether you get any output is dependant on a) whether the other system
2949 knows that the node callsign of this cluster is in fact a node b)
2950 whether the other system is allowing RCMDs from this node and c)
2951 whether you have permission to send this command at all.
2956 read Read the next unread personal message addressed to you
2957 read <msgno> Read the specified message
2960 You can read any messages that are sent as 'non-personal' and also any
2961 message either sent by or sent to your callsign.
2965 8.51. read (extended for sysops) (5)
2967 read <msgno> Read a message on the system
2971 As a sysop you may read any message on the system
2974 8.52. reject/announce
2976 reject/announce [0-9] <pattern> Set a reject filter for announce
2979 Create an 'reject this announce' line for a filter.
2981 An reject filter line means that if the announce matches this filter
2982 it is passed onto the user. See HELP FILTERS for more info. Please
2983 read this to understand how filters work - it will save a lot of grief
2986 You can use any of the following things in this line:-
2990 info <string> eg: iota or qsl
2991 by <prefixes> eg: G,M,2
2993 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
2994 origin_itu <numbers>
2995 origin_zone <numbers>
3000 wx 1 filter WX announces
3001 dest <prefixes> eg: 6MUK,WDX (distros)
3010 rej/ann by_zone 14,15,16 and not by G,M,2
3015 You can use the tag 'all' to reject everything eg:
3024 but this probably for advanced users...
3027 8.53. reject/announce (extended for sysops) (8)
3029 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3033 This version allows a sysop to set a filter for a callsign as well as
3034 the default for nodes and users eg:-
3038 reject/ann input node_default by G,M,2
3039 reject/ann user_default by G,M,2
3045 8.54. reject/route (8)
3047 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3051 Create an 'reject this routing PC Protocol' line for a filter.
3054 An reject filter line means that if a PC16/17/19/21/24/41/50 matches
3055 this filter it is NOT passed thru that interface. See HELP FILTERING
3056 for more info. Please read this to understand how filters work - it
3057 will save a lot of grief later on. You can use any of the following
3058 things in this line:-
3062 call <prefixes> the callsign of the thingy
3063 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3066 origin <prefixes> really the interface it came in on
3067 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3068 origin_itu <numbers>
3069 origin_zone <numbers>
3079 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3085 You can use the tag 'all' to reject everything eg:
3089 rej/route all (equiv to [very] restricted mode)
3095 8.55. reject/spots (0)
3097 reject/spots [0-9] <pattern> Set a reject filter line for spots
3100 Create a 'reject this spot' line for a filter.
3103 A reject filter line means that if the spot matches this filter it is
3104 dumped (not passed on). See HELP FILTERS for more info. Please read
3105 this to understand how filters work - it will save a lot of grief
3108 You can use any of the following things in this line:-
3112 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
3113 on <range> same as 'freq'
3114 call <prefixes> eg: G,PA,HB9
3115 info <string> eg: iota or qsl
3117 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3129 For frequencies, you can use any of the band names defined in
3130 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
3131 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
3132 this is more efficient than saying simply: on HF (but don't get too
3140 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3145 You can use the tag 'all' to reject everything eg:
3154 but this probably for advanced users...
3157 8.56. reject/spots (extended for sysops) (8)
3159 reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
3163 This version allows a sysop to set a filter for a callsign as well as
3164 the default for nodes and users eg:-
3169 reject/spot db0sue-7 1 by_zone 14,15,16
3170 reject/spot node_default all
3171 set/hops node_default 10
3173 reject/spot user_default by G,M,2
3179 8.57. reject/wcy (0)
3181 reject/wcy [0-9] <pattern> Set a reject WCY filter
3184 It is unlikely that you will want to do this, but if you do then you
3185 can filter on the following fields:-
3189 by <prefixes> eg: G,M,2
3191 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3192 origin_itu <numbers>
3193 origin_zone <numbers>
3202 There are no examples because WCY Broadcasts only come from one place
3203 and you either want them or not (see UNSET/WCY if you don't want
3206 This command is really provided for future use.
3208 See HELP FILTER for information.
3211 8.58. reject/wcy (extended for sysops) (8)
3213 reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
3217 This version allows a sysop to set a filter for a callsign as well as
3218 the default for nodes and users eg:-
3220 reject/wcy gb7djk all
3223 8.59. reject/wwv (0)
3225 reject/wwv [0-9] <pattern> Set a reject WWV filter
3228 It is unlikely that you will want to do this, but if you do then you
3229 can filter on the following fields:-
3235 by <prefixes> eg: G,M,2
3237 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
3238 origin_itu <numbers>
3239 origin_zone <numbers>
3252 reject/wwv by_zone 14,15,16
3257 is probably the only useful thing to do (which will only show WWV
3258 broadcasts by stations in the US).
3260 See HELP FILTER for information.
3263 8.60. reject/wwv (extended for sysops) (8)
3265 reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
3269 This version allows a sysop to set a filter for a callsign as well as
3270 the default for nodes and users eg:-
3274 reject/wwv db0sue-7 1 by_zone 4
3275 reject/wwv node_default all
3277 reject/wwv user_default by W
3285 reply Reply (privately) to the last message that you have read
3286 reply <msgno> Reply (privately) to the specified message
3287 reply B <msgno> Reply as a Bulletin to the specified message
3288 reply NOPrivate <msgno> Reply as a Bulletin to the specified message
3289 reply RR <msgno> Reply to the specified message with read receipt
3292 You can reply to a message and the subject will automatically have
3293 "Re:" inserted in front of it, if it isn't already present.
3295 You can also use all the extra qualifiers such as RR, PRIVATE,
3296 NOPRIVATE, B that you can use with the SEND command (see SEND for
3303 send <call> [<call> ...] Send a message to one or more callsigns
3304 send RR <call> Send a message and ask for a read receipt
3305 send COPY <msgno> <call> Send a copy of a message to someone
3306 send PRIVATE <call> Send a personal message
3307 send NOPRIVATE <call> Send a message to all stations
3310 All the SEND commands will create a message which will be sent either
3311 to an individual callsign or to one of the 'bulletin' addresses.
3313 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
3314 is it will mark the message as personal and send it to the cluster
3315 node that that callsign is connected to.
3317 You can have more than one callsign in all of the SEND commands.
3319 You can have multiple qualifiers so that you can have for example:-
3323 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3328 which should send a copy of message 123 to G1TLH and G0RDI and you
3329 will receive a read receipt when they have read the message.
3331 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
3332 is an alias for SEND PRIVATE
3335 8.63. set/address (0)
3337 set/address <your_address> Record your postal address
3340 Literally, record your address details on the cluster.
3343 8.64. set/announce (0)
3345 set/announce Allow announce messages
3348 Allow announce messages to arrive at your terminal.
3351 8.65. set/arcluster (5)
3353 set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
3357 Set the node_call as an AR-Cluster type node
3362 set/baddx <call> Stop words we do not wish to see in the callsign
3363 field of a dx spot being propagated
3367 Setting a word as 'baddx' will prevent spots with that word in the
3368 callsign field of a DX spot from going any further. They will not be
3369 displayed and they will not be sent onto other nodes.
3371 The word must be wriiten in full, no wild cards are allowed eg:-
3375 set/baddx FORSALE VIDEO FR0G
3380 To allow a word again, use the following command ...
3390 8.67. set/badnode (6)
3392 set/badnode <node_call> Stop spots from this node_call being
3396 Setting a callsign as a 'badnode' will prevent spots from that node
3397 going any further. They will not be displayed and they will not be
3398 sent onto other nodes.
3400 The call can be a full or partial call (or a prefix), eg:-
3409 will stop anything from K1TTT (including any SSID's)
3418 will allow spots from him again.
3420 Use with extreme care. This command may well be superceded by
3424 8.68. set/badspotter (8)
3426 set/badspotter <call> Stop spots from this callsign being propagated
3429 Setting a callsign as a 'badspotter' will prevent spots from this
3430 callsign going any further. They will not be displayed and they will
3431 not be sent onto other nodes.
3433 The call must be written in full, no wild cards are allowed eg:-
3437 set/badspotter VE2STN
3442 will stop anything from VE2STN. If you want SSIDs as well then you
3443 must enter them specifically.
3447 unset/badspotter VE2STN
3452 will allow spots from him again.
3454 Use with extreme care. This command may well be superceded by
3460 set/beep Add beeps to terminal messages
3463 Add a beep to DX and other terminal messages.
3468 set/bbs <call> [<call>..]Make <call> a BBS
3473 set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
3477 Set the node_call as a CLX type node
3482 set/debug <name> Add a debug level to the debug set
3485 You can choose to log several different levels. The levels are
3487 chan state msg cron connect
3489 You can show what levels you are logging with the show/debug command.
3491 You can remove a debug level with unset/debug <name>
3496 set/dxAllow DX messages to arrive at your terminal
3499 You can stop DX messages with the unset/dx command
3502 8.74. set/dxgrid (0)
3504 set/dxgridAllow grid squares on the end of DX messages
3507 Some logging programs do not like the additional information at the
3508 end of a DX spot. If this is the case, use the unset/dxgrid command
3509 to remove the grid squares.
3514 set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
3518 Set the node_call as a DXNet type node
3523 set/echo Make the cluster echo your input
3526 If you are connected via a telnet session, different implimentations
3527 of telnet handle echo differently depending on whether you are
3528 connected via port 23 or some other port. You can use this command to
3529 change the setting appropriately.
3531 You can remove the echo with the unset/echo command
3533 The setting is stored in your user profile.
3535 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
3540 set/here Set the here flag
3543 Let others on the cluster know you are here by only displaying your
3544 callsign. If you are away from your terminal you can use the
3545 unset/here command to let people know you are away. This simply puts
3546 brackets around your callsign to indicate you are not available.
3549 8.78. set/homenode (0)
3551 set/homenode <node_call> Set your home cluster
3554 Tell the cluster system where you normally connect to. Any Messages
3555 sent to you will normally find their way there should you not be
3567 set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
3570 Set the hop count for a particular type of broadcast for a node.
3572 This command allows you to set up special hop counts for a node for
3573 currently: announce, spots, wwv and wcy broadcasts.
3578 set/hops gb7djk ann 10
3579 set/hops gb7mbc spots 20
3584 Set SHOW/HOPS for information on what is already set. This command
3585 creates a filter and works in conjunction with the filter system.
3588 8.80. set/isolate (9)
3590 set/isolate <node call> Isolate a node from the rest of the network
3593 Connect a node to your system in such a way that you are a full
3594 protocol member of its network and can see all spots on it, but
3595 nothing either leaks out from it nor goes back into from the rest of
3596 the nodes connected to you.
3598 You can potentially connect several nodes in this way.
3600 You can see which nodes are isolated with the show/isolate (1)
3603 You can remove the isolation with the command unset/isolate.
3606 8.81. set/language (0)
3608 set/language <language> Set the language you wish to use
3611 You can select the language that you want the cluster to use.
3612 Currently the languages available are en (English) and nl (Dutch).
3615 8.82. set/location (0)
3617 set/location <lat and long> Set your latitude and longitude
3620 You can set your latitude and longitude manually or alternatively use
3621 the set/qra command which will do the conversion for you.
3625 set/location 54 04 N 2 02 E
3631 8.83. set/sys_location (9)
3633 set/sys_location <lat & long> Set your cluster latitude and longitude
3636 In order to get accurate headings and such like you must tell the
3637 system what your latitude and longitude is. If you have not yet done a
3638 SET/QRA then this command will set your QRA locator for you. For
3643 SET/LOCATION 52 22 N 0 57 E
3649 8.84. set/logininfo (0)
3651 set/logininfo Show logins and logouts of nodes and users
3654 Show users and nodes when they log in and out of the local cluster.
3655 You can stop these messages by using the unset/logininfo command.
3659 8.85. set/lockout (9)
3661 set/lockout <call> Stop a callsign connecting to the cluster
3664 You can show who is locked out with the show/lockout command. To
3665 allow the user to connect again, use the unset/lockout command.
3670 set/name <your_name> Set your name
3673 Tell the cluster what your name is, eg:-
3685 set/node <call> [<call> ...] Make the callsign an AK1A cluster
3688 Tell the system that the call(s) are to be treated as AK1A cluster and
3689 fed PC Protocol rather normal user commands.
3691 From version 1.41 you can also set the following types of cluster
3705 To see what your nodes are set to, use the show/nodes command.
3708 8.88. set/obscount (9)
3710 set/obscount <count> <node call> Set the 'pump-up' obsolescence
3714 From version 1.35 onwards neighbouring nodes are pinged at regular
3715 intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes.
3716 There is a 'pump-up' counter which is decremented on every outgoing
3717 ping and then reset to the 'obscount' value on every incoming ping.
3718 The default value of this parameter is 2.
3720 What this means is that a neighbouring node will be pinged twice at
3721 (default) 300 second intervals and if no reply has been heard just
3722 before what would be the third attempt, that node is disconnected.
3724 If a ping is heard then the obscount is reset to the full value. Using
3725 default values, if a node has not responded to a ping within 15
3726 minutes, it is disconnected.
3731 set/page <n> Set the number of lines per page
3734 Tell the system how many lines you wish on a page when the number of
3735 lines of output from a command is more than this. The default is 20.
3736 Setting it explicitly to 0 will disable paging.
3746 The setting is stored in your user profile.
3750 8.90. set/password (9)
3752 set/password <callsign> <string> Set a users password
3755 The password for a user can only be set by a full sysop. The string
3756 can contain any characters but any spaces are removed (you can type in
3757 spaces - but they won't appear in the password). You can see the
3758 result with STAT/USER. The password is the usual 30 character baycom
3763 8.91. set/pinginterval (9)
3765 set/pinginterval <time> <node call> Set the ping time to neighbouring
3769 As from version 1.35 all neighbouring nodes are pinged at regular
3770 intervals in order to determine the rolling quality of the link and,
3771 in future, to affect routing decisions. The default interval is 300
3774 You can use this command to set a different interval. Please don't.
3776 But if you do the value you enter is treated as minutes up 60 and
3777 seconds for numbers greater than that.
3779 This is used also to help determine when a link is down at the far end
3780 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
3781 for more information.
3784 8.92. set/privilege (9)
3786 set/privilege <n> <call> [<call> ...] Set the privilege level on a
3790 Set the privilege level on a callsign. The privilege levels that
3791 pertain to commands are as default:-
3796 1 - allow remote nodes normal user RCMDs
3797 5 - various privileged commands (including shutdown, but not disc-
3798 connect), the normal level for another node.
3799 8 - more privileged commands (including disconnect)
3800 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
3806 If you are a sysop and you come in as a normal user on a remote
3807 connection your privilege will automatically be set to 0.
3810 8.93. set/spider (5)
3812 set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
3816 Set the node_call as a DXSpider type node
3819 8.94. set/sys_qra (9)
3821 set/sys_qra <locator> Set your cluster QRA locator
3826 set/qra <locator> Set your QRA locator
3829 Tell the system what your QRA (or Maidenhead) locator is. If you have
3830 not done a SET/LOCATION then your latitude and longitude will be set
3831 roughly correctly (assuming your locator is correct ;-). For example:-
3843 set/qth <your QTH> Set your QTH
3846 Tell the system where your are. For example:-
3850 set/qth East Dereham, Norfolk
3858 set/talk Allow talk messages to be seen at your console
3861 Allow talk messages to arrive at your console. You can switch off
3862 talks with the unset/talk command.
3867 set/wcy Allow WCY messages to be seen at your console
3870 Allow WCY information to be seen at your console. You can switch off
3871 WCY messages with the unset/wcy command.
3876 set/wwv Allow WWV messages to be seen at your console
3879 Allow WWV information to be seen at your console. You can switch off
3880 WWV messages with the unset/wwv command.
3885 set/wx Allow WX messages to be seen at your console
3888 Allow WX information to be seen at your console. You can switch off
3889 WX messages with the unset/wx command.
3895 8.101. show/baddx (1)
3897 show/baddxShow all the bad dx calls in the system
3900 Display all the bad dx callsigns in the system, see SET/BADDX for more
3904 8.102. show/badnode (6)
3906 show/badnode Show all the bad nodes in the system
3909 Display all the bad node callsigns in the system, see SET/BADNODE for
3913 8.103. show/badspotter (1)
3915 show/badspotter Show all the bad spotters in the system
3918 Display all the bad spotter's callsigns in the system, see
3919 SET/BADSPOTTER for more information.
3922 8.104. show/configuration (0)
3924 show/configuration [<node>] Show all visible nodes and their users
3927 This command allows you to see all the users that can be seen and the
3928 nodes to which they are connected. With the optional node, you can
3929 specify a particular node to look at.
3931 This command is normally abbreviated to: sh/c
3933 BE WARNED: the list that is returned can be VERY long
3936 8.105. show/configuration/node (0)
3938 show/configuration/node Show all the nodes connected
3941 Show all the nodes connected locally and the nodes they have
3945 8.106. show/connect (1)
3947 show/connect Show all the active connections
3950 This command shows information on all the active connections known to
3951 the node. This command gives slightly more information than WHO.
3954 8.107. show/date (0)
3956 show/date [<prefix>|<callsign>] Show the local time
3959 This is very nearly the same as SHOW/TIME, the only difference the
3960 format of the date string if no arguments are given.
3961 If no prefixes or callsigns are given then this command returns the
3962 local time and UTC as the computer has it right now. If you give some
3963 prefixes then it will show UTC and UTC + the local offset (not
3964 including DST) at the prefixes or callsigns that you specify.
3967 8.108. show/debug (9)
3969 show/debug Show what levels of debug you are logging
3972 The levels can be set with set/debug
3977 show/dx [options] interrogate the spot database
3980 If you just type SHOW/DX you will get the last so many spots (sysop
3981 configurable, but usually 10).
3983 In addition you can add any number of these options in very nearly any
3984 order to the basic SHOW/DX command, they are:-
3989 on <band> - eg 160m 20m 2m 23cm 6mm
3990 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
3992 <number> - the number of spots you want
3993 <from>-<to> - <from> spot no <to> spot no in
3996 <prefix> - for a spotted callsign beginning with <prefix>
3997 *<suffix> - for a spotted callsign ending in <suffix>
3998 *<string>* - for a spotted callsign containing <string>
4000 day <number> - starting <number> days ago
4001 day <from>-<to> - <from> days <to> days ago
4003 info <text> - any spots containing <text> in the info or remarks
4005 by <call> - any spots spotted by <call> (spotter <call>
4008 qsl - this automatically looks for any qsl info on the call
4009 held in the spot database.
4011 iota [<iota>] - If the iota island number is missing it will
4012 look for the string iota and anything which looks like
4013 an iota island number. If you specify then it will look
4016 qra [<locator>] - this will look for the specific locator if
4017 you specify one or else anything that looks like a locator.
4028 SH/DX on 20m info iota
4029 SH/DX 9a on vhf day 30
4039 8.110. show/dxcc (0)
4041 show/dxcc <prefix> Interrogate the spot database by country
4044 This command takes the <prefix> (which can be a full or partial
4045 callsign if desired), looks up which internal country number it is and
4046 then displays all the spots as per SH/DX for that country.
4048 The options for SHOW/DX also apply to this command. e.g.
4054 SH/DXCC W on 20m info iota
4060 8.111. show/files (0)
4062 show/files [<filearea> [<string>]] List the contents of a filearea
4065 SHOW/FILES on its own will show you a list of the various fileareas
4066 available on the system. To see the contents of a particular file area
4076 where <filearea> is the name of the filearea you want to see the
4079 You can also use shell globbing characters like '*' and '?' in a
4080 string to see a selection of files in a filearea eg:-
4084 SH/FILES bulletins arld*
4089 See also TYPE - to see the contents of a file.
4093 8.112. show/filter (0)
4095 show/filter Show the filters you have set
4098 Show the contents of all the filters that are set by you. This command
4099 displays all the filters set - for all the various categories.
4102 8.113. show/filter (extended for sysops) (5)
4104 show/filter <callsign> Show the filters set by <callsign>
4107 A sysop can look at any filters that have been set.
4110 8.114. show/hops (8)
4112 show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
4116 This command shows the hop counts set up for a node. You can specify
4117 which category you want to see. If you leave the category out then all
4118 the categories will be listed.
4121 8.115. show/isolate (1)
4123 show/isolate Show a list of isolated nodes
4126 Show which nodes are currently set to be isolated.
4129 8.116. show/lockout (9)
4131 show/lockout Show a list of excluded callsigns
4134 Show a list of callsigns that have been excluded (locked out) of the
4135 cluster locally with the set/lockout command
4140 show/log [<callsign>] Show excerpts from the system log
4143 This command outputs a short section of the system log. On its own it
4144 will output a general logfile. With the optional callsign it will
4145 show output from the log associated with that callsign.
4148 8.118. show/moon (0)
4150 show/moon [<prefix>|<callsign>] Show moon rise and set times
4153 Show the Moon rise and set times for a (list of) prefixes or
4154 callsigns, together with the azimuth and elevation of the sun
4155 currently at those locations.
4157 If you don't specify any prefixes or callsigns, it will show the times
4158 for your QTH (assuming you have set it with either SET/LOCATION or
4159 SET/QRA), together with the current azimuth and elevation.
4161 In addition, it will show the gain or loss dB relative to the nominal
4162 distance of 385,000Km due to the ellipsoidal nature of the orbit.
4164 If all else fails it will show the Moonrise and set times for the node
4165 that you are connected to.
4180 show/muf <prefix> [<hours>][long] Show the likely propagation to
4184 This command allow you to estimate the likelihood of you contacting a
4185 station with the prefix you have specified. The output assumes a
4186 modest power of 20dBW and receiver sensitivity of -123dBm (about
4189 The result predicts the most likely operating frequencies and signal
4190 levels for high frequency (shortwave) radio propagation paths on
4191 specified days of the year and hours of the day. It is most useful for
4192 paths between 250 km and 6000 km, but can be used with reduced
4193 accuracy for paths shorter or longer than this.
4195 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
4196 used to predict the MUF given the predicted flux, day of the year,
4197 hour of the day and geographic coordinates of the transmitter and
4198 receiver. This routine is reasonably accurate for the purposes here,
4199 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
4200 than the programs used by major shortwave broadcasting organizations,
4201 such as the Voice of America.
4203 The command will display some header information detailing its
4204 assumptions, together with the locations, latitude and longitudes and
4205 bearings. It will then show UTC (UT), local time at the other end
4206 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
4207 (Zen) and the likely signal strengths. Then for each frequency for
4208 which the system thinks there is a likelihood of a circuit it prints a
4211 The value is currently a likely S meter reading based on the
4212 conventional 6dB / S point scale. If the value has a '+' appended it
4213 means that it is 1/2 an S point stronger. If the value is preceeded by
4214 an 'm' it means that there is likely to be much fading and by an 's'
4215 that the signal is likely to be noisy.
4217 By default SHOW/MUF will show the next two hours worth of data. You
4218 can specify anything up to 24 hours worth of data by appending the no
4219 of hours required after the prefix. For example:-
4229 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
4230 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
4231 Location Lat / Long Azim
4232 East Dereham, Norfolk 52 41 N 0 57 E 47
4233 United-States-W 43 0 N 87 54 W 299
4234 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
4235 18 23 11.5 -35 mS0+ mS2 S3
4236 19 0 11.2 -41 mS0+ mS2 S3
4241 indicating that you will have weak, fading circuits on top band and
4242 80m but usable signals on 40m (about S3).
4253 will get you the above display, but with the next 24 hours worth of
4264 Gives you an estimate of the long path propagation characterics. It
4265 should be noted that the figures will probably not be very useful, nor
4266 terrible accurate, but it is included for completeness.
4269 8.120. show/node (1)
4271 show/node [<node_call> ...] Show the type and version number of nodes
4274 Show the type and version (if connected) of the nodes specified on the
4275 command line. If no callsigns are specified then a sorted list of all
4276 the non-user callsigns known to the system will be displayed.
4279 8.121. show/prefix (0)
4281 show/prefix <callsign> Interrogate the prefix database
4284 This command takes the <callsign> (which can be a full or partial
4285 callsign or a prefix), looks up which internal country number it is
4286 and then displays all the relevant prefixes for that country together
4287 with the internal country no, the CQ and ITU regions.
4291 8.122. show/program (5)
4293 show/program Show the locations of all the included program modules
4296 Show the name and location where every program module was load from.
4297 This is useful for checking where you think you have loaded a .pm file
4303 show/qra <locator> [<locator>] Show the distance between locators
4304 show/qra <lat> <long> Convert latitude and longitude to a locator
4307 This is a multipurpose command that allows you either to calculate the
4308 distance and bearing between two locators or (if only one locator is
4309 given on the command line) the distance and beraing from your station
4310 to the locator. For example:-
4320 The first example will show the distance and bearing to the locator
4321 from yourself, the second example will calculate the distance and
4322 bearing from the first locator to the second. You can use 4 or 6
4325 It is also possible to convert a latitude and longitude to a locator
4326 by using this command with a latitude and longitude as an argument,
4331 SH/QRA 52 41 N 0 58 E
4339 show/qrz <callsign> Show any callbook details on a callsign
4342 This command queries the QRZ callbook server on the internet and
4343 returns any information available for that callsign. This service is
4344 provided for users of this software by http://www.qrz.com
4347 8.125. show/route (0)
4349 show/route <callsign> Show the route to <callsign>
4352 This command allows you to see to which node the callsigns specified
4353 are connected. It is a sort of inverse sh/config.
4363 8.126. show/satellite (0)
4365 show/satellite <name> [<hours> <interval>] Show satellite tracking
4369 Show the tracking data from your location to the satellite of your
4370 choice from now on for the next few hours.
4372 If you use this command without a satellite name it will display a
4373 list of all the satellites known currently to the system.
4375 If you give a name then you can obtain tracking data of all the passes
4376 that start and finish 5 degrees below the horizon. As default it will
4377 give information for the next three hours for every five minute
4380 You can alter the number of hours and the step size, within certain
4383 Each pass in a period is separated with a row of '-----' characters
4390 SH/SAT FENGYUN1 12 2
4398 show/sun [<prefix>|<callsign>] Show sun rise and set times
4401 Show the sun rise and set times for a (list of) prefixes or callsigns,
4402 together with the azimuth and elevation of the sun currently at those
4405 If you don't specify any prefixes or callsigns, it will show the times
4406 for your QTH (assuming you have set it with either SET/LOCATION or
4407 SET/QRA), together with the current azimuth and elevation.
4409 If all else fails it will show the sunrise and set times for the node
4410 that you are connected to.
4417 SH/SUN G1TLH K9CW ZS
4423 8.128. show/time (0)
4425 show/time [<prefix>|<callsign>] Show the local time
4428 If no prefixes or callsigns are given then this command returns the
4429 local time and UTC as the computer has it right now. If you give some
4430 prefixes then it will show UTC and UTC + the local offset (not
4431 including DST) at the prefixes or callsigns that you specify.
4436 show/wcy Show the last 10 WCY broadcasts
4437 show/wcy <n> Show the last <n> WCY broadcasts
4440 Display the most recent WCY information that has been received by the
4446 show/wwv Show the last 10 WWV broadcasts
4447 show/wwv <n> Show the last <n> WWV broadcasts
4450 Display the most recent WWV information that has been received by the
4457 shutdown Shutdown the cluster
4460 Shutdown the cluster and disconnect all the users. If you have Spider
4461 set to respawn in /etc/inittab it will of course restart.
4466 spoof <callsign> <command> Run commands as another user
4469 This is a very simple yet powerful command for the sysop. It allows
4470 you to issue commands as if you were a different user. This is very
4471 useful for the kind of things that users seem to always get wrong..
4472 like home_node for example.
4477 stat/db <dbname> Show the status of a database
4480 Show the internal status of a database descriptor.
4482 Depending on your privilege level you will see more or less
4483 information. This command is unlikely to be of much use to anyone
4489 8.134. stat/channel (5)
4491 stat/channel <callsign> Show the status of a channel on the cluster
4494 Show the internal status of the channel object either for the channel
4495 that you are on or else for the callsign that you asked for.
4497 Only the fields that are defined (in perl term) will be displayed.
4502 stat/msg <msgno> Show the status of a message
4505 This command shows the internal status of a message and includes
4506 information such as to whom it has been forwarded, its size, origin
4510 If no message number is given then the status of the message system is
4514 8.136. stat/route_node (5)
4516 stat/route_node <callsign> Show the data in a Route::Node object
4519 8.137. stat/route_user (5)
4521 stat/route_user <callsign> Show the data in a Route::User object
4524 8.138. stat/user (5)
4526 stat/user <callsign> Show the full status of a user
4529 Shows the full contents of a user record including all the secret
4532 Only the fields that are defined (in perl term) will be displayed.
4537 sysop Regain your privileges if you login remotely
4540 The system automatically reduces your privilege level to that of a
4541 normal user if you login in remotely. This command allows you to
4542 regain your normal privilege level. It uses the normal system: five
4543 numbers are returned that are indexes into the character array that is
4544 your assigned password (see SET/PASSWORD). The indexes start from
4547 You are expected to return a string which contains the characters
4548 required in the correct order. You may intersperse those characters
4549 with others to obscure your reply for any watchers. For example (and
4550 these values are for explanation :-):
4555 password = 012345678901234567890123456789
4566 aa2bbbb0ccc5ddd7xxx3n
4573 They will all match. If there is no password you will still be offered
4574 numbers but nothing will happen when you input a string. Any match is
4580 talk <callsign> Enter talk mode with <callsign>
4581 talk <callsign> <text> Send a text message to <callsign>
4582 talk <callsign> > <node_call> [<text>] Send a text message to
4583 <callsign> via <node_call>
4586 Send a short message to any other station that is visible on the
4587 cluster system. You can send it to anyone you can see with a
4588 SHOW/CONFIGURATION command, they don't have to be connected locally.
4590 The second form of TALK is used when other cluster nodes are connected
4591 with restricted information. This usually means that they don't send
4592 the user information usually associated with logging on and off the
4595 If you know that G3JNB is likely to be present on GB7TLH, but you can
4596 only see GB7TLH in the SH/C list but with no users, then you would use
4597 the second form of the talk message.
4599 If you want to have a ragchew with someone you can leave the text
4600 message out and the system will go into 'Talk' mode. What this means
4601 is that a short message is sent to the recipient telling them that you
4602 are in a 'Talking' frame of mind and then you just type - everything
4603 you send will go to the station that you asked for.
4605 All the usual announcements, spots and so on will still come out on
4608 If you want to do something (such as send a spot) you precede the
4609 normal command with a '/' character, eg:-
4613 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
4619 To leave talk mode type:
4629 type <filearea>/<name> Look at a file in one of the fileareas
4632 Type out the contents of a file in a filearea. So, for example, in
4633 filearea 'bulletins' you want to look at file 'arld051' you would
4638 TYPE bulletins/arld051
4643 See also SHOW/FILES to see what fileareas are available and a list of
4649 who Show who is physically connected locally
4652 This is a quick listing that shows which callsigns are connected and
4653 what sort of connection they have
4658 wx <text> Send a weather message to local users
4659 wx full <text> Send a weather message to all cluster users
4662 Weather messages can sometimes be useful if you are experiencing an
4663 extreme that may indicate enhanced conditions
4666 8.144. wx (enhanced for sysops) (5)
4668 wx sysop <text> Send a weather message to other clusters only
4671 Send a weather message only to other cluster nodes and not to general
projects / spider.git / blob