1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 March 2003 revision 0.5
6 A reference for SysOps of the DXSpider DXCluster program.
7 ______________________________________________________________________
13 1. Routing and Filtering
16 1.3 The node_default filter
17 1.4 General route filtering
18 1.5 General filter rules
22 1.9 Advanced filtering
23 1.10 Basic hop control
24 1.11 Hop Control on Specific Nodes
25 1.12 Isolating networks
29 2.2 Filtering words from text fields in Announce, Talk and DX spots
30 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
39 3.7 Distribution lists
44 5.1 Creating databases
45 5.2 Importing databases
46 5.3 Checking available databases
47 5.4 Looking up databases
48 5.5 Removing databases
50 6. Information, files and useful programs
54 6.4 Other text messages
57 6.7 Updating kepler data
59 6.9 Connecting logging programs
62 8. Web based statistics
68 10.1 CVS from a Linux platform
69 10.2 CVS from a Windows platform
71 11. The DXSpider command set
73 11.2 accept/announce <call> [input] [0-9] <pattern> (8)
74 11.3 accept/announce [0-9] <pattern> (0)
75 11.4 accept/route <call> [0-9] <pattern> (8)
76 11.5 accept/spots <call> [input] [0-9] <pattern> (8)
77 11.6 accept/spots [0-9] <pattern> (0)
78 11.7 accept/wcy <call> [input] [0-9] <pattern> (8)
79 11.8 accept/wcy [0-9] <pattern> (0)
80 11.9 accept/wwv <call> [input] [0-9] <pattern> (8)
81 11.10 accept/wwv [0-9] <pattern> (0)
82 11.11 announce <text> (0)
83 11.12 announce full <text> (0)
84 11.13 announce sysop <text> (5)
85 11.14 apropos <string> (0)
86 11.15 blank [<string>] [<nn>] (0)
88 11.17 catchup <node call> all|[<msgno> ...] (5)
89 11.18 chat <group> <text> (0)
90 11.19 clear/announce <callsign> [input] [0-9|all] (8)
91 11.20 clear/announce [1|all] (0)
92 11.21 clear/route <callsign> [input] [0-9|all] (8)
93 11.22 clear/route [1|all] (0)
94 11.23 clear/spots <callsign> [input] [0-9|all] (8)
95 11.24 clear/spots [0-9|all] (0)
96 11.25 clear/wcy <callsign> [input] [0-9|all] (8)
97 11.26 clear/wcy [1|all] (0)
98 11.27 clear/wwv <callsign> [input] [0-9|all] (8)
99 11.28 clear/wwv [1|all] (0)
100 11.29 connect <callsign> (5)
102 11.31 dbcreate <name> (9)
103 11.32 dbcreate <name> chain <name> [<name>..] (9)
104 11.33 dbcreate <name> cmd <dxspider command> (9)
105 11.34 dbcreate <name> remote <node> (9)
106 11.35 dbimport <dbname> <filename> (9)
107 11.36 dbremove <dbname> (9)
108 11.37 dbshow <dbname> <key> (0)
110 11.39 delete/usdb <callsign> ... (9)
111 11.40 delete/user <callsign> ... (9)
112 11.41 demonstrate <call> <command> (9)
114 11.43 directory <from>-<to> (0)
115 11.44 directory <nn> (0)
116 11.45 directory all (0)
117 11.46 directory from <call> (0)
118 11.47 directory new (0)
119 11.48 directory own (0)
120 11.49 directory subject <string> (0)
121 11.50 directory to <call> (0)
123 11.52 disconnect <call> [<call> ...] (8)
124 11.53 dx [by <call>] <freq> <call> <remarks> (0)
125 11.54 echo <line> (0)
126 11.55 export <msgno> <filename> (9)
127 11.56 export_users [<filename>] (9)
128 11.57 filtering... (0)
129 11.58 forward/latlong <node_call> (8)
130 11.59 forward/opernam <call> (1)
132 11.61 init <node> (5)
133 11.62 join <group> (0)
135 11.64 kill <from msgno>-<to msgno> (0)
136 11.65 kill <from>-<to> (5)
137 11.66 kill <msgno> [<msgno..] (0)
138 11.67 kill <msgno> [<msgno> ...] (0)
139 11.68 kill expunge <msgno> [<msgno..] (6)
140 11.69 kill from <call> (5)
141 11.70 kill full <msgno> [<msgno..] (5)
142 11.71 kill full <msgno> [<msgno] (5)
143 11.72 kill to <call> (5)
144 11.73 kill from <regex> (0)
145 11.74 kill to <regex> (0)
146 11.75 leave <group> (0)
148 11.77 load/aliases (9)
149 11.78 load/badmsg (9)
150 11.79 load/badwords (9)
152 11.81 load/cmd_cache (9)
153 11.82 load/forward (9)
155 11.84 load/keps [nn] (5)
156 11.85 load/messages (9)
157 11.86 load/prefixes (9)
158 11.87 merge <node> [<no spots>/<no wwv>] (5)
159 11.88 msg <cmd> <msgno> [data ... ] (9)
160 11.89 pc <call> <text> (8)
161 11.90 ping <node call> (1)
162 11.91 rcmd <node call> <cmd> (1)
164 11.93 read <msgno> (0)
167 11.96 reject/announce <call> [input] [0-9] <pattern> (8)
168 11.97 reject/announce [0-9] <pattern> (0)
169 11.98 reject/route <call> [0-9] <pattern> (8)
170 11.99 reject/spots <call> [input] [0-9] <pattern> (8)
171 11.100 reject/spots [0-9] <pattern> (0)
172 11.101 reject/wcy <call> [input] [0-9] <pattern> (8)
173 11.102 reject/wcy [0-9] <pattern> (0)
174 11.103 reject/wwv <call> [input] [0-9] <pattern> (8)
175 11.104 reject/wwv [0-9] <pattern> (0)
177 11.106 reply <msgno> (0)
178 11.107 reply b <msgno> (0)
179 11.108 reply noprivate <msgno> (0)
180 11.109 reply rr <msgno> (0)
181 11.110 save [-d -t -a] <filename> "<cmd>" [...] (9)
182 11.111 send <call> [<call> ...] (0)
183 11.112 send copy <msgno> <call> (0)
184 11.113 send noprivate <call> (0)
185 11.114 send private <call> (0)
186 11.115 send rr <call> (0)
187 11.116 set/address <your address> (0)
188 11.117 set/announce (0)
189 11.118 set/anntalk (0)
190 11.119 set/arcluster <call> [<call>..] (5)
191 11.120 set/baddx <call>.. (8)
192 11.121 set/badnode <call>.. (8)
193 11.122 set/badspotter <call>.. (8)
194 11.123 set/badword <word>.. (8)
195 11.124 set/bbs <call> [<call>..] (5)
197 11.126 set/clx <call> [<call>..] (5)
198 11.127 set/debug <name> (9)
201 11.130 set/dxgrid (0)
203 11.132 set/dxnet <call> [<call>..] (5)
205 11.134 set/email <email> ... (0)
207 11.136 set/homenode <node> (0)
208 11.137 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
209 11.138 set/isolate (9)
210 11.139 set/language <lang> (0)
211 11.140 set/location <lat & long> (0)
212 11.141 set/lockout <call> (9)
213 11.142 set/logininfo (0)
214 11.143 set/name <your name> (0)
215 11.144 set/node <call> [<call>..] (5)
216 11.145 set/obscount <count> <call> (8)
217 11.146 set/page <lines per page> (0)
218 11.147 set/password (0)
219 11.148 set/password <callsign> <string> (9)
220 11.149 set/pinginterval <time> <nodecall> (9)
221 11.150 set/privilege <n> <call> [<call..] (9)
222 11.151 set/prompt <string> (0)
223 11.152 set/qra <locator> (0)
224 11.153 set/qth <your qth> (0)
225 11.154 set/register <call> ... (9)
226 11.155 set/spider <call> [<call>..] (5)
227 11.156 set/sys_location <lat & long> (9)
228 11.157 set/sys_qra <locator> (9)
230 11.159 set/usdb <call> <state> <city> (9)
231 11.160 set/usstate (0)
235 11.164 show/baddx (1)
236 11.165 show/badnode (1)
237 11.166 show/badspotter (1)
238 11.167 show/badword (1)
239 11.168 show/chat [<group>] [<lines>] (0)
240 11.169 show/configuration [<node>] (0)
241 11.170 show/configuration/node (0)
242 11.171 show/connect (1)
243 11.172 show/contest <year and month> (0)
244 11.173 show/date [<prefix>|<callsign>] (0)
245 11.174 show/db0sdx <callsign> (0)
246 11.175 show/debug (9)
248 11.177 show/dxcc <prefix> (0)
249 11.178 show/dxqsl <callsign> (0)
250 11.179 show/dxstats [days] [date] (0)
251 11.180 show/files [<filearea> [<string>]] (0)
252 11.181 show/filter (0)
253 11.182 show/hfstats [days] [date] (0)
254 11.183 show/hftable [days] [date] [prefix ...] (0)
255 11.184 show/hops <call> [ann|spots|route|wcy|wwv] (8)
256 11.185 show/isolate (1)
257 11.186 show/lockout <prefix>|all (9)
258 11.187 show/log [<callsign>] (8)
259 11.188 show/moon [ndays] [<prefix>|<callsign>] (0)
260 11.189 show/muf <prefix> [<hours>][long] (0)
261 11.190 show/newconfiguration [<node>] (0)
262 11.191 show/newconfiguration/node (0)
263 11.192 show/node [<callsign> ...] (1)
264 11.193 show/prefix <callsign> (0)
265 11.194 show/program (5)
266 11.195 show/qra <lat> <long> (0)
267 11.196 show/qra <locator> [<locator>] (0)
268 11.197 show/qrz <callsign> (0)
269 11.198 show/registered [<prefix>] (9)
270 11.199 show/route <callsign> ... (0)
271 11.200 show/satellite <name> [<hours> <interval>] (0)
272 11.201 show/station all [<regex>] (6)
273 11.202 show/station [<callsign> ..] (0)
274 11.203 show/sun [ndays] [<prefix>|<callsign>] (0)
275 11.204 show/time [<prefix>|<callsign>] (0)
276 11.205 show/usdb [call ..] (0)
277 11.206 show/vhfstats [days] [date] (0)
278 11.207 show/vhftable [days] [date] [prefix ...] (0)
280 11.209 show/wcy <n> (0)
281 11.210 show/wm7d <callsign> (0)
283 11.212 show/wwv <n> (0)
285 11.214 spoof <call> <command> (9)
286 11.215 stat/channel [<callsign>] (5)
287 11.216 stat/db <dbname> (5)
289 11.218 stat/msg <msgno> (1)
290 11.219 stat/route_node <callsign> (5)
291 11.220 stat/route_node all (5)
292 11.221 stat/route_user <callsign> (5)
293 11.222 stat/route_user all (5)
294 11.223 stat/user [<callsign>] (5)
296 11.225 talk <call> > <node> [<text>] (0)
297 11.226 talk <call> [<text>] (0)
298 11.227 type <filearea>/<name> (0)
299 11.228 uncatchup <node call> all|[msgno> ...] (5)
300 11.229 unset/announce (0)
301 11.230 unset/anntalk (0)
302 11.231 unset/baddx <call>.. (8)
303 11.232 unset/badnode <call>.. (8)
304 11.233 unset/badspotter <call>.. (8)
305 11.234 unset/badword <word>.. (8)
306 11.235 unset/beep (0)
307 11.236 unset/debug <name> (9)
309 11.238 unset/dxcq (0)
310 11.239 unset/dxgrid (0)
311 11.240 unset/dxitu (0)
312 11.241 unset/echo (0)
313 11.242 unset/email (0)
314 11.243 unset/here (0)
315 11.244 unset/hops <call> ann|spots|route|wwv|wcy (8)
316 11.245 unset/isolate (9)
317 11.246 unset/lockout <call> (9)
318 11.247 unset/logininfo (0)
319 11.248 unset/password <call> ... (9)
320 11.249 unset/privilege (0)
321 11.250 unset/prompt (0)
322 11.251 unset/register <call> ... (9)
323 11.252 unset/talk (0)
324 11.253 unset/usstate (0)
330 11.259 wx full <text> (0)
331 11.260 wx sysop <text> (5)
334 ______________________________________________________________________
336 1. Routing and Filtering
340 From DXSpider version 1.48, major changes were introduced to the way
341 node connections are treated. This is part of an ongoing process to
342 remove problems with loops and to enable talk and other functions to
343 propagate across the whole of the worldwide cluster network. In fact,
344 in a Spider network, it would be useful, perhaps even necessary to
345 have loops. This would give real resilience to the network, meaning
346 that if a link dropped, the information flow would simply come in and
347 go out via a different route. Of course, we do not have a complete
348 network of Spider nodes, there are other programs out there. Some of
349 these do not have any protection from loops. Certainly AK1A does not
350 handle loops well at all. It is therefore necessary to have some form
351 of protection for these nodes.
354 In fact DXSpider has had a simple system for some time which is called
355 isolation. This is similar to what in other systems such as clx, is
356 called passive mode. A more detailed explanation of isolation is given
357 further below. This system is still available and, for simple
358 networks, is probably all that you need.
361 The new functionality introduced in version 1.48 allows filtering the
362 node and user protocol frames on a "per interface" basis. We call this
363 route filtering. This is used instead of isolation.
366 What this really means is that you can control more or less completely
367 which user and node management PC protocol frames pass to each of your
368 partner nodes. You can also limit what comes into your node from your
369 partners. It is even possible to control the settings that your
370 partner node has for the routing information that it sends to you
371 (using the rcmd command).
376 Initially when route filters were being tested we generated a
377 "default" filter. Unfortunately it quickly became apparent that this
378 might suit the UK cluster network but didn't really fit anybody else.
379 However using a default filter is an appropriate thing to do. How, is
380 explained further on.
383 The first thing that you must do is determine whether you need to use
384 route filtering at all. If you are a "normal" node with two or three
385 partners and you arranged in an "official" non-looping tree type
386 network, then you do not need to do route filtering and you will feel
387 a lot better for not getting involved. If you are successfully using
388 isolation then you also probably don't need to use route filtering.
391 To put it simply, you should not mix Isolation and Route Filtering.
392 It will work, of sorts, but you will not get the expected results. If
393 you are using Isolation sucessfully at the moment, do not get involved
394 in Route Filtering unless you have a good supply of aspirin! Once you
395 have started down the road of Route Filtering, do not use Isolation
396 either. Use one or the other, not both.
399 You will only require this functionality if you are "well-connected".
400 What that means is that you are connected to several different parts
401 of (say) the EU cluster and, at the same time, also connected to two
402 or three places in the US which, in turn are connected back to the EU.
403 This is called a "loop" and if you are seriously looped then you need
407 I should at this stage give a little bit of background on filters.
408 All the filters in Spider work in basically the same way. You can
409 either accept or reject various options in order to create the filter
410 rules you wish to achieve. Some filters are user settable, others can
411 only be altered by the sysop. Route filtering can only be done by the
416 Anyway, without further discouragement, let me start the process of
420 1.3. The node_default filter
422 All normal systems should have a default routing filter and it should
423 usually be set to send only the normal, unlooped, view of your
424 "national" network. Here in the UK that means nodes from the UK and
425 Eire, in EU it is more complex as the networks there grew up in a more
430 The generic commands are:-
434 reject/route node_default <filter_option>
438 accept/route node_default <filter_option>
442 where filter_option is one of the following ...
451 channel_dxcc <numbers>
452 channel_itu <numbers>
453 channel_zone <numbers>
457 Please be careful if you alter this setting, it will affect ALL your
458 links! Remember, this is a default filter for node connections, not a
462 For the default routing filter then you have two real choices: either
463 a "national" view or the "safe" option of only your own callsign.
464 Examples of each (for my node: GB7DJK) are:-
468 acc/route node_default call_dxcc 61,38
469 acc/route node_default call gb7djk
473 GB7DJK uses the first of these. The DXCC countries can be obtained
474 from the show/prefix command.
477 The example filters shown control output TO all your partner nodes
478 unless they have a specific filter applied to them (see next section).
481 It is also possible to control the incoming routing information that
482 you are prepared to accept FROM your partner nodes. The reason this is
483 necessary is to make sure that stuff like mail, pings and similar
484 commands a) go down the correct links and b) don't loop around
485 excessively. Again using GB7DJK as an example a typical default input
486 filter would be something like:
490 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
494 What this does is accept node and user information for our national
495 network from nodes that are in our national network, but rejects such
496 information from anyone else. Although it doesn't explicitly say so,
497 by implication, any other node information (not from the UK and Eire)
501 As I imagine it will take a little while to get one's head around all
502 of this you can study the effect of any rules that you try by watching
503 the debug output after having done:-
511 After you have got tired of that, to put it back the way it was:-
519 1.4. General route filtering
521 Exactly the same rules apply for general route filtering. You would
522 use either an accept filter or a reject filter like this ...
526 reject/route <node_call> <filter_option>
530 accept/route <node_call> <filter_option>
534 Here are some examples of route filters ...
538 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
539 rej/route all (equiv to [very] restricted mode)
540 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
541 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
545 In practice you will either be opening the default filter out for a
546 partner by defining a specific filter for that callsign:-
551 acc/route gb7baa input all
555 or restricting it quite a lot, in fact making it very nearly like an
556 isolated node, like this:-
560 acc/route pi4ehv-8 call gb7djk
561 rej/route pi4ehv-8 input call_dxcc 61,38
565 This last example takes everything except UK and Eire from PI4EHV-8
566 but only sends him my local configuration (just a PC19 for GB7DJK and
567 PC16s for my local users).
570 It is possible to write much more complex rules, there are up to 10
571 accept/reject pairs per callsign per filter. For more information see
576 1.5. General filter rules
578 Upto v1.44 it was not possible for the user to set their own filters.
579 From v1.45 though that has all changed. It is now possible to set
580 filters for just about anything you wish. If you have just updated
581 from an older version of DXSpider you will need to update your new
582 filters. You do not need to do anything with your old filters, they
583 will be renamed as you update.
586 There are 3 basic commands involved in setting and manipulating
587 filters. These are accept, reject and clear. First we will look
588 generally at filtering. There are a number of things you can filter in
589 the DXSpider system. They all use the same general mechanism.
592 In general terms you can create a "reject" or an "accept" filter which
593 can have up to 10 lines in it. You do this using, for example ...
602 where ..... are the specific commands for that type of filter. There
603 are filters for spots, wwv, announce, wcy and (for sysops) connects.
604 See each different accept or reject command reference for more
607 There is also a command to clear out one or more lines in a filter.
617 There is clear/xxxx command for each type of filter.
620 and you can check that your filters have worked by the command ...
628 For now we are going to use spots for the examples, but you can apply
629 the same principles to all types of filter.
634 There are two main types of filter, accept or reject. You can use
635 either to achieve the result you want dependent on your own preference
636 and which is more simple to do. It is pointless writing 8 lines of
637 reject filters when 1 accept filter would do the same thing! Each
638 filter has 10 lines (of any length) which are tried in order. If a
639 line matches then the action you have specified is taken (ie reject
640 means ignore it and accept means take it)
643 If you specify reject filters, then any lines that arrive that match
644 the filter will be dumped but all else will be accepted. If you use
645 an accept filter, then ONLY the lines in the filter will be accepted
646 and all else will be dumped. For example if you have a single line
651 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
655 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
657 If you set a reject filter like this ...
661 reject/spots on hf/cw
665 Then you will get everything EXCEPT HF CW spots. You could make this
666 single filter even more flexible. For example, if you are interested
667 in IOTA and will work it even on CW even though normally you are not
668 interested in CW, then you could say ...
672 reject/spots on hf/cw and not info iota
676 But in that case you might only be interested in iota and say:-
680 accept/spots not on hf/cw or info iota
684 which achieves exactly the same thing. You should choose one or the
685 other until you are comfortable with the way it works. You can mix
686 them if you wish (actually you can have an accept AND a reject on the
687 same line) but don't attempt this until you are sure you know what you
691 You can arrange your filter lines into logical units, either for your
692 own understanding or simply convenience. Here is an example ...
696 reject/spots 1 on hf/cw
697 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
701 What this does is to ignore all HF CW spots and also rejects any spots
702 on VHF which don't either originate or spot someone in Europe.
705 This is an example where you would use a line number (1 and 2 in this
706 case), if you leave the digit out, the system assumes '1'. Digits
707 '0'-'9' are available. This make it easier to see just what filters
708 you have set. It also makes it more simple to remove individual
709 filters, during a contest for example.
712 You will notice in the above example that the second line has
713 brackets. Look at the line logically. You can see there are 2
714 separate sections to it. We are saying reject spots that are VHF or
715 above APART from those in zones 14, 15 and 16 (either spotted there or
716 originated there). If you did not have the brackets to separate the 2
717 sections, then Spider would read it logically from the front and see a
718 different expression entirely ...
719 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
723 The simple way to remember this is, if you use OR - use brackets.
724 Whilst we are here CASE is not important. 'And BY_Zone' is just the
725 same as 'and by_zone'.
727 As mentioned earlier, setting several filters can be more flexible
728 than simply setting one complex one. Doing it in this way means that
729 if you want to alter your filter you can just redefine or remove one
730 or more lines of it or one line. For example ...
734 reject/spots 1 on hf/ssb
738 would redefine our earlier example, or
746 To remove all the filter lines in the spot filter ...
756 You can filter in several different ways. The options are listed in
757 the various helpfiles for accept, reject and filter.
762 Sometimes all that is needed is a general rule for node connects.
763 This can be done with a node_default filter. This rule will always be
764 followed, even if the link is isolated, unless another filter is set
765 specifically. Default rules can be set for nodes and users. They can
766 be set for spots, announces, WWV and WCY. They can also be used for
767 hops. An example might look like this ...
771 accept/spot node_default by_zone 14,15,16,20,33
772 set/hops node_default spot 50
776 This filter is for spots only, you could set others for announce, WWV
777 and WCY. This filter would work for ALL nodes unless a specific
778 filter is written to override it for a particular node. You can also
779 set a user_default should you require. It is important to note that
780 default filters should be considered to be "connected". By this I
781 mean that should you override the default filter for spots, you need
782 to add a rule for the hops for spots also.
785 1.9. Advanced filtering
787 Once you are happy with the results you get, you may like to
791 The previous example that filters hf/cw spots and accepts vhf/uhf
792 spots from EU can be written with a mixed filter, for example ...
798 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
802 Note that the first filter has not been specified with a number. This
803 will automatically be assumed to be number 1. In this case, we have
804 said reject all HF spots in the CW section of the bands but accept all
805 others at HF. Also accept anything in VHF and above spotted in or by
806 operators in the zones 14, 15 and 16. Each filter slot actually has a
807 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
811 It was mentioned earlier that after a reject test that doesn't match,
812 the default for following tests is 'accept', the reverse is true for
813 'accept'. In the example what happens is that the reject is executed
814 first, any non hf/cw spot is passed to the accept line, which lets
815 through everything else on HF. The next filter line lets through just
816 VHF/UHF spots from EU.
819 1.10. Basic hop control
821 In /spider/data you will find a file called hop_table.pl. This is the
822 file that controls your hop count settings. It has a set of default
823 hops on the various PC frames and also a set for each node you want to
824 alter the hops for. You may be happy with the default settings of
825 course, but this powerful tool can help to protect and improve the
826 network. The file will look something like this ...
831 # hop table construction
836 # default hopcount to use
839 # some variable hop counts based on message type
850 # the per node hop control thingy
882 Each set of hops is contained within a pair of curly braces and
883 contains a series of PC frame types. PC11 for example is a DX spot.
884 The figures here are not exhaustive but should give you a good idea of
888 SHould any of the nodecalls include an ssid, it is important to wrap
889 the whole call in single quotes, like this ...
904 If you do not do this, you will get errors and the file will not work
908 You can alter this file at any time, including whilst the cluster is
909 running. If you alter the file during runtime, the command load/hops
910 will bring your changes into effect.
913 1.11. Hop Control on Specific Nodes
915 You can set a callsign specific hop count for any of the standard
920 set/hops gb7djk spot 4
921 set/hops node_default route 10
922 set/hops gb7baa wcy 5
926 all work on their specific area of the protocol.
929 The set/hops command overrides any hops that you have set otherwise.
932 You can show what hops have been set using the show/hops command.
935 1.12. Isolating networks
937 It is possible to isolate networks from each other on a "gateway" node
938 using the set/isolate <node_call> command.
941 The effect of this is to partition an isolated network completely from
942 another node connected to your node. Your node will appear on and
943 otherwise behave normally on every network to which you are connected,
944 but data from an isolated network will not cross onto any other
945 network or vice versa. However all the spot, announce and WWV traffic
946 and personal messages will still be handled locally (because you are a
947 real node on all connected networks), that is locally connected users
948 will appear on all networks and will be able to access and receive
949 information from all networks transparently. All routed messages will
950 be sent as normal, so if a user on one network knows that you are a
951 gateway for another network, he can still still send a talk/announce
952 etc message via your node and it will be routed across.
955 If you use isolate on a node connection you will continue to receive
956 all information from the isolated partner, however you will not pass
957 any information back to the isolated node. There are times when you
958 would like to forward only spots across a link (maybe during a contest
959 for example). To do this, isolate the node in the normal way and use
960 an acc/spot >call< all filter to override the isolate.
967 In the /spider/msg directory you will find a file called
968 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
969 original looks something like this ....
973 # the list of regexes for messages that we won't store having
974 # received them (bear in mind that we must receive them fully before
978 # The format of each line is as follows
980 # type source pattern
981 # P/B/F T/F/O/S regex
983 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
984 # source: T - to field, F - from field, O - origin, S - subject
985 # pattern: a perl regex on the field requested
987 # Currently only type B and P msgs are affected by this code.
989 # The list is read from the top down, the first pattern that matches
990 # causes the action to be taken.
992 # The pattern can be undef or 0 in which case it will always be selected
993 # for the action specified
1004 I think this is fairly self explanatory. It is simply a list of
1005 subject headers that we do not want to pass on to either the users of
1006 the cluster or the other cluster nodes that we are linked to. This is
1007 usually because of rules and regulations pertaining to items for sale
1008 etc in a particular country.
1012 2.2. Filtering words from text fields in Announce, Talk and DX spots
1014 From version 1.48 onwards the interface to this has changed. You can
1015 now use the commands set/badword to add words that you are not
1016 prepared to see on the cluster, unset/badword to allow that word again
1017 and show/badword to list the words that you have set.
1020 If you have a previous /spider/data/badwords, the first time you start
1021 the node, it will read and convert this file to the new commands. The
1022 old style file will then be removed.
1025 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
1028 There are a number of commands that control whether a spot progresses
1029 any further by regarding it as "bad" in some way.
1032 A DX Spot has a number of fields which can be checked to see whether
1033 they contain "bad" values, they are: the DX callsign itself, the
1034 Spotter and the Originating Node.
1037 There are a set of commands which allow the sysop to control whether a
1048 These work in the same as the set/badword command, you can add any
1049 words or callsigns or whatever to the appropriate database. For
1050 example, to stop a spot from a particular node you do:
1054 set/badnode gb7djk gb7dxc
1062 set/badspotter b0mb p1rat nocall
1070 set/baddx video wsjt
1074 You can remove a word using the appropriate unset command
1075 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1076 of show/baddx, show/badspotter and show/badnode.
1082 DXSpider deals seamlessly with standard AK1A type mail. It supports
1083 both personal and bulletin mail and the sysop has additional commands
1084 to ensure that mail gets to where it is meant. DXSpider will send
1085 mail almost immediately, assuming that the target is on line.
1086 However, only one mail message is dealt with at any one time. If a
1087 mail message is already being sent or recieved, then the new message
1088 will be queued until it has finished.
1090 The cluster mail is automatically deleted after 30 days unless the
1091 sysop sets the "keep" flag using the msg command.
1096 Personal mail is sent using the sp command. This is actually the
1097 default method of sending mail and so a simple s for send will do. A
1098 full list of the send commands and options is in the command set
1099 section, so I will not duplicate them here.
1104 Bulletin mail is sent by using the sb command. This is one of the
1105 most common mistakes users make when sending mail. They send a
1106 bulletin mail with s or sp instead of sb and of course the message
1107 never leaves the cluster. This can be rectified by the sysop by using
1111 Bulletin addresses can be set using the Forward.pl file.
1116 DXSpider receives all and any mail sent to it without any alterations
1117 needed in files. Because personal and bulletin mail are treated
1118 differently, there is no need for a list of accepted bulletin
1119 addresses. It is necessary, however, to tell the program which links
1120 accept which bulletins. For example, it is pointless sending
1121 bulletins addresses to "UK" to any links other than UK ones. The file
1122 that does this is called forward.pl and lives in /spider/msg. At
1123 default, like other spider files it is named forward.pl.issue. Rename
1124 it to forward.pl and edit the file to match your requirements. The
1130 # this is an example message forwarding file for the system
1132 # The format of each line is as follows
1134 # type to/from/at pattern action destinations
1135 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1137 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1138 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1139 # pattern: a perl regex on the field requested
1140 # action: I - ignore, F - forward
1141 # destinations: a reference to an array containing node callsigns
1143 # if it is non-private and isn't in here then it won't get forwarded
1145 # Currently only type B msgs are affected by this code.
1147 # The list is read from the top down, the first pattern that matches
1148 # causes the action to be taken.
1150 # The pattern can be undef or 0 in which case it will always be selected
1151 # for the action specified
1153 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1154 # pattern) then it will always be forwarded to every node that doesn't have
1155 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1156 # you allow a new link with this on EVERY bull will be forwarded immediately
1157 # on first connection)
1167 Simply insert a bulletin address and state in the brackets where you
1168 wish that mail to go. For example, you can see here that mail sent to
1169 "UK" will only be sent to the UK links and not to PA4AB-14.
1172 To force the cluster to reread the file use load/forward
1175 NB: If a user tries to send mail to a bulletin address that does not
1176 exist in this file, they will get an error.
1179 3.4. The msg command
1181 The msg command is a very powerful and flexible tool for the sysop.
1182 It allows the sysop to alter to and from fields and make other changes
1183 to manage the cluster mail.
1185 Here is a full list of the various options ...
1189 MSG TO <msgno> <call> - change TO callsign to <call>
1190 MSG FRom <msgno> <call> - change FROM callsign to <call>
1191 MSG PRrivate <msgno> - set private flag
1192 MSG NOPRrivate <msgno> - unset private flag
1193 MSG RR <msgno> - set RR flag
1194 MSG NORR <msgno> - unset RR flag
1195 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1196 MSG NOKEep <msgno> - unset the keep flag
1197 MSG SUbject <msgno> <new> - change the subject to <new>
1198 MSG WAittime <msgno> - remove any waiting time for this message
1199 MSG NOREad <msgno> - mark message as unread
1200 MSG REad <msgno> - mark message as read
1201 MSG QUeue - queue any outstanding bulletins
1202 MSG QUeue 1 - queue any outstanding private messages
1206 These commands are simply typed from within the cluster as the sysop
1212 You can check on a message from within the cluster by using the
1213 command stat/msg. This will give you additional information on the
1214 message number including which nodes have received it, which node it
1215 was received from and when etc. Here is an example of the output of
1220 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1223 Msg Time: 26-Jan-2001 1302Z
1227 Subject: AMSAT 2line KEPS 01025.AMSAT
1229 Got it Nodes: GB7BAA, GB7ADX
1233 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1239 This is described in the section on Other filters so I will not
1243 3.7. Distribution lists
1245 Distribution lists are simply a list of users to send certain types of
1246 mail to. An example of this is mail you only wish to send to other
1247 sysops. In /spider/msg there is a directory called distro. You put
1248 any distibution lists in here. For example, here is a file called
1249 SYSOP.pl that caters for the UK sysops.
1252 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1253 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1254 GB7DXK GB7DXI GB7DXS)
1258 Any mail sent to "sysop" would only be sent to the callsigns in this
1264 Spider provides a simple BBS interface. No input is required from the
1265 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1266 and pushes any required mail to the cluster. No mail can flow from
1267 Spider to the BBS, the interface is one-way.
1270 Please be careful not to flood the cluster network with unnecessary
1271 mail. Make sure you only send mail to the clusters that want it by
1272 using the Forward.pl file very carefully.
1277 From 1.48 onwards it will become increasingly possible to control
1278 DXSpider's operation with scripts of various kinds.
1281 The directory /spider/scripts is where it all happens and is used for
1282 several things. Firstly it contains a file called startup that can be
1283 used to call in any changes to the cluster from the default settings
1284 on startup. This script is executed immediately after all
1285 initialisation of the node is done but before any connections are
1286 possible. Examples of this include how many spots it is possible to
1287 get with the sh/dx command, whether you want registration/passwords to
1288 be permanently on etc. An example file is shown below and is included
1289 in the distribution as startup.issue.
1294 # startup script example
1296 # set maximum no of spots allowed to 100
1297 # set/var $Spot::maxspots = 100
1299 # Set registration on
1300 # set/var $main::reqreg = 1
1303 # set/var $main::passwdreq = 1
1308 As usual, any text behind a # is treated as a comment and not read.
1309 To use this file, simply rename it from startup.issue to startup. In
1310 our example above there are three options. The first option is the
1311 amount of spots that a user can request with the sh/dx command.
1312 Normally the default is to give 10 spots unless the user specifies
1313 more. Without this line enabled, the maximum a user can request is
1314 100 spots. Depending on your link quality you may wish to enable more
1315 or less by specifying the number.
1318 The other 2 options are dealt with more fully in the security section.
1321 Secondly, it is used to store the login scripts for users and nodes.
1322 Currently this can only be done by the sysop but it is envisaged that
1323 eventually users will be able to set their own. An example is
1324 included in the distibution but here is a further example.
1341 The lines in between commands can simply insert a blank line or a
1342 character such as a + sign to make the output easier to read. Simply
1343 create this script with your favourite editor and save it with the
1344 callsign of the user as the filename. Filenames should always be in
1348 Commands can be inserted in the same way for nodes. A node may wish a
1349 series of commands to be issued on login, such as a merge command for
1353 Thirdly, there are 2 default scripts for users and nodes who do not
1354 have a specifically defined script. These are user_default and
1360 Spider allows the creation of local or remote databases. It supports
1361 chained databases, allowing several different databases to be scanned
1362 with one simple command. Importing of databases is limited at present
1363 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1364 database but will expand with time.
1367 5.1. Creating databases
1369 Creating a database could not be more simple. All the commands are
1370 sent from the cluster prompt as the sysop user.
1372 To create a database you use the command dbcreate. It can be used in
1373 3 different ways like so ..
1380 To simply create a database locally, you just tell the command the
1381 name of the database. This does not create the actual database, it
1382 simply defines it to say that it exists.
1386 dbcreate <name> chain <name> [<name>...]
1390 This creates a chained database entry. The first database will be
1391 scanned, then the second, the third etc...
1395 dbcreate <name> remote <name>
1399 This creates a remote entry. the first name field is the database
1400 name at the remote node, then the remote switch, then the actual
1401 node_call of the remote node, for example...
1405 dbcreate buckmaster remote gb7dxc
1409 Remote databases cannot be chained, however, the last database in a
1410 chain can be a remote database.
1413 5.2. Importing databases
1415 The only databases that Spider can currently import are the standard
1416 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1417 This will be added to with time.
1419 To import such a database, first put the file somewhere useful like
1420 /tmp and then issue the following command ...
1424 dbimport oblast /tmp/OBLAST.FUL
1428 This will update the existing local oblast database or create it if it
1432 5.3. Checking available databases
1434 Once a database is created, you will want to check that it has been
1435 added. To do this use the dbavail command. This will output the
1436 available databases. For example ...
1441 DB Name Location Chain
1445 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1449 5.4. Looking up databases
1451 To look for information in a defined database, simply use the dbshow
1452 command, for example ...
1456 dbshow buckmaster G0YLM
1460 will show the information for the callsign G0YLM from the buckmaster
1461 database if it exists. To make things more standard for the users you
1462 can add an entry in the Aliases file so that it looks like a standard
1463 show command like this ...
1467 Now you can simply use show/buckmaster or an abreviation.
1470 5.5. Removing databases
1472 To delete an existing database you use the dbremove command. For
1481 would remove the oblast database and its associated datafile from the
1482 system. There are no warnings or recovery possible from this command.
1483 If you remove a database it ceases to exist and would have to be
1484 created from scratch if you still required it.
1487 6. Information, files and useful programs
1491 One of the more important things a cluster sysop needs to do is to get
1492 information to his users. The simplest way to do this is to have a
1493 banner that is sent to the user on login. This is know as a "message
1494 of the day" or "motd". To set this up, simply create a file in
1495 /spider/data called motd and edit it to say whatever you want. It is
1496 purely a text file and will be sent automatically to anyone logging in
1500 This message of the day file lives in the same directory as the
1501 standard motd file but is only sent to non-registered users. Once
1502 registered they will receive the same message as any other user.
1505 6.3. Downtime message
1507 If for any reason the cluster is down, maybe for upgrade or
1508 maintenance but the machine is still running, a message can be sent to
1509 the user advising them of the fact. This message lives in the
1510 /spider/data directory and is called "offline". Simply create the
1511 file and edit it to say whatever you wish. This file will be sent to
1512 a user attempting to log into the cluster when DXSpider is not
1516 6.4. Other text messages
1518 You can set other text messages to be read by the user if they input
1519 the file name. This could be for news items or maybe information for
1520 new users. To set this up, make a directory under /spider called
1521 packclus. Under this directory you can create files called news or
1522 newuser for example. In fact you can create files with any names you
1523 like. These can be listed by the user with the command ....
1531 They can be read by the user by typing the command ....
1539 If the file they want to read is called news. You could also set an
1540 alias for this in the Alias file to allow them just to type news
1543 You can also store other information in this directory, either
1544 directly or nested under directories. One use for this would be to
1545 store DX bulletins such as the OPDX bulletins. These can be listed
1546 and read by the user. To keep things tidy, make a directory under
1547 /spider/packclus called bulletin. Now copy any OPDX or similar
1548 bulletins into it. These can be listed by the user in the same way as
1549 above using the show/files command with an extension for the bulletin
1550 directory you have just created, like this ....
1558 An example would look like this ....
1561 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1565 You can see that in the files area (basically the packclus directory)
1566 there is a file called news and a directory called bulletin. You can
1567 also see that dates they were created. In the case of the file news,
1568 you can also see the time it was last modified, a good clue as to
1569 whether the file has been updated since you last read it. To read the
1570 file called news you would simply issue the command ....
1578 To look what is in the bulletin directory you issue the command ....
1583 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1584 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1585 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1586 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1587 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1588 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1589 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1590 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1591 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1592 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1593 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1594 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1595 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1596 Press Enter to continue, A to abort (16 lines) >
1600 You can now read any file in this directory using the type command,
1605 type bulletin/opdx391
1606 Ohio/Penn DX Bulletin No. 391
1607 The Ohio/Penn Dx PacketCluster
1611 Editor Tedd Mirgliotta, KB8NW
1612 Provided by BARF-80 BBS Cleveland, Ohio
1613 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1614 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1615 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1616 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1617 Press Enter to continue, A to abort (508 lines) >
1621 The page length will of course depend on what you have it set to!
1624 6.5. The Aliases file
1626 You will find a file in /spider/cmd/ called Aliases. This is the file
1627 that controls what a user gets when issuing a command. It is also
1628 possible to create your own aliases for databases and files you create
1632 You should not alter the original file in /spider/cmd/ but create a
1633 new file with the same name in /spider/local_cmd. This means that any
1634 new Aliases files that is downloaded will not overwrite your self
1635 created Aliases and also that you do not override any new Aliases with
1636 your copy in /spider/local_cmd/. You must remember that any files you
1637 store in /spider/local/ or /spider/local_cmd override the originals if
1638 the same lines are used in both files.
1641 The best way of dealing with all this then is to only put your own
1642 locally created Aliases in the copy in /spider/local_cmd. The example
1643 below is currently in use at GB7MBC.
1648 # Local Aliases File
1655 '^news$', 'type news', 'type',
1658 '^sh\w*/buck$', 'show/qrz', 'show',
1659 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1660 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1661 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1662 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1668 Each alphabetical section should be preceded by the initial letter and
1669 the section should be wrapped in square brackets as you can see. The
1670 syntax is straightforward. The first section on each line is the new
1671 command that will be allowed once the alias is included. The second
1672 section is the command it is replacing and the last section is the
1673 actual command that is being used.
1676 The eagle-eyed amongst you will have noticed that in the first
1677 section, the new alias command has a '^' at the start and a '$' at the
1678 end. Basically these force a perfect match on the alias. The '^'
1679 says match the beginning exactly and the with similar commands.
1682 I have 3 different types of alias in this file. At the top is an
1683 alias for 'news'. This is a file I have created in the
1684 /spider/packclus/ directory where I can inform users of new
1685 developments or points of interest. In it's initial form a user would
1686 have to use the command type news. The alias allows them to simply
1687 type news to get the info. Second is an alias for the show/qrz
1688 command so that those users used to the original show/buck command in
1689 AK1A will not get an error, and the rest of the lines are for locally
1690 created databases so that a user can type show/hftest instead of
1691 having to use the command dbshow hftest which is not as intuitive.
1694 This file is just an example and you should edit it to your own
1695 requirements. Once created, simply issue the command load/alias at
1696 the cluster prompt as the sysop user and the aliases should be
1703 In later versions of Spider a simple console program is provided for
1704 the sysop. This has a type ahead buffer with line editing facilities
1705 and colour for spots, announces etc. To use this program, simply use
1706 console.pl instead of client.
1709 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1710 edit the file with your favourite editor.
1713 6.7. Updating kepler data
1715 Spider has a powerful and flexible show/satellite command. In order
1716 for this to be accurate, the kepler data has to be updated regularly.
1717 In general, this data is available as an email or via cluster mail.
1718 Updating it is simple. First you need to export the mail message as a
1719 file. You do this with the export command from the cluster prompt as
1720 the sysop. For example ...
1724 export 5467 /spider/perl/keps.in
1728 would export message number 5467 as a file called keps.in in the
1729 /spider/perl directory.
1732 Now login to a VT as sysop and cd /spider/perl. There is a command in
1733 the perl directory called convkeps.pl. All we need to do now is
1734 convert the file like so ...
1738 ./convkeps.pl keps.in
1742 Now go back to the cluster and issue the command ...
1750 That is it! the kepler data has been updated.
1753 6.8. The QRZ callbook
1755 The command sh/qrz will only work once you have followed a few simple
1756 steps. First you need to get a user ID and password from qrz.com.
1757 Simply go to the site and create one. Secondly you need to copy the
1758 file /spider/perl/Internet.pm to /spider/local and alter it to match
1759 your user ID and password. You also at this point need to set
1760 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1761 proprieter of qrz.com for allowing this access.
1764 6.9. Connecting logging programs
1766 There appear to be very few logging programs out there that support
1767 telnet especially the popular ones like LogEQF, Turbolog etc. This
1768 can make it difficult to connect to your own cluster! The way to do
1769 it is to make the logging program think it has a TNC attached to a com
1770 port on the logging PC and 'push' a linux login out to it. This is
1771 achieved very simply by the use of agetty.
1774 All that is required is to add a line in /etc/inittab to have the
1775 client ready for a connection on the com port of your choice.
1776 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1781 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1785 Add this after the standard runlevel lines in /etc/inittab. The above
1786 line works on ttyS1 (com2). Now as root, issue the command telinit q
1787 and it should be ready for connection. All that is required is a 3
1788 wire serial lead (tx, rx and signal ground). Tell you logging program
1789 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1790 Login as normal and then telnet from there to the cluster.
1795 In the spider tree will be a directory spider-web. This is a neat
1796 little java web applet that can be run from a website. The applet
1797 must run on the same machine as the cluster. The included README file
1801 I should comment here that the applet is precompiled, that is, ready
1802 to go. It was compiled using JDK1.3.1. If your version is earlier
1803 than this then it may not work. Should that be the case you need to
1804 recompile or update your JDK. To recompile do the following ...
1808 cd /spider/spider-web
1810 /usr/bin/javac spiderclient.java
1814 I have used /usr/bin/javac as an example, your path to javac may be
1820 Completely based on a clx web client written in Java by dl6dbh
1821 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1823 The webserver has to run on the same machine as your DxSpider software!
1825 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1827 Installation instructions (Performed as root):
1829 Put all the files in the spider-web directory into a newly created directory
1830 under the DocumentRoot of your websever for instance 'client'. In my case
1831 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1832 path should be /usr/local/httpd/htdocs/client/ for example.
1834 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1835 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1836 /usr/local/httpd/cgi-bin/ for example.
1838 Change the permissions of the files to ensure they are correct, obviously you
1839 will need to use the correct path the the files according to your system:
1841 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1842 chmod -R 755 /home/httpd/html/client/
1844 By default the spider.cgi script should pick up your hostname (As long as this
1845 is set correctly). If it does not or your hostname differs from the name that
1846 you attach to the public address that you are using, then edit spider.cgi :
1848 # Uncomment and set the hostname manually here if the above fails.
1849 # $HOSTNAME = "gb7mbc.spoo.org" ;
1853 telnet (see Listeners.pm)
1855 NOTE: If you can start the console but cannot connect to the cluster from it,
1856 then it is possible that the machine you are on cannot resolve the hostname of
1857 your cluster machine. If this is the case, you need to set your hostname
1860 You also need to set the $NODECALL variable. This prints the name of your
1861 choosing (probably your cluster callsign) on the html page.
1863 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1867 8. Web based statistics
1869 From version 1.50, you can use the freeware software MRTG to produce
1870 really nice graphical statistics on your web site. For an example try
1871 http://www.gb7mbc.net/mrtg/stats.html.
1874 The following should help you get it all working.
1877 First you need to download the latest version of MRTG from
1878 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1879 the following files..
1883 libpng-1.0.14.tar.gz
1889 Login to your machine as the root user, put all the downloaded files
1890 in /usr/local/src/ (or wherever you prefer) and untar and compile
1891 them. All the information to compile and install these sources come
1892 with them. After compilation and installation, you will find MRTG in
1896 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1900 You now need to make 2 symbolic links like below...
1904 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1905 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1909 Now login to the cluster with your sysop callsign and run the command
1913 Now you are nearly there! Login as the sysop user and change to the
1914 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1919 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1923 Changing the callsign for your own cluster callsign of course!
1926 And finally you need to login as the root user and create one last
1927 symbolic link. Where this points will depend on where your html
1928 documents are kept. For RedHat systems you use...
1932 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1936 and for SuSE systems...
1940 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1944 If you now point your browser to your website as below it should all
1949 http://www.xxx.xxx/mrtg/stats.html
1953 Of course, to get the stats to update, you need to add some
1954 information in the spider crontab file as below...
1958 # Update stats for mrtg on website
1959 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1963 This will update the site every 5 minutes.
1968 From version 1.49 DXSpider has some additional security features.
1969 These are not by any means meant to be exhaustive, however they do
1970 afford some security against piracy. These two new features can be
1971 used independently of each other or in concert to tighten the
1977 The basic principle of registration is simple. If a user is not
1978 registered by the sysop, then they have read-only access to the
1979 cluster. The only thing they can actually send is a talk or a message
1980 to the sysop. In order for them to be able to spot, send announces or
1981 talks etc the sysop must register them with the set/register command,
1990 The user g0vgs can now fully use the cluster. In order to enable
1991 registration, you can issue the command ...
1993 set/var $main::reqreg = 1
1997 Any users that are not registered will now see the motd_nor file
1998 rather than the motd file as discussed in the Information, files and
1999 useful programs section.
2002 Entering this line at the prompt will only last for the time the
2003 cluster is running of course and would not be present on a restart.
2004 To make the change permanent, add the above line to
2005 /spider/scripts/startup. To read more on the startup file, see the
2006 section on Information, files and useful programs.
2009 To unregister a user use unset/register and to show the list of
2010 registered users, use the command show/register.
2015 At the moment, passwords only affect users who login to a DXSpider
2016 cluster node via telnet. If a user requires a password, they can
2017 either set it themselves or have the sysop enter it for them by using
2018 the set/password command. Any users who already have passwords, such
2019 as remote sysops, will be asked for their passwords automatically by
2020 the cluster. Using passwords in this way means that the user has a
2021 choice on whether to have a password or not. To force the use of
2022 passwords at login, issue the command ...
2026 set/var $main::passwdreq = 1
2030 at the cluster prompt. This can also be added to the
2031 /spider/scripts/startup file as above to make the change permanent.
2034 Of course, if you do this you will have to assign a password for each
2035 of your users. If you were asking them to register, it is anticipated
2036 that you would ask them to send you a message both to ask to be
2037 registered and to give you the password they wish to use.
2040 Should a user forget their password, it can be reset by the sysop by
2041 first removing the existing password and then setting a new one like
2046 unset/password g0vgs
2047 set/password g0vgs new_password
2055 10.1. CVS from a Linux platform
2057 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2058 is held at Sourceforge. This means that it is possible to update your
2059 DXSpider installation to the latest sources by using a few simple
2060 commands. A graphical interface to CVS for Windows is explained in
2064 Please be aware that if you update your system using CVS, it is
2065 possible that you could be running code that is very beta and not
2066 fully tested. There is a possibility that it could be unstable.
2069 I am of course assuming that you have a machine with both DXSpider and
2070 Internet access running.
2073 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2074 ENTIRE SPIDER TREE!!
2077 Assuming you are connected to the Internet, you need to login to the
2078 CVS repository and then update your Spider source. There are several
2079 steps which are listed below ...
2082 First login as the user sysop. Next you need to connect to the CVS
2083 repository. You do this with the command below ...
2086 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2090 You will get a password prompt. Simply hit return here and your
2091 machine should return to a normal linux prompt.
2094 What happens next depends on whether you have an existing installation
2095 that you want to update with the latest and greatest or whether you
2096 just want to see what is there and/or run it on a new machine for
2099 If you are installing Spider from CVS then change directory to
2102 If you are wanting to update Spider then cd to /tmp
2105 The next step will create a brand new 'spider' directory in your
2109 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2113 This command is all on one line.
2116 Hopefully your screen should show you downloading files. The -z3
2117 simply compresses the download to improve speed. When this has
2118 finished, you will have exactly the same as if you had untarred a full
2119 tarball PLUS some extra directories and files that CVS needs to do the
2121 Now if you are doing a new installation, that's it. Carry on as if
2122 you have just downloaded and untarred the lastest tarball.
2125 If you want to upgrade your current installation then do this ...
2129 tar cvfz /tmp/s.tgz spider
2131 tar xvfzp /tmp/s.tgz
2135 This is assuming you downloaded to the /tmp directory of course.
2138 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2139 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2142 Remember to recompile the C client (cd /spider/src; make)
2145 At this point the files have been upgraded. You can (usually) restart
2146 the cluster in your own time. However, if you attempt to use any new
2147 commands or features expect it to be fatal! At least your cluster
2148 will have been restarted then so it will be too late to worry about
2152 Now the magic part! From now on when you want to update, simply
2153 connect to the Internet and then, as the user sysop ...
2162 and your files will be updated. As above, remember to recompile the
2163 "C" client if it has been updated (CVS will tell you) and restart if
2164 any of the perl scripts have been altered or added, again, CVS will
2168 You will find any changes documented in the /spider/Changes file.
2171 10.2. CVS from a Windows platform
2173 After the initial setup, an update to your DXSpider software is no
2174 more than a couple of clicks away. This section is intended to
2175 explain and illustrate the use of the WinCVS application to update
2176 your DXSpider software. The current stable version of WinCVS is Ver.
2177 1.2. You can get this software at:
2179 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2181 Pick your download mirror and then install WinCVS after the download
2185 In this next section I have included a series of links to .jpg files
2186 to take advantage of the picture and 1000 words equivalency. The .jpg
2187 files are in the C:\spider\html directory. If someone using a Linux
2188 system is reading this section from boredom, the files are in
2189 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2190 of gcvs and do your updates graphically as opposed to from the command
2191 line. The following descriptions are almost identical between WinCvs
2192 and gcvs. The following screen shots have duplicate links, depending
2193 upon whether you are viewing this information under the Windows or
2194 Linux operating system.
2196 When WinCVS is installed, running, and you are connected to the
2197 internet, the initial screen looks like:
2201 If you want, you can also look at these .jpg files with another viewer
2202 that might provide some better clarity to the image. On the left is
2203 the directory tree for your hard disk. Notice that the spider
2204 directory has a gray highlight.
2206 To start configuring WinCVS, click on Admin at the top of the screen
2207 and then Preferences. This should get you:
2211 In the top line for CVSROOT, enter:
2214 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2221 "passwd" file on the cvs server
2225 for Authentication on the General tab.
2227 Next, move to the right to the Ports tab.
2231 In here, check the box on the second line down for the "pserver" port.
2232 Enter a port number of 2401.
2234 Finally, go to the WinCvs tab all the way to the right.
2238 Enter Notepad as the viewer to open files. For the HOME folder, put
2239 "C:\spider" and click OK because the configuration is now complete.
2241 You are now ready to upgrade your copy of DXSpider. Click on the
2242 greyed Spider folder shown in the directory tree on the left of the
2243 WinCVS display. Two things should happen. The Spider folder will be
2244 selected and the greyed-out arrow located just below the word Query in
2245 the top line will turn to solid green.
2247 For anyone using gcvs under Linux, the green arrow is located on the
2248 extreme left of the display, under the word File. A gcvs screen looks
2253 Click on the now green arrow to start the download process. An Update
2254 Settings box will be displayed to which you can simply say OK.
2258 For future reference, the Update Settings box is the place where you
2259 can enter information to revert to a prior version of DXSpider.
2260 Information on reverting to a Before Date is contained in the WinCVS
2263 After a short period of time, a series of file names will scroll by in
2264 the lower pane of the WinCVS window. Eventually you should see
2267 *****CVS exited normally with code 0*****
2271 appear in the lower pane. You're done. The updated files are in
2272 place ready for you to stop and then restart your DXSpider. After the
2273 restart, you're running with the latest version of DXSpider.
2277 To paraphrase from the CVS section... Now the magic part! From now on
2278 when you want to update, simply connect to the Internet and start
2282 Click on the greyed-out Spider directory in the left screen
2283 Click on the green down arrow
2284 Click OK on the Update Settings dialog box
2285 Restart your Spider software
2289 11. The DXSpider command set
2293 accept Set a filter to accept something
2295 Create a filter to accept somethingThere are 2 types of filter, accept
2296 and reject. See HELP FILTERING for moreinfo.
2298 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
2300 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2303 This version allows a sysop to set a filter for a callsign as well as
2304 thedefault for nodes and users eg:-
2307 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2311 11.3. accept/announce [0-9] <pattern> (0)
2313 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2316 Create an 'accept this announce' line for a filter. An accept filter
2317 line means that if the announce matches this filter it ispassed onto
2318 the user. See HELP FILTERING for more info. Please read thisto
2319 understand how filters work - it will save a lot of grief later on.You
2320 can use any of the following things in this line:-
2323 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)
2330 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)
2344 acc/ann by_state va,nh,ri,nh
2348 You can use the tag 'all' to accept everything eg:
2355 but this probably for advanced users...
2357 11.4. accept/route <call> [0-9] <pattern> (8)
2359 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2362 Create an 'accept this routing PC Protocol' line for a filter. An
2363 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2364 filter it is passed thru that interface. See HELP FILTERING for more
2365 info. Please read thisto understand how filters work - it will save a
2366 lot of grief later on.You can use any of the following things in this
2370 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
2377 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2381 you can now use 'by' as a synonym for 'call' so:
2384 by = call by_dxcc = call_dxcc
2388 and so onYou can use the tag 'all' to accept everything eg:
2395 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
2397 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2399 This version allows a sysop to set a filter for a callsign as well as
2400 thedefault for nodes and users eg:-
2403 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2407 accept/spot user_default by G,M,2
2411 11.6. accept/spots [0-9] <pattern> (0)
2413 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2415 Create an 'accept this spot' line for a filter. An accept filter line
2416 means that if the spot matches this filter it ispassed onto the user.
2417 See HELP FILTERING for more info. Please read thisto understand how
2418 filters work - it will save a lot of grief later on.You can use any of
2419 the following things in this line:-
2422 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>
2426 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2430 You can use the tag 'all' to accept everything, eg:
2440 acc/spots by_state VA,NH,RI,MA,ME
2444 but this probably for advanced users...
2446 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
2448 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2450 This version allows a sysop to set a filter for a callsign as well as
2451 thedefault for nodes and users eg:-
2454 accept/wcy node_default all set/hops node_default 10
2458 11.8. accept/wcy [0-9] <pattern> (0)
2460 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2462 It is unlikely that you will want to do this, but if you do then you
2463 canfilter on the following fields:-
2466 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>
2470 There are no examples because WCY Broadcasts only come from one place
2471 andyou either want them or not (see UNSET/WCY if you don't want
2472 them).This command is really provided for future use.See HELP FILTER
2475 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
2477 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2479 This version allows a sysop to set a filter for a callsign as well as
2480 thedefault for nodes and users eg:-
2483 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2487 accept/wwv user_default by W,K
2491 11.10. accept/wwv [0-9] <pattern> (0)
2493 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2495 It is unlikely that you will want to do this, but if you do then you
2496 canfilter on the following fields:-
2499 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>
2506 accept/wwv by_zone 4
2510 is probably the only useful thing to do (which will only show WWV
2511 broadcastsby stations in the US).See HELP FILTER for information.
2513 11.11. announce <text> (0)
2515 announce <text> Send an announcement to LOCAL users only
2517 <text> is the text of the announcement you wish to broadcast
2519 11.12. announce full <text> (0)
2521 announce full <text> Send an announcement cluster wide
2523 This will send your announcement cluster wide
2525 11.13. announce sysop <text> (5)
2527 announce sysop <text> Send an announcement to Sysops only
2530 11.14. apropos <string> (0)
2532 apropos <string> Search help database for <string>
2534 Search the help database for <string> (it isn't case sensitive), and
2535 printthe names of all the commands that may be relevant.
2537 11.15. blank [<string>] [<nn>] (0)
2539 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2541 In its basic form this command prints one or more blank lines. However
2542 ifyou pass it a string it will replicate the string for the width of
2543 the screen (default 80) and then print that one or more times, so:
2550 prints two blank lines
2557 prints a row of - characters once.
2564 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2565 script file and you can print a maximumof 9 lines.
2569 bye Exit from the cluster
2571 This will disconnect you from the cluster
2573 11.17. catchup <node call> all|[<msgno> ...] (5)
2575 catchup <node call> all|[<msgno> ...] Mark a message as sent
2578 11.18. chat <group> <text> (0)
2580 chat <group> <text> Chat or Conference to a group
2582 It is now possible to JOIN a group and have network wide conferencing
2583 to thatgroup. DXSpider does not (and probably will not) implement the
2584 AK1A conference mode as this seems very limiting, is hardly used and
2585 doesn't seemto work too well anyway.This system uses the existing ANN
2586 system and is compatible with both otherDXSpider nodes and AK1A
2587 clusters (they use ANN/<group>). You can be a member of as many
2588 "groups" as you want. To join a group type:-
2591 JOIN FOC (where FOC is the group name)
2595 To leave a group type:-
2602 You can see which groups you are in by typing:-
2609 and you can see whether your mate is in the group, if he connects to
2610 thesame node as you, by typing:-
2617 To send a message to a group type:-
2620 CHAT FOC hello everyone
2627 CH #9000 hello I am back
2630 See also JOIN, LEAVE, SHOW/CHAT
2632 11.19. clear/announce <callsign> [input] [0-9|all] (8)
2634 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2637 A sysop can clear an input or normal output filter for a user or
2638 thenode_default or user_default.
2640 11.20. clear/announce [1|all] (0)
2642 clear/announce [1|all] Clear a announce filter line
2644 This command allows you to clear (remove) a line in a annouce filter
2645 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2648 11.21. clear/route <callsign> [input] [0-9|all] (8)
2650 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2652 A sysop can clear an input or normal output filter for a user or
2653 thenode_default or user_default.
2655 11.22. clear/route [1|all] (0)
2657 clear/route [1|all] Clear a route filter line
2659 This command allows you to clear (remove) a line in a route filter or
2660 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2663 11.23. clear/spots <callsign> [input] [0-9|all] (8)
2665 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2667 A sysop can clear an input or normal output filter for a user or
2668 thenode_default or user_default.
2670 11.24. clear/spots [0-9|all] (0)
2672 clear/spots [0-9|all] Clear a spot filter line
2674 This command allows you to clear (remove) a line in a spot filter or
2675 to remove the whole filter.If you have a filter:-
2678 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2689 you will be left with:-
2692 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2703 the filter will be completely removed.
2705 11.25. clear/wcy <callsign> [input] [0-9|all] (8)
2707 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2709 A sysop can clear an input or normal output filter for a user or
2710 thenode_default or user_default.
2712 11.26. clear/wcy [1|all] (0)
2714 clear/wcy [1|all] Clear a WCY filter line
2716 This command allows you to clear (remove) a line in a WCY filter or to
2717 remove the whole filter.see CLEAR/SPOTS for a more detailed
2720 11.27. clear/wwv <callsign> [input] [0-9|all] (8)
2722 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2724 A sysop can clear an input or normal output filter for a user or
2725 thenode_default or user_default.
2727 11.28. clear/wwv [1|all] (0)
2729 clear/wwv [1|all] Clear a WWV filter line
2731 This command allows you to clear (remove) a line in a WWV filter or to
2732 remove the whole filter.see CLEAR/SPOTS for a more detailed
2735 11.29. connect <callsign> (5)
2737 connect <callsign> Start a connection to another DX Cluster
2739 Start a connection process that will culminate in a new connection to
2740 theDX cluster <callsign>. This process creates a new 'client' process
2741 which willuse the script in /spider/connect/<callsign> to effect the
2742 'chat' exchangenecessary to traverse the network(s) to logon to the
2747 dbavail Show a list of all the Databases in the system
2749 Title says it all really, this command lists all the databases
2750 definedin the system. It is also aliased to SHOW/COMMAND.
2752 11.31. dbcreate <name> (9)
2754 dbcreate <name> Create a database entry
2757 11.32. dbcreate <name> chain <name> [<name>..] (9)
2759 dbcreate <name> chain <name> [<name>..] Create a chained database
2762 11.33. dbcreate <name> cmd <dxspider command> (9)
2764 dbcreate <name> cmd <dxspider command> make a local command available
2767 DBCREATE allows you to define a database in the system. It doesn't
2768 actuallycreate anything, just defines it.The databases that are
2769 created are simple DB_File hash databases, they are therefore already
2770 'indexed'.You can define a local database with the first form of the
2778 You can also chain databases with the addition of the 'chain' keyword.
2779 This will search each database one after the other. A typical example
2783 DBCREATE sdx_qsl chain sql_ad
2787 No checking is done to see if the any of the chained databases exist,
2788 infact it is usually better to do the above staement first then do
2789 each ofthe chained databases.Databases can exist offsite. To define a
2790 database that lives on another node do:
2793 DBCREATE buckmaster remote gb7dxc
2797 Remote databases cannot be chained; however, the last database in a a
2798 chain can be a remote database eg:
2801 DBCREATE qsl chain gb7dxc
2805 To see what databases have been defined do:
2808 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2812 It would be normal for you to add an entry into your local Aliases
2813 fileto allow people to use the 'SHOW/<dbname>' style syntax. So you
2814 wouldneed to add a line like:-
2817 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
2828 to work as they may be used to.You can also make local commands avail-
2829 able as 'pseudo' databases. Youcan therefore make spider special com-
2830 mands available as a database. Iimagine that this will be primarily
2831 useful for remote access from legacy nodes. For example:-
2834 DBCREATE dxqsl cmd show/dxqsl
2838 You also use one of these databases in a chain. This may be useful
2839 locally. See DBIMPORT for the importing of existing AK1A format data
2840 to databases.See DBSHOW for generic database enquiry
2842 11.34. dbcreate <name> remote <node> (9)
2844 dbcreate <name> remote <node> Create a remote database entry
2847 11.35. dbimport <dbname> <filename> (9)
2849 dbimport <dbname> <filename> Import AK1A data into a database
2851 If you want to import or update data in bulk to a database you can
2852 usethis command. It will either create or update entries into an
2853 existingdatabase. For example:-
2856 DBIMPORT oblast /tmp/OBLAST.FUL
2860 will import the standard OBLAST database that comes with AK1A into
2861 theoblast database held locally.
2863 11.36. dbremove <dbname> (9)
2865 dbremove <dbname> Delete a database
2867 DBREMOVE will completely remove a database entry and also delete any
2868 datafile that is associated with it. There is no warning, no comeback,
2869 no safety net. For example:
2876 will remove the oblast database from the system and it will also
2877 removethe associated datafile.I repeat:There is no warning, no come-
2878 back, no safety net.You have been warned.
2880 11.37. dbshow <dbname> <key> (0)
2882 dbshow <dbname> <key> Display an entry, if it exists, in a database
2884 This is the generic user interface to the database to the database
2885 system.It is expected that the sysop will add an entry to the local
2886 Aliases fileso that users can use the more familiar AK1A style of
2894 but if he hasn't and the database really does exist (use DBAVAIL
2895 orSHOW/COMMAND to find out) you can do the same thing with:
2904 debug Set the cluster program into debug mode
2906 Executing this command will only have an effect if you are running the
2907 clusterin debug mode i.e.
2914 It will interrupt the cluster just after the debug command has fin-
2917 11.39. delete/usdb <callsign> ... (9)
2919 delete/usdb <callsign> ... Delete this user from the US State Database
2921 This command will completely remove a one or more callsignsfrom the US
2922 States database.There is NO SECOND CHANCE.It goes without saying that
2923 you should use this command CAREFULLY!Note that these callsign may be
2924 re-instated by any weekly updates from the FCC.
2926 11.40. delete/user <callsign> ... (9)
2928 delete/user <callsign> ... Delete this user from the User Database
2930 This command will completely remove a one or more users from the
2931 database.There is NO SECOND CHANCE.It goes without saying that you
2932 should use this command CAREFULLY!
2934 11.41. demonstrate <call> <command> (9)
2936 demonstrate <call> <command> Demonstrate a command to another user
2938 This command is provided so that sysops can demonstrate commands to
2939 other users. It runs a command as though that user had typed it in
2940 andthen sends the output to that user, together with the command that
2944 DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
2948 Note that this command is similar to SPOOF and will have the same
2949 sideeffects. Commands are run at the privilege of the user which is
2950 beingdemonstrated to.
2952 11.42. directory (0)
2954 directory List messages
2958 11.43. directory <from>-<to> (0)
2960 directory <from>-<to> List messages <from> message <to> message
2962 List the messages in the messages directory.If there is a 'p' one
2963 space after the message number then it is a personal message. If there
2964 is a '-' between the message number and the'p' then this indicates
2965 that the message has been read.You can use shell escape characters
2966 such as '*' and '?' in the <call>fields.You can combine some of the
2967 various directory commands together eg:-
2977 DIR SUBJECT IOTA 200-250
2981 You can abbreviate all the commands to one letter and use ak1a syn-
2985 DIR/T G1* 10 DIR/S QSL 10-100 5
2989 11.44. directory <nn> (0)
2991 directory <nn> List last <nn> messages
2994 11.45. directory all (0)
2996 directory all List all messages
2999 11.46. directory from <call> (0)
3001 directory from <call> List all messages from <call>
3004 11.47. directory new (0)
3006 directory new List all new messages
3009 11.48. directory own (0)
3011 directory own List your own messages
3014 11.49. directory subject <string> (0)
3016 directory subject <string> List all messages with <string> in subject
3019 11.50. directory to <call> (0)
3021 directory to <call> List all messages to <call>
3023 11.51. directory- (5)
3027 Sysops can see all users' messages.
3029 11.52. disconnect <call> [<call> ...] (8)
3031 disconnect <call> [<call> ...] Disconnect a user or cluster
3033 Disconnect any <call> connected locally
3035 11.53. dx [by <call>] <freq> <call> <remarks> (0)
3037 dx [by <call>] <freq> <call> <remarks> Send a DX spot
3039 This is how you send a DX Spot to other users. You can, in fact,
3040 nowenter the <freq> and the <call> either way round.
3043 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
3047 will all give the same result. You can add some remarks to the endof
3048 the command and they will be added to the spot.
3051 DX FR0G 144600 this is a test
3055 You can credit someone else by saying:-
3058 DX by G1TLH FR0G 144.600 he isn't on the cluster
3062 The <freq> is compared against the available bands set up in the clus-
3063 ter. See SHOW/BANDS for more information.
3065 11.54. echo <line> (0)
3067 echo <line> Echo the line to the output
3069 This command is useful in scripts and so forth for printing theline
3070 that you give to the command to the output. You can use thisin
3071 user_default scripts and the SAVE command for titling and so forthThe
3072 script will interpret certain standard "escape" sequences as follows:-
3075 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
3079 So the following example:-
3082 echo GB7DJK is a dxcluster
3089 GB7DJK is a dxcluster
3093 on the output. You don't need a \n on the end of the line you want to
3094 send.A more complex example:-
3097 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
3104 GB7DJK g1tlh Dirk g3xvf Richard
3110 11.55. export <msgno> <filename> (9)
3112 export <msgno> <filename> Export a message to a file
3114 Export a message to a file. This command can only be executed on a
3115 localconsole with a fully privileged user. The file produced will be
3116 in a formready to be imported back into the cluster by placing it in
3117 the import directory (/spider/msg/import).This command cannot
3118 overwrite an existing file. This is to provide some measure of
3119 security. Any files written will owned by the same user as the main
3120 cluster, otherwise you can put the new files anywhere the cluster
3121 canaccess. For example:-
3128 11.56. export_users [<filename>] (9)
3130 export_users [<filename>] Export the users database to ascii
3132 Export the users database to a file in ascii format. If no filenameis
3133 given then it will export the file to /spider/data/user_asc.If the
3134 file already exists it will be renamed to <filename>.o. In factup to 5
3135 generations of the file can be kept each one with an extra 'o' on
3136 thesuffix. BE WARNED: this will write to any file you have write
3137 access to. No check ismade on the filename (if any) that you specify.
3139 11.57. filtering... (0)
3141 filtering... Filtering things in DXSpider
3143 There are a number of things you can filter in the DXSpider system.
3144 Theyall use the same general mechanism.In general terms you can create
3145 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
3146 You do this using, for example:-
3149 accept/spots ..... reject/spots .....
3153 where ..... are the specific commands for that type of filter. There-
3154 are filters for spots, wwv, announce, wcy and (for sysops)connects.
3155 See each different accept or reject command reference formore
3156 details.There is also a command to clear out one or more lines in a
3157 filter andone to show you what you have set. They are:-
3160 clear/spots 1 clear/spots all
3171 There is clear/xxxx command for each type of filter.For now we are
3172 going to use spots for the examples, but you can applythe principles
3173 to all types of filter.There are two main types of filter 'accept' or
3174 'reject'; which you usedepends entirely on how you look at the world
3175 and what is leastwriting to achieve what you want. Each filter has 10
3176 lines (of anylength) which are tried in order. If a line matches then
3177 the actionyou have specified is taken (ie reject means ignore it and
3178 acceptmeans gimme it).The important thing to remember is that if you
3179 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
3180 instance)) then ifa spot comes in that doesn't match any of the lines
3181 then you will getit BUT if you specify an 'accept' filter then any
3182 spots that don'tmatch are dumped. For example if I have a one line
3186 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3190 then automatically you will ONLY get VHF spots from or to CQ zones
3191 1415 and 16. If you set a reject filter like:
3194 reject/spots on hf/cw
3198 Then you will get everything EXCEPT HF CW spots, If you am interested
3199 in IOTAand will work it even on CW then you could say:-
3202 reject/spots on hf/cw and not info iota
3206 But in that case you might only be interested in iota and say:-
3209 accept/spots not on hf/cw or info iota
3213 which is exactly the same. You should choose one or the other untilyou
3214 are confortable with the way it works. Yes, you can mix them(actually
3215 you can have an accept AND a reject on the same line) butdon't try
3216 this at home until you can analyse the results that you getwithout
3217 ringing up the sysop for help.Another useful addition now is filtering
3219 accept/spots by_state VA,NH,RI,ME
3223 You can arrange your filter lines into logical units, either for
3224 yourown understanding or simply convenience. I have one set fre-
3228 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
3232 What this does is to ignore all HF CW spots (being a class B I
3233 can'tread any CW and couldn't possibly be interested in HF :-) and
3234 alsorejects any spots on VHF which don't either originate or spot
3235 someonein Europe.This is an exmaple where you would use the line num-
3236 ber (1 and 2 inthis case), if you leave the digit out, the system
3237 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
3238 out if you want, it is implied. You canuse any number of brackets to
3239 make the 'expression' as you wantit. There are things called prece-
3240 dence rules working here which meanthat you will NEED brackets in a
3241 situation like line 2 because,without it, will assume:-
3244 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
3248 annoying, but that is the way it is. If you use OR - usebrackets.
3249 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
3250 by_zone'.If you want to alter your filter you can just redefine one or
3251 morelines of it or clear out one line. For example:-
3254 reject/spots 1 on hf/ssb
3265 To remove the filter in its entirty:-
3272 There are similar CLEAR commands for the other filters:-
3275 clear/announce clear/wcy clear/wwv
3279 ADVANCED USERS:-Once you are happy with the results you get, you may
3280 like to experiment. my example that filters hf/cw spots and accepts
3281 vhf/uhf spots from EUcan be written with a mixed filter, eg:
3285 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)
3289 each filter slot actually has a 'reject' slot and an 'accept'slot. The
3290 reject slot is executed BEFORE the accept slot.It was mentioned ear-
3291 lier that after a reject test that doesn't match,the default for fol-
3292 lowing tests is 'accept', the reverse is true for'accept'. In the
3293 example what happens is that the reject is executedfirst, any non
3294 hf/cw spot is passed to the accept line, which letsthru everything
3295 else on HF.The next filter line lets through just VHF/UHF spots from
3298 11.58. forward/latlong <node_call> (8)
3300 forward/latlong <node_call> Send latitude and longitude information to
3303 This command sends all the latitude and longitude information that
3304 yourcluster is holding against callsigns. One advantage of recieving
3305 thisinformation is that more locator information is held by you.
3306 Thismeans that more locators are given on the DX line assuming you
3307 haveSET/DXGRID enabled. This could be a LOT of information though,
3308 soit is not recommended on slow links.
3310 11.59. forward/opernam <call> (1)
3312 forward/opernam <call> Send out information on this <call> to all
3315 This command sends out any information held in the user file which can
3316 be broadcast in PC41 protocol packets. This information is Name, QTH,
3317 Locationand Homenode. PC41s are only sent for the information that is
3322 help The HELP Command
3324 HELP is available for a number of commands. The syntax is:-
3331 Where <cmd> is the name of the command you want help on.All commands
3332 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3333 can be shortened to AN and so on.Look at the APROPOS <string> command
3334 which will search the help databasefor the <string> you specify and
3335 give you a list of likely commandsto look at with HELP.
3337 11.61. init <node> (5)
3339 init <node> Re-initialise a link to an AK1A compatible node
3341 This command attempts to re-initialise a link to a (usually) AK1A
3342 nodethat has got confused, usually by a protocol loop of some kind. It
3343 maywork - but you usually will be better off simply disconnecting it
3344 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3345 <yournode>).Best of luck - you will need it.
3347 11.62. join <group> (0)
3349 join <group> Join a chat or conference group
3351 JOIN allows you to join a network wide conference group. To join
3352 agroup (called FOC in this case) type:-
3359 See also CHAT, LEAVE, SHOW/CHAT
3365 As a sysop you can kill any message on the system.
3367 11.64. kill <from msgno>-<to msgno> (0)
3369 kill <from msgno>-<to msgno> Delete a range of messages
3372 11.65. kill <from>-<to> (5)
3374 kill <from>-<to> Remove a range of messages from the system
3377 11.66. kill <msgno> [<msgno..] (0)
3379 kill <msgno> [<msgno..] Delete a message from the local system
3382 11.67. kill <msgno> [<msgno> ...] (0)
3384 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3386 You can get rid of any message to or originating from your callsign
3387 using this command. You can remove more than one message at a time.
3389 11.68. kill expunge <msgno> [<msgno..] (6)
3391 kill expunge <msgno> [<msgno..] Expunge a message
3393 Deleting a message using the normal KILL commands only marks that
3394 messagefor deletion. The actual deletion only happens later (usually
3395 two days later).The KILL EXPUNGE command causes the message to be
3396 truly deleted more or lessimmediately.It otherwise is used in the same
3397 way as the KILL command.
3399 11.69. kill from <call> (5)
3401 kill from <call> Remove all messages from a callsign
3404 11.70. kill full <msgno> [<msgno..] (5)
3406 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3408 Delete a message from the local system. You will only be able todelete
3409 messages that you have originated or been sent (unless you arethe
3417 Will delete all the messages that you own between msgnos 1234 and
3425 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3432 will delete all messages to g1tlh.
3439 will delete a message (usually a 'bulletin') from the whole cluster
3440 system. This uses the subject field, so any messages that have exactly
3441 thesame subject will be deleted. Beware!
3443 11.71. kill full <msgno> [<msgno] (5)
3445 kill full <msgno> [<msgno] Remove a message from the entire cluster
3447 Remove this message from the entire cluster system as well as your
3450 11.72. kill to <call> (5)
3452 kill to <call> Remove all messages to a callsign
3455 11.73. kill from <regex> (0)
3457 kill from <regex> Delete messages FROM a callsign or pattern
3460 11.74. kill to <regex> (0)
3462 kill to <regex> Delete messages TO a callsign or pattern
3465 11.75. leave <group> (0)
3467 leave <group> Leave a chat or conference group
3469 LEAVE allows you to leave a network wide conference group. To leave
3470 agroup (called FOC in this case) type:-
3477 See also CHAT, JOIN, SHOW/CHAT
3481 links Show which nodes is physically connected
3483 This is a quick listing that shows which links are connected andsome
3484 information about them. See WHO for a list of all connections.
3486 11.77. load/aliases (9)
3488 load/aliases Reload the command alias table
3490 Reload the /spider/cmd/Aliases file after you have editted it. Youwill
3491 need to do this if you change this file whilst the cluster isrunning
3492 in order for the changes to take effect.
3494 11.78. load/badmsg (9)
3496 load/badmsg Reload the bad msg table
3498 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3499 whilstthe cluster is running. This table contains a number of perl
3500 regular expressions which are searched for in the fields targetted of
3501 each message. If any of them match then that message is immediately
3504 11.79. load/badwords (9)
3506 load/badwords Reload the bad words table
3508 Reload the /spider/data/badwords file if you have changed it manually
3509 whilstthe cluster is running. This file contains a list of words
3510 which, if foundon certain text portions of PC protocol, will cause
3511 those protocol framesto be rejected. It will all put out a message if
3512 any of these words areused on the announce, dx and talk commands. The
3513 words can be one or more on a line, lines starting with '#' are
3516 11.80. load/bands (9)
3518 load/bands Reload the band limits table
3520 Reload the /spider/data/bands.pl file if you have changed it manually
3521 whilstthe cluster is running.
3523 11.81. load/cmd_cache (9)
3525 load/cmd_cache Reload the automatic command cache
3527 Normally, if you change a command file in the cmd or local_cmd tree
3528 itwill automatially be picked up by the cluster program. Sometimes
3529 itcan get confused if you are doing a lot of moving commands about
3530 ordelete a command in the local_cmd tree and want to use the normal
3531 oneagain. Execute this command to reset everything back to the state
3532 itwas just after a cluster restart.
3534 11.82. load/forward (9)
3536 load/forward Reload the msg forwarding routing table
3538 Reload the /spider/msg/forward.pl file if you have changed itmanually
3539 whilst the cluster is running.
3541 11.83. load/keps (5)
3543 load/keps Load new keps data
3547 11.84. load/keps [nn] (5)
3549 load/keps [nn] Load new keps data from message
3551 If there is no message number then reload the current Keps data
3552 fromthe Keps.pm data file. You create this file by running
3555 /spider/perl/convkeps.pl <filename>
3559 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3560 there is a message number, then it will take the message, runcon-
3561 vkeps.pl on it and then load the data, all in one step.These messages
3562 are sent to ALL by GB7DJK (and others) from time to time.
3564 11.85. load/messages (9)
3566 load/messages Reload the system messages file
3568 If you change the /spider/perl/Messages file (usually
3569 whilstfiddling/writing new commands) you can have them take effect
3570 during acluster session by executing this command. You need to do this
3571 if getsomething like :-unknown message 'xxxx' in lang 'en'
3573 11.86. load/prefixes (9)
3575 load/prefixes Reload the prefix table
3577 Reload the /spider/data/prefix_data.pl file if you have changed
3578 itmanually whilst the cluster is running.
3580 11.87. merge <node> [<no spots>/<no wwv>] (5)
3582 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3584 MERGE allows you to bring your spot and wwv database up to date. By
3585 defaultit will request the last 10 spots and 5 WWVs from the node you
3586 select. The node must be connected locally.You can request any number
3587 of spots or wwv and although they will be appendedto your databases
3588 they will not duplicate any that have recently been added (the last 2
3589 days for spots and last month for WWV data).
3591 11.88. msg <cmd> <msgno> [data ... ] (9)
3593 msg <cmd> <msgno> [data ... ] Alter various message parameters
3595 Alter message parameters like To, From, Subject, whether private or
3596 bulletinor return receipt (RR) is required or whether to keep this
3597 message from timingout.
3600 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
3604 You can look at the status of a message by using:-
3611 This will display more information on the message than DIR does.
3613 11.89. pc <call> <text> (8)
3615 pc <call> <text> Send arbitrary text to a connected callsign
3617 Send some arbitrary text to a locally connected callsign. Noprocessing
3618 is done on the text. This command allows you to send PCProtocol to
3619 unstick things if problems arise (messages get stucketc). eg:-
3622 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3629 pc G1TLH Try doing that properly!!!
3633 Send any text you like to the callsign requested. This is used mainly
3634 to sendPC protocol to connected nodes either for testing or to unstick
3635 things. You can also use in the same way as a talk command to a con-
3636 nected user butwithout any processing, added of "from <blah> to <blah"
3639 11.90. ping <node call> (1)
3641 ping <node call> Check the link quality between nodes
3643 This command allows you to send a frame to another cluster node onthe
3644 network and get a return frame. The time it takes to do thisis a good
3645 indication of the quality of the link. The actual timeit takes is
3646 output to the console in seconds.Any visible cluster node can be
3649 11.91. rcmd <node call> <cmd> (1)
3651 rcmd <node call> <cmd> Send a command to another DX Cluster
3653 This command allows you to send nearly any command to another DX
3654 Clusternode that is connected to the system. Whether you get any
3655 output is dependant on a) whether the other system knowsthat the node
3656 callsign of this cluster is in fact a node b) whether theother system
3657 is allowing RCMDs from this node and c) whether you havepermission to
3658 send this command at all.
3662 read Read the next unread personal message addressed to you
3665 11.93. read <msgno> (0)
3667 read <msgno> Read the specified message
3669 You can read any messages that are sent as 'non-personal' and also
3670 anymessage either sent by or sent to your callsign.
3676 As a sysop you may read any message on the system
3681 reject Set a filter to reject something
3683 Create a filter to reject somethingThere are 2 types of filter, accept
3684 and reject. See HELP FILTERING for moreinfo.
3686 11.96. reject/announce <call> [input] [0-9] <pattern> (8)
3688 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3691 This version allows a sysop to set a filter for a callsign as well as
3692 thedefault for nodes and users eg:-
3695 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3699 11.97. reject/announce [0-9] <pattern> (0)
3701 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3704 Create an 'reject this announce' line for a filter. A reject filter
3705 line means that if the announce matches this filter it ispassed onto
3706 the user. See HELP FILTERING for more info. Please read thisto
3707 understand how filters work - it will save a lot of grief later on.You
3708 can use any of the following things in this line:-
3711 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)
3718 rej/ann by_zone 14,15,16 and not by G,M,2
3722 You can use the tag 'all' to reject everything eg:
3729 but this probably for advanced users...
3731 11.98. reject/route <call> [0-9] <pattern> (8)
3733 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3736 Create an 'reject this routing PC Protocol' line for a filter. An
3737 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3738 filter it is NOT passed thru that interface. See HELP FILTERING for
3739 more info. Please read this to understand how filters work - it will
3740 save a lot of grief later on.You can use any of the following things
3744 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
3751 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3755 You can use the tag 'all' to reject everything eg:
3758 rej/route all (equiv to [very] restricted mode)
3762 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3764 11.99. reject/spots <call> [input] [0-9] <pattern> (8)
3766 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3768 This version allows a sysop to set a filter for a callsign as well as
3769 thedefault for nodes and users eg:-
3772 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3776 reject/spot user_default by G,M,2
3780 11.100. reject/spots [0-9] <pattern> (0)
3782 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3784 Create a 'reject this spot' line for a filter. A reject filter line
3785 means that if the spot matches this filter it isdumped (not passed
3786 on). See HELP FILTERING for more info. Please read thisto understand
3787 how filters work - it will save a lot of grief later on.You can use
3788 any of the following things in this line:-
3791 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>
3795 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3799 You can use the tag 'all' to reject everything eg:
3805 but this probably for advanced users...
3807 11.101. reject/wcy <call> [input] [0-9] <pattern> (8)
3809 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3811 This version allows a sysop to set a filter for a callsign as well as
3812 thedefault for nodes and users eg:-
3815 reject/wcy gb7djk all
3819 11.102. reject/wcy [0-9] <pattern> (0)
3821 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3823 It is unlikely that you will want to do this, but if you do then you
3824 canfilter on the following fields:-
3827 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>
3831 There are no examples because WCY Broadcasts only come from one place
3832 andyou either want them or not (see UNSET/WCY if you don't want
3833 them).This command is really provided for future use.See HELP FILTER
3836 11.103. reject/wwv <call> [input] [0-9] <pattern> (8)
3838 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3840 This version allows a sysop to set a filter for a callsign as well as
3841 thedefault for nodes and users eg:-
3844 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3848 reject/wwv user_default by W
3852 11.104. reject/wwv [0-9] <pattern> (0)
3854 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3856 It is unlikely that you will want to do this, but if you do then you
3857 canfilter on the following fields:-
3860 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>
3867 reject/wwv by_zone 14,15,16
3871 is probably the only useful thing to do (which will only show WWV
3872 broadcastsby stations in the US).See HELP FILTER for information.
3876 reply Reply (privately) to the last message that you have read
3879 11.106. reply <msgno> (0)
3881 reply <msgno> Reply (privately) to the specified message
3884 11.107. reply b <msgno> (0)
3886 reply b <msgno> Reply as a Bulletin to the specified message
3889 11.108. reply noprivate <msgno> (0)
3891 reply noprivate <msgno> Reply as a Bulletin to the specified message
3894 11.109. reply rr <msgno> (0)
3896 reply rr <msgno> Reply to the specified message with read receipt
3898 You can reply to a message and the subject will automatically
3899 have"Re:" inserted in front of it, if it isn't already present.You can
3900 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3901 that you can use with the SEND command (see SENDfor further details)
3903 11.110. save [-d -t -a] <filename> "<cmd>" [...] (9)
3905 save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
3907 This sysop only cammand allows you to save the output of one or
3908 morecommands to a file. For example:-
3911 save /spider/packclus/dxstats show/dxstat
3915 will save the output of the normal command "show/dxstat" to the
3916 file"dxstats" in the files area.You can have some extra flags to the
3917 save which will either date stamp or time stamp or both the filename
3921 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
3925 The -a flag means append to the file instead of overwriting it.You can
3926 have more than one command on the line, to do this you MUSTenclose
3927 each command in double quotes (") eg:-
3930 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
3936 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
3940 You can only write into places that the cluster has permission for
3941 (whichis that of the "sysop" user [which had BETTER NOT BE "root"]),
3942 you will need to create any directories you want to put stuff in
3943 beforehand as well.It is likely that you will want to run these com-
3944 mands in a crontab type situation. You would do that something like:-
3947 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
3951 Note that you still enclose each command with (") characters but you
3952 mustenclose the entire save command in (') characters. Now in fact,
3953 this can be varied if you know what you are doing. See theadmin manual
3956 11.111. send <call> [<call> ...] (0)
3958 send <call> [<call> ...] Send a message to one or more callsigns
3961 11.112. send copy <msgno> <call> (0)
3963 send copy <msgno> <call> Send a copy of a message to someone
3966 11.113. send noprivate <call> (0)
3968 send noprivate <call> Send a message to all stations
3970 All the SEND commands will create a message which will be sent either
3971 toan individual callsign or to one of the 'bulletin' addresses. SEND
3972 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3973 will mark the message as personal and send it to the cluster node
3974 thatthat callsign is connected to. If the <call> you have specified is
3975 in facta known bulletin category on your node (eg: ALL) then the
3976 message shouldautomatically become a bulletin.You can have more than
3977 one callsign in all of the SEND commands.You can have multiple
3978 qualifiers so that you can have for example:-
3981 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3985 which should send a copy of message 123 to G1TLH and G0RDI and you
3986 willreceive a read receipt when they have read the message.SB is an
3987 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3988 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3989 tionally this should be no longer than 29 characters for compatibil-
3990 ity. Most modern clustersoftware should accept more.You will now be
3991 prompted to start entering your text. You finish the message by enter-
3992 ing '/EX' on a new line. For instance:
3995 ... bye then Jim 73 Dirk /ex
3999 If you have started a message and you don't want to keep it then you-
4000 can abandon the message with '/ABORT' on a new line, like:-
4003 line 1 line 2 oh I just can't be bothered with this /abort
4007 If you abort the message it will NOT be sent.When you are entering the
4008 text of your message, most normal output (suchas DX announcements and
4009 so on are suppressed and stored for latter display(upto 20 such lines
4010 are stored, as new ones come along, so the oldestlines are
4011 dropped).Also, you can enter normal commands commands (and get the
4012 output immediately) whilst in the middle of a message. You do this by
4013 typingthe command preceeded by a '/' character on a new line, so:-
4016 /dx g1tlh 144010 strong signal
4020 Will issue a dx annoucement to the rest of the cluster. Also, you can
4021 add the output of a command to your message by preceeding the command
4029 This will show YOU the output from SH/VHFTABLE and also store it in
4030 themessage. You can carry on with the message until you are ready to
4033 11.114. send private <call> (0)
4035 send private <call> Send a personal message
4038 11.115. send rr <call> (0)
4040 send rr <call> Send a message and ask for a read receipt
4043 11.116. set/address <your address> (0)
4045 set/address <your address> Record your postal address
4048 11.117. set/announce (0)
4050 set/announce Allow announce messages to come out on your terminal
4053 11.118. set/anntalk (0)
4055 set/anntalk Allow talk like announce messages on your terminal
4058 11.119. set/arcluster <call> [<call>..] (5)
4060 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
4064 11.120. set/baddx <call>.. (8)
4066 set/baddx <call>.. Stop callsigns in a dx spot being propagated
4069 11.121. set/badnode <call>.. (8)
4071 set/badnode <call>.. Stop spots from this node being propagated
4074 11.122. set/badspotter <call>.. (8)
4076 set/badspotter <call>.. Stop spots from this callsign being propagated
4079 11.123. set/badword <word>.. (8)
4081 set/badword <word>.. Stop things with this word being propagated
4084 11.124. set/bbs <call> [<call>..] (5)
4086 set/bbs <call> [<call>..] Make the callsign a BBS
4089 11.125. set/beep (0)
4091 set/beep Add a beep to DX and other messages on your terminal
4094 11.126. set/clx <call> [<call>..] (5)
4096 set/clx <call> [<call>..] Make the callsign an CLX node
4099 11.127. set/debug <name> (9)
4101 set/debug <name> Add a debug level to the debug set
4106 set/dx Allow DX messages to come out on your terminal
4109 11.129. set/dxcq (0)
4111 set/dxcq Show CQ Zones on the end of DX announcements
4114 11.130. set/dxgrid (0)
4116 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
4119 11.131. set/dxitu (0)
4121 set/dxitu Show ITU Zones on the end of DX announcements
4124 11.132. set/dxnet <call> [<call>..] (5)
4126 set/dxnet <call> [<call>..] Make the callsign an DXNet node
4130 11.133. set/echo (0)
4132 set/echo Make the cluster echo your input
4135 11.134. set/email <email> ... (0)
4137 set/email <email> ... Set email address(es) and forward your personals
4140 11.135. set/here (0)
4142 set/here Tell the system you are present at your terminal
4145 11.136. set/homenode <node> (0)
4147 set/homenode <node> Set your normal cluster callsign
4149 Tell the cluster system where you normally connect to. Any Messages
4150 sentto you will normally find their way there should you not be
4158 11.137. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
4160 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
4163 11.138. set/isolate (9)
4165 set/isolate Isolate a node from the rest of the network
4167 Connect a node to your system in such a way that you are a full
4168 protocolmember of its network and can see all spots on it, but nothing
4169 either leaksout from it nor goes back into from the rest of the nodes
4170 connected to you.You can potentially connect several nodes in this
4173 11.139. set/language <lang> (0)
4175 set/language <lang> Set the language you want to use
4177 You can select the language that you want the cluster to use.
4178 Currentlythe languages available are en (English), de (German), es
4179 (Spanish) and nl (Dutch).
4181 11.140. set/location <lat & long> (0)
4183 set/location <lat & long> Set your latitude and longitude
4186 11.141. set/lockout <call> (9)
4188 set/lockout <call> Stop a callsign connecting to the cluster
4191 11.142. set/logininfo (0)
4193 set/logininfo Inform when a station logs in locally
4195 11.143. set/name <your name> (0)
4197 set/name <your name> Set your name
4199 Tell the system what your name is eg:-
4206 11.144. set/node <call> [<call>..] (5)
4208 set/node <call> [<call>..] Make the callsign an AK1A cluster
4210 Tell the system that the call(s) are to be treated as AK1A cluster
4211 andfed PC Protocol rather normal user commands.
4213 11.145. set/obscount <count> <call> (8)
4215 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
4217 From 1.35 onwards neighbouring nodes are pinged at regular intervals
4218 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
4219 'pump-up'counter which is decremented on every outgoing ping and then
4220 reset tothe 'obscount' value on every incoming ping. The default value
4221 of thisparameter is 2. What this means is that a neighbouring node
4222 will be pinged twice at (default) 300 second intervals and if no reply
4223 has been heard just beforewhat would be the third attempt, that node
4224 is disconnected.If a ping is heard then the obscount is reset to the
4225 full value. Usingdefault values, if a node has not responded to a ping
4226 within 15 minutes,it is disconnected.You can set this parameter
4227 between 1 and 9.It is STRONGLY recommended that you don't change the
4230 11.146. set/page <lines per page> (0)
4232 set/page <lines per page> Set the lines per page
4234 Tell the system how many lines you wish on a page when the number of
4235 lineof output from a command is more than this. The default is 20.
4236 Setting itexplicitly to 0 will disable paging.
4239 SET/PAGE 30 SET/PAGE 0
4243 The setting is stored in your user profile.
4245 11.147. set/password (0)
4247 set/password Set your own password
4249 This command only works for a 'telnet' user (currently). It willonly
4250 work if you have a password already set. This initial passwordcan only
4251 be set by the sysop.When you execute this command it will ask you for
4252 your old password,then ask you to type in your new password twice (to
4253 make sure youget it right). You may or may not see the data echoed on
4254 the screenas you type, depending on the type of telnet client you
4259 11.148. set/password <callsign> <string> (9)
4261 set/password <callsign> <string> Set a users password
4263 The password for a user can only be set by a full sysop. The stringcan
4264 contain any characters. The way this field is used depends on context.
4265 If it is being used inthe SYSOP command context then you are offered 5
4266 random numbers and youhave to supply the corresponding letters. This
4267 is now mainly for ax25connections.If it is being used on incoming
4268 telnet connections then, if a passwordis set or the:
4271 set/var $main::passwdreq = 1
4275 command is executed in the startup script, then a password prompt
4276 isgiven after the normal 'login: ' prompt.
4278 11.149. set/pinginterval <time> <nodecall> (9)
4280 set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes
4282 As from release 1.35 all neighbouring nodes are pinged at regular
4283 intervalsin order to determine the rolling quality of the link and, in
4284 future, toaffect routing decisions. The default interval is 300 secs
4285 or 5 minutes.You can use this command to set a different interval.
4286 Please don't. But if you do the value you enter is treated as minutes
4287 up 30 and secondsfor numbers greater than that.This is used also to
4288 help determine when a link is down at the far end(as certain cluster
4289 software doesn't always notice), see SET/OBSCOUNTfor more
4290 information.If you must change it (and it may be useful for internet
4291 connected nodeson dynamic IP addresses that go away after a set time
4292 of usage) the timecan be specified as:-
4295 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
4299 Please be aware that this causes traffic to occur on the link, setting
4300 this value too low may annoy your neighbours beyond the point of
4301 endurance!You can switch this off by setting it to 0.
4303 11.150. set/privilege <n> <call> [<call..] (9)
4305 set/privilege <n> <call> [<call..] Set privilege level on a call
4307 Set the privilege level on a callsign. The privilege levels that
4308 pertainto commands are as default:-
4311 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.
4315 If you are a sysop and you come in as a normal user on a remote con-
4316 nectionyour privilege will automatically be set to 0.
4318 11.151. set/prompt <string> (0)
4320 set/prompt <string> Set your prompt to <string>
4324 11.152. set/qra <locator> (0)
4326 set/qra <locator> Set your QRA Grid locator
4328 Tell the system what your QRA (or Maidenhead) locator is. If you have
4329 notdone a SET/LOCATION then your latitude and longitude will be set
4330 roughlycorrectly (assuming your locator is correct ;-). For example:-
4337 11.153. set/qth <your qth> (0)
4339 set/qth <your qth> Set your QTH
4341 Tell the system where you are. For example:-
4344 SET/QTH East Dereham, Norfolk
4348 11.154. set/register <call> ... (9)
4350 set/register <call> ... Mark a user as registered
4353 11.155. set/spider <call> [<call>..] (5)
4355 set/spider <call> [<call>..] Make the callsign an DXSpider node
4357 Tell the system that the call(s) are to be treated as DXSpider node
4358 andfed new style DX Protocol rather normal user commands.
4360 11.156. set/sys_location <lat & long> (9)
4362 set/sys_location <lat & long> Set your cluster latitude and longitude
4364 In order to get accurate headings and such like you must tell the
4365 systemwhat your latitude and longitude is. If you have not yet done a
4366 SET/QRAthen this command will set your QRA locator for you. For
4370 SET/LOCATION 52 22 N 0 57 E
4374 11.157. set/sys_qra <locator> (9)
4376 set/sys_qra <locator> Set your cluster QRA Grid locator
4379 11.158. set/talk (0)
4381 set/talk Allow TALK messages to come out on your terminal
4385 11.159. set/usdb <call> <state> <city> (9)
4387 set/usdb <call> <state> <city> add/update a US DB callsign
4389 This command allows you to add or alter a callsign in the US
4390 statedatabase. Use with extreme caution. Anything you do here will
4391 beoverwritten by any weekly updates that affect this callsign
4394 set/usdb g1tlh nh downtown rindge
4398 see also DELETE/USDB
4400 11.160. set/usstate (0)
4402 set/usstate Allow US State info on the end of DX announcements
4407 set/wcy Allow WCY messages to come out on your terminal
4412 set/wwv Allow WWV messages to come out on your terminal
4417 set/wx Allow WX messages to come out on your terminal
4420 11.164. show/baddx (1)
4422 show/baddx Show all the bad dx calls in the system
4424 Display all the bad dx callsigns in the system, see SET/BADDXfor more
4427 11.165. show/badnode (1)
4429 show/badnode Show all the bad nodes in the system
4431 Display all the bad node callsigns in the system, see SET/BADNODEfor
4434 11.166. show/badspotter (1)
4436 show/badspotter Show all the bad spotters in the system
4438 Display all the bad spotter's callsigns in the system, see
4439 SET/BADSPOTTERfor more information.
4441 11.167. show/badword (1)
4443 show/badword Show all the bad words in the system
4445 Display all the bad words in the system, see SET/BADWORDfor more
4450 11.168. show/chat [<group>] [<lines>] (0)
4452 show/chat [<group>] [<lines>] Show any chat or conferencing
4454 This command allows you to see any chat or conferencing that has
4455 occurred whilst you were away. SHOW/CHAT on its own will show data
4456 forall groups. If you use a group name then it will show only chat
4459 11.169. show/configuration [<node>] (0)
4461 show/configuration [<node>] Show all the nodes and users visible
4463 This command allows you to see all the users that can be seenand the
4464 nodes to which they are connected.This command is normally abbreviated
4465 to: sh/cNormally, the list returned will be just for the nodes from
4466 your country (because the list otherwise will be very long).
4473 will produce a complete list of all nodes. BE WARNED: the list that is
4474 returned can be VERY longIt is possible to supply a node or part of a
4475 prefix and you will get a list of the users for that node or list of
4476 nodes starting withthat prefix.
4487 11.170. show/configuration/node (0)
4489 show/configuration/node Show all the nodes connected locally
4491 Show all the nodes connected to this node.
4493 11.171. show/connect (1)
4495 show/connect Show all the active connections
4497 This command shows information on all the active connections known
4498 tothe node. This command gives slightly more information than WHO.
4500 11.172. show/contest <year and month> (0)
4502 show/contest <year and month> Show all the contests for a month
4504 Show all known contests which are maintained at
4505 http://www.sk3bg.se/contest/for a particular month or year. The format
4506 is reasonably flexible.For example:-
4509 SH/CONTEST sep2003 SH/CONTEST 03 march
4513 11.173. show/date [<prefix>|<callsign>] (0)
4515 show/date [<prefix>|<callsign>] Show the local time
4517 This is very nearly the same as SHOW/TIME, the only difference the
4518 formatof the date string if no arguments are given.If no prefixes or
4519 callsigns are given then this command returns the localtime and UTC as
4520 the computer has it right now. If you give some prefixesthen it will
4521 show UTC and UTC + the local offset (not including DST) atthe prefixes
4522 or callsigns that you specify.
4524 11.174. show/db0sdx <callsign> (0)
4526 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
4528 This command queries the DB0SDX QSL server on the internetand returns
4529 any information available for that callsign. This serviceis provided
4530 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
4533 11.175. show/debug (9)
4535 show/debug Show what levels of debug information you are logging
4540 show/dx Interrogate the spot database
4542 If you just type SHOW/DX you will get the last so many spots(sysop
4543 configurable, but usually 10).In addition you can add any number of
4544 these commands in very nearlyany order to the basic SHOW/DX command,
4548 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>
4552 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
4556 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
4560 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
4564 info <text> - any spots containing <text> in the info or remarks
4568 by <call> - any spots spotted by <call> (spotter <call> is the same).
4572 qsl - this automatically looks for any qsl info on the call held in the spot database.
4576 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.
4580 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
4584 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
4588 You can also use this with the 'by' keyword so eg by W dxcc
4596 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
4600 11.177. show/dxcc <prefix> (0)
4602 show/dxcc <prefix> Interrogate the spot database by country
4604 This command takes the <prefix> (which can be a full or partial
4605 callsign if desired), looks up which internal country number it isand
4606 then displays all the spots as per SH/DX for that country.This is now
4607 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
4611 SH/DXCC G SH/DXCC W on 20m iota
4615 This can be done with the SHOW/DX command like this:-
4619 SH/DX dxcc g SH/DX dxcc w on 20m iota
4623 11.178. show/dxqsl <callsign> (0)
4625 show/dxqsl <callsign> Show any QSL info gathered from spots
4627 The node collects information from the comment fields in spots
4628 (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a
4629 database.This command allows you to interrogate that database and if
4630 the callsignis found will display the manager(s) that people have
4631 spotted. This information is NOT reliable, but it is normally
4632 reasonably accurate ifit is spotted enough times.For example:-
4639 You can check the raw input spots yourself with:-
4646 This gives you more background information.
4648 11.179. show/dxstats [days] [date] (0)
4650 show/dxstats [days] [date] Show the DX Statistics
4652 Show the total DX spots for the last <days> no of days (default is
4653 31), starting from a <date> (default: today).
4655 11.180. show/files [<filearea> [<string>]] (0)
4657 show/files [<filearea> [<string>]] List the contents of a filearea
4659 SHOW/FILES on its own will show you a list of the various
4660 fileareasavailable on the system. To see the contents of a particular
4668 where <filearea> is the name of the filearea you want to see the con-
4669 tents of.You can also use shell globbing characters like '*' and '?'
4670 in astring to see a selection of files in a filearea eg:-
4673 SH/FILES bulletins arld*
4677 See also TYPE - to see the contents of a file.
4679 11.181. show/filter (0)
4681 show/filter Show the contents of all the filters you have set
4684 Show the contents of all the filters that are set. This command
4685 displaysall the filters set - for all the various categories.
4687 11.182. show/hfstats [days] [date] (0)
4689 show/hfstats [days] [date] Show the HF DX Statistics
4691 Show the HF DX spots breakdown by band for the last <days> no of days
4692 (default is 31), starting from a <date> (default: today).
4694 11.183. show/hftable [days] [date] [prefix ...] (0)
4696 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4698 Show the HF DX Spotter table for the list of prefixes for the last
4699 <days> no of days (default is 31), starting from a <date> (default:
4700 today).If there are no prefixes then it will show the table for your
4701 country.Remember that some countries have more than one "DXCC country"
4702 in them(eg G :-), to show them (assuming you are not in G already
4703 which isspecially treated in the code) you must list all the relevant
4707 sh/hftable g gm gd gi gj gw gu
4711 Note that the prefixes are converted into country codes so you don't
4712 haveto list all possible prefixes for each country.If you want more or
4713 less days than the default simply include thenumber you require:-
4720 If you want to start at a different day, simply add the date in some
4724 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4728 This will show the stats for your DXCC for that CQWW contest weekend.
4729 You can specify either prefixes or full callsigns (so you can see how
4730 youdid against all your mates). You can also say 'all' which will then
4731 printthe worldwide statistics.
4738 11.184. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4740 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4743 This command shows the hop counts set up for a node. You can
4744 specifywhich category you want to see. If you leave the category out
4745 then all the categories will be listed.
4749 11.185. show/isolate (1)
4751 show/isolate Show list of ISOLATED nodes
4754 11.186. show/lockout <prefix>|all (9)
4756 show/lockout <prefix>|all Show the list of locked out or excluded
4760 11.187. show/log [<callsign>] (8)
4762 show/log [<callsign>] Show excerpts from the system log
4764 This command outputs a short section of the system log. On its ownit
4765 will output a general logfile. With the optional callsign it willshow
4766 output from the log associated with that callsign.
4768 11.188. show/moon [ndays] [<prefix>|<callsign>] (0)
4770 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4772 Show the Moon rise and set times for a (list of) prefixes or
4773 callsigns, together with the azimuth and elevation of the sun
4774 currently at thoselocations.If you don't specify any prefixes or
4775 callsigns, it will show the times foryour QTH (assuming you have set
4776 it with either SET/LOCATION or SET/QRA),together with the current
4777 azimuth and elevation.In addition, it will show the illuminated
4778 fraction of the moons disk.If all else fails it will show the Moonrise
4779 and set times for the nodethat you are connected to. For example:-
4782 SH/MOON SH/MOON G1TLH W5UN
4786 You can also use this command to see into the past or the future, soif
4787 you want to see yesterday's times then do:-
4794 or in three days time:-
4801 Upto 366 days can be checked both in the past and in the future.Please
4802 note that the rise and set times are given as the UT times of rise and
4803 set on the requested UT day.
4805 11.189. show/muf <prefix> [<hours>][long] (0)
4807 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4810 This command allow you to estimate the likelihood of you contactinga
4811 station with the prefix you have specified. The output assumes a
4812 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4813 0.15muV/10dB SINAD)The result predicts the most likely operating
4814 frequencies and signallevels for high frequency (shortwave) radio
4815 propagation paths onspecified days of the year and hours of the day.
4816 It is most useful forpaths between 250 km and 6000 km, but can be used
4817 with reduced accuracyfor paths shorter or longer than this.The command
4818 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4819 predict the MUF given the predicted flux, day of the year,hour of the
4820 day and geographic coordinates of the transmitter andreceiver. This
4821 routine is reasonably accurate for the purposes here,with a claimed
4822 RMS error of 3.8 MHz, but much smaller and less complexthan the
4823 programs used by major shortwave broadcasting organizations,such as
4824 the Voice of America.The command will display some header information
4825 detailing itsassumptions, together with the locations, latitude and
4826 longitudes andbearings. It will then show UTC (UT), local time at the
4827 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4828 the path(Zen) and the likely signal strengths. Then for each frequency
4829 for whichthe system thinks there is a likelihood of a circuit it
4830 prints a value.The value is currently a likely S meter reading based
4831 on the conventional6dB / S point scale. If the value has a '+'
4832 appended it means that it is1/2 an S point stronger. If the value is
4833 preceeded by an 'm' it means thatthere is likely to be much fading and
4834 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4835 will show the next two hours worth of data. Youcan specify anything up
4836 to 24 hours worth of data by appending the no ofhours required after
4837 the prefix. For example:-
4847 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
4851 indicating that you will have weak, fading circuits on top band and
4852 80m but usable signals on 40m (about S3).inputing:-
4859 will get you the above display, but with the next 24 hours worth
4863 SH/MUF W L 24 SH/MUF W 24 Long
4867 Gives you an estimate of the long path propagation characterics.
4868 Itshould be noted that the figures will probably not be very useful,
4869 norterrible accurate, but it is included for completeness.
4871 11.190. show/newconfiguration [<node>] (0)
4873 show/newconfiguration [<node>] Show all the nodes and users visible
4875 This command allows you to see all the users that can be seenand the
4876 nodes to which they are connected. This command produces essentially
4877 the same information as SHOW/CONFIGURATION except that it shows all
4878 the duplication ofany routes that might be present It also uses a
4879 different formatwhich may not take up quite as much space if you don't
4880 have anyloops.BE WARNED: the list that is returned can be VERY long
4881 11.191. show/newconfiguration/node (0)
4883 show/newconfiguration/node Show all the nodes connected locally
4885 Show all the nodes connected to this node in the new format.
4887 11.192. show/node [<callsign> ...] (1)
4889 show/node [<callsign> ...] Show the type and version number of nodes
4891 Show the type and version (if connected) of the nodes specified on
4892 thecommand line. If no callsigns are specified then a sorted list of
4893 allthe non-user callsigns known to the system will be displayed.
4895 11.193. show/prefix <callsign> (0)
4897 show/prefix <callsign> Interrogate the prefix database
4899 This command takes the <callsign> (which can be a full or partial
4900 callsign or a prefix), looks up which internal country number it is
4901 and then displays all the relevant prefixes for that countrytogether
4902 with the internal country no, the CQ and ITU regions. See also
4905 11.194. show/program (5)
4907 show/program Show the locations of all the included program modules
4909 Show the name and location where every program module was load from.
4910 Thisis useful for checking where you think you have loaded a .pm file
4913 11.195. show/qra <lat> <long> (0)
4915 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4917 This is a multipurpose command that allows you either to calculate
4918 thedistance and bearing between two locators or (if only one locator
4919 isgiven on the command line) the distance and beraing from your
4920 stationto the locator. For example:-
4923 SH/QRA IO92QL SH/QRA JN06 IN73
4927 The first example will show the distance and bearing to the locator
4928 fromyourself, the second example will calculate the distance and bear-
4929 ing fromthe first locator to the second. You can use 4 or 6 character
4930 locators.It is also possible to convert a latitude and longitude to a
4931 locator by using this command with a latitude and longitude as an
4932 argument, forexample:-
4935 SH/QRA 52 41 N 0 58 E
4939 11.196. show/qra <locator> [<locator>] (0)
4941 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4945 11.197. show/qrz <callsign> (0)
4947 show/qrz <callsign> Show any callbook details on a callsign
4949 This command queries the QRZ callbook server on the internetand
4950 returns any information available for that callsign. This serviceis
4951 provided for users of this software by http://www.qrz.com See also
4952 SHOW/WM7D for an alternative.
4954 11.198. show/registered [<prefix>] (9)
4956 show/registered [<prefix>] Show the registered users
4959 11.199. show/route <callsign> ... (0)
4961 show/route <callsign> ... Show the route to the callsign
4963 This command allows you to see to which node the callsigns specified
4964 areconnected. It is a sort of inverse sh/config.
4971 11.200. show/satellite <name> [<hours> <interval>] (0)
4973 show/satellite <name> [<hours> <interval>] Show tracking data
4975 Show the tracking data from your location to the satellite of your
4976 choicefrom now on for the next few hours.If you use this command
4977 without a satellite name it will display a listof all the satellites
4978 known currently to the system. If you give a name then you can obtain
4979 tracking data of all the passesthat start and finish 5 degrees below
4980 the horizon. As default it willgive information for the next three
4981 hours for every five minute period.You can alter the number of hours
4982 and the step size, within certain limits. Each pass in a period is
4983 separated with a row of '-----' charactersSo for example:-
4986 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4990 11.201. show/station all [<regex>] (6)
4992 show/station all [<regex>] Show list of users in the system
4995 11.202. show/station [<callsign> ..] (0)
4997 show/station [<callsign> ..] Show information about a callsign
4999 Show the information known about a callsign and whether (and
5000 where)that callsign is connected to the cluster.
5007 If no callsign is given then show the information for yourself.
5009 11.203. show/sun [ndays] [<prefix>|<callsign>] (0)
5011 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
5013 Show the sun rise and set times for a (list of) prefixes or callsigns,
5014 together with the azimuth and elevation of the sun currently at
5015 thoselocations.If you don't specify any prefixes or callsigns, it will
5016 show the times foryour QTH (assuming you have set it with either
5017 SET/LOCATION or SET/QRA),together with the current azimuth and
5018 elevation.If all else fails it will show the sunrise and set times for
5019 the nodethat you are connected to. For example:-
5022 SH/SUN SH/SUN G1TLH K9CW ZS
5026 You can also use this command to see into the past or the future, soif
5027 you want to see yesterday's times then do:-
5034 or in three days time:-
5041 Upto 366 days can be checked both in the past and in the future.Please
5042 note that the rise and set times are given as the UT times of rise and
5043 set on the requested UT day.
5045 11.204. show/time [<prefix>|<callsign>] (0)
5047 show/time [<prefix>|<callsign>] Show the local time
5049 If no prefixes or callsigns are given then this command returns the
5050 localtime and UTC as the computer has it right now. If you give some
5051 prefixesthen it will show UTC and UTC + the local offset (not
5052 including DST) atthe prefixes or callsigns that you specify.
5054 11.205. show/usdb [call ..] (0)
5056 show/usdb [call ..] Show information held on the FCC Call database
5058 Show the City and State of a Callsign held on the FCC database ifhis
5059 is being run on this system, eg:-
5066 11.206. show/vhfstats [days] [date] (0)
5068 show/vhfstats [days] [date] Show the VHF DX Statistics
5070 Show the VHF DX spots breakdown by band for the last <days> no of days
5071 (default is 31), starting from a date (default: today).
5074 11.207. show/vhftable [days] [date] [prefix ...] (0)
5076 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
5078 Show the VHF DX Spotter table for the list of prefixes for the last
5079 <days> no of days (default is 31), starting from a date (default:
5080 today).If there are no prefixes then it will show the table for your
5081 country.Remember that some countries have more than one "DXCC country"
5082 in them(eg G :-), to show them (assuming you are not in G already
5083 which isspecially treated in the code) you must list all the relevant
5087 sh/vhftable g gm gd gi gj gw gu
5091 Note that the prefixes are converted into country codes so you don't
5092 haveto list all possible prefixes for each country.If you want more or
5093 less days than the default simply include thenumber you require:-
5100 If you want to start at a different day, simply add the date in some
5104 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
5108 This will show the stats for your DXCC for that CQWW contest weekend.
5109 You can specify either prefixes or full callsigns (so you can see how
5110 youdid against all your mates). You can also say 'all' which will then
5111 printthe worldwide statistics.
5118 11.208. show/wcy (0)
5120 show/wcy Show last 10 WCY broadcasts
5123 11.209. show/wcy <n> (0)
5125 show/wcy <n> Show last <n> WCY broadcasts
5127 Display the most recent WCY information that has been received by the
5130 11.210. show/wm7d <callsign> (0)
5132 show/wm7d <callsign> Show callbook details on a US callsigns
5134 This command queries the WM7D callbook server on the internetand
5135 returns any information available for that US callsign. This serviceis
5136 provided for users of this software by http://www.wm7d.net.See also
5139 11.211. show/wwv (0)
5141 show/wwv Show last 10 WWV broadcasts
5144 11.212. show/wwv <n> (0)
5146 show/wwv <n> Show last <n> WWV broadcasts
5148 Display the most recent WWV information that has been received by the
5151 11.213. shutdown (5)
5153 shutdown Shutdown the cluster
5155 Shutdown the cluster and disconnect all the users
5157 11.214. spoof <call> <command> (9)
5159 spoof <call> <command> Do a command as though you are another user
5161 This command is provided so that sysops can set a user's parameters
5162 withoutme having to write a special 'sysop' version for every user
5163 command. Itallows you to pretend that you are doing the command as the
5164 user you specify.eg:-
5167 SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
5171 11.215. stat/channel [<callsign>] (5)
5173 stat/channel [<callsign>] Show the status of a channel on the cluster
5175 Show the internal status of the channel object either for the channel
5176 that you are on or else for the callsign that you asked for.Only the
5177 fields that are defined (in perl term) will be displayed.
5179 11.216. stat/db <dbname> (5)
5181 stat/db <dbname> Show the status of a database
5183 Show the internal status of a database descriptor.Depending on your
5184 privilege level you will see more or less information. This command is
5185 unlikely to be of much use to anyone other than a sysop.
5187 11.217. stat/msg (1)
5189 stat/msg Show the status of the message system
5192 11.218. stat/msg <msgno> (1)
5194 stat/msg <msgno> Show the status of a message
5196 This command shows the internal status of a message and includes
5197 informationsuch as to whom it has been forwarded, its size, origin etc
5198 etc.If no message number is given then the status of the message
5199 system is displayed.
5203 11.219. stat/route_node <callsign> (5)
5205 stat/route_node <callsign> Show the data in a Route::Node object
5208 11.220. stat/route_node all (5)
5210 stat/route_node all Show list of all Route::Node objects
5213 11.221. stat/route_user <callsign> (5)
5215 stat/route_user <callsign> Show the data in a Route::User object
5218 11.222. stat/route_user all (5)
5220 stat/route_user all Show list of all Route::User objects
5223 11.223. stat/user [<callsign>] (5)
5225 stat/user [<callsign>] Show the full status of a user
5227 Shows the full contents of a user record including all the secret
5228 flagsand stuff.Only the fields that are defined (in perl term) will be
5233 sysop Regain your privileges if you login remotely
5235 The system automatically reduces your privilege level to that of
5236 anormal user if you login in remotely. This command allows you
5237 toregain your normal privilege level. It uses the normal system:
5238 fivenumbers are returned that are indexes into the character array
5239 that isyour assigned password (see SET/PASSWORD). The indexes start
5240 fromzero.You are expected to return a string which contains the
5241 charactersrequired in the correct order. You may intersperse those
5242 characterswith others to obscure your reply for any watchers. For
5243 example (andthese values are for explanation :-):
5246 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
5253 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
5257 They will all match. If there is no password you will still be
5258 offerednumbers but nothing will happen when you input a string. Any
5259 match iscase sensitive.
5261 11.225. talk <call> > <node> [<text>] (0)
5263 talk <call> > <node> [<text>] Send a text message to another station
5266 Send a short message to any other station that is visible on the
5267 clustersystem. You can send it to anyone you can see with a
5268 SHOW/CONFIGURATION command, they don't have to be connected
5269 locally.The second form of TALK is used when other cluster nodes are
5270 connectedwith restricted information. This usually means that they
5271 don't send the user information usually associated with logging on and
5272 off the cluster.If you know that G3JNB is likely to be present on
5273 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
5274 then you would use thesecond form of the talk message.If you want to
5275 have a ragchew with someone you can leave the text messageout and the
5276 system will go into 'Talk' mode. What this means is that ashort
5277 message is sent to the recipient telling them that you are in
5278 a'Talking' frame of mind and then you just type - everything you send
5279 willgo to the station that you asked for. All the usual announcements,
5280 spots and so on will still come out on yourterminal.If you want to do
5281 something (such as send a spot) you preceed the normal command with a
5285 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
5289 To leave talk mode type:
5296 If you are in 'Talk' mode, there is an extention to the '/' command
5297 whichallows you to send the output to all the people you are talking
5298 to. You do with the '//' command. For example:-
5305 will send the hftable as you have it to all the people you are cur-
5308 11.226. talk <call> [<text>] (0)
5310 talk <call> [<text>] Send a text message to another station
5313 11.227. type <filearea>/<name> (0)
5315 type <filearea>/<name> Look at the contents of a file in one of the
5318 Type out the contents of a file in a filearea. So, for example, in
5319 filearea 'bulletins' you want to look at file 'arld051' you would
5323 TYPE bulletins/arld051
5327 See also SHOW/FILES to see what fileareas are available and a list of
5330 11.228. uncatchup <node call> all|[msgno> ...] (5)
5332 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
5335 When you send messages the fact that you have forwarded it to another
5336 node is remembered so that it isn't sent again. When you have a new
5337 partnernode and you add their callsign to your /spider/msg/forward.pl
5338 file, alloutstanding non-private messages will be forwarded to them.
5339 This may wellbe ALL the non-private messages. You can prevent this by
5340 using these commmands:-
5343 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
5347 and to undo what you have just done:-
5350 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
5354 which will arrange for them to be forward candidates again.Order is
5357 11.229. unset/announce (0)
5359 unset/announce Stop announce messages coming out on your terminal
5362 11.230. unset/anntalk (0)
5364 unset/anntalk Stop talk like announce messages on your terminal
5366 The announce system on legacy cluster nodes is used as a talk
5367 substitute because the network is so poorly connected. If you:
5374 you will suppress several of these announces, you may miss the odd
5375 useful one as well, but you would probably miss them anyway in thewel-
5376 ter of useless ones.
5383 allows you to see them again. This is the default.
5385 11.231. unset/baddx <call>.. (8)
5387 unset/baddx <call>.. Propagate a dx spot with this callsign again
5389 Setting a word as 'baddx' will prevent spots with that word in
5390 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
5391 anyfurther. They will not be displayed and they will not be sent
5392 ontoother nodes.The word must be written in full, no wild cards are
5396 set/baddx FORSALE VIDEO FR0G
5400 To allow a word again, use the following command ...
5407 11.232. unset/badnode <call>.. (8)
5409 unset/badnode <call>.. Allow spots from this node again
5411 Setting a callsign as a 'badnode' will prevent spots from that node
5412 going any further. They will not be displayed and they will not be
5413 sent onto other nodes.The call must be a full eg:-
5420 will stop anything from K1TTT. If you want SSIDs as well then you mus-
5421 tenter them specifically.
5428 will allow spots from him again.Use with extreme care. This command
5429 may well be superceeded by FILTERing.
5431 11.233. unset/badspotter <call>.. (8)
5433 unset/badspotter <call>.. Allow spots from this callsign again
5435 Setting a callsign as a 'badspotter' will prevent spots from this
5436 callsign going any further. They will not be displayed and they will
5437 not be sent onto other nodes.The call must be written in full, no wild
5438 cards are allowed eg:-
5441 set/badspotter VE2STN
5445 will stop anything from VE2STN. This command will automaticallystop
5446 spots from this user, regardless of whether or which SSID he uses. DO
5447 NOT USE SSIDs in the callsign, just use the callsignas above or below.
5450 unset/badspotter VE2STN
5454 will allow spots from him again.Use with extreme care. This command
5455 may well be superceded by FILTERing.
5457 11.234. unset/badword <word>.. (8)
5459 unset/badword <word>.. Propagate things with this word again
5461 Setting a word as a 'badword' will prevent things like spots,announces
5462 or talks with this word in the the text part from going anyfurther.
5463 They will not be displayed and they will not be sent ontoother
5464 nodes.The word must be written in full, no wild cards are allowed eg:-
5465 set/badword annihilate annihilated annihilation
5469 will stop anything with these words in the text.
5472 unset/badword annihilated
5476 will allow text with this word again.
5478 11.235. unset/beep (0)
5480 unset/beep Stop beeps for DX and other messages on your terminal
5483 11.236. unset/debug <name> (9)
5485 unset/debug <name> Remove a debug level from the debug set
5487 You can choose to log several different levels. The levels are
5490 chan state msg cron connect
5494 You can show what levels you are logging with SHOW/DEBUG
5496 11.237. unset/dx (0)
5498 unset/dx Stop DX messages coming out on your terminal
5501 11.238. unset/dxcq (0)
5503 unset/dxcq Stop CQ Zones on the end of DX announcements
5505 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
5506 announcement (there is just enough room). Some user programscannot
5507 cope with this. The Spotter's CQ is on the RHS of the time, the
5508 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
5509 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5512 11.239. unset/dxgrid (0)
5514 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
5516 A standard feature which is enabled in version 1.43 and above is that
5517 if the spotter's grid square is known it is output on the endof a DX
5518 announcement (there is just enough room). Some user programscannot
5519 cope with this. You can use this command to reset (or set)this
5520 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
5521 flags you have set if you are confused.
5523 11.240. unset/dxitu (0)
5525 unset/dxitu Stop ITU Zones on the end of DX announcements
5527 Display both the Spotter's and the Spotted's ITU Zone on the endof a
5528 DX announcement (there is just enough room). Some user programscannot
5529 cope with this. The Spotter's ITU is on the RHS of the time, the
5530 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
5531 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5534 11.241. unset/echo (0)
5536 unset/echo Stop the cluster echoing your input
5538 If you are connected via a telnet session, different implimentationsof
5539 telnet handle echo differently depending on whether you are connected
5540 via port 23 or some other port. You can use this commandto change the
5541 setting appropriately. The setting is stored in your user profile.YOU
5542 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
5544 11.242. unset/email (0)
5546 unset/email Stop personal msgs being forwarded by email
5548 If any personal messages come in for your callsign then you can
5549 usethese commands to control whether they are forwarded onto your
5550 emailaddress. To enable the forwarding do something like:-
5553 SET/EMAIL mike.tubby@somewhere.com
5557 You can have more than one email address (each one separated by a
5558 space).Emails are forwarded to all the email addresses you specify.You
5559 can disable forwarding by:-
5566 11.243. unset/here (0)
5568 unset/here Tell the system you are absent from your terminal
5571 11.244. unset/hops <call> ann|spots|route|wwv|wcy (8)
5573 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
5575 Set the hop count for a particular type of broadcast for a node.This
5576 command allows you to set up special hop counts for a node for
5577 currently: announce, spots, wwv and wcy broadcasts.eg:
5580 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
5584 Set SHOW/HOPS for information on what is already set. This commandcre-
5585 ates a filter and works in conjunction with the filter system. You can
5586 unset the hops with command UNSET/HOPS. For example:-
5589 unset/hops gb7djk ann unset/hops gb7mbc spots
5593 11.245. unset/isolate (9)
5595 unset/isolate Stop Isolation of a node from the rest of the network
5597 Remove isolation from a node - SET/ISOLATE
5599 11.246. unset/lockout <call> (9)
5601 unset/lockout <call> Allow a callsign to connect to the cluster
5604 11.247. unset/logininfo (0)
5606 unset/logininfo Inform when a station logs out locally
5609 11.248. unset/password <call> ... (9)
5611 unset/password <call> ... Delete (remove) a user's password
5613 This command allows the sysop to completely delete and remove a
5614 password for a user.
5616 11.249. unset/privilege (0)
5618 unset/privilege Remove any privilege for this session
5620 You can use this command to 'protect' this session from
5621 unauthoriseduse. If you want to get your normal privilege back you
5622 will need toeither logout and login again (if you are on a console) or
5623 use theSYSOP command.
5625 11.250. unset/prompt (0)
5627 unset/prompt Set your prompt back to default
5629 This command will set your user prompt to exactly the string that you
5630 say. The point of this command to enable a user to interface to
5631 programsthat are looking for a specific prompt (or else you just want
5632 a differentfixed prompt).
5639 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
5642 11.251. unset/register <call> ... (9)
5644 unset/register <call> ... Mark a user as not registered
5646 Registration is a concept that you can switch on by executing the
5649 set/var $main::regreq = 1
5653 command (usually in your startup file)If a user is NOT registered
5654 then, firstly, instead of the normalmotd file (/spider/data/motd)
5655 being sent to the user at startup, theuser is sent the motd_nor file
5656 instead. Secondly, the non registereduser only has READ-ONLY access to
5657 the node. The non-registered usercannot use DX, ANN etc. The only
5658 exception to this is that a non-registered user can TALK orSEND
5659 messages to the sysop.
5661 11.252. unset/talk (0)
5663 unset/talk Stop TALK messages coming out on your terminal
5666 11.253. unset/usstate (0)
5668 unset/usstate Stop US State info on the end of DX announcements
5670 If the spotter's or spotted's US State is known it is output on the
5671 end of a DX announcement (there is just enough room). A spotter's
5672 state will appear on the RHS of the time (like SET/DXGRID) and the
5673 spotted's State will appear on the LHS of thetime field. Any
5674 information found will override any locator information from
5675 SET/DXGRID.Some user programs cannot cope with this. You can use this
5676 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
5677 SET/DXITUDo a STAT/USER to see which flags you have set if you are
5680 11.254. unset/wcy (0)
5682 unset/wcy Stop WCY messages coming out on your terminal
5685 11.255. unset/wwv (0)
5687 unset/wwv Stop WWV messages coming out on your terminal
5690 11.256. unset/wx (0)
5692 unset/wx Stop WX messages coming out on your terminal
5697 who Show who is physically connected
5699 This is a quick listing that shows which callsigns are connected
5700 andwhat sort of connection they have
5702 11.258. wx <text> (0)
5704 wx <text> Send a weather message to local users
5707 11.259. wx full <text> (0)
5709 wx full <text> Send a weather message to all cluster users
5712 11.260. wx sysop <text> (5)
5714 wx sysop <text> Send a weather message to other clusters only
5716 Weather messages can sometimes be useful if you are experiencing an
5717 extremethat may indicate enhanced conditions