1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 March 2003 revision 0.5
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 10.4 accept/announce <call> [input] [0-9] <pattern> (8)
72 10.5 accept/announce [0-9] <pattern> (0)
73 10.6 accept/route <call> [0-9] <pattern> (8)
74 10.7 accept/spots <call> [input] [0-9] <pattern> (8)
75 10.8 accept/spots [0-9] <pattern> (0)
76 10.9 accept/wcy <call> [input] [0-9] <pattern> (8)
77 10.10 accept/wcy [0-9] <pattern> (0)
78 10.11 accept/wwv <call> [input] [0-9] <pattern> (8)
79 10.12 accept/wwv [0-9] <pattern> (0)
80 10.13 announce <text> (0)
81 10.14 announce full <text> (0)
82 10.15 announce sysop <text> (5)
83 10.16 apropos <string> (0)
84 10.17 blank [<string>] [<nn>] (0)
86 10.19 catchup <node call> all|[<msgno> ...] (5)
87 10.20 chat <group> <text> (0)
88 10.21 clear/announce <callsign> [input] [0-9|all] (8)
89 10.22 clear/announce [1|all] (0)
90 10.23 clear/route <callsign> [input] [0-9|all] (8)
91 10.24 clear/route [1|all] (0)
92 10.25 clear/spots <callsign> [input] [0-9|all] (8)
93 10.26 clear/spots [0-9|all] (0)
94 10.27 clear/wcy <callsign> [input] [0-9|all] (8)
95 10.28 clear/wcy [1|all] (0)
96 10.29 clear/wwv <callsign> [input] [0-9|all] (8)
97 10.30 clear/wwv [1|all] (0)
98 10.31 connect <callsign> (5)
100 10.33 dbcreate <name> (9)
101 10.34 dbcreate <name> chain <name> [<name>..] (9)
102 10.35 dbcreate <name> cmd <dxspider command> (9)
103 10.36 dbcreate <name> remote <node> (9)
104 10.37 dbimport <dbname> <filename> (9)
105 10.38 dbremove <dbname> (9)
106 10.39 dbshow <dbname> <key> (0)
108 10.41 delete/usdb <callsign> ... (9)
109 10.42 delete/user <callsign> ... (9)
110 10.43 demonstrate <call> <command> (9)
112 10.45 directory <from>-<to> (0)
113 10.46 directory <nn> (0)
114 10.47 directory all (0)
115 10.48 directory from <call> (0)
116 10.49 directory new (0)
117 10.50 directory own (0)
118 10.51 directory subject <string> (0)
119 10.52 directory to <call> (0)
121 10.54 disconnect <call> [<call> ...] (8)
122 10.55 dx [by <call>] <freq> <call> <remarks> (0)
123 10.56 echo <line> (0)
124 10.57 export <msgno> <filename> (9)
125 10.58 export_users [<filename>] (9)
126 10.59 filtering... (0)
127 10.60 forward/latlong <node_call> (8)
128 10.61 forward/opernam <call> (1)
130 10.63 init <node> (5)
131 10.64 join <group> (0)
133 10.66 kill <from msgno>-<to msgno> (0)
134 10.67 kill <from>-<to> (5)
135 10.68 kill <msgno> [<msgno..] (0)
136 10.69 kill <msgno> [<msgno> ...] (0)
137 10.70 kill expunge <msgno> [<msgno..] (6)
138 10.71 kill from <call> (5)
139 10.72 kill full <msgno> [<msgno..] (5)
140 10.73 kill full <msgno> [<msgno] (5)
141 10.74 kill to <call> (5)
142 10.75 kill from <regex> (0)
143 10.76 kill to <regex> (0)
144 10.77 leave <group> (0)
146 10.79 load/aliases (9)
147 10.80 load/badmsg (9)
148 10.81 load/badwords (9)
150 10.83 load/cmd_cache (9)
151 10.84 load/forward (9)
153 10.86 load/keps [nn] (5)
154 10.87 load/messages (9)
155 10.88 load/prefixes (9)
156 10.89 merge <node> [<no spots>/<no wwv>] (5)
157 10.90 msg <cmd> <msgno> [data ... ] (9)
158 10.91 pc <call> <text> (8)
159 10.92 ping <node call> (1)
160 10.93 rcmd <node call> <cmd> (1)
162 10.95 read <msgno> (0)
165 10.98 reject/announce <call> [input] [0-9] <pattern> (8)
166 10.99 reject/announce [0-9] <pattern> (0)
167 10.100 reject/route <call> [0-9] <pattern> (8)
168 10.101 reject/spots <call> [input] [0-9] <pattern> (8)
169 10.102 reject/spots [0-9] <pattern> (0)
170 10.103 reject/wcy <call> [input] [0-9] <pattern> (8)
171 10.104 reject/wcy [0-9] <pattern> (0)
172 10.105 reject/wwv <call> [input] [0-9] <pattern> (8)
173 10.106 reject/wwv [0-9] <pattern> (0)
175 10.108 reply <msgno> (0)
176 10.109 reply b <msgno> (0)
177 10.110 reply noprivate <msgno> (0)
178 10.111 reply rr <msgno> (0)
179 10.112 save [-d -t -a] <filename> "<cmd>" [...] (9)
180 10.113 send <call> [<call> ...] (0)
181 10.114 send copy <msgno> <call> (0)
182 10.115 send noprivate <call> (0)
183 10.116 send private <call> (0)
184 10.117 send rr <call> (0)
185 10.118 set/address <your address> (0)
186 10.119 set/announce (0)
187 10.120 set/anntalk (0)
188 10.121 set/arcluster <call> [<call>..] (5)
189 10.122 set/baddx <call>.. (8)
190 10.123 set/badnode <call>.. (8)
191 10.124 set/badspotter <call>.. (8)
192 10.125 set/badword <word>.. (8)
193 10.126 set/bbs <call> [<call>..] (5)
195 10.128 set/clx <call> [<call>..] (5)
196 10.129 set/debug <name> (9)
199 10.132 set/dxgrid (0)
201 10.134 set/dxnet <call> [<call>..] (5)
203 10.136 set/email <email> ... (0)
205 10.138 set/homenode <node> (0)
206 10.139 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
207 10.140 set/isolate (9)
208 10.141 set/language <lang> (0)
209 10.142 set/location <lat & long> (0)
210 10.143 set/lockout <call> (9)
211 10.144 set/logininfo (0)
212 10.145 set/name <your name> (0)
213 10.146 set/node <call> [<call>..] (5)
214 10.147 set/obscount <count> <call> (8)
215 10.148 set/page <lines per page> (0)
216 10.149 set/password (0)
217 10.150 set/password <callsign> <string> (9)
218 10.151 set/pinginterval <time> <nodecall> (9)
219 10.152 set/privilege <n> <call> [<call..] (9)
220 10.153 set/prompt <string> (0)
221 10.154 set/qra <locator> (0)
222 10.155 set/qth <your qth> (0)
223 10.156 set/register <call> ... (9)
224 10.157 set/spider <call> [<call>..] (5)
225 10.158 set/sys_location <lat & long> (9)
226 10.159 set/sys_qra <locator> (9)
228 10.161 set/usdb <call> <state> <city> (9)
229 10.162 set/usstate (0)
233 10.166 show/baddx (1)
234 10.167 show/badnode (1)
235 10.168 show/badspotter (1)
236 10.169 show/badword (1)
237 10.170 show/chat [<group>] [<lines>] (0)
238 10.171 show/configuration [<node>] (0)
239 10.172 show/configuration/node (0)
240 10.173 show/connect (1)
241 10.174 show/contest <year and month> (0)
242 10.175 show/date [<prefix>|<callsign>] (0)
243 10.176 show/db0sdx <callsign> (0)
244 10.177 show/debug (9)
246 10.179 show/dxcc <prefix> (0)
247 10.180 show/dxqsl <callsign> (0)
248 10.181 show/dxstats [days] [date] (0)
249 10.182 show/files [<filearea> [<string>]] (0)
250 10.183 show/filter (0)
251 10.184 show/hfstats [days] [date] (0)
252 10.185 show/hftable [days] [date] [prefix ...] (0)
253 10.186 show/hops <call> [ann|spots|route|wcy|wwv] (8)
254 10.187 show/isolate (1)
255 10.188 show/lockout <prefix>|all (9)
256 10.189 show/log [<callsign>] (8)
257 10.190 show/moon [ndays] [<prefix>|<callsign>] (0)
258 10.191 show/muf <prefix> [<hours>][long] (0)
259 10.192 show/newconfiguration [<node>] (0)
260 10.193 show/newconfiguration/node (0)
261 10.194 show/node [<callsign> ...] (1)
262 10.195 show/prefix <callsign> (0)
263 10.196 show/program (5)
264 10.197 show/qra <lat> <long> (0)
265 10.198 show/qra <locator> [<locator>] (0)
266 10.199 show/qrz <callsign> (0)
267 10.200 show/registered [<prefix>] (9)
268 10.201 show/route <callsign> ... (0)
269 10.202 show/satellite <name> [<hours> <interval>] (0)
270 10.203 show/station all [<regex>] (6)
271 10.204 show/station [<callsign> ..] (0)
272 10.205 show/sun [ndays] [<prefix>|<callsign>] (0)
273 10.206 show/time [<prefix>|<callsign>] (0)
274 10.207 show/usdb [call ..] (0)
275 10.208 show/vhfstats [days] [date] (0)
276 10.209 show/vhftable [days] [date] [prefix ...] (0)
278 10.211 show/wcy <n> (0)
279 10.212 show/wm7d <callsign> (0)
281 10.214 show/wwv <n> (0)
283 10.216 spoof <call> <command> (9)
284 10.217 stat/channel [<callsign>] (5)
285 10.218 stat/db <dbname> (5)
287 10.220 stat/msg <msgno> (1)
288 10.221 stat/route_node <callsign> (5)
289 10.222 stat/route_node all (5)
290 10.223 stat/route_user <callsign> (5)
291 10.224 stat/route_user all (5)
292 10.225 stat/user [<callsign>] (5)
294 10.227 talk <call> > <node> [<text>] (0)
295 10.228 talk <call> [<text>] (0)
296 10.229 type <filearea>/<name> (0)
297 10.230 uncatchup <node call> all|[msgno> ...] (5)
298 10.231 unset/announce (0)
299 10.232 unset/anntalk (0)
300 10.233 unset/baddx <call>.. (8)
301 10.234 unset/badnode <call>.. (8)
302 10.235 unset/badspotter <call>.. (8)
303 10.236 unset/badword <word>.. (8)
304 10.237 unset/beep (0)
305 10.238 unset/debug <name> (9)
307 10.240 unset/dxcq (0)
308 10.241 unset/dxgrid (0)
309 10.242 unset/dxitu (0)
310 10.243 unset/echo (0)
311 10.244 unset/email (0)
312 10.245 unset/here (0)
313 10.246 unset/hops <call> ann|spots|route|wwv|wcy (8)
314 10.247 unset/isolate (9)
315 10.248 unset/lockout <call> (9)
316 10.249 unset/logininfo (0)
317 10.250 unset/password <call> ... (9)
318 10.251 unset/privilege (0)
319 10.252 unset/prompt (0)
320 10.253 unset/register <call> ... (9)
321 10.254 unset/talk (0)
322 10.255 unset/usstate (0)
328 10.261 wx full <text> (0)
329 10.262 wx sysop <text> (5)
332 ______________________________________________________________________
334 1. Routing and Filtering
338 From DXSpider version 1.48, major changes were introduced to the way
339 node connections are treated. This is part of an ongoing process to
340 remove problems with loops and to enable talk and other functions to
341 propagate across the whole of the worldwide cluster network. In fact,
342 in a Spider network, it would be useful, perhaps even necessary to
343 have loops. This would give real resilience to the network, meaning
344 that if a link dropped, the information flow would simply come in and
345 go out via a different route. Of course, we do not have a complete
346 network of Spider nodes, there are other programs out there. Some of
347 these do not have any protection from loops. Certainly AK1A does not
348 handle loops well at all. It is therefore necessary to have some form
349 of protection for these nodes.
352 In fact DXSpider has had a simple system for some time which is called
353 isolation. This is similar to what in other systems such as clx, is
354 called passive mode. A more detailed explanation of isolation is given
355 further below. This system is still available and, for simple
356 networks, is probably all that you need.
359 The new functionality introduced in version 1.48 allows filtering the
360 node and user protocol frames on a "per interface" basis. We call this
361 route filtering. This is used instead of isolation.
364 What this really means is that you can control more or less completely
365 which user and node management PC protocol frames pass to each of your
366 partner nodes. You can also limit what comes into your node from your
367 partners. It is even possible to control the settings that your
368 partner node has for the routing information that it sends to you
369 (using the rcmd command).
374 Initially when route filters were being tested we generated a
375 "default" filter. Unfortunately it quickly became apparent that this
376 might suit the UK cluster network but didn't really fit anybody else.
377 However using a default filter is an appropriate thing to do. How, is
378 explained further on.
381 The first thing that you must do is determine whether you need to use
382 route filtering at all. If you are a "normal" node with two or three
383 partners and you arranged in an "official" non-looping tree type
384 network, then you do not need to do route filtering and you will feel
385 a lot better for not getting involved. If you are successfully using
386 isolation then you also probably don't need to use route filtering.
389 To put it simply, you should not mix Isolation and Route Filtering.
390 It will work, of sorts, but you will not get the expected results. If
391 you are using Isolation sucessfully at the moment, do not get involved
392 in Route Filtering unless you have a good supply of aspirin! Once you
393 have started down the road of Route Filtering, do not use Isolation
394 either. Use one or the other, not both.
397 You will only require this functionality if you are "well-connected".
398 What that means is that you are connected to several different parts
399 of (say) the EU cluster and, at the same time, also connected to two
400 or three places in the US which, in turn are connected back to the EU.
401 This is called a "loop" and if you are seriously looped then you need
405 I should at this stage give a little bit of background on filters.
406 All the filters in Spider work in basically the same way. You can
407 either accept or reject various options in order to create the filter
408 rules you wish to achieve. Some filters are user settable, others can
409 only be altered by the sysop. Route filtering can only be done by the
414 Anyway, without further discouragement, let me start the process of
418 1.3. The node_default filter
420 All normal systems should have a default routing filter and it should
421 usually be set to send only the normal, unlooped, view of your
422 "national" network. Here in the UK that means nodes from the UK and
423 Eire, in EU it is more complex as the networks there grew up in a more
428 The generic commands are:-
432 reject/route node_default <filter_option>
436 accept/route node_default <filter_option>
440 where filter_option is one of the following ...
449 channel_dxcc <numbers>
450 channel_itu <numbers>
451 channel_zone <numbers>
455 Please be careful if you alter this setting, it will affect ALL your
456 links! Remember, this is a default filter for node connections, not a
460 For the default routing filter then you have two real choices: either
461 a "national" view or the "safe" option of only your own callsign.
462 Examples of each (for my node: GB7DJK) are:-
466 acc/route node_default call_dxcc 61,38
467 acc/route node_default call gb7djk
471 GB7DJK uses the first of these. The DXCC countries can be obtained
472 from the show/prefix command.
475 The example filters shown control output TO all your partner nodes
476 unless they have a specific filter applied to them (see next section).
479 It is also possible to control the incoming routing information that
480 you are prepared to accept FROM your partner nodes. The reason this is
481 necessary is to make sure that stuff like mail, pings and similar
482 commands a) go down the correct links and b) don't loop around
483 excessively. Again using GB7DJK as an example a typical default input
484 filter would be something like:
488 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
492 What this does is accept node and user information for our national
493 network from nodes that are in our national network, but rejects such
494 information from anyone else. Although it doesn't explicitly say so,
495 by implication, any other node information (not from the UK and Eire)
499 As I imagine it will take a little while to get one's head around all
500 of this you can study the effect of any rules that you try by watching
501 the debug output after having done:-
509 After you have got tired of that, to put it back the way it was:-
517 1.4. General route filtering
519 Exactly the same rules apply for general route filtering. You would
520 use either an accept filter or a reject filter like this ...
524 reject/route <node_call> <filter_option>
528 accept/route <node_call> <filter_option>
532 Here are some examples of route filters ...
536 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
537 rej/route all (equiv to [very] restricted mode)
538 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
539 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
543 In practice you will either be opening the default filter out for a
544 partner by defining a specific filter for that callsign:-
549 acc/route gb7baa input all
553 or restricting it quite a lot, in fact making it very nearly like an
554 isolated node, like this:-
558 acc/route pi4ehv-8 call gb7djk
559 rej/route pi4ehv-8 input call_dxcc 61,38
563 This last example takes everything except UK and Eire from PI4EHV-8
564 but only sends him my local configuration (just a PC19 for GB7DJK and
565 PC16s for my local users).
568 It is possible to write much more complex rules, there are up to 10
569 accept/reject pairs per callsign per filter. For more information see
574 1.5. General filter rules
576 Upto v1.44 it was not possible for the user to set their own filters.
577 From v1.45 though that has all changed. It is now possible to set
578 filters for just about anything you wish. If you have just updated
579 from an older version of DXSpider you will need to update your new
580 filters. You do not need to do anything with your old filters, they
581 will be renamed as you update.
584 There are 3 basic commands involved in setting and manipulating
585 filters. These are accept, reject and clear. First we will look
586 generally at filtering. There are a number of things you can filter in
587 the DXSpider system. They all use the same general mechanism.
590 In general terms you can create a "reject" or an "accept" filter which
591 can have up to 10 lines in it. You do this using, for example ...
600 where ..... are the specific commands for that type of filter. There
601 are filters for spots, wwv, announce, wcy and (for sysops) connects.
602 See each different accept or reject command reference for more
605 There is also a command to clear out one or more lines in a filter.
615 There is clear/xxxx command for each type of filter.
618 and you can check that your filters have worked by the command ...
626 For now we are going to use spots for the examples, but you can apply
627 the same principles to all types of filter.
632 There are two main types of filter, accept or reject. You can use
633 either to achieve the result you want dependent on your own preference
634 and which is more simple to do. It is pointless writing 8 lines of
635 reject filters when 1 accept filter would do the same thing! Each
636 filter has 10 lines (of any length) which are tried in order. If a
637 line matches then the action you have specified is taken (ie reject
638 means ignore it and accept means take it)
641 If you specify reject filters, then any lines that arrive that match
642 the filter will be dumped but all else will be accepted. If you use
643 an accept filter, then ONLY the lines in the filter will be accepted
644 and all else will be dumped. For example if you have a single line
649 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
653 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
655 If you set a reject filter like this ...
659 reject/spots on hf/cw
663 Then you will get everything EXCEPT HF CW spots. You could make this
664 single filter even more flexible. For example, if you are interested
665 in IOTA and will work it even on CW even though normally you are not
666 interested in CW, then you could say ...
670 reject/spots on hf/cw and not info iota
674 But in that case you might only be interested in iota and say:-
678 accept/spots not on hf/cw or info iota
682 which achieves exactly the same thing. You should choose one or the
683 other until you are comfortable with the way it works. You can mix
684 them if you wish (actually you can have an accept AND a reject on the
685 same line) but don't attempt this until you are sure you know what you
689 You can arrange your filter lines into logical units, either for your
690 own understanding or simply convenience. Here is an example ...
694 reject/spots 1 on hf/cw
695 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
699 What this does is to ignore all HF CW spots and also rejects any spots
700 on VHF which don't either originate or spot someone in Europe.
703 This is an example where you would use a line number (1 and 2 in this
704 case), if you leave the digit out, the system assumes '1'. Digits
705 '0'-'9' are available. This make it easier to see just what filters
706 you have set. It also makes it more simple to remove individual
707 filters, during a contest for example.
710 You will notice in the above example that the second line has
711 brackets. Look at the line logically. You can see there are 2
712 separate sections to it. We are saying reject spots that are VHF or
713 above APART from those in zones 14, 15 and 16 (either spotted there or
714 originated there). If you did not have the brackets to separate the 2
715 sections, then Spider would read it logically from the front and see a
716 different expression entirely ...
717 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
721 The simple way to remember this is, if you use OR - use brackets.
722 Whilst we are here CASE is not important. 'And BY_Zone' is just the
723 same as 'and by_zone'.
725 As mentioned earlier, setting several filters can be more flexible
726 than simply setting one complex one. Doing it in this way means that
727 if you want to alter your filter you can just redefine or remove one
728 or more lines of it or one line. For example ...
732 reject/spots 1 on hf/ssb
736 would redefine our earlier example, or
744 To remove all the filter lines in the spot filter ...
754 You can filter in several different ways. The options are listed in
755 the various helpfiles for accept, reject and filter.
760 Sometimes all that is needed is a general rule for node connects.
761 This can be done with a node_default filter. This rule will always be
762 followed, even if the link is isolated, unless another filter is set
763 specifically. Default rules can be set for nodes and users. They can
764 be set for spots, announces, WWV and WCY. They can also be used for
765 hops. An example might look like this ...
769 accept/spot node_default by_zone 14,15,16,20,33
770 set/hops node_default spot 50
774 This filter is for spots only, you could set others for announce, WWV
775 and WCY. This filter would work for ALL nodes unless a specific
776 filter is written to override it for a particular node. You can also
777 set a user_default should you require. It is important to note that
778 default filters should be considered to be "connected". By this I
779 mean that should you override the default filter for spots, you need
780 to add a rule for the hops for spots also.
783 1.9. Advanced filtering
785 Once you are happy with the results you get, you may like to
789 The previous example that filters hf/cw spots and accepts vhf/uhf
790 spots from EU can be written with a mixed filter, for example ...
796 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
800 Note that the first filter has not been specified with a number. This
801 will automatically be assumed to be number 1. In this case, we have
802 said reject all HF spots in the CW section of the bands but accept all
803 others at HF. Also accept anything in VHF and above spotted in or by
804 operators in the zones 14, 15 and 16. Each filter slot actually has a
805 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
809 It was mentioned earlier that after a reject test that doesn't match,
810 the default for following tests is 'accept', the reverse is true for
811 'accept'. In the example what happens is that the reject is executed
812 first, any non hf/cw spot is passed to the accept line, which lets
813 through everything else on HF. The next filter line lets through just
814 VHF/UHF spots from EU.
817 1.10. Basic hop control
819 In /spider/data you will find a file called hop_table.pl. This is the
820 file that controls your hop count settings. It has a set of default
821 hops on the various PC frames and also a set for each node you want to
822 alter the hops for. You may be happy with the default settings of
823 course, but this powerful tool can help to protect and improve the
824 network. The file will look something like this ...
829 # hop table construction
834 # default hopcount to use
837 # some variable hop counts based on message type
848 # the per node hop control thingy
880 Each set of hops is contained within a pair of curly braces and
881 contains a series of PC frame types. PC11 for example is a DX spot.
882 The figures here are not exhaustive but should give you a good idea of
886 SHould any of the nodecalls include an ssid, it is important to wrap
887 the whole call in single quotes, like this ...
902 If you do not do this, you will get errors and the file will not work
906 You can alter this file at any time, including whilst the cluster is
907 running. If you alter the file during runtime, the command load/hops
908 will bring your changes into effect.
911 1.11. Hop Control on Specific Nodes
913 You can set a callsign specific hop count for any of the standard
918 set/hops gb7djk spot 4
919 set/hops node_default route 10
920 set/hops gb7baa wcy 5
924 all work on their specific area of the protocol.
927 The set/hops command overrides any hops that you have set otherwise.
930 You can show what hops have been set using the show/hops command.
933 1.12. Isolating networks
935 It is possible to isolate networks from each other on a "gateway" node
936 using the set/isolate <node_call> command.
939 The effect of this is to partition an isolated network completely from
940 another node connected to your node. Your node will appear on and
941 otherwise behave normally on every network to which you are connected,
942 but data from an isolated network will not cross onto any other
943 network or vice versa. However all the spot, announce and WWV traffic
944 and personal messages will still be handled locally (because you are a
945 real node on all connected networks), that is locally connected users
946 will appear on all networks and will be able to access and receive
947 information from all networks transparently. All routed messages will
948 be sent as normal, so if a user on one network knows that you are a
949 gateway for another network, he can still still send a talk/announce
950 etc message via your node and it will be routed across.
953 If you use isolate on a node connection you will continue to receive
954 all information from the isolated partner, however you will not pass
955 any information back to the isolated node. There are times when you
956 would like to forward only spots across a link (maybe during a contest
957 for example). To do this, isolate the node in the normal way and use
958 an acc/spot >call< all filter to override the isolate.
965 In the /spider/msg directory you will find a file called
966 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
967 original looks something like this ....
971 # the list of regexes for messages that we won't store having
972 # received them (bear in mind that we must receive them fully before
976 # The format of each line is as follows
978 # type source pattern
979 # P/B/F T/F/O/S regex
981 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
982 # source: T - to field, F - from field, O - origin, S - subject
983 # pattern: a perl regex on the field requested
985 # Currently only type B and P msgs are affected by this code.
987 # The list is read from the top down, the first pattern that matches
988 # causes the action to be taken.
990 # The pattern can be undef or 0 in which case it will always be selected
991 # for the action specified
1002 I think this is fairly self explanatory. It is simply a list of
1003 subject headers that we do not want to pass on to either the users of
1004 the cluster or the other cluster nodes that we are linked to. This is
1005 usually because of rules and regulations pertaining to items for sale
1006 etc in a particular country.
1010 2.2. Filtering words from text fields in Announce, Talk and DX spots
1012 From version 1.48 onwards the interface to this has changed. You can
1013 now use the commands set/badword to add words that you are not
1014 prepared to see on the cluster, unset/badword to allow that word again
1015 and show/badword to list the words that you have set.
1018 If you have a previous /spider/data/badwords, the first time you start
1019 the node, it will read and convert this file to the new commands. The
1020 old style file will then be removed.
1023 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
1026 There are a number of commands that control whether a spot progresses
1027 any further by regarding it as "bad" in some way.
1030 A DX Spot has a number of fields which can be checked to see whether
1031 they contain "bad" values, they are: the DX callsign itself, the
1032 Spotter and the Originating Node.
1035 There are a set of commands which allow the sysop to control whether a
1046 These work in the same as the set/badword command, you can add any
1047 words or callsigns or whatever to the appropriate database. For
1048 example, to stop a spot from a particular node you do:
1052 set/badnode gb7djk gb7dxc
1060 set/badspotter b0mb p1rat nocall
1068 set/baddx video wsjt
1072 You can remove a word using the appropriate unset command
1073 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1074 of show/baddx, show/badspotter and show/badnode.
1080 DXSpider deals seamlessly with standard AK1A type mail. It supports
1081 both personal and bulletin mail and the sysop has additional commands
1082 to ensure that mail gets to where it is meant. DXSpider will send
1083 mail almost immediately, assuming that the target is on line.
1084 However, only one mail message is dealt with at any one time. If a
1085 mail message is already being sent or recieved, then the new message
1086 will be queued until it has finished.
1088 The cluster mail is automatically deleted after 30 days unless the
1089 sysop sets the "keep" flag using the msg command.
1094 Personal mail is sent using the sp command. This is actually the
1095 default method of sending mail and so a simple s for send will do. A
1096 full list of the send commands and options is in the command set
1097 section, so I will not duplicate them here.
1102 Bulletin mail is sent by using the sb command. This is one of the
1103 most common mistakes users make when sending mail. They send a
1104 bulletin mail with s or sp instead of sb and of course the message
1105 never leaves the cluster. This can be rectified by the sysop by using
1109 Bulletin addresses can be set using the Forward.pl file.
1114 DXSpider receives all and any mail sent to it without any alterations
1115 needed in files. Because personal and bulletin mail are treated
1116 differently, there is no need for a list of accepted bulletin
1117 addresses. It is necessary, however, to tell the program which links
1118 accept which bulletins. For example, it is pointless sending
1119 bulletins addresses to "UK" to any links other than UK ones. The file
1120 that does this is called forward.pl and lives in /spider/msg. At
1121 default, like other spider files it is named forward.pl.issue. Rename
1122 it to forward.pl and edit the file to match your requirements. The
1128 # this is an example message forwarding file for the system
1130 # The format of each line is as follows
1132 # type to/from/at pattern action destinations
1133 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1135 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1136 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1137 # pattern: a perl regex on the field requested
1138 # action: I - ignore, F - forward
1139 # destinations: a reference to an array containing node callsigns
1141 # if it is non-private and isn't in here then it won't get forwarded
1143 # Currently only type B msgs are affected by this code.
1145 # The list is read from the top down, the first pattern that matches
1146 # causes the action to be taken.
1148 # The pattern can be undef or 0 in which case it will always be selected
1149 # for the action specified
1151 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1152 # pattern) then it will always be forwarded to every node that doesn't have
1153 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1154 # you allow a new link with this on EVERY bull will be forwarded immediately
1155 # on first connection)
1165 Simply insert a bulletin address and state in the brackets where you
1166 wish that mail to go. For example, you can see here that mail sent to
1167 "UK" will only be sent to the UK links and not to PA4AB-14.
1170 To force the cluster to reread the file use load/forward
1173 NB: If a user tries to send mail to a bulletin address that does not
1174 exist in this file, they will get an error.
1177 3.4. The msg command
1179 The msg command is a very powerful and flexible tool for the sysop.
1180 It allows the sysop to alter to and from fields and make other changes
1181 to manage the cluster mail.
1183 Here is a full list of the various options ...
1187 MSG TO <msgno> <call> - change TO callsign to <call>
1188 MSG FRom <msgno> <call> - change FROM callsign to <call>
1189 MSG PRrivate <msgno> - set private flag
1190 MSG NOPRrivate <msgno> - unset private flag
1191 MSG RR <msgno> - set RR flag
1192 MSG NORR <msgno> - unset RR flag
1193 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1194 MSG NOKEep <msgno> - unset the keep flag
1195 MSG SUbject <msgno> <new> - change the subject to <new>
1196 MSG WAittime <msgno> - remove any waiting time for this message
1197 MSG NOREad <msgno> - mark message as unread
1198 MSG REad <msgno> - mark message as read
1199 MSG QUeue - queue any outstanding bulletins
1200 MSG QUeue 1 - queue any outstanding private messages
1204 These commands are simply typed from within the cluster as the sysop
1210 You can check on a message from within the cluster by using the
1211 command stat/msg. This will give you additional information on the
1212 message number including which nodes have received it, which node it
1213 was received from and when etc. Here is an example of the output of
1218 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1221 Msg Time: 26-Jan-2001 1302Z
1225 Subject: AMSAT 2line KEPS 01025.AMSAT
1227 Got it Nodes: GB7BAA, GB7ADX
1231 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1237 This is described in the section on Other filters so I will not
1241 3.7. Distribution lists
1243 Distribution lists are simply a list of users to send certain types of
1244 mail to. An example of this is mail you only wish to send to other
1245 sysops. In /spider/msg there is a directory called distro. You put
1246 any distibution lists in here. For example, here is a file called
1247 SYSOP.pl that caters for the UK sysops.
1250 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1251 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1252 GB7DXK GB7DXI GB7DXS)
1256 Any mail sent to "sysop" would only be sent to the callsigns in this
1262 Spider provides a simple BBS interface. No input is required from the
1263 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1264 and pushes any required mail to the cluster. No mail can flow from
1265 Spider to the BBS, the interface is one-way.
1268 Please be careful not to flood the cluster network with unnecessary
1269 mail. Make sure you only send mail to the clusters that want it by
1270 using the Forward.pl file very carefully.
1275 From 1.48 onwards it will become increasingly possible to control
1276 DXSpider's operation with scripts of various kinds.
1279 The directory /spider/scripts is where it all happens and is used for
1280 several things. Firstly it contains a file called startup that can be
1281 used to call in any changes to the cluster from the default settings
1282 on startup. This script is executed immediately after all
1283 initialisation of the node is done but before any connections are
1284 possible. Examples of this include how many spots it is possible to
1285 get with the sh/dx command, whether you want registration/passwords to
1286 be permanently on etc. An example file is shown below and is included
1287 in the distribution as startup.issue.
1292 # startup script example
1294 # set maximum no of spots allowed to 100
1295 # set/var $Spot::maxspots = 100
1297 # Set registration on
1298 # set/var $main::reqreg = 1
1301 # set/var $main::passwdreq = 1
1306 As usual, any text behind a # is treated as a comment and not read.
1307 To use this file, simply rename it from startup.issue to startup. In
1308 our example above there are three options. The first option is the
1309 amount of spots that a user can request with the sh/dx command.
1310 Normally the default is to give 10 spots unless the user specifies
1311 more. Without this line enabled, the maximum a user can request is
1312 100 spots. Depending on your link quality you may wish to enable more
1313 or less by specifying the number.
1316 The other 2 options are dealt with more fully in the security section.
1319 Secondly, it is used to store the login scripts for users and nodes.
1320 Currently this can only be done by the sysop but it is envisaged that
1321 eventually users will be able to set their own. An example is
1322 included in the distibution but here is a further example.
1339 The lines in between commands can simply insert a blank line or a
1340 character such as a + sign to make the output easier to read. Simply
1341 create this script with your favourite editor and save it with the
1342 callsign of the user as the filename. Filenames should always be in
1346 Commands can be inserted in the same way for nodes. A node may wish a
1347 series of commands to be issued on login, such as a merge command for
1351 Thirdly, there are 2 default scripts for users and nodes who do not
1352 have a specifically defined script. These are user_default and
1358 Spider allows the creation of local or remote databases. It supports
1359 chained databases, allowing several different databases to be scanned
1360 with one simple command. Importing of databases is limited at present
1361 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1362 database but will expand with time.
1365 5.1. Creating databases
1367 Creating a database could not be more simple. All the commands are
1368 sent from the cluster prompt as the sysop user.
1370 To create a database you use the command dbcreate. It can be used in
1371 3 different ways like so ..
1378 To simply create a database locally, you just tell the command the
1379 name of the database. This does not create the actual database, it
1380 simply defines it to say that it exists.
1384 dbcreate <name> chain <name> [<name>...]
1388 This creates a chained database entry. The first database will be
1389 scanned, then the second, the third etc...
1393 dbcreate <name> remote <name>
1397 This creates a remote entry. the first name field is the database
1398 name at the remote node, then the remote switch, then the actual
1399 node_call of the remote node, for example...
1403 dbcreate buckmaster remote gb7dxc
1407 Remote databases cannot be chained, however, the last database in a
1408 chain can be a remote database.
1411 5.2. Importing databases
1413 The only databases that Spider can currently import are the standard
1414 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1415 This will be added to with time.
1417 To import such a database, first put the file somewhere useful like
1418 /tmp and then issue the following command ...
1422 dbimport oblast /tmp/OBLAST.FUL
1426 This will update the existing local oblast database or create it if it
1430 5.3. Checking available databases
1432 Once a database is created, you will want to check that it has been
1433 added. To do this use the dbavail command. This will output the
1434 available databases. For example ...
1439 DB Name Location Chain
1443 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1447 5.4. Looking up databases
1449 To look for information in a defined database, simply use the dbshow
1450 command, for example ...
1454 dbshow buckmaster G0YLM
1458 will show the information for the callsign G0YLM from the buckmaster
1459 database if it exists. To make things more standard for the users you
1460 can add an entry in the Aliases file so that it looks like a standard
1461 show command like this ...
1465 Now you can simply use show/buckmaster or an abreviation.
1468 5.5. Removing databases
1470 To delete an existing database you use the dbremove command. For
1479 would remove the oblast database and its associated datafile from the
1480 system. There are no warnings or recovery possible from this command.
1481 If you remove a database it ceases to exist and would have to be
1482 created from scratch if you still required it.
1485 6. Information, files and useful programs
1489 One of the more important things a cluster sysop needs to do is to get
1490 information to his users. The simplest way to do this is to have a
1491 banner that is sent to the user on login. This is know as a "message
1492 of the day" or "motd". To set this up, simply create a file in
1493 /spider/data called motd and edit it to say whatever you want. It is
1494 purely a text file and will be sent automatically to anyone logging in
1498 This message of the day file lives in the same directory as the
1499 standard motd file but is only sent to non-registered users. Once
1500 registered they will receive the same message as any other user.
1503 6.3. Downtime message
1505 If for any reason the cluster is down, maybe for upgrade or
1506 maintenance but the machine is still running, a message can be sent to
1507 the user advising them of the fact. This message lives in the
1508 /spider/data directory and is called "offline". Simply create the
1509 file and edit it to say whatever you wish. This file will be sent to
1510 a user attempting to log into the cluster when DXSpider is not
1514 6.4. Other text messages
1516 You can set other text messages to be read by the user if they input
1517 the file name. This could be for news items or maybe information for
1518 new users. To set this up, make a directory under /spider called
1519 packclus. Under this directory you can create files called news or
1520 newuser for example. In fact you can create files with any names you
1521 like. These can be listed by the user with the command ....
1529 They can be read by the user by typing the command ....
1537 If the file they want to read is called news. You could also set an
1538 alias for this in the Alias file to allow them just to type news
1541 You can also store other information in this directory, either
1542 directly or nested under directories. One use for this would be to
1543 store DX bulletins such as the OPDX bulletins. These can be listed
1544 and read by the user. To keep things tidy, make a directory under
1545 /spider/packclus called bulletin. Now copy any OPDX or similar
1546 bulletins into it. These can be listed by the user in the same way as
1547 above using the show/files command with an extension for the bulletin
1548 directory you have just created, like this ....
1556 An example would look like this ....
1559 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1563 You can see that in the files area (basically the packclus directory)
1564 there is a file called news and a directory called bulletin. You can
1565 also see that dates they were created. In the case of the file news,
1566 you can also see the time it was last modified, a good clue as to
1567 whether the file has been updated since you last read it. To read the
1568 file called news you would simply issue the command ....
1576 To look what is in the bulletin directory you issue the command ....
1581 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1582 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1583 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1584 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1585 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1586 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1587 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1588 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1589 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1590 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1591 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1592 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1593 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1594 Press Enter to continue, A to abort (16 lines) >
1598 You can now read any file in this directory using the type command,
1603 type bulletin/opdx391
1604 Ohio/Penn DX Bulletin No. 391
1605 The Ohio/Penn Dx PacketCluster
1609 Editor Tedd Mirgliotta, KB8NW
1610 Provided by BARF-80 BBS Cleveland, Ohio
1611 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1612 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1613 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1614 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1615 Press Enter to continue, A to abort (508 lines) >
1619 The page length will of course depend on what you have it set to!
1622 6.5. The Aliases file
1624 You will find a file in /spider/cmd/ called Aliases. This is the file
1625 that controls what a user gets when issuing a command. It is also
1626 possible to create your own aliases for databases and files you create
1630 You should not alter the original file in /spider/cmd/ but create a
1631 new file with the same name in /spider/local_cmd. This means that any
1632 new Aliases files that is downloaded will not overwrite your self
1633 created Aliases and also that you do not override any new Aliases with
1634 your copy in /spider/local_cmd/. You must remember that any files you
1635 store in /spider/local/ or /spider/local_cmd override the originals if
1636 the same lines are used in both files.
1639 The best way of dealing with all this then is to only put your own
1640 locally created Aliases in the copy in /spider/local_cmd. The example
1641 below is currently in use at GB7MBC.
1646 # Local Aliases File
1653 '^news$', 'type news', 'type',
1656 '^sh\w*/buck$', 'show/qrz', 'show',
1657 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1658 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1659 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1660 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1666 Each alphabetical section should be preceded by the initial letter and
1667 the section should be wrapped in square brackets as you can see. The
1668 syntax is straightforward. The first section on each line is the new
1669 command that will be allowed once the alias is included. The second
1670 section is the command it is replacing and the last section is the
1671 actual command that is being used.
1674 The eagle-eyed amongst you will have noticed that in the first
1675 section, the new alias command has a '^' at the start and a '$' at the
1676 end. Basically these force a perfect match on the alias. The '^'
1677 says match the beginning exactly and the with similar commands.
1680 I have 3 different types of alias in this file. At the top is an
1681 alias for 'news'. This is a file I have created in the
1682 /spider/packclus/ directory where I can inform users of new
1683 developments or points of interest. In it's initial form a user would
1684 have to use the command type news. The alias allows them to simply
1685 type news to get the info. Second is an alias for the show/qrz
1686 command so that those users used to the original show/buck command in
1687 AK1A will not get an error, and the rest of the lines are for locally
1688 created databases so that a user can type show/hftest instead of
1689 having to use the command dbshow hftest which is not as intuitive.
1692 This file is just an example and you should edit it to your own
1693 requirements. Once created, simply issue the command load/alias at
1694 the cluster prompt as the sysop user and the aliases should be
1701 In later versions of Spider a simple console program is provided for
1702 the sysop. This has a type ahead buffer with line editing facilities
1703 and colour for spots, announces etc. To use this program, simply use
1704 console.pl instead of client.
1707 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1708 edit the file with your favourite editor.
1711 6.7. Updating kepler data
1713 Spider has a powerful and flexible show/satellite command. In order
1714 for this to be accurate, the kepler data has to be updated regularly.
1715 In general, this data is available as an email or via cluster mail.
1716 Updating it is simple. First you need to export the mail message as a
1717 file. You do this with the export command from the cluster prompt as
1718 the sysop. For example ...
1722 export 5467 /spider/perl/keps.in
1726 would export message number 5467 as a file called keps.in in the
1727 /spider/perl directory.
1730 Now login to a VT as sysop and cd /spider/perl. There is a command in
1731 the perl directory called convkeps.pl. All we need to do now is
1732 convert the file like so ...
1736 ./convkeps.pl keps.in
1740 Now go back to the cluster and issue the command ...
1748 That is it! the kepler data has been updated.
1751 6.8. The QRZ callbook
1753 The command sh/qrz will only work once you have followed a few simple
1754 steps. First you need to get a user ID and password from qrz.com.
1755 Simply go to the site and create one. Secondly you need to copy the
1756 file /spider/perl/Internet.pm to /spider/local and alter it to match
1757 your user ID and password. You also at this point need to set
1758 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1759 proprieter of qrz.com for allowing this access.
1762 6.9. Connecting logging programs
1764 There appear to be very few logging programs out there that support
1765 telnet especially the popular ones like LogEQF, Turbolog etc. This
1766 can make it difficult to connect to your own cluster! The way to do
1767 it is to make the logging program think it has a TNC attached to a com
1768 port on the logging PC and 'push' a linux login out to it. This is
1769 achieved very simply by the use of agetty.
1772 All that is required is to add a line in /etc/inittab to have the
1773 client ready for a connection on the com port of your choice.
1774 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1779 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1783 Add this after the standard runlevel lines in /etc/inittab. The above
1784 line works on ttyS1 (com2). Now as root, issue the command telinit q
1785 and it should be ready for connection. All that is required is a 3
1786 wire serial lead (tx, rx and signal ground). Tell you logging program
1787 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1788 Login as normal and then telnet from there to the cluster.
1793 In the spider tree will be a directory spider-web. This is a neat
1794 little java web applet that can be run from a website. The applet
1795 must run on the same machine as the cluster. The included README file
1799 I should comment here that the applet is precompiled, that is, ready
1800 to go. It was compiled using JDK1.3.1. If your version is earlier
1801 than this then it may not work. Should that be the case you need to
1802 recompile or update your JDK. To recompile do the following ...
1806 cd /spider/spider-web
1808 /usr/bin/javac spiderclient.java
1812 I have used /usr/bin/javac as an example, your path to javac may be
1818 Completely based on a clx web client written in Java by dl6dbh
1819 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1821 The webserver has to run on the same machine as your DxSpider software!
1823 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1825 Installation instructions (Performed as root):
1827 Put all the files in the spider-web directory into a newly created directory
1828 under the DocumentRoot of your websever for instance 'client'. In my case
1829 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1830 path should be /usr/local/httpd/htdocs/client/ for example.
1832 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1833 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1834 /usr/local/httpd/cgi-bin/ for example.
1836 Change the permissions of the files to ensure they are correct, obviously you
1837 will need to use the correct path the the files according to your system:
1839 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1840 chmod -R 755 /home/httpd/html/client/
1842 By default the spider.cgi script should pick up your hostname (As long as this
1843 is set correctly). If it does not or your hostname differs from the name that
1844 you attach to the public address that you are using, then edit spider.cgi :
1846 # Uncomment and set the hostname manually here if the above fails.
1847 # $HOSTNAME = "gb7mbc.spoo.org" ;
1851 telnet (see Listeners.pm)
1853 NOTE: If you can start the console but cannot connect to the cluster from it,
1854 then it is possible that the machine you are on cannot resolve the hostname of
1855 your cluster machine. If this is the case, you need to set your hostname
1858 You also need to set the $NODECALL variable. This prints the name of your
1859 choosing (probably your cluster callsign) on the html page.
1861 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1865 8. Web based statistics
1867 From version 1.50, you can use the freeware software MRTG to produce
1868 really nice graphical statistics on your web site. For an example try
1869 http://www.gb7mbc.net/mrtg/stats.html.
1872 The following should help you get it all working.
1875 First you need to download the latest version of MRTG from
1876 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1877 the following files..
1881 libpng-1.0.14.tar.gz
1887 Login to your machine as the root user, put all the downloaded files
1888 in /usr/local/src/ (or wherever you prefer) and untar and compile
1889 them. All the information to compile and install these sources come
1890 with them. After compilation and installation, you will find MRTG in
1894 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1898 You now need to make 2 symbolic links like below...
1902 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1903 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1907 Now login to the cluster with your sysop callsign and run the command
1911 Now you are nearly there! Login as the sysop user and change to the
1912 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1917 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1921 Changing the callsign for your own cluster callsign of course!
1924 And finally you need to login as the root user and create one last
1925 symbolic link. Where this points will depend on where your html
1926 documents are kept. For RedHat systems you use...
1930 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1934 and for SuSE systems...
1938 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1942 If you now point your browser to your website as below it should all
1947 http://www.xxx.xxx/mrtg/stats.html
1951 Of course, to get the stats to update, you need to add some
1952 information in the spider crontab file as below...
1956 # Update stats for mrtg on website
1957 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1961 This will update the site every 5 minutes.
1966 From version 1.49 DXSpider has some additional security features.
1967 These are not by any means meant to be exhaustive, however they do
1968 afford some security against piracy. These two new features can be
1969 used independently of each other or in concert to tighten the
1975 The basic principle of registration is simple. If a user is not
1976 registered by the sysop, then they have read-only access to the
1977 cluster. The only thing they can actually send is a talk or a message
1978 to the sysop. In order for them to be able to spot, send announces or
1979 talks etc the sysop must register them with the set/register command,
1988 The user g0vgs can now fully use the cluster. In order to enable
1989 registration, you can issue the command ...
1991 set/var $main::reqreg = 1
1995 Any users that are not registered will now see the motd_nor file
1996 rather than the motd file as discussed in the Information, files and
1997 useful programs section.
2000 Entering this line at the prompt will only last for the time the
2001 cluster is running of course and would not be present on a restart.
2002 To make the change permanent, add the above line to
2003 /spider/scripts/startup. To read more on the startup file, see the
2004 section on Information, files and useful programs.
2007 To unregister a user use unset/register and to show the list of
2008 registered users, use the command show/register.
2013 At the moment, passwords only affect users who login to a DXSpider
2014 cluster node via telnet. If a user requires a password, they can
2015 either set it themselves or have the sysop enter it for them by using
2016 the set/password command. Any users who already have passwords, such
2017 as remote sysops, will be asked for their passwords automatically by
2018 the cluster. Using passwords in this way means that the user has a
2019 choice on whether to have a password or not. To force the use of
2020 passwords at login, issue the command ...
2024 set/var $main::passwdreq = 1
2028 at the cluster prompt. This can also be added to the
2029 /spider/scripts/startup file as above to make the change permanent.
2032 Of course, if you do this you will have to assign a password for each
2033 of your users. If you were asking them to register, it is anticipated
2034 that you would ask them to send you a message both to ask to be
2035 registered and to give you the password they wish to use.
2038 Should a user forget their password, it can be reset by the sysop by
2039 first removing the existing password and then setting a new one like
2044 unset/password g0vgs
2045 set/password g0vgs new_password
2053 10.1. CVS from a Linux platform
2055 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2056 is held at Sourceforge. This means that it is possible to update your
2057 DXSpider installation to the latest sources by using a few simple
2058 commands. A graphical interface to CVS for Windows is explained in
2062 Please be aware that if you update your system using CVS, it is
2063 possible that you could be running code that is very beta and not
2064 fully tested. There is a possibility that it could be unstable.
2067 I am of course assuming that you have a machine with both DXSpider and
2068 Internet access running.
2071 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2072 ENTIRE SPIDER TREE!!
2075 Assuming you are connected to the Internet, you need to login to the
2076 CVS repository and then update your Spider source. There are several
2077 steps which are listed below ...
2080 First login as the user sysop. Next you need to connect to the CVS
2081 repository. You do this with the command below ...
2084 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2088 You will get a password prompt. Simply hit return here and your
2089 machine should return to a normal linux prompt.
2092 What happens next depends on whether you have an existing installation
2093 that you want to update with the latest and greatest or whether you
2094 just want to see what is there and/or run it on a new machine for
2097 If you are installing Spider from CVS then change directory to
2100 If you are wanting to update Spider then cd to /tmp
2103 The next step will create a brand new 'spider' directory in your
2107 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2111 This command is all on one line.
2114 Hopefully your screen should show you downloading files. The -z3
2115 simply compresses the download to improve speed. When this has
2116 finished, you will have exactly the same as if you had untarred a full
2117 tarball PLUS some extra directories and files that CVS needs to do the
2119 Now if you are doing a new installation, that's it. Carry on as if
2120 you have just downloaded and untarred the lastest tarball.
2123 If you want to upgrade your current installation then do this ...
2127 tar cvfz /tmp/s.tgz spider
2129 tar xvfzp /tmp/s.tgz
2133 This is assuming you downloaded to the /tmp directory of course.
2136 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2137 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2140 Remember to recompile the C client (cd /spider/src; make)
2143 At this point the files have been upgraded. You can (usually) restart
2144 the cluster in your own time. However, if you attempt to use any new
2145 commands or features expect it to be fatal! At least your cluster
2146 will have been restarted then so it will be too late to worry about
2150 Now the magic part! From now on when you want to update, simply
2151 connect to the Internet and then, as the user sysop ...
2160 and your files will be updated. As above, remember to recompile the
2161 "C" client if it has been updated (CVS will tell you) and restart if
2162 any of the perl scripts have been altered or added, again, CVS will
2166 You will find any changes documented in the /spider/Changes file.
2169 10.2. CVS from a Windows platform
2171 After the initial setup, an update to your DXSpider software is no
2172 more than a couple of clicks away. This section is intended to
2173 explain and illustrate the use of the WinCVS application to update
2174 your DXSpider software. The current stable version of WinCVS is Ver.
2175 1.2. You can get this software at:
2177 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2179 Pick your download mirror and then install WinCVS after the download
2183 In this next section I have included a series of links to .jpg files
2184 to take advantage of the picture and 1000 words equivalency. The .jpg
2185 files are in the C:\spider\html directory. If someone using a Linux
2186 system is reading this section from boredom, the files are in
2187 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2188 of gcvs and do your updates graphically as opposed to from the command
2189 line. The following descriptions are almost identical between WinCvs
2190 and gcvs. The following screen shots have duplicate links, depending
2191 upon whether you are viewing this information under the Windows or
2192 Linux operating system.
2194 When WinCVS is installed, running, and you are connected to the
2195 internet, the initial screen looks like:
2199 If you want, you can also look at these .jpg files with another viewer
2200 that might provide some better clarity to the image. On the left is
2201 the directory tree for your hard disk. Notice that the spider
2202 directory has a gray highlight.
2204 To start configuring WinCVS, click on Admin at the top of the screen
2205 and then Preferences. This should get you:
2209 In the top line for CVSROOT, enter:
2212 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2219 "passwd" file on the cvs server
2223 for Authentication on the General tab.
2225 Next, move to the right to the Ports tab.
2229 In here, check the box on the second line down for the "pserver" port.
2230 Enter a port number of 2401.
2232 Finally, go to the WinCvs tab all the way to the right.
2236 Enter Notepad as the viewer to open files. For the HOME folder, put
2237 "C:\spider" and click OK because the configuration is now complete.
2239 You are now ready to upgrade your copy of DXSpider. Click on the
2240 greyed Spider folder shown in the directory tree on the left of the
2241 WinCVS display. Two things should happen. The Spider folder will be
2242 selected and the greyed-out arrow located just below the word Query in
2243 the top line will turn to solid green.
2245 For anyone using gcvs under Linux, the green arrow is located on the
2246 extreme left of the display, under the word File. A gcvs screen looks
2251 Click on the now green arrow to start the download process. An Update
2252 Settings box will be displayed to which you can simply say OK.
2256 For future reference, the Update Settings box is the place where you
2257 can enter information to revert to a prior version of DXSpider.
2258 Information on reverting to a Before Date is contained in the WinCVS
2261 After a short period of time, a series of file names will scroll by in
2262 the lower pane of the WinCVS window. Eventually you should see
2265 *****CVS exited normally with code 0*****
2269 appear in the lower pane. You're done. The updated files are in
2270 place ready for you to stop and then restart your DXSpider. After the
2271 restart, you're running with the latest version of DXSpider.
2275 To paraphrase from the CVS section... Now the magic part! From now on
2276 when you want to update, simply connect to the Internet and start
2280 Click on the greyed-out Spider directory in the left screen
2281 Click on the green down arrow
2282 Click OK on the Update Settings dialog box
2283 Restart your Spider software
2289 accept Set a filter to accept something
2291 Create a filter to accept somethingThere are 2 types of filter, accept
2292 and reject. See HELP FILTERING for moreinfo.
2294 10.4. accept/announce <call> [input] [0-9] <pattern> (8)
2296 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2299 This version allows a sysop to set a filter for a callsign as well as
2300 thedefault for nodes and users eg:-
2303 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2307 10.5. accept/announce [0-9] <pattern> (0)
2309 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2312 Create an 'accept this announce' line for a filter. An accept filter
2313 line means that if the announce matches this filter it ispassed onto
2314 the user. See HELP FILTERING for more info. Please read thisto
2315 understand how filters work - it will save a lot of grief later on.You
2316 can use any of the following things in this line:-
2319 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)
2326 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)
2340 acc/ann by_state va,nh,ri,nh
2344 You can use the tag 'all' to accept everything eg:
2351 but this probably for advanced users...
2353 10.6. accept/route <call> [0-9] <pattern> (8)
2355 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2358 Create an 'accept this routing PC Protocol' line for a filter. An
2359 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2360 filter it is passed thru that interface. See HELP FILTERING for more
2361 info. Please read thisto understand how filters work - it will save a
2362 lot of grief later on.You can use any of the following things in this
2366 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
2373 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2377 you can now use 'by' as a synonym for 'call' so:
2380 by = call by_dxcc = call_dxcc
2384 and so onYou can use the tag 'all' to accept everything eg:
2391 10.7. accept/spots <call> [input] [0-9] <pattern> (8)
2393 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2395 This version allows a sysop to set a filter for a callsign as well as
2396 thedefault for nodes and users eg:-
2399 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2403 accept/spot user_default by G,M,2
2407 10.8. accept/spots [0-9] <pattern> (0)
2409 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2411 Create an 'accept this spot' line for a filter. An accept filter line
2412 means that if the spot matches this filter it ispassed onto the user.
2413 See HELP FILTERING for more info. Please read thisto understand how
2414 filters work - it will save a lot of grief later on.You can use any of
2415 the following things in this line:-
2418 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>
2422 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2426 You can use the tag 'all' to accept everything, eg:
2436 acc/spots by_state VA,NH,RI,MA,ME
2440 but this probably for advanced users...
2442 10.9. accept/wcy <call> [input] [0-9] <pattern> (8)
2444 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2446 This version allows a sysop to set a filter for a callsign as well as
2447 thedefault for nodes and users eg:-
2450 accept/wcy node_default all set/hops node_default 10
2454 10.10. accept/wcy [0-9] <pattern> (0)
2456 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2458 It is unlikely that you will want to do this, but if you do then you
2459 canfilter on the following fields:-
2462 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>
2466 There are no examples because WCY Broadcasts only come from one place
2467 andyou either want them or not (see UNSET/WCY if you don't want
2468 them).This command is really provided for future use.See HELP FILTER
2471 10.11. accept/wwv <call> [input] [0-9] <pattern> (8)
2473 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2475 This version allows a sysop to set a filter for a callsign as well as
2476 thedefault for nodes and users eg:-
2479 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2483 accept/wwv user_default by W,K
2487 10.12. accept/wwv [0-9] <pattern> (0)
2489 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2491 It is unlikely that you will want to do this, but if you do then you
2492 canfilter on the following fields:-
2495 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>
2502 accept/wwv by_zone 4
2506 is probably the only useful thing to do (which will only show WWV
2507 broadcastsby stations in the US).See HELP FILTER for information.
2509 10.13. announce <text> (0)
2511 announce <text> Send an announcement to LOCAL users only
2513 <text> is the text of the announcement you wish to broadcast
2515 10.14. announce full <text> (0)
2517 announce full <text> Send an announcement cluster wide
2519 This will send your announcement cluster wide
2521 10.15. announce sysop <text> (5)
2523 announce sysop <text> Send an announcement to Sysops only
2526 10.16. apropos <string> (0)
2528 apropos <string> Search help database for <string>
2530 Search the help database for <string> (it isn't case sensitive), and
2531 printthe names of all the commands that may be relevant.
2533 10.17. blank [<string>] [<nn>] (0)
2535 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2537 In its basic form this command prints one or more blank lines. However
2538 ifyou pass it a string it will replicate the string for the width of
2539 the screen (default 80) and then print that one or more times, so:
2546 prints two blank lines
2553 prints a row of - characters once.
2560 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2561 script file and you can print a maximumof 9 lines.
2565 bye Exit from the cluster
2567 This will disconnect you from the cluster
2569 10.19. catchup <node call> all|[<msgno> ...] (5)
2571 catchup <node call> all|[<msgno> ...] Mark a message as sent
2574 10.20. chat <group> <text> (0)
2576 chat <group> <text> Chat or Conference to a group
2578 It is now possible to JOIN a group and have network wide conferencing
2579 to thatgroup. DXSpider does not (and probably will not) implement the
2580 AK1A conference mode as this seems very limiting, is hardly used and
2581 doesn't seemto work too well anyway.This system uses the existing ANN
2582 system and is compatible with both otherDXSpider nodes and AK1A
2583 clusters (they use ANN/<group>). You can be a member of as many
2584 "groups" as you want. To join a group type:-
2587 JOIN FOC (where FOC is the group name)
2591 To leave a group type:-
2598 You can see which groups you are in by typing:-
2605 and you can see whether your mate is in the group, if he connects to
2606 thesame node as you, by typing:-
2613 To send a message to a group type:-
2616 CHAT FOC hello everyone
2623 CH #9000 hello I am back
2626 See also JOIN, LEAVE, SHOW/CHAT
2628 10.21. clear/announce <callsign> [input] [0-9|all] (8)
2630 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2633 A sysop can clear an input or normal output filter for a user or
2634 thenode_default or user_default.
2636 10.22. clear/announce [1|all] (0)
2638 clear/announce [1|all] Clear a announce filter line
2640 This command allows you to clear (remove) a line in a annouce filter
2641 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2644 10.23. clear/route <callsign> [input] [0-9|all] (8)
2646 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2648 A sysop can clear an input or normal output filter for a user or
2649 thenode_default or user_default.
2651 10.24. clear/route [1|all] (0)
2653 clear/route [1|all] Clear a route filter line
2655 This command allows you to clear (remove) a line in a route filter or
2656 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2659 10.25. clear/spots <callsign> [input] [0-9|all] (8)
2661 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2663 A sysop can clear an input or normal output filter for a user or
2664 thenode_default or user_default.
2666 10.26. clear/spots [0-9|all] (0)
2668 clear/spots [0-9|all] Clear a spot filter line
2670 This command allows you to clear (remove) a line in a spot filter or
2671 to remove the whole filter.If you have a filter:-
2674 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2685 you will be left with:-
2688 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2699 the filter will be completely removed.
2701 10.27. clear/wcy <callsign> [input] [0-9|all] (8)
2703 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2705 A sysop can clear an input or normal output filter for a user or
2706 thenode_default or user_default.
2708 10.28. clear/wcy [1|all] (0)
2710 clear/wcy [1|all] Clear a WCY filter line
2712 This command allows you to clear (remove) a line in a WCY filter or to
2713 remove the whole filter.see CLEAR/SPOTS for a more detailed
2716 10.29. clear/wwv <callsign> [input] [0-9|all] (8)
2718 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2720 A sysop can clear an input or normal output filter for a user or
2721 thenode_default or user_default.
2723 10.30. clear/wwv [1|all] (0)
2725 clear/wwv [1|all] Clear a WWV filter line
2727 This command allows you to clear (remove) a line in a WWV filter or to
2728 remove the whole filter.see CLEAR/SPOTS for a more detailed
2731 10.31. connect <callsign> (5)
2733 connect <callsign> Start a connection to another DX Cluster
2735 Start a connection process that will culminate in a new connection to
2736 theDX cluster <callsign>. This process creates a new 'client' process
2737 which willuse the script in /spider/connect/<callsign> to effect the
2738 'chat' exchangenecessary to traverse the network(s) to logon to the
2743 dbavail Show a list of all the Databases in the system
2745 Title says it all really, this command lists all the databases
2746 definedin the system. It is also aliased to SHOW/COMMAND.
2748 10.33. dbcreate <name> (9)
2750 dbcreate <name> Create a database entry
2753 10.34. dbcreate <name> chain <name> [<name>..] (9)
2755 dbcreate <name> chain <name> [<name>..] Create a chained database
2758 10.35. dbcreate <name> cmd <dxspider command> (9)
2760 dbcreate <name> cmd <dxspider command> make a local command available
2763 DBCREATE allows you to define a database in the system. It doesn't
2764 actuallycreate anything, just defines it.The databases that are
2765 created are simple DB_File hash databases, they are therefore already
2766 'indexed'.You can define a local database with the first form of the
2774 You can also chain databases with the addition of the 'chain' keyword.
2775 This will search each database one after the other. A typical example
2779 DBCREATE sdx_qsl chain sql_ad
2783 No checking is done to see if the any of the chained databases exist,
2784 infact it is usually better to do the above staement first then do
2785 each ofthe chained databases.Databases can exist offsite. To define a
2786 database that lives on another node do:
2789 DBCREATE buckmaster remote gb7dxc
2793 Remote databases cannot be chained; however, the last database in a a
2794 chain can be a remote database eg:
2797 DBCREATE qsl chain gb7dxc
2801 To see what databases have been defined do:
2804 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2808 It would be normal for you to add an entry into your local Aliases
2809 fileto allow people to use the 'SHOW/<dbname>' style syntax. So you
2810 wouldneed to add a line like:-
2813 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
2824 to work as they may be used to.You can also make local commands avail-
2825 able as 'pseudo' databases. Youcan therefore make spider special com-
2826 mands available as a database. Iimagine that this will be primarily
2827 useful for remote access from legacy nodes. For example:-
2830 DBCREATE dxqsl cmd show/dxqsl
2834 You also use one of these databases in a chain. This may be useful
2835 locally. See DBIMPORT for the importing of existing AK1A format data
2836 to databases.See DBSHOW for generic database enquiry
2838 10.36. dbcreate <name> remote <node> (9)
2840 dbcreate <name> remote <node> Create a remote database entry
2843 10.37. dbimport <dbname> <filename> (9)
2845 dbimport <dbname> <filename> Import AK1A data into a database
2847 If you want to import or update data in bulk to a database you can
2848 usethis command. It will either create or update entries into an
2849 existingdatabase. For example:-
2852 DBIMPORT oblast /tmp/OBLAST.FUL
2856 will import the standard OBLAST database that comes with AK1A into
2857 theoblast database held locally.
2859 10.38. dbremove <dbname> (9)
2861 dbremove <dbname> Delete a database
2863 DBREMOVE will completely remove a database entry and also delete any
2864 datafile that is associated with it. There is no warning, no comeback,
2865 no safety net. For example:
2872 will remove the oblast database from the system and it will also
2873 removethe associated datafile.I repeat:There is no warning, no come-
2874 back, no safety net.You have been warned.
2876 10.39. dbshow <dbname> <key> (0)
2878 dbshow <dbname> <key> Display an entry, if it exists, in a database
2880 This is the generic user interface to the database to the database
2881 system.It is expected that the sysop will add an entry to the local
2882 Aliases fileso that users can use the more familiar AK1A style of
2890 but if he hasn't and the database really does exist (use DBAVAIL
2891 orSHOW/COMMAND to find out) you can do the same thing with:
2900 debug Set the cluster program into debug mode
2902 Executing this command will only have an effect if you are running the
2903 clusterin debug mode i.e.
2910 It will interrupt the cluster just after the debug command has fin-
2913 10.41. delete/usdb <callsign> ... (9)
2915 delete/usdb <callsign> ... Delete this user from the US State Database
2917 This command will completely remove a one or more callsignsfrom the US
2918 States database.There is NO SECOND CHANCE.It goes without saying that
2919 you should use this command CAREFULLY!Note that these callsign may be
2920 re-instated by any weekly updates from the FCC.
2922 10.42. delete/user <callsign> ... (9)
2924 delete/user <callsign> ... Delete this user from the User Database
2926 This command will completely remove a one or more users from the
2927 database.There is NO SECOND CHANCE.It goes without saying that you
2928 should use this command CAREFULLY!
2930 10.43. demonstrate <call> <command> (9)
2932 demonstrate <call> <command> Demonstrate a command to another user
2934 This command is provided so that sysops can demonstrate commands to
2935 other users. It runs a command as though that user had typed it in
2936 andthen sends the output to that user, together with the command that
2940 DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
2944 Note that this command is similar to SPOOF and will have the same
2945 sideeffects. Commands are run at the privilege of the user which is
2946 beingdemonstrated to.
2948 10.44. directory (0)
2950 directory List messages
2954 10.45. directory <from>-<to> (0)
2956 directory <from>-<to> List messages <from> message <to> message
2958 List the messages in the messages directory.If there is a 'p' one
2959 space after the message number then it is a personal message. If there
2960 is a '-' between the message number and the'p' then this indicates
2961 that the message has been read.You can use shell escape characters
2962 such as '*' and '?' in the <call>fields.You can combine some of the
2963 various directory commands together eg:-
2973 DIR SUBJECT IOTA 200-250
2977 You can abbreviate all the commands to one letter and use ak1a syn-
2981 DIR/T G1* 10 DIR/S QSL 10-100 5
2985 10.46. directory <nn> (0)
2987 directory <nn> List last <nn> messages
2990 10.47. directory all (0)
2992 directory all List all messages
2995 10.48. directory from <call> (0)
2997 directory from <call> List all messages from <call>
3000 10.49. directory new (0)
3002 directory new List all new messages
3005 10.50. directory own (0)
3007 directory own List your own messages
3010 10.51. directory subject <string> (0)
3012 directory subject <string> List all messages with <string> in subject
3015 10.52. directory to <call> (0)
3017 directory to <call> List all messages to <call>
3019 10.53. directory- (5)
3023 Sysops can see all users' messages.
3025 10.54. disconnect <call> [<call> ...] (8)
3027 disconnect <call> [<call> ...] Disconnect a user or cluster
3029 Disconnect any <call> connected locally
3031 10.55. dx [by <call>] <freq> <call> <remarks> (0)
3033 dx [by <call>] <freq> <call> <remarks> Send a DX spot
3035 This is how you send a DX Spot to other users. You can, in fact,
3036 nowenter the <freq> and the <call> either way round.
3039 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
3043 will all give the same result. You can add some remarks to the endof
3044 the command and they will be added to the spot.
3047 DX FR0G 144600 this is a test
3051 You can credit someone else by saying:-
3054 DX by G1TLH FR0G 144.600 he isn't on the cluster
3058 The <freq> is compared against the available bands set up in the clus-
3059 ter. See SHOW/BANDS for more information.
3061 10.56. echo <line> (0)
3063 echo <line> Echo the line to the output
3065 This command is useful in scripts and so forth for printing theline
3066 that you give to the command to the output. You can use thisin
3067 user_default scripts and the SAVE command for titling and so forthThe
3068 script will interpret certain standard "escape" sequences as follows:-
3071 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
3075 So the following example:-
3078 echo GB7DJK is a dxcluster
3085 GB7DJK is a dxcluster
3089 on the output. You don't need a \n on the end of the line you want to
3090 send.A more complex example:-
3093 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
3100 GB7DJK g1tlh Dirk g3xvf Richard
3106 10.57. export <msgno> <filename> (9)
3108 export <msgno> <filename> Export a message to a file
3110 Export a message to a file. This command can only be executed on a
3111 localconsole with a fully privileged user. The file produced will be
3112 in a formready to be imported back into the cluster by placing it in
3113 the import directory (/spider/msg/import).This command cannot
3114 overwrite an existing file. This is to provide some measure of
3115 security. Any files written will owned by the same user as the main
3116 cluster, otherwise you can put the new files anywhere the cluster
3117 canaccess. For example:-
3124 10.58. export_users [<filename>] (9)
3126 export_users [<filename>] Export the users database to ascii
3128 Export the users database to a file in ascii format. If no filenameis
3129 given then it will export the file to /spider/data/user_asc.If the
3130 file already exists it will be renamed to <filename>.o. In factup to 5
3131 generations of the file can be kept each one with an extra 'o' on
3132 thesuffix. BE WARNED: this will write to any file you have write
3133 access to. No check ismade on the filename (if any) that you specify.
3135 10.59. filtering... (0)
3137 filtering... Filtering things in DXSpider
3139 There are a number of things you can filter in the DXSpider system.
3140 Theyall use the same general mechanism.In general terms you can create
3141 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
3142 You do this using, for example:-
3145 accept/spots ..... reject/spots .....
3149 where ..... are the specific commands for that type of filter. There-
3150 are filters for spots, wwv, announce, wcy and (for sysops)connects.
3151 See each different accept or reject command reference formore
3152 details.There is also a command to clear out one or more lines in a
3153 filter andone to show you what you have set. They are:-
3156 clear/spots 1 clear/spots all
3167 There is clear/xxxx command for each type of filter.For now we are
3168 going to use spots for the examples, but you can applythe principles
3169 to all types of filter.There are two main types of filter 'accept' or
3170 'reject'; which you usedepends entirely on how you look at the world
3171 and what is leastwriting to achieve what you want. Each filter has 10
3172 lines (of anylength) which are tried in order. If a line matches then
3173 the actionyou have specified is taken (ie reject means ignore it and
3174 acceptmeans gimme it).The important thing to remember is that if you
3175 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
3176 instance)) then ifa spot comes in that doesn't match any of the lines
3177 then you will getit BUT if you specify an 'accept' filter then any
3178 spots that don'tmatch are dumped. For example if I have a one line
3182 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3186 then automatically you will ONLY get VHF spots from or to CQ zones
3187 1415 and 16. If you set a reject filter like:
3190 reject/spots on hf/cw
3194 Then you will get everything EXCEPT HF CW spots, If you am interested
3195 in IOTAand will work it even on CW then you could say:-
3198 reject/spots on hf/cw and not info iota
3202 But in that case you might only be interested in iota and say:-
3205 accept/spots not on hf/cw or info iota
3209 which is exactly the same. You should choose one or the other untilyou
3210 are confortable with the way it works. Yes, you can mix them(actually
3211 you can have an accept AND a reject on the same line) butdon't try
3212 this at home until you can analyse the results that you getwithout
3213 ringing up the sysop for help.Another useful addition now is filtering
3215 accept/spots by_state VA,NH,RI,ME
3219 You can arrange your filter lines into logical units, either for
3220 yourown understanding or simply convenience. I have one set fre-
3224 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
3228 What this does is to ignore all HF CW spots (being a class B I
3229 can'tread any CW and couldn't possibly be interested in HF :-) and
3230 alsorejects any spots on VHF which don't either originate or spot
3231 someonein Europe.This is an exmaple where you would use the line num-
3232 ber (1 and 2 inthis case), if you leave the digit out, the system
3233 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
3234 out if you want, it is implied. You canuse any number of brackets to
3235 make the 'expression' as you wantit. There are things called prece-
3236 dence rules working here which meanthat you will NEED brackets in a
3237 situation like line 2 because,without it, will assume:-
3240 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
3244 annoying, but that is the way it is. If you use OR - usebrackets.
3245 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
3246 by_zone'.If you want to alter your filter you can just redefine one or
3247 morelines of it or clear out one line. For example:-
3250 reject/spots 1 on hf/ssb
3261 To remove the filter in its entirty:-
3268 There are similar CLEAR commands for the other filters:-
3271 clear/announce clear/wcy clear/wwv
3275 ADVANCED USERS:-Once you are happy with the results you get, you may
3276 like to experiment. my example that filters hf/cw spots and accepts
3277 vhf/uhf spots from EUcan be written with a mixed filter, eg:
3281 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)
3285 each filter slot actually has a 'reject' slot and an 'accept'slot. The
3286 reject slot is executed BEFORE the accept slot.It was mentioned ear-
3287 lier that after a reject test that doesn't match,the default for fol-
3288 lowing tests is 'accept', the reverse is true for'accept'. In the
3289 example what happens is that the reject is executedfirst, any non
3290 hf/cw spot is passed to the accept line, which letsthru everything
3291 else on HF.The next filter line lets through just VHF/UHF spots from
3294 10.60. forward/latlong <node_call> (8)
3296 forward/latlong <node_call> Send latitude and longitude information to
3299 This command sends all the latitude and longitude information that
3300 yourcluster is holding against callsigns. One advantage of recieving
3301 thisinformation is that more locator information is held by you.
3302 Thismeans that more locators are given on the DX line assuming you
3303 haveSET/DXGRID enabled. This could be a LOT of information though,
3304 soit is not recommended on slow links.
3306 10.61. forward/opernam <call> (1)
3308 forward/opernam <call> Send out information on this <call> to all
3311 This command sends out any information held in the user file which can
3312 be broadcast in PC41 protocol packets. This information is Name, QTH,
3313 Locationand Homenode. PC41s are only sent for the information that is
3318 help The HELP Command
3320 HELP is available for a number of commands. The syntax is:-
3327 Where <cmd> is the name of the command you want help on.All commands
3328 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3329 can be shortened to AN and so on.Look at the APROPOS <string> command
3330 which will search the help databasefor the <string> you specify and
3331 give you a list of likely commandsto look at with HELP.
3333 10.63. init <node> (5)
3335 init <node> Re-initialise a link to an AK1A compatible node
3337 This command attempts to re-initialise a link to a (usually) AK1A
3338 nodethat has got confused, usually by a protocol loop of some kind. It
3339 maywork - but you usually will be better off simply disconnecting it
3340 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3341 <yournode>).Best of luck - you will need it.
3343 10.64. join <group> (0)
3345 join <group> Join a chat or conference group
3347 JOIN allows you to join a network wide conference group. To join
3348 agroup (called FOC in this case) type:-
3355 See also CHAT, LEAVE, SHOW/CHAT
3361 As a sysop you can kill any message on the system.
3363 10.66. kill <from msgno>-<to msgno> (0)
3365 kill <from msgno>-<to msgno> Delete a range of messages
3368 10.67. kill <from>-<to> (5)
3370 kill <from>-<to> Remove a range of messages from the system
3373 10.68. kill <msgno> [<msgno..] (0)
3375 kill <msgno> [<msgno..] Delete a message from the local system
3378 10.69. kill <msgno> [<msgno> ...] (0)
3380 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3382 You can get rid of any message to or originating from your callsign
3383 using this command. You can remove more than one message at a time.
3385 10.70. kill expunge <msgno> [<msgno..] (6)
3387 kill expunge <msgno> [<msgno..] Expunge a message
3389 Deleting a message using the normal KILL commands only marks that
3390 messagefor deletion. The actual deletion only happens later (usually
3391 two days later).The KILL EXPUNGE command causes the message to be
3392 truly deleted more or lessimmediately.It otherwise is used in the same
3393 way as the KILL command.
3395 10.71. kill from <call> (5)
3397 kill from <call> Remove all messages from a callsign
3400 10.72. kill full <msgno> [<msgno..] (5)
3402 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3404 Delete a message from the local system. You will only be able todelete
3405 messages that you have originated or been sent (unless you arethe
3413 Will delete all the messages that you own between msgnos 1234 and
3421 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3428 will delete all messages to g1tlh.
3435 will delete a message (usually a 'bulletin') from the whole cluster
3436 system. This uses the subject field, so any messages that have exactly
3437 thesame subject will be deleted. Beware!
3439 10.73. kill full <msgno> [<msgno] (5)
3441 kill full <msgno> [<msgno] Remove a message from the entire cluster
3443 Remove this message from the entire cluster system as well as your
3446 10.74. kill to <call> (5)
3448 kill to <call> Remove all messages to a callsign
3451 10.75. kill from <regex> (0)
3453 kill from <regex> Delete messages FROM a callsign or pattern
3456 10.76. kill to <regex> (0)
3458 kill to <regex> Delete messages TO a callsign or pattern
3461 10.77. leave <group> (0)
3463 leave <group> Leave a chat or conference group
3465 LEAVE allows you to leave a network wide conference group. To leave
3466 agroup (called FOC in this case) type:-
3473 See also CHAT, JOIN, SHOW/CHAT
3477 links Show which nodes is physically connected
3479 This is a quick listing that shows which links are connected andsome
3480 information about them. See WHO for a list of all connections.
3482 10.79. load/aliases (9)
3484 load/aliases Reload the command alias table
3486 Reload the /spider/cmd/Aliases file after you have editted it. Youwill
3487 need to do this if you change this file whilst the cluster isrunning
3488 in order for the changes to take effect.
3490 10.80. load/badmsg (9)
3492 load/badmsg Reload the bad msg table
3494 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3495 whilstthe cluster is running. This table contains a number of perl
3496 regular expressions which are searched for in the fields targetted of
3497 each message. If any of them match then that message is immediately
3500 10.81. load/badwords (9)
3502 load/badwords Reload the bad words table
3504 Reload the /spider/data/badwords file if you have changed it manually
3505 whilstthe cluster is running. This file contains a list of words
3506 which, if foundon certain text portions of PC protocol, will cause
3507 those protocol framesto be rejected. It will all put out a message if
3508 any of these words areused on the announce, dx and talk commands. The
3509 words can be one or more on a line, lines starting with '#' are
3512 10.82. load/bands (9)
3514 load/bands Reload the band limits table
3516 Reload the /spider/data/bands.pl file if you have changed it manually
3517 whilstthe cluster is running.
3519 10.83. load/cmd_cache (9)
3521 load/cmd_cache Reload the automatic command cache
3523 Normally, if you change a command file in the cmd or local_cmd tree
3524 itwill automatially be picked up by the cluster program. Sometimes
3525 itcan get confused if you are doing a lot of moving commands about
3526 ordelete a command in the local_cmd tree and want to use the normal
3527 oneagain. Execute this command to reset everything back to the state
3528 itwas just after a cluster restart.
3530 10.84. load/forward (9)
3532 load/forward Reload the msg forwarding routing table
3534 Reload the /spider/msg/forward.pl file if you have changed itmanually
3535 whilst the cluster is running.
3537 10.85. load/keps (5)
3539 load/keps Load new keps data
3543 10.86. load/keps [nn] (5)
3545 load/keps [nn] Load new keps data from message
3547 If there is no message number then reload the current Keps data
3548 fromthe Keps.pm data file. You create this file by running
3551 /spider/perl/convkeps.pl <filename>
3555 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3556 there is a message number, then it will take the message, runcon-
3557 vkeps.pl on it and then load the data, all in one step.These messages
3558 are sent to ALL by GB7DJK (and others) from time to time.
3560 10.87. load/messages (9)
3562 load/messages Reload the system messages file
3564 If you change the /spider/perl/Messages file (usually
3565 whilstfiddling/writing new commands) you can have them take effect
3566 during acluster session by executing this command. You need to do this
3567 if getsomething like :-unknown message 'xxxx' in lang 'en'
3569 10.88. load/prefixes (9)
3571 load/prefixes Reload the prefix table
3573 Reload the /spider/data/prefix_data.pl file if you have changed
3574 itmanually whilst the cluster is running.
3576 10.89. merge <node> [<no spots>/<no wwv>] (5)
3578 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3580 MERGE allows you to bring your spot and wwv database up to date. By
3581 defaultit will request the last 10 spots and 5 WWVs from the node you
3582 select. The node must be connected locally.You can request any number
3583 of spots or wwv and although they will be appendedto your databases
3584 they will not duplicate any that have recently been added (the last 2
3585 days for spots and last month for WWV data).
3587 10.90. msg <cmd> <msgno> [data ... ] (9)
3589 msg <cmd> <msgno> [data ... ] Alter various message parameters
3591 Alter message parameters like To, From, Subject, whether private or
3592 bulletinor return receipt (RR) is required or whether to keep this
3593 message from timingout.
3596 MSG TO <msgno> <call> - change TO callsign to <call> MSG FRom <msgno> <call> - change FROM callsign to <call> MSG PRrivate <msgno> - set private flag MSG NOPRrivate <msgno> - unset private flag MSG RR <msgno> - set RR flag MSG NORR <msgno> - unset RR flag MSG KEep <msgno> - set the keep flag (message won't be deleted ever) MSG NOKEep <msgno> - unset the keep flag MSG SUbject <msgno> <new> - change the subject to <new> MSG WAittime <msgno> - remove any waitting time for this message MSG NOREad <msgno> - mark message as unread MSG REad <msgno> - mark message as read MSG QUeue - queue any outstanding bulletins MSG QUeue 1 - queue any outstanding private messages
3600 You can look at the status of a message by using:-
3607 This will display more information on the message than DIR does.
3609 10.91. pc <call> <text> (8)
3611 pc <call> <text> Send arbitrary text to a connected callsign
3613 Send some arbitrary text to a locally connected callsign. Noprocessing
3614 is done on the text. This command allows you to send PCProtocol to
3615 unstick things if problems arise (messages get stucketc). eg:-
3618 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3625 pc G1TLH Try doing that properly!!!
3629 Send any text you like to the callsign requested. This is used mainly
3630 to sendPC protocol to connected nodes either for testing or to unstick
3631 things. You can also use in the same way as a talk command to a con-
3632 nected user butwithout any processing, added of "from <blah> to <blah"
3635 10.92. ping <node call> (1)
3637 ping <node call> Check the link quality between nodes
3639 This command allows you to send a frame to another cluster node onthe
3640 network and get a return frame. The time it takes to do thisis a good
3641 indication of the quality of the link. The actual timeit takes is
3642 output to the console in seconds.Any visible cluster node can be
3645 10.93. rcmd <node call> <cmd> (1)
3647 rcmd <node call> <cmd> Send a command to another DX Cluster
3649 This command allows you to send nearly any command to another DX
3650 Clusternode that is connected to the system. Whether you get any
3651 output is dependant on a) whether the other system knowsthat the node
3652 callsign of this cluster is in fact a node b) whether theother system
3653 is allowing RCMDs from this node and c) whether you havepermission to
3654 send this command at all.
3658 read Read the next unread personal message addressed to you
3661 10.95. read <msgno> (0)
3663 read <msgno> Read the specified message
3665 You can read any messages that are sent as 'non-personal' and also
3666 anymessage either sent by or sent to your callsign.
3672 As a sysop you may read any message on the system
3677 reject Set a filter to reject something
3679 Create a filter to reject somethingThere are 2 types of filter, accept
3680 and reject. See HELP FILTERING for moreinfo.
3682 10.98. reject/announce <call> [input] [0-9] <pattern> (8)
3684 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3687 This version allows a sysop to set a filter for a callsign as well as
3688 thedefault for nodes and users eg:-
3691 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3695 10.99. reject/announce [0-9] <pattern> (0)
3697 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3700 Create an 'reject this announce' line for a filter. A reject filter
3701 line means that if the announce matches this filter it ispassed onto
3702 the user. See HELP FILTERING for more info. Please read thisto
3703 understand how filters work - it will save a lot of grief later on.You
3704 can use any of the following things in this line:-
3707 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)
3714 rej/ann by_zone 14,15,16 and not by G,M,2
3718 You can use the tag 'all' to reject everything eg:
3725 but this probably for advanced users...
3727 10.100. reject/route <call> [0-9] <pattern> (8)
3729 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3732 Create an 'reject this routing PC Protocol' line for a filter. An
3733 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3734 filter it is NOT passed thru that interface. See HELP FILTERING for
3735 more info. Please read this to understand how filters work - it will
3736 save a lot of grief later on.You can use any of the following things
3740 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
3747 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3751 You can use the tag 'all' to reject everything eg:
3754 rej/route all (equiv to [very] restricted mode)
3758 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3760 10.101. reject/spots <call> [input] [0-9] <pattern> (8)
3762 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3764 This version allows a sysop to set a filter for a callsign as well as
3765 thedefault for nodes and users eg:-
3768 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3772 reject/spot user_default by G,M,2
3776 10.102. reject/spots [0-9] <pattern> (0)
3778 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3780 Create a 'reject this spot' line for a filter. A reject filter line
3781 means that if the spot matches this filter it isdumped (not passed
3782 on). See HELP FILTERING for more info. Please read thisto understand
3783 how filters work - it will save a lot of grief later on.You can use
3784 any of the following things in this line:-
3787 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>
3791 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3795 You can use the tag 'all' to reject everything eg:
3801 but this probably for advanced users...
3803 10.103. reject/wcy <call> [input] [0-9] <pattern> (8)
3805 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3807 This version allows a sysop to set a filter for a callsign as well as
3808 thedefault for nodes and users eg:-
3811 reject/wcy gb7djk all
3815 10.104. reject/wcy [0-9] <pattern> (0)
3817 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3819 It is unlikely that you will want to do this, but if you do then you
3820 canfilter on the following fields:-
3823 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>
3827 There are no examples because WCY Broadcasts only come from one place
3828 andyou either want them or not (see UNSET/WCY if you don't want
3829 them).This command is really provided for future use.See HELP FILTER
3832 10.105. reject/wwv <call> [input] [0-9] <pattern> (8)
3834 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3836 This version allows a sysop to set a filter for a callsign as well as
3837 thedefault for nodes and users eg:-
3840 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3844 reject/wwv user_default by W
3848 10.106. reject/wwv [0-9] <pattern> (0)
3850 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3852 It is unlikely that you will want to do this, but if you do then you
3853 canfilter on the following fields:-
3856 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>
3863 reject/wwv by_zone 14,15,16
3867 is probably the only useful thing to do (which will only show WWV
3868 broadcastsby stations in the US).See HELP FILTER for information.
3872 reply Reply (privately) to the last message that you have read
3875 10.108. reply <msgno> (0)
3877 reply <msgno> Reply (privately) to the specified message
3880 10.109. reply b <msgno> (0)
3882 reply b <msgno> Reply as a Bulletin to the specified message
3885 10.110. reply noprivate <msgno> (0)
3887 reply noprivate <msgno> Reply as a Bulletin to the specified message
3890 10.111. reply rr <msgno> (0)
3892 reply rr <msgno> Reply to the specified message with read receipt
3894 You can reply to a message and the subject will automatically
3895 have"Re:" inserted in front of it, if it isn't already present.You can
3896 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3897 that you can use with the SEND command (see SENDfor further details)
3899 10.112. save [-d -t -a] <filename> "<cmd>" [...] (9)
3901 save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
3903 This sysop only cammand allows you to save the output of one or
3904 morecommands to a file. For example:-
3907 save /spider/packclus/dxstats show/dxstat
3911 will save the output of the normal command "show/dxstat" to the
3912 file"dxstats" in the files area.You can have some extra flags to the
3913 save which will either date stamp or time stamp or both the filename
3917 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002 save -t /tmp/a <cmd> creates /tmp/a_2301Z save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
3921 The -a flag means append to the file instead of overwriting it.You can
3922 have more than one command on the line, to do this you MUSTenclose
3923 each command in double quotes (") eg:-
3926 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
3932 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
3936 You can only write into places that the cluster has permission for
3937 (whichis that of the "sysop" user [which had BETTER NOT BE "root"]),
3938 you will need to create any directories you want to put stuff in
3939 beforehand as well.It is likely that you will want to run these com-
3940 mands in a crontab type situation. You would do that something like:-
3943 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
3947 Note that you still enclose each command with (") characters but you
3948 mustenclose the entire save command in (') characters. Now in fact,
3949 this can be varied if you know what you are doing. See theadmin manual
3952 10.113. send <call> [<call> ...] (0)
3954 send <call> [<call> ...] Send a message to one or more callsigns
3957 10.114. send copy <msgno> <call> (0)
3959 send copy <msgno> <call> Send a copy of a message to someone
3962 10.115. send noprivate <call> (0)
3964 send noprivate <call> Send a message to all stations
3966 All the SEND commands will create a message which will be sent either
3967 toan individual callsign or to one of the 'bulletin' addresses. SEND
3968 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3969 will mark the message as personal and send it to the cluster node
3970 thatthat callsign is connected to. If the <call> you have specified is
3971 in facta known bulletin category on your node (eg: ALL) then the
3972 message shouldautomatically become a bulletin.You can have more than
3973 one callsign in all of the SEND commands.You can have multiple
3974 qualifiers so that you can have for example:-
3977 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3981 which should send a copy of message 123 to G1TLH and G0RDI and you
3982 willreceive a read receipt when they have read the message.SB is an
3983 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3984 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3985 tionally this should be no longer than 29 characters for compatibil-
3986 ity. Most modern clustersoftware should accept more.You will now be
3987 prompted to start entering your text. You finish the message by enter-
3988 ing '/EX' on a new line. For instance:
3991 ... bye then Jim 73 Dirk /ex
3995 If you have started a message and you don't want to keep it then you-
3996 can abandon the message with '/ABORT' on a new line, like:-
3999 line 1 line 2 oh I just can't be bothered with this /abort
4003 If you abort the message it will NOT be sent.When you are entering the
4004 text of your message, most normal output (suchas DX announcements and
4005 so on are suppressed and stored for latter display(upto 20 such lines
4006 are stored, as new ones come along, so the oldestlines are
4007 dropped).Also, you can enter normal commands commands (and get the
4008 output immediately) whilst in the middle of a message. You do this by
4009 typingthe command preceeded by a '/' character on a new line, so:-
4012 /dx g1tlh 144010 strong signal
4016 Will issue a dx annoucement to the rest of the cluster. Also, you can
4017 add the output of a command to your message by preceeding the command
4025 This will show YOU the output from SH/VHFTABLE and also store it in
4026 themessage. You can carry on with the message until you are ready to
4029 10.116. send private <call> (0)
4031 send private <call> Send a personal message
4034 10.117. send rr <call> (0)
4036 send rr <call> Send a message and ask for a read receipt
4039 10.118. set/address <your address> (0)
4041 set/address <your address> Record your postal address
4044 10.119. set/announce (0)
4046 set/announce Allow announce messages to come out on your terminal
4049 10.120. set/anntalk (0)
4051 set/anntalk Allow talk like announce messages on your terminal
4054 10.121. set/arcluster <call> [<call>..] (5)
4056 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
4060 10.122. set/baddx <call>.. (8)
4062 set/baddx <call>.. Stop callsigns in a dx spot being propagated
4065 10.123. set/badnode <call>.. (8)
4067 set/badnode <call>.. Stop spots from this node being propagated
4070 10.124. set/badspotter <call>.. (8)
4072 set/badspotter <call>.. Stop spots from this callsign being propagated
4075 10.125. set/badword <word>.. (8)
4077 set/badword <word>.. Stop things with this word being propagated
4080 10.126. set/bbs <call> [<call>..] (5)
4082 set/bbs <call> [<call>..] Make the callsign a BBS
4085 10.127. set/beep (0)
4087 set/beep Add a beep to DX and other messages on your terminal
4090 10.128. set/clx <call> [<call>..] (5)
4092 set/clx <call> [<call>..] Make the callsign an CLX node
4095 10.129. set/debug <name> (9)
4097 set/debug <name> Add a debug level to the debug set
4102 set/dx Allow DX messages to come out on your terminal
4105 10.131. set/dxcq (0)
4107 set/dxcq Show CQ Zones on the end of DX announcements
4110 10.132. set/dxgrid (0)
4112 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
4115 10.133. set/dxitu (0)
4117 set/dxitu Show ITU Zones on the end of DX announcements
4120 10.134. set/dxnet <call> [<call>..] (5)
4122 set/dxnet <call> [<call>..] Make the callsign an DXNet node
4126 10.135. set/echo (0)
4128 set/echo Make the cluster echo your input
4131 10.136. set/email <email> ... (0)
4133 set/email <email> ... Set email address(es) and forward your personals
4136 10.137. set/here (0)
4138 set/here Tell the system you are present at your terminal
4141 10.138. set/homenode <node> (0)
4143 set/homenode <node> Set your normal cluster callsign
4145 Tell the cluster system where you normally connect to. Any Messages
4146 sentto you will normally find their way there should you not be
4154 10.139. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
4156 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
4159 10.140. set/isolate (9)
4161 set/isolate Isolate a node from the rest of the network
4163 Connect a node to your system in such a way that you are a full
4164 protocolmember of its network and can see all spots on it, but nothing
4165 either leaksout from it nor goes back into from the rest of the nodes
4166 connected to you.You can potentially connect several nodes in this
4169 10.141. set/language <lang> (0)
4171 set/language <lang> Set the language you want to use
4173 You can select the language that you want the cluster to use.
4174 Currentlythe languages available are en (English), de (German), es
4175 (Spanish) and nl (Dutch).
4177 10.142. set/location <lat & long> (0)
4179 set/location <lat & long> Set your latitude and longitude
4182 10.143. set/lockout <call> (9)
4184 set/lockout <call> Stop a callsign connecting to the cluster
4187 10.144. set/logininfo (0)
4189 set/logininfo Inform when a station logs in locally
4191 10.145. set/name <your name> (0)
4193 set/name <your name> Set your name
4195 Tell the system what your name is eg:-
4202 10.146. set/node <call> [<call>..] (5)
4204 set/node <call> [<call>..] Make the callsign an AK1A cluster
4206 Tell the system that the call(s) are to be treated as AK1A cluster
4207 andfed PC Protocol rather normal user commands.
4209 10.147. set/obscount <count> <call> (8)
4211 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
4213 From 1.35 onwards neighbouring nodes are pinged at regular intervals
4214 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
4215 'pump-up'counter which is decremented on every outgoing ping and then
4216 reset tothe 'obscount' value on every incoming ping. The default value
4217 of thisparameter is 2. What this means is that a neighbouring node
4218 will be pinged twice at (default) 300 second intervals and if no reply
4219 has been heard just beforewhat would be the third attempt, that node
4220 is disconnected.If a ping is heard then the obscount is reset to the
4221 full value. Usingdefault values, if a node has not responded to a ping
4222 within 15 minutes,it is disconnected.You can set this parameter
4223 between 1 and 9.It is STRONGLY recommended that you don't change the
4226 10.148. set/page <lines per page> (0)
4228 set/page <lines per page> Set the lines per page
4230 Tell the system how many lines you wish on a page when the number of
4231 lineof output from a command is more than this. The default is 20.
4232 Setting itexplicitly to 0 will disable paging.
4235 SET/PAGE 30 SET/PAGE 0
4239 The setting is stored in your user profile.
4241 10.149. set/password (0)
4243 set/password Set your own password
4245 This command only works for a 'telnet' user (currently). It willonly
4246 work if you have a password already set. This initial passwordcan only
4247 be set by the sysop.When you execute this command it will ask you for
4248 your old password,then ask you to type in your new password twice (to
4249 make sure youget it right). You may or may not see the data echoed on
4250 the screenas you type, depending on the type of telnet client you
4255 10.150. set/password <callsign> <string> (9)
4257 set/password <callsign> <string> Set a users password
4259 The password for a user can only be set by a full sysop. The stringcan
4260 contain any characters. The way this field is used depends on context.
4261 If it is being used inthe SYSOP command context then you are offered 5
4262 random numbers and youhave to supply the corresponding letters. This
4263 is now mainly for ax25connections.If it is being used on incoming
4264 telnet connections then, if a passwordis set or the:
4267 set/var $main::passwdreq = 1
4271 command is executed in the startup script, then a password prompt
4272 isgiven after the normal 'login: ' prompt.
4274 10.151. set/pinginterval <time> <nodecall> (9)
4276 set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes
4278 As from release 1.35 all neighbouring nodes are pinged at regular
4279 intervalsin order to determine the rolling quality of the link and, in
4280 future, toaffect routing decisions. The default interval is 300 secs
4281 or 5 minutes.You can use this command to set a different interval.
4282 Please don't. But if you do the value you enter is treated as minutes
4283 up 30 and secondsfor numbers greater than that.This is used also to
4284 help determine when a link is down at the far end(as certain cluster
4285 software doesn't always notice), see SET/OBSCOUNTfor more
4286 information.If you must change it (and it may be useful for internet
4287 connected nodeson dynamic IP addresses that go away after a set time
4288 of usage) the timecan be specified as:-
4291 5 which if less than 30 is converted to minutes otherwise is taken as the no of seconds between pings. 120s 120 seconds 5m 5 minutes 1h 1 hour
4295 Please be aware that this causes traffic to occur on the link, setting
4296 this value too low may annoy your neighbours beyond the point of
4297 endurance!You can switch this off by setting it to 0.
4299 10.152. set/privilege <n> <call> [<call..] (9)
4301 set/privilege <n> <call> [<call..] Set privilege level on a call
4303 Set the privilege level on a callsign. The privilege levels that
4304 pertainto commands are as default:-
4307 0 - normal user 1 - allow remote nodes normal user RCMDs 5 - various privileged commands (including shutdown, but not disc- connect), the normal level for another node. 8 - more privileged commands (including disconnect) 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS LEVEL.
4311 If you are a sysop and you come in as a normal user on a remote con-
4312 nectionyour privilege will automatically be set to 0.
4314 10.153. set/prompt <string> (0)
4316 set/prompt <string> Set your prompt to <string>
4320 10.154. set/qra <locator> (0)
4322 set/qra <locator> Set your QRA Grid locator
4324 Tell the system what your QRA (or Maidenhead) locator is. If you have
4325 notdone a SET/LOCATION then your latitude and longitude will be set
4326 roughlycorrectly (assuming your locator is correct ;-). For example:-
4333 10.155. set/qth <your qth> (0)
4335 set/qth <your qth> Set your QTH
4337 Tell the system where you are. For example:-
4340 SET/QTH East Dereham, Norfolk
4344 10.156. set/register <call> ... (9)
4346 set/register <call> ... Mark a user as registered
4349 10.157. set/spider <call> [<call>..] (5)
4351 set/spider <call> [<call>..] Make the callsign an DXSpider node
4353 Tell the system that the call(s) are to be treated as DXSpider node
4354 andfed new style DX Protocol rather normal user commands.
4356 10.158. set/sys_location <lat & long> (9)
4358 set/sys_location <lat & long> Set your cluster latitude and longitude
4360 In order to get accurate headings and such like you must tell the
4361 systemwhat your latitude and longitude is. If you have not yet done a
4362 SET/QRAthen this command will set your QRA locator for you. For
4366 SET/LOCATION 52 22 N 0 57 E
4370 10.159. set/sys_qra <locator> (9)
4372 set/sys_qra <locator> Set your cluster QRA Grid locator
4375 10.160. set/talk (0)
4377 set/talk Allow TALK messages to come out on your terminal
4381 10.161. set/usdb <call> <state> <city> (9)
4383 set/usdb <call> <state> <city> add/update a US DB callsign
4385 This command allows you to add or alter a callsign in the US
4386 statedatabase. Use with extreme caution. Anything you do here will
4387 beoverwritten by any weekly updates that affect this callsign
4390 set/usdb g1tlh nh downtown rindge
4394 see also DELETE/USDB
4396 10.162. set/usstate (0)
4398 set/usstate Allow US State info on the end of DX announcements
4403 set/wcy Allow WCY messages to come out on your terminal
4408 set/wwv Allow WWV messages to come out on your terminal
4413 set/wx Allow WX messages to come out on your terminal
4416 10.166. show/baddx (1)
4418 show/baddx Show all the bad dx calls in the system
4420 Display all the bad dx callsigns in the system, see SET/BADDXfor more
4423 10.167. show/badnode (1)
4425 show/badnode Show all the bad nodes in the system
4427 Display all the bad node callsigns in the system, see SET/BADNODEfor
4430 10.168. show/badspotter (1)
4432 show/badspotter Show all the bad spotters in the system
4434 Display all the bad spotter's callsigns in the system, see
4435 SET/BADSPOTTERfor more information.
4437 10.169. show/badword (1)
4439 show/badword Show all the bad words in the system
4441 Display all the bad words in the system, see SET/BADWORDfor more
4446 10.170. show/chat [<group>] [<lines>] (0)
4448 show/chat [<group>] [<lines>] Show any chat or conferencing
4450 This command allows you to see any chat or conferencing that has
4451 occurred whilst you were away. SHOW/CHAT on its own will show data
4452 forall groups. If you use a group name then it will show only chat
4455 10.171. show/configuration [<node>] (0)
4457 show/configuration [<node>] Show all the nodes and users visible
4459 This command allows you to see all the users that can be seenand the
4460 nodes to which they are connected.This command is normally abbreviated
4461 to: sh/cNormally, the list returned will be just for the nodes from
4462 your country (because the list otherwise will be very long).
4469 will produce a complete list of all nodes. BE WARNED: the list that is
4470 returned can be VERY longIt is possible to supply a node or part of a
4471 prefix and you will get a list of the users for that node or list of
4472 nodes starting withthat prefix.
4483 10.172. show/configuration/node (0)
4485 show/configuration/node Show all the nodes connected locally
4487 Show all the nodes connected to this node.
4489 10.173. show/connect (1)
4491 show/connect Show all the active connections
4493 This command shows information on all the active connections known
4494 tothe node. This command gives slightly more information than WHO.
4496 10.174. show/contest <year and month> (0)
4498 show/contest <year and month> Show all the contests for a month
4500 Show all known contests which are maintained at
4501 http://www.sk3bg.se/contest/for a particular month or year. The format
4502 is reasonably flexible.For example:-
4505 SH/CONTEST sep2003 SH/CONTEST 03 march
4509 10.175. show/date [<prefix>|<callsign>] (0)
4511 show/date [<prefix>|<callsign>] Show the local time
4513 This is very nearly the same as SHOW/TIME, the only difference the
4514 formatof the date string if no arguments are given.If no prefixes or
4515 callsigns are given then this command returns the localtime and UTC as
4516 the computer has it right now. If you give some prefixesthen it will
4517 show UTC and UTC + the local offset (not including DST) atthe prefixes
4518 or callsigns that you specify.
4520 10.176. show/db0sdx <callsign> (0)
4522 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
4524 This command queries the DB0SDX QSL server on the internetand returns
4525 any information available for that callsign. This serviceis provided
4526 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
4529 10.177. show/debug (9)
4531 show/debug Show what levels of debug information you are logging
4536 show/dx Interrogate the spot database
4538 If you just type SHOW/DX you will get the last so many spots(sysop
4539 configurable, but usually 10).In addition you can add any number of
4540 these commands in very nearlyany order to the basic SHOW/DX command,
4544 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>
4548 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
4552 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
4556 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
4560 info <text> - any spots containing <text> in the info or remarks
4564 by <call> - any spots spotted by <call> (spotter <call> is the same).
4568 qsl - this automatically looks for any qsl info on the call held in the spot database.
4572 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.
4576 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
4580 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
4584 You can also use this with the 'by' keyword so eg by W dxcc
4592 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
4596 10.179. show/dxcc <prefix> (0)
4598 show/dxcc <prefix> Interrogate the spot database by country
4600 This command takes the <prefix> (which can be a full or partial
4601 callsign if desired), looks up which internal country number it isand
4602 then displays all the spots as per SH/DX for that country.This is now
4603 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
4607 SH/DXCC G SH/DXCC W on 20m iota
4611 This can be done with the SHOW/DX command like this:-
4615 SH/DX dxcc g SH/DX dxcc w on 20m iota
4619 10.180. show/dxqsl <callsign> (0)
4621 show/dxqsl <callsign> Show any QSL info gathered from spots
4623 The node collects information from the comment fields in spots
4624 (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a
4625 database.This command allows you to interrogate that database and if
4626 the callsignis found will display the manager(s) that people have
4627 spotted. This information is NOT reliable, but it is normally
4628 reasonably accurate ifit is spotted enough times.For example:-
4635 You can check the raw input spots yourself with:-
4642 This gives you more background information.
4644 10.181. show/dxstats [days] [date] (0)
4646 show/dxstats [days] [date] Show the DX Statistics
4648 Show the total DX spots for the last <days> no of days (default is
4649 31), starting from a <date> (default: today).
4651 10.182. show/files [<filearea> [<string>]] (0)
4653 show/files [<filearea> [<string>]] List the contents of a filearea
4655 SHOW/FILES on its own will show you a list of the various
4656 fileareasavailable on the system. To see the contents of a particular
4664 where <filearea> is the name of the filearea you want to see the con-
4665 tents of.You can also use shell globbing characters like '*' and '?'
4666 in astring to see a selection of files in a filearea eg:-
4669 SH/FILES bulletins arld*
4673 See also TYPE - to see the contents of a file.
4675 10.183. show/filter (0)
4677 show/filter Show the contents of all the filters you have set
4680 Show the contents of all the filters that are set. This command
4681 displaysall the filters set - for all the various categories.
4683 10.184. show/hfstats [days] [date] (0)
4685 show/hfstats [days] [date] Show the HF DX Statistics
4687 Show the HF DX spots breakdown by band for the last <days> no of days
4688 (default is 31), starting from a <date> (default: today).
4690 10.185. show/hftable [days] [date] [prefix ...] (0)
4692 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4694 Show the HF DX Spotter table for the list of prefixes for the last
4695 <days> no of days (default is 31), starting from a <date> (default:
4696 today).If there are no prefixes then it will show the table for your
4697 country.Remember that some countries have more than one "DXCC country"
4698 in them(eg G :-), to show them (assuming you are not in G already
4699 which isspecially treated in the code) you must list all the relevant
4703 sh/hftable g gm gd gi gj gw gu
4707 Note that the prefixes are converted into country codes so you don't
4708 haveto list all possible prefixes for each country.If you want more or
4709 less days than the default simply include thenumber you require:-
4716 If you want to start at a different day, simply add the date in some
4720 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4724 This will show the stats for your DXCC for that CQWW contest weekend.
4725 You can specify either prefixes or full callsigns (so you can see how
4726 youdid against all your mates). You can also say 'all' which will then
4727 printthe worldwide statistics.
4734 10.186. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4736 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4739 This command shows the hop counts set up for a node. You can
4740 specifywhich category you want to see. If you leave the category out
4741 then all the categories will be listed.
4745 10.187. show/isolate (1)
4747 show/isolate Show list of ISOLATED nodes
4750 10.188. show/lockout <prefix>|all (9)
4752 show/lockout <prefix>|all Show the list of locked out or excluded
4756 10.189. show/log [<callsign>] (8)
4758 show/log [<callsign>] Show excerpts from the system log
4760 This command outputs a short section of the system log. On its ownit
4761 will output a general logfile. With the optional callsign it willshow
4762 output from the log associated with that callsign.
4764 10.190. show/moon [ndays] [<prefix>|<callsign>] (0)
4766 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4768 Show the Moon rise and set times for a (list of) prefixes or
4769 callsigns, together with the azimuth and elevation of the sun
4770 currently at thoselocations.If you don't specify any prefixes or
4771 callsigns, it will show the times foryour QTH (assuming you have set
4772 it with either SET/LOCATION or SET/QRA),together with the current
4773 azimuth and elevation.In addition, it will show the illuminated
4774 fraction of the moons disk.If all else fails it will show the Moonrise
4775 and set times for the nodethat you are connected to. For example:-
4778 SH/MOON SH/MOON G1TLH W5UN
4782 You can also use this command to see into the past or the future, soif
4783 you want to see yesterday's times then do:-
4790 or in three days time:-
4797 Upto 366 days can be checked both in the past and in the future.Please
4798 note that the rise and set times are given as the UT times of rise and
4799 set on the requested UT day.
4801 10.191. show/muf <prefix> [<hours>][long] (0)
4803 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4806 This command allow you to estimate the likelihood of you contactinga
4807 station with the prefix you have specified. The output assumes a
4808 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4809 0.15muV/10dB SINAD)The result predicts the most likely operating
4810 frequencies and signallevels for high frequency (shortwave) radio
4811 propagation paths onspecified days of the year and hours of the day.
4812 It is most useful forpaths between 250 km and 6000 km, but can be used
4813 with reduced accuracyfor paths shorter or longer than this.The command
4814 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4815 predict the MUF given the predicted flux, day of the year,hour of the
4816 day and geographic coordinates of the transmitter andreceiver. This
4817 routine is reasonably accurate for the purposes here,with a claimed
4818 RMS error of 3.8 MHz, but much smaller and less complexthan the
4819 programs used by major shortwave broadcasting organizations,such as
4820 the Voice of America.The command will display some header information
4821 detailing itsassumptions, together with the locations, latitude and
4822 longitudes andbearings. It will then show UTC (UT), local time at the
4823 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4824 the path(Zen) and the likely signal strengths. Then for each frequency
4825 for whichthe system thinks there is a likelihood of a circuit it
4826 prints a value.The value is currently a likely S meter reading based
4827 on the conventional6dB / S point scale. If the value has a '+'
4828 appended it means that it is1/2 an S point stronger. If the value is
4829 preceeded by an 'm' it means thatthere is likely to be much fading and
4830 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4831 will show the next two hours worth of data. Youcan specify anything up
4832 to 24 hours worth of data by appending the no ofhours required after
4833 the prefix. For example:-
4843 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
4847 indicating that you will have weak, fading circuits on top band and
4848 80m but usable signals on 40m (about S3).inputing:-
4855 will get you the above display, but with the next 24 hours worth
4859 SH/MUF W L 24 SH/MUF W 24 Long
4863 Gives you an estimate of the long path propagation characterics.
4864 Itshould be noted that the figures will probably not be very useful,
4865 norterrible accurate, but it is included for completeness.
4867 10.192. show/newconfiguration [<node>] (0)
4869 show/newconfiguration [<node>] Show all the nodes and users visible
4871 This command allows you to see all the users that can be seenand the
4872 nodes to which they are connected. This command produces essentially
4873 the same information as SHOW/CONFIGURATION except that it shows all
4874 the duplication ofany routes that might be present It also uses a
4875 different formatwhich may not take up quite as much space if you don't
4876 have anyloops.BE WARNED: the list that is returned can be VERY long
4877 10.193. show/newconfiguration/node (0)
4879 show/newconfiguration/node Show all the nodes connected locally
4881 Show all the nodes connected to this node in the new format.
4883 10.194. show/node [<callsign> ...] (1)
4885 show/node [<callsign> ...] Show the type and version number of nodes
4887 Show the type and version (if connected) of the nodes specified on
4888 thecommand line. If no callsigns are specified then a sorted list of
4889 allthe non-user callsigns known to the system will be displayed.
4891 10.195. show/prefix <callsign> (0)
4893 show/prefix <callsign> Interrogate the prefix database
4895 This command takes the <callsign> (which can be a full or partial
4896 callsign or a prefix), looks up which internal country number it is
4897 and then displays all the relevant prefixes for that countrytogether
4898 with the internal country no, the CQ and ITU regions. See also
4901 10.196. show/program (5)
4903 show/program Show the locations of all the included program modules
4905 Show the name and location where every program module was load from.
4906 Thisis useful for checking where you think you have loaded a .pm file
4909 10.197. show/qra <lat> <long> (0)
4911 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4913 This is a multipurpose command that allows you either to calculate
4914 thedistance and bearing between two locators or (if only one locator
4915 isgiven on the command line) the distance and beraing from your
4916 stationto the locator. For example:-
4919 SH/QRA IO92QL SH/QRA JN06 IN73
4923 The first example will show the distance and bearing to the locator
4924 fromyourself, the second example will calculate the distance and bear-
4925 ing fromthe first locator to the second. You can use 4 or 6 character
4926 locators.It is also possible to convert a latitude and longitude to a
4927 locator by using this command with a latitude and longitude as an
4928 argument, forexample:-
4931 SH/QRA 52 41 N 0 58 E
4935 10.198. show/qra <locator> [<locator>] (0)
4937 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4941 10.199. show/qrz <callsign> (0)
4943 show/qrz <callsign> Show any callbook details on a callsign
4945 This command queries the QRZ callbook server on the internetand
4946 returns any information available for that callsign. This serviceis
4947 provided for users of this software by http://www.qrz.com See also
4948 SHOW/WM7D for an alternative.
4950 10.200. show/registered [<prefix>] (9)
4952 show/registered [<prefix>] Show the registered users
4955 10.201. show/route <callsign> ... (0)
4957 show/route <callsign> ... Show the route to the callsign
4959 This command allows you to see to which node the callsigns specified
4960 areconnected. It is a sort of inverse sh/config.
4967 10.202. show/satellite <name> [<hours> <interval>] (0)
4969 show/satellite <name> [<hours> <interval>] Show tracking data
4971 Show the tracking data from your location to the satellite of your
4972 choicefrom now on for the next few hours.If you use this command
4973 without a satellite name it will display a listof all the satellites
4974 known currently to the system. If you give a name then you can obtain
4975 tracking data of all the passesthat start and finish 5 degrees below
4976 the horizon. As default it willgive information for the next three
4977 hours for every five minute period.You can alter the number of hours
4978 and the step size, within certain limits. Each pass in a period is
4979 separated with a row of '-----' charactersSo for example:-
4982 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4986 10.203. show/station all [<regex>] (6)
4988 show/station all [<regex>] Show list of users in the system
4991 10.204. show/station [<callsign> ..] (0)
4993 show/station [<callsign> ..] Show information about a callsign
4995 Show the information known about a callsign and whether (and
4996 where)that callsign is connected to the cluster.
5003 If no callsign is given then show the information for yourself.
5005 10.205. show/sun [ndays] [<prefix>|<callsign>] (0)
5007 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
5009 Show the sun rise and set times for a (list of) prefixes or callsigns,
5010 together with the azimuth and elevation of the sun currently at
5011 thoselocations.If you don't specify any prefixes or callsigns, it will
5012 show the times foryour QTH (assuming you have set it with either
5013 SET/LOCATION or SET/QRA),together with the current azimuth and
5014 elevation.If all else fails it will show the sunrise and set times for
5015 the nodethat you are connected to. For example:-
5018 SH/SUN SH/SUN G1TLH K9CW ZS
5022 You can also use this command to see into the past or the future, soif
5023 you want to see yesterday's times then do:-
5030 or in three days time:-
5037 Upto 366 days can be checked both in the past and in the future.Please
5038 note that the rise and set times are given as the UT times of rise and
5039 set on the requested UT day.
5041 10.206. show/time [<prefix>|<callsign>] (0)
5043 show/time [<prefix>|<callsign>] Show the local time
5045 If no prefixes or callsigns are given then this command returns the
5046 localtime and UTC as the computer has it right now. If you give some
5047 prefixesthen it will show UTC and UTC + the local offset (not
5048 including DST) atthe prefixes or callsigns that you specify.
5050 10.207. show/usdb [call ..] (0)
5052 show/usdb [call ..] Show information held on the FCC Call database
5054 Show the City and State of a Callsign held on the FCC database ifhis
5055 is being run on this system, eg:-
5062 10.208. show/vhfstats [days] [date] (0)
5064 show/vhfstats [days] [date] Show the VHF DX Statistics
5066 Show the VHF DX spots breakdown by band for the last <days> no of days
5067 (default is 31), starting from a date (default: today).
5070 10.209. show/vhftable [days] [date] [prefix ...] (0)
5072 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
5074 Show the VHF DX Spotter table for the list of prefixes for the last
5075 <days> no of days (default is 31), starting from a date (default:
5076 today).If there are no prefixes then it will show the table for your
5077 country.Remember that some countries have more than one "DXCC country"
5078 in them(eg G :-), to show them (assuming you are not in G already
5079 which isspecially treated in the code) you must list all the relevant
5083 sh/vhftable g gm gd gi gj gw gu
5087 Note that the prefixes are converted into country codes so you don't
5088 haveto list all possible prefixes for each country.If you want more or
5089 less days than the default simply include thenumber you require:-
5096 If you want to start at a different day, simply add the date in some
5100 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
5104 This will show the stats for your DXCC for that CQWW contest weekend.
5105 You can specify either prefixes or full callsigns (so you can see how
5106 youdid against all your mates). You can also say 'all' which will then
5107 printthe worldwide statistics.
5114 10.210. show/wcy (0)
5116 show/wcy Show last 10 WCY broadcasts
5119 10.211. show/wcy <n> (0)
5121 show/wcy <n> Show last <n> WCY broadcasts
5123 Display the most recent WCY information that has been received by the
5126 10.212. show/wm7d <callsign> (0)
5128 show/wm7d <callsign> Show callbook details on a US callsigns
5130 This command queries the WM7D callbook server on the internetand
5131 returns any information available for that US callsign. This serviceis
5132 provided for users of this software by http://www.wm7d.net.See also
5135 10.213. show/wwv (0)
5137 show/wwv Show last 10 WWV broadcasts
5140 10.214. show/wwv <n> (0)
5142 show/wwv <n> Show last <n> WWV broadcasts
5144 Display the most recent WWV information that has been received by the
5147 10.215. shutdown (5)
5149 shutdown Shutdown the cluster
5151 Shutdown the cluster and disconnect all the users
5153 10.216. spoof <call> <command> (9)
5155 spoof <call> <command> Do a command as though you are another user
5157 This command is provided so that sysops can set a user's parameters
5158 withoutme having to write a special 'sysop' version for every user
5159 command. Itallows you to pretend that you are doing the command as the
5160 user you specify.eg:-
5163 SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
5167 10.217. stat/channel [<callsign>] (5)
5169 stat/channel [<callsign>] Show the status of a channel on the cluster
5171 Show the internal status of the channel object either for the channel
5172 that you are on or else for the callsign that you asked for.Only the
5173 fields that are defined (in perl term) will be displayed.
5175 10.218. stat/db <dbname> (5)
5177 stat/db <dbname> Show the status of a database
5179 Show the internal status of a database descriptor.Depending on your
5180 privilege level you will see more or less information. This command is
5181 unlikely to be of much use to anyone other than a sysop.
5183 10.219. stat/msg (1)
5185 stat/msg Show the status of the message system
5188 10.220. stat/msg <msgno> (1)
5190 stat/msg <msgno> Show the status of a message
5192 This command shows the internal status of a message and includes
5193 informationsuch as to whom it has been forwarded, its size, origin etc
5194 etc.If no message number is given then the status of the message
5195 system is displayed.
5199 10.221. stat/route_node <callsign> (5)
5201 stat/route_node <callsign> Show the data in a Route::Node object
5204 10.222. stat/route_node all (5)
5206 stat/route_node all Show list of all Route::Node objects
5209 10.223. stat/route_user <callsign> (5)
5211 stat/route_user <callsign> Show the data in a Route::User object
5214 10.224. stat/route_user all (5)
5216 stat/route_user all Show list of all Route::User objects
5219 10.225. stat/user [<callsign>] (5)
5221 stat/user [<callsign>] Show the full status of a user
5223 Shows the full contents of a user record including all the secret
5224 flagsand stuff.Only the fields that are defined (in perl term) will be
5229 sysop Regain your privileges if you login remotely
5231 The system automatically reduces your privilege level to that of
5232 anormal user if you login in remotely. This command allows you
5233 toregain your normal privilege level. It uses the normal system:
5234 fivenumbers are returned that are indexes into the character array
5235 that isyour assigned password (see SET/PASSWORD). The indexes start
5236 fromzero.You are expected to return a string which contains the
5237 charactersrequired in the correct order. You may intersperse those
5238 characterswith others to obscure your reply for any watchers. For
5239 example (andthese values are for explanation :-):
5242 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
5249 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
5253 They will all match. If there is no password you will still be
5254 offerednumbers but nothing will happen when you input a string. Any
5255 match iscase sensitive.
5257 10.227. talk <call> > <node> [<text>] (0)
5259 talk <call> > <node> [<text>] Send a text message to another station
5262 Send a short message to any other station that is visible on the
5263 clustersystem. You can send it to anyone you can see with a
5264 SHOW/CONFIGURATION command, they don't have to be connected
5265 locally.The second form of TALK is used when other cluster nodes are
5266 connectedwith restricted information. This usually means that they
5267 don't send the user information usually associated with logging on and
5268 off the cluster.If you know that G3JNB is likely to be present on
5269 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
5270 then you would use thesecond form of the talk message.If you want to
5271 have a ragchew with someone you can leave the text messageout and the
5272 system will go into 'Talk' mode. What this means is that ashort
5273 message is sent to the recipient telling them that you are in
5274 a'Talking' frame of mind and then you just type - everything you send
5275 willgo to the station that you asked for. All the usual announcements,
5276 spots and so on will still come out on yourterminal.If you want to do
5277 something (such as send a spot) you preceed the normal command with a
5281 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
5285 To leave talk mode type:
5292 If you are in 'Talk' mode, there is an extention to the '/' command
5293 whichallows you to send the output to all the people you are talking
5294 to. You do with the '//' command. For example:-
5301 will send the hftable as you have it to all the people you are cur-
5304 10.228. talk <call> [<text>] (0)
5306 talk <call> [<text>] Send a text message to another station
5309 10.229. type <filearea>/<name> (0)
5311 type <filearea>/<name> Look at the contents of a file in one of the
5314 Type out the contents of a file in a filearea. So, for example, in
5315 filearea 'bulletins' you want to look at file 'arld051' you would
5319 TYPE bulletins/arld051
5323 See also SHOW/FILES to see what fileareas are available and a list of
5326 10.230. uncatchup <node call> all|[msgno> ...] (5)
5328 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
5331 When you send messages the fact that you have forwarded it to another
5332 node is remembered so that it isn't sent again. When you have a new
5333 partnernode and you add their callsign to your /spider/msg/forward.pl
5334 file, alloutstanding non-private messages will be forwarded to them.
5335 This may wellbe ALL the non-private messages. You can prevent this by
5336 using these commmands:-
5339 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
5343 and to undo what you have just done:-
5346 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
5350 which will arrange for them to be forward candidates again.Order is
5353 10.231. unset/announce (0)
5355 unset/announce Stop announce messages coming out on your terminal
5358 10.232. unset/anntalk (0)
5360 unset/anntalk Stop talk like announce messages on your terminal
5362 The announce system on legacy cluster nodes is used as a talk
5363 substitute because the network is so poorly connected. If you:
5370 you will suppress several of these announces, you may miss the odd
5371 useful one as well, but you would probably miss them anyway in thewel-
5372 ter of useless ones.
5379 allows you to see them again. This is the default.
5381 10.233. unset/baddx <call>.. (8)
5383 unset/baddx <call>.. Propagate a dx spot with this callsign again
5385 Setting a word as 'baddx' will prevent spots with that word in
5386 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
5387 anyfurther. They will not be displayed and they will not be sent
5388 ontoother nodes.The word must be written in full, no wild cards are
5392 set/baddx FORSALE VIDEO FR0G
5396 To allow a word again, use the following command ...
5403 10.234. unset/badnode <call>.. (8)
5405 unset/badnode <call>.. Allow spots from this node again
5407 Setting a callsign as a 'badnode' will prevent spots from that node
5408 going any further. They will not be displayed and they will not be
5409 sent onto other nodes.The call must be a full eg:-
5416 will stop anything from K1TTT. If you want SSIDs as well then you mus-
5417 tenter them specifically.
5424 will allow spots from him again.Use with extreme care. This command
5425 may well be superceeded by FILTERing.
5427 10.235. unset/badspotter <call>.. (8)
5429 unset/badspotter <call>.. Allow spots from this callsign again
5431 Setting a callsign as a 'badspotter' will prevent spots from this
5432 callsign going any further. They will not be displayed and they will
5433 not be sent onto other nodes.The call must be written in full, no wild
5434 cards are allowed eg:-
5437 set/badspotter VE2STN
5441 will stop anything from VE2STN. This command will automaticallystop
5442 spots from this user, regardless of whether or which SSID he uses. DO
5443 NOT USE SSIDs in the callsign, just use the callsignas above or below.
5446 unset/badspotter VE2STN
5450 will allow spots from him again.Use with extreme care. This command
5451 may well be superceded by FILTERing.
5453 10.236. unset/badword <word>.. (8)
5455 unset/badword <word>.. Propagate things with this word again
5457 Setting a word as a 'badword' will prevent things like spots,announces
5458 or talks with this word in the the text part from going anyfurther.
5459 They will not be displayed and they will not be sent ontoother
5460 nodes.The word must be written in full, no wild cards are allowed eg:-
5461 set/badword annihilate annihilated annihilation
5465 will stop anything with these words in the text.
5468 unset/badword annihilated
5472 will allow text with this word again.
5474 10.237. unset/beep (0)
5476 unset/beep Stop beeps for DX and other messages on your terminal
5479 10.238. unset/debug <name> (9)
5481 unset/debug <name> Remove a debug level from the debug set
5483 You can choose to log several different levels. The levels are
5486 chan state msg cron connect
5490 You can show what levels you are logging with SHOW/DEBUG
5492 10.239. unset/dx (0)
5494 unset/dx Stop DX messages coming out on your terminal
5497 10.240. unset/dxcq (0)
5499 unset/dxcq Stop CQ Zones on the end of DX announcements
5501 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
5502 announcement (there is just enough room). Some user programscannot
5503 cope with this. The Spotter's CQ is on the RHS of the time, the
5504 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
5505 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5508 10.241. unset/dxgrid (0)
5510 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
5512 A standard feature which is enabled in version 1.43 and above is that
5513 if the spotter's grid square is known it is output on the endof a DX
5514 announcement (there is just enough room). Some user programscannot
5515 cope with this. You can use this command to reset (or set)this
5516 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
5517 flags you have set if you are confused.
5519 10.242. unset/dxitu (0)
5521 unset/dxitu Stop ITU Zones on the end of DX announcements
5523 Display both the Spotter's and the Spotted's ITU Zone on the endof a
5524 DX announcement (there is just enough room). Some user programscannot
5525 cope with this. The Spotter's ITU is on the RHS of the time, the
5526 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
5527 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5530 10.243. unset/echo (0)
5532 unset/echo Stop the cluster echoing your input
5534 If you are connected via a telnet session, different implimentationsof
5535 telnet handle echo differently depending on whether you are connected
5536 via port 23 or some other port. You can use this commandto change the
5537 setting appropriately. The setting is stored in your user profile.YOU
5538 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
5540 10.244. unset/email (0)
5542 unset/email Stop personal msgs being forwarded by email
5544 If any personal messages come in for your callsign then you can
5545 usethese commands to control whether they are forwarded onto your
5546 emailaddress. To enable the forwarding do something like:-
5549 SET/EMAIL mike.tubby@somewhere.com
5553 You can have more than one email address (each one separated by a
5554 space).Emails are forwarded to all the email addresses you specify.You
5555 can disable forwarding by:-
5562 10.245. unset/here (0)
5564 unset/here Tell the system you are absent from your terminal
5567 10.246. unset/hops <call> ann|spots|route|wwv|wcy (8)
5569 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
5571 Set the hop count for a particular type of broadcast for a node.This
5572 command allows you to set up special hop counts for a node for
5573 currently: announce, spots, wwv and wcy broadcasts.eg:
5576 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
5580 Set SHOW/HOPS for information on what is already set. This commandcre-
5581 ates a filter and works in conjunction with the filter system. You can
5582 unset the hops with command UNSET/HOPS. For example:-
5585 unset/hops gb7djk ann unset/hops gb7mbc spots
5589 10.247. unset/isolate (9)
5591 unset/isolate Stop Isolation of a node from the rest of the network
5593 Remove isolation from a node - SET/ISOLATE
5595 10.248. unset/lockout <call> (9)
5597 unset/lockout <call> Allow a callsign to connect to the cluster
5600 10.249. unset/logininfo (0)
5602 unset/logininfo Inform when a station logs out locally
5605 10.250. unset/password <call> ... (9)
5607 unset/password <call> ... Delete (remove) a user's password
5609 This command allows the sysop to completely delete and remove a
5610 password for a user.
5612 10.251. unset/privilege (0)
5614 unset/privilege Remove any privilege for this session
5616 You can use this command to 'protect' this session from
5617 unauthoriseduse. If you want to get your normal privilege back you
5618 will need toeither logout and login again (if you are on a console) or
5619 use theSYSOP command.
5621 10.252. unset/prompt (0)
5623 unset/prompt Set your prompt back to default
5625 This command will set your user prompt to exactly the string that you
5626 say. The point of this command to enable a user to interface to
5627 programsthat are looking for a specific prompt (or else you just want
5628 a differentfixed prompt).
5635 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
5638 10.253. unset/register <call> ... (9)
5640 unset/register <call> ... Mark a user as not registered
5642 Registration is a concept that you can switch on by executing the
5645 set/var $main::regreq = 1
5649 command (usually in your startup file)If a user is NOT registered
5650 then, firstly, instead of the normalmotd file (/spider/data/motd)
5651 being sent to the user at startup, theuser is sent the motd_nor file
5652 instead. Secondly, the non registereduser only has READ-ONLY access to
5653 the node. The non-registered usercannot use DX, ANN etc. The only
5654 exception to this is that a non-registered user can TALK orSEND
5655 messages to the sysop.
5657 10.254. unset/talk (0)
5659 unset/talk Stop TALK messages coming out on your terminal
5662 10.255. unset/usstate (0)
5664 unset/usstate Stop US State info on the end of DX announcements
5666 If the spotter's or spotted's US State is known it is output on the
5667 end of a DX announcement (there is just enough room). A spotter's
5668 state will appear on the RHS of the time (like SET/DXGRID) and the
5669 spotted's State will appear on the LHS of thetime field. Any
5670 information found will override any locator information from
5671 SET/DXGRID.Some user programs cannot cope with this. You can use this
5672 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
5673 SET/DXITUDo a STAT/USER to see which flags you have set if you are
5676 10.256. unset/wcy (0)
5678 unset/wcy Stop WCY messages coming out on your terminal
5681 10.257. unset/wwv (0)
5683 unset/wwv Stop WWV messages coming out on your terminal
5686 10.258. unset/wx (0)
5688 unset/wx Stop WX messages coming out on your terminal
5693 who Show who is physically connected
5695 This is a quick listing that shows which callsigns are connected
5696 andwhat sort of connection they have
5698 10.260. wx <text> (0)
5700 wx <text> Send a weather message to local users
5703 10.261. wx full <text> (0)
5705 wx full <text> Send a weather message to all cluster users
5708 10.262. wx sysop <text> (5)
5710 wx sysop <text> Send a weather message to other clusters only
5712 Weather messages can sometimes be useful if you are experiencing an
5713 extremethat may indicate enhanced conditions