1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 February 2003 revision 0.3
6 A reference for SysOps of the DXSpider DXCluster program.
7 ______________________________________________________________________
13 1. Routing and Filtering
16 1.3 The node_default filter
17 1.4 General route filtering
18 1.5 General filter rules
22 1.9 Advanced filtering
23 1.10 Basic hop control
24 1.11 Hop Control on Specific Nodes
25 1.12 Isolating networks
29 2.2 Filtering words from text fields in Announce, Talk and DX spots
30 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
39 3.7 Distribution lists
44 5.1 Creating databases
45 5.2 Importing databases
46 5.3 Checking available databases
47 5.4 Looking up databases
48 5.5 Removing databases
50 6. Information, files and useful programs
54 6.4 Other text messages
57 6.7 Updating kepler data
59 6.9 Connecting logging programs
62 8. Web based statistics
68 10.1 CVS from a Linux platform
69 10.2 CVS from a Windows platform
71 11. The DXSpider command set
73 11.2 accept/announce <call> [input] [0-9] <pattern> (8)
74 11.3 accept/announce [0-9] <pattern> (0)
75 11.4 accept/route <call> [0-9] <pattern> (8)
76 11.5 accept/spots <call> [input] [0-9] <pattern> (8)
77 11.6 accept/spots [0-9] <pattern> (0)
78 11.7 accept/wcy <call> [input] [0-9] <pattern> (8)
79 11.8 accept/wcy [0-9] <pattern> (0)
80 11.9 accept/wwv <call> [input] [0-9] <pattern> (8)
81 11.10 accept/wwv [0-9] <pattern> (0)
82 11.11 announce <text> (0)
83 11.12 announce full <text> (0)
84 11.13 announce sysop <text> (5)
85 11.14 apropos <string> (0)
86 11.15 blank [<string>] [<nn>] (0)
88 11.17 catchup <node call> all|[<msgno> ...] (5)
89 11.18 clear/announce <callsign> [input] [0-9|all] (8)
90 11.19 clear/announce [1|all] (0)
91 11.20 clear/route <callsign> [input] [0-9|all] (8)
92 11.21 clear/route [1|all] (0)
93 11.22 clear/spots <callsign> [input] [0-9|all] (8)
94 11.23 clear/spots [0-9|all] (0)
95 11.24 clear/wcy <callsign> [input] [0-9|all] (8)
96 11.25 clear/wcy [1|all] (0)
97 11.26 clear/wwv <callsign> [input] [0-9|all] (8)
98 11.27 clear/wwv [1|all] (0)
99 11.28 connect <callsign> (5)
101 11.30 dbshow <dbname> <key> (0)
103 11.32 directory <from>-<to> (0)
104 11.33 directory <nn> (0)
105 11.34 directory all (0)
106 11.35 directory from <call> (0)
107 11.36 directory new (0)
108 11.37 directory own (0)
109 11.38 directory subject <string> (0)
110 11.39 directory to <call> (0)
112 11.41 disconnect <call> [<call> ...] (8)
113 11.42 dx [by <call>] <freq> <call> <remarks> (0)
114 11.43 echo <line> (0)
115 11.44 filtering... (0)
116 11.45 forward/latlong <node_call> (8)
117 11.46 forward/opernam <call> (1)
119 11.48 init <node> (5)
121 11.50 kill <from msgno>-<to msgno> (0)
122 11.51 kill <from>-<to> (5)
123 11.52 kill <msgno> [<msgno..] (0)
124 11.53 kill <msgno> [<msgno> ...] (0)
125 11.54 kill expunge <msgno> [<msgno..] (6)
126 11.55 kill from <call> (5)
127 11.56 kill full <msgno> [<msgno..] (5)
128 11.57 kill full <msgno> [<msgno] (5)
129 11.58 kill to <call> (5)
130 11.59 kill from <regex> (0)
131 11.60 kill to <regex> (0)
134 11.63 load/keps [nn] (5)
135 11.64 merge <node> [<no spots>/<no wwv>] (5)
136 11.65 pc <call> <text> (8)
137 11.66 ping <node call> (1)
138 11.67 rcmd <node call> <cmd> (1)
140 11.69 read <msgno> (0)
143 11.72 reject/announce <call> [input] [0-9] <pattern> (8)
144 11.73 reject/announce [0-9] <pattern> (0)
145 11.74 reject/route <call> [0-9] <pattern> (8)
146 11.75 reject/spots <call> [input] [0-9] <pattern> (8)
147 11.76 reject/spots [0-9] <pattern> (0)
148 11.77 reject/wcy <call> [input] [0-9] <pattern> (8)
149 11.78 reject/wcy [0-9] <pattern> (0)
150 11.79 reject/wwv <call> [input] [0-9] <pattern> (8)
151 11.80 reject/wwv [0-9] <pattern> (0)
153 11.82 reply <msgno> (0)
154 11.83 reply b <msgno> (0)
155 11.84 reply noprivate <msgno> (0)
156 11.85 reply rr <msgno> (0)
157 11.86 send <call> [<call> ...] (0)
158 11.87 send copy <msgno> <call> (0)
159 11.88 send noprivate <call> (0)
160 11.89 send private <call> (0)
161 11.90 send rr <call> (0)
162 11.91 set/address <your address> (0)
163 11.92 set/announce (0)
164 11.93 set/anntalk (0)
165 11.94 set/arcluster <call> [<call>..] (5)
166 11.95 set/baddx <call>.. (8)
167 11.96 set/badnode <call>.. (8)
168 11.97 set/badspotter <call>.. (8)
169 11.98 set/badword <word>.. (8)
170 11.99 set/bbs <call> [<call>..] (5)
172 11.101 set/clx <call> [<call>..] (5)
174 11.103 set/dxgrid (0)
175 11.104 set/dxnet <call> [<call>..] (5)
177 11.106 set/email <email> ... (0)
179 11.108 set/homenode <node> (0)
180 11.109 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
181 11.110 set/language <lang> (0)
182 11.111 set/location <lat & long> (0)
183 11.112 set/logininfo (0)
184 11.113 set/name <your name> (0)
185 11.114 set/node <call> [<call>..] (5)
186 11.115 set/obscount <count> <call> (8)
187 11.116 set/page <lines per page> (0)
188 11.117 set/password (0)
189 11.118 set/prompt <string> (0)
190 11.119 set/qra <locator> (0)
191 11.120 set/qth <your qth> (0)
192 11.121 set/spider <call> [<call>..] (5)
197 11.126 show/baddx (1)
198 11.127 show/badnode (1)
199 11.128 show/badspotter (1)
200 11.129 show/badword (1)
201 11.130 show/configuration [<node>] (0)
202 11.131 show/configuration/node (0)
203 11.132 show/connect (1)
204 11.133 show/date [<prefix>|<callsign>] (0)
206 11.135 show/dxcc <prefix> (0)
207 11.136 show/dxstats [days] [date] (0)
208 11.137 show/files [<filearea> [<string>]] (0)
209 11.138 show/filter (0)
210 11.139 show/hfstats [days] [date] (0)
211 11.140 show/hftable [days] [date] [prefix ...] (0)
212 11.141 show/hops <call> [ann|spots|route|wcy|wwv] (8)
213 11.142 show/isolate (1)
214 11.143 show/log [<callsign>] (8)
215 11.144 show/moon [ndays] [<prefix>|<callsign>] (0)
216 11.145 show/muf <prefix> [<hours>][long] (0)
217 11.146 show/newconfiguration [<node>] (0)
218 11.147 show/newconfiguration/node (0)
219 11.148 show/node [<callsign> ...] (1)
220 11.149 show/prefix <callsign> (0)
221 11.150 show/program (5)
222 11.151 show/qra <lat> <long> (0)
223 11.152 show/qra <locator> [<locator>] (0)
224 11.153 show/qrz <callsign> (0)
225 11.154 show/route <callsign> ... (0)
226 11.155 show/satellite <name> [<hours> <interval>] (0)
227 11.156 show/station all [<regex>] (6)
228 11.157 show/station [<callsign> ..] (0)
229 11.158 show/sun [ndays] [<prefix>|<callsign>] (0)
230 11.159 show/time [<prefix>|<callsign>] (0)
231 11.160 show/usdb [call ..] (0)
232 11.161 show/vhfstats [days] [date] (0)
233 11.162 show/vhftable [days] [date] [prefix ...] (0)
235 11.164 show/wcy <n> (0)
237 11.166 show/wwv <n> (0)
239 11.168 stat/channel [<callsign>] (5)
240 11.169 stat/db <dbname> (5)
242 11.171 stat/msg <msgno> (1)
243 11.172 stat/route_node <callsign> (5)
244 11.173 stat/route_node all (5)
245 11.174 stat/route_user <callsign> (5)
246 11.175 stat/route_user all (5)
247 11.176 stat/user [<callsign>] (5)
249 11.178 talk <call> > <node> [<text>] (0)
250 11.179 talk <call> [<text>] (0)
251 11.180 type <filearea>/<name> (0)
252 11.181 uncatchup <node call> all|[msgno> ...] (5)
253 11.182 unset/announce (0)
254 11.183 unset/anntalk (0)
255 11.184 unset/baddx <call>.. (8)
256 11.185 unset/badnode <call>.. (8)
257 11.186 unset/badspotter <call>.. (8)
258 11.187 unset/badword <word>.. (8)
259 11.188 unset/beep (0)
261 11.190 unset/dxgrid (0)
262 11.191 unset/echo (0)
263 11.192 unset/email (0)
264 11.193 unset/here (0)
265 11.194 unset/hops <call> ann|spots|route|wwv|wcy (8)
266 11.195 unset/logininfo (0)
267 11.196 unset/privilege (0)
268 11.197 unset/prompt (0)
269 11.198 unset/talk (0)
275 11.204 wx full <text> (0)
276 11.205 wx sysop <text> (5)
277 ______________________________________________________________________
279 1. Routing and Filtering
283 From DXSpider version 1.48, major changes were introduced to the way
284 node connections are treated. This is part of an ongoing process to
285 remove problems with loops and to enable talk and other functions to
286 propagate across the whole of the worldwide cluster network. In fact,
287 in a Spider network, it would be useful, perhaps even necessary to
288 have loops. This would give real resilience to the network, meaning
289 that if a link dropped, the information flow would simply come in and
290 go out via a different route. Of course, we do not have a complete
291 network of Spider nodes, there are other programs out there. Some of
292 these do not have any protection from loops. Certainly AK1A does not
293 handle loops well at all. It is therefore necessary to have some form
294 of protection for these nodes.
297 In fact DXSpider has had a simple system for some time which is called
298 isolation. This is similar to what in other systems such as clx, is
299 called passive mode. A more detailed explanation of isolation is given
300 further below. This system is still available and, for simple
301 networks, is probably all that you need.
304 The new functionality introduced in version 1.48 allows filtering the
305 node and user protocol frames on a "per interface" basis. We call this
306 route filtering. This is used instead of isolation.
309 What this really means is that you can control more or less completely
310 which user and node management PC protocol frames pass to each of your
311 partner nodes. You can also limit what comes into your node from your
312 partners. It is even possible to control the settings that your
313 partner node has for the routing information that it sends to you
314 (using the rcmd command).
319 Initially when route filters were being tested we generated a
320 "default" filter. Unfortunately it quickly became apparent that this
321 might suit the UK cluster network but didn't really fit anybody else.
322 However using a default filter is an appropriate thing to do. How, is
323 explained further on.
326 The first thing that you must do is determine whether you need to use
327 route filtering at all. If you are a "normal" node with two or three
328 partners and you arranged in an "official" non-looping tree type
329 network, then you do not need to do route filtering and you will feel
330 a lot better for not getting involved. If you are successfully using
331 isolation then you also probably don't need to use route filtering.
334 To put it simply, you should not mix Isolation and Route Filtering.
335 It will work, of sorts, but you will not get the expected results. If
336 you are using Isolation sucessfully at the moment, do not get involved
337 in Route Filtering unless you have a good supply of aspirin! Once you
338 have started down the road of Route Filtering, do not use Isolation
339 either. Use one or the other, not both.
343 You will only require this functionality if you are "well-connected".
344 What that means is that you are connected to several different parts
345 of (say) the EU cluster and, at the same time, also connected to two
346 or three places in the US which, in turn are connected back to the EU.
347 This is called a "loop" and if you are seriously looped then you need
351 I should at this stage give a little bit of background on filters.
352 All the filters in Spider work in basically the same way. You can
353 either accept or reject various options in order to create the filter
354 rules you wish to achieve. Some filters are user settable, others can
355 only be altered by the sysop. Route filtering can only be done by the
360 Anyway, without further discouragement, let me start the process of
364 1.3. The node_default filter
366 All normal systems should have a default routing filter and it should
367 usually be set to send only the normal, unlooped, view of your
368 "national" network. Here in the UK that means nodes from the UK and
369 Eire, in EU it is more complex as the networks there grew up in a more
374 The generic commands are:-
378 reject/route node_default <filter_option>
382 accept/route node_default <filter_option>
386 where filter_option is one of the following ...
395 channel_dxcc <numbers>
396 channel_itu <numbers>
397 channel_zone <numbers>
401 Please be careful if you alter this setting, it will affect ALL your
402 links! Remember, this is a default filter for node connections, not a
407 For the default routing filter then you have two real choices: either
408 a "national" view or the "safe" option of only your own callsign.
409 Examples of each (for my node: GB7DJK) are:-
413 acc/route node_default call_dxcc 61,38
414 acc/route node_default call gb7djk
418 GB7DJK uses the first of these. The DXCC countries can be obtained
419 from the show/prefix command.
422 The example filters shown control output TO all your partner nodes
423 unless they have a specific filter applied to them (see next section).
426 It is also possible to control the incoming routing information that
427 you are prepared to accept FROM your partner nodes. The reason this is
428 necessary is to make sure that stuff like mail, pings and similar
429 commands a) go down the correct links and b) don't loop around
430 excessively. Again using GB7DJK as an example a typical default input
431 filter would be something like:
435 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
439 What this does is accept node and user information for our national
440 network from nodes that are in our national network, but rejects such
441 information from anyone else. Although it doesn't explicitly say so,
442 by implication, any other node information (not from the UK and Eire)
446 As I imagine it will take a little while to get one's head around all
447 of this you can study the effect of any rules that you try by watching
448 the debug output after having done:-
456 After you have got tired of that, to put it back the way it was:-
464 1.4. General route filtering
466 Exactly the same rules apply for general route filtering. You would
467 use either an accept filter or a reject filter like this ...
468 reject/route <node_call> <filter_option>
472 accept/route <node_call> <filter_option>
476 Here are some examples of route filters ...
480 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
481 rej/route all (equiv to [very] restricted mode)
482 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
483 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
487 In practice you will either be opening the default filter out for a
488 partner by defining a specific filter for that callsign:-
493 acc/route gb7baa input all
497 or restricting it quite a lot, in fact making it very nearly like an
498 isolated node, like this:-
502 acc/route pi4ehv-8 call gb7djk
503 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 ...
545 where ..... are the specific commands for that type of filter. There
546 are filters for spots, wwv, announce, wcy and (for sysops) connects.
547 See each different accept or reject command reference for more
550 There is also a command to clear out one or more lines in a filter.
560 There is clear/xxxx command for each type of filter.
563 and you can check that your filters have worked by the command ...
571 For now we are going to use spots for the examples, but you can apply
572 the same principles to all types of filter.
577 There are two main types of filter, accept or reject. You can use
578 either to achieve the result you want dependent on your own preference
579 and which is more simple to do. It is pointless writing 8 lines of
580 reject filters when 1 accept filter would do the same thing! Each
581 filter has 10 lines (of any length) which are tried in order. If a
582 line matches then the action you have specified is taken (ie reject
583 means ignore it and accept means take it)
586 If you specify reject filters, then any lines that arrive that match
587 the filter will be dumped but all else will be accepted. If you use
588 an accept filter, then ONLY the lines in the filter will be accepted
589 and all else will be dumped. For example if you have a single line
594 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
598 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
601 If you set a reject filter like this ...
605 reject/spots on hf/cw
609 Then you will get everything EXCEPT HF CW spots. You could make this
610 single filter even more flexible. For example, if you are interested
611 in IOTA and will work it even on CW even though normally you are not
612 interested in CW, then you could say ...
616 reject/spots on hf/cw and not info iota
620 But in that case you might only be interested in iota and say:-
624 accept/spots not on hf/cw or info iota
628 which achieves exactly the same thing. You should choose one or the
629 other until you are comfortable with the way it works. You can mix
630 them if you wish (actually you can have an accept AND a reject on the
631 same line) but don't attempt this until you are sure you know what you
635 You can arrange your filter lines into logical units, either for your
636 own understanding or simply convenience. Here is an example ...
640 reject/spots 1 on hf/cw
641 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
645 What this does is to ignore all HF CW spots and also rejects any spots
646 on VHF which don't either originate or spot someone in Europe.
650 This is an example where you would use a line number (1 and 2 in this
651 case), if you leave the digit out, the system assumes '1'. Digits
652 '0'-'9' are available. This make it easier to see just what filters
653 you have set. It also makes it more simple to remove individual
654 filters, during a contest for example.
657 You will notice in the above example that the second line has
658 brackets. Look at the line logically. You can see there are 2
659 separate sections to it. We are saying reject spots that are VHF or
660 above APART from those in zones 14, 15 and 16 (either spotted there or
661 originated there). If you did not have the brackets to separate the 2
662 sections, then Spider would read it logically from the front and see a
663 different expression entirely ...
667 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
671 The simple way to remember this is, if you use OR - use brackets.
672 Whilst we are here CASE is not important. 'And BY_Zone' is just the
673 same as 'and by_zone'.
675 As mentioned earlier, setting several filters can be more flexible
676 than simply setting one complex one. Doing it in this way means that
677 if you want to alter your filter you can just redefine or remove one
678 or more lines of it or one line. For example ...
682 reject/spots 1 on hf/ssb
686 would redefine our earlier example, or
694 To remove all the filter lines in the spot filter ...
704 You can filter in several different ways. The options are listed in
705 the various helpfiles for accept, reject and filter.
711 Sometimes all that is needed is a general rule for node connects.
712 This can be done with a node_default filter. This rule will always be
713 followed, even if the link is isolated, unless another filter is set
714 specifically. Default rules can be set for nodes and users. They can
715 be set for spots, announces, WWV and WCY. They can also be used for
716 hops. An example might look like this ...
720 accept/spot node_default by_zone 14,15,16,20,33
721 set/hops node_default spot 50
725 This filter is for spots only, you could set others for announce, WWV
726 and WCY. This filter would work for ALL nodes unless a specific
727 filter is written to override it for a particular node. You can also
728 set a user_default should you require. It is important to note that
729 default filters should be considered to be "connected". By this I
730 mean that should you override the default filter for spots, you need
731 to add a rule for the hops for spots also.
734 1.9. Advanced filtering
736 Once you are happy with the results you get, you may like to
740 The previous example that filters hf/cw spots and accepts vhf/uhf
741 spots from EU can be written with a mixed filter, for example ...
747 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
751 Note that the first filter has not been specified with a number. This
752 will automatically be assumed to be number 1. In this case, we have
753 said reject all HF spots in the CW section of the bands but accept all
754 others at HF. Also accept anything in VHF and above spotted in or by
755 operators in the zones 14, 15 and 16. Each filter slot actually has a
756 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
760 It was mentioned earlier that after a reject test that doesn't match,
761 the default for following tests is 'accept', the reverse is true for
762 'accept'. In the example what happens is that the reject is executed
763 first, any non hf/cw spot is passed to the accept line, which lets
764 through everything else on HF. The next filter line lets through just
765 VHF/UHF spots from EU.
768 1.10. Basic hop control
770 In /spider/data you will find a file called hop_table.pl. This is the
771 file that controls your hop count settings. It has a set of default
772 hops on the various PC frames and also a set for each node you want to
773 alter the hops for. You may be happy with the default settings of
774 course, but this powerful tool can help to protect and improve the
775 network. The file will look something like this ...
780 # hop table construction
785 # default hopcount to use
788 # some variable hop counts based on message type
799 # the per node hop control thingy
831 Each set of hops is contained within a pair of curly braces and
832 contains a series of PC frame types. PC11 for example is a DX spot.
833 The figures here are not exhaustive but should give you a good idea of
837 SHould any of the nodecalls include an ssid, it is important to wrap
838 the whole call in single quotes, like this ...
853 If you do not do this, you will get errors and the file will not work
857 You can alter this file at any time, including whilst the cluster is
858 running. If you alter the file during runtime, the command load/hops
859 will bring your changes into effect.
862 1.11. Hop Control on Specific Nodes
864 You can set a callsign specific hop count for any of the standard
869 set/hops gb7djk spot 4
870 set/hops node_default route 10
871 set/hops gb7baa wcy 5
875 all work on their specific area of the protocol.
878 The set/hops command overrides any hops that you have set otherwise.
881 You can show what hops have been set using the show/hops command.
884 1.12. Isolating networks
886 It is possible to isolate networks from each other on a "gateway" node
887 using the set/isolate <node_call> command.
890 The effect of this is to partition an isolated network completely from
891 another node connected to your node. Your node will appear on and
892 otherwise behave normally on every network to which you are connected,
893 but data from an isolated network will not cross onto any other
894 network or vice versa. However all the spot, announce and WWV traffic
895 and personal messages will still be handled locally (because you are a
896 real node on all connected networks), that is locally connected users
897 will appear on all networks and will be able to access and receive
898 information from all networks transparently. All routed messages will
899 be sent as normal, so if a user on one network knows that you are a
900 gateway for another network, he can still still send a talk/announce
901 etc message via your node and it will be routed across.
904 If you use isolate on a node connection you will continue to receive
905 all information from the isolated partner, however you will not pass
906 any information back to the isolated node. There are times when you
907 would like to forward only spots across a link (maybe during a contest
908 for example). To do this, isolate the node in the normal way and use
909 an acc/spot >call< all filter to override the isolate.
916 In the /spider/msg directory you will find a file called
917 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
918 original looks something like this ....
922 # the list of regexes for messages that we won't store having
923 # received them (bear in mind that we must receive them fully before
927 # The format of each line is as follows
929 # type source pattern
930 # P/B/F T/F/O/S regex
932 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
933 # source: T - to field, F - from field, O - origin, S - subject
934 # pattern: a perl regex on the field requested
936 # Currently only type B and P msgs are affected by this code.
938 # The list is read from the top down, the first pattern that matches
939 # causes the action to be taken.
941 # The pattern can be undef or 0 in which case it will always be selected
942 # for the action specified
953 I think this is fairly self explanatory. It is simply a list of
954 subject headers that we do not want to pass on to either the users of
955 the cluster or the other cluster nodes that we are linked to. This is
956 usually because of rules and regulations pertaining to items for sale
957 etc in a particular country.
961 2.2. Filtering words from text fields in Announce, Talk and DX spots
963 From version 1.48 onwards the interface to this has changed. You can
964 now use the commands set/badword to add words that you are not
965 prepared to see on the cluster, unset/badword to allow that word again
966 and show/badword to list the words that you have set.
969 If you have a previous /spider/data/badwords, the first time you start
970 the node, it will read and convert this file to the new commands. The
971 old style file will then be removed.
974 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
977 There are a number of commands that control whether a spot progresses
978 any further by regarding it as "bad" in some way.
981 A DX Spot has a number of fields which can be checked to see whether
982 they contain "bad" values, they are: the DX callsign itself, the
983 Spotter and the Originating Node.
986 There are a set of commands which allow the sysop to control whether a
997 These work in the same as the set/badword command, you can add any
998 words or callsigns or whatever to the appropriate database. For
999 example, to stop a spot from a particular node you do:
1003 set/badnode gb7djk gb7dxc
1011 set/badspotter b0mb p1rat nocall
1019 set/baddx video wsjt
1023 You can remove a word using the appropriate unset command
1024 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1025 of show/baddx, show/badspotter and show/badnode.
1030 DXSpider deals seamlessly with standard AK1A type mail. It supports
1031 both personal and bulletin mail and the sysop has additional commands
1032 to ensure that mail gets to where it is meant. DXSpider will send
1033 mail almost immediately, assuming that the target is on line.
1034 However, only one mail message is dealt with at any one time. If a
1035 mail message is already being sent or recieved, then the new message
1036 will be queued until it has finished.
1038 The cluster mail is automatically deleted after 30 days unless the
1039 sysop sets the "keep" flag using the msg command.
1044 Personal mail is sent using the sp command. This is actually the
1045 default method of sending mail and so a simple s for send will do. A
1046 full list of the send commands and options is in the command set
1047 section, so I will not duplicate them here.
1052 Bulletin mail is sent by using the sb command. This is one of the
1053 most common mistakes users make when sending mail. They send a
1054 bulletin mail with s or sp instead of sb and of course the message
1055 never leaves the cluster. This can be rectified by the sysop by using
1059 Bulletin addresses can be set using the Forward.pl file.
1064 DXSpider receives all and any mail sent to it without any alterations
1065 needed in files. Because personal and bulletin mail are treated
1066 differently, there is no need for a list of accepted bulletin
1067 addresses. It is necessary, however, to tell the program which links
1068 accept which bulletins. For example, it is pointless sending
1069 bulletins addresses to "UK" to any links other than UK ones. The file
1070 that does this is called forward.pl and lives in /spider/msg. At
1071 default, like other spider files it is named forward.pl.issue. Rename
1072 it to forward.pl and edit the file to match your requirements. The
1078 # this is an example message forwarding file for the system
1080 # The format of each line is as follows
1082 # type to/from/at pattern action destinations
1083 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1085 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1086 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1087 # pattern: a perl regex on the field requested
1088 # action: I - ignore, F - forward
1089 # destinations: a reference to an array containing node callsigns
1091 # if it is non-private and isn't in here then it won't get forwarded
1093 # Currently only type B msgs are affected by this code.
1095 # The list is read from the top down, the first pattern that matches
1096 # causes the action to be taken.
1098 # The pattern can be undef or 0 in which case it will always be selected
1099 # for the action specified
1101 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1102 # pattern) then it will always be forwarded to every node that doesn't have
1103 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1104 # you allow a new link with this on EVERY bull will be forwarded immediately
1105 # on first connection)
1115 Simply insert a bulletin address and state in the brackets where you
1116 wish that mail to go. For example, you can see here that mail sent to
1117 "UK" will only be sent to the UK links and not to PA4AB-14.
1120 To force the cluster to reread the file use load/forward
1123 NB: If a user tries to send mail to a bulletin address that does not
1124 exist in this file, they will get an error.
1127 3.4. The msg command
1129 The msg command is a very powerful and flexible tool for the sysop.
1130 It allows the sysop to alter to and from fields and make other changes
1131 to manage the cluster mail.
1133 Here is a full list of the various options ...
1137 MSG TO <msgno> <call> - change TO callsign to <call>
1138 MSG FRom <msgno> <call> - change FROM callsign to <call>
1139 MSG PRrivate <msgno> - set private flag
1140 MSG NOPRrivate <msgno> - unset private flag
1141 MSG RR <msgno> - set RR flag
1142 MSG NORR <msgno> - unset RR flag
1143 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1144 MSG NOKEep <msgno> - unset the keep flag
1145 MSG SUbject <msgno> <new> - change the subject to <new>
1146 MSG WAittime <msgno> - remove any waiting time for this message
1147 MSG NOREad <msgno> - mark message as unread
1148 MSG REad <msgno> - mark message as read
1149 MSG QUeue - queue any outstanding bulletins
1150 MSG QUeue 1 - queue any outstanding private messages
1154 These commands are simply typed from within the cluster as the sysop
1160 You can check on a message from within the cluster by using the
1161 command stat/msg. This will give you additional information on the
1162 message number including which nodes have received it, which node it
1163 was received from and when etc. Here is an example of the output of
1168 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1171 Msg Time: 26-Jan-2001 1302Z
1175 Subject: AMSAT 2line KEPS 01025.AMSAT
1177 Got it Nodes: GB7BAA, GB7ADX
1181 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1187 This is described in the section on Other filters so I will not
1191 3.7. Distribution lists
1193 Distribution lists are simply a list of users to send certain types of
1194 mail to. An example of this is mail you only wish to send to other
1195 sysops. In /spider/msg there is a directory called distro. You put
1196 any distibution lists in here. For example, here is a file called
1197 SYSOP.pl that caters for the UK sysops.
1200 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1201 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1202 GB7DXK GB7DXI GB7DXS)
1206 Any mail sent to "sysop" would only be sent to the callsigns in this
1212 Spider provides a simple BBS interface. No input is required from the
1213 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1214 and pushes any required mail to the cluster. No mail can flow from
1215 Spider to the BBS, the interface is one-way.
1218 Please be careful not to flood the cluster network with unnecessary
1219 mail. Make sure you only send mail to the clusters that want it by
1220 using the Forward.pl file very carefully.
1225 From 1.48 onwards it will become increasingly possible to control
1226 DXSpider's operation with scripts of various kinds.
1229 The directory /spider/scripts is where it all happens and is used for
1230 several things. Firstly it contains a file called startup that can be
1231 used to call in any changes to the cluster from the default settings
1232 on startup. This script is executed immediately after all
1233 initialisation of the node is done but before any connections are
1234 possible. Examples of this include how many spots it is possible to
1235 get with the sh/dx command, whether you want registration/passwords to
1236 be permanently on etc. An example file is shown below and is included
1237 in the distribution as startup.issue.
1242 # startup script example
1244 # set maximum no of spots allowed to 100
1245 # set/var $Spot::maxspots = 100
1247 # Set registration on
1248 # set/var $main::reqreg = 1
1251 # set/var $main::passwdreq = 1
1256 As usual, any text behind a # is treated as a comment and not read.
1257 To use this file, simply rename it from startup.issue to startup. In
1258 our example above there are three options. The first option is the
1259 amount of spots that a user can request with the sh/dx command.
1260 Normally the default is to give 10 spots unless the user specifies
1261 more. Without this line enabled, the maximum a user can request is
1262 100 spots. Depending on your link quality you may wish to enable more
1263 or less by specifying the number.
1266 The other 2 options are dealt with more fully in the security section.
1269 Secondly, it is used to store the login scripts for users and nodes.
1270 Currently this can only be done by the sysop but it is envisaged that
1271 eventually users will be able to set their own. An example is
1272 included in the distibution but here is a further example.
1289 The lines in between commands can simply insert a blank line or a
1290 character such as a + sign to make the output easier to read. Simply
1291 create this script with your favourite editor and save it with the
1292 callsign of the user as the filename. Filenames should always be in
1296 Commands can be inserted in the same way for nodes. A node may wish a
1297 series of commands to be issued on login, such as a merge command for
1301 Thirdly, there are 2 default scripts for users and nodes who do not
1302 have a specifically defined script. These are user_default and
1308 Spider allows the creation of local or remote databases. It supports
1309 chained databases, allowing several different databases to be scanned
1310 with one simple command. Importing of databases is limited at present
1311 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1312 database but will expand with time.
1315 5.1. Creating databases
1317 Creating a database could not be more simple. All the commands are
1318 sent from the cluster prompt as the sysop user.
1320 To create a database you use the command dbcreate. It can be used in
1321 3 different ways like so ..
1328 To simply create a database locally, you just tell the command the
1329 name of the database. This does not create the actual database, it
1330 simply defines it to say that it exists.
1334 dbcreate <name> chain <name> [<name>...]
1338 This creates a chained database entry. The first database will be
1339 scanned, then the second, the third etc...
1343 dbcreate <name> remote <name>
1347 This creates a remote entry. the first name field is the database
1348 name at the remote node, then the remote switch, then the actual
1349 node_call of the remote node, for example...
1353 dbcreate buckmaster remote gb7dxc
1357 Remote databases cannot be chained, however, the last database in a
1358 chain can be a remote database.
1361 5.2. Importing databases
1363 The only databases that Spider can currently import are the standard
1364 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1365 This will be added to with time.
1367 To import such a database, first put the file somewhere useful like
1368 /tmp and then issue the following command ...
1372 dbimport oblast /tmp/OBLAST.FUL
1376 This will update the existing local oblast database or create it if it
1380 5.3. Checking available databases
1382 Once a database is created, you will want to check that it has been
1383 added. To do this use the dbavail command. This will output the
1384 available databases. For example ...
1389 DB Name Location Chain
1393 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1397 5.4. Looking up databases
1399 To look for information in a defined database, simply use the dbshow
1400 command, for example ...
1404 dbshow buckmaster G0YLM
1408 will show the information for the callsign G0YLM from the buckmaster
1409 database if it exists. To make things more standard for the users you
1410 can add an entry in the Aliases file so that it looks like a standard
1411 show command like this ...
1415 Now you can simply use show/buckmaster or an abreviation.
1418 5.5. Removing databases
1420 To delete an existing database you use the dbremove command. For
1429 would remove the oblast database and its associated datafile from the
1430 system. There are no warnings or recovery possible from this command.
1431 If you remove a database it ceases to exist and would have to be
1432 created from scratch if you still required it.
1435 6. Information, files and useful programs
1439 One of the more important things a cluster sysop needs to do is to get
1440 information to his users. The simplest way to do this is to have a
1441 banner that is sent to the user on login. This is know as a "message
1442 of the day" or "motd". To set this up, simply create a file in
1443 /spider/data called motd and edit it to say whatever you want. It is
1444 purely a text file and will be sent automatically to anyone logging in
1448 This message of the day file lives in the same directory as the
1449 standard motd file but is only sent to non-registered users. Once
1450 registered they will receive the same message as any other user.
1453 6.3. Downtime message
1455 If for any reason the cluster is down, maybe for upgrade or
1456 maintenance but the machine is still running, a message can be sent to
1457 the user advising them of the fact. This message lives in the
1458 /spider/data directory and is called "offline". Simply create the
1459 file and edit it to say whatever you wish. This file will be sent to
1460 a user attempting to log into the cluster when DXSpider is not
1464 6.4. Other text messages
1466 You can set other text messages to be read by the user if they input
1467 the file name. This could be for news items or maybe information for
1468 new users. To set this up, make a directory under /spider called
1469 packclus. Under this directory you can create files called news or
1470 newuser for example. In fact you can create files with any names you
1471 like. These can be listed by the user with the command ....
1479 They can be read by the user by typing the command ....
1487 If the file they want to read is called news. You could also set an
1488 alias for this in the Alias file to allow them just to type news
1491 You can also store other information in this directory, either
1492 directly or nested under directories. One use for this would be to
1493 store DX bulletins such as the OPDX bulletins. These can be listed
1494 and read by the user. To keep things tidy, make a directory under
1495 /spider/packclus called bulletin. Now copy any OPDX or similar
1496 bulletins into it. These can be listed by the user in the same way as
1497 above using the show/files command with an extension for the bulletin
1498 directory you have just created, like this ....
1506 An example would look like this ....
1509 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1513 You can see that in the files area (basically the packclus directory)
1514 there is a file called news and a directory called bulletin. You can
1515 also see that dates they were created. In the case of the file news,
1516 you can also see the time it was last modified, a good clue as to
1517 whether the file has been updated since you last read it. To read the
1518 file called news you would simply issue the command ....
1526 To look what is in the bulletin directory you issue the command ....
1531 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1532 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1533 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1534 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1535 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1536 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1537 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1538 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1539 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1540 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1541 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1542 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1543 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1544 Press Enter to continue, A to abort (16 lines) >
1548 You can now read any file in this directory using the type command,
1553 type bulletin/opdx391
1554 Ohio/Penn DX Bulletin No. 391
1555 The Ohio/Penn Dx PacketCluster
1559 Editor Tedd Mirgliotta, KB8NW
1560 Provided by BARF-80 BBS Cleveland, Ohio
1561 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1562 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1563 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1564 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1565 Press Enter to continue, A to abort (508 lines) >
1569 The page length will of course depend on what you have it set to!
1572 6.5. The Aliases file
1574 You will find a file in /spider/cmd/ called Aliases. This is the file
1575 that controls what a user gets when issuing a command. It is also
1576 possible to create your own aliases for databases and files you create
1580 You should not alter the original file in /spider/cmd/ but create a
1581 new file with the same name in /spider/local_cmd. This means that any
1582 new Aliases files that is downloaded will not overwrite your self
1583 created Aliases and also that you do not override any new Aliases with
1584 your copy in /spider/local_cmd/. You must remember that any files you
1585 store in /spider/local/ or /spider/local_cmd override the originals if
1586 the same lines are used in both files.
1589 The best way of dealing with all this then is to only put your own
1590 locally created Aliases in the copy in /spider/local_cmd. The example
1591 below is currently in use at GB7MBC.
1596 # Local Aliases File
1603 '^news$', 'type news', 'type',
1606 '^sh\w*/buck$', 'show/qrz', 'show',
1607 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1608 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1609 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1610 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1616 Each alphabetical section should be preceded by the initial letter and
1617 the section should be wrapped in square brackets as you can see. The
1618 syntax is straightforward. The first section on each line is the new
1619 command that will be allowed once the alias is included. The second
1620 section is the command it is replacing and the last section is the
1621 actual command that is being used.
1624 The eagle-eyed amongst you will have noticed that in the first
1625 section, the new alias command has a '^' at the start and a '$' at the
1626 end. Basically these force a perfect match on the alias. The '^'
1627 says match the beginning exactly and the with similar commands.
1630 I have 3 different types of alias in this file. At the top is an
1631 alias for 'news'. This is a file I have created in the
1632 /spider/packclus/ directory where I can inform users of new
1633 developments or points of interest. In it's initial form a user would
1634 have to use the command type news. The alias allows them to simply
1635 type news to get the info. Second is an alias for the show/qrz
1636 command so that those users used to the original show/buck command in
1637 AK1A will not get an error, and the rest of the lines are for locally
1638 created databases so that a user can type show/hftest instead of
1639 having to use the command dbshow hftest which is not as intuitive.
1642 This file is just an example and you should edit it to your own
1643 requirements. Once created, simply issue the command load/alias at
1644 the cluster prompt as the sysop user and the aliases should be
1651 In later versions of Spider a simple console program is provided for
1652 the sysop. This has a type ahead buffer with line editing facilities
1653 and colour for spots, announces etc. To use this program, simply use
1654 console.pl instead of client.
1657 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1658 edit the file with your favourite editor.
1661 6.7. Updating kepler data
1663 Spider has a powerful and flexible show/satellite command. In order
1664 for this to be accurate, the kepler data has to be updated regularly.
1665 In general, this data is available as an email or via cluster mail.
1666 Updating it is simple. First you need to export the mail message as a
1667 file. You do this with the export command from the cluster prompt as
1668 the sysop. For example ...
1672 export 5467 /spider/perl/keps.in
1676 would export message number 5467 as a file called keps.in in the
1677 /spider/perl directory.
1680 Now login to a VT as sysop and cd /spider/perl. There is a command in
1681 the perl directory called convkeps.pl. All we need to do now is
1682 convert the file like so ...
1686 ./convkeps.pl keps.in
1690 Now go back to the cluster and issue the command ...
1698 That is it! the kepler data has been updated.
1701 6.8. The QRZ callbook
1703 The command sh/qrz will only work once you have followed a few simple
1704 steps. First you need to get a user ID and password from qrz.com.
1705 Simply go to the site and create one. Secondly you need to copy the
1706 file /spider/perl/Internet.pm to /spider/local and alter it to match
1707 your user ID and password. You also at this point need to set
1708 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1709 proprieter of qrz.com for allowing this access.
1712 6.9. Connecting logging programs
1714 There appear to be very few logging programs out there that support
1715 telnet especially the popular ones like LogEQF, Turbolog etc. This
1716 can make it difficult to connect to your own cluster! The way to do
1717 it is to make the logging program think it has a TNC attached to a com
1718 port on the logging PC and 'push' a linux login out to it. This is
1719 achieved very simply by the use of agetty.
1722 All that is required is to add a line in /etc/inittab to have the
1723 client ready for a connection on the com port of your choice.
1724 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1729 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1733 Add this after the standard runlevel lines in /etc/inittab. The above
1734 line works on ttyS1 (com2). Now as root, issue the command telinit q
1735 and it should be ready for connection. All that is required is a 3
1736 wire serial lead (tx, rx and signal ground). Tell you logging program
1737 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1738 Login as normal and then telnet from there to the cluster.
1743 In the spider tree will be a directory spider-web. This is a neat
1744 little java web applet that can be run from a website. The applet
1745 must run on the same machine as the cluster. The included README file
1749 I should comment here that the applet is precompiled, that is, ready
1750 to go. It was compiled using JDK1.3.1. If your version is earlier
1751 than this then it may not work. Should that be the case you need to
1752 recompile or update your JDK. To recompile do the following ...
1756 cd /spider/spider-web
1758 /usr/bin/javac spiderclient.java
1762 I have used /usr/bin/javac as an example, your path to javac may be
1768 Completely based on a clx web client written in Java by dl6dbh
1769 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1771 The webserver has to run on the same machine as your DxSpider software!
1773 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1775 Installation instructions (Performed as root):
1777 Put all the files in the spider-web directory into a newly created directory
1778 under the DocumentRoot of your websever for instance 'client'. In my case
1779 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1780 path should be /usr/local/httpd/htdocs/client/ for example.
1782 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1783 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1784 /usr/local/httpd/cgi-bin/ for example.
1786 Change the permissions of the files to ensure they are correct, obviously you
1787 will need to use the correct path the the files according to your system:
1789 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1790 chmod -R 755 /home/httpd/html/client/
1792 By default the spider.cgi script should pick up your hostname (As long as this
1793 is set correctly). If it does not or your hostname differs from the name that
1794 you attach to the public address that you are using, then edit spider.cgi :
1796 # Uncomment and set the hostname manually here if the above fails.
1797 # $HOSTNAME = "gb7mbc.spoo.org" ;
1801 telnet (see Listeners.pm)
1803 NOTE: If you can start the console but cannot connect to the cluster from it,
1804 then it is possible that the machine you are on cannot resolve the hostname of
1805 your cluster machine. If this is the case, you need to set your hostname
1808 You also need to set the $NODECALL variable. This prints the name of your
1809 choosing (probably your cluster callsign) on the html page.
1811 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1815 8. Web based statistics
1817 From version 1.50, you can use the freeware software MRTG to produce
1818 really nice graphical statistics on your web site. For an example try
1819 http://www.gb7mbc.net/mrtg/stats.html.
1822 The following should help you get it all working.
1825 First you need to download the latest version of MRTG from
1826 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1827 the following files..
1831 libpng-1.0.14.tar.gz
1837 Login to your machine as the root user, put all the downloaded files
1838 in /usr/local/src/ (or wherever you prefer) and untar and compile
1839 them. All the information to compile and install these sources come
1840 with them. After compilation and installation, you will find MRTG in
1844 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1848 You now need to make 2 symbolic links like below...
1852 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1853 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1857 Now login to the cluster with your sysop callsign and run the command
1861 Now you are nearly there! Login as the sysop user and change to the
1862 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1867 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1871 Changing the callsign for your own cluster callsign of course!
1874 And finally you need to login as the root user and create one last
1875 symbolic link. Where this points will depend on where your html
1876 documents are kept. For RedHat systems you use...
1880 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1884 and for SuSE systems...
1888 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1892 If you now point your browser to your website as below it should all
1897 http://www.xxx.xxx/mrtg/stats.html
1901 Of course, to get the stats to update, you need to add some
1902 information in the spider crontab file as below...
1906 # Update stats for mrtg on website
1907 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1911 This will update the site every 5 minutes.
1916 From version 1.49 DXSpider has some additional security features.
1917 These are not by any means meant to be exhaustive, however they do
1918 afford some security against piracy. These two new features can be
1919 used independently of each other or in concert to tighten the
1925 The basic principle of registration is simple. If a user is not
1926 registered by the sysop, then they have read-only access to the
1927 cluster. The only thing they can actually send is a talk or a message
1928 to the sysop. In order for them to be able to spot, send announces or
1929 talks etc the sysop must register them with the set/register command,
1938 The user g0vgs can now fully use the cluster. In order to enable
1939 registration, you can issue the command ...
1941 set/var $main::reqreg = 1
1945 Any users that are not registered will now see the motd_nor file
1946 rather than the motd file as discussed in the Information, files and
1947 useful programs section.
1950 Entering this line at the prompt will only last for the time the
1951 cluster is running of course and would not be present on a restart.
1952 To make the change permanent, add the above line to
1953 /spider/scripts/startup. To read more on the startup file, see the
1954 section on Information, files and useful programs.
1957 To unregister a user use unset/register and to show the list of
1958 registered users, use the command show/register.
1963 At the moment, passwords only affect users who login to a DXSpider
1964 cluster node via telnet. If a user requires a password, they can
1965 either set it themselves or have the sysop enter it for them by using
1966 the set/password command. Any users who already have passwords, such
1967 as remote sysops, will be asked for their passwords automatically by
1968 the cluster. Using passwords in this way means that the user has a
1969 choice on whether to have a password or not. To force the use of
1970 passwords at login, issue the command ...
1974 set/var $main::passwdreq = 1
1978 at the cluster prompt. This can also be added to the
1979 /spider/scripts/startup file as above to make the change permanent.
1982 Of course, if you do this you will have to assign a password for each
1983 of your users. If you were asking them to register, it is anticipated
1984 that you would ask them to send you a message both to ask to be
1985 registered and to give you the password they wish to use.
1988 Should a user forget their password, it can be reset by the sysop by
1989 first removing the existing password and then setting a new one like
1994 unset/password g0vgs
1995 set/password g0vgs new_password
2003 10.1. CVS from a Linux platform
2005 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2006 is held at Sourceforge. This means that it is possible to update your
2007 DXSpider installation to the latest sources by using a few simple
2008 commands. A graphical interface to CVS for Windows is explained in
2012 Please be aware that if you update your system using CVS, it is
2013 possible that you could be running code that is very beta and not
2014 fully tested. There is a possibility that it could be unstable.
2017 I am of course assuming that you have a machine with both DXSpider and
2018 Internet access running.
2021 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2022 ENTIRE SPIDER TREE!!
2025 Assuming you are connected to the Internet, you need to login to the
2026 CVS repository and then update your Spider source. There are several
2027 steps which are listed below ...
2030 First login as the user sysop. Next you need to connect to the CVS
2031 repository. You do this with the command below ...
2034 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2038 You will get a password prompt. Simply hit return here and your
2039 machine should return to a normal linux prompt.
2042 What happens next depends on whether you have an existing installation
2043 that you want to update with the latest and greatest or whether you
2044 just want to see what is there and/or run it on a new machine for
2047 If you are installing Spider from CVS then change directory to
2050 If you are wanting to update Spider then cd to /tmp
2053 The next step will create a brand new 'spider' directory in your
2057 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2061 This command is all on one line.
2064 Hopefully your screen should show you downloading files. The -z3
2065 simply compresses the download to improve speed. When this has
2066 finished, you will have exactly the same as if you had untarred a full
2067 tarball PLUS some extra directories and files that CVS needs to do the
2069 Now if you are doing a new installation, that's it. Carry on as if
2070 you have just downloaded and untarred the lastest tarball.
2073 If you want to upgrade your current installation then do this ...
2077 tar cvfz /tmp/s.tgz spider
2079 tar xvfzp /tmp/s.tgz
2083 This is assuming you downloaded to the /tmp directory of course.
2086 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2087 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2090 Remember to recompile the C client (cd /spider/src; make)
2093 At this point the files have been upgraded. You can (usually) restart
2094 the cluster in your own time. However, if you attempt to use any new
2095 commands or features expect it to be fatal! At least your cluster
2096 will have been restarted then so it will be too late to worry about
2100 Now the magic part! From now on when you want to update, simply
2101 connect to the Internet and then, as the user sysop ...
2110 and your files will be updated. As above, remember to recompile the
2111 "C" client if it has been updated (CVS will tell you) and restart if
2112 any of the perl scripts have been altered or added, again, CVS will
2116 You will find any changes documented in the /spider/Changes file.
2119 10.2. CVS from a Windows platform
2121 After the initial setup, an update to your DXSpider software is no
2122 more than a couple of clicks away. This section is intended to
2123 explain and illustrate the use of the WinCVS application to update
2124 your DXSpider software. The current stable version of WinCVS is Ver.
2125 1.2. You can get this software at:
2127 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2129 Pick your download mirror and then install WinCVS after the download
2133 In this next section I have included a series of links to .jpg files
2134 to take advantage of the picture and 1000 words equivalency. The .jpg
2135 files are in the C:\spider\html directory. If someone using a Linux
2136 system is reading this section from boredom, the files are in
2137 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2138 of gcvs and do your updates graphically as opposed to from the command
2139 line. The following descriptions are almost identical between WinCvs
2140 and gcvs. The following screen shots have duplicate links, depending
2141 upon whether you are viewing this information under the Windows or
2142 Linux operating system.
2144 When WinCVS is installed, running, and you are connected to the
2145 internet, the initial screen looks like:
2149 If you want, you can also look at these .jpg files with another viewer
2150 that might provide some better clarity to the image. On the left is
2151 the directory tree for your hard disk. Notice that the spider
2152 directory has a gray highlight.
2154 To start configuring WinCVS, click on Admin at the top of the screen
2155 and then Preferences. This should get you:
2159 In the top line for CVSROOT, enter:
2162 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2169 "passwd" file on the cvs server
2173 for Authentication on the General tab.
2175 Next, move to the right to the Ports tab.
2179 In here, check the box on the second line down for the "pserver" port.
2180 Enter a port number of 2401.
2182 Finally, go to the WinCvs tab all the way to the right.
2186 Enter Notepad as the viewer to open files. For the HOME folder, put
2187 "C:\spider" and click OK because the configuration is now complete.
2189 You are now ready to upgrade your copy of DXSpider. Click on the
2190 greyed Spider folder shown in the directory tree on the left of the
2191 WinCVS display. Two things should happen. The Spider folder will be
2192 selected and the greyed-out arrow located just below the word Query in
2193 the top line will turn to solid green.
2195 For anyone using gcvs under Linux, the green arrow is located on the
2196 extreme left of the display, under the word File. A gcvs screen looks
2201 Click on the now green arrow to start the download process. An Update
2202 Settings box will be displayed to which you can simply say OK.
2206 For future reference, the Update Settings box is the place where you
2207 can enter information to revert to a prior version of DXSpider.
2208 Information on reverting to a Before Date is contained in the WinCVS
2211 After a short period of time, a series of file names will scroll by in
2212 the lower pane of the WinCVS window. Eventually you should see
2215 *****CVS exited normally with code 0*****
2219 appear in the lower pane. You're done. The updated files are in
2220 place ready for you to stop and then restart your DXSpider. After the
2221 restart, you're running with the latest version of DXSpider.
2225 To paraphrase from the CVS section... Now the magic part! From now on
2226 when you want to update, simply connect to the Internet and start
2230 Click on the greyed-out Spider directory in the left screen
2231 Click on the green down arrow
2232 Click OK on the Update Settings dialog box
2233 Restart your Spider software
2237 11. The DXSpider command set
2241 accept Set a filter to accept something
2243 Create a filter to accept somethingThere are 2 types of filter, accept
2244 and reject. See HELP FILTERING for moreinfo.
2246 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
2248 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2251 This version allows a sysop to set a filter for a callsign as well as
2252 thedefault for nodes and users eg:-
2255 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2259 11.3. accept/announce [0-9] <pattern> (0)
2261 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2264 Create an 'accept this announce' line for a filter. An accept filter
2265 line means that if the announce matches this filter it ispassed onto
2266 the user. See HELP FILTERING for more info. Please read thisto
2267 understand how filters work - it will save a lot of grief later on.You
2268 can use any of the following things in this line:-
2271 info <string> eg: iota or qsl by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,NH by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> channel <prefixes> wx 1 filter WX announces dest <prefixes> eg: 6MUK,WDX (distros)
2278 acc/ann dest 6MUK acc/ann 2 by_zone 14,15,16 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
2292 acc/ann by_state va,nh,ri,nh
2296 You can use the tag 'all' to accept everything eg:
2303 but this probably for advanced users...
2305 11.4. accept/route <call> [0-9] <pattern> (8)
2307 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2310 Create an 'accept this routing PC Protocol' line for a filter. An
2311 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2312 filter it is passed thru that interface. See HELP FILTERING for more
2313 info. Please read thisto understand how filters work - it will save a
2314 lot of grief later on.You can use any of the following things in this
2318 call <prefixes> the callsign of the thingy call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,NH origin <prefixes> really the interface it came in on origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,NH
2325 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2329 you can now use 'by' as a synonym for 'call' so:
2332 by = call by_dxcc = call_dxcc
2336 and so onYou can use the tag 'all' to accept everything eg:
2343 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
2345 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2347 This version allows a sysop to set a filter for a callsign as well as
2348 thedefault for nodes and users eg:-
2351 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2355 accept/spot user_default by G,M,2
2359 11.6. accept/spots [0-9] <pattern> (0)
2361 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2363 Create an 'accept this spot' line for a filter. An accept filter line
2364 means that if the spot matches this filter it ispassed onto the user.
2365 See HELP FILTERING for more info. Please read thisto understand how
2366 filters work - it will save a lot of grief later on.You can use any of
2367 the following things in this line:-
2370 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m on <range> same as 'freq' call <prefixes> eg: G,PA,HB9 info <string> eg: iota or qsl by <prefixes> call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,ME by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> eg: VA,NH,RI,ME origin <prefixes> channel <prefixes>
2374 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2378 You can use the tag 'all' to accept everything, eg:
2388 acc/spots by_state VA,NH,RI,MA,ME
2392 but this probably for advanced users...
2394 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
2396 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2398 This version allows a sysop to set a filter for a callsign as well as
2399 thedefault for nodes and users eg:-
2402 accept/wcy node_default all set/hops node_default 10
2406 11.8. accept/wcy [0-9] <pattern> (0)
2408 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2410 It is unlikely that you will want to do this, but if you do then you
2411 canfilter on the following fields:-
2414 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
2418 There are no examples because WCY Broadcasts only come from one place
2419 andyou either want them or not (see UNSET/WCY if you don't want
2420 them).This command is really provided for future use.See HELP FILTER
2423 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
2425 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2427 This version allows a sysop to set a filter for a callsign as well as
2428 thedefault for nodes and users eg:-
2431 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2435 accept/wwv user_default by W,K
2439 11.10. accept/wwv [0-9] <pattern> (0)
2441 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2443 It is unlikely that you will want to do this, but if you do then you
2444 canfilter on the following fields:-
2447 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
2454 accept/wwv by_zone 4
2458 is probably the only useful thing to do (which will only show WWV
2459 broadcastsby stations in the US).See HELP FILTER for information.
2461 11.11. announce <text> (0)
2463 announce <text> Send an announcement to LOCAL users only
2465 <text> is the text of the announcement you wish to broadcast
2467 11.12. announce full <text> (0)
2469 announce full <text> Send an announcement cluster wide
2471 This will send your announcement cluster wide
2473 11.13. announce sysop <text> (5)
2475 announce sysop <text> Send an announcement to Sysops only
2478 11.14. apropos <string> (0)
2480 apropos <string> Search help database for <string>
2482 Search the help database for <string> (it isn't case sensitive), and
2483 printthe names of all the commands that may be relevant.
2485 11.15. blank [<string>] [<nn>] (0)
2487 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2489 In its basic form this command prints one or more blank lines. However
2490 ifyou pass it a string it will replicate the string for the width of
2491 the screen (default 80) and then print that one or more times, so:
2498 prints two blank lines
2505 prints a row of - characters once.
2512 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2513 script file and you can print a maximumof 9 lines.
2517 bye Exit from the cluster
2519 This will disconnect you from the cluster
2521 11.17. catchup <node call> all|[<msgno> ...] (5)
2523 catchup <node call> all|[<msgno> ...] Mark a message as sent
2526 11.18. clear/announce <callsign> [input] [0-9|all] (8)
2528 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2531 A sysop can clear an input or normal output filter for a user or
2532 thenode_default or user_default.
2534 11.19. clear/announce [1|all] (0)
2536 clear/announce [1|all] Clear a announce filter line
2538 This command allows you to clear (remove) a line in a annouce filter
2539 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2542 11.20. clear/route <callsign> [input] [0-9|all] (8)
2544 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2546 A sysop can clear an input or normal output filter for a user or
2547 thenode_default or user_default.
2549 11.21. clear/route [1|all] (0)
2551 clear/route [1|all] Clear a route filter line
2553 This command allows you to clear (remove) a line in a route filter or
2554 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2557 11.22. clear/spots <callsign> [input] [0-9|all] (8)
2559 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2561 A sysop can clear an input or normal output filter for a user or
2562 thenode_default or user_default.
2564 11.23. clear/spots [0-9|all] (0)
2566 clear/spots [0-9|all] Clear a spot filter line
2568 This command allows you to clear (remove) a line in a spot filter or
2569 to remove the whole filter.If you have a filter:-
2572 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2582 you will be left with:-
2585 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2596 the filter will be completely removed.
2598 11.24. clear/wcy <callsign> [input] [0-9|all] (8)
2600 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2602 A sysop can clear an input or normal output filter for a user or
2603 thenode_default or user_default.
2605 11.25. clear/wcy [1|all] (0)
2607 clear/wcy [1|all] Clear a WCY filter line
2609 This command allows you to clear (remove) a line in a WCY filter or to
2610 remove the whole filter.see CLEAR/SPOTS for a more detailed
2613 11.26. clear/wwv <callsign> [input] [0-9|all] (8)
2615 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2617 A sysop can clear an input or normal output filter for a user or
2618 thenode_default or user_default.
2620 11.27. clear/wwv [1|all] (0)
2622 clear/wwv [1|all] Clear a WWV filter line
2624 This command allows you to clear (remove) a line in a WWV filter or to
2625 remove the whole filter.see CLEAR/SPOTS for a more detailed
2628 11.28. connect <callsign> (5)
2630 connect <callsign> Start a connection to another DX Cluster
2632 Start a connection process that will culminate in a new connection to
2633 theDX cluster <callsign>. This process creates a new 'client' process
2634 which willuse the script in /spider/connect/<callsign> to effect the
2635 'chat' exchangenecessary to traverse the network(s) to logon to the
2640 dbavail Show a list of all the Databases in the system
2642 Title says it all really, this command lists all the databases
2643 definedin the system. It is also aliased to SHOW/COMMAND.
2644 11.30. dbshow <dbname> <key> (0)
2646 dbshow <dbname> <key> Display an entry, if it exists, in a database
2648 This is the generic user interface to the database to the database
2649 system.It is expected that the sysop will add an entry to the local
2650 Aliases fileso that users can use the more familiar AK1A style of
2658 but if he hasn't and the database really does exist (use DBAVAIL
2659 orSHOW/COMMAND to find out) you can do the same thing with:
2666 11.31. directory (0)
2668 directory List messages
2671 11.32. directory <from>-<to> (0)
2673 directory <from>-<to> List messages <from> message <to> message
2675 List the messages in the messages directory.If there is a 'p' one
2676 space after the message number then it is a personal message. If there
2677 is a '-' between the message number and the'p' then this indicates
2678 that the message has been read.You can use shell escape characters
2679 such as '*' and '?' in the <call>fields.You can combine some of the
2680 various directory commands together eg:-
2690 DIR SUBJECT IOTA 200-250
2694 You can abbreviate all the commands to one letter and use ak1a syn-
2698 DIR/T G1* 10 DIR/S QSL 10-100 5
2702 11.33. directory <nn> (0)
2704 directory <nn> List last <nn> messages
2708 11.34. directory all (0)
2710 directory all List all messages
2713 11.35. directory from <call> (0)
2715 directory from <call> List all messages from <call>
2718 11.36. directory new (0)
2720 directory new List all new messages
2723 11.37. directory own (0)
2725 directory own List your own messages
2728 11.38. directory subject <string> (0)
2730 directory subject <string> List all messages with <string> in subject
2733 11.39. directory to <call> (0)
2735 directory to <call> List all messages to <call>
2738 11.40. directory- (5)
2742 Sysops can see all users' messages.
2744 11.41. disconnect <call> [<call> ...] (8)
2746 disconnect <call> [<call> ...] Disconnect a user or cluster
2748 Disconnect any <call> connected locally
2750 11.42. dx [by <call>] <freq> <call> <remarks> (0)
2752 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2754 This is how you send a DX Spot to other users. You can, in fact,
2755 nowenter the <freq> and the <call> either way round.
2758 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
2762 will all give the same result. You can add some remarks to the endof
2763 the command and they will be added to the spot.
2766 DX FR0G 144600 this is a test
2770 You can credit someone else by saying:-
2774 DX by G1TLH FR0G 144.600 he isn't on the cluster
2778 The <freq> is compared against the available bands set up in the clus-
2779 ter. See SHOW/BANDS for more information.
2781 11.43. echo <line> (0)
2783 echo <line> Echo the line to the output
2785 This command is useful in scripts and so forth for printing theline
2786 that you give to the command to the output. You can use thisin
2787 user_default scripts and the SAVE command for titling and so forthThe
2788 script will interpret certain standard "escape" sequences as follows:-
2791 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
2795 So the following example:-
2798 echo GB7DJK is a dxcluster
2805 GB7DJK is a dxcluster
2809 on the output. You don't need a \n on the end of the line you want to
2810 send.A more complex example:-
2813 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
2820 GB7DJK g1tlh Dirk g3xvf Richard
2826 11.44. filtering... (0)
2828 filtering... Filtering things in DXSpider
2830 There are a number of things you can filter in the DXSpider system.
2831 Theyall use the same general mechanism.In general terms you can create
2832 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
2833 You do this using, for example:-
2836 accept/spots ..... reject/spots .....
2840 where ..... are the specific commands for that type of filter. There-
2841 are filters for spots, wwv, announce, wcy and (for sysops)connects.
2842 See each different accept or reject command reference formore
2843 details.There is also a command to clear out one or more lines in a
2844 filter andone to show you what you have set. They are:-
2847 clear/spots 1 clear/spots all
2858 There is clear/xxxx command for each type of filter.For now we are
2859 going to use spots for the examples, but you can applythe principles
2860 to all types of filter.There are two main types of filter 'accept' or
2861 'reject'; which you usedepends entirely on how you look at the world
2862 and what is leastwriting to achieve what you want. Each filter has 10
2863 lines (of anylength) which are tried in order. If a line matches then
2864 the actionyou have specified is taken (ie reject means ignore it and
2865 acceptmeans gimme it).The important thing to remember is that if you
2866 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
2867 instance)) then ifa spot comes in that doesn't match any of the lines
2868 then you will getit BUT if you specify an 'accept' filter then any
2869 spots that don'tmatch are dumped. For example if I have a one line
2873 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2877 then automatically you will ONLY get VHF spots from or to CQ zones
2878 1415 and 16. If you set a reject filter like:
2881 reject/spots on hf/cw
2885 Then you will get everything EXCEPT HF CW spots, If you am interested
2886 in IOTAand will work it even on CW then you could say:-
2889 reject/spots on hf/cw and not info iota
2893 But in that case you might only be interested in iota and say:-
2896 accept/spots not on hf/cw or info iota
2900 which is exactly the same. You should choose one or the other untilyou
2901 are confortable with the way it works. Yes, you can mix them(actually
2902 you can have an accept AND a reject on the same line) butdon't try
2903 this at home until you can analyse the results that you getwithout
2904 ringing up the sysop for help.Another useful addition now is filtering
2906 accept/spots by_state VA,NH,RI,ME
2910 You can arrange your filter lines into logical units, either for
2911 yourown understanding or simply convenience. I have one set fre-
2915 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2919 What this does is to ignore all HF CW spots (being a class B I
2920 can'tread any CW and couldn't possibly be interested in HF :-) and
2921 alsorejects any spots on VHF which don't either originate or spot
2922 someonein Europe.This is an exmaple where you would use the line num-
2923 ber (1 and 2 inthis case), if you leave the digit out, the system
2924 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
2925 out if you want, it is implied. You canuse any number of brackets to
2926 make the 'expression' as you wantit. There are things called prece-
2927 dence rules working here which meanthat you will NEED brackets in a
2928 situation like line 2 because,without it, will assume:-
2931 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2935 annoying, but that is the way it is. If you use OR - usebrackets.
2936 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
2937 by_zone'.If you want to alter your filter you can just redefine one or
2938 morelines of it or clear out one line. For example:-
2941 reject/spots 1 on hf/ssb
2952 To remove the filter in its entirty:-
2959 There are similar CLEAR commands for the other filters:-
2962 clear/announce clear/wcy clear/wwv
2966 ADVANCED USERS:-Once you are happy with the results you get, you may
2967 like to experiment. my example that filters hf/cw spots and accepts
2968 vhf/uhf spots from EUcan be written with a mixed filter, eg:
2972 rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
2976 each filter slot actually has a 'reject' slot and an 'accept'slot. The
2977 reject slot is executed BEFORE the accept slot.It was mentioned ear-
2978 lier that after a reject test that doesn't match,the default for fol-
2979 lowing tests is 'accept', the reverse is true for'accept'. In the
2980 example what happens is that the reject is executedfirst, any non
2981 hf/cw spot is passed to the accept line, which letsthru everything
2982 else on HF.The next filter line lets through just VHF/UHF spots from
2985 11.45. forward/latlong <node_call> (8)
2987 forward/latlong <node_call> Send latitude and longitude information to
2990 This command sends all the latitude and longitude information that
2991 yourcluster is holding against callsigns. One advantage of recieving
2992 thisinformation is that more locator information is held by you.
2993 Thismeans that more locators are given on the DX line assuming you
2994 haveSET/DXGRID enabled. This could be a LOT of information though,
2995 soit is not recommended on slow links.
2997 11.46. forward/opernam <call> (1)
2999 forward/opernam <call> Send out information on this <call> to all
3002 This command sends out any information held in the user file which can
3003 be broadcast in PC41 protocol packets. This information is Name, QTH,
3004 Locationand Homenode. PC41s are only sent for the information that is
3009 help The HELP Command
3011 HELP is available for a number of commands. The syntax is:-
3018 Where <cmd> is the name of the command you want help on.All commands
3019 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3020 can be shortened to AN and so on.Look at the APROPOS <string> command
3021 which will search the help databasefor the <string> you specify and
3022 give you a list of likely commandsto look at with HELP.
3024 11.48. init <node> (5)
3026 init <node> Re-initialise a link to an AK1A compatible node
3028 This command attempts to re-initialise a link to a (usually) AK1A
3029 nodethat has got confused, usually by a protocol loop of some kind. It
3030 maywork - but you usually will be better off simply disconnecting it
3031 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3032 <yournode>).Best of luck - you will need it.
3038 As a sysop you can kill any message on the system.
3040 11.50. kill <from msgno>-<to msgno> (0)
3042 kill <from msgno>-<to msgno> Delete a range of messages
3045 11.51. kill <from>-<to> (5)
3047 kill <from>-<to> Remove a range of messages from the system
3050 11.52. kill <msgno> [<msgno..] (0)
3052 kill <msgno> [<msgno..] Delete a message from the local system
3055 11.53. kill <msgno> [<msgno> ...] (0)
3057 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3059 You can get rid of any message to or originating from your callsign
3060 using this command. You can remove more than one message at a time.
3062 11.54. kill expunge <msgno> [<msgno..] (6)
3064 kill expunge <msgno> [<msgno..] Expunge a message
3066 Deleting a message using the normal KILL commands only marks that
3067 messagefor deletion. The actual deletion only happens later (usually
3068 two days later).The KILL EXPUNGE command causes the message to be
3069 truly deleted more or lessimmediately.It otherwise is used in the same
3070 way as the KILL command.
3072 11.55. kill from <call> (5)
3074 kill from <call> Remove all messages from a callsign
3077 11.56. kill full <msgno> [<msgno..] (5)
3079 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3081 Delete a message from the local system. You will only be able todelete
3082 messages that you have originated or been sent (unless you arethe
3090 Will delete all the messages that you own between msgnos 1234 and
3098 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3104 will delete all messages to g1tlh.
3111 will delete a message (usually a 'bulletin') from the whole cluster
3112 system. This uses the subject field, so any messages that have exactly
3113 thesame subject will be deleted. Beware!
3115 11.57. kill full <msgno> [<msgno] (5)
3117 kill full <msgno> [<msgno] Remove a message from the entire cluster
3119 Remove this message from the entire cluster system as well as your
3122 11.58. kill to <call> (5)
3124 kill to <call> Remove all messages to a callsign
3127 11.59. kill from <regex> (0)
3129 kill from <regex> Delete messages FROM a callsign or pattern
3132 11.60. kill to <regex> (0)
3134 kill to <regex> Delete messages TO a callsign or pattern
3139 links Show which nodes is physically connected
3141 This is a quick listing that shows which links are connected andsome
3142 information about them. See WHO for a list of all connections.
3144 11.62. load/keps (5)
3146 load/keps Load new keps data
3149 11.63. load/keps [nn] (5)
3151 load/keps [nn] Load new keps data from message
3153 If there is no message number then reload the current Keps data
3154 fromthe Keps.pm data file. You create this file by running
3157 /spider/perl/convkeps.pl <filename>
3161 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3162 there is a message number, then it will take the message, runcon-
3163 vkeps.pl on it and then load the data, all in one step.These messages
3164 are sent to ALL by GB7DJK (and others) from time to time.
3166 11.64. merge <node> [<no spots>/<no wwv>] (5)
3168 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3170 MERGE allows you to bring your spot and wwv database up to date. By
3171 defaultit will request the last 10 spots and 5 WWVs from the node you
3172 select. The node must be connected locally.You can request any number
3173 of spots or wwv and although they will be appendedto your databases
3174 they will not duplicate any that have recently been added (the last 2
3175 days for spots and last month for WWV data).
3177 11.65. pc <call> <text> (8)
3179 pc <call> <text> Send arbitrary text to a connected callsign
3181 Send some arbitrary text to a locally connected callsign. Noprocessing
3182 is done on the text. This command allows you to send PCProtocol to
3183 unstick things if problems arise (messages get stucketc). eg:-
3186 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3193 pc G1TLH Try doing that properly!!!
3197 Send any text you like to the callsign requested. This is used mainly
3198 to sendPC protocol to connected nodes either for testing or to unstick
3199 things. You can also use in the same way as a talk command to a con-
3200 nected user butwithout any processing, added of "from <blah> to <blah"
3203 11.66. ping <node call> (1)
3205 ping <node call> Check the link quality between nodes
3207 This command allows you to send a frame to another cluster node onthe
3208 network and get a return frame. The time it takes to do thisis a good
3209 indication of the quality of the link. The actual timeit takes is
3210 output to the console in seconds.Any visible cluster node can be
3213 11.67. rcmd <node call> <cmd> (1)
3215 rcmd <node call> <cmd> Send a command to another DX Cluster
3217 This command allows you to send nearly any command to another DX
3218 Clusternode that is connected to the system. Whether you get any
3219 output is dependant on a) whether the other system knowsthat the node
3220 callsign of this cluster is in fact a node b) whether theother system
3221 is allowing RCMDs from this node and c) whether you havepermission to
3222 send this command at all.
3226 read Read the next unread personal message addressed to you
3229 11.69. read <msgno> (0)
3231 read <msgno> Read the specified message
3233 You can read any messages that are sent as 'non-personal' and also
3234 anymessage either sent by or sent to your callsign.
3240 As a sysop you may read any message on the system
3244 reject Set a filter to reject something
3246 Create a filter to reject somethingThere are 2 types of filter, accept
3247 and reject. See HELP FILTERING for moreinfo.
3249 11.72. reject/announce <call> [input] [0-9] <pattern> (8)
3251 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3254 This version allows a sysop to set a filter for a callsign as well as
3255 thedefault for nodes and users eg:-
3258 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3262 11.73. reject/announce [0-9] <pattern> (0)
3264 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3267 Create an 'reject this announce' line for a filter. A reject filter
3268 line means that if the announce matches this filter it ispassed onto
3269 the user. See HELP FILTERING for more info. Please read thisto
3270 understand how filters work - it will save a lot of grief later on.You
3271 can use any of the following things in this line:-
3274 info <string> eg: iota or qsl by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,ME by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> eg: VA,NH,RI,ME channel <prefixes> wx 1 filter WX announces dest <prefixes> eg: 6MUK,WDX (distros)
3281 rej/ann by_zone 14,15,16 and not by G,M,2
3285 You can use the tag 'all' to reject everything eg:
3292 but this probably for advanced users...
3294 11.74. reject/route <call> [0-9] <pattern> (8)
3296 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3299 Create an 'reject this routing PC Protocol' line for a filter. An
3300 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3301 filter it is NOT passed thru that interface. See HELP FILTERING for
3302 more info. Please read this to understand how filters work - it will
3303 save a lot of grief later on.You can use any of the following things
3307 call <prefixes> the callsign of the thingy call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,ME origin <prefixes> really the interface it came in on origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> origin_state <states> eg: VA,NH,RI,ME
3314 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3318 You can use the tag 'all' to reject everything eg:
3321 rej/route all (equiv to [very] restricted mode)
3325 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3327 11.75. reject/spots <call> [input] [0-9] <pattern> (8)
3329 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3331 This version allows a sysop to set a filter for a callsign as well as
3332 thedefault for nodes and users eg:-
3335 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3339 reject/spot user_default by G,M,2
3343 11.76. reject/spots [0-9] <pattern> (0)
3345 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3347 Create a 'reject this spot' line for a filter. A reject filter line
3348 means that if the spot matches this filter it isdumped (not passed
3349 on). See HELP FILTERING for more info. Please read thisto understand
3350 how filters work - it will save a lot of grief later on.You can use
3351 any of the following things in this line:-
3354 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m on <range> same as 'freq' call <prefixes> eg: G,PA,HB9 info <string> eg: iota or qsl by <prefixes> call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) call_itu <prefixes or numbers> or: G,GM,GW call_zone <prefixes or numbers> call_state <states> eg: VA,NH,RI,ME by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> by_state <states> eg: VA,NH,RI,ME origin <prefixes> channel <prefixes>
3358 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3362 You can use the tag 'all' to reject everything eg:
3369 but this probably for advanced users...
3371 11.77. reject/wcy <call> [input] [0-9] <pattern> (8)
3373 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3375 This version allows a sysop to set a filter for a callsign as well as
3376 thedefault for nodes and users eg:-
3379 reject/wcy gb7djk all
3383 11.78. reject/wcy [0-9] <pattern> (0)
3385 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3387 It is unlikely that you will want to do this, but if you do then you
3388 canfilter on the following fields:-
3391 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
3395 There are no examples because WCY Broadcasts only come from one place
3396 andyou either want them or not (see UNSET/WCY if you don't want
3397 them).This command is really provided for future use.See HELP FILTER
3400 11.79. reject/wwv <call> [input] [0-9] <pattern> (8)
3402 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3404 This version allows a sysop to set a filter for a callsign as well as
3405 thedefault for nodes and users eg:-
3408 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3412 reject/wwv user_default by W
3416 11.80. reject/wwv [0-9] <pattern> (0)
3418 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3420 It is unlikely that you will want to do this, but if you do then you
3421 canfilter on the following fields:-
3424 by <prefixes> eg: G,M,2 origin <prefixes> origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G) origin_itu <prefixes or numbers> or: G,GM,GW origin_zone <prefixes or numbers> by_dxcc <prefixes or numbers> by_itu <prefixes or numbers> by_zone <prefixes or numbers> channel <prefixes>
3431 reject/wwv by_zone 14,15,16
3435 is probably the only useful thing to do (which will only show WWV
3436 broadcastsby stations in the US).See HELP FILTER for information.
3440 reply Reply (privately) to the last message that you have read
3443 11.82. reply <msgno> (0)
3445 reply <msgno> Reply (privately) to the specified message
3448 11.83. reply b <msgno> (0)
3450 reply b <msgno> Reply as a Bulletin to the specified message
3453 11.84. reply noprivate <msgno> (0)
3455 reply noprivate <msgno> Reply as a Bulletin to the specified message
3458 11.85. reply rr <msgno> (0)
3460 reply rr <msgno> Reply to the specified message with read receipt
3462 You can reply to a message and the subject will automatically
3463 have"Re:" inserted in front of it, if it isn't already present.You can
3464 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3465 that you can use with the SEND command (see SENDfor further details)
3467 11.86. send <call> [<call> ...] (0)
3469 send <call> [<call> ...] Send a message to one or more callsigns
3472 11.87. send copy <msgno> <call> (0)
3474 send copy <msgno> <call> Send a copy of a message to someone
3477 11.88. send noprivate <call> (0)
3479 send noprivate <call> Send a message to all stations
3481 All the SEND commands will create a message which will be sent either
3482 toan individual callsign or to one of the 'bulletin' addresses. SEND
3483 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3484 will mark the message as personal and send it to the cluster node
3485 thatthat callsign is connected to. If the <call> you have specified is
3486 in facta known bulletin category on your node (eg: ALL) then the
3487 message shouldautomatically become a bulletin.You can have more than
3488 one callsign in all of the SEND commands.You can have multiple
3489 qualifiers so that you can have for example:-
3490 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3494 which should send a copy of message 123 to G1TLH and G0RDI and you
3495 willreceive a read receipt when they have read the message.SB is an
3496 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3497 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3498 tionally this should be no longer than 29 characters for compatibil-
3499 ity. Most modern clustersoftware should accept more.You will now be
3500 prompted to start entering your text. You finish the message by enter-
3501 ing '/EX' on a new line. For instance:
3504 ... bye then Jim 73 Dirk /ex
3508 If you have started a message and you don't want to keep it then you-
3509 can abandon the message with '/ABORT' on a new line, like:-
3512 line 1 line 2 oh I just can't be bothered with this /abort
3516 If you abort the message it will NOT be sent.When you are entering the
3517 text of your message, most normal output (suchas DX announcements and
3518 so on are suppressed and stored for latter display(upto 20 such lines
3519 are stored, as new ones come along, so the oldestlines are
3520 dropped).Also, you can enter normal commands commands (and get the
3521 output immediately) whilst in the middle of a message. You do this by
3522 typingthe command preceeded by a '/' character on a new line, so:-
3525 /dx g1tlh 144010 strong signal
3529 Will issue a dx annoucement to the rest of the cluster. Also, you can
3530 add the output of a command to your message by preceeding the command
3538 This will show YOU the output from SH/VHFTABLE and also store it in
3539 themessage. You can carry on with the message until you are ready to
3542 11.89. send private <call> (0)
3544 send private <call> Send a personal message
3547 11.90. send rr <call> (0)
3549 send rr <call> Send a message and ask for a read receipt
3552 11.91. set/address <your address> (0)
3554 set/address <your address> Record your postal address
3556 11.92. set/announce (0)
3558 set/announce Allow announce messages to come out on your terminal
3561 11.93. set/anntalk (0)
3563 set/anntalk Allow talk like announce messages on your terminal
3566 11.94. set/arcluster <call> [<call>..] (5)
3568 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
3571 11.95. set/baddx <call>.. (8)
3573 set/baddx <call>.. Stop callsigns in a dx spot being propagated
3576 11.96. set/badnode <call>.. (8)
3578 set/badnode <call>.. Stop spots from this node being propagated
3581 11.97. set/badspotter <call>.. (8)
3583 set/badspotter <call>.. Stop spots from this callsign being propagated
3586 11.98. set/badword <word>.. (8)
3588 set/badword <word>.. Stop things with this word being propagated
3591 11.99. set/bbs <call> [<call>..] (5)
3593 set/bbs <call> [<call>..] Make the callsign a BBS
3596 11.100. set/beep (0)
3598 set/beep Add a beep to DX and other messages on your terminal
3601 11.101. set/clx <call> [<call>..] (5)
3603 set/clx <call> [<call>..] Make the callsign an CLX node
3608 set/dx Allow DX messages to come out on your terminal
3611 11.103. set/dxgrid (0)
3613 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
3616 11.104. set/dxnet <call> [<call>..] (5)
3618 set/dxnet <call> [<call>..] Make the callsign an DXNet node
3622 11.105. set/echo (0)
3624 set/echo Make the cluster echo your input
3627 11.106. set/email <email> ... (0)
3629 set/email <email> ... Set email address(es) and forward your personals
3632 11.107. set/here (0)
3634 set/here Tell the system you are present at your terminal
3637 11.108. set/homenode <node> (0)
3639 set/homenode <node> Set your normal cluster callsign
3641 Tell the cluster system where you normally connect to. Any Messages
3642 sentto you will normally find their way there should you not be
3650 11.109. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
3652 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
3655 11.110. set/language <lang> (0)
3657 set/language <lang> Set the language you want to use
3659 You can select the language that you want the cluster to use.
3660 Currentlythe languages available are en (English), de (German), es
3661 (Spanish) and nl (Dutch).
3663 11.111. set/location <lat & long> (0)
3665 set/location <lat & long> Set your latitude and longitude
3668 11.112. set/logininfo (0)
3670 set/logininfo Inform when a station logs in locally
3673 11.113. set/name <your name> (0)
3675 set/name <your name> Set your name
3677 Tell the system what your name is eg:-
3684 11.114. set/node <call> [<call>..] (5)
3686 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
3689 andfed PC Protocol rather normal user commands.
3691 11.115. set/obscount <count> <call> (8)
3693 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
3695 From 1.35 onwards neighbouring nodes are pinged at regular intervals
3696 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
3697 'pump-up'counter which is decremented on every outgoing ping and then
3698 reset tothe 'obscount' value on every incoming ping. The default value
3699 of thisparameter is 2. What this means is that a neighbouring node
3700 will be pinged twice at (default) 300 second intervals and if no reply
3701 has been heard just beforewhat would be the third attempt, that node
3702 is disconnected.If a ping is heard then the obscount is reset to the
3703 full value. Usingdefault values, if a node has not responded to a ping
3704 within 15 minutes,it is disconnected.You can set this parameter
3705 between 1 and 9.It is STRONGLY recommended that you don't change the
3708 11.116. set/page <lines per page> (0)
3710 set/page <lines per page> Set the lines per page
3712 Tell the system how many lines you wish on a page when the number of
3713 lineof output from a command is more than this. The default is 20.
3714 Setting itexplicitly to 0 will disable paging.
3717 SET/PAGE 30 SET/PAGE 0
3721 The setting is stored in your user profile.
3723 11.117. set/password (0)
3725 set/password Set your own password
3727 This command only works for a 'telnet' user (currently). It willonly
3728 work if you have a password already set. This initial passwordcan only
3729 be set by the sysop.When you execute this command it will ask you for
3730 your old password,then ask you to type in your new password twice (to
3731 make sure youget it right). You may or may not see the data echoed on
3732 the screenas you type, depending on the type of telnet client you
3735 11.118. set/prompt <string> (0)
3737 set/prompt <string> Set your prompt to <string>
3740 11.119. set/qra <locator> (0)
3742 set/qra <locator> Set your QRA Grid locator
3744 Tell the system what your QRA (or Maidenhead) locator is. If you have
3745 notdone a SET/LOCATION then your latitude and longitude will be set
3746 roughlycorrectly (assuming your locator is correct ;-). For example:-
3754 11.120. set/qth <your qth> (0)
3756 set/qth <your qth> Set your QTH
3758 Tell the system where you are. For example:-
3761 SET/QTH East Dereham, Norfolk
3765 11.121. set/spider <call> [<call>..] (5)
3767 set/spider <call> [<call>..] Make the callsign an DXSpider node
3769 Tell the system that the call(s) are to be treated as DXSpider node
3770 andfed new style DX Protocol rather normal user commands.
3772 11.122. set/talk (0)
3774 set/talk Allow TALK messages to come out on your terminal
3779 set/wcy Allow WCY messages to come out on your terminal
3784 set/wwv Allow WWV messages to come out on your terminal
3789 set/wx Allow WX messages to come out on your terminal
3792 11.126. show/baddx (1)
3794 show/baddx Show all the bad dx calls in the system
3796 Display all the bad dx callsigns in the system, see SET/BADDXfor more
3799 11.127. show/badnode (1)
3801 show/badnode Show all the bad nodes in the system
3803 Display all the bad node callsigns in the system, see SET/BADNODEfor
3806 11.128. show/badspotter (1)
3808 show/badspotter Show all the bad spotters in the system
3810 Display all the bad spotter's callsigns in the system, see
3811 SET/BADSPOTTERfor more information.
3814 11.129. show/badword (1)
3816 show/badword Show all the bad words in the system
3818 Display all the bad words in the system, see SET/BADWORDfor more
3821 11.130. show/configuration [<node>] (0)
3823 show/configuration [<node>] Show all the nodes and users visible
3825 This command allows you to see all the users that can be seenand the
3826 nodes to which they are connected.This command is normally abbreviated
3827 to: sh/cNormally, the list returned will be just for the nodes from
3828 your country (because the list otherwise will be very long).
3835 will produce a complete list of all nodes. BE WARNED: the list that is
3836 returned can be VERY longIt is possible to supply a node or part of a
3837 prefix and you will get a list of the users for that node or list of
3838 nodes starting withthat prefix.
3849 11.131. show/configuration/node (0)
3851 show/configuration/node Show all the nodes connected locally
3853 Show all the nodes connected to this node.
3855 11.132. show/connect (1)
3857 show/connect Show all the active connections
3859 This command shows information on all the active connections known
3860 tothe node. This command gives slightly more information than WHO.
3862 11.133. show/date [<prefix>|<callsign>] (0)
3864 show/date [<prefix>|<callsign>] Show the local time
3866 This is very nearly the same as SHOW/TIME, the only difference the
3867 formatof the date string if no arguments are given.If no prefixes or
3868 callsigns are given then this command returns the localtime and UTC as
3869 the computer has it right now. If you give some prefixesthen it will
3870 show UTC and UTC + the local offset (not including DST) atthe prefixes
3871 or callsigns that you specify.
3875 show/dx Interrogate the spot database
3877 If you just type SHOW/DX you will get the last so many spots(sysop
3878 configurable, but usually 10).In addition you can add any number of
3879 these commands in very nearlyany order to the basic SHOW/DX command,
3883 on <band> - eg 160m 20m 2m 23cm 6mm on <region> - eg hf vhf uhf shf (see SHOW/BANDS) on <from>/<to> - eg 1000/4000 14000-30000 (in Khz) <from>-<to>
3887 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
3891 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
3895 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
3899 info <text> - any spots containing <text> in the info or remarks
3903 by <call> - any spots spotted by <call> (spotter <call> is the same).
3907 qsl - this automatically looks for any qsl info on the call held in the spot database.
3911 iota [<iota>] - If the iota island number is missing it will look for the string iota and anything which looks like an iota island number. If you specify then it will look for that island.
3915 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
3919 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
3923 You can also use this with the 'by' keyword so eg by W dxcc
3931 SH/DX 9m0 SH/DX on 20m info iota SH/DX 9a on vhf day 30 SH/DX rf1p qsl SH/DX iota SH/DX iota eu-064 SH/DX qra jn86 SH/DX dxcc oq2 SH/DX dxcc oq2 by w dxcc
3935 11.135. show/dxcc <prefix> (0)
3937 show/dxcc <prefix> Interrogate the spot database by country
3939 This command takes the <prefix> (which can be a full or partial
3940 callsign if desired), looks up which internal country number it isand
3941 then displays all the spots as per SH/DX for that country.This is now
3942 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
3946 SH/DXCC G SH/DXCC W on 20m iota
3950 This can be done with the SHOW/DX command like this:-
3953 SH/DX dxcc g SH/DX dxcc w on 20m iota
3957 11.136. show/dxstats [days] [date] (0)
3959 show/dxstats [days] [date] Show the DX Statistics
3961 Show the total DX spots for the last <days> no of days (default is
3962 31), starting from a <date> (default: today).
3964 11.137. show/files [<filearea> [<string>]] (0)
3966 show/files [<filearea> [<string>]] List the contents of a filearea
3968 SHOW/FILES on its own will show you a list of the various
3969 fileareasavailable on the system. To see the contents of a particular
3977 where <filearea> is the name of the filearea you want to see the con-
3978 tents of.You can also use shell globbing characters like '*' and '?'
3979 in astring to see a selection of files in a filearea eg:-
3983 SH/FILES bulletins arld*
3987 See also TYPE - to see the contents of a file.
3989 11.138. show/filter (0)
3991 show/filter Show the contents of all the filters you have set
3993 Show the contents of all the filters that are set. This command
3994 displaysall the filters set - for all the various categories.
3996 11.139. show/hfstats [days] [date] (0)
3998 show/hfstats [days] [date] Show the HF DX Statistics
4000 Show the HF DX spots breakdown by band for the last <days> no of days
4001 (default is 31), starting from a <date> (default: today).
4003 11.140. show/hftable [days] [date] [prefix ...] (0)
4005 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4007 Show the HF DX Spotter table for the list of prefixes for the last
4008 <days> no of days (default is 31), starting from a <date> (default:
4009 today).If there are no prefixes then it will show the table for your
4010 country.Remember that some countries have more than one "DXCC country"
4011 in them(eg G :-), to show them (assuming you are not in G already
4012 which isspecially treated in the code) you must list all the relevant
4016 sh/hftable g gm gd gi gj gw gu
4020 Note that the prefixes are converted into country codes so you don't
4021 haveto list all possible prefixes for each country.If you want more or
4022 less days than the default simply include thenumber you require:-
4029 If you want to start at a different day, simply add the date in some
4033 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4037 This will show the stats for your DXCC for that CQWW contest weekend.
4038 You can specify either prefixes or full callsigns (so you can see how
4039 youdid against all your mates). You can also say 'all' which will then
4040 printthe worldwide statistics.
4047 11.141. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4049 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4052 This command shows the hop counts set up for a node. You can
4053 specifywhich category you want to see. If you leave the category out
4054 then all the categories will be listed.
4056 11.142. show/isolate (1)
4058 show/isolate Show list of ISOLATED nodes
4061 11.143. show/log [<callsign>] (8)
4063 show/log [<callsign>] Show excerpts from the system log
4065 This command outputs a short section of the system log. On its ownit
4066 will output a general logfile. With the optional callsign it willshow
4067 output from the log associated with that callsign.
4069 11.144. show/moon [ndays] [<prefix>|<callsign>] (0)
4071 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4073 Show the Moon rise and set times for a (list of) prefixes or
4074 callsigns, together with the azimuth and elevation of the sun
4075 currently at thoselocations.If you don't specify any prefixes or
4076 callsigns, it will show the times foryour QTH (assuming you have set
4077 it with either SET/LOCATION or SET/QRA),together with the current
4078 azimuth and elevation.In addition, it will show the illuminated
4079 fraction of the moons disk.If all else fails it will show the Moonrise
4080 and set times for the nodethat you are connected to. For example:-
4083 SH/MOON SH/MOON G1TLH W5UN
4087 You can also use this command to see into the past or the future, soif
4088 you want to see yesterday's times then do:-
4095 or in three days time:-
4102 Upto 366 days can be checked both in the past and in the future.Please
4103 note that the rise and set times are given as the UT times of rise and
4104 set on the requested UT day.
4106 11.145. show/muf <prefix> [<hours>][long] (0)
4108 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4111 This command allow you to estimate the likelihood of you contactinga
4112 station with the prefix you have specified. The output assumes a
4113 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4114 0.15muV/10dB SINAD)The result predicts the most likely operating
4115 frequencies and signallevels for high frequency (shortwave) radio
4116 propagation paths onspecified days of the year and hours of the day.
4117 It is most useful forpaths between 250 km and 6000 km, but can be used
4118 with reduced accuracyfor paths shorter or longer than this.The command
4119 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4120 predict the MUF given the predicted flux, day of the year,hour of the
4121 day and geographic coordinates of the transmitter andreceiver. This
4122 routine is reasonably accurate for the purposes here,with a claimed
4123 RMS error of 3.8 MHz, but much smaller and less complexthan the
4124 programs used by major shortwave broadcasting organizations,such as
4125 the Voice of America.The command will display some header information
4126 detailing itsassumptions, together with the locations, latitude and
4127 longitudes andbearings. It will then show UTC (UT), local time at the
4128 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4129 the path(Zen) and the likely signal strengths. Then for each frequency
4130 for whichthe system thinks there is a likelihood of a circuit it
4131 prints a value.The value is currently a likely S meter reading based
4132 on the conventional6dB / S point scale. If the value has a '+'
4133 appended it means that it is1/2 an S point stronger. If the value is
4134 preceeded by an 'm' it means thatthere is likely to be much fading and
4135 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4136 will show the next two hours worth of data. Youcan specify anything up
4137 to 24 hours worth of data by appending the no ofhours required after
4138 the prefix. For example:-
4148 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms Location Lat / Long Azim East Dereham, Norfolk 52 41 N 0 57 E 47 United-States-W 43 0 N 87 54 W 299 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0 18 23 11.5 -35 mS0+ mS2 S3 19 0 11.2 -41 mS0+ mS2 S3
4152 indicating that you will have weak, fading circuits on top band and
4153 80m but usable signals on 40m (about S3).inputing:-
4160 will get you the above display, but with the next 24 hours worth
4164 SH/MUF W L 24 SH/MUF W 24 Long
4168 Gives you an estimate of the long path propagation characterics.
4169 Itshould be noted that the figures will probably not be very useful,
4170 norterrible accurate, but it is included for completeness.
4172 11.146. show/newconfiguration [<node>] (0)
4174 show/newconfiguration [<node>] Show all the nodes and users visible
4176 This command allows you to see all the users that can be seenand the
4177 nodes to which they are connected. This command produces essentially
4178 the same information as SHOW/CONFIGURATION except that it shows all
4179 the duplication ofany routes that might be present It also uses a
4180 different formatwhich may not take up quite as much space if you don't
4181 have anyloops.BE WARNED: the list that is returned can be VERY long
4183 11.147. show/newconfiguration/node (0)
4185 show/newconfiguration/node Show all the nodes connected locally
4187 Show all the nodes connected to this node in the new format.
4189 11.148. show/node [<callsign> ...] (1)
4191 show/node [<callsign> ...] Show the type and version number of nodes
4193 Show the type and version (if connected) of the nodes specified on
4194 thecommand line. If no callsigns are specified then a sorted list of
4195 allthe non-user callsigns known to the system will be displayed.
4197 11.149. show/prefix <callsign> (0)
4199 show/prefix <callsign> Interrogate the prefix database
4201 This command takes the <callsign> (which can be a full or partial
4202 callsign or a prefix), looks up which internal country number it is
4203 and then displays all the relevant prefixes for that countrytogether
4204 with the internal country no, the CQ and ITU regions. See also
4207 11.150. show/program (5)
4209 show/program Show the locations of all the included program modules
4211 Show the name and location where every program module was load from.
4212 Thisis useful for checking where you think you have loaded a .pm file
4215 11.151. show/qra <lat> <long> (0)
4217 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4219 This is a multipurpose command that allows you either to calculate
4220 thedistance and bearing between two locators or (if only one locator
4221 isgiven on the command line) the distance and beraing from your
4222 stationto the locator. For example:-
4225 SH/QRA IO92QL SH/QRA JN06 IN73
4229 The first example will show the distance and bearing to the locator
4230 fromyourself, the second example will calculate the distance and bear-
4231 ing fromthe first locator to the second. You can use 4 or 6 character
4232 locators.It is also possible to convert a latitude and longitude to a
4233 locator by using this command with a latitude and longitude as an
4234 argument, forexample:-
4237 SH/QRA 52 41 N 0 58 E
4241 11.152. show/qra <locator> [<locator>] (0)
4243 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4246 11.153. show/qrz <callsign> (0)
4248 show/qrz <callsign> Show any callbook details on a callsign
4250 This command queries the QRZ callbook server on the internetand
4251 returns any information available for that callsign. This serviceis
4252 provided for users of this software by http://www.qrz.com
4254 11.154. show/route <callsign> ... (0)
4256 show/route <callsign> ... Show the route to the callsign
4258 This command allows you to see to which node the callsigns specified
4259 areconnected. It is a sort of inverse sh/config.
4266 11.155. show/satellite <name> [<hours> <interval>] (0)
4268 show/satellite <name> [<hours> <interval>] Show tracking data
4270 Show the tracking data from your location to the satellite of your
4271 choicefrom now on for the next few hours.If you use this command
4272 without a satellite name it will display a listof all the satellites
4273 known currently to the system. If you give a name then you can obtain
4274 tracking data of all the passesthat start and finish 5 degrees below
4275 the horizon. As default it willgive information for the next three
4276 hours for every five minute period.You can alter the number of hours
4277 and the step size, within certain limits. Each pass in a period is
4278 separated with a row of '-----' charactersSo for example:-
4281 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4285 11.156. show/station all [<regex>] (6)
4287 show/station all [<regex>] Show list of users in the system
4290 11.157. show/station [<callsign> ..] (0)
4292 show/station [<callsign> ..] Show information about a callsign
4294 Show the information known about a callsign and whether (and
4295 where)that callsign is connected to the cluster.
4302 If no callsign is given then show the information for yourself.
4305 11.158. show/sun [ndays] [<prefix>|<callsign>] (0)
4307 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
4309 Show the sun rise and set times for a (list of) prefixes or callsigns,
4310 together with the azimuth and elevation of the sun currently at
4311 thoselocations.If you don't specify any prefixes or callsigns, it will
4312 show the times foryour QTH (assuming you have set it with either
4313 SET/LOCATION or SET/QRA),together with the current azimuth and
4314 elevation.If all else fails it will show the sunrise and set times for
4315 the nodethat you are connected to. For example:-
4318 SH/SUN SH/SUN G1TLH K9CW ZS
4322 You can also use this command to see into the past or the future, soif
4323 you want to see yesterday's times then do:-
4330 or in three days time:-
4337 Upto 366 days can be checked both in the past and in the future.Please
4338 note that the rise and set times are given as the UT times of rise and
4339 set on the requested UT day.
4341 11.159. show/time [<prefix>|<callsign>] (0)
4343 show/time [<prefix>|<callsign>] Show the local time
4345 If no prefixes or callsigns are given then this command returns the
4346 localtime and UTC as the computer has it right now. If you give some
4347 prefixesthen it will show UTC and UTC + the local offset (not
4348 including DST) atthe prefixes or callsigns that you specify.
4350 11.160. show/usdb [call ..] (0)
4352 show/usdb [call ..] Show information held on the FCC Call database
4354 Show the City and State of a Callsign held on the FCC database ifhis
4355 is being run on this system, eg:-
4362 11.161. show/vhfstats [days] [date] (0)
4364 show/vhfstats [days] [date] Show the VHF DX Statistics
4366 Show the VHF DX spots breakdown by band for the last <days> no of days
4367 (default is 31), starting from a date (default: today).
4370 11.162. show/vhftable [days] [date] [prefix ...] (0)
4372 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
4374 Show the VHF DX Spotter table for the list of prefixes for the last
4375 <days> no of days (default is 31), starting from a date (default:
4376 today).If there are no prefixes then it will show the table for your
4377 country.Remember that some countries have more than one "DXCC country"
4378 in them(eg G :-), to show them (assuming you are not in G already
4379 which isspecially treated in the code) you must list all the relevant
4383 sh/vhftable g gm gd gi gj gw gu
4387 Note that the prefixes are converted into country codes so you don't
4388 haveto list all possible prefixes for each country.If you want more or
4389 less days than the default simply include thenumber you require:-
4396 If you want to start at a different day, simply add the date in some
4400 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
4404 This will show the stats for your DXCC for that CQWW contest weekend.
4405 You can specify either prefixes or full callsigns (so you can see how
4406 youdid against all your mates). You can also say 'all' which will then
4407 printthe worldwide statistics.
4414 11.163. show/wcy (0)
4416 show/wcy Show last 10 WCY broadcasts
4419 11.164. show/wcy <n> (0)
4421 show/wcy <n> Show last <n> WCY broadcasts
4423 Display the most recent WCY information that has been received by the
4426 11.165. show/wwv (0)
4428 show/wwv Show last 10 WWV broadcasts
4431 11.166. show/wwv <n> (0)
4433 show/wwv <n> Show last <n> WWV broadcasts
4435 Display the most recent WWV information that has been received by the
4438 11.167. shutdown (5)
4440 shutdown Shutdown the cluster
4442 Shutdown the cluster and disconnect all the users
4444 11.168. stat/channel [<callsign>] (5)
4446 stat/channel [<callsign>] Show the status of a channel on the cluster
4448 Show the internal status of the channel object either for the channel
4449 that you are on or else for the callsign that you asked for.Only the
4450 fields that are defined (in perl term) will be displayed.
4452 11.169. stat/db <dbname> (5)
4454 stat/db <dbname> Show the status of a database
4456 Show the internal status of a database descriptor.Depending on your
4457 privilege level you will see more or less information. This command is
4458 unlikely to be of much use to anyone other than a sysop.
4460 11.170. stat/msg (1)
4462 stat/msg Show the status of the message system
4465 11.171. stat/msg <msgno> (1)
4467 stat/msg <msgno> Show the status of a message
4469 This command shows the internal status of a message and includes
4470 informationsuch as to whom it has been forwarded, its size, origin etc
4471 etc.If no message number is given then the status of the message
4472 system is displayed.
4474 11.172. stat/route_node <callsign> (5)
4476 stat/route_node <callsign> Show the data in a Route::Node object
4479 11.173. stat/route_node all (5)
4481 stat/route_node all Show list of all Route::Node objects
4484 11.174. stat/route_user <callsign> (5)
4486 stat/route_user <callsign> Show the data in a Route::User object
4489 11.175. stat/route_user all (5)
4491 stat/route_user all Show list of all Route::User objects
4494 11.176. stat/user [<callsign>] (5)
4496 stat/user [<callsign>] Show the full status of a user
4498 Shows the full contents of a user record including all the secret
4499 flagsand stuff.Only the fields that are defined (in perl term) will be
4503 sysop Regain your privileges if you login remotely
4505 The system automatically reduces your privilege level to that of
4506 anormal user if you login in remotely. This command allows you
4507 toregain your normal privilege level. It uses the normal system:
4508 fivenumbers are returned that are indexes into the character array
4509 that isyour assigned password (see SET/PASSWORD). The indexes start
4510 fromzero.You are expected to return a string which contains the
4511 charactersrequired in the correct order. You may intersperse those
4512 characterswith others to obscure your reply for any watchers. For
4513 example (andthese values are for explanation :-):
4516 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
4523 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
4527 They will all match. If there is no password you will still be
4528 offerednumbers but nothing will happen when you input a string. Any
4529 match iscase sensitive.
4531 11.178. talk <call> > <node> [<text>] (0)
4533 talk <call> > <node> [<text>] Send a text message to another station
4536 Send a short message to any other station that is visible on the
4537 clustersystem. You can send it to anyone you can see with a
4538 SHOW/CONFIGURATION command, they don't have to be connected
4539 locally.The second form of TALK is used when other cluster nodes are
4540 connectedwith restricted information. This usually means that they
4541 don't send the user information usually associated with logging on and
4542 off the cluster.If you know that G3JNB is likely to be present on
4543 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
4544 then you would use thesecond form of the talk message.If you want to
4545 have a ragchew with someone you can leave the text messageout and the
4546 system will go into 'Talk' mode. What this means is that ashort
4547 message is sent to the recipient telling them that you are in
4548 a'Talking' frame of mind and then you just type - everything you send
4549 willgo to the station that you asked for. All the usual announcements,
4550 spots and so on will still come out on yourterminal.If you want to do
4551 something (such as send a spot) you preceed the normal command with a
4555 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
4559 To leave talk mode type:
4566 If you are in 'Talk' mode, there is an extention to the '/' command
4567 whichallows you to send the output to all the people you are talking
4568 to. You do with the '//' command. For example:-
4575 will send the hftable as you have it to all the people you are cur-
4578 11.179. talk <call> [<text>] (0)
4580 talk <call> [<text>] Send a text message to another station
4583 11.180. type <filearea>/<name> (0)
4585 type <filearea>/<name> Look at the contents of a file in one of the
4588 Type out the contents of a file in a filearea. So, for example, in
4589 filearea 'bulletins' you want to look at file 'arld051' you would
4593 TYPE bulletins/arld051
4597 See also SHOW/FILES to see what fileareas are available and a list of
4600 11.181. uncatchup <node call> all|[msgno> ...] (5)
4602 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
4604 When you send messages the fact that you have forwarded it to another
4605 node is remembered so that it isn't sent again. When you have a new
4606 partnernode and you add their callsign to your /spider/msg/forward.pl
4607 file, alloutstanding non-private messages will be forwarded to them.
4608 This may wellbe ALL the non-private messages. You can prevent this by
4609 using these commmands:-
4612 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
4616 and to undo what you have just done:-
4619 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
4623 which will arrange for them to be forward candidates again.Order is
4626 11.182. unset/announce (0)
4628 unset/announce Stop announce messages coming out on your terminal
4632 11.183. unset/anntalk (0)
4634 unset/anntalk Stop talk like announce messages on your terminal
4636 The announce system on legacy cluster nodes is used as a talk
4637 substitute because the network is so poorly connected. If you:
4644 you will suppress several of these announces, you may miss the odd
4645 useful one as well, but you would probably miss them anyway in thewel-
4646 ter of useless ones.
4653 allows you to see them again. This is the default.
4655 11.184. unset/baddx <call>.. (8)
4657 unset/baddx <call>.. Propagate a dx spot with this callsign again
4659 Setting a word as 'baddx' will prevent spots with that word in
4660 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
4661 anyfurther. They will not be displayed and they will not be sent
4662 ontoother nodes.The word must be written in full, no wild cards are
4666 set/baddx FORSALE VIDEO FR0G
4670 To allow a word again, use the following command ...
4677 11.185. unset/badnode <call>.. (8)
4679 unset/badnode <call>.. Allow spots from this node again
4681 Setting a callsign as a 'badnode' will prevent spots from that node
4682 going any further. They will not be displayed and they will not be
4683 sent onto other nodes.The call must be a full eg:-
4690 will stop anything from K1TTT. If you want SSIDs as well then you mus-
4691 tenter them specifically.
4697 will allow spots from him again.Use with extreme care. This command
4698 may well be superceeded by FILTERing.
4700 11.186. unset/badspotter <call>.. (8)
4702 unset/badspotter <call>.. Allow spots from this callsign again
4704 Setting a callsign as a 'badspotter' will prevent spots from this
4705 callsign going any further. They will not be displayed and they will
4706 not be sent onto other nodes.The call must be written in full, no wild
4707 cards are allowed eg:-
4710 set/badspotter VE2STN
4714 will stop anything from VE2STN. This command will automaticallystop
4715 spots from this user, regardless of whether or which SSID he uses. DO
4716 NOT USE SSIDs in the callsign, just use the callsignas above or below.
4719 unset/badspotter VE2STN
4723 will allow spots from him again.Use with extreme care. This command
4724 may well be superceded by FILTERing.
4726 11.187. unset/badword <word>.. (8)
4728 unset/badword <word>.. Propagate things with this word again
4730 Setting a word as a 'badword' will prevent things like spots,announces
4731 or talks with this word in the the text part from going anyfurther.
4732 They will not be displayed and they will not be sent ontoother
4733 nodes.The word must be written in full, no wild cards are allowed eg:-
4736 set/badword annihilate annihilated annihilation
4740 will stop anything with these words in the text.
4743 unset/badword annihilated
4747 will allow text with this word again.
4749 11.188. unset/beep (0)
4751 unset/beep Stop beeps for DX and other messages on your terminal
4754 11.189. unset/dx (0)
4756 unset/dx Stop DX messages coming out on your terminal
4759 11.190. unset/dxgrid (0)
4761 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
4763 A standard feature which is enabled in version 1.43 and above is that
4764 if the spotter's grid square is known it is output on the endof a DX
4765 announcement (there is just enough room). Some user programscannot
4766 cope with this. You can use this command to reset (or set)this
4769 11.191. unset/echo (0)
4771 unset/echo Stop the cluster echoing your input
4773 If you are connected via a telnet session, different implimentationsof
4774 telnet handle echo differently depending on whether you are connected
4775 via port 23 or some other port. You can use this commandto change the
4776 setting appropriately. The setting is stored in your user profile.YOU
4777 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
4779 11.192. unset/email (0)
4781 unset/email Stop personal msgs being forwarded by email
4783 If any personal messages come in for your callsign then you can
4784 usethese commands to control whether they are forwarded onto your
4785 emailaddress. To enable the forwarding do something like:-
4788 SET/EMAIL mike.tubby@somewhere.com
4792 You can have more than one email address (each one separated by a
4793 space).Emails are forwarded to all the email addresses you specify.You
4794 can disable forwarding by:-
4801 11.193. unset/here (0)
4803 unset/here Tell the system you are absent from your terminal
4806 11.194. unset/hops <call> ann|spots|route|wwv|wcy (8)
4808 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
4810 Set the hop count for a particular type of broadcast for a node.This
4811 command allows you to set up special hop counts for a node for
4812 currently: announce, spots, wwv and wcy broadcasts.eg:
4815 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
4819 Set SHOW/HOPS for information on what is already set. This commandcre-
4820 ates a filter and works in conjunction with the filter system. You can
4821 unset the hops with command UNSET/HOPS. For example:-
4824 unset/hops gb7djk ann unset/hops gb7mbc spots
4828 11.195. unset/logininfo (0)
4830 unset/logininfo Inform when a station logs out locally
4833 11.196. unset/privilege (0)
4835 unset/privilege Remove any privilege for this session
4837 You can use this command to 'protect' this session from
4838 unauthoriseduse. If you want to get your normal privilege back you
4839 will need toeither logout and login again (if you are on a console) or
4840 use theSYSOP command.
4842 11.197. unset/prompt (0)
4844 unset/prompt Set your prompt back to default
4846 This command will set your user prompt to exactly the string that you
4847 say. The point of this command to enable a user to interface to
4848 programsthat are looking for a specific prompt (or else you just want
4849 a differentfixed prompt).
4856 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
4859 11.198. unset/talk (0)
4861 unset/talk Stop TALK messages coming out on your terminal
4864 11.199. unset/wcy (0)
4866 unset/wcy Stop WCY messages coming out on your terminal
4869 11.200. unset/wwv (0)
4871 unset/wwv Stop WWV messages coming out on your terminal
4874 11.201. unset/wx (0)
4876 unset/wx Stop WX messages coming out on your terminal
4881 who Show who is physically connected
4883 This is a quick listing that shows which callsigns are connected
4884 andwhat sort of connection they have
4886 11.203. wx <text> (0)
4888 wx <text> Send a weather message to local users
4892 11.204. wx full <text> (0)
4894 wx full <text> Send a weather message to all cluster users
4897 11.205. wx sysop <text> (5)
4899 wx sysop <text> Send a weather message to other clusters only
4901 Weather messages can sometimes be useful if you are experiencing an
4902 extremethat may indicate enhanced conditions