1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 February 2003 revision 0.4
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)
176 11.105 set/dxstate (0)
178 11.107 set/email <email> ... (0)
180 11.109 set/homenode <node> (0)
181 11.110 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
182 11.111 set/language <lang> (0)
183 11.112 set/location <lat & long> (0)
184 11.113 set/logininfo (0)
185 11.114 set/name <your name> (0)
186 11.115 set/node <call> [<call>..] (5)
187 11.116 set/obscount <count> <call> (8)
188 11.117 set/page <lines per page> (0)
189 11.118 set/password (0)
190 11.119 set/prompt <string> (0)
191 11.120 set/qra <locator> (0)
192 11.121 set/qth <your qth> (0)
193 11.122 set/spider <call> [<call>..] (5)
198 11.127 show/baddx (1)
199 11.128 show/badnode (1)
200 11.129 show/badspotter (1)
201 11.130 show/badword (1)
202 11.131 show/configuration [<node>] (0)
203 11.132 show/configuration/node (0)
204 11.133 show/connect (1)
205 11.134 show/date [<prefix>|<callsign>] (0)
206 11.135 show/db0sdx <callsign> (0)
208 11.137 show/dxcc <prefix> (0)
209 11.138 show/dxstats [days] [date] (0)
210 11.139 show/files [<filearea> [<string>]] (0)
211 11.140 show/filter (0)
212 11.141 show/hfstats [days] [date] (0)
213 11.142 show/hftable [days] [date] [prefix ...] (0)
214 11.143 show/hops <call> [ann|spots|route|wcy|wwv] (8)
215 11.144 show/isolate (1)
216 11.145 show/log [<callsign>] (8)
217 11.146 show/moon [ndays] [<prefix>|<callsign>] (0)
218 11.147 show/muf <prefix> [<hours>][long] (0)
219 11.148 show/newconfiguration [<node>] (0)
220 11.149 show/newconfiguration/node (0)
221 11.150 show/node [<callsign> ...] (1)
222 11.151 show/prefix <callsign> (0)
223 11.152 show/program (5)
224 11.153 show/qra <lat> <long> (0)
225 11.154 show/qra <locator> [<locator>] (0)
226 11.155 show/qrz <callsign> (0)
227 11.156 show/route <callsign> ... (0)
228 11.157 show/satellite <name> [<hours> <interval>] (0)
229 11.158 show/station all [<regex>] (6)
230 11.159 show/station [<callsign> ..] (0)
231 11.160 show/sun [ndays] [<prefix>|<callsign>] (0)
232 11.161 show/time [<prefix>|<callsign>] (0)
233 11.162 show/usdb [call ..] (0)
234 11.163 show/vhfstats [days] [date] (0)
235 11.164 show/vhftable [days] [date] [prefix ...] (0)
237 11.166 show/wcy <n> (0)
238 11.167 show/wm7d <callsign> (0)
240 11.169 show/wwv <n> (0)
242 11.171 stat/channel [<callsign>] (5)
243 11.172 stat/db <dbname> (5)
245 11.174 stat/msg <msgno> (1)
246 11.175 stat/route_node <callsign> (5)
247 11.176 stat/route_node all (5)
248 11.177 stat/route_user <callsign> (5)
249 11.178 stat/route_user all (5)
250 11.179 stat/user [<callsign>] (5)
252 11.181 talk <call> > <node> [<text>] (0)
253 11.182 talk <call> [<text>] (0)
254 11.183 type <filearea>/<name> (0)
255 11.184 uncatchup <node call> all|[msgno> ...] (5)
256 11.185 unset/announce (0)
257 11.186 unset/anntalk (0)
258 11.187 unset/baddx <call>.. (8)
259 11.188 unset/badnode <call>.. (8)
260 11.189 unset/badspotter <call>.. (8)
261 11.190 unset/badword <word>.. (8)
262 11.191 unset/beep (0)
264 11.193 unset/dxgrid (0)
265 11.194 unset/dxstate (0)
266 11.195 unset/echo (0)
267 11.196 unset/email (0)
268 11.197 unset/here (0)
269 11.198 unset/hops <call> ann|spots|route|wwv|wcy (8)
270 11.199 unset/logininfo (0)
271 11.200 unset/privilege (0)
272 11.201 unset/prompt (0)
273 11.202 unset/talk (0)
279 11.208 wx full <text> (0)
280 11.209 wx sysop <text> (5)
283 ______________________________________________________________________
285 1. Routing and Filtering
289 From DXSpider version 1.48, major changes were introduced to the way
290 node connections are treated. This is part of an ongoing process to
291 remove problems with loops and to enable talk and other functions to
292 propagate across the whole of the worldwide cluster network. In fact,
293 in a Spider network, it would be useful, perhaps even necessary to
294 have loops. This would give real resilience to the network, meaning
295 that if a link dropped, the information flow would simply come in and
296 go out via a different route. Of course, we do not have a complete
297 network of Spider nodes, there are other programs out there. Some of
298 these do not have any protection from loops. Certainly AK1A does not
299 handle loops well at all. It is therefore necessary to have some form
300 of protection for these nodes.
303 In fact DXSpider has had a simple system for some time which is called
304 isolation. This is similar to what in other systems such as clx, is
305 called passive mode. A more detailed explanation of isolation is given
306 further below. This system is still available and, for simple
307 networks, is probably all that you need.
310 The new functionality introduced in version 1.48 allows filtering the
311 node and user protocol frames on a "per interface" basis. We call this
312 route filtering. This is used instead of isolation.
315 What this really means is that you can control more or less completely
316 which user and node management PC protocol frames pass to each of your
317 partner nodes. You can also limit what comes into your node from your
318 partners. It is even possible to control the settings that your
319 partner node has for the routing information that it sends to you
320 (using the rcmd command).
325 Initially when route filters were being tested we generated a
326 "default" filter. Unfortunately it quickly became apparent that this
327 might suit the UK cluster network but didn't really fit anybody else.
328 However using a default filter is an appropriate thing to do. How, is
329 explained further on.
332 The first thing that you must do is determine whether you need to use
333 route filtering at all. If you are a "normal" node with two or three
334 partners and you arranged in an "official" non-looping tree type
335 network, then you do not need to do route filtering and you will feel
336 a lot better for not getting involved. If you are successfully using
337 isolation then you also probably don't need to use route filtering.
340 To put it simply, you should not mix Isolation and Route Filtering.
341 It will work, of sorts, but you will not get the expected results. If
342 you are using Isolation sucessfully at the moment, do not get involved
343 in Route Filtering unless you have a good supply of aspirin! Once you
344 have started down the road of Route Filtering, do not use Isolation
345 either. Use one or the other, not both.
348 You will only require this functionality if you are "well-connected".
349 What that means is that you are connected to several different parts
350 of (say) the EU cluster and, at the same time, also connected to two
351 or three places in the US which, in turn are connected back to the EU.
352 This is called a "loop" and if you are seriously looped then you need
356 I should at this stage give a little bit of background on filters.
357 All the filters in Spider work in basically the same way. You can
358 either accept or reject various options in order to create the filter
359 rules you wish to achieve. Some filters are user settable, others can
360 only be altered by the sysop. Route filtering can only be done by the
365 Anyway, without further discouragement, let me start the process of
369 1.3. The node_default filter
371 All normal systems should have a default routing filter and it should
372 usually be set to send only the normal, unlooped, view of your
373 "national" network. Here in the UK that means nodes from the UK and
374 Eire, in EU it is more complex as the networks there grew up in a more
379 The generic commands are:-
383 reject/route node_default <filter_option>
387 accept/route node_default <filter_option>
391 where filter_option is one of the following ...
400 channel_dxcc <numbers>
401 channel_itu <numbers>
402 channel_zone <numbers>
406 Please be careful if you alter this setting, it will affect ALL your
407 links! Remember, this is a default filter for node connections, not a
411 For the default routing filter then you have two real choices: either
412 a "national" view or the "safe" option of only your own callsign.
413 Examples of each (for my node: GB7DJK) are:-
417 acc/route node_default call_dxcc 61,38
418 acc/route node_default call gb7djk
422 GB7DJK uses the first of these. The DXCC countries can be obtained
423 from the show/prefix command.
426 The example filters shown control output TO all your partner nodes
427 unless they have a specific filter applied to them (see next section).
430 It is also possible to control the incoming routing information that
431 you are prepared to accept FROM your partner nodes. The reason this is
432 necessary is to make sure that stuff like mail, pings and similar
433 commands a) go down the correct links and b) don't loop around
434 excessively. Again using GB7DJK as an example a typical default input
435 filter would be something like:
439 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
443 What this does is accept node and user information for our national
444 network from nodes that are in our national network, but rejects such
445 information from anyone else. Although it doesn't explicitly say so,
446 by implication, any other node information (not from the UK and Eire)
450 As I imagine it will take a little while to get one's head around all
451 of this you can study the effect of any rules that you try by watching
452 the debug output after having done:-
460 After you have got tired of that, to put it back the way it was:-
468 1.4. General route filtering
470 Exactly the same rules apply for general route filtering. You would
471 use either an accept filter or a reject filter like this ...
475 reject/route <node_call> <filter_option>
479 accept/route <node_call> <filter_option>
483 Here are some examples of route filters ...
487 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
488 rej/route all (equiv to [very] restricted mode)
489 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
490 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
494 In practice you will either be opening the default filter out for a
495 partner by defining a specific filter for that callsign:-
500 acc/route gb7baa input all
504 or restricting it quite a lot, in fact making it very nearly like an
505 isolated node, like this:-
509 acc/route pi4ehv-8 call gb7djk
510 rej/route pi4ehv-8 input call_dxcc 61,38
514 This last example takes everything except UK and Eire from PI4EHV-8
515 but only sends him my local configuration (just a PC19 for GB7DJK and
516 PC16s for my local users).
519 It is possible to write much more complex rules, there are up to 10
520 accept/reject pairs per callsign per filter. For more information see
525 1.5. General filter rules
527 Upto v1.44 it was not possible for the user to set their own filters.
528 From v1.45 though that has all changed. It is now possible to set
529 filters for just about anything you wish. If you have just updated
530 from an older version of DXSpider you will need to update your new
531 filters. You do not need to do anything with your old filters, they
532 will be renamed as you update.
535 There are 3 basic commands involved in setting and manipulating
536 filters. These are accept, reject and clear. First we will look
537 generally at filtering. There are a number of things you can filter in
538 the DXSpider system. They all use the same general mechanism.
541 In general terms you can create a "reject" or an "accept" filter which
542 can have up to 10 lines in it. You do this using, for example ...
551 where ..... are the specific commands for that type of filter. There
552 are filters for spots, wwv, announce, wcy and (for sysops) connects.
553 See each different accept or reject command reference for more
556 There is also a command to clear out one or more lines in a filter.
566 There is clear/xxxx command for each type of filter.
569 and you can check that your filters have worked by the command ...
577 For now we are going to use spots for the examples, but you can apply
578 the same principles to all types of filter.
583 There are two main types of filter, accept or reject. You can use
584 either to achieve the result you want dependent on your own preference
585 and which is more simple to do. It is pointless writing 8 lines of
586 reject filters when 1 accept filter would do the same thing! Each
587 filter has 10 lines (of any length) which are tried in order. If a
588 line matches then the action you have specified is taken (ie reject
589 means ignore it and accept means take it)
592 If you specify reject filters, then any lines that arrive that match
593 the filter will be dumped but all else will be accepted. If you use
594 an accept filter, then ONLY the lines in the filter will be accepted
595 and all else will be dumped. For example if you have a single line
600 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
604 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
607 If you set a reject filter like this ...
611 reject/spots on hf/cw
615 Then you will get everything EXCEPT HF CW spots. You could make this
616 single filter even more flexible. For example, if you are interested
617 in IOTA and will work it even on CW even though normally you are not
618 interested in CW, then you could say ...
622 reject/spots on hf/cw and not info iota
626 But in that case you might only be interested in iota and say:-
630 accept/spots not on hf/cw or info iota
634 which achieves exactly the same thing. You should choose one or the
635 other until you are comfortable with the way it works. You can mix
636 them if you wish (actually you can have an accept AND a reject on the
637 same line) but don't attempt this until you are sure you know what you
641 You can arrange your filter lines into logical units, either for your
642 own understanding or simply convenience. Here is an example ...
646 reject/spots 1 on hf/cw
647 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
651 What this does is to ignore all HF CW spots and also rejects any spots
652 on VHF which don't either originate or spot someone in Europe.
655 This is an example where you would use a line number (1 and 2 in this
656 case), if you leave the digit out, the system assumes '1'. Digits
657 '0'-'9' are available. This make it easier to see just what filters
658 you have set. It also makes it more simple to remove individual
659 filters, during a contest for example.
662 You will notice in the above example that the second line has
663 brackets. Look at the line logically. You can see there are 2
664 separate sections to it. We are saying reject spots that are VHF or
665 above APART from those in zones 14, 15 and 16 (either spotted there or
666 originated there). If you did not have the brackets to separate the 2
667 sections, then Spider would read it logically from the front and see a
668 different expression entirely ...
672 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
676 The simple way to remember this is, if you use OR - use brackets.
677 Whilst we are here CASE is not important. 'And BY_Zone' is just the
678 same as 'and by_zone'.
680 As mentioned earlier, setting several filters can be more flexible
681 than simply setting one complex one. Doing it in this way means that
682 if you want to alter your filter you can just redefine or remove one
683 or more lines of it or one line. For example ...
687 reject/spots 1 on hf/ssb
691 would redefine our earlier example, or
699 To remove all the filter lines in the spot filter ...
709 You can filter in several different ways. The options are listed in
710 the various helpfiles for accept, reject and filter.
714 Sometimes all that is needed is a general rule for node connects.
715 This can be done with a node_default filter. This rule will always be
716 followed, even if the link is isolated, unless another filter is set
717 specifically. Default rules can be set for nodes and users. They can
718 be set for spots, announces, WWV and WCY. They can also be used for
719 hops. An example might look like this ...
723 accept/spot node_default by_zone 14,15,16,20,33
724 set/hops node_default spot 50
728 This filter is for spots only, you could set others for announce, WWV
729 and WCY. This filter would work for ALL nodes unless a specific
730 filter is written to override it for a particular node. You can also
731 set a user_default should you require. It is important to note that
732 default filters should be considered to be "connected". By this I
733 mean that should you override the default filter for spots, you need
734 to add a rule for the hops for spots also.
737 1.9. Advanced filtering
739 Once you are happy with the results you get, you may like to
743 The previous example that filters hf/cw spots and accepts vhf/uhf
744 spots from EU can be written with a mixed filter, for example ...
750 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
754 Note that the first filter has not been specified with a number. This
755 will automatically be assumed to be number 1. In this case, we have
756 said reject all HF spots in the CW section of the bands but accept all
757 others at HF. Also accept anything in VHF and above spotted in or by
758 operators in the zones 14, 15 and 16. Each filter slot actually has a
759 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
763 It was mentioned earlier that after a reject test that doesn't match,
764 the default for following tests is 'accept', the reverse is true for
765 'accept'. In the example what happens is that the reject is executed
766 first, any non hf/cw spot is passed to the accept line, which lets
767 through everything else on HF. The next filter line lets through just
768 VHF/UHF spots from EU.
771 1.10. Basic hop control
773 In /spider/data you will find a file called hop_table.pl. This is the
774 file that controls your hop count settings. It has a set of default
775 hops on the various PC frames and also a set for each node you want to
776 alter the hops for. You may be happy with the default settings of
777 course, but this powerful tool can help to protect and improve the
778 network. The file will look something like this ...
783 # hop table construction
788 # default hopcount to use
791 # some variable hop counts based on message type
802 # the per node hop control thingy
834 Each set of hops is contained within a pair of curly braces and
835 contains a series of PC frame types. PC11 for example is a DX spot.
836 The figures here are not exhaustive but should give you a good idea of
840 SHould any of the nodecalls include an ssid, it is important to wrap
841 the whole call in single quotes, like this ...
856 If you do not do this, you will get errors and the file will not work
860 You can alter this file at any time, including whilst the cluster is
861 running. If you alter the file during runtime, the command load/hops
862 will bring your changes into effect.
865 1.11. Hop Control on Specific Nodes
867 You can set a callsign specific hop count for any of the standard
872 set/hops gb7djk spot 4
873 set/hops node_default route 10
874 set/hops gb7baa wcy 5
878 all work on their specific area of the protocol.
881 The set/hops command overrides any hops that you have set otherwise.
884 You can show what hops have been set using the show/hops command.
887 1.12. Isolating networks
889 It is possible to isolate networks from each other on a "gateway" node
890 using the set/isolate <node_call> command.
893 The effect of this is to partition an isolated network completely from
894 another node connected to your node. Your node will appear on and
895 otherwise behave normally on every network to which you are connected,
896 but data from an isolated network will not cross onto any other
897 network or vice versa. However all the spot, announce and WWV traffic
898 and personal messages will still be handled locally (because you are a
899 real node on all connected networks), that is locally connected users
900 will appear on all networks and will be able to access and receive
901 information from all networks transparently. All routed messages will
902 be sent as normal, so if a user on one network knows that you are a
903 gateway for another network, he can still still send a talk/announce
904 etc message via your node and it will be routed across.
907 If you use isolate on a node connection you will continue to receive
908 all information from the isolated partner, however you will not pass
909 any information back to the isolated node. There are times when you
910 would like to forward only spots across a link (maybe during a contest
911 for example). To do this, isolate the node in the normal way and use
912 an acc/spot >call< all filter to override the isolate.
919 In the /spider/msg directory you will find a file called
920 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
921 original looks something like this ....
925 # the list of regexes for messages that we won't store having
926 # received them (bear in mind that we must receive them fully before
930 # The format of each line is as follows
932 # type source pattern
933 # P/B/F T/F/O/S regex
935 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
936 # source: T - to field, F - from field, O - origin, S - subject
937 # pattern: a perl regex on the field requested
939 # Currently only type B and P msgs are affected by this code.
941 # The list is read from the top down, the first pattern that matches
942 # causes the action to be taken.
944 # The pattern can be undef or 0 in which case it will always be selected
945 # for the action specified
956 I think this is fairly self explanatory. It is simply a list of
957 subject headers that we do not want to pass on to either the users of
958 the cluster or the other cluster nodes that we are linked to. This is
959 usually because of rules and regulations pertaining to items for sale
960 etc in a particular country.
964 2.2. Filtering words from text fields in Announce, Talk and DX spots
966 From version 1.48 onwards the interface to this has changed. You can
967 now use the commands set/badword to add words that you are not
968 prepared to see on the cluster, unset/badword to allow that word again
969 and show/badword to list the words that you have set.
972 If you have a previous /spider/data/badwords, the first time you start
973 the node, it will read and convert this file to the new commands. The
974 old style file will then be removed.
977 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
980 There are a number of commands that control whether a spot progresses
981 any further by regarding it as "bad" in some way.
984 A DX Spot has a number of fields which can be checked to see whether
985 they contain "bad" values, they are: the DX callsign itself, the
986 Spotter and the Originating Node.
989 There are a set of commands which allow the sysop to control whether a
1000 These work in the same as the set/badword command, you can add any
1001 words or callsigns or whatever to the appropriate database. For
1002 example, to stop a spot from a particular node you do:
1006 set/badnode gb7djk gb7dxc
1014 set/badspotter b0mb p1rat nocall
1022 set/baddx video wsjt
1026 You can remove a word using the appropriate unset command
1027 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1028 of show/baddx, show/badspotter and show/badnode.
1033 DXSpider deals seamlessly with standard AK1A type mail. It supports
1034 both personal and bulletin mail and the sysop has additional commands
1035 to ensure that mail gets to where it is meant. DXSpider will send
1036 mail almost immediately, assuming that the target is on line.
1037 However, only one mail message is dealt with at any one time. If a
1038 mail message is already being sent or recieved, then the new message
1039 will be queued until it has finished.
1041 The cluster mail is automatically deleted after 30 days unless the
1042 sysop sets the "keep" flag using the msg command.
1047 Personal mail is sent using the sp command. This is actually the
1048 default method of sending mail and so a simple s for send will do. A
1049 full list of the send commands and options is in the command set
1050 section, so I will not duplicate them here.
1055 Bulletin mail is sent by using the sb command. This is one of the
1056 most common mistakes users make when sending mail. They send a
1057 bulletin mail with s or sp instead of sb and of course the message
1058 never leaves the cluster. This can be rectified by the sysop by using
1062 Bulletin addresses can be set using the Forward.pl file.
1067 DXSpider receives all and any mail sent to it without any alterations
1068 needed in files. Because personal and bulletin mail are treated
1069 differently, there is no need for a list of accepted bulletin
1070 addresses. It is necessary, however, to tell the program which links
1071 accept which bulletins. For example, it is pointless sending
1072 bulletins addresses to "UK" to any links other than UK ones. The file
1073 that does this is called forward.pl and lives in /spider/msg. At
1074 default, like other spider files it is named forward.pl.issue. Rename
1075 it to forward.pl and edit the file to match your requirements. The
1081 # this is an example message forwarding file for the system
1083 # The format of each line is as follows
1085 # type to/from/at pattern action destinations
1086 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1088 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1089 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1090 # pattern: a perl regex on the field requested
1091 # action: I - ignore, F - forward
1092 # destinations: a reference to an array containing node callsigns
1094 # if it is non-private and isn't in here then it won't get forwarded
1096 # Currently only type B msgs are affected by this code.
1098 # The list is read from the top down, the first pattern that matches
1099 # causes the action to be taken.
1101 # The pattern can be undef or 0 in which case it will always be selected
1102 # for the action specified
1104 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1105 # pattern) then it will always be forwarded to every node that doesn't have
1106 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1107 # you allow a new link with this on EVERY bull will be forwarded immediately
1108 # on first connection)
1118 Simply insert a bulletin address and state in the brackets where you
1119 wish that mail to go. For example, you can see here that mail sent to
1120 "UK" will only be sent to the UK links and not to PA4AB-14.
1123 To force the cluster to reread the file use load/forward
1126 NB: If a user tries to send mail to a bulletin address that does not
1127 exist in this file, they will get an error.
1130 3.4. The msg command
1132 The msg command is a very powerful and flexible tool for the sysop.
1133 It allows the sysop to alter to and from fields and make other changes
1134 to manage the cluster mail.
1136 Here is a full list of the various options ...
1140 MSG TO <msgno> <call> - change TO callsign to <call>
1141 MSG FRom <msgno> <call> - change FROM callsign to <call>
1142 MSG PRrivate <msgno> - set private flag
1143 MSG NOPRrivate <msgno> - unset private flag
1144 MSG RR <msgno> - set RR flag
1145 MSG NORR <msgno> - unset RR flag
1146 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1147 MSG NOKEep <msgno> - unset the keep flag
1148 MSG SUbject <msgno> <new> - change the subject to <new>
1149 MSG WAittime <msgno> - remove any waiting time for this message
1150 MSG NOREad <msgno> - mark message as unread
1151 MSG REad <msgno> - mark message as read
1152 MSG QUeue - queue any outstanding bulletins
1153 MSG QUeue 1 - queue any outstanding private messages
1157 These commands are simply typed from within the cluster as the sysop
1163 You can check on a message from within the cluster by using the
1164 command stat/msg. This will give you additional information on the
1165 message number including which nodes have received it, which node it
1166 was received from and when etc. Here is an example of the output of
1171 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1174 Msg Time: 26-Jan-2001 1302Z
1178 Subject: AMSAT 2line KEPS 01025.AMSAT
1180 Got it Nodes: GB7BAA, GB7ADX
1184 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1190 This is described in the section on Other filters so I will not
1194 3.7. Distribution lists
1196 Distribution lists are simply a list of users to send certain types of
1197 mail to. An example of this is mail you only wish to send to other
1198 sysops. In /spider/msg there is a directory called distro. You put
1199 any distibution lists in here. For example, here is a file called
1200 SYSOP.pl that caters for the UK sysops.
1203 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1204 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1205 GB7DXK GB7DXI GB7DXS)
1209 Any mail sent to "sysop" would only be sent to the callsigns in this
1215 Spider provides a simple BBS interface. No input is required from the
1216 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1217 and pushes any required mail to the cluster. No mail can flow from
1218 Spider to the BBS, the interface is one-way.
1221 Please be careful not to flood the cluster network with unnecessary
1222 mail. Make sure you only send mail to the clusters that want it by
1223 using the Forward.pl file very carefully.
1228 From 1.48 onwards it will become increasingly possible to control
1229 DXSpider's operation with scripts of various kinds.
1232 The directory /spider/scripts is where it all happens and is used for
1233 several things. Firstly it contains a file called startup that can be
1234 used to call in any changes to the cluster from the default settings
1235 on startup. This script is executed immediately after all
1236 initialisation of the node is done but before any connections are
1237 possible. Examples of this include how many spots it is possible to
1238 get with the sh/dx command, whether you want registration/passwords to
1239 be permanently on etc. An example file is shown below and is included
1240 in the distribution as startup.issue.
1245 # startup script example
1247 # set maximum no of spots allowed to 100
1248 # set/var $Spot::maxspots = 100
1250 # Set registration on
1251 # set/var $main::reqreg = 1
1254 # set/var $main::passwdreq = 1
1259 As usual, any text behind a # is treated as a comment and not read.
1260 To use this file, simply rename it from startup.issue to startup. In
1261 our example above there are three options. The first option is the
1262 amount of spots that a user can request with the sh/dx command.
1263 Normally the default is to give 10 spots unless the user specifies
1264 more. Without this line enabled, the maximum a user can request is
1265 100 spots. Depending on your link quality you may wish to enable more
1266 or less by specifying the number.
1269 The other 2 options are dealt with more fully in the security section.
1272 Secondly, it is used to store the login scripts for users and nodes.
1273 Currently this can only be done by the sysop but it is envisaged that
1274 eventually users will be able to set their own. An example is
1275 included in the distibution but here is a further example.
1292 The lines in between commands can simply insert a blank line or a
1293 character such as a + sign to make the output easier to read. Simply
1294 create this script with your favourite editor and save it with the
1295 callsign of the user as the filename. Filenames should always be in
1299 Commands can be inserted in the same way for nodes. A node may wish a
1300 series of commands to be issued on login, such as a merge command for
1304 Thirdly, there are 2 default scripts for users and nodes who do not
1305 have a specifically defined script. These are user_default and
1311 Spider allows the creation of local or remote databases. It supports
1312 chained databases, allowing several different databases to be scanned
1313 with one simple command. Importing of databases is limited at present
1314 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1315 database but will expand with time.
1318 5.1. Creating databases
1320 Creating a database could not be more simple. All the commands are
1321 sent from the cluster prompt as the sysop user.
1323 To create a database you use the command dbcreate. It can be used in
1324 3 different ways like so ..
1331 To simply create a database locally, you just tell the command the
1332 name of the database. This does not create the actual database, it
1333 simply defines it to say that it exists.
1337 dbcreate <name> chain <name> [<name>...]
1341 This creates a chained database entry. The first database will be
1342 scanned, then the second, the third etc...
1346 dbcreate <name> remote <name>
1350 This creates a remote entry. the first name field is the database
1351 name at the remote node, then the remote switch, then the actual
1352 node_call of the remote node, for example...
1356 dbcreate buckmaster remote gb7dxc
1360 Remote databases cannot be chained, however, the last database in a
1361 chain can be a remote database.
1364 5.2. Importing databases
1366 The only databases that Spider can currently import are the standard
1367 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1368 This will be added to with time.
1370 To import such a database, first put the file somewhere useful like
1371 /tmp and then issue the following command ...
1375 dbimport oblast /tmp/OBLAST.FUL
1379 This will update the existing local oblast database or create it if it
1383 5.3. Checking available databases
1385 Once a database is created, you will want to check that it has been
1386 added. To do this use the dbavail command. This will output the
1387 available databases. For example ...
1392 DB Name Location Chain
1396 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1400 5.4. Looking up databases
1402 To look for information in a defined database, simply use the dbshow
1403 command, for example ...
1407 dbshow buckmaster G0YLM
1411 will show the information for the callsign G0YLM from the buckmaster
1412 database if it exists. To make things more standard for the users you
1413 can add an entry in the Aliases file so that it looks like a standard
1414 show command like this ...
1418 Now you can simply use show/buckmaster or an abreviation.
1421 5.5. Removing databases
1423 To delete an existing database you use the dbremove command. For
1432 would remove the oblast database and its associated datafile from the
1433 system. There are no warnings or recovery possible from this command.
1434 If you remove a database it ceases to exist and would have to be
1435 created from scratch if you still required it.
1438 6. Information, files and useful programs
1442 One of the more important things a cluster sysop needs to do is to get
1443 information to his users. The simplest way to do this is to have a
1444 banner that is sent to the user on login. This is know as a "message
1445 of the day" or "motd". To set this up, simply create a file in
1446 /spider/data called motd and edit it to say whatever you want. It is
1447 purely a text file and will be sent automatically to anyone logging in
1451 This message of the day file lives in the same directory as the
1452 standard motd file but is only sent to non-registered users. Once
1453 registered they will receive the same message as any other user.
1456 6.3. Downtime message
1458 If for any reason the cluster is down, maybe for upgrade or
1459 maintenance but the machine is still running, a message can be sent to
1460 the user advising them of the fact. This message lives in the
1461 /spider/data directory and is called "offline". Simply create the
1462 file and edit it to say whatever you wish. This file will be sent to
1463 a user attempting to log into the cluster when DXSpider is not
1467 6.4. Other text messages
1469 You can set other text messages to be read by the user if they input
1470 the file name. This could be for news items or maybe information for
1471 new users. To set this up, make a directory under /spider called
1472 packclus. Under this directory you can create files called news or
1473 newuser for example. In fact you can create files with any names you
1474 like. These can be listed by the user with the command ....
1482 They can be read by the user by typing the command ....
1490 If the file they want to read is called news. You could also set an
1491 alias for this in the Alias file to allow them just to type news
1494 You can also store other information in this directory, either
1495 directly or nested under directories. One use for this would be to
1496 store DX bulletins such as the OPDX bulletins. These can be listed
1497 and read by the user. To keep things tidy, make a directory under
1498 /spider/packclus called bulletin. Now copy any OPDX or similar
1499 bulletins into it. These can be listed by the user in the same way as
1500 above using the show/files command with an extension for the bulletin
1501 directory you have just created, like this ....
1509 An example would look like this ....
1512 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1516 You can see that in the files area (basically the packclus directory)
1517 there is a file called news and a directory called bulletin. You can
1518 also see that dates they were created. In the case of the file news,
1519 you can also see the time it was last modified, a good clue as to
1520 whether the file has been updated since you last read it. To read the
1521 file called news you would simply issue the command ....
1529 To look what is in the bulletin directory you issue the command ....
1534 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1535 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1536 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1537 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1538 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1539 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1540 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1541 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1542 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1543 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1544 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1545 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1546 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1547 Press Enter to continue, A to abort (16 lines) >
1551 You can now read any file in this directory using the type command,
1556 type bulletin/opdx391
1557 Ohio/Penn DX Bulletin No. 391
1558 The Ohio/Penn Dx PacketCluster
1562 Editor Tedd Mirgliotta, KB8NW
1563 Provided by BARF-80 BBS Cleveland, Ohio
1564 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1565 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1566 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1567 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1568 Press Enter to continue, A to abort (508 lines) >
1572 The page length will of course depend on what you have it set to!
1575 6.5. The Aliases file
1577 You will find a file in /spider/cmd/ called Aliases. This is the file
1578 that controls what a user gets when issuing a command. It is also
1579 possible to create your own aliases for databases and files you create
1583 You should not alter the original file in /spider/cmd/ but create a
1584 new file with the same name in /spider/local_cmd. This means that any
1585 new Aliases files that is downloaded will not overwrite your self
1586 created Aliases and also that you do not override any new Aliases with
1587 your copy in /spider/local_cmd/. You must remember that any files you
1588 store in /spider/local/ or /spider/local_cmd override the originals if
1589 the same lines are used in both files.
1592 The best way of dealing with all this then is to only put your own
1593 locally created Aliases in the copy in /spider/local_cmd. The example
1594 below is currently in use at GB7MBC.
1599 # Local Aliases File
1606 '^news$', 'type news', 'type',
1609 '^sh\w*/buck$', 'show/qrz', 'show',
1610 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1611 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1612 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1613 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1619 Each alphabetical section should be preceded by the initial letter and
1620 the section should be wrapped in square brackets as you can see. The
1621 syntax is straightforward. The first section on each line is the new
1622 command that will be allowed once the alias is included. The second
1623 section is the command it is replacing and the last section is the
1624 actual command that is being used.
1627 The eagle-eyed amongst you will have noticed that in the first
1628 section, the new alias command has a '^' at the start and a '$' at the
1629 end. Basically these force a perfect match on the alias. The '^'
1630 says match the beginning exactly and the with similar commands.
1633 I have 3 different types of alias in this file. At the top is an
1634 alias for 'news'. This is a file I have created in the
1635 /spider/packclus/ directory where I can inform users of new
1636 developments or points of interest. In it's initial form a user would
1637 have to use the command type news. The alias allows them to simply
1638 type news to get the info. Second is an alias for the show/qrz
1639 command so that those users used to the original show/buck command in
1640 AK1A will not get an error, and the rest of the lines are for locally
1641 created databases so that a user can type show/hftest instead of
1642 having to use the command dbshow hftest which is not as intuitive.
1645 This file is just an example and you should edit it to your own
1646 requirements. Once created, simply issue the command load/alias at
1647 the cluster prompt as the sysop user and the aliases should be
1654 In later versions of Spider a simple console program is provided for
1655 the sysop. This has a type ahead buffer with line editing facilities
1656 and colour for spots, announces etc. To use this program, simply use
1657 console.pl instead of client.
1660 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1661 edit the file with your favourite editor.
1664 6.7. Updating kepler data
1666 Spider has a powerful and flexible show/satellite command. In order
1667 for this to be accurate, the kepler data has to be updated regularly.
1668 In general, this data is available as an email or via cluster mail.
1669 Updating it is simple. First you need to export the mail message as a
1670 file. You do this with the export command from the cluster prompt as
1671 the sysop. For example ...
1675 export 5467 /spider/perl/keps.in
1679 would export message number 5467 as a file called keps.in in the
1680 /spider/perl directory.
1683 Now login to a VT as sysop and cd /spider/perl. There is a command in
1684 the perl directory called convkeps.pl. All we need to do now is
1685 convert the file like so ...
1689 ./convkeps.pl keps.in
1693 Now go back to the cluster and issue the command ...
1701 That is it! the kepler data has been updated.
1704 6.8. The QRZ callbook
1706 The command sh/qrz will only work once you have followed a few simple
1707 steps. First you need to get a user ID and password from qrz.com.
1708 Simply go to the site and create one. Secondly you need to copy the
1709 file /spider/perl/Internet.pm to /spider/local and alter it to match
1710 your user ID and password. You also at this point need to set
1711 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1712 proprieter of qrz.com for allowing this access.
1715 6.9. Connecting logging programs
1717 There appear to be very few logging programs out there that support
1718 telnet especially the popular ones like LogEQF, Turbolog etc. This
1719 can make it difficult to connect to your own cluster! The way to do
1720 it is to make the logging program think it has a TNC attached to a com
1721 port on the logging PC and 'push' a linux login out to it. This is
1722 achieved very simply by the use of agetty.
1725 All that is required is to add a line in /etc/inittab to have the
1726 client ready for a connection on the com port of your choice.
1727 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1732 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1736 Add this after the standard runlevel lines in /etc/inittab. The above
1737 line works on ttyS1 (com2). Now as root, issue the command telinit q
1738 and it should be ready for connection. All that is required is a 3
1739 wire serial lead (tx, rx and signal ground). Tell you logging program
1740 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1741 Login as normal and then telnet from there to the cluster.
1746 In the spider tree will be a directory spider-web. This is a neat
1747 little java web applet that can be run from a website. The applet
1748 must run on the same machine as the cluster. The included README file
1752 I should comment here that the applet is precompiled, that is, ready
1753 to go. It was compiled using JDK1.3.1. If your version is earlier
1754 than this then it may not work. Should that be the case you need to
1755 recompile or update your JDK. To recompile do the following ...
1759 cd /spider/spider-web
1761 /usr/bin/javac spiderclient.java
1765 I have used /usr/bin/javac as an example, your path to javac may be
1771 Completely based on a clx web client written in Java by dl6dbh
1772 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1774 The webserver has to run on the same machine as your DxSpider software!
1776 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1778 Installation instructions (Performed as root):
1780 Put all the files in the spider-web directory into a newly created directory
1781 under the DocumentRoot of your websever for instance 'client'. In my case
1782 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1783 path should be /usr/local/httpd/htdocs/client/ for example.
1785 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1786 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1787 /usr/local/httpd/cgi-bin/ for example.
1789 Change the permissions of the files to ensure they are correct, obviously you
1790 will need to use the correct path the the files according to your system:
1792 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1793 chmod -R 755 /home/httpd/html/client/
1795 By default the spider.cgi script should pick up your hostname (As long as this
1796 is set correctly). If it does not or your hostname differs from the name that
1797 you attach to the public address that you are using, then edit spider.cgi :
1799 # Uncomment and set the hostname manually here if the above fails.
1800 # $HOSTNAME = "gb7mbc.spoo.org" ;
1804 telnet (see Listeners.pm)
1806 NOTE: If you can start the console but cannot connect to the cluster from it,
1807 then it is possible that the machine you are on cannot resolve the hostname of
1808 your cluster machine. If this is the case, you need to set your hostname
1811 You also need to set the $NODECALL variable. This prints the name of your
1812 choosing (probably your cluster callsign) on the html page.
1814 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1818 8. Web based statistics
1820 From version 1.50, you can use the freeware software MRTG to produce
1821 really nice graphical statistics on your web site. For an example try
1822 http://www.gb7mbc.net/mrtg/stats.html.
1825 The following should help you get it all working.
1828 First you need to download the latest version of MRTG from
1829 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1830 the following files..
1834 libpng-1.0.14.tar.gz
1840 Login to your machine as the root user, put all the downloaded files
1841 in /usr/local/src/ (or wherever you prefer) and untar and compile
1842 them. All the information to compile and install these sources come
1843 with them. After compilation and installation, you will find MRTG in
1847 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1851 You now need to make 2 symbolic links like below...
1855 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1856 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1860 Now login to the cluster with your sysop callsign and run the command
1864 Now you are nearly there! Login as the sysop user and change to the
1865 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1870 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1874 Changing the callsign for your own cluster callsign of course!
1877 And finally you need to login as the root user and create one last
1878 symbolic link. Where this points will depend on where your html
1879 documents are kept. For RedHat systems you use...
1883 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1887 and for SuSE systems...
1891 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1895 If you now point your browser to your website as below it should all
1900 http://www.xxx.xxx/mrtg/stats.html
1904 Of course, to get the stats to update, you need to add some
1905 information in the spider crontab file as below...
1909 # Update stats for mrtg on website
1910 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1914 This will update the site every 5 minutes.
1919 From version 1.49 DXSpider has some additional security features.
1920 These are not by any means meant to be exhaustive, however they do
1921 afford some security against piracy. These two new features can be
1922 used independently of each other or in concert to tighten the
1928 The basic principle of registration is simple. If a user is not
1929 registered by the sysop, then they have read-only access to the
1930 cluster. The only thing they can actually send is a talk or a message
1931 to the sysop. In order for them to be able to spot, send announces or
1932 talks etc the sysop must register them with the set/register command,
1941 The user g0vgs can now fully use the cluster. In order to enable
1942 registration, you can issue the command ...
1944 set/var $main::reqreg = 1
1948 Any users that are not registered will now see the motd_nor file
1949 rather than the motd file as discussed in the Information, files and
1950 useful programs section.
1953 Entering this line at the prompt will only last for the time the
1954 cluster is running of course and would not be present on a restart.
1955 To make the change permanent, add the above line to
1956 /spider/scripts/startup. To read more on the startup file, see the
1957 section on Information, files and useful programs.
1960 To unregister a user use unset/register and to show the list of
1961 registered users, use the command show/register.
1966 At the moment, passwords only affect users who login to a DXSpider
1967 cluster node via telnet. If a user requires a password, they can
1968 either set it themselves or have the sysop enter it for them by using
1969 the set/password command. Any users who already have passwords, such
1970 as remote sysops, will be asked for their passwords automatically by
1971 the cluster. Using passwords in this way means that the user has a
1972 choice on whether to have a password or not. To force the use of
1973 passwords at login, issue the command ...
1977 set/var $main::passwdreq = 1
1981 at the cluster prompt. This can also be added to the
1982 /spider/scripts/startup file as above to make the change permanent.
1985 Of course, if you do this you will have to assign a password for each
1986 of your users. If you were asking them to register, it is anticipated
1987 that you would ask them to send you a message both to ask to be
1988 registered and to give you the password they wish to use.
1991 Should a user forget their password, it can be reset by the sysop by
1992 first removing the existing password and then setting a new one like
1997 unset/password g0vgs
1998 set/password g0vgs new_password
2006 10.1. CVS from a Linux platform
2008 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2009 is held at Sourceforge. This means that it is possible to update your
2010 DXSpider installation to the latest sources by using a few simple
2011 commands. A graphical interface to CVS for Windows is explained in
2015 Please be aware that if you update your system using CVS, it is
2016 possible that you could be running code that is very beta and not
2017 fully tested. There is a possibility that it could be unstable.
2020 I am of course assuming that you have a machine with both DXSpider and
2021 Internet access running.
2024 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2025 ENTIRE SPIDER TREE!!
2028 Assuming you are connected to the Internet, you need to login to the
2029 CVS repository and then update your Spider source. There are several
2030 steps which are listed below ...
2033 First login as the user sysop. Next you need to connect to the CVS
2034 repository. You do this with the command below ...
2037 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2041 You will get a password prompt. Simply hit return here and your
2042 machine should return to a normal linux prompt.
2045 What happens next depends on whether you have an existing installation
2046 that you want to update with the latest and greatest or whether you
2047 just want to see what is there and/or run it on a new machine for
2050 If you are installing Spider from CVS then change directory to
2053 If you are wanting to update Spider then cd to /tmp
2056 The next step will create a brand new 'spider' directory in your
2060 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2064 This command is all on one line.
2067 Hopefully your screen should show you downloading files. The -z3
2068 simply compresses the download to improve speed. When this has
2069 finished, you will have exactly the same as if you had untarred a full
2070 tarball PLUS some extra directories and files that CVS needs to do the
2072 Now if you are doing a new installation, that's it. Carry on as if
2073 you have just downloaded and untarred the lastest tarball.
2076 If you want to upgrade your current installation then do this ...
2080 tar cvfz /tmp/s.tgz spider
2082 tar xvfzp /tmp/s.tgz
2086 This is assuming you downloaded to the /tmp directory of course.
2089 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2090 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2093 Remember to recompile the C client (cd /spider/src; make)
2096 At this point the files have been upgraded. You can (usually) restart
2097 the cluster in your own time. However, if you attempt to use any new
2098 commands or features expect it to be fatal! At least your cluster
2099 will have been restarted then so it will be too late to worry about
2103 Now the magic part! From now on when you want to update, simply
2104 connect to the Internet and then, as the user sysop ...
2113 and your files will be updated. As above, remember to recompile the
2114 "C" client if it has been updated (CVS will tell you) and restart if
2115 any of the perl scripts have been altered or added, again, CVS will
2119 You will find any changes documented in the /spider/Changes file.
2122 10.2. CVS from a Windows platform
2124 After the initial setup, an update to your DXSpider software is no
2125 more than a couple of clicks away. This section is intended to
2126 explain and illustrate the use of the WinCVS application to update
2127 your DXSpider software. The current stable version of WinCVS is Ver.
2128 1.2. You can get this software at:
2130 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2132 Pick your download mirror and then install WinCVS after the download
2136 In this next section I have included a series of links to .jpg files
2137 to take advantage of the picture and 1000 words equivalency. The .jpg
2138 files are in the C:\spider\html directory. If someone using a Linux
2139 system is reading this section from boredom, the files are in
2140 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2141 of gcvs and do your updates graphically as opposed to from the command
2142 line. The following descriptions are almost identical between WinCvs
2143 and gcvs. The following screen shots have duplicate links, depending
2144 upon whether you are viewing this information under the Windows or
2145 Linux operating system.
2147 When WinCVS is installed, running, and you are connected to the
2148 internet, the initial screen looks like:
2152 If you want, you can also look at these .jpg files with another viewer
2153 that might provide some better clarity to the image. On the left is
2154 the directory tree for your hard disk. Notice that the spider
2155 directory has a gray highlight.
2157 To start configuring WinCVS, click on Admin at the top of the screen
2158 and then Preferences. This should get you:
2162 In the top line for CVSROOT, enter:
2165 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2172 "passwd" file on the cvs server
2176 for Authentication on the General tab.
2178 Next, move to the right to the Ports tab.
2182 In here, check the box on the second line down for the "pserver" port.
2183 Enter a port number of 2401.
2185 Finally, go to the WinCvs tab all the way to the right.
2189 Enter Notepad as the viewer to open files. For the HOME folder, put
2190 "C:\spider" and click OK because the configuration is now complete.
2192 You are now ready to upgrade your copy of DXSpider. Click on the
2193 greyed Spider folder shown in the directory tree on the left of the
2194 WinCVS display. Two things should happen. The Spider folder will be
2195 selected and the greyed-out arrow located just below the word Query in
2196 the top line will turn to solid green.
2198 For anyone using gcvs under Linux, the green arrow is located on the
2199 extreme left of the display, under the word File. A gcvs screen looks
2204 Click on the now green arrow to start the download process. An Update
2205 Settings box will be displayed to which you can simply say OK.
2209 For future reference, the Update Settings box is the place where you
2210 can enter information to revert to a prior version of DXSpider.
2211 Information on reverting to a Before Date is contained in the WinCVS
2214 After a short period of time, a series of file names will scroll by in
2215 the lower pane of the WinCVS window. Eventually you should see
2218 *****CVS exited normally with code 0*****
2222 appear in the lower pane. You're done. The updated files are in
2223 place ready for you to stop and then restart your DXSpider. After the
2224 restart, you're running with the latest version of DXSpider.
2228 To paraphrase from the CVS section... Now the magic part! From now on
2229 when you want to update, simply connect to the Internet and start
2233 Click on the greyed-out Spider directory in the left screen
2234 Click on the green down arrow
2235 Click OK on the Update Settings dialog box
2236 Restart your Spider software
2240 11. The DXSpider command set
2244 accept Set a filter to accept something
2246 Create a filter to accept somethingThere are 2 types of filter, accept
2247 and reject. See HELP FILTERING for moreinfo.
2249 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
2251 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2254 This version allows a sysop to set a filter for a callsign as well as
2255 thedefault for nodes and users eg:-
2258 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2262 11.3. accept/announce [0-9] <pattern> (0)
2264 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2267 Create an 'accept this announce' line for a filter. An accept filter
2268 line means that if the announce matches this filter it ispassed onto
2269 the user. See HELP FILTERING for more info. Please read thisto
2270 understand how filters work - it will save a lot of grief later on.You
2271 can use any of the following things in this line:-
2274 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)
2281 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)
2295 acc/ann by_state va,nh,ri,nh
2299 You can use the tag 'all' to accept everything eg:
2306 but this probably for advanced users...
2308 11.4. accept/route <call> [0-9] <pattern> (8)
2310 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2313 Create an 'accept this routing PC Protocol' line for a filter. An
2314 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2315 filter it is passed thru that interface. See HELP FILTERING for more
2316 info. Please read thisto understand how filters work - it will save a
2317 lot of grief later on.You can use any of the following things in this
2321 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
2328 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2332 you can now use 'by' as a synonym for 'call' so:
2335 by = call by_dxcc = call_dxcc
2339 and so onYou can use the tag 'all' to accept everything eg:
2346 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
2348 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2350 This version allows a sysop to set a filter for a callsign as well as
2351 thedefault for nodes and users eg:-
2354 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2358 accept/spot user_default by G,M,2
2362 11.6. accept/spots [0-9] <pattern> (0)
2364 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2366 Create an 'accept this spot' line for a filter. An accept filter line
2367 means that if the spot matches this filter it ispassed onto the user.
2368 See HELP FILTERING for more info. Please read thisto understand how
2369 filters work - it will save a lot of grief later on.You can use any of
2370 the following things in this line:-
2373 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>
2377 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2381 You can use the tag 'all' to accept everything, eg:
2391 acc/spots by_state VA,NH,RI,MA,ME
2395 but this probably for advanced users...
2397 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
2399 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2401 This version allows a sysop to set a filter for a callsign as well as
2402 thedefault for nodes and users eg:-
2405 accept/wcy node_default all set/hops node_default 10
2409 11.8. accept/wcy [0-9] <pattern> (0)
2411 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2413 It is unlikely that you will want to do this, but if you do then you
2414 canfilter on the following fields:-
2417 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>
2421 There are no examples because WCY Broadcasts only come from one place
2422 andyou either want them or not (see UNSET/WCY if you don't want
2423 them).This command is really provided for future use.See HELP FILTER
2426 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
2428 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2430 This version allows a sysop to set a filter for a callsign as well as
2431 thedefault for nodes and users eg:-
2434 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2438 accept/wwv user_default by W,K
2442 11.10. accept/wwv [0-9] <pattern> (0)
2444 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2446 It is unlikely that you will want to do this, but if you do then you
2447 canfilter on the following fields:-
2450 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>
2457 accept/wwv by_zone 4
2461 is probably the only useful thing to do (which will only show WWV
2462 broadcastsby stations in the US).See HELP FILTER for information.
2464 11.11. announce <text> (0)
2466 announce <text> Send an announcement to LOCAL users only
2468 <text> is the text of the announcement you wish to broadcast
2470 11.12. announce full <text> (0)
2472 announce full <text> Send an announcement cluster wide
2474 This will send your announcement cluster wide
2476 11.13. announce sysop <text> (5)
2478 announce sysop <text> Send an announcement to Sysops only
2481 11.14. apropos <string> (0)
2483 apropos <string> Search help database for <string>
2485 Search the help database for <string> (it isn't case sensitive), and
2486 printthe names of all the commands that may be relevant.
2488 11.15. blank [<string>] [<nn>] (0)
2490 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2492 In its basic form this command prints one or more blank lines. However
2493 ifyou pass it a string it will replicate the string for the width of
2494 the screen (default 80) and then print that one or more times, so:
2501 prints two blank lines
2508 prints a row of - characters once.
2515 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2516 script file and you can print a maximumof 9 lines.
2520 bye Exit from the cluster
2522 This will disconnect you from the cluster
2524 11.17. catchup <node call> all|[<msgno> ...] (5)
2526 catchup <node call> all|[<msgno> ...] Mark a message as sent
2529 11.18. clear/announce <callsign> [input] [0-9|all] (8)
2531 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2534 A sysop can clear an input or normal output filter for a user or
2535 thenode_default or user_default.
2537 11.19. clear/announce [1|all] (0)
2539 clear/announce [1|all] Clear a announce filter line
2541 This command allows you to clear (remove) a line in a annouce filter
2542 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2545 11.20. clear/route <callsign> [input] [0-9|all] (8)
2547 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2549 A sysop can clear an input or normal output filter for a user or
2550 thenode_default or user_default.
2552 11.21. clear/route [1|all] (0)
2554 clear/route [1|all] Clear a route filter line
2556 This command allows you to clear (remove) a line in a route filter or
2557 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2560 11.22. clear/spots <callsign> [input] [0-9|all] (8)
2562 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2564 A sysop can clear an input or normal output filter for a user or
2565 thenode_default or user_default.
2567 11.23. clear/spots [0-9|all] (0)
2569 clear/spots [0-9|all] Clear a spot filter line
2571 This command allows you to clear (remove) a line in a spot filter or
2572 to remove the whole filter.If you have a filter:-
2575 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2585 you will be left with:-
2588 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2599 the filter will be completely removed.
2601 11.24. clear/wcy <callsign> [input] [0-9|all] (8)
2603 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2605 A sysop can clear an input or normal output filter for a user or
2606 thenode_default or user_default.
2608 11.25. clear/wcy [1|all] (0)
2610 clear/wcy [1|all] Clear a WCY filter line
2612 This command allows you to clear (remove) a line in a WCY filter or to
2613 remove the whole filter.see CLEAR/SPOTS for a more detailed
2616 11.26. clear/wwv <callsign> [input] [0-9|all] (8)
2618 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2620 A sysop can clear an input or normal output filter for a user or
2621 thenode_default or user_default.
2623 11.27. clear/wwv [1|all] (0)
2625 clear/wwv [1|all] Clear a WWV filter line
2627 This command allows you to clear (remove) a line in a WWV filter or to
2628 remove the whole filter.see CLEAR/SPOTS for a more detailed
2631 11.28. connect <callsign> (5)
2633 connect <callsign> Start a connection to another DX Cluster
2635 Start a connection process that will culminate in a new connection to
2636 theDX cluster <callsign>. This process creates a new 'client' process
2637 which willuse the script in /spider/connect/<callsign> to effect the
2638 'chat' exchangenecessary to traverse the network(s) to logon to the
2643 dbavail Show a list of all the Databases in the system
2645 Title says it all really, this command lists all the databases
2646 definedin the system. It is also aliased to SHOW/COMMAND.
2647 11.30. dbshow <dbname> <key> (0)
2649 dbshow <dbname> <key> Display an entry, if it exists, in a database
2651 This is the generic user interface to the database to the database
2652 system.It is expected that the sysop will add an entry to the local
2653 Aliases fileso that users can use the more familiar AK1A style of
2661 but if he hasn't and the database really does exist (use DBAVAIL
2662 orSHOW/COMMAND to find out) you can do the same thing with:
2669 11.31. directory (0)
2671 directory List messages
2674 11.32. directory <from>-<to> (0)
2676 directory <from>-<to> List messages <from> message <to> message
2678 List the messages in the messages directory.If there is a 'p' one
2679 space after the message number then it is a personal message. If there
2680 is a '-' between the message number and the'p' then this indicates
2681 that the message has been read.You can use shell escape characters
2682 such as '*' and '?' in the <call>fields.You can combine some of the
2683 various directory commands together eg:-
2693 DIR SUBJECT IOTA 200-250
2697 You can abbreviate all the commands to one letter and use ak1a syn-
2701 DIR/T G1* 10 DIR/S QSL 10-100 5
2705 11.33. directory <nn> (0)
2707 directory <nn> List last <nn> messages
2711 11.34. directory all (0)
2713 directory all List all messages
2716 11.35. directory from <call> (0)
2718 directory from <call> List all messages from <call>
2721 11.36. directory new (0)
2723 directory new List all new messages
2726 11.37. directory own (0)
2728 directory own List your own messages
2731 11.38. directory subject <string> (0)
2733 directory subject <string> List all messages with <string> in subject
2736 11.39. directory to <call> (0)
2738 directory to <call> List all messages to <call>
2741 11.40. directory- (5)
2745 Sysops can see all users' messages.
2747 11.41. disconnect <call> [<call> ...] (8)
2749 disconnect <call> [<call> ...] Disconnect a user or cluster
2751 Disconnect any <call> connected locally
2753 11.42. dx [by <call>] <freq> <call> <remarks> (0)
2755 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2757 This is how you send a DX Spot to other users. You can, in fact,
2758 nowenter the <freq> and the <call> either way round.
2761 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
2765 will all give the same result. You can add some remarks to the endof
2766 the command and they will be added to the spot.
2769 DX FR0G 144600 this is a test
2773 You can credit someone else by saying:-
2777 DX by G1TLH FR0G 144.600 he isn't on the cluster
2781 The <freq> is compared against the available bands set up in the clus-
2782 ter. See SHOW/BANDS for more information.
2784 11.43. echo <line> (0)
2786 echo <line> Echo the line to the output
2788 This command is useful in scripts and so forth for printing theline
2789 that you give to the command to the output. You can use thisin
2790 user_default scripts and the SAVE command for titling and so forthThe
2791 script will interpret certain standard "escape" sequences as follows:-
2794 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
2798 So the following example:-
2801 echo GB7DJK is a dxcluster
2808 GB7DJK is a dxcluster
2812 on the output. You don't need a \n on the end of the line you want to
2813 send.A more complex example:-
2816 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
2823 GB7DJK g1tlh Dirk g3xvf Richard
2829 11.44. filtering... (0)
2831 filtering... Filtering things in DXSpider
2833 There are a number of things you can filter in the DXSpider system.
2834 Theyall use the same general mechanism.In general terms you can create
2835 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
2836 You do this using, for example:-
2839 accept/spots ..... reject/spots .....
2843 where ..... are the specific commands for that type of filter. There-
2844 are filters for spots, wwv, announce, wcy and (for sysops)connects.
2845 See each different accept or reject command reference formore
2846 details.There is also a command to clear out one or more lines in a
2847 filter andone to show you what you have set. They are:-
2850 clear/spots 1 clear/spots all
2861 There is clear/xxxx command for each type of filter.For now we are
2862 going to use spots for the examples, but you can applythe principles
2863 to all types of filter.There are two main types of filter 'accept' or
2864 'reject'; which you usedepends entirely on how you look at the world
2865 and what is leastwriting to achieve what you want. Each filter has 10
2866 lines (of anylength) which are tried in order. If a line matches then
2867 the actionyou have specified is taken (ie reject means ignore it and
2868 acceptmeans gimme it).The important thing to remember is that if you
2869 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
2870 instance)) then ifa spot comes in that doesn't match any of the lines
2871 then you will getit BUT if you specify an 'accept' filter then any
2872 spots that don'tmatch are dumped. For example if I have a one line
2876 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2880 then automatically you will ONLY get VHF spots from or to CQ zones
2881 1415 and 16. If you set a reject filter like:
2884 reject/spots on hf/cw
2888 Then you will get everything EXCEPT HF CW spots, If you am interested
2889 in IOTAand will work it even on CW then you could say:-
2892 reject/spots on hf/cw and not info iota
2896 But in that case you might only be interested in iota and say:-
2899 accept/spots not on hf/cw or info iota
2903 which is exactly the same. You should choose one or the other untilyou
2904 are confortable with the way it works. Yes, you can mix them(actually
2905 you can have an accept AND a reject on the same line) butdon't try
2906 this at home until you can analyse the results that you getwithout
2907 ringing up the sysop for help.Another useful addition now is filtering
2909 accept/spots by_state VA,NH,RI,ME
2913 You can arrange your filter lines into logical units, either for
2914 yourown understanding or simply convenience. I have one set fre-
2918 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2922 What this does is to ignore all HF CW spots (being a class B I
2923 can'tread any CW and couldn't possibly be interested in HF :-) and
2924 alsorejects any spots on VHF which don't either originate or spot
2925 someonein Europe.This is an exmaple where you would use the line num-
2926 ber (1 and 2 inthis case), if you leave the digit out, the system
2927 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
2928 out if you want, it is implied. You canuse any number of brackets to
2929 make the 'expression' as you wantit. There are things called prece-
2930 dence rules working here which meanthat you will NEED brackets in a
2931 situation like line 2 because,without it, will assume:-
2934 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2938 annoying, but that is the way it is. If you use OR - usebrackets.
2939 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
2940 by_zone'.If you want to alter your filter you can just redefine one or
2941 morelines of it or clear out one line. For example:-
2944 reject/spots 1 on hf/ssb
2955 To remove the filter in its entirty:-
2962 There are similar CLEAR commands for the other filters:-
2965 clear/announce clear/wcy clear/wwv
2969 ADVANCED USERS:-Once you are happy with the results you get, you may
2970 like to experiment. my example that filters hf/cw spots and accepts
2971 vhf/uhf spots from EUcan be written with a mixed filter, eg:
2975 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)
2979 each filter slot actually has a 'reject' slot and an 'accept'slot. The
2980 reject slot is executed BEFORE the accept slot.It was mentioned ear-
2981 lier that after a reject test that doesn't match,the default for fol-
2982 lowing tests is 'accept', the reverse is true for'accept'. In the
2983 example what happens is that the reject is executedfirst, any non
2984 hf/cw spot is passed to the accept line, which letsthru everything
2985 else on HF.The next filter line lets through just VHF/UHF spots from
2988 11.45. forward/latlong <node_call> (8)
2990 forward/latlong <node_call> Send latitude and longitude information to
2993 This command sends all the latitude and longitude information that
2994 yourcluster is holding against callsigns. One advantage of recieving
2995 thisinformation is that more locator information is held by you.
2996 Thismeans that more locators are given on the DX line assuming you
2997 haveSET/DXGRID enabled. This could be a LOT of information though,
2998 soit is not recommended on slow links.
3000 11.46. forward/opernam <call> (1)
3002 forward/opernam <call> Send out information on this <call> to all
3005 This command sends out any information held in the user file which can
3006 be broadcast in PC41 protocol packets. This information is Name, QTH,
3007 Locationand Homenode. PC41s are only sent for the information that is
3012 help The HELP Command
3014 HELP is available for a number of commands. The syntax is:-
3021 Where <cmd> is the name of the command you want help on.All commands
3022 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3023 can be shortened to AN and so on.Look at the APROPOS <string> command
3024 which will search the help databasefor the <string> you specify and
3025 give you a list of likely commandsto look at with HELP.
3027 11.48. init <node> (5)
3029 init <node> Re-initialise a link to an AK1A compatible node
3031 This command attempts to re-initialise a link to a (usually) AK1A
3032 nodethat has got confused, usually by a protocol loop of some kind. It
3033 maywork - but you usually will be better off simply disconnecting it
3034 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3035 <yournode>).Best of luck - you will need it.
3041 As a sysop you can kill any message on the system.
3043 11.50. kill <from msgno>-<to msgno> (0)
3045 kill <from msgno>-<to msgno> Delete a range of messages
3048 11.51. kill <from>-<to> (5)
3050 kill <from>-<to> Remove a range of messages from the system
3053 11.52. kill <msgno> [<msgno..] (0)
3055 kill <msgno> [<msgno..] Delete a message from the local system
3058 11.53. kill <msgno> [<msgno> ...] (0)
3060 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3062 You can get rid of any message to or originating from your callsign
3063 using this command. You can remove more than one message at a time.
3065 11.54. kill expunge <msgno> [<msgno..] (6)
3067 kill expunge <msgno> [<msgno..] Expunge a message
3069 Deleting a message using the normal KILL commands only marks that
3070 messagefor deletion. The actual deletion only happens later (usually
3071 two days later).The KILL EXPUNGE command causes the message to be
3072 truly deleted more or lessimmediately.It otherwise is used in the same
3073 way as the KILL command.
3075 11.55. kill from <call> (5)
3077 kill from <call> Remove all messages from a callsign
3080 11.56. kill full <msgno> [<msgno..] (5)
3082 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3084 Delete a message from the local system. You will only be able todelete
3085 messages that you have originated or been sent (unless you arethe
3093 Will delete all the messages that you own between msgnos 1234 and
3101 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3107 will delete all messages to g1tlh.
3114 will delete a message (usually a 'bulletin') from the whole cluster
3115 system. This uses the subject field, so any messages that have exactly
3116 thesame subject will be deleted. Beware!
3118 11.57. kill full <msgno> [<msgno] (5)
3120 kill full <msgno> [<msgno] Remove a message from the entire cluster
3122 Remove this message from the entire cluster system as well as your
3125 11.58. kill to <call> (5)
3127 kill to <call> Remove all messages to a callsign
3130 11.59. kill from <regex> (0)
3132 kill from <regex> Delete messages FROM a callsign or pattern
3135 11.60. kill to <regex> (0)
3137 kill to <regex> Delete messages TO a callsign or pattern
3142 links Show which nodes is physically connected
3144 This is a quick listing that shows which links are connected andsome
3145 information about them. See WHO for a list of all connections.
3147 11.62. load/keps (5)
3149 load/keps Load new keps data
3152 11.63. load/keps [nn] (5)
3154 load/keps [nn] Load new keps data from message
3156 If there is no message number then reload the current Keps data
3157 fromthe Keps.pm data file. You create this file by running
3160 /spider/perl/convkeps.pl <filename>
3164 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3165 there is a message number, then it will take the message, runcon-
3166 vkeps.pl on it and then load the data, all in one step.These messages
3167 are sent to ALL by GB7DJK (and others) from time to time.
3169 11.64. merge <node> [<no spots>/<no wwv>] (5)
3171 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3173 MERGE allows you to bring your spot and wwv database up to date. By
3174 defaultit will request the last 10 spots and 5 WWVs from the node you
3175 select. The node must be connected locally.You can request any number
3176 of spots or wwv and although they will be appendedto your databases
3177 they will not duplicate any that have recently been added (the last 2
3178 days for spots and last month for WWV data).
3180 11.65. pc <call> <text> (8)
3182 pc <call> <text> Send arbitrary text to a connected callsign
3184 Send some arbitrary text to a locally connected callsign. Noprocessing
3185 is done on the text. This command allows you to send PCProtocol to
3186 unstick things if problems arise (messages get stucketc). eg:-
3189 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3196 pc G1TLH Try doing that properly!!!
3200 Send any text you like to the callsign requested. This is used mainly
3201 to sendPC protocol to connected nodes either for testing or to unstick
3202 things. You can also use in the same way as a talk command to a con-
3203 nected user butwithout any processing, added of "from <blah> to <blah"
3206 11.66. ping <node call> (1)
3208 ping <node call> Check the link quality between nodes
3210 This command allows you to send a frame to another cluster node onthe
3211 network and get a return frame. The time it takes to do thisis a good
3212 indication of the quality of the link. The actual timeit takes is
3213 output to the console in seconds.Any visible cluster node can be
3216 11.67. rcmd <node call> <cmd> (1)
3218 rcmd <node call> <cmd> Send a command to another DX Cluster
3220 This command allows you to send nearly any command to another DX
3221 Clusternode that is connected to the system. Whether you get any
3222 output is dependant on a) whether the other system knowsthat the node
3223 callsign of this cluster is in fact a node b) whether theother system
3224 is allowing RCMDs from this node and c) whether you havepermission to
3225 send this command at all.
3229 read Read the next unread personal message addressed to you
3232 11.69. read <msgno> (0)
3234 read <msgno> Read the specified message
3236 You can read any messages that are sent as 'non-personal' and also
3237 anymessage either sent by or sent to your callsign.
3243 As a sysop you may read any message on the system
3247 reject Set a filter to reject something
3249 Create a filter to reject somethingThere are 2 types of filter, accept
3250 and reject. See HELP FILTERING for moreinfo.
3252 11.72. reject/announce <call> [input] [0-9] <pattern> (8)
3254 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3257 This version allows a sysop to set a filter for a callsign as well as
3258 thedefault for nodes and users eg:-
3261 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3265 11.73. reject/announce [0-9] <pattern> (0)
3267 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3270 Create an 'reject this announce' line for a filter. A reject filter
3271 line means that if the announce matches this filter it ispassed onto
3272 the user. See HELP FILTERING for more info. Please read thisto
3273 understand how filters work - it will save a lot of grief later on.You
3274 can use any of the following things in this line:-
3277 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)
3284 rej/ann by_zone 14,15,16 and not by G,M,2
3288 You can use the tag 'all' to reject everything eg:
3295 but this probably for advanced users...
3297 11.74. reject/route <call> [0-9] <pattern> (8)
3299 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3302 Create an 'reject this routing PC Protocol' line for a filter. An
3303 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3304 filter it is NOT passed thru that interface. See HELP FILTERING for
3305 more info. Please read this to understand how filters work - it will
3306 save a lot of grief later on.You can use any of the following things
3310 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
3317 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3321 You can use the tag 'all' to reject everything eg:
3324 rej/route all (equiv to [very] restricted mode)
3328 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3330 11.75. reject/spots <call> [input] [0-9] <pattern> (8)
3332 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3334 This version allows a sysop to set a filter for a callsign as well as
3335 thedefault for nodes and users eg:-
3338 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3342 reject/spot user_default by G,M,2
3346 11.76. reject/spots [0-9] <pattern> (0)
3348 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3350 Create a 'reject this spot' line for a filter. A reject filter line
3351 means that if the spot matches this filter it isdumped (not passed
3352 on). See HELP FILTERING for more info. Please read thisto understand
3353 how filters work - it will save a lot of grief later on.You can use
3354 any of the following things in this line:-
3357 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>
3361 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3365 You can use the tag 'all' to reject everything eg:
3372 but this probably for advanced users...
3374 11.77. reject/wcy <call> [input] [0-9] <pattern> (8)
3376 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3378 This version allows a sysop to set a filter for a callsign as well as
3379 thedefault for nodes and users eg:-
3382 reject/wcy gb7djk all
3386 11.78. reject/wcy [0-9] <pattern> (0)
3388 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3390 It is unlikely that you will want to do this, but if you do then you
3391 canfilter on the following fields:-
3394 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>
3398 There are no examples because WCY Broadcasts only come from one place
3399 andyou either want them or not (see UNSET/WCY if you don't want
3400 them).This command is really provided for future use.See HELP FILTER
3403 11.79. reject/wwv <call> [input] [0-9] <pattern> (8)
3405 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3407 This version allows a sysop to set a filter for a callsign as well as
3408 thedefault for nodes and users eg:-
3411 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3415 reject/wwv user_default by W
3419 11.80. reject/wwv [0-9] <pattern> (0)
3421 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3423 It is unlikely that you will want to do this, but if you do then you
3424 canfilter on the following fields:-
3427 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>
3434 reject/wwv by_zone 14,15,16
3438 is probably the only useful thing to do (which will only show WWV
3439 broadcastsby stations in the US).See HELP FILTER for information.
3443 reply Reply (privately) to the last message that you have read
3446 11.82. reply <msgno> (0)
3448 reply <msgno> Reply (privately) to the specified message
3451 11.83. reply b <msgno> (0)
3453 reply b <msgno> Reply as a Bulletin to the specified message
3456 11.84. reply noprivate <msgno> (0)
3458 reply noprivate <msgno> Reply as a Bulletin to the specified message
3461 11.85. reply rr <msgno> (0)
3463 reply rr <msgno> Reply to the specified message with read receipt
3465 You can reply to a message and the subject will automatically
3466 have"Re:" inserted in front of it, if it isn't already present.You can
3467 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3468 that you can use with the SEND command (see SENDfor further details)
3470 11.86. send <call> [<call> ...] (0)
3472 send <call> [<call> ...] Send a message to one or more callsigns
3475 11.87. send copy <msgno> <call> (0)
3477 send copy <msgno> <call> Send a copy of a message to someone
3480 11.88. send noprivate <call> (0)
3482 send noprivate <call> Send a message to all stations
3484 All the SEND commands will create a message which will be sent either
3485 toan individual callsign or to one of the 'bulletin' addresses. SEND
3486 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3487 will mark the message as personal and send it to the cluster node
3488 thatthat callsign is connected to. If the <call> you have specified is
3489 in facta known bulletin category on your node (eg: ALL) then the
3490 message shouldautomatically become a bulletin.You can have more than
3491 one callsign in all of the SEND commands.You can have multiple
3492 qualifiers so that you can have for example:-
3493 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3497 which should send a copy of message 123 to G1TLH and G0RDI and you
3498 willreceive a read receipt when they have read the message.SB is an
3499 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3500 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3501 tionally this should be no longer than 29 characters for compatibil-
3502 ity. Most modern clustersoftware should accept more.You will now be
3503 prompted to start entering your text. You finish the message by enter-
3504 ing '/EX' on a new line. For instance:
3507 ... bye then Jim 73 Dirk /ex
3511 If you have started a message and you don't want to keep it then you-
3512 can abandon the message with '/ABORT' on a new line, like:-
3515 line 1 line 2 oh I just can't be bothered with this /abort
3519 If you abort the message it will NOT be sent.When you are entering the
3520 text of your message, most normal output (suchas DX announcements and
3521 so on are suppressed and stored for latter display(upto 20 such lines
3522 are stored, as new ones come along, so the oldestlines are
3523 dropped).Also, you can enter normal commands commands (and get the
3524 output immediately) whilst in the middle of a message. You do this by
3525 typingthe command preceeded by a '/' character on a new line, so:-
3528 /dx g1tlh 144010 strong signal
3532 Will issue a dx annoucement to the rest of the cluster. Also, you can
3533 add the output of a command to your message by preceeding the command
3541 This will show YOU the output from SH/VHFTABLE and also store it in
3542 themessage. You can carry on with the message until you are ready to
3545 11.89. send private <call> (0)
3547 send private <call> Send a personal message
3550 11.90. send rr <call> (0)
3552 send rr <call> Send a message and ask for a read receipt
3555 11.91. set/address <your address> (0)
3557 set/address <your address> Record your postal address
3559 11.92. set/announce (0)
3561 set/announce Allow announce messages to come out on your terminal
3564 11.93. set/anntalk (0)
3566 set/anntalk Allow talk like announce messages on your terminal
3569 11.94. set/arcluster <call> [<call>..] (5)
3571 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
3574 11.95. set/baddx <call>.. (8)
3576 set/baddx <call>.. Stop callsigns in a dx spot being propagated
3579 11.96. set/badnode <call>.. (8)
3581 set/badnode <call>.. Stop spots from this node being propagated
3584 11.97. set/badspotter <call>.. (8)
3586 set/badspotter <call>.. Stop spots from this callsign being propagated
3589 11.98. set/badword <word>.. (8)
3591 set/badword <word>.. Stop things with this word being propagated
3594 11.99. set/bbs <call> [<call>..] (5)
3596 set/bbs <call> [<call>..] Make the callsign a BBS
3599 11.100. set/beep (0)
3601 set/beep Add a beep to DX and other messages on your terminal
3604 11.101. set/clx <call> [<call>..] (5)
3606 set/clx <call> [<call>..] Make the callsign an CLX node
3611 set/dx Allow DX messages to come out on your terminal
3614 11.103. set/dxgrid (0)
3616 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
3619 11.104. set/dxnet <call> [<call>..] (5)
3621 set/dxnet <call> [<call>..] Make the callsign an DXNet node
3625 11.105. set/dxstate (0)
3627 set/dxstate Allow US State info on the end of DX announcements
3630 11.106. set/echo (0)
3632 set/echo Make the cluster echo your input
3635 11.107. set/email <email> ... (0)
3637 set/email <email> ... Set email address(es) and forward your personals
3640 11.108. set/here (0)
3642 set/here Tell the system you are present at your terminal
3645 11.109. set/homenode <node> (0)
3647 set/homenode <node> Set your normal cluster callsign
3649 Tell the cluster system where you normally connect to. Any Messages
3650 sentto you will normally find their way there should you not be
3658 11.110. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
3660 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
3663 11.111. set/language <lang> (0)
3665 set/language <lang> Set the language you want to use
3667 You can select the language that you want the cluster to use.
3668 Currentlythe languages available are en (English), de (German), es
3669 (Spanish) and nl (Dutch).
3671 11.112. set/location <lat & long> (0)
3673 set/location <lat & long> Set your latitude and longitude
3676 11.113. set/logininfo (0)
3678 set/logininfo Inform when a station logs in locally
3681 11.114. set/name <your name> (0)
3683 set/name <your name> Set your name
3685 Tell the system what your name is eg:-
3690 11.115. set/node <call> [<call>..] (5)
3692 set/node <call> [<call>..] Make the callsign an AK1A cluster
3694 Tell the system that the call(s) are to be treated as AK1A cluster
3695 andfed PC Protocol rather normal user commands.
3697 11.116. set/obscount <count> <call> (8)
3699 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
3701 From 1.35 onwards neighbouring nodes are pinged at regular intervals
3702 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
3703 'pump-up'counter which is decremented on every outgoing ping and then
3704 reset tothe 'obscount' value on every incoming ping. The default value
3705 of thisparameter is 2. What this means is that a neighbouring node
3706 will be pinged twice at (default) 300 second intervals and if no reply
3707 has been heard just beforewhat would be the third attempt, that node
3708 is disconnected.If a ping is heard then the obscount is reset to the
3709 full value. Usingdefault values, if a node has not responded to a ping
3710 within 15 minutes,it is disconnected.You can set this parameter
3711 between 1 and 9.It is STRONGLY recommended that you don't change the
3714 11.117. set/page <lines per page> (0)
3716 set/page <lines per page> Set the lines per page
3718 Tell the system how many lines you wish on a page when the number of
3719 lineof output from a command is more than this. The default is 20.
3720 Setting itexplicitly to 0 will disable paging.
3723 SET/PAGE 30 SET/PAGE 0
3727 The setting is stored in your user profile.
3729 11.118. set/password (0)
3731 set/password Set your own password
3733 This command only works for a 'telnet' user (currently). It willonly
3734 work if you have a password already set. This initial passwordcan only
3735 be set by the sysop.When you execute this command it will ask you for
3736 your old password,then ask you to type in your new password twice (to
3737 make sure youget it right). You may or may not see the data echoed on
3738 the screenas you type, depending on the type of telnet client you
3741 11.119. set/prompt <string> (0)
3743 set/prompt <string> Set your prompt to <string>
3746 11.120. set/qra <locator> (0)
3748 set/qra <locator> Set your QRA Grid locator
3750 Tell the system what your QRA (or Maidenhead) locator is. If you have
3751 notdone a SET/LOCATION then your latitude and longitude will be set
3752 roughlycorrectly (assuming your locator is correct ;-). For example:-
3760 11.121. set/qth <your qth> (0)
3762 set/qth <your qth> Set your QTH
3764 Tell the system where you are. For example:-
3767 SET/QTH East Dereham, Norfolk
3771 11.122. set/spider <call> [<call>..] (5)
3773 set/spider <call> [<call>..] Make the callsign an DXSpider node
3775 Tell the system that the call(s) are to be treated as DXSpider node
3776 andfed new style DX Protocol rather normal user commands.
3778 11.123. set/talk (0)
3780 set/talk Allow TALK messages to come out on your terminal
3785 set/wcy Allow WCY messages to come out on your terminal
3790 set/wwv Allow WWV messages to come out on your terminal
3795 set/wx Allow WX messages to come out on your terminal
3798 11.127. show/baddx (1)
3800 show/baddx Show all the bad dx calls in the system
3802 Display all the bad dx callsigns in the system, see SET/BADDXfor more
3805 11.128. show/badnode (1)
3807 show/badnode Show all the bad nodes in the system
3809 Display all the bad node callsigns in the system, see SET/BADNODEfor
3812 11.129. show/badspotter (1)
3814 show/badspotter Show all the bad spotters in the system
3816 Display all the bad spotter's callsigns in the system, see
3817 SET/BADSPOTTERfor more information.
3820 11.130. show/badword (1)
3822 show/badword Show all the bad words in the system
3824 Display all the bad words in the system, see SET/BADWORDfor more
3827 11.131. show/configuration [<node>] (0)
3829 show/configuration [<node>] Show all the nodes and users visible
3831 This command allows you to see all the users that can be seenand the
3832 nodes to which they are connected.This command is normally abbreviated
3833 to: sh/cNormally, the list returned will be just for the nodes from
3834 your country (because the list otherwise will be very long).
3841 will produce a complete list of all nodes. BE WARNED: the list that is
3842 returned can be VERY longIt is possible to supply a node or part of a
3843 prefix and you will get a list of the users for that node or list of
3844 nodes starting withthat prefix.
3855 11.132. show/configuration/node (0)
3857 show/configuration/node Show all the nodes connected locally
3859 Show all the nodes connected to this node.
3861 11.133. show/connect (1)
3863 show/connect Show all the active connections
3865 This command shows information on all the active connections known
3866 tothe node. This command gives slightly more information than WHO.
3868 11.134. show/date [<prefix>|<callsign>] (0)
3870 show/date [<prefix>|<callsign>] Show the local time
3872 This is very nearly the same as SHOW/TIME, the only difference the
3873 formatof the date string if no arguments are given.If no prefixes or
3874 callsigns are given then this command returns the localtime and UTC as
3875 the computer has it right now. If you give some prefixesthen it will
3876 show UTC and UTC + the local offset (not including DST) atthe prefixes
3877 or callsigns that you specify.
3879 11.135. show/db0sdx <callsign> (0)
3881 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
3883 This command queries the DB0SDX QSL server on the internetand returns
3884 any information available for that callsign. This serviceis provided
3885 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
3890 show/dx Interrogate the spot database
3892 If you just type SHOW/DX you will get the last so many spots(sysop
3893 configurable, but usually 10).In addition you can add any number of
3894 these commands in very nearlyany order to the basic SHOW/DX command,
3898 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>
3902 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
3906 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
3910 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
3914 info <text> - any spots containing <text> in the info or remarks
3918 by <call> - any spots spotted by <call> (spotter <call> is the same).
3922 qsl - this automatically looks for any qsl info on the call held in the spot database.
3926 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.
3930 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
3933 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
3937 You can also use this with the 'by' keyword so eg by W dxcc
3945 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
3949 11.137. show/dxcc <prefix> (0)
3951 show/dxcc <prefix> Interrogate the spot database by country
3953 This command takes the <prefix> (which can be a full or partial
3954 callsign if desired), looks up which internal country number it isand
3955 then displays all the spots as per SH/DX for that country.This is now
3956 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
3960 SH/DXCC G SH/DXCC W on 20m iota
3964 This can be done with the SHOW/DX command like this:-
3967 SH/DX dxcc g SH/DX dxcc w on 20m iota
3971 11.138. show/dxstats [days] [date] (0)
3973 show/dxstats [days] [date] Show the DX Statistics
3975 Show the total DX spots for the last <days> no of days (default is
3976 31), starting from a <date> (default: today).
3978 11.139. show/files [<filearea> [<string>]] (0)
3980 show/files [<filearea> [<string>]] List the contents of a filearea
3982 SHOW/FILES on its own will show you a list of the various
3983 fileareasavailable on the system. To see the contents of a particular
3991 where <filearea> is the name of the filearea you want to see the con-
3992 tents of.You can also use shell globbing characters like '*' and '?'
3993 in astring to see a selection of files in a filearea eg:-
3996 SH/FILES bulletins arld*
4000 See also TYPE - to see the contents of a file.
4002 11.140. show/filter (0)
4004 show/filter Show the contents of all the filters you have set
4006 Show the contents of all the filters that are set. This command
4007 displaysall the filters set - for all the various categories.
4009 11.141. show/hfstats [days] [date] (0)
4011 show/hfstats [days] [date] Show the HF DX Statistics
4013 Show the HF DX spots breakdown by band for the last <days> no of days
4014 (default is 31), starting from a <date> (default: today).
4016 11.142. show/hftable [days] [date] [prefix ...] (0)
4018 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4020 Show the HF DX Spotter table for the list of prefixes for the last
4021 <days> no of days (default is 31), starting from a <date> (default:
4022 today).If there are no prefixes then it will show the table for your
4023 country.Remember that some countries have more than one "DXCC country"
4024 in them(eg G :-), to show them (assuming you are not in G already
4025 which isspecially treated in the code) you must list all the relevant
4029 sh/hftable g gm gd gi gj gw gu
4033 Note that the prefixes are converted into country codes so you don't
4034 haveto list all possible prefixes for each country.If you want more or
4035 less days than the default simply include thenumber you require:-
4042 If you want to start at a different day, simply add the date in some
4046 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4050 This will show the stats for your DXCC for that CQWW contest weekend.
4051 You can specify either prefixes or full callsigns (so you can see how
4052 youdid against all your mates). You can also say 'all' which will then
4053 printthe worldwide statistics.
4061 11.143. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4063 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4066 This command shows the hop counts set up for a node. You can
4067 specifywhich category you want to see. If you leave the category out
4068 then all the categories will be listed.
4070 11.144. show/isolate (1)
4072 show/isolate Show list of ISOLATED nodes
4075 11.145. show/log [<callsign>] (8)
4077 show/log [<callsign>] Show excerpts from the system log
4079 This command outputs a short section of the system log. On its ownit
4080 will output a general logfile. With the optional callsign it willshow
4081 output from the log associated with that callsign.
4083 11.146. show/moon [ndays] [<prefix>|<callsign>] (0)
4085 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4087 Show the Moon rise and set times for a (list of) prefixes or
4088 callsigns, together with the azimuth and elevation of the sun
4089 currently at thoselocations.If you don't specify any prefixes or
4090 callsigns, it will show the times foryour QTH (assuming you have set
4091 it with either SET/LOCATION or SET/QRA),together with the current
4092 azimuth and elevation.In addition, it will show the illuminated
4093 fraction of the moons disk.If all else fails it will show the Moonrise
4094 and set times for the nodethat you are connected to. For example:-
4097 SH/MOON SH/MOON G1TLH W5UN
4101 You can also use this command to see into the past or the future, soif
4102 you want to see yesterday's times then do:-
4109 or in three days time:-
4116 Upto 366 days can be checked both in the past and in the future.Please
4117 note that the rise and set times are given as the UT times of rise and
4118 set on the requested UT day.
4122 11.147. show/muf <prefix> [<hours>][long] (0)
4124 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4127 This command allow you to estimate the likelihood of you contactinga
4128 station with the prefix you have specified. The output assumes a
4129 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4130 0.15muV/10dB SINAD)The result predicts the most likely operating
4131 frequencies and signallevels for high frequency (shortwave) radio
4132 propagation paths onspecified days of the year and hours of the day.
4133 It is most useful forpaths between 250 km and 6000 km, but can be used
4134 with reduced accuracyfor paths shorter or longer than this.The command
4135 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4136 predict the MUF given the predicted flux, day of the year,hour of the
4137 day and geographic coordinates of the transmitter andreceiver. This
4138 routine is reasonably accurate for the purposes here,with a claimed
4139 RMS error of 3.8 MHz, but much smaller and less complexthan the
4140 programs used by major shortwave broadcasting organizations,such as
4141 the Voice of America.The command will display some header information
4142 detailing itsassumptions, together with the locations, latitude and
4143 longitudes andbearings. It will then show UTC (UT), local time at the
4144 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4145 the path(Zen) and the likely signal strengths. Then for each frequency
4146 for whichthe system thinks there is a likelihood of a circuit it
4147 prints a value.The value is currently a likely S meter reading based
4148 on the conventional6dB / S point scale. If the value has a '+'
4149 appended it means that it is1/2 an S point stronger. If the value is
4150 preceeded by an 'm' it means thatthere is likely to be much fading and
4151 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4152 will show the next two hours worth of data. Youcan specify anything up
4153 to 24 hours worth of data by appending the no ofhours required after
4154 the prefix. For example:-
4164 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
4168 indicating that you will have weak, fading circuits on top band and
4169 80m but usable signals on 40m (about S3).inputing:-
4176 will get you the above display, but with the next 24 hours worth
4180 SH/MUF W L 24 SH/MUF W 24 Long
4184 Gives you an estimate of the long path propagation characterics.
4185 Itshould be noted that the figures will probably not be very useful,
4186 norterrible accurate, but it is included for completeness.
4188 11.148. show/newconfiguration [<node>] (0)
4190 show/newconfiguration [<node>] Show all the nodes and users visible
4192 This command allows you to see all the users that can be seenand the
4193 nodes to which they are connected. This command produces essentially
4194 the same information as SHOW/CONFIGURATION except that it shows all
4195 the duplication ofany routes that might be present It also uses a
4196 different formatwhich may not take up quite as much space if you don't
4197 have anyloops.BE WARNED: the list that is returned can be VERY long
4199 11.149. show/newconfiguration/node (0)
4201 show/newconfiguration/node Show all the nodes connected locally
4203 Show all the nodes connected to this node in the new format.
4205 11.150. show/node [<callsign> ...] (1)
4207 show/node [<callsign> ...] Show the type and version number of nodes
4209 Show the type and version (if connected) of the nodes specified on
4210 thecommand line. If no callsigns are specified then a sorted list of
4211 allthe non-user callsigns known to the system will be displayed.
4213 11.151. show/prefix <callsign> (0)
4215 show/prefix <callsign> Interrogate the prefix database
4217 This command takes the <callsign> (which can be a full or partial
4218 callsign or a prefix), looks up which internal country number it is
4219 and then displays all the relevant prefixes for that countrytogether
4220 with the internal country no, the CQ and ITU regions. See also
4223 11.152. show/program (5)
4225 show/program Show the locations of all the included program modules
4227 Show the name and location where every program module was load from.
4228 Thisis useful for checking where you think you have loaded a .pm file
4231 11.153. show/qra <lat> <long> (0)
4233 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4235 This is a multipurpose command that allows you either to calculate
4236 thedistance and bearing between two locators or (if only one locator
4237 isgiven on the command line) the distance and beraing from your
4238 stationto the locator. For example:-
4241 SH/QRA IO92QL SH/QRA JN06 IN73
4245 The first example will show the distance and bearing to the locator
4246 fromyourself, the second example will calculate the distance and bear-
4247 ing fromthe first locator to the second. You can use 4 or 6 character
4248 locators.It is also possible to convert a latitude and longitude to a
4249 locator by using this command with a latitude and longitude as an
4250 argument, forexample:-
4254 SH/QRA 52 41 N 0 58 E
4258 11.154. show/qra <locator> [<locator>] (0)
4260 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4263 11.155. show/qrz <callsign> (0)
4265 show/qrz <callsign> Show any callbook details on a callsign
4267 This command queries the QRZ callbook server on the internetand
4268 returns any information available for that callsign. This serviceis
4269 provided for users of this software by http://www.qrz.com See also
4270 SHOW/WM7D for an alternative.
4272 11.156. show/route <callsign> ... (0)
4274 show/route <callsign> ... Show the route to the callsign
4276 This command allows you to see to which node the callsigns specified
4277 areconnected. It is a sort of inverse sh/config.
4284 11.157. show/satellite <name> [<hours> <interval>] (0)
4286 show/satellite <name> [<hours> <interval>] Show tracking data
4288 Show the tracking data from your location to the satellite of your
4289 choicefrom now on for the next few hours.If you use this command
4290 without a satellite name it will display a listof all the satellites
4291 known currently to the system. If you give a name then you can obtain
4292 tracking data of all the passesthat start and finish 5 degrees below
4293 the horizon. As default it willgive information for the next three
4294 hours for every five minute period.You can alter the number of hours
4295 and the step size, within certain limits. Each pass in a period is
4296 separated with a row of '-----' charactersSo for example:-
4299 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4303 11.158. show/station all [<regex>] (6)
4305 show/station all [<regex>] Show list of users in the system
4308 11.159. show/station [<callsign> ..] (0)
4310 show/station [<callsign> ..] Show information about a callsign
4312 Show the information known about a callsign and whether (and
4313 where)that callsign is connected to the cluster.
4321 If no callsign is given then show the information for yourself.
4323 11.160. show/sun [ndays] [<prefix>|<callsign>] (0)
4325 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
4327 Show the sun rise and set times for a (list of) prefixes or callsigns,
4328 together with the azimuth and elevation of the sun currently at
4329 thoselocations.If you don't specify any prefixes or callsigns, it will
4330 show the times foryour QTH (assuming you have set it with either
4331 SET/LOCATION or SET/QRA),together with the current azimuth and
4332 elevation.If all else fails it will show the sunrise and set times for
4333 the nodethat you are connected to. For example:-
4336 SH/SUN SH/SUN G1TLH K9CW ZS
4340 You can also use this command to see into the past or the future, soif
4341 you want to see yesterday's times then do:-
4348 or in three days time:-
4355 Upto 366 days can be checked both in the past and in the future.Please
4356 note that the rise and set times are given as the UT times of rise and
4357 set on the requested UT day.
4359 11.161. show/time [<prefix>|<callsign>] (0)
4361 show/time [<prefix>|<callsign>] Show the local time
4363 If no prefixes or callsigns are given then this command returns the
4364 localtime and UTC as the computer has it right now. If you give some
4365 prefixesthen it will show UTC and UTC + the local offset (not
4366 including DST) atthe prefixes or callsigns that you specify.
4368 11.162. show/usdb [call ..] (0)
4370 show/usdb [call ..] Show information held on the FCC Call database
4372 Show the City and State of a Callsign held on the FCC database ifhis
4373 is being run on this system, eg:-
4380 11.163. show/vhfstats [days] [date] (0)
4382 show/vhfstats [days] [date] Show the VHF DX Statistics
4384 Show the VHF DX spots breakdown by band for the last <days> no of days
4385 (default is 31), starting from a date (default: today).
4387 11.164. show/vhftable [days] [date] [prefix ...] (0)
4389 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
4391 Show the VHF DX Spotter table for the list of prefixes for the last
4392 <days> no of days (default is 31), starting from a date (default:
4393 today).If there are no prefixes then it will show the table for your
4394 country.Remember that some countries have more than one "DXCC country"
4395 in them(eg G :-), to show them (assuming you are not in G already
4396 which isspecially treated in the code) you must list all the relevant
4400 sh/vhftable g gm gd gi gj gw gu
4404 Note that the prefixes are converted into country codes so you don't
4405 haveto list all possible prefixes for each country.If you want more or
4406 less days than the default simply include thenumber you require:-
4413 If you want to start at a different day, simply add the date in some
4417 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
4421 This will show the stats for your DXCC for that CQWW contest weekend.
4422 You can specify either prefixes or full callsigns (so you can see how
4423 youdid against all your mates). You can also say 'all' which will then
4424 printthe worldwide statistics.
4431 11.165. show/wcy (0)
4433 show/wcy Show last 10 WCY broadcasts
4436 11.166. show/wcy <n> (0)
4438 show/wcy <n> Show last <n> WCY broadcasts
4440 Display the most recent WCY information that has been received by the
4445 11.167. show/wm7d <callsign> (0)
4447 show/wm7d <callsign> Show callbook details on a US callsigns
4449 This command queries the WM7D callbook server on the internetand
4450 returns any information available for that US callsign. This serviceis
4451 provided for users of this software by http://www.wm7d.net.See also
4454 11.168. show/wwv (0)
4456 show/wwv Show last 10 WWV broadcasts
4459 11.169. show/wwv <n> (0)
4461 show/wwv <n> Show last <n> WWV broadcasts
4463 Display the most recent WWV information that has been received by the
4466 11.170. shutdown (5)
4468 shutdown Shutdown the cluster
4470 Shutdown the cluster and disconnect all the users
4472 11.171. stat/channel [<callsign>] (5)
4474 stat/channel [<callsign>] Show the status of a channel on the cluster
4476 Show the internal status of the channel object either for the channel
4477 that you are on or else for the callsign that you asked for.Only the
4478 fields that are defined (in perl term) will be displayed.
4480 11.172. stat/db <dbname> (5)
4482 stat/db <dbname> Show the status of a database
4484 Show the internal status of a database descriptor.Depending on your
4485 privilege level you will see more or less information. This command is
4486 unlikely to be of much use to anyone other than a sysop.
4488 11.173. stat/msg (1)
4490 stat/msg Show the status of the message system
4493 11.174. stat/msg <msgno> (1)
4495 stat/msg <msgno> Show the status of a message
4497 This command shows the internal status of a message and includes
4498 informationsuch as to whom it has been forwarded, its size, origin etc
4499 etc.If no message number is given then the status of the message
4500 system is displayed.
4502 11.175. stat/route_node <callsign> (5)
4504 stat/route_node <callsign> Show the data in a Route::Node object
4507 11.176. stat/route_node all (5)
4509 stat/route_node all Show list of all Route::Node objects
4511 11.177. stat/route_user <callsign> (5)
4513 stat/route_user <callsign> Show the data in a Route::User object
4516 11.178. stat/route_user all (5)
4518 stat/route_user all Show list of all Route::User objects
4521 11.179. stat/user [<callsign>] (5)
4523 stat/user [<callsign>] Show the full status of a user
4525 Shows the full contents of a user record including all the secret
4526 flagsand stuff.Only the fields that are defined (in perl term) will be
4531 sysop Regain your privileges if you login remotely
4533 The system automatically reduces your privilege level to that of
4534 anormal user if you login in remotely. This command allows you
4535 toregain your normal privilege level. It uses the normal system:
4536 fivenumbers are returned that are indexes into the character array
4537 that isyour assigned password (see SET/PASSWORD). The indexes start
4538 fromzero.You are expected to return a string which contains the
4539 charactersrequired in the correct order. You may intersperse those
4540 characterswith others to obscure your reply for any watchers. For
4541 example (andthese values are for explanation :-):
4544 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
4551 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
4555 They will all match. If there is no password you will still be
4556 offerednumbers but nothing will happen when you input a string. Any
4557 match iscase sensitive.
4559 11.181. talk <call> > <node> [<text>] (0)
4561 talk <call> > <node> [<text>] Send a text message to another station
4564 Send a short message to any other station that is visible on the
4565 clustersystem. You can send it to anyone you can see with a
4566 SHOW/CONFIGURATION command, they don't have to be connected
4567 locally.The second form of TALK is used when other cluster nodes are
4568 connectedwith restricted information. This usually means that they
4569 don't send the user information usually associated with logging on and
4570 off the cluster.If you know that G3JNB is likely to be present on
4571 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
4572 then you would use thesecond form of the talk message.If you want to
4573 have a ragchew with someone you can leave the text messageout and the
4574 system will go into 'Talk' mode. What this means is that ashort
4575 message is sent to the recipient telling them that you are in
4576 a'Talking' frame of mind and then you just type - everything you send
4577 willgo to the station that you asked for. All the usual announcements,
4578 spots and so on will still come out on yourterminal.If you want to do
4579 something (such as send a spot) you preceed the normal command with a
4583 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
4587 To leave talk mode type:
4594 If you are in 'Talk' mode, there is an extention to the '/' command
4595 whichallows you to send the output to all the people you are talking
4596 to. You do with the '//' command. For example:-
4603 will send the hftable as you have it to all the people you are cur-
4606 11.182. talk <call> [<text>] (0)
4608 talk <call> [<text>] Send a text message to another station
4611 11.183. type <filearea>/<name> (0)
4613 type <filearea>/<name> Look at the contents of a file in one of the
4616 Type out the contents of a file in a filearea. So, for example, in
4617 filearea 'bulletins' you want to look at file 'arld051' you would
4621 TYPE bulletins/arld051
4625 See also SHOW/FILES to see what fileareas are available and a list of
4628 11.184. uncatchup <node call> all|[msgno> ...] (5)
4630 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
4632 When you send messages the fact that you have forwarded it to another
4633 node is remembered so that it isn't sent again. When you have a new
4634 partnernode and you add their callsign to your /spider/msg/forward.pl
4635 file, alloutstanding non-private messages will be forwarded to them.
4636 This may wellbe ALL the non-private messages. You can prevent this by
4637 using these commmands:-
4640 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
4643 and to undo what you have just done:-
4646 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
4650 which will arrange for them to be forward candidates again.Order is
4653 11.185. unset/announce (0)
4655 unset/announce Stop announce messages coming out on your terminal
4658 11.186. unset/anntalk (0)
4660 unset/anntalk Stop talk like announce messages on your terminal
4662 The announce system on legacy cluster nodes is used as a talk
4663 substitute because the network is so poorly connected. If you:
4670 you will suppress several of these announces, you may miss the odd
4671 useful one as well, but you would probably miss them anyway in thewel-
4672 ter of useless ones.
4679 allows you to see them again. This is the default.
4681 11.187. unset/baddx <call>.. (8)
4683 unset/baddx <call>.. Propagate a dx spot with this callsign again
4685 Setting a word as 'baddx' will prevent spots with that word in
4686 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
4687 anyfurther. They will not be displayed and they will not be sent
4688 ontoother nodes.The word must be written in full, no wild cards are
4692 set/baddx FORSALE VIDEO FR0G
4696 To allow a word again, use the following command ...
4703 11.188. unset/badnode <call>.. (8)
4705 unset/badnode <call>.. Allow spots from this node again
4708 Setting a callsign as a 'badnode' will prevent spots from that node
4709 going any further. They will not be displayed and they will not be
4710 sent onto other nodes.The call must be a full eg:-
4717 will stop anything from K1TTT. If you want SSIDs as well then you mus-
4718 tenter them specifically.
4725 will allow spots from him again.Use with extreme care. This command
4726 may well be superceeded by FILTERing.
4728 11.189. unset/badspotter <call>.. (8)
4730 unset/badspotter <call>.. Allow spots from this callsign again
4732 Setting a callsign as a 'badspotter' will prevent spots from this
4733 callsign going any further. They will not be displayed and they will
4734 not be sent onto other nodes.The call must be written in full, no wild
4735 cards are allowed eg:-
4738 set/badspotter VE2STN
4742 will stop anything from VE2STN. This command will automaticallystop
4743 spots from this user, regardless of whether or which SSID he uses. DO
4744 NOT USE SSIDs in the callsign, just use the callsignas above or below.
4747 unset/badspotter VE2STN
4751 will allow spots from him again.Use with extreme care. This command
4752 may well be superceded by FILTERing.
4754 11.190. unset/badword <word>.. (8)
4756 unset/badword <word>.. Propagate things with this word again
4758 Setting a word as a 'badword' will prevent things like spots,announces
4759 or talks with this word in the the text part from going anyfurther.
4760 They will not be displayed and they will not be sent ontoother
4761 nodes.The word must be written in full, no wild cards are allowed eg:-
4764 set/badword annihilate annihilated annihilation
4768 will stop anything with these words in the text.
4771 unset/badword annihilated
4774 will allow text with this word again.
4776 11.191. unset/beep (0)
4778 unset/beep Stop beeps for DX and other messages on your terminal
4781 11.192. unset/dx (0)
4783 unset/dx Stop DX messages coming out on your terminal
4786 11.193. unset/dxgrid (0)
4788 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
4790 A standard feature which is enabled in version 1.43 and above is that
4791 if the spotter's grid square is known it is output on the endof a DX
4792 announcement (there is just enough room). Some user programscannot
4793 cope with this. You can use this command to reset (or set)this
4796 11.194. unset/dxstate (0)
4798 unset/dxstate Stop US State info on the end of DX announcements
4800 If the spotter's or spotted's US State is known it is output on the
4801 end of a DX announcement (there is just enough room). A spotter's
4802 state will appear on the RHS of the time (like SET/DXGRID) and the
4803 spotted's State will appear on the LHS of thetime field. Any
4804 information found will override any locator information from
4805 SET/DXGRID.Some user programs cannot cope with this. You can use this
4806 command to reset (or set) this feature.
4808 11.195. unset/echo (0)
4810 unset/echo Stop the cluster echoing your input
4812 If you are connected via a telnet session, different implimentationsof
4813 telnet handle echo differently depending on whether you are connected
4814 via port 23 or some other port. You can use this commandto change the
4815 setting appropriately. The setting is stored in your user profile.YOU
4816 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
4818 11.196. unset/email (0)
4820 unset/email Stop personal msgs being forwarded by email
4822 If any personal messages come in for your callsign then you can
4823 usethese commands to control whether they are forwarded onto your
4824 emailaddress. To enable the forwarding do something like:-
4827 SET/EMAIL mike.tubby@somewhere.com
4831 You can have more than one email address (each one separated by a
4832 space).Emails are forwarded to all the email addresses you specify.You
4833 can disable forwarding by:-
4840 11.197. unset/here (0)
4842 unset/here Tell the system you are absent from your terminal
4845 11.198. unset/hops <call> ann|spots|route|wwv|wcy (8)
4847 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
4849 Set the hop count for a particular type of broadcast for a node.This
4850 command allows you to set up special hop counts for a node for
4851 currently: announce, spots, wwv and wcy broadcasts.eg:
4854 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
4858 Set SHOW/HOPS for information on what is already set. This commandcre-
4859 ates a filter and works in conjunction with the filter system. You can
4860 unset the hops with command UNSET/HOPS. For example:-
4863 unset/hops gb7djk ann unset/hops gb7mbc spots
4867 11.199. unset/logininfo (0)
4869 unset/logininfo Inform when a station logs out locally
4872 11.200. unset/privilege (0)
4874 unset/privilege Remove any privilege for this session
4876 You can use this command to 'protect' this session from
4877 unauthoriseduse. If you want to get your normal privilege back you
4878 will need toeither logout and login again (if you are on a console) or
4879 use theSYSOP command.
4881 11.201. unset/prompt (0)
4883 unset/prompt Set your prompt back to default
4885 This command will set your user prompt to exactly the string that you
4886 say. The point of this command to enable a user to interface to
4887 programsthat are looking for a specific prompt (or else you just want
4888 a differentfixed prompt).
4895 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
4898 11.202. unset/talk (0)
4900 unset/talk Stop TALK messages coming out on your terminal
4904 11.203. unset/wcy (0)
4906 unset/wcy Stop WCY messages coming out on your terminal
4909 11.204. unset/wwv (0)
4911 unset/wwv Stop WWV messages coming out on your terminal
4914 11.205. unset/wx (0)
4916 unset/wx Stop WX messages coming out on your terminal
4921 who Show who is physically connected
4923 This is a quick listing that shows which callsigns are connected
4924 andwhat sort of connection they have
4926 11.207. wx <text> (0)
4928 wx <text> Send a weather message to local users
4931 11.208. wx full <text> (0)
4933 wx full <text> Send a weather message to all cluster users
4936 11.209. wx sysop <text> (5)
4938 wx sysop <text> Send a weather message to other clusters only
4940 Weather messages can sometimes be useful if you are experiencing an
4941 extremethat may indicate enhanced conditions