1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 March 2003 revision 0.6
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
26 1.13 A DXSpider Filtering Tutorial
30 2.2 Filtering words from text fields in Announce, Talk and DX spots
31 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
40 3.7 Distribution lists
45 5.1 Creating databases
46 5.2 Importing databases
47 5.3 Checking available databases
48 5.4 Looking up databases
49 5.5 Removing databases
51 6. Information, files and useful programs
55 6.4 Other text messages
58 6.7 Updating kepler data
60 6.9 Connecting logging programs
63 8. Web based statistics
69 10.1 CVS from a Linux platform
70 10.2 CVS from a Windows platform
72 10.4 accept/announce <call> [input] [0-9] <pattern> (8)
73 10.5 accept/announce [0-9] <pattern> (0)
74 10.6 accept/route <call> [0-9] <pattern> (8)
75 10.7 accept/spots <call> [input] [0-9] <pattern> (8)
76 10.8 accept/spots [0-9] <pattern> (0)
77 10.9 accept/wcy <call> [input] [0-9] <pattern> (8)
78 10.10 accept/wcy [0-9] <pattern> (0)
79 10.11 accept/wwv <call> [input] [0-9] <pattern> (8)
80 10.12 accept/wwv [0-9] <pattern> (0)
81 10.13 announce <text> (0)
82 10.14 announce full <text> (0)
83 10.15 announce sysop <text> (5)
84 10.16 apropos <string> (0)
85 10.17 blank [<string>] [<nn>] (0)
87 10.19 catchup <node call> all|[<msgno> ...] (5)
88 10.20 chat <group> <text> (0)
89 10.21 clear/announce <callsign> [input] [0-9|all] (8)
90 10.22 clear/announce [1|all] (0)
91 10.23 clear/route <callsign> [input] [0-9|all] (8)
92 10.24 clear/route [1|all] (0)
93 10.25 clear/spots <callsign> [input] [0-9|all] (8)
94 10.26 clear/spots [0-9|all] (0)
95 10.27 clear/wcy <callsign> [input] [0-9|all] (8)
96 10.28 clear/wcy [1|all] (0)
97 10.29 clear/wwv <callsign> [input] [0-9|all] (8)
98 10.30 clear/wwv [1|all] (0)
99 10.31 connect <callsign> (5)
101 10.33 dbcreate <name> (9)
102 10.34 dbcreate <name> chain <name> [<name>..] (9)
103 10.35 dbcreate <name> cmd <dxspider command> (9)
104 10.36 dbcreate <name> remote <node> (9)
105 10.37 dbimport <dbname> <filename> (9)
106 10.38 dbremove <dbname> (9)
107 10.39 dbshow <dbname> <key> (0)
109 10.41 delete/usdb <callsign> ... (9)
110 10.42 delete/user <callsign> ... (9)
111 10.43 demonstrate <call> <command> (9)
113 10.45 directory <from>-<to> (0)
114 10.46 directory <nn> (0)
115 10.47 directory all (0)
116 10.48 directory from <call> (0)
117 10.49 directory new (0)
118 10.50 directory own (0)
119 10.51 directory subject <string> (0)
120 10.52 directory to <call> (0)
122 10.54 disconnect <call> [<call> ...] (8)
123 10.55 dx [by <call>] <freq> <call> <remarks> (0)
124 10.56 echo <line> (0)
125 10.57 export <msgno> <filename> (9)
126 10.58 export_users [<filename>] (9)
127 10.59 filtering... (0)
128 10.60 forward/latlong <node_call> (8)
129 10.61 forward/opernam <call> (1)
131 10.63 init <node> (5)
132 10.64 join <group> (0)
134 10.66 kill <from msgno>-<to msgno> (0)
135 10.67 kill <from>-<to> (5)
136 10.68 kill <msgno> [<msgno..] (0)
137 10.69 kill <msgno> [<msgno> ...] (0)
138 10.70 kill expunge <msgno> [<msgno..] (6)
139 10.71 kill from <call> (5)
140 10.72 kill full <msgno> [<msgno..] (5)
141 10.73 kill full <msgno> [<msgno] (5)
142 10.74 kill to <call> (5)
143 10.75 kill from <regex> (0)
144 10.76 kill to <regex> (0)
145 10.77 leave <group> (0)
147 10.79 load/aliases (9)
148 10.80 load/badmsg (9)
149 10.81 load/badwords (9)
151 10.83 load/cmd_cache (9)
152 10.84 load/forward (9)
154 10.86 load/keps [nn] (5)
155 10.87 load/messages (9)
156 10.88 load/prefixes (9)
157 10.89 merge <node> [<no spots>/<no wwv>] (5)
158 10.90 msg <cmd> <msgno> [data ... ] (9)
159 10.91 pc <call> <text> (8)
160 10.92 ping <node call> (1)
161 10.93 rcmd <node call> <cmd> (1)
163 10.95 read <msgno> (0)
166 10.98 reject/announce <call> [input] [0-9] <pattern> (8)
167 10.99 reject/announce [0-9] <pattern> (0)
168 10.100 reject/route <call> [0-9] <pattern> (8)
169 10.101 reject/spots <call> [input] [0-9] <pattern> (8)
170 10.102 reject/spots [0-9] <pattern> (0)
171 10.103 reject/wcy <call> [input] [0-9] <pattern> (8)
172 10.104 reject/wcy [0-9] <pattern> (0)
173 10.105 reject/wwv <call> [input] [0-9] <pattern> (8)
174 10.106 reject/wwv [0-9] <pattern> (0)
176 10.108 reply <msgno> (0)
177 10.109 reply b <msgno> (0)
178 10.110 reply noprivate <msgno> (0)
179 10.111 reply rr <msgno> (0)
180 10.112 save [-d -t -a] <filename> "<cmd>" [...] (9)
181 10.113 send <call> [<call> ...] (0)
182 10.114 send copy <msgno> <call> (0)
183 10.115 send noprivate <call> (0)
184 10.116 send private <call> (0)
185 10.117 send rr <call> (0)
186 10.118 set/address <your address> (0)
187 10.119 set/announce (0)
188 10.120 set/anntalk (0)
189 10.121 set/arcluster <call> [<call>..] (5)
190 10.122 set/baddx <call>.. (8)
191 10.123 set/badnode <call>.. (8)
192 10.124 set/badspotter <call>.. (8)
193 10.125 set/badword <word>.. (8)
194 10.126 set/bbs <call> [<call>..] (5)
196 10.128 set/clx <call> [<call>..] (5)
197 10.129 set/debug <name> (9)
200 10.132 set/dxgrid (0)
202 10.134 set/dxnet <call> [<call>..] (5)
204 10.136 set/email <email> ... (0)
206 10.138 set/homenode <node> (0)
207 10.139 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
208 10.140 set/isolate (9)
209 10.141 set/language <lang> (0)
210 10.142 set/location <lat & long> (0)
211 10.143 set/lockout <call> (9)
212 10.144 set/logininfo (0)
213 10.145 set/name <your name> (0)
214 10.146 set/node <call> [<call>..] (5)
215 10.147 set/obscount <count> <call> (8)
216 10.148 set/page <lines per page> (0)
217 10.149 set/password (0)
218 10.150 set/password <callsign> <string> (9)
219 10.151 set/pinginterval <time> <nodecall> (9)
220 10.152 set/privilege <n> <call> [<call..] (9)
221 10.153 set/prompt <string> (0)
222 10.154 set/qra <locator> (0)
223 10.155 set/qth <your qth> (0)
224 10.156 set/register <call> ... (9)
225 10.157 set/spider <call> [<call>..] (5)
226 10.158 set/sys_location <lat & long> (9)
227 10.159 set/sys_qra <locator> (9)
229 10.161 set/usdb <call> <state> <city> (9)
230 10.162 set/usstate (0)
234 10.166 show/baddx (1)
235 10.167 show/badnode (1)
236 10.168 show/badspotter (1)
237 10.169 show/badword (1)
238 10.170 show/chat [<group>] [<lines>] (0)
239 10.171 show/configuration [<node>] (0)
240 10.172 show/configuration/node (0)
241 10.173 show/connect (1)
242 10.174 show/contest <year and month> (0)
243 10.175 show/date [<prefix>|<callsign>] (0)
244 10.176 show/db0sdx <callsign> (0)
245 10.177 show/debug (9)
247 10.179 show/dxcc <prefix> (0)
248 10.180 show/dxqsl <callsign> (0)
249 10.181 show/dxstats [days] [date] (0)
250 10.182 show/files [<filearea> [<string>]] (0)
251 10.183 show/filter (0)
252 10.184 show/hfstats [days] [date] (0)
253 10.185 show/hftable [days] [date] [prefix ...] (0)
254 10.186 show/hops <call> [ann|spots|route|wcy|wwv] (8)
255 10.187 show/isolate (1)
256 10.188 show/lockout <prefix>|all (9)
257 10.189 show/log [<callsign>] (8)
258 10.190 show/moon [ndays] [<prefix>|<callsign>] (0)
259 10.191 show/muf <prefix> [<hours>][long] (0)
260 10.192 show/newconfiguration [<node>] (0)
261 10.193 show/newconfiguration/node (0)
262 10.194 show/node [<callsign> ...] (1)
263 10.195 show/prefix <callsign> (0)
264 10.196 show/program (5)
265 10.197 show/qra <lat> <long> (0)
266 10.198 show/qra <locator> [<locator>] (0)
267 10.199 show/qrz <callsign> (0)
268 10.200 show/registered [<prefix>] (9)
269 10.201 show/route <callsign> ... (0)
270 10.202 show/satellite <name> [<hours> <interval>] (0)
271 10.203 show/station all [<regex>] (6)
272 10.204 show/station [<callsign> ..] (0)
273 10.205 show/sun [ndays] [<prefix>|<callsign>] (0)
274 10.206 show/time [<prefix>|<callsign>] (0)
275 10.207 show/usdb [call ..] (0)
276 10.208 show/vhfstats [days] [date] (0)
277 10.209 show/vhftable [days] [date] [prefix ...] (0)
279 10.211 show/wcy <n> (0)
280 10.212 show/wm7d <callsign> (0)
282 10.214 show/wwv <n> (0)
284 10.216 spoof <call> <command> (9)
285 10.217 stat/channel [<callsign>] (5)
286 10.218 stat/db <dbname> (5)
288 10.220 stat/msg <msgno> (1)
289 10.221 stat/route_node <callsign> (5)
290 10.222 stat/route_node all (5)
291 10.223 stat/route_user <callsign> (5)
292 10.224 stat/route_user all (5)
293 10.225 stat/user [<callsign>] (5)
295 10.227 talk <call> > <node> [<text>] (0)
296 10.228 talk <call> [<text>] (0)
297 10.229 type <filearea>/<name> (0)
298 10.230 uncatchup <node call> all|[msgno> ...] (5)
299 10.231 unset/announce (0)
300 10.232 unset/anntalk (0)
301 10.233 unset/baddx <call>.. (8)
302 10.234 unset/badnode <call>.. (8)
303 10.235 unset/badspotter <call>.. (8)
304 10.236 unset/badword <word>.. (8)
305 10.237 unset/beep (0)
306 10.238 unset/debug <name> (9)
308 10.240 unset/dxcq (0)
309 10.241 unset/dxgrid (0)
310 10.242 unset/dxitu (0)
311 10.243 unset/echo (0)
312 10.244 unset/email (0)
313 10.245 unset/here (0)
314 10.246 unset/hops <call> ann|spots|route|wwv|wcy (8)
315 10.247 unset/isolate (9)
316 10.248 unset/lockout <call> (9)
317 10.249 unset/logininfo (0)
318 10.250 unset/password <call> ... (9)
319 10.251 unset/privilege (0)
320 10.252 unset/prompt (0)
321 10.253 unset/register <call> ... (9)
322 10.254 unset/talk (0)
323 10.255 unset/usstate (0)
329 10.261 wx full <text> (0)
330 10.262 wx sysop <text> (5)
333 ______________________________________________________________________
335 1. Routing and Filtering
339 From DXSpider version 1.48, major changes were introduced to the way
340 node connections are treated. This is part of an ongoing process to
341 remove problems with loops and to enable talk and other functions to
342 propagate across the whole of the worldwide cluster network. In fact,
343 in a Spider network, it would be useful, perhaps even necessary to
344 have loops. This would give real resilience to the network, meaning
345 that if a link dropped, the information flow would simply come in and
346 go out via a different route. Of course, we do not have a complete
347 network of Spider nodes, there are other programs out there. Some of
348 these do not have any protection from loops. Certainly AK1A does not
349 handle loops well at all. It is therefore necessary to have some form
350 of protection for these nodes.
353 In fact DXSpider has had a simple system for some time which is called
354 isolation. This is similar to what in other systems such as clx, is
355 called passive mode. A more detailed explanation of isolation is given
356 further below. This system is still available and, for simple
357 networks, is probably all that you need.
360 The new functionality introduced in version 1.48 allows filtering the
361 node and user protocol frames on a "per interface" basis. We call this
362 route filtering. This is used instead of isolation.
365 What this really means is that you can control more or less completely
366 which user and node management PC protocol frames pass to each of your
367 partner nodes. You can also limit what comes into your node from your
368 partners. It is even possible to control the settings that your
369 partner node has for the routing information that it sends to you
370 (using the rcmd command).
375 Initially when route filters were being tested we generated a
376 "default" filter. Unfortunately it quickly became apparent that this
377 might suit the UK cluster network but didn't really fit anybody else.
378 However using a default filter is an appropriate thing to do. How, is
379 explained further on.
382 The first thing that you must do is determine whether you need to use
383 route filtering at all. If you are a "normal" node with two or three
384 partners and you arranged in an "official" non-looping tree type
385 network, then you do not need to do route filtering and you will feel
386 a lot better for not getting involved. If you are successfully using
387 isolation then you also probably don't need to use route filtering.
390 To put it simply, you should not mix Isolation and Route Filtering.
391 It will work, of sorts, but you will not get the expected results. If
392 you are using Isolation sucessfully at the moment, do not get involved
393 in Route Filtering unless you have a good supply of aspirin! Once you
394 have started down the road of Route Filtering, do not use Isolation
395 either. Use one or the other, not both.
398 You will only require this functionality if you are "well-connected".
399 What that means is that you are connected to several different parts
400 of (say) the EU cluster and, at the same time, also connected to two
401 or three places in the US which, in turn are connected back to the EU.
402 This is called a "loop" and if you are seriously looped then you need
406 I should at this stage give a little bit of background on filters.
407 All the filters in Spider work in basically the same way. You can
408 either accept or reject various options in order to create the filter
409 rules you wish to achieve. Some filters are user settable, others can
410 only be altered by the sysop. Route filtering can only be done by the
415 Anyway, without further discouragement, let me start the process of
419 1.3. The node_default filter
421 All normal systems should have a default routing filter and it should
422 usually be set to send only the normal, unlooped, view of your
423 "national" network. Here in the UK that means nodes from the UK and
424 Eire, in EU it is more complex as the networks there grew up in a more
429 The generic commands are:-
433 reject/route node_default <filter_option>
437 accept/route node_default <filter_option>
441 where filter_option is one of the following ...
450 channel_dxcc <numbers>
451 channel_itu <numbers>
452 channel_zone <numbers>
456 Please be careful if you alter this setting, it will affect ALL your
457 links! Remember, this is a default filter for node connections, not a
461 For the default routing filter then you have two real choices: either
462 a "national" view or the "safe" option of only your own callsign.
463 Examples of each (for my node: GB7DJK) are:-
467 acc/route node_default call_dxcc 61,38
468 acc/route node_default call gb7djk
472 GB7DJK uses the first of these. The DXCC countries can be obtained
473 from the show/prefix command.
476 The example filters shown control output TO all your partner nodes
477 unless they have a specific filter applied to them (see next section).
480 It is also possible to control the incoming routing information that
481 you are prepared to accept FROM your partner nodes. The reason this is
482 necessary is to make sure that stuff like mail, pings and similar
483 commands a) go down the correct links and b) don't loop around
484 excessively. Again using GB7DJK as an example a typical default input
485 filter would be something like:
489 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
493 What this does is accept node and user information for our national
494 network from nodes that are in our national network, but rejects such
495 information from anyone else. Although it doesn't explicitly say so,
496 by implication, any other node information (not from the UK and Eire)
500 As I imagine it will take a little while to get one's head around all
501 of this you can study the effect of any rules that you try by watching
502 the debug output after having done:-
510 After you have got tired of that, to put it back the way it was:-
518 1.4. General route filtering
520 Exactly the same rules apply for general route filtering. You would
521 use either an accept filter or a reject filter like this ...
525 reject/route <node_call> <filter_option>
529 accept/route <node_call> <filter_option>
533 Here are some examples of route filters ...
537 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
538 rej/route all (equiv to [very] restricted mode)
539 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
540 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
544 In practice you will either be opening the default filter out for a
545 partner by defining a specific filter for that callsign:-
550 acc/route gb7baa input all
554 or restricting it quite a lot, in fact making it very nearly like an
555 isolated node, like this:-
559 acc/route pi4ehv-8 call gb7djk
560 rej/route pi4ehv-8 input call_dxcc 61,38
564 This last example takes everything except UK and Eire from PI4EHV-8
565 but only sends him my local configuration (just a PC19 for GB7DJK and
566 PC16s for my local users).
569 It is possible to write much more complex rules, there are up to 10
570 accept/reject pairs per callsign per filter. For more information see
575 1.5. General filter rules
577 Upto v1.44 it was not possible for the user to set their own filters.
578 From v1.45 though that has all changed. It is now possible to set
579 filters for just about anything you wish. If you have just updated
580 from an older version of DXSpider you will need to update your new
581 filters. You do not need to do anything with your old filters, they
582 will be renamed as you update.
585 There are 3 basic commands involved in setting and manipulating
586 filters. These are accept, reject and clear. First we will look
587 generally at filtering. There are a number of things you can filter in
588 the DXSpider system. They all use the same general mechanism.
591 In general terms you can create a "reject" or an "accept" filter which
592 can have up to 10 lines in it. You do this using, for example ...
601 where ..... are the specific commands for that type of filter. There
602 are filters for spots, wwv, announce, wcy and (for sysops) connects.
603 See each different accept or reject command reference for more
606 There is also a command to clear out one or more lines in a filter.
616 There is clear/xxxx command for each type of filter.
619 and you can check that your filters have worked by the command ...
627 For now we are going to use spots for the examples, but you can apply
628 the same principles to all types of filter.
633 There are two main types of filter, accept or reject. You can use
634 either to achieve the result you want dependent on your own preference
635 and which is more simple to do. It is pointless writing 8 lines of
636 reject filters when 1 accept filter would do the same thing! Each
637 filter has 10 lines (of any length) which are tried in order. If a
638 line matches then the action you have specified is taken (ie reject
639 means ignore it and accept means take it)
642 If you specify reject filters, then any lines that arrive that match
643 the filter will be dumped but all else will be accepted. If you use
644 an accept filter, then ONLY the lines in the filter will be accepted
645 and all else will be dumped. For example if you have a single line
650 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
654 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
656 If you set a reject filter like this ...
660 reject/spots on hf/cw
664 Then you will get everything EXCEPT HF CW spots. You could make this
665 single filter even more flexible. For example, if you are interested
666 in IOTA and will work it even on CW even though normally you are not
667 interested in CW, then you could say ...
671 reject/spots on hf/cw and not info iota
675 But in that case you might only be interested in iota and say:-
679 accept/spots not on hf/cw or info iota
683 which achieves exactly the same thing. You should choose one or the
684 other until you are comfortable with the way it works. You can mix
685 them if you wish (actually you can have an accept AND a reject on the
686 same line) but don't attempt this until you are sure you know what you
690 You can arrange your filter lines into logical units, either for your
691 own understanding or simply convenience. Here is an example ...
695 reject/spots 1 on hf/cw
696 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
700 What this does is to ignore all HF CW spots and also rejects any spots
701 on VHF which don't either originate or spot someone in Europe.
704 This is an example where you would use a line number (1 and 2 in this
705 case), if you leave the digit out, the system assumes '1'. Digits
706 '0'-'9' are available. This make it easier to see just what filters
707 you have set. It also makes it more simple to remove individual
708 filters, during a contest for example.
711 You will notice in the above example that the second line has
712 brackets. Look at the line logically. You can see there are 2
713 separate sections to it. We are saying reject spots that are VHF or
714 above APART from those in zones 14, 15 and 16 (either spotted there or
715 originated there). If you did not have the brackets to separate the 2
716 sections, then Spider would read it logically from the front and see a
717 different expression entirely ...
718 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
722 The simple way to remember this is, if you use OR - use brackets.
723 Whilst we are here CASE is not important. 'And BY_Zone' is just the
724 same as 'and by_zone'.
726 As mentioned earlier, setting several filters can be more flexible
727 than simply setting one complex one. Doing it in this way means that
728 if you want to alter your filter you can just redefine or remove one
729 or more lines of it or one line. For example ...
733 reject/spots 1 on hf/ssb
737 would redefine our earlier example, or
745 To remove all the filter lines in the spot filter ...
755 You can filter in several different ways. The options are listed in
756 the various helpfiles for accept, reject and filter.
761 Sometimes all that is needed is a general rule for node connects.
762 This can be done with a node_default filter. This rule will always be
763 followed, even if the link is isolated, unless another filter is set
764 specifically. Default rules can be set for nodes and users. They can
765 be set for spots, announces, WWV and WCY. They can also be used for
766 hops. An example might look like this ...
770 accept/spot node_default by_zone 14,15,16,20,33
771 set/hops node_default spot 50
775 This filter is for spots only, you could set others for announce, WWV
776 and WCY. This filter would work for ALL nodes unless a specific
777 filter is written to override it for a particular node. You can also
778 set a user_default should you require. It is important to note that
779 default filters should be considered to be "connected". By this I
780 mean that should you override the default filter for spots, you need
781 to add a rule for the hops for spots also.
784 1.9. Advanced filtering
786 Once you are happy with the results you get, you may like to
790 The previous example that filters hf/cw spots and accepts vhf/uhf
791 spots from EU can be written with a mixed filter, for example ...
797 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
801 Note that the first filter has not been specified with a number. This
802 will automatically be assumed to be number 1. In this case, we have
803 said reject all HF spots in the CW section of the bands but accept all
804 others at HF. Also accept anything in VHF and above spotted in or by
805 operators in the zones 14, 15 and 16. Each filter slot actually has a
806 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
810 It was mentioned earlier that after a reject test that doesn't match,
811 the default for following tests is 'accept', the reverse is true for
812 'accept'. In the example what happens is that the reject is executed
813 first, any non hf/cw spot is passed to the accept line, which lets
814 through everything else on HF. The next filter line lets through just
815 VHF/UHF spots from EU.
818 1.10. Basic hop control
820 In /spider/data you will find a file called hop_table.pl. This is the
821 file that controls your hop count settings. It has a set of default
822 hops on the various PC frames and also a set for each node you want to
823 alter the hops for. You may be happy with the default settings of
824 course, but this powerful tool can help to protect and improve the
825 network. The file will look something like this ...
830 # hop table construction
835 # default hopcount to use
838 # some variable hop counts based on message type
849 # the per node hop control thingy
881 Each set of hops is contained within a pair of curly braces and
882 contains a series of PC frame types. PC11 for example is a DX spot.
883 The figures here are not exhaustive but should give you a good idea of
887 SHould any of the nodecalls include an ssid, it is important to wrap
888 the whole call in single quotes, like this ...
903 If you do not do this, you will get errors and the file will not work
907 You can alter this file at any time, including whilst the cluster is
908 running. If you alter the file during runtime, the command load/hops
909 will bring your changes into effect.
912 1.11. Hop Control on Specific Nodes
914 You can set a callsign specific hop count for any of the standard
919 set/hops gb7djk spot 4
920 set/hops node_default route 10
921 set/hops gb7baa wcy 5
925 all work on their specific area of the protocol.
928 The set/hops command overrides any hops that you have set otherwise.
931 You can show what hops have been set using the show/hops command.
934 1.12. Isolating networks
936 It is possible to isolate networks from each other on a "gateway" node
937 using the set/isolate <node_call> command.
940 The effect of this is to partition an isolated network completely from
941 another node connected to your node. Your node will appear on and
942 otherwise behave normally on every network to which you are connected,
943 but data from an isolated network will not cross onto any other
944 network or vice versa. However all the spot, announce and WWV traffic
945 and personal messages will still be handled locally (because you are a
946 real node on all connected networks), that is locally connected users
947 will appear on all networks and will be able to access and receive
948 information from all networks transparently. All routed messages will
949 be sent as normal, so if a user on one network knows that you are a
950 gateway for another network, he can still still send a talk/announce
951 etc message via your node and it will be routed across.
954 If you use isolate on a node connection you will continue to receive
955 all information from the isolated partner, however you will not pass
956 any information back to the isolated node. There are times when you
957 would like to forward only spots across a link (maybe during a contest
958 for example). To do this, isolate the node in the normal way and use
959 an acc/spot >call< all filter to override the isolate.
962 1.13. A DXSpider Filtering Tutorial
964 There is now an excellent primer/tutorial on filtering written by Jim
965 Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
966 suggest you read. You can read it here The DXSpider User Filtering
974 In the /spider/msg directory you will find a file called
975 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
976 original looks something like this ....
980 # the list of regexes for messages that we won't store having
981 # received them (bear in mind that we must receive them fully before
985 # The format of each line is as follows
987 # type source pattern
988 # P/B/F T/F/O/S regex
990 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
991 # source: T - to field, F - from field, O - origin, S - subject
992 # pattern: a perl regex on the field requested
994 # Currently only type B and P msgs are affected by this code.
996 # The list is read from the top down, the first pattern that matches
997 # causes the action to be taken.
999 # The pattern can be undef or 0 in which case it will always be selected
1000 # for the action specified
1011 I think this is fairly self explanatory. It is simply a list of
1012 subject headers that we do not want to pass on to either the users of
1013 the cluster or the other cluster nodes that we are linked to. This is
1014 usually because of rules and regulations pertaining to items for sale
1015 etc in a particular country.
1019 2.2. Filtering words from text fields in Announce, Talk and DX spots
1021 From version 1.48 onwards the interface to this has changed. You can
1022 now use the commands set/badword to add words that you are not
1023 prepared to see on the cluster, unset/badword to allow that word again
1024 and show/badword to list the words that you have set.
1027 If you have a previous /spider/data/badwords, the first time you start
1028 the node, it will read and convert this file to the new commands. The
1029 old style file will then be removed.
1032 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
1035 There are a number of commands that control whether a spot progresses
1036 any further by regarding it as "bad" in some way.
1039 A DX Spot has a number of fields which can be checked to see whether
1040 they contain "bad" values, they are: the DX callsign itself, the
1041 Spotter and the Originating Node.
1044 There are a set of commands which allow the sysop to control whether a
1055 These work in the same as the set/badword command, you can add any
1056 words or callsigns or whatever to the appropriate database. For
1057 example, to stop a spot from a particular node you do:
1061 set/badnode gb7djk gb7dxc
1069 set/badspotter b0mb p1rat nocall
1077 set/baddx video wsjt
1081 You can remove a word using the appropriate unset command
1082 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1083 of show/baddx, show/badspotter and show/badnode.
1088 DXSpider deals seamlessly with standard AK1A type mail. It supports
1089 both personal and bulletin mail and the sysop has additional commands
1090 to ensure that mail gets to where it is meant. DXSpider will send
1091 mail almost immediately, assuming that the target is on line.
1092 However, only one mail message is dealt with at any one time. If a
1093 mail message is already being sent or recieved, then the new message
1094 will be queued until it has finished.
1096 The cluster mail is automatically deleted after 30 days unless the
1097 sysop sets the "keep" flag using the msg command.
1102 Personal mail is sent using the sp command. This is actually the
1103 default method of sending mail and so a simple s for send will do. A
1104 full list of the send commands and options is in the command set
1105 section, so I will not duplicate them here.
1110 Bulletin mail is sent by using the sb command. This is one of the
1111 most common mistakes users make when sending mail. They send a
1112 bulletin mail with s or sp instead of sb and of course the message
1113 never leaves the cluster. This can be rectified by the sysop by using
1117 Bulletin addresses can be set using the Forward.pl file.
1122 DXSpider receives all and any mail sent to it without any alterations
1123 needed in files. Because personal and bulletin mail are treated
1124 differently, there is no need for a list of accepted bulletin
1125 addresses. It is necessary, however, to tell the program which links
1126 accept which bulletins. For example, it is pointless sending
1127 bulletins addresses to "UK" to any links other than UK ones. The file
1128 that does this is called forward.pl and lives in /spider/msg. At
1129 default, like other spider files it is named forward.pl.issue. Rename
1130 it to forward.pl and edit the file to match your requirements. The
1136 # this is an example message forwarding file for the system
1138 # The format of each line is as follows
1140 # type to/from/at pattern action destinations
1141 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1143 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1144 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1145 # pattern: a perl regex on the field requested
1146 # action: I - ignore, F - forward
1147 # destinations: a reference to an array containing node callsigns
1149 # if it is non-private and isn't in here then it won't get forwarded
1151 # Currently only type B msgs are affected by this code.
1153 # The list is read from the top down, the first pattern that matches
1154 # causes the action to be taken.
1156 # The pattern can be undef or 0 in which case it will always be selected
1157 # for the action specified
1159 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1160 # pattern) then it will always be forwarded to every node that doesn't have
1161 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1162 # you allow a new link with this on EVERY bull will be forwarded immediately
1163 # on first connection)
1173 Simply insert a bulletin address and state in the brackets where you
1174 wish that mail to go. For example, you can see here that mail sent to
1175 "UK" will only be sent to the UK links and not to PA4AB-14.
1178 To force the cluster to reread the file use load/forward
1181 NB: If a user tries to send mail to a bulletin address that does not
1182 exist in this file, they will get an error.
1185 3.4. The msg command
1187 The msg command is a very powerful and flexible tool for the sysop.
1188 It allows the sysop to alter to and from fields and make other changes
1189 to manage the cluster mail.
1191 Here is a full list of the various options ...
1195 MSG TO <msgno> <call> - change TO callsign to <call>
1196 MSG FRom <msgno> <call> - change FROM callsign to <call>
1197 MSG PRrivate <msgno> - set private flag
1198 MSG NOPRrivate <msgno> - unset private flag
1199 MSG RR <msgno> - set RR flag
1200 MSG NORR <msgno> - unset RR flag
1201 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1202 MSG NOKEep <msgno> - unset the keep flag
1203 MSG SUbject <msgno> <new> - change the subject to <new>
1204 MSG WAittime <msgno> - remove any waiting time for this message
1205 MSG NOREad <msgno> - mark message as unread
1206 MSG REad <msgno> - mark message as read
1207 MSG QUeue - queue any outstanding bulletins
1208 MSG QUeue 1 - queue any outstanding private messages
1212 These commands are simply typed from within the cluster as the sysop
1218 You can check on a message from within the cluster by using the
1219 command stat/msg. This will give you additional information on the
1220 message number including which nodes have received it, which node it
1221 was received from and when etc. Here is an example of the output of
1226 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1229 Msg Time: 26-Jan-2001 1302Z
1233 Subject: AMSAT 2line KEPS 01025.AMSAT
1235 Got it Nodes: GB7BAA, GB7ADX
1239 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1245 This is described in the section on Other filters so I will not
1249 3.7. Distribution lists
1251 Distribution lists are simply a list of users to send certain types of
1252 mail to. An example of this is mail you only wish to send to other
1253 sysops. In /spider/msg there is a directory called distro. You put
1254 any distibution lists in here. For example, here is a file called
1255 SYSOP.pl that caters for the UK sysops.
1258 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1259 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1260 GB7DXK GB7DXI GB7DXS)
1264 Any mail sent to "sysop" would only be sent to the callsigns in this
1270 Spider provides a simple BBS interface. No input is required from the
1271 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1272 and pushes any required mail to the cluster. No mail can flow from
1273 Spider to the BBS, the interface is one-way.
1276 Please be careful not to flood the cluster network with unnecessary
1277 mail. Make sure you only send mail to the clusters that want it by
1278 using the Forward.pl file very carefully.
1283 From 1.48 onwards it will become increasingly possible to control
1284 DXSpider's operation with scripts of various kinds.
1287 The directory /spider/scripts is where it all happens and is used for
1288 several things. Firstly it contains a file called startup that can be
1289 used to call in any changes to the cluster from the default settings
1290 on startup. This script is executed immediately after all
1291 initialisation of the node is done but before any connections are
1292 possible. Examples of this include how many spots it is possible to
1293 get with the sh/dx command, whether you want registration/passwords to
1294 be permanently on etc. An example file is shown below and is included
1295 in the distribution as startup.issue.
1300 # startup script example
1302 # set maximum no of spots allowed to 100
1303 # set/var $Spot::maxspots = 100
1305 # Set registration on
1306 # set/var $main::reqreg = 1
1309 # set/var $main::passwdreq = 1
1314 As usual, any text behind a # is treated as a comment and not read.
1315 To use this file, simply rename it from startup.issue to startup. In
1316 our example above there are three options. The first option is the
1317 amount of spots that a user can request with the sh/dx command.
1318 Normally the default is to give 10 spots unless the user specifies
1319 more. Without this line enabled, the maximum a user can request is
1320 100 spots. Depending on your link quality you may wish to enable more
1321 or less by specifying the number.
1324 The other 2 options are dealt with more fully in the security section.
1327 Secondly, it is used to store the login scripts for users and nodes.
1328 Currently this can only be done by the sysop but it is envisaged that
1329 eventually users will be able to set their own. An example is
1330 included in the distibution but here is a further example.
1347 The lines in between commands can simply insert a blank line or a
1348 character such as a + sign to make the output easier to read. Simply
1349 create this script with your favourite editor and save it with the
1350 callsign of the user as the filename. Filenames should always be in
1354 Commands can be inserted in the same way for nodes. A node may wish a
1355 series of commands to be issued on login, such as a merge command for
1359 Thirdly, there are 2 default scripts for users and nodes who do not
1360 have a specifically defined script. These are user_default and
1366 Spider allows the creation of local or remote databases. It supports
1367 chained databases, allowing several different databases to be scanned
1368 with one simple command. Importing of databases is limited at present
1369 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1370 database but will expand with time.
1373 5.1. Creating databases
1375 Creating a database could not be more simple. All the commands are
1376 sent from the cluster prompt as the sysop user.
1378 To create a database you use the command dbcreate. It can be used in
1379 3 different ways like so ..
1386 To simply create a database locally, you just tell the command the
1387 name of the database. This does not create the actual database, it
1388 simply defines it to say that it exists.
1392 dbcreate <name> chain <name> [<name>...]
1396 This creates a chained database entry. The first database will be
1397 scanned, then the second, the third etc...
1401 dbcreate <name> remote <name>
1405 This creates a remote entry. the first name field is the database
1406 name at the remote node, then the remote switch, then the actual
1407 node_call of the remote node, for example...
1411 dbcreate buckmaster remote gb7dxc
1415 Remote databases cannot be chained, however, the last database in a
1416 chain can be a remote database.
1419 5.2. Importing databases
1421 The only databases that Spider can currently import are the standard
1422 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1423 This will be added to with time.
1425 To import such a database, first put the file somewhere useful like
1426 /tmp and then issue the following command ...
1430 dbimport oblast /tmp/OBLAST.FUL
1434 This will update the existing local oblast database or create it if it
1438 5.3. Checking available databases
1440 Once a database is created, you will want to check that it has been
1441 added. To do this use the dbavail command. This will output the
1442 available databases. For example ...
1447 DB Name Location Chain
1451 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1455 5.4. Looking up databases
1457 To look for information in a defined database, simply use the dbshow
1458 command, for example ...
1462 dbshow buckmaster G0YLM
1466 will show the information for the callsign G0YLM from the buckmaster
1467 database if it exists. To make things more standard for the users you
1468 can add an entry in the Aliases file so that it looks like a standard
1469 show command like this ...
1473 Now you can simply use show/buckmaster or an abreviation.
1476 5.5. Removing databases
1478 To delete an existing database you use the dbremove command. For
1487 would remove the oblast database and its associated datafile from the
1488 system. There are no warnings or recovery possible from this command.
1489 If you remove a database it ceases to exist and would have to be
1490 created from scratch if you still required it.
1493 6. Information, files and useful programs
1497 One of the more important things a cluster sysop needs to do is to get
1498 information to his users. The simplest way to do this is to have a
1499 banner that is sent to the user on login. This is know as a "message
1500 of the day" or "motd". To set this up, simply create a file in
1501 /spider/data called motd and edit it to say whatever you want. It is
1502 purely a text file and will be sent automatically to anyone logging in
1506 This message of the day file lives in the same directory as the
1507 standard motd file but is only sent to non-registered users. Once
1508 registered they will receive the same message as any other user.
1511 6.3. Downtime message
1513 If for any reason the cluster is down, maybe for upgrade or
1514 maintenance but the machine is still running, a message can be sent to
1515 the user advising them of the fact. This message lives in the
1516 /spider/data directory and is called "offline". Simply create the
1517 file and edit it to say whatever you wish. This file will be sent to
1518 a user attempting to log into the cluster when DXSpider is not
1522 6.4. Other text messages
1524 You can set other text messages to be read by the user if they input
1525 the file name. This could be for news items or maybe information for
1526 new users. To set this up, make a directory under /spider called
1527 packclus. Under this directory you can create files called news or
1528 newuser for example. In fact you can create files with any names you
1529 like. These can be listed by the user with the command ....
1537 They can be read by the user by typing the command ....
1545 If the file they want to read is called news. You could also set an
1546 alias for this in the Alias file to allow them just to type news
1549 You can also store other information in this directory, either
1550 directly or nested under directories. One use for this would be to
1551 store DX bulletins such as the OPDX bulletins. These can be listed
1552 and read by the user. To keep things tidy, make a directory under
1553 /spider/packclus called bulletin. Now copy any OPDX or similar
1554 bulletins into it. These can be listed by the user in the same way as
1555 above using the show/files command with an extension for the bulletin
1556 directory you have just created, like this ....
1564 An example would look like this ....
1567 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1571 You can see that in the files area (basically the packclus directory)
1572 there is a file called news and a directory called bulletin. You can
1573 also see that dates they were created. In the case of the file news,
1574 you can also see the time it was last modified, a good clue as to
1575 whether the file has been updated since you last read it. To read the
1576 file called news you would simply issue the command ....
1584 To look what is in the bulletin directory you issue the command ....
1589 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1590 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1591 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1592 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1593 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1594 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1595 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1596 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1597 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1598 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1599 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1600 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1601 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1602 Press Enter to continue, A to abort (16 lines) >
1606 You can now read any file in this directory using the type command,
1611 type bulletin/opdx391
1612 Ohio/Penn DX Bulletin No. 391
1613 The Ohio/Penn Dx PacketCluster
1617 Editor Tedd Mirgliotta, KB8NW
1618 Provided by BARF-80 BBS Cleveland, Ohio
1619 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1620 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1621 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1622 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1623 Press Enter to continue, A to abort (508 lines) >
1627 The page length will of course depend on what you have it set to!
1630 6.5. The Aliases file
1632 You will find a file in /spider/cmd/ called Aliases. This is the file
1633 that controls what a user gets when issuing a command. It is also
1634 possible to create your own aliases for databases and files you create
1638 You should not alter the original file in /spider/cmd/ but create a
1639 new file with the same name in /spider/local_cmd. This means that any
1640 new Aliases files that is downloaded will not overwrite your self
1641 created Aliases and also that you do not override any new Aliases with
1642 your copy in /spider/local_cmd/. You must remember that any files you
1643 store in /spider/local/ or /spider/local_cmd override the originals if
1644 the same lines are used in both files.
1647 The best way of dealing with all this then is to only put your own
1648 locally created Aliases in the copy in /spider/local_cmd. The example
1649 below is currently in use at GB7MBC.
1654 # Local Aliases File
1661 '^news$', 'type news', 'type',
1664 '^sh\w*/buck$', 'show/qrz', 'show',
1665 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1666 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1667 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1668 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1674 Each alphabetical section should be preceded by the initial letter and
1675 the section should be wrapped in square brackets as you can see. The
1676 syntax is straightforward. The first section on each line is the new
1677 command that will be allowed once the alias is included. The second
1678 section is the command it is replacing and the last section is the
1679 actual command that is being used.
1682 The eagle-eyed amongst you will have noticed that in the first
1683 section, the new alias command has a '^' at the start and a '$' at the
1684 end. Basically these force a perfect match on the alias. The '^'
1685 says match the beginning exactly and the with similar commands.
1688 I have 3 different types of alias in this file. At the top is an
1689 alias for 'news'. This is a file I have created in the
1690 /spider/packclus/ directory where I can inform users of new
1691 developments or points of interest. In it's initial form a user would
1692 have to use the command type news. The alias allows them to simply
1693 type news to get the info. Second is an alias for the show/qrz
1694 command so that those users used to the original show/buck command in
1695 AK1A will not get an error, and the rest of the lines are for locally
1696 created databases so that a user can type show/hftest instead of
1697 having to use the command dbshow hftest which is not as intuitive.
1700 This file is just an example and you should edit it to your own
1701 requirements. Once created, simply issue the command load/alias at
1702 the cluster prompt as the sysop user and the aliases should be
1709 In later versions of Spider a simple console program is provided for
1710 the sysop. This has a type ahead buffer with line editing facilities
1711 and colour for spots, announces etc. To use this program, simply use
1712 console.pl instead of client.
1715 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1716 edit the file with your favourite editor.
1719 6.7. Updating kepler data
1721 Spider has a powerful and flexible show/satellite command. In order
1722 for this to be accurate, the kepler data has to be updated regularly.
1723 In general, this data is available as an email or via cluster mail.
1724 Updating it is simple. First you need to export the mail message as a
1725 file. You do this with the export command from the cluster prompt as
1726 the sysop. For example ...
1730 export 5467 /spider/perl/keps.in
1734 would export message number 5467 as a file called keps.in in the
1735 /spider/perl directory.
1738 Now login to a VT as sysop and cd /spider/perl. There is a command in
1739 the perl directory called convkeps.pl. All we need to do now is
1740 convert the file like so ...
1744 ./convkeps.pl keps.in
1748 Now go back to the cluster and issue the command ...
1756 That is it! the kepler data has been updated.
1759 6.8. The QRZ callbook
1761 The command sh/qrz will only work once you have followed a few simple
1762 steps. First you need to get a user ID and password from qrz.com.
1763 Simply go to the site and create one. Secondly you need to copy the
1764 file /spider/perl/Internet.pm to /spider/local and alter it to match
1765 your user ID and password. You also at this point need to set
1766 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1767 proprieter of qrz.com for allowing this access.
1770 6.9. Connecting logging programs
1772 There appear to be very few logging programs out there that support
1773 telnet especially the popular ones like LogEQF, Turbolog etc. This
1774 can make it difficult to connect to your own cluster! The way to do
1775 it is to make the logging program think it has a TNC attached to a com
1776 port on the logging PC and 'push' a linux login out to it. This is
1777 achieved very simply by the use of agetty.
1780 All that is required is to add a line in /etc/inittab to have the
1781 client ready for a connection on the com port of your choice.
1782 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1787 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1791 Add this after the standard runlevel lines in /etc/inittab. The above
1792 line works on ttyS1 (com2). Now as root, issue the command telinit q
1793 and it should be ready for connection. All that is required is a 3
1794 wire serial lead (tx, rx and signal ground). Tell you logging program
1795 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1796 Login as normal and then telnet from there to the cluster.
1801 In the spider tree will be a directory spider-web. This is a neat
1802 little java web applet that can be run from a website. The applet
1803 must run on the same machine as the cluster. The included README file
1807 I should comment here that the applet is precompiled, that is, ready
1808 to go. It was compiled using JDK1.3.1. If your version is earlier
1809 than this then it may not work. Should that be the case you need to
1810 recompile or update your JDK. To recompile do the following ...
1814 cd /spider/spider-web
1816 /usr/bin/javac spiderclient.java
1820 I have used /usr/bin/javac as an example, your path to javac may be
1826 Completely based on a clx web client written in Java by dl6dbh
1827 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1829 The webserver has to run on the same machine as your DxSpider software!
1831 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1833 Installation instructions (Performed as root):
1835 Put all the files in the spider-web directory into a newly created directory
1836 under the DocumentRoot of your websever for instance 'client'. In my case
1837 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1838 path should be /usr/local/httpd/htdocs/client/ for example.
1840 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1841 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1842 /usr/local/httpd/cgi-bin/ for example.
1844 Change the permissions of the files to ensure they are correct, obviously you
1845 will need to use the correct path the the files according to your system:
1847 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1848 chmod -R 755 /home/httpd/html/client/
1850 By default the spider.cgi script should pick up your hostname (As long as this
1851 is set correctly). If it does not or your hostname differs from the name that
1852 you attach to the public address that you are using, then edit spider.cgi :
1854 # Uncomment and set the hostname manually here if the above fails.
1855 # $HOSTNAME = "gb7mbc.spoo.org" ;
1859 telnet (see Listeners.pm)
1861 NOTE: If you can start the console but cannot connect to the cluster from it,
1862 then it is possible that the machine you are on cannot resolve the hostname of
1863 your cluster machine. If this is the case, you need to set your hostname
1866 You also need to set the $NODECALL variable. This prints the name of your
1867 choosing (probably your cluster callsign) on the html page.
1869 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1873 8. Web based statistics
1875 From version 1.50, you can use the freeware software MRTG to produce
1876 really nice graphical statistics on your web site. For an example try
1877 http://www.gb7mbc.net/mrtg/stats.html.
1880 The following should help you get it all working.
1883 First you need to download the latest version of MRTG from
1884 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1885 the following files..
1889 libpng-1.0.14.tar.gz
1895 Login to your machine as the root user, put all the downloaded files
1896 in /usr/local/src/ (or wherever you prefer) and untar and compile
1897 them. All the information to compile and install these sources come
1898 with them. After compilation and installation, you will find MRTG in
1902 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1906 You now need to make 2 symbolic links like below...
1910 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1911 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1915 Now login to the cluster with your sysop callsign and run the command
1919 Now you are nearly there! Login as the sysop user and change to the
1920 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1925 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1929 Changing the callsign for your own cluster callsign of course!
1932 And finally you need to login as the root user and create one last
1933 symbolic link. Where this points will depend on where your html
1934 documents are kept. For RedHat systems you use...
1938 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1942 and for SuSE systems...
1946 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1950 If you now point your browser to your website as below it should all
1955 http://www.xxx.xxx/mrtg/stats.html
1959 Of course, to get the stats to update, you need to add some
1960 information in the spider crontab file as below...
1964 # Update stats for mrtg on website
1965 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1969 This will update the site every 5 minutes.
1974 From version 1.49 DXSpider has some additional security features.
1975 These are not by any means meant to be exhaustive, however they do
1976 afford some security against piracy. These two new features can be
1977 used independently of each other or in concert to tighten the
1983 The basic principle of registration is simple. If a user is not
1984 registered by the sysop, then they have read-only access to the
1985 cluster. The only thing they can actually send is a talk or a message
1986 to the sysop. In order for them to be able to spot, send announces or
1987 talks etc the sysop must register them with the set/register command,
1996 The user g0vgs can now fully use the cluster. In order to enable
1997 registration, you can issue the command ...
1999 set/var $main::reqreg = 1
2003 Any users that are not registered will now see the motd_nor file
2004 rather than the motd file as discussed in the Information, files and
2005 useful programs section.
2008 Entering this line at the prompt will only last for the time the
2009 cluster is running of course and would not be present on a restart.
2010 To make the change permanent, add the above line to
2011 /spider/scripts/startup. To read more on the startup file, see the
2012 section on Information, files and useful programs.
2015 To unregister a user use unset/register and to show the list of
2016 registered users, use the command show/register.
2021 At the moment, passwords only affect users who login to a DXSpider
2022 cluster node via telnet. If a user requires a password, they can
2023 either set it themselves or have the sysop enter it for them by using
2024 the set/password command. Any users who already have passwords, such
2025 as remote sysops, will be asked for their passwords automatically by
2026 the cluster. Using passwords in this way means that the user has a
2027 choice on whether to have a password or not. To force the use of
2028 passwords at login, issue the command ...
2032 set/var $main::passwdreq = 1
2036 at the cluster prompt. This can also be added to the
2037 /spider/scripts/startup file as above to make the change permanent.
2040 Of course, if you do this you will have to assign a password for each
2041 of your users. If you were asking them to register, it is anticipated
2042 that you would ask them to send you a message both to ask to be
2043 registered and to give you the password they wish to use.
2046 Should a user forget their password, it can be reset by the sysop by
2047 first removing the existing password and then setting a new one like
2052 unset/password g0vgs
2053 set/password g0vgs new_password
2061 10.1. CVS from a Linux platform
2063 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2064 is held at Sourceforge. This means that it is possible to update your
2065 DXSpider installation to the latest sources by using a few simple
2066 commands. A graphical interface to CVS for Windows is explained in
2070 Please be aware that if you update your system using CVS, it is
2071 possible that you could be running code that is very beta and not
2072 fully tested. There is a possibility that it could be unstable.
2075 I am of course assuming that you have a machine with both DXSpider and
2076 Internet access running.
2079 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2080 ENTIRE SPIDER TREE!!
2083 Assuming you are connected to the Internet, you need to login to the
2084 CVS repository and then update your Spider source. There are several
2085 steps which are listed below ...
2088 First login as the user sysop. Next you need to connect to the CVS
2089 repository. You do this with the command below ...
2092 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2096 You will get a password prompt. Simply hit return here and your
2097 machine should return to a normal linux prompt.
2100 What happens next depends on whether you have an existing installation
2101 that you want to update with the latest and greatest or whether you
2102 just want to see what is there and/or run it on a new machine for
2105 If you are installing Spider from CVS then change directory to
2108 If you are wanting to update Spider then cd to /tmp
2111 The next step will create a brand new 'spider' directory in your
2115 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2119 This command is all on one line.
2122 Hopefully your screen should show you downloading files. The -z3
2123 simply compresses the download to improve speed. When this has
2124 finished, you will have exactly the same as if you had untarred a full
2125 tarball PLUS some extra directories and files that CVS needs to do the
2127 Now if you are doing a new installation, that's it. Carry on as if
2128 you have just downloaded and untarred the lastest tarball.
2131 If you want to upgrade your current installation then do this ...
2135 tar cvfz /tmp/s.tgz spider
2137 tar xvfzp /tmp/s.tgz
2141 This is assuming you downloaded to the /tmp directory of course.
2144 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2145 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2148 Remember to recompile the C client (cd /spider/src; make)
2151 At this point the files have been upgraded. You can (usually) restart
2152 the cluster in your own time. However, if you attempt to use any new
2153 commands or features expect it to be fatal! At least your cluster
2154 will have been restarted then so it will be too late to worry about
2158 Now the magic part! From now on when you want to update, simply
2159 connect to the Internet and then, as the user sysop ...
2168 and your files will be updated. As above, remember to recompile the
2169 "C" client if it has been updated (CVS will tell you) and restart if
2170 any of the perl scripts have been altered or added, again, CVS will
2174 You will find any changes documented in the /spider/Changes file.
2177 10.2. CVS from a Windows platform
2179 After the initial setup, an update to your DXSpider software is no
2180 more than a couple of clicks away. This section is intended to
2181 explain and illustrate the use of the WinCVS application to update
2182 your DXSpider software. The current stable version of WinCVS is Ver.
2183 1.2. You can get this software at:
2185 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2187 Pick your download mirror and then install WinCVS after the download
2191 In this next section I have included a series of links to .jpg files
2192 to take advantage of the picture and 1000 words equivalency. The .jpg
2193 files are in the C:\spider\html directory. If someone using a Linux
2194 system is reading this section from boredom, the files are in
2195 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2196 of gcvs and do your updates graphically as opposed to from the command
2197 line. The following descriptions are almost identical between WinCvs
2198 and gcvs. The following screen shots have duplicate links, depending
2199 upon whether you are viewing this information under the Windows or
2200 Linux operating system.
2202 When WinCVS is installed, running, and you are connected to the
2203 internet, the initial screen looks like:
2207 If you want, you can also look at these .jpg files with another viewer
2208 that might provide some better clarity to the image. On the left is
2209 the directory tree for your hard disk. Notice that the spider
2210 directory has a gray highlight.
2212 To start configuring WinCVS, click on Admin at the top of the screen
2213 and then Preferences. This should get you:
2217 In the top line for CVSROOT, enter:
2220 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2227 "passwd" file on the cvs server
2231 for Authentication on the General tab.
2233 Next, move to the right to the Ports tab.
2237 In here, check the box on the second line down for the "pserver" port.
2238 Enter a port number of 2401.
2240 Finally, go to the WinCvs tab all the way to the right.
2244 Enter Notepad as the viewer to open files. For the HOME folder, put
2245 "C:\spider" and click OK because the configuration is now complete.
2247 You are now ready to upgrade your copy of DXSpider. Click on the
2248 greyed Spider folder shown in the directory tree on the left of the
2249 WinCVS display. Two things should happen. The Spider folder will be
2250 selected and the greyed-out arrow located just below the word Query in
2251 the top line will turn to solid green.
2253 For anyone using gcvs under Linux, the green arrow is located on the
2254 extreme left of the display, under the word File. A gcvs screen looks
2259 Click on the now green arrow to start the download process. An Update
2260 Settings box will be displayed to which you can simply say OK.
2264 For future reference, the Update Settings box is the place where you
2265 can enter information to revert to a prior version of DXSpider.
2266 Information on reverting to a Before Date is contained in the WinCVS
2269 After a short period of time, a series of file names will scroll by in
2270 the lower pane of the WinCVS window. Eventually you should see
2273 *****CVS exited normally with code 0*****
2277 appear in the lower pane. You're done. The updated files are in
2278 place ready for you to stop and then restart your DXSpider. After the
2279 restart, you're running with the latest version of DXSpider.
2283 To paraphrase from the CVS section... Now the magic part! From now on
2284 when you want to update, simply connect to the Internet and start
2288 Click on the greyed-out Spider directory in the left screen
2289 Click on the green down arrow
2290 Click OK on the Update Settings dialog box
2291 Restart your Spider software
2297 accept Set a filter to accept something
2299 Create a filter to accept somethingThere are 2 types of filter, accept
2300 and reject. See HELP FILTERING for moreinfo.
2302 10.4. accept/announce <call> [input] [0-9] <pattern> (8)
2304 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2307 This version allows a sysop to set a filter for a callsign as well as
2308 thedefault for nodes and users eg:-
2311 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2315 10.5. accept/announce [0-9] <pattern> (0)
2317 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2320 Create an 'accept this announce' line for a filter. An accept filter
2321 line means that if the announce matches this filter it ispassed onto
2322 the user. See HELP FILTERING for more info. Please read thisto
2323 understand how filters work - it will save a lot of grief later on.You
2324 can use any of the following things in this line:-
2327 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)
2334 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)
2348 acc/ann by_state va,nh,ri,nh
2352 You can use the tag 'all' to accept everything eg:
2359 but this probably for advanced users...
2361 10.6. accept/route <call> [0-9] <pattern> (8)
2363 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2366 Create an 'accept this routing PC Protocol' line for a filter. An
2367 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2368 filter it is passed thru that interface. See HELP FILTERING for more
2369 info. Please read thisto understand how filters work - it will save a
2370 lot of grief later on.You can use any of the following things in this
2374 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
2381 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2385 you can now use 'by' as a synonym for 'call' so:
2388 by = call by_dxcc = call_dxcc
2392 and so onYou can use the tag 'all' to accept everything eg:
2399 10.7. accept/spots <call> [input] [0-9] <pattern> (8)
2401 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2403 This version allows a sysop to set a filter for a callsign as well as
2404 thedefault for nodes and users eg:-
2407 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2411 accept/spot user_default by G,M,2
2415 10.8. accept/spots [0-9] <pattern> (0)
2417 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2419 Create an 'accept this spot' line for a filter. An accept filter line
2420 means that if the spot matches this filter it ispassed onto the user.
2421 See HELP FILTERING for more info. Please read thisto understand how
2422 filters work - it will save a lot of grief later on.You can use any of
2423 the following things in this line:-
2426 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>
2430 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2434 You can use the tag 'all' to accept everything, eg:
2444 acc/spots by_state VA,NH,RI,MA,ME
2448 but this probably for advanced users...
2450 10.9. accept/wcy <call> [input] [0-9] <pattern> (8)
2452 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2454 This version allows a sysop to set a filter for a callsign as well as
2455 thedefault for nodes and users eg:-
2458 accept/wcy node_default all set/hops node_default 10
2462 10.10. accept/wcy [0-9] <pattern> (0)
2464 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2466 It is unlikely that you will want to do this, but if you do then you
2467 canfilter on the following fields:-
2470 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>
2474 There are no examples because WCY Broadcasts only come from one place
2475 andyou either want them or not (see UNSET/WCY if you don't want
2476 them).This command is really provided for future use.See HELP FILTER
2479 10.11. accept/wwv <call> [input] [0-9] <pattern> (8)
2481 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2483 This version allows a sysop to set a filter for a callsign as well as
2484 thedefault for nodes and users eg:-
2487 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2491 accept/wwv user_default by W,K
2495 10.12. accept/wwv [0-9] <pattern> (0)
2497 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2499 It is unlikely that you will want to do this, but if you do then you
2500 canfilter on the following fields:-
2503 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>
2510 accept/wwv by_zone 4
2514 is probably the only useful thing to do (which will only show WWV
2515 broadcastsby stations in the US).See HELP FILTER for information.
2517 10.13. announce <text> (0)
2519 announce <text> Send an announcement to LOCAL users only
2521 <text> is the text of the announcement you wish to broadcast
2523 10.14. announce full <text> (0)
2525 announce full <text> Send an announcement cluster wide
2527 This will send your announcement cluster wide
2529 10.15. announce sysop <text> (5)
2531 announce sysop <text> Send an announcement to Sysops only
2534 10.16. apropos <string> (0)
2536 apropos <string> Search help database for <string>
2538 Search the help database for <string> (it isn't case sensitive), and
2539 printthe names of all the commands that may be relevant.
2541 10.17. blank [<string>] [<nn>] (0)
2543 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2545 In its basic form this command prints one or more blank lines. However
2546 ifyou pass it a string it will replicate the string for the width of
2547 the screen (default 80) and then print that one or more times, so:
2554 prints two blank lines
2561 prints a row of - characters once.
2568 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2569 script file and you can print a maximumof 9 lines.
2573 bye Exit from the cluster
2575 This will disconnect you from the cluster
2577 10.19. catchup <node call> all|[<msgno> ...] (5)
2579 catchup <node call> all|[<msgno> ...] Mark a message as sent
2582 10.20. chat <group> <text> (0)
2584 chat <group> <text> Chat or Conference to a group
2586 It is now possible to JOIN a group and have network wide conferencing
2587 to thatgroup. DXSpider does not (and probably will not) implement the
2588 AK1A conference mode as this seems very limiting, is hardly used and
2589 doesn't seemto work too well anyway.This system uses the existing ANN
2590 system and is compatible with both otherDXSpider nodes and AK1A
2591 clusters (they use ANN/<group>). You can be a member of as many
2592 "groups" as you want. To join a group type:-
2595 JOIN FOC (where FOC is the group name)
2599 To leave a group type:-
2606 You can see which groups you are in by typing:-
2613 and you can see whether your mate is in the group, if he connects to
2614 thesame node as you, by typing:-
2621 To send a message to a group type:-
2624 CHAT FOC hello everyone
2631 CH #9000 hello I am back
2634 See also JOIN, LEAVE, SHOW/CHAT
2636 10.21. clear/announce <callsign> [input] [0-9|all] (8)
2638 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2641 A sysop can clear an input or normal output filter for a user or
2642 thenode_default or user_default.
2644 10.22. clear/announce [1|all] (0)
2646 clear/announce [1|all] Clear a announce filter line
2648 This command allows you to clear (remove) a line in a annouce filter
2649 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2652 10.23. clear/route <callsign> [input] [0-9|all] (8)
2654 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2656 A sysop can clear an input or normal output filter for a user or
2657 thenode_default or user_default.
2659 10.24. clear/route [1|all] (0)
2661 clear/route [1|all] Clear a route filter line
2663 This command allows you to clear (remove) a line in a route filter or
2664 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2667 10.25. clear/spots <callsign> [input] [0-9|all] (8)
2669 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2671 A sysop can clear an input or normal output filter for a user or
2672 thenode_default or user_default.
2674 10.26. clear/spots [0-9|all] (0)
2676 clear/spots [0-9|all] Clear a spot filter line
2678 This command allows you to clear (remove) a line in a spot filter or
2679 to remove the whole filter.If you have a filter:-
2682 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2693 you will be left with:-
2696 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2707 the filter will be completely removed.
2709 10.27. clear/wcy <callsign> [input] [0-9|all] (8)
2711 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2713 A sysop can clear an input or normal output filter for a user or
2714 thenode_default or user_default.
2716 10.28. clear/wcy [1|all] (0)
2718 clear/wcy [1|all] Clear a WCY filter line
2720 This command allows you to clear (remove) a line in a WCY filter or to
2721 remove the whole filter.see CLEAR/SPOTS for a more detailed
2724 10.29. clear/wwv <callsign> [input] [0-9|all] (8)
2726 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2728 A sysop can clear an input or normal output filter for a user or
2729 thenode_default or user_default.
2731 10.30. clear/wwv [1|all] (0)
2733 clear/wwv [1|all] Clear a WWV filter line
2735 This command allows you to clear (remove) a line in a WWV filter or to
2736 remove the whole filter.see CLEAR/SPOTS for a more detailed
2739 10.31. connect <callsign> (5)
2741 connect <callsign> Start a connection to another DX Cluster
2743 Start a connection process that will culminate in a new connection to
2744 theDX cluster <callsign>. This process creates a new 'client' process
2745 which willuse the script in /spider/connect/<callsign> to effect the
2746 'chat' exchangenecessary to traverse the network(s) to logon to the
2751 dbavail Show a list of all the Databases in the system
2753 Title says it all really, this command lists all the databases
2754 definedin the system. It is also aliased to SHOW/COMMAND.
2756 10.33. dbcreate <name> (9)
2758 dbcreate <name> Create a database entry
2761 10.34. dbcreate <name> chain <name> [<name>..] (9)
2763 dbcreate <name> chain <name> [<name>..] Create a chained database
2766 10.35. dbcreate <name> cmd <dxspider command> (9)
2768 dbcreate <name> cmd <dxspider command> make a local command available
2771 DBCREATE allows you to define a database in the system. It doesn't
2772 actuallycreate anything, just defines it.The databases that are
2773 created are simple DB_File hash databases, they are therefore already
2774 'indexed'.You can define a local database with the first form of the
2782 You can also chain databases with the addition of the 'chain' keyword.
2783 This will search each database one after the other. A typical example
2787 DBCREATE sdx_qsl chain sql_ad
2791 No checking is done to see if the any of the chained databases exist,
2792 infact it is usually better to do the above staement first then do
2793 each ofthe chained databases.Databases can exist offsite. To define a
2794 database that lives on another node do:
2797 DBCREATE buckmaster remote gb7dxc
2801 Remote databases cannot be chained; however, the last database in a a
2802 chain can be a remote database eg:
2805 DBCREATE qsl chain gb7dxc
2809 To see what databases have been defined do:
2812 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2816 It would be normal for you to add an entry into your local Aliases
2817 fileto allow people to use the 'SHOW/<dbname>' style syntax. So you
2818 wouldneed to add a line like:-
2821 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
2832 to work as they may be used to.You can also make local commands avail-
2833 able as 'pseudo' databases. Youcan therefore make spider special com-
2834 mands available as a database. Iimagine that this will be primarily
2835 useful for remote access from legacy nodes. For example:-
2838 DBCREATE dxqsl cmd show/dxqsl
2842 You also use one of these databases in a chain. This may be useful
2843 locally. See DBIMPORT for the importing of existing AK1A format data
2844 to databases.See DBSHOW for generic database enquiry
2846 10.36. dbcreate <name> remote <node> (9)
2848 dbcreate <name> remote <node> Create a remote database entry
2851 10.37. dbimport <dbname> <filename> (9)
2853 dbimport <dbname> <filename> Import AK1A data into a database
2855 If you want to import or update data in bulk to a database you can
2856 usethis command. It will either create or update entries into an
2857 existingdatabase. For example:-
2860 DBIMPORT oblast /tmp/OBLAST.FUL
2864 will import the standard OBLAST database that comes with AK1A into
2865 theoblast database held locally.
2867 10.38. dbremove <dbname> (9)
2869 dbremove <dbname> Delete a database
2871 DBREMOVE will completely remove a database entry and also delete any
2872 datafile that is associated with it. There is no warning, no comeback,
2873 no safety net. For example:
2880 will remove the oblast database from the system and it will also
2881 removethe associated datafile.I repeat:There is no warning, no come-
2882 back, no safety net.You have been warned.
2884 10.39. dbshow <dbname> <key> (0)
2886 dbshow <dbname> <key> Display an entry, if it exists, in a database
2888 This is the generic user interface to the database to the database
2889 system.It is expected that the sysop will add an entry to the local
2890 Aliases fileso that users can use the more familiar AK1A style of
2898 but if he hasn't and the database really does exist (use DBAVAIL
2899 orSHOW/COMMAND to find out) you can do the same thing with:
2908 debug Set the cluster program into debug mode
2910 Executing this command will only have an effect if you are running the
2911 clusterin debug mode i.e.
2918 It will interrupt the cluster just after the debug command has fin-
2921 10.41. delete/usdb <callsign> ... (9)
2923 delete/usdb <callsign> ... Delete this user from the US State Database
2925 This command will completely remove a one or more callsignsfrom the US
2926 States database.There is NO SECOND CHANCE.It goes without saying that
2927 you should use this command CAREFULLY!Note that these callsign may be
2928 re-instated by any weekly updates from the FCC.
2930 10.42. delete/user <callsign> ... (9)
2932 delete/user <callsign> ... Delete this user from the User Database
2934 This command will completely remove a one or more users from the
2935 database.There is NO SECOND CHANCE.It goes without saying that you
2936 should use this command CAREFULLY!
2938 10.43. demonstrate <call> <command> (9)
2940 demonstrate <call> <command> Demonstrate a command to another user
2942 This command is provided so that sysops can demonstrate commands to
2943 other users. It runs a command as though that user had typed it in
2944 andthen sends the output to that user, together with the command that
2948 DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
2952 Note that this command is similar to SPOOF and will have the same
2953 sideeffects. Commands are run at the privilege of the user which is
2954 beingdemonstrated to.
2956 10.44. directory (0)
2958 directory List messages
2962 10.45. directory <from>-<to> (0)
2964 directory <from>-<to> List messages <from> message <to> message
2966 List the messages in the messages directory.If there is a 'p' one
2967 space after the message number then it is a personal message. If there
2968 is a '-' between the message number and the'p' then this indicates
2969 that the message has been read.You can use shell escape characters
2970 such as '*' and '?' in the <call>fields.You can combine some of the
2971 various directory commands together eg:-
2981 DIR SUBJECT IOTA 200-250
2985 You can abbreviate all the commands to one letter and use ak1a syn-
2989 DIR/T G1* 10 DIR/S QSL 10-100 5
2993 10.46. directory <nn> (0)
2995 directory <nn> List last <nn> messages
2998 10.47. directory all (0)
3000 directory all List all messages
3003 10.48. directory from <call> (0)
3005 directory from <call> List all messages from <call>
3008 10.49. directory new (0)
3010 directory new List all new messages
3013 10.50. directory own (0)
3015 directory own List your own messages
3018 10.51. directory subject <string> (0)
3020 directory subject <string> List all messages with <string> in subject
3023 10.52. directory to <call> (0)
3025 directory to <call> List all messages to <call>
3027 10.53. directory- (5)
3031 Sysops can see all users' messages.
3033 10.54. disconnect <call> [<call> ...] (8)
3035 disconnect <call> [<call> ...] Disconnect a user or cluster
3037 Disconnect any <call> connected locally
3039 10.55. dx [by <call>] <freq> <call> <remarks> (0)
3041 dx [by <call>] <freq> <call> <remarks> Send a DX spot
3043 This is how you send a DX Spot to other users. You can, in fact,
3044 nowenter the <freq> and the <call> either way round.
3047 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
3051 will all give the same result. You can add some remarks to the endof
3052 the command and they will be added to the spot.
3055 DX FR0G 144600 this is a test
3059 You can credit someone else by saying:-
3062 DX by G1TLH FR0G 144.600 he isn't on the cluster
3066 The <freq> is compared against the available bands set up in the clus-
3067 ter. See SHOW/BANDS for more information.
3069 10.56. echo <line> (0)
3071 echo <line> Echo the line to the output
3073 This command is useful in scripts and so forth for printing theline
3074 that you give to the command to the output. You can use thisin
3075 user_default scripts and the SAVE command for titling and so forthThe
3076 script will interpret certain standard "escape" sequences as follows:-
3079 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
3083 So the following example:-
3086 echo GB7DJK is a dxcluster
3093 GB7DJK is a dxcluster
3097 on the output. You don't need a \n on the end of the line you want to
3098 send.A more complex example:-
3101 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
3108 GB7DJK g1tlh Dirk g3xvf Richard
3114 10.57. export <msgno> <filename> (9)
3116 export <msgno> <filename> Export a message to a file
3118 Export a message to a file. This command can only be executed on a
3119 localconsole with a fully privileged user. The file produced will be
3120 in a formready to be imported back into the cluster by placing it in
3121 the import directory (/spider/msg/import).This command cannot
3122 overwrite an existing file. This is to provide some measure of
3123 security. Any files written will owned by the same user as the main
3124 cluster, otherwise you can put the new files anywhere the cluster
3125 canaccess. For example:-
3132 10.58. export_users [<filename>] (9)
3134 export_users [<filename>] Export the users database to ascii
3136 Export the users database to a file in ascii format. If no filenameis
3137 given then it will export the file to /spider/data/user_asc.If the
3138 file already exists it will be renamed to <filename>.o. In factup to 5
3139 generations of the file can be kept each one with an extra 'o' on
3140 thesuffix. BE WARNED: this will write to any file you have write
3141 access to. No check ismade on the filename (if any) that you specify.
3143 10.59. filtering... (0)
3145 filtering... Filtering things in DXSpider
3147 There are a number of things you can filter in the DXSpider system.
3148 Theyall use the same general mechanism.In general terms you can create
3149 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
3150 You do this using, for example:-
3153 accept/spots ..... reject/spots .....
3157 where ..... are the specific commands for that type of filter. There-
3158 are filters for spots, wwv, announce, wcy and (for sysops)connects.
3159 See each different accept or reject command reference formore
3160 details.There is also a command to clear out one or more lines in a
3161 filter andone to show you what you have set. They are:-
3164 clear/spots 1 clear/spots all
3175 There is clear/xxxx command for each type of filter.For now we are
3176 going to use spots for the examples, but you can applythe principles
3177 to all types of filter.There are two main types of filter 'accept' or
3178 'reject'; which you usedepends entirely on how you look at the world
3179 and what is leastwriting to achieve what you want. Each filter has 10
3180 lines (of anylength) which are tried in order. If a line matches then
3181 the actionyou have specified is taken (ie reject means ignore it and
3182 acceptmeans gimme it).The important thing to remember is that if you
3183 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
3184 instance)) then ifa spot comes in that doesn't match any of the lines
3185 then you will getit BUT if you specify an 'accept' filter then any
3186 spots that don'tmatch are dumped. For example if I have a one line
3190 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3194 then automatically you will ONLY get VHF spots from or to CQ zones
3195 1415 and 16. If you set a reject filter like:
3198 reject/spots on hf/cw
3202 Then you will get everything EXCEPT HF CW spots, If you am interested
3203 in IOTAand will work it even on CW then you could say:-
3206 reject/spots on hf/cw and not info iota
3210 But in that case you might only be interested in iota and say:-
3213 accept/spots not on hf/cw or info iota
3217 which is exactly the same. You should choose one or the other untilyou
3218 are confortable with the way it works. Yes, you can mix them(actually
3219 you can have an accept AND a reject on the same line) butdon't try
3220 this at home until you can analyse the results that you getwithout
3221 ringing up the sysop for help.Another useful addition now is filtering
3223 accept/spots by_state VA,NH,RI,ME
3227 You can arrange your filter lines into logical units, either for
3228 yourown understanding or simply convenience. I have one set fre-
3232 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
3236 What this does is to ignore all HF CW spots (being a class B I
3237 can'tread any CW and couldn't possibly be interested in HF :-) and
3238 alsorejects any spots on VHF which don't either originate or spot
3239 someonein Europe.This is an exmaple where you would use the line num-
3240 ber (1 and 2 inthis case), if you leave the digit out, the system
3241 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
3242 out if you want, it is implied. You canuse any number of brackets to
3243 make the 'expression' as you wantit. There are things called prece-
3244 dence rules working here which meanthat you will NEED brackets in a
3245 situation like line 2 because,without it, will assume:-
3248 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
3252 annoying, but that is the way it is. If you use OR - usebrackets.
3253 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
3254 by_zone'.If you want to alter your filter you can just redefine one or
3255 morelines of it or clear out one line. For example:-
3258 reject/spots 1 on hf/ssb
3269 To remove the filter in its entirty:-
3276 There are similar CLEAR commands for the other filters:-
3279 clear/announce clear/wcy clear/wwv
3283 ADVANCED USERS:-Once you are happy with the results you get, you may
3284 like to experiment. my example that filters hf/cw spots and accepts
3285 vhf/uhf spots from EUcan be written with a mixed filter, eg:
3289 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)
3293 each filter slot actually has a 'reject' slot and an 'accept'slot. The
3294 reject slot is executed BEFORE the accept slot.It was mentioned ear-
3295 lier that after a reject test that doesn't match,the default for fol-
3296 lowing tests is 'accept', the reverse is true for'accept'. In the
3297 example what happens is that the reject is executedfirst, any non
3298 hf/cw spot is passed to the accept line, which letsthru everything
3299 else on HF.The next filter line lets through just VHF/UHF spots from
3302 10.60. forward/latlong <node_call> (8)
3304 forward/latlong <node_call> Send latitude and longitude information to
3307 This command sends all the latitude and longitude information that
3308 yourcluster is holding against callsigns. One advantage of recieving
3309 thisinformation is that more locator information is held by you.
3310 Thismeans that more locators are given on the DX line assuming you
3311 haveSET/DXGRID enabled. This could be a LOT of information though,
3312 soit is not recommended on slow links.
3314 10.61. forward/opernam <call> (1)
3316 forward/opernam <call> Send out information on this <call> to all
3319 This command sends out any information held in the user file which can
3320 be broadcast in PC41 protocol packets. This information is Name, QTH,
3321 Locationand Homenode. PC41s are only sent for the information that is
3326 help The HELP Command
3328 HELP is available for a number of commands. The syntax is:-
3335 Where <cmd> is the name of the command you want help on.All commands
3336 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3337 can be shortened to AN and so on.Look at the APROPOS <string> command
3338 which will search the help databasefor the <string> you specify and
3339 give you a list of likely commandsto look at with HELP.
3341 10.63. init <node> (5)
3343 init <node> Re-initialise a link to an AK1A compatible node
3345 This command attempts to re-initialise a link to a (usually) AK1A
3346 nodethat has got confused, usually by a protocol loop of some kind. It
3347 maywork - but you usually will be better off simply disconnecting it
3348 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3349 <yournode>).Best of luck - you will need it.
3351 10.64. join <group> (0)
3353 join <group> Join a chat or conference group
3355 JOIN allows you to join a network wide conference group. To join
3356 agroup (called FOC in this case) type:-
3363 See also CHAT, LEAVE, SHOW/CHAT
3369 As a sysop you can kill any message on the system.
3371 10.66. kill <from msgno>-<to msgno> (0)
3373 kill <from msgno>-<to msgno> Delete a range of messages
3376 10.67. kill <from>-<to> (5)
3378 kill <from>-<to> Remove a range of messages from the system
3381 10.68. kill <msgno> [<msgno..] (0)
3383 kill <msgno> [<msgno..] Delete a message from the local system
3386 10.69. kill <msgno> [<msgno> ...] (0)
3388 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3390 You can get rid of any message to or originating from your callsign
3391 using this command. You can remove more than one message at a time.
3393 10.70. kill expunge <msgno> [<msgno..] (6)
3395 kill expunge <msgno> [<msgno..] Expunge a message
3397 Deleting a message using the normal KILL commands only marks that
3398 messagefor deletion. The actual deletion only happens later (usually
3399 two days later).The KILL EXPUNGE command causes the message to be
3400 truly deleted more or lessimmediately.It otherwise is used in the same
3401 way as the KILL command.
3403 10.71. kill from <call> (5)
3405 kill from <call> Remove all messages from a callsign
3408 10.72. kill full <msgno> [<msgno..] (5)
3410 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3412 Delete a message from the local system. You will only be able todelete
3413 messages that you have originated or been sent (unless you arethe
3421 Will delete all the messages that you own between msgnos 1234 and
3429 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3436 will delete all messages to g1tlh.
3443 will delete a message (usually a 'bulletin') from the whole cluster
3444 system. This uses the subject field, so any messages that have exactly
3445 thesame subject will be deleted. Beware!
3447 10.73. kill full <msgno> [<msgno] (5)
3449 kill full <msgno> [<msgno] Remove a message from the entire cluster
3451 Remove this message from the entire cluster system as well as your
3454 10.74. kill to <call> (5)
3456 kill to <call> Remove all messages to a callsign
3459 10.75. kill from <regex> (0)
3461 kill from <regex> Delete messages FROM a callsign or pattern
3464 10.76. kill to <regex> (0)
3466 kill to <regex> Delete messages TO a callsign or pattern
3469 10.77. leave <group> (0)
3471 leave <group> Leave a chat or conference group
3473 LEAVE allows you to leave a network wide conference group. To leave
3474 agroup (called FOC in this case) type:-
3481 See also CHAT, JOIN, SHOW/CHAT
3485 links Show which nodes is physically connected
3487 This is a quick listing that shows which links are connected andsome
3488 information about them. See WHO for a list of all connections.
3490 10.79. load/aliases (9)
3492 load/aliases Reload the command alias table
3494 Reload the /spider/cmd/Aliases file after you have editted it. Youwill
3495 need to do this if you change this file whilst the cluster isrunning
3496 in order for the changes to take effect.
3498 10.80. load/badmsg (9)
3500 load/badmsg Reload the bad msg table
3502 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3503 whilstthe cluster is running. This table contains a number of perl
3504 regular expressions which are searched for in the fields targetted of
3505 each message. If any of them match then that message is immediately
3508 10.81. load/badwords (9)
3510 load/badwords Reload the bad words table
3512 Reload the /spider/data/badwords file if you have changed it manually
3513 whilstthe cluster is running. This file contains a list of words
3514 which, if foundon certain text portions of PC protocol, will cause
3515 those protocol framesto be rejected. It will all put out a message if
3516 any of these words areused on the announce, dx and talk commands. The
3517 words can be one or more on a line, lines starting with '#' are
3520 10.82. load/bands (9)
3522 load/bands Reload the band limits table
3524 Reload the /spider/data/bands.pl file if you have changed it manually
3525 whilstthe cluster is running.
3527 10.83. load/cmd_cache (9)
3529 load/cmd_cache Reload the automatic command cache
3531 Normally, if you change a command file in the cmd or local_cmd tree
3532 itwill automatially be picked up by the cluster program. Sometimes
3533 itcan get confused if you are doing a lot of moving commands about
3534 ordelete a command in the local_cmd tree and want to use the normal
3535 oneagain. Execute this command to reset everything back to the state
3536 itwas just after a cluster restart.
3538 10.84. load/forward (9)
3540 load/forward Reload the msg forwarding routing table
3542 Reload the /spider/msg/forward.pl file if you have changed itmanually
3543 whilst the cluster is running.
3545 10.85. load/keps (5)
3547 load/keps Load new keps data
3551 10.86. load/keps [nn] (5)
3553 load/keps [nn] Load new keps data from message
3555 If there is no message number then reload the current Keps data
3556 fromthe Keps.pm data file. You create this file by running
3559 /spider/perl/convkeps.pl <filename>
3563 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3564 there is a message number, then it will take the message, runcon-
3565 vkeps.pl on it and then load the data, all in one step.These messages
3566 are sent to ALL by GB7DJK (and others) from time to time.
3568 10.87. load/messages (9)
3570 load/messages Reload the system messages file
3572 If you change the /spider/perl/Messages file (usually
3573 whilstfiddling/writing new commands) you can have them take effect
3574 during acluster session by executing this command. You need to do this
3575 if getsomething like :-unknown message 'xxxx' in lang 'en'
3577 10.88. load/prefixes (9)
3579 load/prefixes Reload the prefix table
3581 Reload the /spider/data/prefix_data.pl file if you have changed
3582 itmanually whilst the cluster is running.
3584 10.89. merge <node> [<no spots>/<no wwv>] (5)
3586 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3588 MERGE allows you to bring your spot and wwv database up to date. By
3589 defaultit will request the last 10 spots and 5 WWVs from the node you
3590 select. The node must be connected locally.You can request any number
3591 of spots or wwv and although they will be appendedto your databases
3592 they will not duplicate any that have recently been added (the last 2
3593 days for spots and last month for WWV data).
3595 10.90. msg <cmd> <msgno> [data ... ] (9)
3597 msg <cmd> <msgno> [data ... ] Alter various message parameters
3599 Alter message parameters like To, From, Subject, whether private or
3600 bulletinor return receipt (RR) is required or whether to keep this
3601 message from timingout.
3604 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
3608 You can look at the status of a message by using:-
3615 This will display more information on the message than DIR does.
3617 10.91. pc <call> <text> (8)
3619 pc <call> <text> Send arbitrary text to a connected callsign
3621 Send some arbitrary text to a locally connected callsign. Noprocessing
3622 is done on the text. This command allows you to send PCProtocol to
3623 unstick things if problems arise (messages get stucketc). eg:-
3626 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3633 pc G1TLH Try doing that properly!!!
3637 Send any text you like to the callsign requested. This is used mainly
3638 to sendPC protocol to connected nodes either for testing or to unstick
3639 things. You can also use in the same way as a talk command to a con-
3640 nected user butwithout any processing, added of "from <blah> to <blah"
3643 10.92. ping <node call> (1)
3645 ping <node call> Check the link quality between nodes
3647 This command allows you to send a frame to another cluster node onthe
3648 network and get a return frame. The time it takes to do thisis a good
3649 indication of the quality of the link. The actual timeit takes is
3650 output to the console in seconds.Any visible cluster node can be
3653 10.93. rcmd <node call> <cmd> (1)
3655 rcmd <node call> <cmd> Send a command to another DX Cluster
3657 This command allows you to send nearly any command to another DX
3658 Clusternode that is connected to the system. Whether you get any
3659 output is dependant on a) whether the other system knowsthat the node
3660 callsign of this cluster is in fact a node b) whether theother system
3661 is allowing RCMDs from this node and c) whether you havepermission to
3662 send this command at all.
3666 read Read the next unread personal message addressed to you
3669 10.95. read <msgno> (0)
3671 read <msgno> Read the specified message
3673 You can read any messages that are sent as 'non-personal' and also
3674 anymessage either sent by or sent to your callsign.
3680 As a sysop you may read any message on the system
3685 reject Set a filter to reject something
3687 Create a filter to reject somethingThere are 2 types of filter, accept
3688 and reject. See HELP FILTERING for moreinfo.
3690 10.98. reject/announce <call> [input] [0-9] <pattern> (8)
3692 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3695 This version allows a sysop to set a filter for a callsign as well as
3696 thedefault for nodes and users eg:-
3699 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3703 10.99. reject/announce [0-9] <pattern> (0)
3705 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3708 Create an 'reject this announce' line for a filter. A reject filter
3709 line means that if the announce matches this filter it ispassed onto
3710 the user. See HELP FILTERING for more info. Please read thisto
3711 understand how filters work - it will save a lot of grief later on.You
3712 can use any of the following things in this line:-
3715 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)
3722 rej/ann by_zone 14,15,16 and not by G,M,2
3726 You can use the tag 'all' to reject everything eg:
3733 but this probably for advanced users...
3735 10.100. reject/route <call> [0-9] <pattern> (8)
3737 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3740 Create an 'reject this routing PC Protocol' line for a filter. An
3741 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3742 filter it is NOT passed thru that interface. See HELP FILTERING for
3743 more info. Please read this to understand how filters work - it will
3744 save a lot of grief later on.You can use any of the following things
3748 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
3755 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3759 You can use the tag 'all' to reject everything eg:
3762 rej/route all (equiv to [very] restricted mode)
3766 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3768 10.101. reject/spots <call> [input] [0-9] <pattern> (8)
3770 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3772 This version allows a sysop to set a filter for a callsign as well as
3773 thedefault for nodes and users eg:-
3776 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3780 reject/spot user_default by G,M,2
3784 10.102. reject/spots [0-9] <pattern> (0)
3786 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3788 Create a 'reject this spot' line for a filter. A reject filter line
3789 means that if the spot matches this filter it isdumped (not passed
3790 on). See HELP FILTERING for more info. Please read thisto understand
3791 how filters work - it will save a lot of grief later on.You can use
3792 any of the following things in this line:-
3795 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>
3799 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3803 You can use the tag 'all' to reject everything eg:
3809 but this probably for advanced users...
3811 10.103. reject/wcy <call> [input] [0-9] <pattern> (8)
3813 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3815 This version allows a sysop to set a filter for a callsign as well as
3816 thedefault for nodes and users eg:-
3819 reject/wcy gb7djk all
3823 10.104. reject/wcy [0-9] <pattern> (0)
3825 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3827 It is unlikely that you will want to do this, but if you do then you
3828 canfilter on the following fields:-
3831 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>
3835 There are no examples because WCY Broadcasts only come from one place
3836 andyou either want them or not (see UNSET/WCY if you don't want
3837 them).This command is really provided for future use.See HELP FILTER
3840 10.105. reject/wwv <call> [input] [0-9] <pattern> (8)
3842 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3844 This version allows a sysop to set a filter for a callsign as well as
3845 thedefault for nodes and users eg:-
3848 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3852 reject/wwv user_default by W
3856 10.106. reject/wwv [0-9] <pattern> (0)
3858 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3860 It is unlikely that you will want to do this, but if you do then you
3861 canfilter on the following fields:-
3864 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>
3871 reject/wwv by_zone 14,15,16
3875 is probably the only useful thing to do (which will only show WWV
3876 broadcastsby stations in the US).See HELP FILTER for information.
3880 reply Reply (privately) to the last message that you have read
3883 10.108. reply <msgno> (0)
3885 reply <msgno> Reply (privately) to the specified message
3888 10.109. reply b <msgno> (0)
3890 reply b <msgno> Reply as a Bulletin to the specified message
3893 10.110. reply noprivate <msgno> (0)
3895 reply noprivate <msgno> Reply as a Bulletin to the specified message
3898 10.111. reply rr <msgno> (0)
3900 reply rr <msgno> Reply to the specified message with read receipt
3902 You can reply to a message and the subject will automatically
3903 have"Re:" inserted in front of it, if it isn't already present.You can
3904 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3905 that you can use with the SEND command (see SENDfor further details)
3907 10.112. save [-d -t -a] <filename> "<cmd>" [...] (9)
3909 save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
3911 This sysop only cammand allows you to save the output of one or
3912 morecommands to a file. For example:-
3915 save /spider/packclus/dxstats show/dxstat
3919 will save the output of the normal command "show/dxstat" to the
3920 file"dxstats" in the files area.You can have some extra flags to the
3921 save which will either date stamp or time stamp or both the filename
3925 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
3929 The -a flag means append to the file instead of overwriting it.You can
3930 have more than one command on the line, to do this you MUSTenclose
3931 each command in double quotes (") eg:-
3934 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
3940 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
3944 You can only write into places that the cluster has permission for
3945 (whichis that of the "sysop" user [which had BETTER NOT BE "root"]),
3946 you will need to create any directories you want to put stuff in
3947 beforehand as well.It is likely that you will want to run these com-
3948 mands in a crontab type situation. You would do that something like:-
3951 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
3955 Note that you still enclose each command with (") characters but you
3956 mustenclose the entire save command in (') characters. Now in fact,
3957 this can be varied if you know what you are doing. See theadmin manual
3960 10.113. send <call> [<call> ...] (0)
3962 send <call> [<call> ...] Send a message to one or more callsigns
3965 10.114. send copy <msgno> <call> (0)
3967 send copy <msgno> <call> Send a copy of a message to someone
3970 10.115. send noprivate <call> (0)
3972 send noprivate <call> Send a message to all stations
3974 All the SEND commands will create a message which will be sent either
3975 toan individual callsign or to one of the 'bulletin' addresses. SEND
3976 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3977 will mark the message as personal and send it to the cluster node
3978 thatthat callsign is connected to. If the <call> you have specified is
3979 in facta known bulletin category on your node (eg: ALL) then the
3980 message shouldautomatically become a bulletin.You can have more than
3981 one callsign in all of the SEND commands.You can have multiple
3982 qualifiers so that you can have for example:-
3985 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3989 which should send a copy of message 123 to G1TLH and G0RDI and you
3990 willreceive a read receipt when they have read the message.SB is an
3991 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3992 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3993 tionally this should be no longer than 29 characters for compatibil-
3994 ity. Most modern clustersoftware should accept more.You will now be
3995 prompted to start entering your text. You finish the message by enter-
3996 ing '/EX' on a new line. For instance:
3999 ... bye then Jim 73 Dirk /ex
4003 If you have started a message and you don't want to keep it then you-
4004 can abandon the message with '/ABORT' on a new line, like:-
4007 line 1 line 2 oh I just can't be bothered with this /abort
4011 If you abort the message it will NOT be sent.When you are entering the
4012 text of your message, most normal output (suchas DX announcements and
4013 so on are suppressed and stored for latter display(upto 20 such lines
4014 are stored, as new ones come along, so the oldestlines are
4015 dropped).Also, you can enter normal commands commands (and get the
4016 output immediately) whilst in the middle of a message. You do this by
4017 typingthe command preceeded by a '/' character on a new line, so:-
4020 /dx g1tlh 144010 strong signal
4024 Will issue a dx annoucement to the rest of the cluster. Also, you can
4025 add the output of a command to your message by preceeding the command
4033 This will show YOU the output from SH/VHFTABLE and also store it in
4034 themessage. You can carry on with the message until you are ready to
4037 10.116. send private <call> (0)
4039 send private <call> Send a personal message
4042 10.117. send rr <call> (0)
4044 send rr <call> Send a message and ask for a read receipt
4047 10.118. set/address <your address> (0)
4049 set/address <your address> Record your postal address
4052 10.119. set/announce (0)
4054 set/announce Allow announce messages to come out on your terminal
4057 10.120. set/anntalk (0)
4059 set/anntalk Allow talk like announce messages on your terminal
4062 10.121. set/arcluster <call> [<call>..] (5)
4064 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
4068 10.122. set/baddx <call>.. (8)
4070 set/baddx <call>.. Stop callsigns in a dx spot being propagated
4073 10.123. set/badnode <call>.. (8)
4075 set/badnode <call>.. Stop spots from this node being propagated
4078 10.124. set/badspotter <call>.. (8)
4080 set/badspotter <call>.. Stop spots from this callsign being propagated
4083 10.125. set/badword <word>.. (8)
4085 set/badword <word>.. Stop things with this word being propagated
4088 10.126. set/bbs <call> [<call>..] (5)
4090 set/bbs <call> [<call>..] Make the callsign a BBS
4093 10.127. set/beep (0)
4095 set/beep Add a beep to DX and other messages on your terminal
4098 10.128. set/clx <call> [<call>..] (5)
4100 set/clx <call> [<call>..] Make the callsign an CLX node
4103 10.129. set/debug <name> (9)
4105 set/debug <name> Add a debug level to the debug set
4110 set/dx Allow DX messages to come out on your terminal
4113 10.131. set/dxcq (0)
4115 set/dxcq Show CQ Zones on the end of DX announcements
4118 10.132. set/dxgrid (0)
4120 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
4123 10.133. set/dxitu (0)
4125 set/dxitu Show ITU Zones on the end of DX announcements
4128 10.134. set/dxnet <call> [<call>..] (5)
4130 set/dxnet <call> [<call>..] Make the callsign an DXNet node
4134 10.135. set/echo (0)
4136 set/echo Make the cluster echo your input
4139 10.136. set/email <email> ... (0)
4141 set/email <email> ... Set email address(es) and forward your personals
4144 10.137. set/here (0)
4146 set/here Tell the system you are present at your terminal
4149 10.138. set/homenode <node> (0)
4151 set/homenode <node> Set your normal cluster callsign
4153 Tell the cluster system where you normally connect to. Any Messages
4154 sentto you will normally find their way there should you not be
4162 10.139. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
4164 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
4167 10.140. set/isolate (9)
4169 set/isolate Isolate a node from the rest of the network
4171 Connect a node to your system in such a way that you are a full
4172 protocolmember of its network and can see all spots on it, but nothing
4173 either leaksout from it nor goes back into from the rest of the nodes
4174 connected to you.You can potentially connect several nodes in this
4177 10.141. set/language <lang> (0)
4179 set/language <lang> Set the language you want to use
4181 You can select the language that you want the cluster to use.
4182 Currentlythe languages available are en (English), de (German), es
4183 (Spanish) and nl (Dutch).
4185 10.142. set/location <lat & long> (0)
4187 set/location <lat & long> Set your latitude and longitude
4190 10.143. set/lockout <call> (9)
4192 set/lockout <call> Stop a callsign connecting to the cluster
4195 10.144. set/logininfo (0)
4197 set/logininfo Inform when a station logs in locally
4199 10.145. set/name <your name> (0)
4201 set/name <your name> Set your name
4203 Tell the system what your name is eg:-
4210 10.146. set/node <call> [<call>..] (5)
4212 set/node <call> [<call>..] Make the callsign an AK1A cluster
4214 Tell the system that the call(s) are to be treated as AK1A cluster
4215 andfed PC Protocol rather normal user commands.
4217 10.147. set/obscount <count> <call> (8)
4219 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
4221 From 1.35 onwards neighbouring nodes are pinged at regular intervals
4222 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
4223 'pump-up'counter which is decremented on every outgoing ping and then
4224 reset tothe 'obscount' value on every incoming ping. The default value
4225 of thisparameter is 2. What this means is that a neighbouring node
4226 will be pinged twice at (default) 300 second intervals and if no reply
4227 has been heard just beforewhat would be the third attempt, that node
4228 is disconnected.If a ping is heard then the obscount is reset to the
4229 full value. Usingdefault values, if a node has not responded to a ping
4230 within 15 minutes,it is disconnected.You can set this parameter
4231 between 1 and 9.It is STRONGLY recommended that you don't change the
4234 10.148. set/page <lines per page> (0)
4236 set/page <lines per page> Set the lines per page
4238 Tell the system how many lines you wish on a page when the number of
4239 lineof output from a command is more than this. The default is 20.
4240 Setting itexplicitly to 0 will disable paging.
4243 SET/PAGE 30 SET/PAGE 0
4247 The setting is stored in your user profile.
4249 10.149. set/password (0)
4251 set/password Set your own password
4253 This command only works for a 'telnet' user (currently). It willonly
4254 work if you have a password already set. This initial passwordcan only
4255 be set by the sysop.When you execute this command it will ask you for
4256 your old password,then ask you to type in your new password twice (to
4257 make sure youget it right). You may or may not see the data echoed on
4258 the screenas you type, depending on the type of telnet client you
4263 10.150. set/password <callsign> <string> (9)
4265 set/password <callsign> <string> Set a users password
4267 The password for a user can only be set by a full sysop. The stringcan
4268 contain any characters. The way this field is used depends on context.
4269 If it is being used inthe SYSOP command context then you are offered 5
4270 random numbers and youhave to supply the corresponding letters. This
4271 is now mainly for ax25connections.If it is being used on incoming
4272 telnet connections then, if a passwordis set or the:
4275 set/var $main::passwdreq = 1
4279 command is executed in the startup script, then a password prompt
4280 isgiven after the normal 'login: ' prompt.
4282 10.151. set/pinginterval <time> <nodecall> (9)
4284 set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes
4286 As from release 1.35 all neighbouring nodes are pinged at regular
4287 intervalsin order to determine the rolling quality of the link and, in
4288 future, toaffect routing decisions. The default interval is 300 secs
4289 or 5 minutes.You can use this command to set a different interval.
4290 Please don't. But if you do the value you enter is treated as minutes
4291 up 30 and secondsfor numbers greater than that.This is used also to
4292 help determine when a link is down at the far end(as certain cluster
4293 software doesn't always notice), see SET/OBSCOUNTfor more
4294 information.If you must change it (and it may be useful for internet
4295 connected nodeson dynamic IP addresses that go away after a set time
4296 of usage) the timecan be specified as:-
4299 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
4303 Please be aware that this causes traffic to occur on the link, setting
4304 this value too low may annoy your neighbours beyond the point of
4305 endurance!You can switch this off by setting it to 0.
4307 10.152. set/privilege <n> <call> [<call..] (9)
4309 set/privilege <n> <call> [<call..] Set privilege level on a call
4311 Set the privilege level on a callsign. The privilege levels that
4312 pertainto commands are as default:-
4315 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.
4319 If you are a sysop and you come in as a normal user on a remote con-
4320 nectionyour privilege will automatically be set to 0.
4322 10.153. set/prompt <string> (0)
4324 set/prompt <string> Set your prompt to <string>
4328 10.154. set/qra <locator> (0)
4330 set/qra <locator> Set your QRA Grid locator
4332 Tell the system what your QRA (or Maidenhead) locator is. If you have
4333 notdone a SET/LOCATION then your latitude and longitude will be set
4334 roughlycorrectly (assuming your locator is correct ;-). For example:-
4341 10.155. set/qth <your qth> (0)
4343 set/qth <your qth> Set your QTH
4345 Tell the system where you are. For example:-
4348 SET/QTH East Dereham, Norfolk
4352 10.156. set/register <call> ... (9)
4354 set/register <call> ... Mark a user as registered
4357 10.157. set/spider <call> [<call>..] (5)
4359 set/spider <call> [<call>..] Make the callsign an DXSpider node
4361 Tell the system that the call(s) are to be treated as DXSpider node
4362 andfed new style DX Protocol rather normal user commands.
4364 10.158. set/sys_location <lat & long> (9)
4366 set/sys_location <lat & long> Set your cluster latitude and longitude
4368 In order to get accurate headings and such like you must tell the
4369 systemwhat your latitude and longitude is. If you have not yet done a
4370 SET/QRAthen this command will set your QRA locator for you. For
4374 SET/LOCATION 52 22 N 0 57 E
4378 10.159. set/sys_qra <locator> (9)
4380 set/sys_qra <locator> Set your cluster QRA Grid locator
4383 10.160. set/talk (0)
4385 set/talk Allow TALK messages to come out on your terminal
4389 10.161. set/usdb <call> <state> <city> (9)
4391 set/usdb <call> <state> <city> add/update a US DB callsign
4393 This command allows you to add or alter a callsign in the US
4394 statedatabase. Use with extreme caution. Anything you do here will
4395 beoverwritten by any weekly updates that affect this callsign
4398 set/usdb g1tlh nh downtown rindge
4402 see also DELETE/USDB
4404 10.162. set/usstate (0)
4406 set/usstate Allow US State info on the end of DX announcements
4411 set/wcy Allow WCY messages to come out on your terminal
4416 set/wwv Allow WWV messages to come out on your terminal
4421 set/wx Allow WX messages to come out on your terminal
4424 10.166. show/baddx (1)
4426 show/baddx Show all the bad dx calls in the system
4428 Display all the bad dx callsigns in the system, see SET/BADDXfor more
4431 10.167. show/badnode (1)
4433 show/badnode Show all the bad nodes in the system
4435 Display all the bad node callsigns in the system, see SET/BADNODEfor
4438 10.168. show/badspotter (1)
4440 show/badspotter Show all the bad spotters in the system
4442 Display all the bad spotter's callsigns in the system, see
4443 SET/BADSPOTTERfor more information.
4445 10.169. show/badword (1)
4447 show/badword Show all the bad words in the system
4449 Display all the bad words in the system, see SET/BADWORDfor more
4454 10.170. show/chat [<group>] [<lines>] (0)
4456 show/chat [<group>] [<lines>] Show any chat or conferencing
4458 This command allows you to see any chat or conferencing that has
4459 occurred whilst you were away. SHOW/CHAT on its own will show data
4460 forall groups. If you use a group name then it will show only chat
4463 10.171. show/configuration [<node>] (0)
4465 show/configuration [<node>] Show all the nodes and users visible
4467 This command allows you to see all the users that can be seenand the
4468 nodes to which they are connected.This command is normally abbreviated
4469 to: sh/cNormally, the list returned will be just for the nodes from
4470 your country (because the list otherwise will be very long).
4477 will produce a complete list of all nodes. BE WARNED: the list that is
4478 returned can be VERY longIt is possible to supply a node or part of a
4479 prefix and you will get a list of the users for that node or list of
4480 nodes starting withthat prefix.
4491 10.172. show/configuration/node (0)
4493 show/configuration/node Show all the nodes connected locally
4495 Show all the nodes connected to this node.
4497 10.173. show/connect (1)
4499 show/connect Show all the active connections
4501 This command shows information on all the active connections known
4502 tothe node. This command gives slightly more information than WHO.
4504 10.174. show/contest <year and month> (0)
4506 show/contest <year and month> Show all the contests for a month
4508 Show all known contests which are maintained at
4509 http://www.sk3bg.se/contest/for a particular month or year. The format
4510 is reasonably flexible.For example:-
4513 SH/CONTEST sep2003 SH/CONTEST 03 march
4517 10.175. show/date [<prefix>|<callsign>] (0)
4519 show/date [<prefix>|<callsign>] Show the local time
4521 This is very nearly the same as SHOW/TIME, the only difference the
4522 formatof the date string if no arguments are given.If no prefixes or
4523 callsigns are given then this command returns the localtime and UTC as
4524 the computer has it right now. If you give some prefixesthen it will
4525 show UTC and UTC + the local offset (not including DST) atthe prefixes
4526 or callsigns that you specify.
4528 10.176. show/db0sdx <callsign> (0)
4530 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
4532 This command queries the DB0SDX QSL server on the internetand returns
4533 any information available for that callsign. This serviceis provided
4534 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
4537 10.177. show/debug (9)
4539 show/debug Show what levels of debug information you are logging
4544 show/dx Interrogate the spot database
4546 If you just type SHOW/DX you will get the last so many spots(sysop
4547 configurable, but usually 10).In addition you can add any number of
4548 these commands in very nearlyany order to the basic SHOW/DX command,
4552 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>
4556 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
4560 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
4564 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
4568 info <text> - any spots containing <text> in the info or remarks
4572 by <call> - any spots spotted by <call> (spotter <call> is the same).
4576 qsl - this automatically looks for any qsl info on the call held in the spot database.
4580 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.
4584 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
4588 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
4592 You can also use this with the 'by' keyword so eg by W dxcc
4600 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
4604 10.179. show/dxcc <prefix> (0)
4606 show/dxcc <prefix> Interrogate the spot database by country
4608 This command takes the <prefix> (which can be a full or partial
4609 callsign if desired), looks up which internal country number it isand
4610 then displays all the spots as per SH/DX for that country.This is now
4611 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
4615 SH/DXCC G SH/DXCC W on 20m iota
4619 This can be done with the SHOW/DX command like this:-
4623 SH/DX dxcc g SH/DX dxcc w on 20m iota
4627 10.180. show/dxqsl <callsign> (0)
4629 show/dxqsl <callsign> Show any QSL info gathered from spots
4631 The node collects information from the comment fields in spots
4632 (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a
4633 database.This command allows you to interrogate that database and if
4634 the callsignis found will display the manager(s) that people have
4635 spotted. This information is NOT reliable, but it is normally
4636 reasonably accurate ifit is spotted enough times.For example:-
4643 You can check the raw input spots yourself with:-
4650 This gives you more background information.
4652 10.181. show/dxstats [days] [date] (0)
4654 show/dxstats [days] [date] Show the DX Statistics
4656 Show the total DX spots for the last <days> no of days (default is
4657 31), starting from a <date> (default: today).
4659 10.182. show/files [<filearea> [<string>]] (0)
4661 show/files [<filearea> [<string>]] List the contents of a filearea
4663 SHOW/FILES on its own will show you a list of the various
4664 fileareasavailable on the system. To see the contents of a particular
4672 where <filearea> is the name of the filearea you want to see the con-
4673 tents of.You can also use shell globbing characters like '*' and '?'
4674 in astring to see a selection of files in a filearea eg:-
4677 SH/FILES bulletins arld*
4681 See also TYPE - to see the contents of a file.
4683 10.183. show/filter (0)
4685 show/filter Show the contents of all the filters you have set
4688 Show the contents of all the filters that are set. This command
4689 displaysall the filters set - for all the various categories.
4691 10.184. show/hfstats [days] [date] (0)
4693 show/hfstats [days] [date] Show the HF DX Statistics
4695 Show the HF DX spots breakdown by band for the last <days> no of days
4696 (default is 31), starting from a <date> (default: today).
4698 10.185. show/hftable [days] [date] [prefix ...] (0)
4700 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4702 Show the HF DX Spotter table for the list of prefixes for the last
4703 <days> no of days (default is 31), starting from a <date> (default:
4704 today).If there are no prefixes then it will show the table for your
4705 country.Remember that some countries have more than one "DXCC country"
4706 in them(eg G :-), to show them (assuming you are not in G already
4707 which isspecially treated in the code) you must list all the relevant
4711 sh/hftable g gm gd gi gj gw gu
4715 Note that the prefixes are converted into country codes so you don't
4716 haveto list all possible prefixes for each country.If you want more or
4717 less days than the default simply include thenumber you require:-
4724 If you want to start at a different day, simply add the date in some
4728 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4732 This will show the stats for your DXCC for that CQWW contest weekend.
4733 You can specify either prefixes or full callsigns (so you can see how
4734 youdid against all your mates). You can also say 'all' which will then
4735 printthe worldwide statistics.
4742 10.186. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4744 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4747 This command shows the hop counts set up for a node. You can
4748 specifywhich category you want to see. If you leave the category out
4749 then all the categories will be listed.
4753 10.187. show/isolate (1)
4755 show/isolate Show list of ISOLATED nodes
4758 10.188. show/lockout <prefix>|all (9)
4760 show/lockout <prefix>|all Show the list of locked out or excluded
4764 10.189. show/log [<callsign>] (8)
4766 show/log [<callsign>] Show excerpts from the system log
4768 This command outputs a short section of the system log. On its ownit
4769 will output a general logfile. With the optional callsign it willshow
4770 output from the log associated with that callsign.
4772 10.190. show/moon [ndays] [<prefix>|<callsign>] (0)
4774 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4776 Show the Moon rise and set times for a (list of) prefixes or
4777 callsigns, together with the azimuth and elevation of the sun
4778 currently at thoselocations.If you don't specify any prefixes or
4779 callsigns, it will show the times foryour QTH (assuming you have set
4780 it with either SET/LOCATION or SET/QRA),together with the current
4781 azimuth and elevation.In addition, it will show the illuminated
4782 fraction of the moons disk.If all else fails it will show the Moonrise
4783 and set times for the nodethat you are connected to. For example:-
4786 SH/MOON SH/MOON G1TLH W5UN
4790 You can also use this command to see into the past or the future, soif
4791 you want to see yesterday's times then do:-
4798 or in three days time:-
4805 Upto 366 days can be checked both in the past and in the future.Please
4806 note that the rise and set times are given as the UT times of rise and
4807 set on the requested UT day.
4809 10.191. show/muf <prefix> [<hours>][long] (0)
4811 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4814 This command allow you to estimate the likelihood of you contactinga
4815 station with the prefix you have specified. The output assumes a
4816 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4817 0.15muV/10dB SINAD)The result predicts the most likely operating
4818 frequencies and signallevels for high frequency (shortwave) radio
4819 propagation paths onspecified days of the year and hours of the day.
4820 It is most useful forpaths between 250 km and 6000 km, but can be used
4821 with reduced accuracyfor paths shorter or longer than this.The command
4822 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4823 predict the MUF given the predicted flux, day of the year,hour of the
4824 day and geographic coordinates of the transmitter andreceiver. This
4825 routine is reasonably accurate for the purposes here,with a claimed
4826 RMS error of 3.8 MHz, but much smaller and less complexthan the
4827 programs used by major shortwave broadcasting organizations,such as
4828 the Voice of America.The command will display some header information
4829 detailing itsassumptions, together with the locations, latitude and
4830 longitudes andbearings. It will then show UTC (UT), local time at the
4831 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4832 the path(Zen) and the likely signal strengths. Then for each frequency
4833 for whichthe system thinks there is a likelihood of a circuit it
4834 prints a value.The value is currently a likely S meter reading based
4835 on the conventional6dB / S point scale. If the value has a '+'
4836 appended it means that it is1/2 an S point stronger. If the value is
4837 preceeded by an 'm' it means thatthere is likely to be much fading and
4838 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4839 will show the next two hours worth of data. Youcan specify anything up
4840 to 24 hours worth of data by appending the no ofhours required after
4841 the prefix. For example:-
4851 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
4855 indicating that you will have weak, fading circuits on top band and
4856 80m but usable signals on 40m (about S3).inputing:-
4863 will get you the above display, but with the next 24 hours worth
4867 SH/MUF W L 24 SH/MUF W 24 Long
4871 Gives you an estimate of the long path propagation characterics.
4872 Itshould be noted that the figures will probably not be very useful,
4873 norterrible accurate, but it is included for completeness.
4875 10.192. show/newconfiguration [<node>] (0)
4877 show/newconfiguration [<node>] Show all the nodes and users visible
4879 This command allows you to see all the users that can be seenand the
4880 nodes to which they are connected. This command produces essentially
4881 the same information as SHOW/CONFIGURATION except that it shows all
4882 the duplication ofany routes that might be present It also uses a
4883 different formatwhich may not take up quite as much space if you don't
4884 have anyloops.BE WARNED: the list that is returned can be VERY long
4885 10.193. show/newconfiguration/node (0)
4887 show/newconfiguration/node Show all the nodes connected locally
4889 Show all the nodes connected to this node in the new format.
4891 10.194. show/node [<callsign> ...] (1)
4893 show/node [<callsign> ...] Show the type and version number of nodes
4895 Show the type and version (if connected) of the nodes specified on
4896 thecommand line. If no callsigns are specified then a sorted list of
4897 allthe non-user callsigns known to the system will be displayed.
4899 10.195. show/prefix <callsign> (0)
4901 show/prefix <callsign> Interrogate the prefix database
4903 This command takes the <callsign> (which can be a full or partial
4904 callsign or a prefix), looks up which internal country number it is
4905 and then displays all the relevant prefixes for that countrytogether
4906 with the internal country no, the CQ and ITU regions. See also
4909 10.196. show/program (5)
4911 show/program Show the locations of all the included program modules
4913 Show the name and location where every program module was load from.
4914 Thisis useful for checking where you think you have loaded a .pm file
4917 10.197. show/qra <lat> <long> (0)
4919 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4921 This is a multipurpose command that allows you either to calculate
4922 thedistance and bearing between two locators or (if only one locator
4923 isgiven on the command line) the distance and beraing from your
4924 stationto the locator. For example:-
4927 SH/QRA IO92QL SH/QRA JN06 IN73
4931 The first example will show the distance and bearing to the locator
4932 fromyourself, the second example will calculate the distance and bear-
4933 ing fromthe first locator to the second. You can use 4 or 6 character
4934 locators.It is also possible to convert a latitude and longitude to a
4935 locator by using this command with a latitude and longitude as an
4936 argument, forexample:-
4939 SH/QRA 52 41 N 0 58 E
4943 10.198. show/qra <locator> [<locator>] (0)
4945 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4949 10.199. show/qrz <callsign> (0)
4951 show/qrz <callsign> Show any callbook details on a callsign
4953 This command queries the QRZ callbook server on the internetand
4954 returns any information available for that callsign. This serviceis
4955 provided for users of this software by http://www.qrz.com See also
4956 SHOW/WM7D for an alternative.
4958 10.200. show/registered [<prefix>] (9)
4960 show/registered [<prefix>] Show the registered users
4963 10.201. show/route <callsign> ... (0)
4965 show/route <callsign> ... Show the route to the callsign
4967 This command allows you to see to which node the callsigns specified
4968 areconnected. It is a sort of inverse sh/config.
4975 10.202. show/satellite <name> [<hours> <interval>] (0)
4977 show/satellite <name> [<hours> <interval>] Show tracking data
4979 Show the tracking data from your location to the satellite of your
4980 choicefrom now on for the next few hours.If you use this command
4981 without a satellite name it will display a listof all the satellites
4982 known currently to the system. If you give a name then you can obtain
4983 tracking data of all the passesthat start and finish 5 degrees below
4984 the horizon. As default it willgive information for the next three
4985 hours for every five minute period.You can alter the number of hours
4986 and the step size, within certain limits. Each pass in a period is
4987 separated with a row of '-----' charactersSo for example:-
4990 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4994 10.203. show/station all [<regex>] (6)
4996 show/station all [<regex>] Show list of users in the system
4999 10.204. show/station [<callsign> ..] (0)
5001 show/station [<callsign> ..] Show information about a callsign
5003 Show the information known about a callsign and whether (and
5004 where)that callsign is connected to the cluster.
5011 If no callsign is given then show the information for yourself.
5013 10.205. show/sun [ndays] [<prefix>|<callsign>] (0)
5015 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
5017 Show the sun rise and set times for a (list of) prefixes or callsigns,
5018 together with the azimuth and elevation of the sun currently at
5019 thoselocations.If you don't specify any prefixes or callsigns, it will
5020 show the times foryour QTH (assuming you have set it with either
5021 SET/LOCATION or SET/QRA),together with the current azimuth and
5022 elevation.If all else fails it will show the sunrise and set times for
5023 the nodethat you are connected to. For example:-
5026 SH/SUN SH/SUN G1TLH K9CW ZS
5030 You can also use this command to see into the past or the future, soif
5031 you want to see yesterday's times then do:-
5038 or in three days time:-
5045 Upto 366 days can be checked both in the past and in the future.Please
5046 note that the rise and set times are given as the UT times of rise and
5047 set on the requested UT day.
5049 10.206. show/time [<prefix>|<callsign>] (0)
5051 show/time [<prefix>|<callsign>] Show the local time
5053 If no prefixes or callsigns are given then this command returns the
5054 localtime and UTC as the computer has it right now. If you give some
5055 prefixesthen it will show UTC and UTC + the local offset (not
5056 including DST) atthe prefixes or callsigns that you specify.
5058 10.207. show/usdb [call ..] (0)
5060 show/usdb [call ..] Show information held on the FCC Call database
5062 Show the City and State of a Callsign held on the FCC database ifhis
5063 is being run on this system, eg:-
5070 10.208. show/vhfstats [days] [date] (0)
5072 show/vhfstats [days] [date] Show the VHF DX Statistics
5074 Show the VHF DX spots breakdown by band for the last <days> no of days
5075 (default is 31), starting from a date (default: today).
5078 10.209. show/vhftable [days] [date] [prefix ...] (0)
5080 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
5082 Show the VHF DX Spotter table for the list of prefixes for the last
5083 <days> no of days (default is 31), starting from a date (default:
5084 today).If there are no prefixes then it will show the table for your
5085 country.Remember that some countries have more than one "DXCC country"
5086 in them(eg G :-), to show them (assuming you are not in G already
5087 which isspecially treated in the code) you must list all the relevant
5091 sh/vhftable g gm gd gi gj gw gu
5095 Note that the prefixes are converted into country codes so you don't
5096 haveto list all possible prefixes for each country.If you want more or
5097 less days than the default simply include thenumber you require:-
5104 If you want to start at a different day, simply add the date in some
5108 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
5112 This will show the stats for your DXCC for that CQWW contest weekend.
5113 You can specify either prefixes or full callsigns (so you can see how
5114 youdid against all your mates). You can also say 'all' which will then
5115 printthe worldwide statistics.
5122 10.210. show/wcy (0)
5124 show/wcy Show last 10 WCY broadcasts
5127 10.211. show/wcy <n> (0)
5129 show/wcy <n> Show last <n> WCY broadcasts
5131 Display the most recent WCY information that has been received by the
5134 10.212. show/wm7d <callsign> (0)
5136 show/wm7d <callsign> Show callbook details on a US callsigns
5138 This command queries the WM7D callbook server on the internetand
5139 returns any information available for that US callsign. This serviceis
5140 provided for users of this software by http://www.wm7d.net.See also
5143 10.213. show/wwv (0)
5145 show/wwv Show last 10 WWV broadcasts
5148 10.214. show/wwv <n> (0)
5150 show/wwv <n> Show last <n> WWV broadcasts
5152 Display the most recent WWV information that has been received by the
5155 10.215. shutdown (5)
5157 shutdown Shutdown the cluster
5159 Shutdown the cluster and disconnect all the users
5161 10.216. spoof <call> <command> (9)
5163 spoof <call> <command> Do a command as though you are another user
5165 This command is provided so that sysops can set a user's parameters
5166 withoutme having to write a special 'sysop' version for every user
5167 command. Itallows you to pretend that you are doing the command as the
5168 user you specify.eg:-
5171 SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
5175 10.217. stat/channel [<callsign>] (5)
5177 stat/channel [<callsign>] Show the status of a channel on the cluster
5179 Show the internal status of the channel object either for the channel
5180 that you are on or else for the callsign that you asked for.Only the
5181 fields that are defined (in perl term) will be displayed.
5183 10.218. stat/db <dbname> (5)
5185 stat/db <dbname> Show the status of a database
5187 Show the internal status of a database descriptor.Depending on your
5188 privilege level you will see more or less information. This command is
5189 unlikely to be of much use to anyone other than a sysop.
5191 10.219. stat/msg (1)
5193 stat/msg Show the status of the message system
5196 10.220. stat/msg <msgno> (1)
5198 stat/msg <msgno> Show the status of a message
5200 This command shows the internal status of a message and includes
5201 informationsuch as to whom it has been forwarded, its size, origin etc
5202 etc.If no message number is given then the status of the message
5203 system is displayed.
5207 10.221. stat/route_node <callsign> (5)
5209 stat/route_node <callsign> Show the data in a Route::Node object
5212 10.222. stat/route_node all (5)
5214 stat/route_node all Show list of all Route::Node objects
5217 10.223. stat/route_user <callsign> (5)
5219 stat/route_user <callsign> Show the data in a Route::User object
5222 10.224. stat/route_user all (5)
5224 stat/route_user all Show list of all Route::User objects
5227 10.225. stat/user [<callsign>] (5)
5229 stat/user [<callsign>] Show the full status of a user
5231 Shows the full contents of a user record including all the secret
5232 flagsand stuff.Only the fields that are defined (in perl term) will be
5237 sysop Regain your privileges if you login remotely
5239 The system automatically reduces your privilege level to that of
5240 anormal user if you login in remotely. This command allows you
5241 toregain your normal privilege level. It uses the normal system:
5242 fivenumbers are returned that are indexes into the character array
5243 that isyour assigned password (see SET/PASSWORD). The indexes start
5244 fromzero.You are expected to return a string which contains the
5245 charactersrequired in the correct order. You may intersperse those
5246 characterswith others to obscure your reply for any watchers. For
5247 example (andthese values are for explanation :-):
5250 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
5257 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
5261 They will all match. If there is no password you will still be
5262 offerednumbers but nothing will happen when you input a string. Any
5263 match iscase sensitive.
5265 10.227. talk <call> > <node> [<text>] (0)
5267 talk <call> > <node> [<text>] Send a text message to another station
5270 Send a short message to any other station that is visible on the
5271 clustersystem. You can send it to anyone you can see with a
5272 SHOW/CONFIGURATION command, they don't have to be connected
5273 locally.The second form of TALK is used when other cluster nodes are
5274 connectedwith restricted information. This usually means that they
5275 don't send the user information usually associated with logging on and
5276 off the cluster.If you know that G3JNB is likely to be present on
5277 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
5278 then you would use thesecond form of the talk message.If you want to
5279 have a ragchew with someone you can leave the text messageout and the
5280 system will go into 'Talk' mode. What this means is that ashort
5281 message is sent to the recipient telling them that you are in
5282 a'Talking' frame of mind and then you just type - everything you send
5283 willgo to the station that you asked for. All the usual announcements,
5284 spots and so on will still come out on yourterminal.If you want to do
5285 something (such as send a spot) you preceed the normal command with a
5289 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
5293 To leave talk mode type:
5300 If you are in 'Talk' mode, there is an extention to the '/' command
5301 whichallows you to send the output to all the people you are talking
5302 to. You do with the '//' command. For example:-
5309 will send the hftable as you have it to all the people you are cur-
5312 10.228. talk <call> [<text>] (0)
5314 talk <call> [<text>] Send a text message to another station
5317 10.229. type <filearea>/<name> (0)
5319 type <filearea>/<name> Look at the contents of a file in one of the
5322 Type out the contents of a file in a filearea. So, for example, in
5323 filearea 'bulletins' you want to look at file 'arld051' you would
5327 TYPE bulletins/arld051
5331 See also SHOW/FILES to see what fileareas are available and a list of
5334 10.230. uncatchup <node call> all|[msgno> ...] (5)
5336 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
5339 When you send messages the fact that you have forwarded it to another
5340 node is remembered so that it isn't sent again. When you have a new
5341 partnernode and you add their callsign to your /spider/msg/forward.pl
5342 file, alloutstanding non-private messages will be forwarded to them.
5343 This may wellbe ALL the non-private messages. You can prevent this by
5344 using these commmands:-
5347 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
5351 and to undo what you have just done:-
5354 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
5358 which will arrange for them to be forward candidates again.Order is
5361 10.231. unset/announce (0)
5363 unset/announce Stop announce messages coming out on your terminal
5366 10.232. unset/anntalk (0)
5368 unset/anntalk Stop talk like announce messages on your terminal
5370 The announce system on legacy cluster nodes is used as a talk
5371 substitute because the network is so poorly connected. If you:
5378 you will suppress several of these announces, you may miss the odd
5379 useful one as well, but you would probably miss them anyway in thewel-
5380 ter of useless ones.
5387 allows you to see them again. This is the default.
5389 10.233. unset/baddx <call>.. (8)
5391 unset/baddx <call>.. Propagate a dx spot with this callsign again
5393 Setting a word as 'baddx' will prevent spots with that word in
5394 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
5395 anyfurther. They will not be displayed and they will not be sent
5396 ontoother nodes.The word must be written in full, no wild cards are
5400 set/baddx FORSALE VIDEO FR0G
5404 To allow a word again, use the following command ...
5411 10.234. unset/badnode <call>.. (8)
5413 unset/badnode <call>.. Allow spots from this node again
5415 Setting a callsign as a 'badnode' will prevent spots from that node
5416 going any further. They will not be displayed and they will not be
5417 sent onto other nodes.The call must be a full eg:-
5424 will stop anything from K1TTT. If you want SSIDs as well then you mus-
5425 tenter them specifically.
5432 will allow spots from him again.Use with extreme care. This command
5433 may well be superceeded by FILTERing.
5435 10.235. unset/badspotter <call>.. (8)
5437 unset/badspotter <call>.. Allow spots from this callsign again
5439 Setting a callsign as a 'badspotter' will prevent spots from this
5440 callsign going any further. They will not be displayed and they will
5441 not be sent onto other nodes.The call must be written in full, no wild
5442 cards are allowed eg:-
5445 set/badspotter VE2STN
5449 will stop anything from VE2STN. This command will automaticallystop
5450 spots from this user, regardless of whether or which SSID he uses. DO
5451 NOT USE SSIDs in the callsign, just use the callsignas above or below.
5454 unset/badspotter VE2STN
5458 will allow spots from him again.Use with extreme care. This command
5459 may well be superceded by FILTERing.
5461 10.236. unset/badword <word>.. (8)
5463 unset/badword <word>.. Propagate things with this word again
5465 Setting a word as a 'badword' will prevent things like spots,announces
5466 or talks with this word in the the text part from going anyfurther.
5467 They will not be displayed and they will not be sent ontoother
5468 nodes.The word must be written in full, no wild cards are allowed eg:-
5469 set/badword annihilate annihilated annihilation
5473 will stop anything with these words in the text.
5476 unset/badword annihilated
5480 will allow text with this word again.
5482 10.237. unset/beep (0)
5484 unset/beep Stop beeps for DX and other messages on your terminal
5487 10.238. unset/debug <name> (9)
5489 unset/debug <name> Remove a debug level from the debug set
5491 You can choose to log several different levels. The levels are
5494 chan state msg cron connect
5498 You can show what levels you are logging with SHOW/DEBUG
5500 10.239. unset/dx (0)
5502 unset/dx Stop DX messages coming out on your terminal
5505 10.240. unset/dxcq (0)
5507 unset/dxcq Stop CQ Zones on the end of DX announcements
5509 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
5510 announcement (there is just enough room). Some user programscannot
5511 cope with this. The Spotter's CQ is on the RHS of the time, the
5512 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
5513 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5516 10.241. unset/dxgrid (0)
5518 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
5520 A standard feature which is enabled in version 1.43 and above is that
5521 if the spotter's grid square is known it is output on the endof a DX
5522 announcement (there is just enough room). Some user programscannot
5523 cope with this. You can use this command to reset (or set)this
5524 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
5525 flags you have set if you are confused.
5527 10.242. unset/dxitu (0)
5529 unset/dxitu Stop ITU Zones on the end of DX announcements
5531 Display both the Spotter's and the Spotted's ITU Zone on the endof a
5532 DX announcement (there is just enough room). Some user programscannot
5533 cope with this. The Spotter's ITU is on the RHS of the time, the
5534 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
5535 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5538 10.243. unset/echo (0)
5540 unset/echo Stop the cluster echoing your input
5542 If you are connected via a telnet session, different implimentationsof
5543 telnet handle echo differently depending on whether you are connected
5544 via port 23 or some other port. You can use this commandto change the
5545 setting appropriately. The setting is stored in your user profile.YOU
5546 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
5548 10.244. unset/email (0)
5550 unset/email Stop personal msgs being forwarded by email
5552 If any personal messages come in for your callsign then you can
5553 usethese commands to control whether they are forwarded onto your
5554 emailaddress. To enable the forwarding do something like:-
5557 SET/EMAIL mike.tubby@somewhere.com
5561 You can have more than one email address (each one separated by a
5562 space).Emails are forwarded to all the email addresses you specify.You
5563 can disable forwarding by:-
5570 10.245. unset/here (0)
5572 unset/here Tell the system you are absent from your terminal
5575 10.246. unset/hops <call> ann|spots|route|wwv|wcy (8)
5577 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
5579 Set the hop count for a particular type of broadcast for a node.This
5580 command allows you to set up special hop counts for a node for
5581 currently: announce, spots, wwv and wcy broadcasts.eg:
5584 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
5588 Set SHOW/HOPS for information on what is already set. This commandcre-
5589 ates a filter and works in conjunction with the filter system. You can
5590 unset the hops with command UNSET/HOPS. For example:-
5593 unset/hops gb7djk ann unset/hops gb7mbc spots
5597 10.247. unset/isolate (9)
5599 unset/isolate Stop Isolation of a node from the rest of the network
5601 Remove isolation from a node - SET/ISOLATE
5603 10.248. unset/lockout <call> (9)
5605 unset/lockout <call> Allow a callsign to connect to the cluster
5608 10.249. unset/logininfo (0)
5610 unset/logininfo Inform when a station logs out locally
5613 10.250. unset/password <call> ... (9)
5615 unset/password <call> ... Delete (remove) a user's password
5617 This command allows the sysop to completely delete and remove a
5618 password for a user.
5620 10.251. unset/privilege (0)
5622 unset/privilege Remove any privilege for this session
5624 You can use this command to 'protect' this session from
5625 unauthoriseduse. If you want to get your normal privilege back you
5626 will need toeither logout and login again (if you are on a console) or
5627 use theSYSOP command.
5629 10.252. unset/prompt (0)
5631 unset/prompt Set your prompt back to default
5633 This command will set your user prompt to exactly the string that you
5634 say. The point of this command to enable a user to interface to
5635 programsthat are looking for a specific prompt (or else you just want
5636 a differentfixed prompt).
5643 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
5646 10.253. unset/register <call> ... (9)
5648 unset/register <call> ... Mark a user as not registered
5650 Registration is a concept that you can switch on by executing the
5653 set/var $main::regreq = 1
5657 command (usually in your startup file)If a user is NOT registered
5658 then, firstly, instead of the normalmotd file (/spider/data/motd)
5659 being sent to the user at startup, theuser is sent the motd_nor file
5660 instead. Secondly, the non registereduser only has READ-ONLY access to
5661 the node. The non-registered usercannot use DX, ANN etc. The only
5662 exception to this is that a non-registered user can TALK orSEND
5663 messages to the sysop.
5665 10.254. unset/talk (0)
5667 unset/talk Stop TALK messages coming out on your terminal
5670 10.255. unset/usstate (0)
5672 unset/usstate Stop US State info on the end of DX announcements
5674 If the spotter's or spotted's US State is known it is output on the
5675 end of a DX announcement (there is just enough room). A spotter's
5676 state will appear on the RHS of the time (like SET/DXGRID) and the
5677 spotted's State will appear on the LHS of thetime field. Any
5678 information found will override any locator information from
5679 SET/DXGRID.Some user programs cannot cope with this. You can use this
5680 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
5681 SET/DXITUDo a STAT/USER to see which flags you have set if you are
5684 10.256. unset/wcy (0)
5686 unset/wcy Stop WCY messages coming out on your terminal
5689 10.257. unset/wwv (0)
5691 unset/wwv Stop WWV messages coming out on your terminal
5694 10.258. unset/wx (0)
5696 unset/wx Stop WX messages coming out on your terminal
5701 who Show who is physically connected
5703 This is a quick listing that shows which callsigns are connected
5704 andwhat sort of connection they have
5706 10.260. wx <text> (0)
5708 wx <text> Send a weather message to local users
5711 10.261. wx full <text> (0)
5713 wx full <text> Send a weather message to all cluster users
5716 10.262. wx sysop <text> (5)
5718 wx sysop <text> Send a weather message to other clusters only
5720 Weather messages can sometimes be useful if you are experiencing an
5721 extremethat may indicate enhanced conditions