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 clear/announce <callsign> [input] [0-9|all] (8)
90 11.19 clear/announce [1|all] (0)
91 11.20 clear/route <callsign> [input] [0-9|all] (8)
92 11.21 clear/route [1|all] (0)
93 11.22 clear/spots <callsign> [input] [0-9|all] (8)
94 11.23 clear/spots [0-9|all] (0)
95 11.24 clear/wcy <callsign> [input] [0-9|all] (8)
96 11.25 clear/wcy [1|all] (0)
97 11.26 clear/wwv <callsign> [input] [0-9|all] (8)
98 11.27 clear/wwv [1|all] (0)
99 11.28 connect <callsign> (5)
101 11.30 dbcreate <name> (9)
102 11.31 dbcreate <name> chain <name> [<name>..] (9)
103 11.32 dbcreate <name> cmd <dxspider command> (9)
104 11.33 dbcreate <name> remote <node> (9)
105 11.34 dbimport <dbname> <filename> (9)
106 11.35 dbremove <dbname> (9)
107 11.36 dbshow <dbname> <key> (0)
109 11.38 delete/usdb <callsign> ... (9)
110 11.39 delete/user <callsign> ... (9)
111 11.40 demonstrate <call> <command> (9)
113 11.42 directory <from>-<to> (0)
114 11.43 directory <nn> (0)
115 11.44 directory all (0)
116 11.45 directory from <call> (0)
117 11.46 directory new (0)
118 11.47 directory own (0)
119 11.48 directory subject <string> (0)
120 11.49 directory to <call> (0)
122 11.51 disconnect <call> [<call> ...] (8)
123 11.52 dx [by <call>] <freq> <call> <remarks> (0)
124 11.53 echo <line> (0)
125 11.54 export <msgno> <filename> (9)
126 11.55 export_users [<filename>] (9)
127 11.56 filtering... (0)
128 11.57 forward/latlong <node_call> (8)
129 11.58 forward/opernam <call> (1)
131 11.60 init <node> (5)
133 11.62 kill <from msgno>-<to msgno> (0)
134 11.63 kill <from>-<to> (5)
135 11.64 kill <msgno> [<msgno..] (0)
136 11.65 kill <msgno> [<msgno> ...] (0)
137 11.66 kill expunge <msgno> [<msgno..] (6)
138 11.67 kill from <call> (5)
139 11.68 kill full <msgno> [<msgno..] (5)
140 11.69 kill full <msgno> [<msgno] (5)
141 11.70 kill to <call> (5)
142 11.71 kill from <regex> (0)
143 11.72 kill to <regex> (0)
145 11.74 load/aliases (9)
146 11.75 load/badmsg (9)
147 11.76 load/badwords (9)
149 11.78 load/cmd_cache (9)
150 11.79 load/forward (9)
152 11.81 load/keps [nn] (5)
153 11.82 load/messages (9)
154 11.83 load/prefixes (9)
155 11.84 merge <node> [<no spots>/<no wwv>] (5)
156 11.85 msg <cmd> <msgno> [data ... ] (9)
157 11.86 pc <call> <text> (8)
158 11.87 ping <node call> (1)
159 11.88 rcmd <node call> <cmd> (1)
161 11.90 read <msgno> (0)
164 11.93 reject/announce <call> [input] [0-9] <pattern> (8)
165 11.94 reject/announce [0-9] <pattern> (0)
166 11.95 reject/route <call> [0-9] <pattern> (8)
167 11.96 reject/spots <call> [input] [0-9] <pattern> (8)
168 11.97 reject/spots [0-9] <pattern> (0)
169 11.98 reject/wcy <call> [input] [0-9] <pattern> (8)
170 11.99 reject/wcy [0-9] <pattern> (0)
171 11.100 reject/wwv <call> [input] [0-9] <pattern> (8)
172 11.101 reject/wwv [0-9] <pattern> (0)
174 11.103 reply <msgno> (0)
175 11.104 reply b <msgno> (0)
176 11.105 reply noprivate <msgno> (0)
177 11.106 reply rr <msgno> (0)
178 11.107 save [-d -t -a] <filename> "<cmd>" [...] (9)
179 11.108 send <call> [<call> ...] (0)
180 11.109 send copy <msgno> <call> (0)
181 11.110 send noprivate <call> (0)
182 11.111 send private <call> (0)
183 11.112 send rr <call> (0)
184 11.113 set/address <your address> (0)
185 11.114 set/announce (0)
186 11.115 set/anntalk (0)
187 11.116 set/arcluster <call> [<call>..] (5)
188 11.117 set/baddx <call>.. (8)
189 11.118 set/badnode <call>.. (8)
190 11.119 set/badspotter <call>.. (8)
191 11.120 set/badword <word>.. (8)
192 11.121 set/bbs <call> [<call>..] (5)
194 11.123 set/clx <call> [<call>..] (5)
195 11.124 set/debug <name> (9)
198 11.127 set/dxgrid (0)
200 11.129 set/dxnet <call> [<call>..] (5)
202 11.131 set/email <email> ... (0)
204 11.133 set/homenode <node> (0)
205 11.134 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
206 11.135 set/isolate (9)
207 11.136 set/language <lang> (0)
208 11.137 set/location <lat & long> (0)
209 11.138 set/lockout <call> (9)
210 11.139 set/logininfo (0)
211 11.140 set/name <your name> (0)
212 11.141 set/node <call> [<call>..] (5)
213 11.142 set/obscount <count> <call> (8)
214 11.143 set/page <lines per page> (0)
215 11.144 set/password (0)
216 11.145 set/password <callsign> <string> (9)
217 11.146 set/pinginterval <time> <nodecall> (9)
218 11.147 set/privilege <n> <call> [<call..] (9)
219 11.148 set/prompt <string> (0)
220 11.149 set/qra <locator> (0)
221 11.150 set/qth <your qth> (0)
222 11.151 set/register <call> ... (9)
223 11.152 set/spider <call> [<call>..] (5)
224 11.153 set/sys_location <lat & long> (9)
225 11.154 set/sys_qra <locator> (9)
227 11.156 set/usdb <call> <state> <city> (9)
228 11.157 set/usstate (0)
232 11.161 show/baddx (1)
233 11.162 show/badnode (1)
234 11.163 show/badspotter (1)
235 11.164 show/badword (1)
236 11.165 show/configuration [<node>] (0)
237 11.166 show/configuration/node (0)
238 11.167 show/connect (1)
239 11.168 show/contest <year and month> (0)
240 11.169 show/date [<prefix>|<callsign>] (0)
241 11.170 show/db0sdx <callsign> (0)
242 11.171 show/debug (9)
244 11.173 show/dxcc <prefix> (0)
245 11.174 show/dxqsl <callsign> (0)
246 11.175 show/dxstats [days] [date] (0)
247 11.176 show/files [<filearea> [<string>]] (0)
248 11.177 show/filter (0)
249 11.178 show/hfstats [days] [date] (0)
250 11.179 show/hftable [days] [date] [prefix ...] (0)
251 11.180 show/hops <call> [ann|spots|route|wcy|wwv] (8)
252 11.181 show/isolate (1)
253 11.182 show/lockout <prefix>|all (9)
254 11.183 show/log [<callsign>] (8)
255 11.184 show/moon [ndays] [<prefix>|<callsign>] (0)
256 11.185 show/muf <prefix> [<hours>][long] (0)
257 11.186 show/newconfiguration [<node>] (0)
258 11.187 show/newconfiguration/node (0)
259 11.188 show/node [<callsign> ...] (1)
260 11.189 show/prefix <callsign> (0)
261 11.190 show/program (5)
262 11.191 show/qra <lat> <long> (0)
263 11.192 show/qra <locator> [<locator>] (0)
264 11.193 show/qrz <callsign> (0)
265 11.194 show/registered [<prefix>] (9)
266 11.195 show/route <callsign> ... (0)
267 11.196 show/satellite <name> [<hours> <interval>] (0)
268 11.197 show/station all [<regex>] (6)
269 11.198 show/station [<callsign> ..] (0)
270 11.199 show/sun [ndays] [<prefix>|<callsign>] (0)
271 11.200 show/time [<prefix>|<callsign>] (0)
272 11.201 show/usdb [call ..] (0)
273 11.202 show/vhfstats [days] [date] (0)
274 11.203 show/vhftable [days] [date] [prefix ...] (0)
276 11.205 show/wcy <n> (0)
277 11.206 show/wm7d <callsign> (0)
279 11.208 show/wwv <n> (0)
281 11.210 spoof <call> <command> (9)
282 11.211 stat/channel [<callsign>] (5)
283 11.212 stat/db <dbname> (5)
285 11.214 stat/msg <msgno> (1)
286 11.215 stat/route_node <callsign> (5)
287 11.216 stat/route_node all (5)
288 11.217 stat/route_user <callsign> (5)
289 11.218 stat/route_user all (5)
290 11.219 stat/user [<callsign>] (5)
292 11.221 talk <call> > <node> [<text>] (0)
293 11.222 talk <call> [<text>] (0)
294 11.223 type <filearea>/<name> (0)
295 11.224 uncatchup <node call> all|[msgno> ...] (5)
296 11.225 unset/announce (0)
297 11.226 unset/anntalk (0)
298 11.227 unset/baddx <call>.. (8)
299 11.228 unset/badnode <call>.. (8)
300 11.229 unset/badspotter <call>.. (8)
301 11.230 unset/badword <word>.. (8)
302 11.231 unset/beep (0)
303 11.232 unset/debug <name> (9)
305 11.234 unset/dxcq (0)
306 11.235 unset/dxgrid (0)
307 11.236 unset/dxitu (0)
308 11.237 unset/echo (0)
309 11.238 unset/email (0)
310 11.239 unset/here (0)
311 11.240 unset/hops <call> ann|spots|route|wwv|wcy (8)
312 11.241 unset/isolate (9)
313 11.242 unset/lockout <call> (9)
314 11.243 unset/logininfo (0)
315 11.244 unset/password <call> ... (9)
316 11.245 unset/privilege (0)
317 11.246 unset/prompt (0)
318 11.247 unset/register <call> ... (9)
319 11.248 unset/talk (0)
320 11.249 unset/usstate (0)
326 11.255 wx full <text> (0)
327 11.256 wx sysop <text> (5)
330 ______________________________________________________________________
332 1. Routing and Filtering
336 From DXSpider version 1.48, major changes were introduced to the way
337 node connections are treated. This is part of an ongoing process to
338 remove problems with loops and to enable talk and other functions to
339 propagate across the whole of the worldwide cluster network. In fact,
340 in a Spider network, it would be useful, perhaps even necessary to
341 have loops. This would give real resilience to the network, meaning
342 that if a link dropped, the information flow would simply come in and
343 go out via a different route. Of course, we do not have a complete
344 network of Spider nodes, there are other programs out there. Some of
345 these do not have any protection from loops. Certainly AK1A does not
346 handle loops well at all. It is therefore necessary to have some form
347 of protection for these nodes.
350 In fact DXSpider has had a simple system for some time which is called
351 isolation. This is similar to what in other systems such as clx, is
352 called passive mode. A more detailed explanation of isolation is given
353 further below. This system is still available and, for simple
354 networks, is probably all that you need.
357 The new functionality introduced in version 1.48 allows filtering the
358 node and user protocol frames on a "per interface" basis. We call this
359 route filtering. This is used instead of isolation.
362 What this really means is that you can control more or less completely
363 which user and node management PC protocol frames pass to each of your
364 partner nodes. You can also limit what comes into your node from your
365 partners. It is even possible to control the settings that your
366 partner node has for the routing information that it sends to you
367 (using the rcmd command).
372 Initially when route filters were being tested we generated a
373 "default" filter. Unfortunately it quickly became apparent that this
374 might suit the UK cluster network but didn't really fit anybody else.
375 However using a default filter is an appropriate thing to do. How, is
376 explained further on.
379 The first thing that you must do is determine whether you need to use
380 route filtering at all. If you are a "normal" node with two or three
381 partners and you arranged in an "official" non-looping tree type
382 network, then you do not need to do route filtering and you will feel
383 a lot better for not getting involved. If you are successfully using
384 isolation then you also probably don't need to use route filtering.
387 To put it simply, you should not mix Isolation and Route Filtering.
388 It will work, of sorts, but you will not get the expected results. If
389 you are using Isolation sucessfully at the moment, do not get involved
390 in Route Filtering unless you have a good supply of aspirin! Once you
391 have started down the road of Route Filtering, do not use Isolation
392 either. Use one or the other, not both.
395 You will only require this functionality if you are "well-connected".
396 What that means is that you are connected to several different parts
397 of (say) the EU cluster and, at the same time, also connected to two
398 or three places in the US which, in turn are connected back to the EU.
399 This is called a "loop" and if you are seriously looped then you need
403 I should at this stage give a little bit of background on filters.
404 All the filters in Spider work in basically the same way. You can
405 either accept or reject various options in order to create the filter
406 rules you wish to achieve. Some filters are user settable, others can
407 only be altered by the sysop. Route filtering can only be done by the
409 Anyway, without further discouragement, let me start the process of
413 1.3. The node_default filter
415 All normal systems should have a default routing filter and it should
416 usually be set to send only the normal, unlooped, view of your
417 "national" network. Here in the UK that means nodes from the UK and
418 Eire, in EU it is more complex as the networks there grew up in a more
423 The generic commands are:-
427 reject/route node_default <filter_option>
431 accept/route node_default <filter_option>
435 where filter_option is one of the following ...
444 channel_dxcc <numbers>
445 channel_itu <numbers>
446 channel_zone <numbers>
450 Please be careful if you alter this setting, it will affect ALL your
451 links! Remember, this is a default filter for node connections, not a
455 For the default routing filter then you have two real choices: either
456 a "national" view or the "safe" option of only your own callsign.
457 Examples of each (for my node: GB7DJK) are:-
461 acc/route node_default call_dxcc 61,38
462 acc/route node_default call gb7djk
466 GB7DJK uses the first of these. The DXCC countries can be obtained
467 from the show/prefix command.
470 The example filters shown control output TO all your partner nodes
471 unless they have a specific filter applied to them (see next section).
472 It is also possible to control the incoming routing information that
473 you are prepared to accept FROM your partner nodes. The reason this is
474 necessary is to make sure that stuff like mail, pings and similar
475 commands a) go down the correct links and b) don't loop around
476 excessively. Again using GB7DJK as an example a typical default input
477 filter would be something like:
481 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
485 What this does is accept node and user information for our national
486 network from nodes that are in our national network, but rejects such
487 information from anyone else. Although it doesn't explicitly say so,
488 by implication, any other node information (not from the UK and Eire)
492 As I imagine it will take a little while to get one's head around all
493 of this you can study the effect of any rules that you try by watching
494 the debug output after having done:-
502 After you have got tired of that, to put it back the way it was:-
510 1.4. General route filtering
512 Exactly the same rules apply for general route filtering. You would
513 use either an accept filter or a reject filter like this ...
517 reject/route <node_call> <filter_option>
521 accept/route <node_call> <filter_option>
525 Here are some examples of route filters ...
529 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
530 rej/route all (equiv to [very] restricted mode)
531 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
532 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
536 In practice you will either be opening the default filter out for a
537 partner by defining a specific filter for that callsign:-
542 acc/route gb7baa input all
546 or restricting it quite a lot, in fact making it very nearly like an
547 isolated node, like this:-
551 acc/route pi4ehv-8 call gb7djk
552 rej/route pi4ehv-8 input call_dxcc 61,38
556 This last example takes everything except UK and Eire from PI4EHV-8
557 but only sends him my local configuration (just a PC19 for GB7DJK and
558 PC16s for my local users).
561 It is possible to write much more complex rules, there are up to 10
562 accept/reject pairs per callsign per filter. For more information see
567 1.5. General filter rules
569 Upto v1.44 it was not possible for the user to set their own filters.
570 From v1.45 though that has all changed. It is now possible to set
571 filters for just about anything you wish. If you have just updated
572 from an older version of DXSpider you will need to update your new
573 filters. You do not need to do anything with your old filters, they
574 will be renamed as you update.
577 There are 3 basic commands involved in setting and manipulating
578 filters. These are accept, reject and clear. First we will look
579 generally at filtering. There are a number of things you can filter in
580 the DXSpider system. They all use the same general mechanism.
583 In general terms you can create a "reject" or an "accept" filter which
584 can have up to 10 lines in it. You do this using, for example ...
591 where ..... are the specific commands for that type of filter. There
592 are filters for spots, wwv, announce, wcy and (for sysops) connects.
593 See each different accept or reject command reference for more
596 There is also a command to clear out one or more lines in a filter.
606 There is clear/xxxx command for each type of filter.
609 and you can check that your filters have worked by the command ...
617 For now we are going to use spots for the examples, but you can apply
618 the same principles to all types of filter.
623 There are two main types of filter, accept or reject. You can use
624 either to achieve the result you want dependent on your own preference
625 and which is more simple to do. It is pointless writing 8 lines of
626 reject filters when 1 accept filter would do the same thing! Each
627 filter has 10 lines (of any length) which are tried in order. If a
628 line matches then the action you have specified is taken (ie reject
629 means ignore it and accept means take it)
632 If you specify reject filters, then any lines that arrive that match
633 the filter will be dumped but all else will be accepted. If you use
634 an accept filter, then ONLY the lines in the filter will be accepted
635 and all else will be dumped. For example if you have a single line
640 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
644 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
647 If you set a reject filter like this ...
651 reject/spots on hf/cw
655 Then you will get everything EXCEPT HF CW spots. You could make this
656 single filter even more flexible. For example, if you are interested
657 in IOTA and will work it even on CW even though normally you are not
658 interested in CW, then you could say ...
662 reject/spots on hf/cw and not info iota
666 But in that case you might only be interested in iota and say:-
670 accept/spots not on hf/cw or info iota
674 which achieves exactly the same thing. You should choose one or the
675 other until you are comfortable with the way it works. You can mix
676 them if you wish (actually you can have an accept AND a reject on the
677 same line) but don't attempt this until you are sure you know what you
681 You can arrange your filter lines into logical units, either for your
682 own understanding or simply convenience. Here is an example ...
686 reject/spots 1 on hf/cw
687 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
691 What this does is to ignore all HF CW spots and also rejects any spots
692 on VHF which don't either originate or spot someone in Europe.
695 This is an example where you would use a line number (1 and 2 in this
696 case), if you leave the digit out, the system assumes '1'. Digits
697 '0'-'9' are available. This make it easier to see just what filters
698 you have set. It also makes it more simple to remove individual
699 filters, during a contest for example.
702 You will notice in the above example that the second line has
703 brackets. Look at the line logically. You can see there are 2
704 separate sections to it. We are saying reject spots that are VHF or
705 above APART from those in zones 14, 15 and 16 (either spotted there or
706 originated there). If you did not have the brackets to separate the 2
707 sections, then Spider would read it logically from the front and see a
708 different expression entirely ...
712 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
716 The simple way to remember this is, if you use OR - use brackets.
717 Whilst we are here CASE is not important. 'And BY_Zone' is just the
718 same as 'and by_zone'.
720 As mentioned earlier, setting several filters can be more flexible
721 than simply setting one complex one. Doing it in this way means that
722 if you want to alter your filter you can just redefine or remove one
723 or more lines of it or one line. For example ...
727 reject/spots 1 on hf/ssb
731 would redefine our earlier example, or
739 To remove all the filter lines in the spot filter ...
749 You can filter in several different ways. The options are listed in
750 the various helpfiles for accept, reject and filter.
755 Sometimes all that is needed is a general rule for node connects.
756 This can be done with a node_default filter. This rule will always be
757 followed, even if the link is isolated, unless another filter is set
758 specifically. Default rules can be set for nodes and users. They can
759 be set for spots, announces, WWV and WCY. They can also be used for
760 hops. An example might look like this ...
764 accept/spot node_default by_zone 14,15,16,20,33
765 set/hops node_default spot 50
769 This filter is for spots only, you could set others for announce, WWV
770 and WCY. This filter would work for ALL nodes unless a specific
771 filter is written to override it for a particular node. You can also
772 set a user_default should you require. It is important to note that
773 default filters should be considered to be "connected". By this I
774 mean that should you override the default filter for spots, you need
775 to add a rule for the hops for spots also.
778 1.9. Advanced filtering
780 Once you are happy with the results you get, you may like to
784 The previous example that filters hf/cw spots and accepts vhf/uhf
785 spots from EU can be written with a mixed filter, for example ...
791 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
795 Note that the first filter has not been specified with a number. This
796 will automatically be assumed to be number 1. In this case, we have
797 said reject all HF spots in the CW section of the bands but accept all
798 others at HF. Also accept anything in VHF and above spotted in or by
799 operators in the zones 14, 15 and 16. Each filter slot actually has a
800 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
804 It was mentioned earlier that after a reject test that doesn't match,
805 the default for following tests is 'accept', the reverse is true for
806 'accept'. In the example what happens is that the reject is executed
807 first, any non hf/cw spot is passed to the accept line, which lets
808 through everything else on HF. The next filter line lets through just
809 VHF/UHF spots from EU.
812 1.10. Basic hop control
814 In /spider/data you will find a file called hop_table.pl. This is the
815 file that controls your hop count settings. It has a set of default
816 hops on the various PC frames and also a set for each node you want to
817 alter the hops for. You may be happy with the default settings of
818 course, but this powerful tool can help to protect and improve the
819 network. The file will look something like this ...
824 # hop table construction
829 # default hopcount to use
832 # some variable hop counts based on message type
843 # the per node hop control thingy
875 Each set of hops is contained within a pair of curly braces and
876 contains a series of PC frame types. PC11 for example is a DX spot.
877 The figures here are not exhaustive but should give you a good idea of
881 SHould any of the nodecalls include an ssid, it is important to wrap
882 the whole call in single quotes, like this ...
897 If you do not do this, you will get errors and the file will not work
901 You can alter this file at any time, including whilst the cluster is
902 running. If you alter the file during runtime, the command load/hops
903 will bring your changes into effect.
906 1.11. Hop Control on Specific Nodes
908 You can set a callsign specific hop count for any of the standard
913 set/hops gb7djk spot 4
914 set/hops node_default route 10
915 set/hops gb7baa wcy 5
919 all work on their specific area of the protocol.
922 The set/hops command overrides any hops that you have set otherwise.
925 You can show what hops have been set using the show/hops command.
928 1.12. Isolating networks
930 It is possible to isolate networks from each other on a "gateway" node
931 using the set/isolate <node_call> command.
934 The effect of this is to partition an isolated network completely from
935 another node connected to your node. Your node will appear on and
936 otherwise behave normally on every network to which you are connected,
937 but data from an isolated network will not cross onto any other
938 network or vice versa. However all the spot, announce and WWV traffic
939 and personal messages will still be handled locally (because you are a
940 real node on all connected networks), that is locally connected users
941 will appear on all networks and will be able to access and receive
942 information from all networks transparently. All routed messages will
943 be sent as normal, so if a user on one network knows that you are a
944 gateway for another network, he can still still send a talk/announce
945 etc message via your node and it will be routed across.
948 If you use isolate on a node connection you will continue to receive
949 all information from the isolated partner, however you will not pass
950 any information back to the isolated node. There are times when you
951 would like to forward only spots across a link (maybe during a contest
952 for example). To do this, isolate the node in the normal way and use
953 an acc/spot >call< all filter to override the isolate.
960 In the /spider/msg directory you will find a file called
961 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
962 original looks something like this ....
966 # the list of regexes for messages that we won't store having
967 # received them (bear in mind that we must receive them fully before
971 # The format of each line is as follows
973 # type source pattern
974 # P/B/F T/F/O/S regex
976 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
977 # source: T - to field, F - from field, O - origin, S - subject
978 # pattern: a perl regex on the field requested
980 # Currently only type B and P msgs are affected by this code.
982 # The list is read from the top down, the first pattern that matches
983 # causes the action to be taken.
985 # The pattern can be undef or 0 in which case it will always be selected
986 # for the action specified
997 I think this is fairly self explanatory. It is simply a list of
998 subject headers that we do not want to pass on to either the users of
999 the cluster or the other cluster nodes that we are linked to. This is
1000 usually because of rules and regulations pertaining to items for sale
1001 etc in a particular country.
1005 2.2. Filtering words from text fields in Announce, Talk and DX spots
1007 From version 1.48 onwards the interface to this has changed. You can
1008 now use the commands set/badword to add words that you are not
1009 prepared to see on the cluster, unset/badword to allow that word again
1010 and show/badword to list the words that you have set.
1013 If you have a previous /spider/data/badwords, the first time you start
1014 the node, it will read and convert this file to the new commands. The
1015 old style file will then be removed.
1018 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
1021 There are a number of commands that control whether a spot progresses
1022 any further by regarding it as "bad" in some way.
1025 A DX Spot has a number of fields which can be checked to see whether
1026 they contain "bad" values, they are: the DX callsign itself, the
1027 Spotter and the Originating Node.
1030 There are a set of commands which allow the sysop to control whether a
1041 These work in the same as the set/badword command, you can add any
1042 words or callsigns or whatever to the appropriate database. For
1043 example, to stop a spot from a particular node you do:
1047 set/badnode gb7djk gb7dxc
1055 set/badspotter b0mb p1rat nocall
1063 set/baddx video wsjt
1067 You can remove a word using the appropriate unset command
1068 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1069 of show/baddx, show/badspotter and show/badnode.
1075 DXSpider deals seamlessly with standard AK1A type mail. It supports
1076 both personal and bulletin mail and the sysop has additional commands
1077 to ensure that mail gets to where it is meant. DXSpider will send
1078 mail almost immediately, assuming that the target is on line.
1079 However, only one mail message is dealt with at any one time. If a
1080 mail message is already being sent or recieved, then the new message
1081 will be queued until it has finished.
1083 The cluster mail is automatically deleted after 30 days unless the
1084 sysop sets the "keep" flag using the msg command.
1089 Personal mail is sent using the sp command. This is actually the
1090 default method of sending mail and so a simple s for send will do. A
1091 full list of the send commands and options is in the command set
1092 section, so I will not duplicate them here.
1097 Bulletin mail is sent by using the sb command. This is one of the
1098 most common mistakes users make when sending mail. They send a
1099 bulletin mail with s or sp instead of sb and of course the message
1100 never leaves the cluster. This can be rectified by the sysop by using
1104 Bulletin addresses can be set using the Forward.pl file.
1109 DXSpider receives all and any mail sent to it without any alterations
1110 needed in files. Because personal and bulletin mail are treated
1111 differently, there is no need for a list of accepted bulletin
1112 addresses. It is necessary, however, to tell the program which links
1113 accept which bulletins. For example, it is pointless sending
1114 bulletins addresses to "UK" to any links other than UK ones. The file
1115 that does this is called forward.pl and lives in /spider/msg. At
1116 default, like other spider files it is named forward.pl.issue. Rename
1117 it to forward.pl and edit the file to match your requirements. The
1123 # this is an example message forwarding file for the system
1125 # The format of each line is as follows
1127 # type to/from/at pattern action destinations
1128 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1130 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1131 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1132 # pattern: a perl regex on the field requested
1133 # action: I - ignore, F - forward
1134 # destinations: a reference to an array containing node callsigns
1136 # if it is non-private and isn't in here then it won't get forwarded
1138 # Currently only type B msgs are affected by this code.
1140 # The list is read from the top down, the first pattern that matches
1141 # causes the action to be taken.
1143 # The pattern can be undef or 0 in which case it will always be selected
1144 # for the action specified
1146 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1147 # pattern) then it will always be forwarded to every node that doesn't have
1148 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1149 # you allow a new link with this on EVERY bull will be forwarded immediately
1150 # on first connection)
1160 Simply insert a bulletin address and state in the brackets where you
1161 wish that mail to go. For example, you can see here that mail sent to
1162 "UK" will only be sent to the UK links and not to PA4AB-14.
1165 To force the cluster to reread the file use load/forward
1168 NB: If a user tries to send mail to a bulletin address that does not
1169 exist in this file, they will get an error.
1172 3.4. The msg command
1174 The msg command is a very powerful and flexible tool for the sysop.
1175 It allows the sysop to alter to and from fields and make other changes
1176 to manage the cluster mail.
1178 Here is a full list of the various options ...
1182 MSG TO <msgno> <call> - change TO callsign to <call>
1183 MSG FRom <msgno> <call> - change FROM callsign to <call>
1184 MSG PRrivate <msgno> - set private flag
1185 MSG NOPRrivate <msgno> - unset private flag
1186 MSG RR <msgno> - set RR flag
1187 MSG NORR <msgno> - unset RR flag
1188 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1189 MSG NOKEep <msgno> - unset the keep flag
1190 MSG SUbject <msgno> <new> - change the subject to <new>
1191 MSG WAittime <msgno> - remove any waiting time for this message
1192 MSG NOREad <msgno> - mark message as unread
1193 MSG REad <msgno> - mark message as read
1194 MSG QUeue - queue any outstanding bulletins
1195 MSG QUeue 1 - queue any outstanding private messages
1199 These commands are simply typed from within the cluster as the sysop
1205 You can check on a message from within the cluster by using the
1206 command stat/msg. This will give you additional information on the
1207 message number including which nodes have received it, which node it
1208 was received from and when etc. Here is an example of the output of
1213 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1216 Msg Time: 26-Jan-2001 1302Z
1220 Subject: AMSAT 2line KEPS 01025.AMSAT
1222 Got it Nodes: GB7BAA, GB7ADX
1226 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1232 This is described in the section on Other filters so I will not
1236 3.7. Distribution lists
1238 Distribution lists are simply a list of users to send certain types of
1239 mail to. An example of this is mail you only wish to send to other
1240 sysops. In /spider/msg there is a directory called distro. You put
1241 any distibution lists in here. For example, here is a file called
1242 SYSOP.pl that caters for the UK sysops.
1245 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1246 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1247 GB7DXK GB7DXI GB7DXS)
1251 Any mail sent to "sysop" would only be sent to the callsigns in this
1257 Spider provides a simple BBS interface. No input is required from the
1258 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1259 and pushes any required mail to the cluster. No mail can flow from
1260 Spider to the BBS, the interface is one-way.
1263 Please be careful not to flood the cluster network with unnecessary
1264 mail. Make sure you only send mail to the clusters that want it by
1265 using the Forward.pl file very carefully.
1270 From 1.48 onwards it will become increasingly possible to control
1271 DXSpider's operation with scripts of various kinds.
1274 The directory /spider/scripts is where it all happens and is used for
1275 several things. Firstly it contains a file called startup that can be
1276 used to call in any changes to the cluster from the default settings
1277 on startup. This script is executed immediately after all
1278 initialisation of the node is done but before any connections are
1279 possible. Examples of this include how many spots it is possible to
1280 get with the sh/dx command, whether you want registration/passwords to
1281 be permanently on etc. An example file is shown below and is included
1282 in the distribution as startup.issue.
1287 # startup script example
1289 # set maximum no of spots allowed to 100
1290 # set/var $Spot::maxspots = 100
1292 # Set registration on
1293 # set/var $main::reqreg = 1
1296 # set/var $main::passwdreq = 1
1301 As usual, any text behind a # is treated as a comment and not read.
1302 To use this file, simply rename it from startup.issue to startup. In
1303 our example above there are three options. The first option is the
1304 amount of spots that a user can request with the sh/dx command.
1305 Normally the default is to give 10 spots unless the user specifies
1306 more. Without this line enabled, the maximum a user can request is
1307 100 spots. Depending on your link quality you may wish to enable more
1308 or less by specifying the number.
1311 The other 2 options are dealt with more fully in the security section.
1314 Secondly, it is used to store the login scripts for users and nodes.
1315 Currently this can only be done by the sysop but it is envisaged that
1316 eventually users will be able to set their own. An example is
1317 included in the distibution but here is a further example.
1334 The lines in between commands can simply insert a blank line or a
1335 character such as a + sign to make the output easier to read. Simply
1336 create this script with your favourite editor and save it with the
1337 callsign of the user as the filename. Filenames should always be in
1341 Commands can be inserted in the same way for nodes. A node may wish a
1342 series of commands to be issued on login, such as a merge command for
1346 Thirdly, there are 2 default scripts for users and nodes who do not
1347 have a specifically defined script. These are user_default and
1353 Spider allows the creation of local or remote databases. It supports
1354 chained databases, allowing several different databases to be scanned
1355 with one simple command. Importing of databases is limited at present
1356 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1357 database but will expand with time.
1360 5.1. Creating databases
1362 Creating a database could not be more simple. All the commands are
1363 sent from the cluster prompt as the sysop user.
1365 To create a database you use the command dbcreate. It can be used in
1366 3 different ways like so ..
1373 To simply create a database locally, you just tell the command the
1374 name of the database. This does not create the actual database, it
1375 simply defines it to say that it exists.
1379 dbcreate <name> chain <name> [<name>...]
1383 This creates a chained database entry. The first database will be
1384 scanned, then the second, the third etc...
1388 dbcreate <name> remote <name>
1392 This creates a remote entry. the first name field is the database
1393 name at the remote node, then the remote switch, then the actual
1394 node_call of the remote node, for example...
1398 dbcreate buckmaster remote gb7dxc
1402 Remote databases cannot be chained, however, the last database in a
1403 chain can be a remote database.
1406 5.2. Importing databases
1408 The only databases that Spider can currently import are the standard
1409 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1410 This will be added to with time.
1412 To import such a database, first put the file somewhere useful like
1413 /tmp and then issue the following command ...
1417 dbimport oblast /tmp/OBLAST.FUL
1421 This will update the existing local oblast database or create it if it
1425 5.3. Checking available databases
1427 Once a database is created, you will want to check that it has been
1428 added. To do this use the dbavail command. This will output the
1429 available databases. For example ...
1434 DB Name Location Chain
1438 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1442 5.4. Looking up databases
1444 To look for information in a defined database, simply use the dbshow
1445 command, for example ...
1449 dbshow buckmaster G0YLM
1453 will show the information for the callsign G0YLM from the buckmaster
1454 database if it exists. To make things more standard for the users you
1455 can add an entry in the Aliases file so that it looks like a standard
1456 show command like this ...
1460 Now you can simply use show/buckmaster or an abreviation.
1463 5.5. Removing databases
1465 To delete an existing database you use the dbremove command. For
1474 would remove the oblast database and its associated datafile from the
1475 system. There are no warnings or recovery possible from this command.
1476 If you remove a database it ceases to exist and would have to be
1477 created from scratch if you still required it.
1480 6. Information, files and useful programs
1484 One of the more important things a cluster sysop needs to do is to get
1485 information to his users. The simplest way to do this is to have a
1486 banner that is sent to the user on login. This is know as a "message
1487 of the day" or "motd". To set this up, simply create a file in
1488 /spider/data called motd and edit it to say whatever you want. It is
1489 purely a text file and will be sent automatically to anyone logging in
1493 This message of the day file lives in the same directory as the
1494 standard motd file but is only sent to non-registered users. Once
1495 registered they will receive the same message as any other user.
1498 6.3. Downtime message
1500 If for any reason the cluster is down, maybe for upgrade or
1501 maintenance but the machine is still running, a message can be sent to
1502 the user advising them of the fact. This message lives in the
1503 /spider/data directory and is called "offline". Simply create the
1504 file and edit it to say whatever you wish. This file will be sent to
1505 a user attempting to log into the cluster when DXSpider is not
1509 6.4. Other text messages
1511 You can set other text messages to be read by the user if they input
1512 the file name. This could be for news items or maybe information for
1513 new users. To set this up, make a directory under /spider called
1514 packclus. Under this directory you can create files called news or
1515 newuser for example. In fact you can create files with any names you
1516 like. These can be listed by the user with the command ....
1524 They can be read by the user by typing the command ....
1532 If the file they want to read is called news. You could also set an
1533 alias for this in the Alias file to allow them just to type news
1536 You can also store other information in this directory, either
1537 directly or nested under directories. One use for this would be to
1538 store DX bulletins such as the OPDX bulletins. These can be listed
1539 and read by the user. To keep things tidy, make a directory under
1540 /spider/packclus called bulletin. Now copy any OPDX or similar
1541 bulletins into it. These can be listed by the user in the same way as
1542 above using the show/files command with an extension for the bulletin
1543 directory you have just created, like this ....
1551 An example would look like this ....
1554 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1558 You can see that in the files area (basically the packclus directory)
1559 there is a file called news and a directory called bulletin. You can
1560 also see that dates they were created. In the case of the file news,
1561 you can also see the time it was last modified, a good clue as to
1562 whether the file has been updated since you last read it. To read the
1563 file called news you would simply issue the command ....
1571 To look what is in the bulletin directory you issue the command ....
1576 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1577 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1578 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1579 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1580 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1581 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1582 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1583 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1584 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1585 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1586 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1587 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1588 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1589 Press Enter to continue, A to abort (16 lines) >
1593 You can now read any file in this directory using the type command,
1598 type bulletin/opdx391
1599 Ohio/Penn DX Bulletin No. 391
1600 The Ohio/Penn Dx PacketCluster
1604 Editor Tedd Mirgliotta, KB8NW
1605 Provided by BARF-80 BBS Cleveland, Ohio
1606 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1607 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1608 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1609 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1610 Press Enter to continue, A to abort (508 lines) >
1614 The page length will of course depend on what you have it set to!
1617 6.5. The Aliases file
1619 You will find a file in /spider/cmd/ called Aliases. This is the file
1620 that controls what a user gets when issuing a command. It is also
1621 possible to create your own aliases for databases and files you create
1625 You should not alter the original file in /spider/cmd/ but create a
1626 new file with the same name in /spider/local_cmd. This means that any
1627 new Aliases files that is downloaded will not overwrite your self
1628 created Aliases and also that you do not override any new Aliases with
1629 your copy in /spider/local_cmd/. You must remember that any files you
1630 store in /spider/local/ or /spider/local_cmd override the originals if
1631 the same lines are used in both files.
1634 The best way of dealing with all this then is to only put your own
1635 locally created Aliases in the copy in /spider/local_cmd. The example
1636 below is currently in use at GB7MBC.
1641 # Local Aliases File
1648 '^news$', 'type news', 'type',
1651 '^sh\w*/buck$', 'show/qrz', 'show',
1652 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1653 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1654 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1655 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1661 Each alphabetical section should be preceded by the initial letter and
1662 the section should be wrapped in square brackets as you can see. The
1663 syntax is straightforward. The first section on each line is the new
1664 command that will be allowed once the alias is included. The second
1665 section is the command it is replacing and the last section is the
1666 actual command that is being used.
1669 The eagle-eyed amongst you will have noticed that in the first
1670 section, the new alias command has a '^' at the start and a '$' at the
1671 end. Basically these force a perfect match on the alias. The '^'
1672 says match the beginning exactly and the with similar commands.
1675 I have 3 different types of alias in this file. At the top is an
1676 alias for 'news'. This is a file I have created in the
1677 /spider/packclus/ directory where I can inform users of new
1678 developments or points of interest. In it's initial form a user would
1679 have to use the command type news. The alias allows them to simply
1680 type news to get the info. Second is an alias for the show/qrz
1681 command so that those users used to the original show/buck command in
1682 AK1A will not get an error, and the rest of the lines are for locally
1683 created databases so that a user can type show/hftest instead of
1684 having to use the command dbshow hftest which is not as intuitive.
1687 This file is just an example and you should edit it to your own
1688 requirements. Once created, simply issue the command load/alias at
1689 the cluster prompt as the sysop user and the aliases should be
1696 In later versions of Spider a simple console program is provided for
1697 the sysop. This has a type ahead buffer with line editing facilities
1698 and colour for spots, announces etc. To use this program, simply use
1699 console.pl instead of client.
1702 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1703 edit the file with your favourite editor.
1706 6.7. Updating kepler data
1708 Spider has a powerful and flexible show/satellite command. In order
1709 for this to be accurate, the kepler data has to be updated regularly.
1710 In general, this data is available as an email or via cluster mail.
1711 Updating it is simple. First you need to export the mail message as a
1712 file. You do this with the export command from the cluster prompt as
1713 the sysop. For example ...
1717 export 5467 /spider/perl/keps.in
1721 would export message number 5467 as a file called keps.in in the
1722 /spider/perl directory.
1725 Now login to a VT as sysop and cd /spider/perl. There is a command in
1726 the perl directory called convkeps.pl. All we need to do now is
1727 convert the file like so ...
1731 ./convkeps.pl keps.in
1735 Now go back to the cluster and issue the command ...
1743 That is it! the kepler data has been updated.
1746 6.8. The QRZ callbook
1748 The command sh/qrz will only work once you have followed a few simple
1749 steps. First you need to get a user ID and password from qrz.com.
1750 Simply go to the site and create one. Secondly you need to copy the
1751 file /spider/perl/Internet.pm to /spider/local and alter it to match
1752 your user ID and password. You also at this point need to set
1753 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1754 proprieter of qrz.com for allowing this access.
1757 6.9. Connecting logging programs
1759 There appear to be very few logging programs out there that support
1760 telnet especially the popular ones like LogEQF, Turbolog etc. This
1761 can make it difficult to connect to your own cluster! The way to do
1762 it is to make the logging program think it has a TNC attached to a com
1763 port on the logging PC and 'push' a linux login out to it. This is
1764 achieved very simply by the use of agetty.
1767 All that is required is to add a line in /etc/inittab to have the
1768 client ready for a connection on the com port of your choice.
1769 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1774 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1778 Add this after the standard runlevel lines in /etc/inittab. The above
1779 line works on ttyS1 (com2). Now as root, issue the command telinit q
1780 and it should be ready for connection. All that is required is a 3
1781 wire serial lead (tx, rx and signal ground). Tell you logging program
1782 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1783 Login as normal and then telnet from there to the cluster.
1788 In the spider tree will be a directory spider-web. This is a neat
1789 little java web applet that can be run from a website. The applet
1790 must run on the same machine as the cluster. The included README file
1794 I should comment here that the applet is precompiled, that is, ready
1795 to go. It was compiled using JDK1.3.1. If your version is earlier
1796 than this then it may not work. Should that be the case you need to
1797 recompile or update your JDK. To recompile do the following ...
1801 cd /spider/spider-web
1803 /usr/bin/javac spiderclient.java
1807 I have used /usr/bin/javac as an example, your path to javac may be
1813 Completely based on a clx web client written in Java by dl6dbh
1814 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1816 The webserver has to run on the same machine as your DxSpider software!
1818 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1820 Installation instructions (Performed as root):
1822 Put all the files in the spider-web directory into a newly created directory
1823 under the DocumentRoot of your websever for instance 'client'. In my case
1824 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1825 path should be /usr/local/httpd/htdocs/client/ for example.
1827 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1828 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1829 /usr/local/httpd/cgi-bin/ for example.
1831 Change the permissions of the files to ensure they are correct, obviously you
1832 will need to use the correct path the the files according to your system:
1834 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1835 chmod -R 755 /home/httpd/html/client/
1837 By default the spider.cgi script should pick up your hostname (As long as this
1838 is set correctly). If it does not or your hostname differs from the name that
1839 you attach to the public address that you are using, then edit spider.cgi :
1841 # Uncomment and set the hostname manually here if the above fails.
1842 # $HOSTNAME = "gb7mbc.spoo.org" ;
1846 telnet (see Listeners.pm)
1848 NOTE: If you can start the console but cannot connect to the cluster from it,
1849 then it is possible that the machine you are on cannot resolve the hostname of
1850 your cluster machine. If this is the case, you need to set your hostname
1853 You also need to set the $NODECALL variable. This prints the name of your
1854 choosing (probably your cluster callsign) on the html page.
1856 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1860 8. Web based statistics
1862 From version 1.50, you can use the freeware software MRTG to produce
1863 really nice graphical statistics on your web site. For an example try
1864 http://www.gb7mbc.net/mrtg/stats.html.
1867 The following should help you get it all working.
1870 First you need to download the latest version of MRTG from
1871 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1872 the following files..
1876 libpng-1.0.14.tar.gz
1882 Login to your machine as the root user, put all the downloaded files
1883 in /usr/local/src/ (or wherever you prefer) and untar and compile
1884 them. All the information to compile and install these sources come
1885 with them. After compilation and installation, you will find MRTG in
1889 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1893 You now need to make 2 symbolic links like below...
1897 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1898 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1902 Now login to the cluster with your sysop callsign and run the command
1906 Now you are nearly there! Login as the sysop user and change to the
1907 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1912 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1916 Changing the callsign for your own cluster callsign of course!
1919 And finally you need to login as the root user and create one last
1920 symbolic link. Where this points will depend on where your html
1921 documents are kept. For RedHat systems you use...
1925 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1929 and for SuSE systems...
1933 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1937 If you now point your browser to your website as below it should all
1942 http://www.xxx.xxx/mrtg/stats.html
1946 Of course, to get the stats to update, you need to add some
1947 information in the spider crontab file as below...
1951 # Update stats for mrtg on website
1952 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1956 This will update the site every 5 minutes.
1961 From version 1.49 DXSpider has some additional security features.
1962 These are not by any means meant to be exhaustive, however they do
1963 afford some security against piracy. These two new features can be
1964 used independently of each other or in concert to tighten the
1970 The basic principle of registration is simple. If a user is not
1971 registered by the sysop, then they have read-only access to the
1972 cluster. The only thing they can actually send is a talk or a message
1973 to the sysop. In order for them to be able to spot, send announces or
1974 talks etc the sysop must register them with the set/register command,
1983 The user g0vgs can now fully use the cluster. In order to enable
1984 registration, you can issue the command ...
1986 set/var $main::reqreg = 1
1990 Any users that are not registered will now see the motd_nor file
1991 rather than the motd file as discussed in the Information, files and
1992 useful programs section.
1995 Entering this line at the prompt will only last for the time the
1996 cluster is running of course and would not be present on a restart.
1997 To make the change permanent, add the above line to
1998 /spider/scripts/startup. To read more on the startup file, see the
1999 section on Information, files and useful programs.
2002 To unregister a user use unset/register and to show the list of
2003 registered users, use the command show/register.
2008 At the moment, passwords only affect users who login to a DXSpider
2009 cluster node via telnet. If a user requires a password, they can
2010 either set it themselves or have the sysop enter it for them by using
2011 the set/password command. Any users who already have passwords, such
2012 as remote sysops, will be asked for their passwords automatically by
2013 the cluster. Using passwords in this way means that the user has a
2014 choice on whether to have a password or not. To force the use of
2015 passwords at login, issue the command ...
2019 set/var $main::passwdreq = 1
2023 at the cluster prompt. This can also be added to the
2024 /spider/scripts/startup file as above to make the change permanent.
2027 Of course, if you do this you will have to assign a password for each
2028 of your users. If you were asking them to register, it is anticipated
2029 that you would ask them to send you a message both to ask to be
2030 registered and to give you the password they wish to use.
2033 Should a user forget their password, it can be reset by the sysop by
2034 first removing the existing password and then setting a new one like
2039 unset/password g0vgs
2040 set/password g0vgs new_password
2048 10.1. CVS from a Linux platform
2050 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2051 is held at Sourceforge. This means that it is possible to update your
2052 DXSpider installation to the latest sources by using a few simple
2053 commands. A graphical interface to CVS for Windows is explained in
2057 Please be aware that if you update your system using CVS, it is
2058 possible that you could be running code that is very beta and not
2059 fully tested. There is a possibility that it could be unstable.
2062 I am of course assuming that you have a machine with both DXSpider and
2063 Internet access running.
2066 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2067 ENTIRE SPIDER TREE!!
2070 Assuming you are connected to the Internet, you need to login to the
2071 CVS repository and then update your Spider source. There are several
2072 steps which are listed below ...
2075 First login as the user sysop. Next you need to connect to the CVS
2076 repository. You do this with the command below ...
2079 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2083 You will get a password prompt. Simply hit return here and your
2084 machine should return to a normal linux prompt.
2087 What happens next depends on whether you have an existing installation
2088 that you want to update with the latest and greatest or whether you
2089 just want to see what is there and/or run it on a new machine for
2092 If you are installing Spider from CVS then change directory to
2095 If you are wanting to update Spider then cd to /tmp
2098 The next step will create a brand new 'spider' directory in your
2102 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2106 This command is all on one line.
2109 Hopefully your screen should show you downloading files. The -z3
2110 simply compresses the download to improve speed. When this has
2111 finished, you will have exactly the same as if you had untarred a full
2112 tarball PLUS some extra directories and files that CVS needs to do the
2114 Now if you are doing a new installation, that's it. Carry on as if
2115 you have just downloaded and untarred the lastest tarball.
2118 If you want to upgrade your current installation then do this ...
2122 tar cvfz /tmp/s.tgz spider
2124 tar xvfzp /tmp/s.tgz
2128 This is assuming you downloaded to the /tmp directory of course.
2131 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2132 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2135 Remember to recompile the C client (cd /spider/src; make)
2138 At this point the files have been upgraded. You can (usually) restart
2139 the cluster in your own time. However, if you attempt to use any new
2140 commands or features expect it to be fatal! At least your cluster
2141 will have been restarted then so it will be too late to worry about
2145 Now the magic part! From now on when you want to update, simply
2146 connect to the Internet and then, as the user sysop ...
2155 and your files will be updated. As above, remember to recompile the
2156 "C" client if it has been updated (CVS will tell you) and restart if
2157 any of the perl scripts have been altered or added, again, CVS will
2161 You will find any changes documented in the /spider/Changes file.
2164 10.2. CVS from a Windows platform
2166 After the initial setup, an update to your DXSpider software is no
2167 more than a couple of clicks away. This section is intended to
2168 explain and illustrate the use of the WinCVS application to update
2169 your DXSpider software. The current stable version of WinCVS is Ver.
2170 1.2. You can get this software at:
2172 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2174 Pick your download mirror and then install WinCVS after the download
2178 In this next section I have included a series of links to .jpg files
2179 to take advantage of the picture and 1000 words equivalency. The .jpg
2180 files are in the C:\spider\html directory. If someone using a Linux
2181 system is reading this section from boredom, the files are in
2182 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2183 of gcvs and do your updates graphically as opposed to from the command
2184 line. The following descriptions are almost identical between WinCvs
2185 and gcvs. The following screen shots have duplicate links, depending
2186 upon whether you are viewing this information under the Windows or
2187 Linux operating system.
2189 When WinCVS is installed, running, and you are connected to the
2190 internet, the initial screen looks like:
2194 If you want, you can also look at these .jpg files with another viewer
2195 that might provide some better clarity to the image. On the left is
2196 the directory tree for your hard disk. Notice that the spider
2197 directory has a gray highlight.
2199 To start configuring WinCVS, click on Admin at the top of the screen
2200 and then Preferences. This should get you:
2204 In the top line for CVSROOT, enter:
2207 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2214 "passwd" file on the cvs server
2218 for Authentication on the General tab.
2220 Next, move to the right to the Ports tab.
2224 In here, check the box on the second line down for the "pserver" port.
2225 Enter a port number of 2401.
2227 Finally, go to the WinCvs tab all the way to the right.
2231 Enter Notepad as the viewer to open files. For the HOME folder, put
2232 "C:\spider" and click OK because the configuration is now complete.
2234 You are now ready to upgrade your copy of DXSpider. Click on the
2235 greyed Spider folder shown in the directory tree on the left of the
2236 WinCVS display. Two things should happen. The Spider folder will be
2237 selected and the greyed-out arrow located just below the word Query in
2238 the top line will turn to solid green.
2240 For anyone using gcvs under Linux, the green arrow is located on the
2241 extreme left of the display, under the word File. A gcvs screen looks
2246 Click on the now green arrow to start the download process. An Update
2247 Settings box will be displayed to which you can simply say OK.
2251 For future reference, the Update Settings box is the place where you
2252 can enter information to revert to a prior version of DXSpider.
2253 Information on reverting to a Before Date is contained in the WinCVS
2256 After a short period of time, a series of file names will scroll by in
2257 the lower pane of the WinCVS window. Eventually you should see
2260 *****CVS exited normally with code 0*****
2264 appear in the lower pane. You're done. The updated files are in
2265 place ready for you to stop and then restart your DXSpider. After the
2266 restart, you're running with the latest version of DXSpider.
2270 To paraphrase from the CVS section... Now the magic part! From now on
2271 when you want to update, simply connect to the Internet and start
2275 Click on the greyed-out Spider directory in the left screen
2276 Click on the green down arrow
2277 Click OK on the Update Settings dialog box
2278 Restart your Spider software
2282 11. The DXSpider command set
2286 accept Set a filter to accept something
2288 Create a filter to accept somethingThere are 2 types of filter, accept
2289 and reject. See HELP FILTERING for moreinfo.
2291 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
2293 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2296 This version allows a sysop to set a filter for a callsign as well as
2297 thedefault for nodes and users eg:-
2300 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2304 11.3. accept/announce [0-9] <pattern> (0)
2306 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2309 Create an 'accept this announce' line for a filter. An accept filter
2310 line means that if the announce matches this filter it ispassed onto
2311 the user. See HELP FILTERING for more info. Please read thisto
2312 understand how filters work - it will save a lot of grief later on.You
2313 can use any of the following things in this line:-
2316 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)
2323 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)
2337 acc/ann by_state va,nh,ri,nh
2341 You can use the tag 'all' to accept everything eg:
2348 but this probably for advanced users...
2350 11.4. accept/route <call> [0-9] <pattern> (8)
2352 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2355 Create an 'accept this routing PC Protocol' line for a filter. An
2356 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2357 filter it is passed thru that interface. See HELP FILTERING for more
2358 info. Please read thisto understand how filters work - it will save a
2359 lot of grief later on.You can use any of the following things in this
2363 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
2370 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2374 you can now use 'by' as a synonym for 'call' so:
2377 by = call by_dxcc = call_dxcc
2381 and so onYou can use the tag 'all' to accept everything eg:
2388 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
2390 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2392 This version allows a sysop to set a filter for a callsign as well as
2393 thedefault for nodes and users eg:-
2396 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2400 accept/spot user_default by G,M,2
2404 11.6. accept/spots [0-9] <pattern> (0)
2406 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2408 Create an 'accept this spot' line for a filter. An accept filter line
2409 means that if the spot matches this filter it ispassed onto the user.
2410 See HELP FILTERING for more info. Please read thisto understand how
2411 filters work - it will save a lot of grief later on.You can use any of
2412 the following things in this line:-
2415 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>
2419 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2423 You can use the tag 'all' to accept everything, eg:
2433 acc/spots by_state VA,NH,RI,MA,ME
2437 but this probably for advanced users...
2439 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
2441 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2443 This version allows a sysop to set a filter for a callsign as well as
2444 thedefault for nodes and users eg:-
2447 accept/wcy node_default all set/hops node_default 10
2451 11.8. accept/wcy [0-9] <pattern> (0)
2453 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2455 It is unlikely that you will want to do this, but if you do then you
2456 canfilter on the following fields:-
2459 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>
2463 There are no examples because WCY Broadcasts only come from one place
2464 andyou either want them or not (see UNSET/WCY if you don't want
2465 them).This command is really provided for future use.See HELP FILTER
2468 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
2470 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2472 This version allows a sysop to set a filter for a callsign as well as
2473 thedefault for nodes and users eg:-
2476 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2480 accept/wwv user_default by W,K
2484 11.10. accept/wwv [0-9] <pattern> (0)
2486 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2488 It is unlikely that you will want to do this, but if you do then you
2489 canfilter on the following fields:-
2492 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>
2499 accept/wwv by_zone 4
2503 is probably the only useful thing to do (which will only show WWV
2504 broadcastsby stations in the US).See HELP FILTER for information.
2506 11.11. announce <text> (0)
2508 announce <text> Send an announcement to LOCAL users only
2510 <text> is the text of the announcement you wish to broadcast
2512 11.12. announce full <text> (0)
2514 announce full <text> Send an announcement cluster wide
2516 This will send your announcement cluster wide
2518 11.13. announce sysop <text> (5)
2520 announce sysop <text> Send an announcement to Sysops only
2523 11.14. apropos <string> (0)
2525 apropos <string> Search help database for <string>
2527 Search the help database for <string> (it isn't case sensitive), and
2528 printthe names of all the commands that may be relevant.
2530 11.15. blank [<string>] [<nn>] (0)
2532 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2534 In its basic form this command prints one or more blank lines. However
2535 ifyou pass it a string it will replicate the string for the width of
2536 the screen (default 80) and then print that one or more times, so:
2543 prints two blank lines
2550 prints a row of - characters once.
2557 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2558 script file and you can print a maximumof 9 lines.
2562 bye Exit from the cluster
2564 This will disconnect you from the cluster
2566 11.17. catchup <node call> all|[<msgno> ...] (5)
2568 catchup <node call> all|[<msgno> ...] Mark a message as sent
2571 11.18. clear/announce <callsign> [input] [0-9|all] (8)
2573 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2576 A sysop can clear an input or normal output filter for a user or
2577 thenode_default or user_default.
2579 11.19. clear/announce [1|all] (0)
2581 clear/announce [1|all] Clear a announce filter line
2583 This command allows you to clear (remove) a line in a annouce filter
2584 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2587 11.20. clear/route <callsign> [input] [0-9|all] (8)
2589 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2591 A sysop can clear an input or normal output filter for a user or
2592 thenode_default or user_default.
2594 11.21. clear/route [1|all] (0)
2596 clear/route [1|all] Clear a route filter line
2598 This command allows you to clear (remove) a line in a route filter or
2599 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2602 11.22. clear/spots <callsign> [input] [0-9|all] (8)
2604 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2606 A sysop can clear an input or normal output filter for a user or
2607 thenode_default or user_default.
2609 11.23. clear/spots [0-9|all] (0)
2611 clear/spots [0-9|all] Clear a spot filter line
2613 This command allows you to clear (remove) a line in a spot filter or
2614 to remove the whole filter.If you have a filter:-
2617 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2627 you will be left with:-
2630 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2641 the filter will be completely removed.
2643 11.24. clear/wcy <callsign> [input] [0-9|all] (8)
2645 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2647 A sysop can clear an input or normal output filter for a user or
2648 thenode_default or user_default.
2650 11.25. clear/wcy [1|all] (0)
2652 clear/wcy [1|all] Clear a WCY filter line
2654 This command allows you to clear (remove) a line in a WCY filter or to
2655 remove the whole filter.see CLEAR/SPOTS for a more detailed
2658 11.26. clear/wwv <callsign> [input] [0-9|all] (8)
2660 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2662 A sysop can clear an input or normal output filter for a user or
2663 thenode_default or user_default.
2665 11.27. clear/wwv [1|all] (0)
2667 clear/wwv [1|all] Clear a WWV filter line
2669 This command allows you to clear (remove) a line in a WWV filter or to
2670 remove the whole filter.see CLEAR/SPOTS for a more detailed
2673 11.28. connect <callsign> (5)
2675 connect <callsign> Start a connection to another DX Cluster
2677 Start a connection process that will culminate in a new connection to
2678 theDX cluster <callsign>. This process creates a new 'client' process
2679 which willuse the script in /spider/connect/<callsign> to effect the
2680 'chat' exchangenecessary to traverse the network(s) to logon to the
2685 dbavail Show a list of all the Databases in the system
2687 Title says it all really, this command lists all the databases
2688 definedin the system. It is also aliased to SHOW/COMMAND.
2689 11.30. dbcreate <name> (9)
2691 dbcreate <name> Create a database entry
2694 11.31. dbcreate <name> chain <name> [<name>..] (9)
2696 dbcreate <name> chain <name> [<name>..] Create a chained database
2700 11.32. dbcreate <name> cmd <dxspider command> (9)
2702 dbcreate <name> cmd <dxspider command> make a local command available
2705 DBCREATE allows you to define a database in the system. It doesn't
2706 actuallycreate anything, just defines it.The databases that are
2707 created are simple DB_File hash databases, they are therefore already
2708 'indexed'.You can define a local database with the first form of the
2716 You can also chain databases with the addition of the 'chain' keyword.
2717 This will search each database one after the other. A typical example
2721 DBCREATE sdx_qsl chain sql_ad
2725 No checking is done to see if the any of the chained databases exist,
2726 infact it is usually better to do the above staement first then do
2727 each ofthe chained databases.Databases can exist offsite. To define a
2728 database that lives on another node do:
2731 DBCREATE buckmaster remote gb7dxc
2735 Remote databases cannot be chained; however, the last database in a a
2736 chain can be a remote database eg:
2739 DBCREATE qsl chain gb7dxc
2743 To see what databases have been defined do:
2746 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2750 It would be normal for you to add an entry into your local Aliases
2751 fileto allow people to use the 'SHOW/<dbname>' style syntax. So you
2752 wouldneed to add a line like:-
2755 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
2766 to work as they may be used to.You can also make local commands avail-
2767 able as 'pseudo' databases. Youcan therefore make spider special com-
2768 mands available as a database. Iimagine that this will be primarily
2769 useful for remote access from legacy nodes. For example:-
2772 DBCREATE dxqsl cmd show/dxqsl
2776 You also use one of these databases in a chain. This may be useful
2777 locally. See DBIMPORT for the importing of existing AK1A format data
2778 to databases.See DBSHOW for generic database enquiry
2780 11.33. dbcreate <name> remote <node> (9)
2782 dbcreate <name> remote <node> Create a remote database entry
2785 11.34. dbimport <dbname> <filename> (9)
2787 dbimport <dbname> <filename> Import AK1A data into a database
2789 If you want to import or update data in bulk to a database you can
2790 usethis command. It will either create or update entries into an
2791 existingdatabase. For example:-
2794 DBIMPORT oblast /tmp/OBLAST.FUL
2798 will import the standard OBLAST database that comes with AK1A into
2799 theoblast database held locally.
2801 11.35. dbremove <dbname> (9)
2803 dbremove <dbname> Delete a database
2805 DBREMOVE will completely remove a database entry and also delete any
2806 datafile that is associated with it. There is no warning, no comeback,
2807 no safety net. For example:
2814 will remove the oblast database from the system and it will also
2815 removethe associated datafile.I repeat:There is no warning, no come-
2816 back, no safety net.You have been warned.
2820 11.36. dbshow <dbname> <key> (0)
2822 dbshow <dbname> <key> Display an entry, if it exists, in a database
2824 This is the generic user interface to the database to the database
2825 system.It is expected that the sysop will add an entry to the local
2826 Aliases fileso that users can use the more familiar AK1A style of
2834 but if he hasn't and the database really does exist (use DBAVAIL
2835 orSHOW/COMMAND to find out) you can do the same thing with:
2844 debug Set the cluster program into debug mode
2846 Executing this command will only have an effect if you are running the
2847 clusterin debug mode i.e.
2854 It will interrupt the cluster just after the debug command has fin-
2857 11.38. delete/usdb <callsign> ... (9)
2859 delete/usdb <callsign> ... Delete this user from the US State Database
2861 This command will completely remove a one or more callsignsfrom the US
2862 States database.There is NO SECOND CHANCE.It goes without saying that
2863 you should use this command CAREFULLY!Note that these callsign may be
2864 re-instated by any weekly updates from the FCC.
2866 11.39. delete/user <callsign> ... (9)
2868 delete/user <callsign> ... Delete this user from the User Database
2870 This command will completely remove a one or more users from the
2871 database.There is NO SECOND CHANCE.It goes without saying that you
2872 should use this command CAREFULLY!
2874 11.40. demonstrate <call> <command> (9)
2876 demonstrate <call> <command> Demonstrate a command to another user
2878 This command is provided so that sysops can demonstrate commands to
2879 other users. It runs a command as though that user had typed it in
2880 andthen sends the output to that user, together with the command that
2885 DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
2889 Note that this command is similar to SPOOF and will have the same
2890 sideeffects. Commands are run at the privilege of the user which is
2891 beingdemonstrated to.
2893 11.41. directory (0)
2895 directory List messages
2898 11.42. directory <from>-<to> (0)
2900 directory <from>-<to> List messages <from> message <to> message
2902 List the messages in the messages directory.If there is a 'p' one
2903 space after the message number then it is a personal message. If there
2904 is a '-' between the message number and the'p' then this indicates
2905 that the message has been read.You can use shell escape characters
2906 such as '*' and '?' in the <call>fields.You can combine some of the
2907 various directory commands together eg:-
2917 DIR SUBJECT IOTA 200-250
2921 You can abbreviate all the commands to one letter and use ak1a syn-
2925 DIR/T G1* 10 DIR/S QSL 10-100 5
2929 11.43. directory <nn> (0)
2931 directory <nn> List last <nn> messages
2934 11.44. directory all (0)
2936 directory all List all messages
2939 11.45. directory from <call> (0)
2941 directory from <call> List all messages from <call>
2944 11.46. directory new (0)
2946 directory new List all new messages
2950 11.47. directory own (0)
2952 directory own List your own messages
2955 11.48. directory subject <string> (0)
2957 directory subject <string> List all messages with <string> in subject
2960 11.49. directory to <call> (0)
2962 directory to <call> List all messages to <call>
2965 11.50. directory- (5)
2969 Sysops can see all users' messages.
2971 11.51. disconnect <call> [<call> ...] (8)
2973 disconnect <call> [<call> ...] Disconnect a user or cluster
2975 Disconnect any <call> connected locally
2977 11.52. dx [by <call>] <freq> <call> <remarks> (0)
2979 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2981 This is how you send a DX Spot to other users. You can, in fact,
2982 nowenter the <freq> and the <call> either way round.
2985 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
2989 will all give the same result. You can add some remarks to the endof
2990 the command and they will be added to the spot.
2993 DX FR0G 144600 this is a test
2997 You can credit someone else by saying:-
3000 DX by G1TLH FR0G 144.600 he isn't on the cluster
3004 The <freq> is compared against the available bands set up in the clus-
3005 ter. See SHOW/BANDS for more information.
3007 11.53. echo <line> (0)
3009 echo <line> Echo the line to the output
3011 This command is useful in scripts and so forth for printing theline
3012 that you give to the command to the output. You can use thisin
3013 user_default scripts and the SAVE command for titling and so forthThe
3014 script will interpret certain standard "escape" sequences as follows:-
3016 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
3020 So the following example:-
3023 echo GB7DJK is a dxcluster
3030 GB7DJK is a dxcluster
3034 on the output. You don't need a \n on the end of the line you want to
3035 send.A more complex example:-
3038 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
3045 GB7DJK g1tlh Dirk g3xvf Richard
3051 11.54. export <msgno> <filename> (9)
3053 export <msgno> <filename> Export a message to a file
3055 Export a message to a file. This command can only be executed on a
3056 localconsole with a fully privileged user. The file produced will be
3057 in a formready to be imported back into the cluster by placing it in
3058 the import directory (/spider/msg/import).This command cannot
3059 overwrite an existing file. This is to provide some measure of
3060 security. Any files written will owned by the same user as the main
3061 cluster, otherwise you can put the new files anywhere the cluster
3062 canaccess. For example:-
3069 11.55. export_users [<filename>] (9)
3071 export_users [<filename>] Export the users database to ascii
3073 Export the users database to a file in ascii format. If no filenameis
3074 given then it will export the file to /spider/data/user_asc.If the
3075 file already exists it will be renamed to <filename>.o. In factup to 5
3076 generations of the file can be kept each one with an extra 'o' on
3077 thesuffix. BE WARNED: this will write to any file you have write
3078 access to. No check ismade on the filename (if any) that you specify.
3081 11.56. filtering... (0)
3083 filtering... Filtering things in DXSpider
3085 There are a number of things you can filter in the DXSpider system.
3086 Theyall use the same general mechanism.In general terms you can create
3087 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
3088 You do this using, for example:-
3091 accept/spots ..... reject/spots .....
3095 where ..... are the specific commands for that type of filter. There-
3096 are filters for spots, wwv, announce, wcy and (for sysops)connects.
3097 See each different accept or reject command reference formore
3098 details.There is also a command to clear out one or more lines in a
3099 filter andone to show you what you have set. They are:-
3102 clear/spots 1 clear/spots all
3113 There is clear/xxxx command for each type of filter.For now we are
3114 going to use spots for the examples, but you can applythe principles
3115 to all types of filter.There are two main types of filter 'accept' or
3116 'reject'; which you usedepends entirely on how you look at the world
3117 and what is leastwriting to achieve what you want. Each filter has 10
3118 lines (of anylength) which are tried in order. If a line matches then
3119 the actionyou have specified is taken (ie reject means ignore it and
3120 acceptmeans gimme it).The important thing to remember is that if you
3121 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
3122 instance)) then ifa spot comes in that doesn't match any of the lines
3123 then you will getit BUT if you specify an 'accept' filter then any
3124 spots that don'tmatch are dumped. For example if I have a one line
3128 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3132 then automatically you will ONLY get VHF spots from or to CQ zones
3133 1415 and 16. If you set a reject filter like:
3136 reject/spots on hf/cw
3140 Then you will get everything EXCEPT HF CW spots, If you am interested
3141 in IOTAand will work it even on CW then you could say:-
3144 reject/spots on hf/cw and not info iota
3147 But in that case you might only be interested in iota and say:-
3150 accept/spots not on hf/cw or info iota
3154 which is exactly the same. You should choose one or the other untilyou
3155 are confortable with the way it works. Yes, you can mix them(actually
3156 you can have an accept AND a reject on the same line) butdon't try
3157 this at home until you can analyse the results that you getwithout
3158 ringing up the sysop for help.Another useful addition now is filtering
3162 accept/spots by_state VA,NH,RI,ME
3166 You can arrange your filter lines into logical units, either for
3167 yourown understanding or simply convenience. I have one set fre-
3171 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
3175 What this does is to ignore all HF CW spots (being a class B I
3176 can'tread any CW and couldn't possibly be interested in HF :-) and
3177 alsorejects any spots on VHF which don't either originate or spot
3178 someonein Europe.This is an exmaple where you would use the line num-
3179 ber (1 and 2 inthis case), if you leave the digit out, the system
3180 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
3181 out if you want, it is implied. You canuse any number of brackets to
3182 make the 'expression' as you wantit. There are things called prece-
3183 dence rules working here which meanthat you will NEED brackets in a
3184 situation like line 2 because,without it, will assume:-
3187 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
3191 annoying, but that is the way it is. If you use OR - usebrackets.
3192 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
3193 by_zone'.If you want to alter your filter you can just redefine one or
3194 morelines of it or clear out one line. For example:-
3197 reject/spots 1 on hf/ssb
3208 To remove the filter in its entirty:-
3213 There are similar CLEAR commands for the other filters:-
3216 clear/announce clear/wcy clear/wwv
3220 ADVANCED USERS:-Once you are happy with the results you get, you may
3221 like to experiment. my example that filters hf/cw spots and accepts
3222 vhf/uhf spots from EUcan be written with a mixed filter, eg:
3225 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)
3229 each filter slot actually has a 'reject' slot and an 'accept'slot. The
3230 reject slot is executed BEFORE the accept slot.It was mentioned ear-
3231 lier that after a reject test that doesn't match,the default for fol-
3232 lowing tests is 'accept', the reverse is true for'accept'. In the
3233 example what happens is that the reject is executedfirst, any non
3234 hf/cw spot is passed to the accept line, which letsthru everything
3235 else on HF.The next filter line lets through just VHF/UHF spots from
3238 11.57. forward/latlong <node_call> (8)
3240 forward/latlong <node_call> Send latitude and longitude information to
3243 This command sends all the latitude and longitude information that
3244 yourcluster is holding against callsigns. One advantage of recieving
3245 thisinformation is that more locator information is held by you.
3246 Thismeans that more locators are given on the DX line assuming you
3247 haveSET/DXGRID enabled. This could be a LOT of information though,
3248 soit is not recommended on slow links.
3250 11.58. forward/opernam <call> (1)
3252 forward/opernam <call> Send out information on this <call> to all
3255 This command sends out any information held in the user file which can
3256 be broadcast in PC41 protocol packets. This information is Name, QTH,
3257 Locationand Homenode. PC41s are only sent for the information that is
3262 help The HELP Command
3264 HELP is available for a number of commands. The syntax is:-
3271 Where <cmd> is the name of the command you want help on.All commands
3272 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3273 can be shortened to AN and so on.Look at the APROPOS <string> command
3274 which will search the help databasefor the <string> you specify and
3275 give you a list of likely commandsto look at with HELP.
3279 11.60. init <node> (5)
3281 init <node> Re-initialise a link to an AK1A compatible node
3283 This command attempts to re-initialise a link to a (usually) AK1A
3284 nodethat has got confused, usually by a protocol loop of some kind. It
3285 maywork - but you usually will be better off simply disconnecting it
3286 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3287 <yournode>).Best of luck - you will need it.
3293 As a sysop you can kill any message on the system.
3295 11.62. kill <from msgno>-<to msgno> (0)
3297 kill <from msgno>-<to msgno> Delete a range of messages
3300 11.63. kill <from>-<to> (5)
3302 kill <from>-<to> Remove a range of messages from the system
3305 11.64. kill <msgno> [<msgno..] (0)
3307 kill <msgno> [<msgno..] Delete a message from the local system
3310 11.65. kill <msgno> [<msgno> ...] (0)
3312 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3314 You can get rid of any message to or originating from your callsign
3315 using this command. You can remove more than one message at a time.
3317 11.66. kill expunge <msgno> [<msgno..] (6)
3319 kill expunge <msgno> [<msgno..] Expunge a message
3321 Deleting a message using the normal KILL commands only marks that
3322 messagefor deletion. The actual deletion only happens later (usually
3323 two days later).The KILL EXPUNGE command causes the message to be
3324 truly deleted more or lessimmediately.It otherwise is used in the same
3325 way as the KILL command.
3327 11.67. kill from <call> (5)
3329 kill from <call> Remove all messages from a callsign
3332 11.68. kill full <msgno> [<msgno..] (5)
3334 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3336 Delete a message from the local system. You will only be able todelete
3337 messages that you have originated or been sent (unless you arethe
3345 Will delete all the messages that you own between msgnos 1234 and
3353 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3360 will delete all messages to g1tlh.
3367 will delete a message (usually a 'bulletin') from the whole cluster
3368 system. This uses the subject field, so any messages that have exactly
3369 thesame subject will be deleted. Beware!
3371 11.69. kill full <msgno> [<msgno] (5)
3373 kill full <msgno> [<msgno] Remove a message from the entire cluster
3375 Remove this message from the entire cluster system as well as your
3378 11.70. kill to <call> (5)
3380 kill to <call> Remove all messages to a callsign
3383 11.71. kill from <regex> (0)
3385 kill from <regex> Delete messages FROM a callsign or pattern
3388 11.72. kill to <regex> (0)
3390 kill to <regex> Delete messages TO a callsign or pattern
3395 links Show which nodes is physically connected
3397 This is a quick listing that shows which links are connected andsome
3398 information about them. See WHO for a list of all connections.
3400 11.74. load/aliases (9)
3402 load/aliases Reload the command alias table
3404 Reload the /spider/cmd/Aliases file after you have editted it. Youwill
3405 need to do this if you change this file whilst the cluster isrunning
3406 in order for the changes to take effect.
3410 11.75. load/badmsg (9)
3412 load/badmsg Reload the bad msg table
3414 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3415 whilstthe cluster is running. This table contains a number of perl
3416 regular expressions which are searched for in the fields targetted of
3417 each message. If any of them match then that message is immediately
3420 11.76. load/badwords (9)
3422 load/badwords Reload the bad words table
3424 Reload the /spider/data/badwords file if you have changed it manually
3425 whilstthe cluster is running. This file contains a list of words
3426 which, if foundon certain text portions of PC protocol, will cause
3427 those protocol framesto be rejected. It will all put out a message if
3428 any of these words areused on the announce, dx and talk commands. The
3429 words can be one or more on a line, lines starting with '#' are
3432 11.77. load/bands (9)
3434 load/bands Reload the band limits table
3436 Reload the /spider/data/bands.pl file if you have changed it manually
3437 whilstthe cluster is running.
3439 11.78. load/cmd_cache (9)
3441 load/cmd_cache Reload the automatic command cache
3443 Normally, if you change a command file in the cmd or local_cmd tree
3444 itwill automatially be picked up by the cluster program. Sometimes
3445 itcan get confused if you are doing a lot of moving commands about
3446 ordelete a command in the local_cmd tree and want to use the normal
3447 oneagain. Execute this command to reset everything back to the state
3448 itwas just after a cluster restart.
3450 11.79. load/forward (9)
3452 load/forward Reload the msg forwarding routing table
3454 Reload the /spider/msg/forward.pl file if you have changed itmanually
3455 whilst the cluster is running.
3457 11.80. load/keps (5)
3459 load/keps Load new keps data
3462 11.81. load/keps [nn] (5)
3464 load/keps [nn] Load new keps data from message
3466 If there is no message number then reload the current Keps data
3467 fromthe Keps.pm data file. You create this file by running
3470 /spider/perl/convkeps.pl <filename>
3474 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3475 there is a message number, then it will take the message,
3476 runconvkeps.pl on it and then load the data, all in one step.These
3477 messages are sent to ALL by GB7DJK (and others) from time to time.
3479 11.82. load/messages (9)
3481 load/messages Reload the system messages file
3483 If you change the /spider/perl/Messages file (usually
3484 whilstfiddling/writing new commands) you can have them take effect
3485 during acluster session by executing this command. You need to do this
3486 if getsomething like :-unknown message 'xxxx' in lang 'en'
3488 11.83. load/prefixes (9)
3490 load/prefixes Reload the prefix table
3492 Reload the /spider/data/prefix_data.pl file if you have changed
3493 itmanually whilst the cluster is running.
3495 11.84. merge <node> [<no spots>/<no wwv>] (5)
3497 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3499 MERGE allows you to bring your spot and wwv database up to date. By
3500 defaultit will request the last 10 spots and 5 WWVs from the node you
3501 select. The node must be connected locally.You can request any number
3502 of spots or wwv and although they will be appendedto your databases
3503 they will not duplicate any that have recently been added (the last 2
3504 days for spots and last month for WWV data).
3506 11.85. msg <cmd> <msgno> [data ... ] (9)
3508 msg <cmd> <msgno> [data ... ] Alter various message parameters
3510 Alter message parameters like To, From, Subject, whether private or
3511 bulletinor return receipt (RR) is required or whether to keep this
3512 message from timingout.
3515 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
3519 You can look at the status of a message by using:-
3526 This will display more information on the message than DIR does.
3528 11.86. pc <call> <text> (8)
3530 pc <call> <text> Send arbitrary text to a connected callsign
3532 Send some arbitrary text to a locally connected callsign. Noprocessing
3533 is done on the text. This command allows you to send PCProtocol to
3534 unstick things if problems arise (messages get stucketc). eg:-
3537 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3544 pc G1TLH Try doing that properly!!!
3548 Send any text you like to the callsign requested. This is used mainly
3549 to sendPC protocol to connected nodes either for testing or to unstick
3550 things. You can also use in the same way as a talk command to a con-
3551 nected user butwithout any processing, added of "from <blah> to <blah"
3554 11.87. ping <node call> (1)
3556 ping <node call> Check the link quality between nodes
3558 This command allows you to send a frame to another cluster node onthe
3559 network and get a return frame. The time it takes to do thisis a good
3560 indication of the quality of the link. The actual timeit takes is
3561 output to the console in seconds.Any visible cluster node can be
3564 11.88. rcmd <node call> <cmd> (1)
3566 rcmd <node call> <cmd> Send a command to another DX Cluster
3568 This command allows you to send nearly any command to another DX
3569 Clusternode that is connected to the system. Whether you get any
3570 output is dependant on a) whether the other system knowsthat the node
3571 callsign of this cluster is in fact a node b) whether theother system
3572 is allowing RCMDs from this node and c) whether you havepermission to
3573 send this command at all.
3577 read Read the next unread personal message addressed to you
3580 11.90. read <msgno> (0)
3582 read <msgno> Read the specified message
3584 You can read any messages that are sent as 'non-personal' and also
3585 anymessage either sent by or sent to your callsign.
3591 As a sysop you may read any message on the system
3595 reject Set a filter to reject something
3597 Create a filter to reject somethingThere are 2 types of filter, accept
3598 and reject. See HELP FILTERING for moreinfo.
3600 11.93. reject/announce <call> [input] [0-9] <pattern> (8)
3602 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3605 This version allows a sysop to set a filter for a callsign as well as
3606 thedefault for nodes and users eg:-
3607 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3611 11.94. reject/announce [0-9] <pattern> (0)
3613 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3616 Create an 'reject this announce' line for a filter. A reject filter
3617 line means that if the announce matches this filter it ispassed onto
3618 the user. See HELP FILTERING for more info. Please read thisto
3619 understand how filters work - it will save a lot of grief later on.You
3620 can use any of the following things in this line:-
3623 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)
3630 rej/ann by_zone 14,15,16 and not by G,M,2
3634 You can use the tag 'all' to reject everything eg:
3641 but this probably for advanced users...
3643 11.95. reject/route <call> [0-9] <pattern> (8)
3645 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3648 Create an 'reject this routing PC Protocol' line for a filter. An
3649 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3650 filter it is NOT passed thru that interface. See HELP FILTERING for
3651 more info. Please read this to understand how filters work - it will
3652 save a lot of grief later on.You can use any of the following things
3656 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
3663 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3667 You can use the tag 'all' to reject everything eg:
3670 rej/route all (equiv to [very] restricted mode)
3672 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3674 11.96. reject/spots <call> [input] [0-9] <pattern> (8)
3676 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3678 This version allows a sysop to set a filter for a callsign as well as
3679 thedefault for nodes and users eg:-
3682 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3686 reject/spot user_default by G,M,2
3690 11.97. reject/spots [0-9] <pattern> (0)
3692 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3694 Create a 'reject this spot' line for a filter. A reject filter line
3695 means that if the spot matches this filter it isdumped (not passed
3696 on). See HELP FILTERING for more info. Please read thisto understand
3697 how filters work - it will save a lot of grief later on.You can use
3698 any of the following things in this line:-
3701 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>
3705 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3709 You can use the tag 'all' to reject everything eg:
3716 but this probably for advanced users...
3718 11.98. reject/wcy <call> [input] [0-9] <pattern> (8)
3720 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3722 This version allows a sysop to set a filter for a callsign as well as
3723 thedefault for nodes and users eg:-
3726 reject/wcy gb7djk all
3730 11.99. reject/wcy [0-9] <pattern> (0)
3732 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3734 It is unlikely that you will want to do this, but if you do then you
3735 canfilter on the following fields:-
3738 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>
3742 There are no examples because WCY Broadcasts only come from one place
3743 andyou either want them or not (see UNSET/WCY if you don't want
3744 them).This command is really provided for future use.See HELP FILTER
3747 11.100. reject/wwv <call> [input] [0-9] <pattern> (8)
3749 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3751 This version allows a sysop to set a filter for a callsign as well as
3752 thedefault for nodes and users eg:-
3755 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3759 reject/wwv user_default by W
3763 11.101. reject/wwv [0-9] <pattern> (0)
3765 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3767 It is unlikely that you will want to do this, but if you do then you
3768 canfilter on the following fields:-
3771 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>
3778 reject/wwv by_zone 14,15,16
3782 is probably the only useful thing to do (which will only show WWV
3783 broadcastsby stations in the US).See HELP FILTER for information.
3787 reply Reply (privately) to the last message that you have read
3791 11.103. reply <msgno> (0)
3793 reply <msgno> Reply (privately) to the specified message
3796 11.104. reply b <msgno> (0)
3798 reply b <msgno> Reply as a Bulletin to the specified message
3801 11.105. reply noprivate <msgno> (0)
3803 reply noprivate <msgno> Reply as a Bulletin to the specified message
3806 11.106. reply rr <msgno> (0)
3808 reply rr <msgno> Reply to the specified message with read receipt
3810 You can reply to a message and the subject will automatically
3811 have"Re:" inserted in front of it, if it isn't already present.You can
3812 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3813 that you can use with the SEND command (see SENDfor further details)
3815 11.107. save [-d -t -a] <filename> "<cmd>" [...] (9)
3817 save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
3819 This sysop only cammand allows you to save the output of one or
3820 morecommands to a file. For example:-
3823 save /spider/packclus/dxstats show/dxstat
3827 will save the output of the normal command "show/dxstat" to the
3828 file"dxstats" in the files area.You can have some extra flags to the
3829 save which will either date stamp or time stamp or both the filename
3833 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
3837 The -a flag means append to the file instead of overwriting it.You can
3838 have more than one command on the line, to do this you MUSTenclose
3839 each command in double quotes (") eg:-
3842 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
3849 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
3853 You can only write into places that the cluster has permission for
3854 (whichis that of the "sysop" user [which had BETTER NOT BE "root"]),
3855 you will need to create any directories you want to put stuff in
3856 beforehand as well.It is likely that you will want to run these
3857 commands in a crontab type situation. You would do that something
3861 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
3865 Note that you still enclose each command with (") characters but you
3866 mustenclose the entire save command in (') characters. Now in fact,
3867 this can be varied if you know what you are doing. See theadmin manual
3870 11.108. send <call> [<call> ...] (0)
3872 send <call> [<call> ...] Send a message to one or more callsigns
3875 11.109. send copy <msgno> <call> (0)
3877 send copy <msgno> <call> Send a copy of a message to someone
3880 11.110. send noprivate <call> (0)
3882 send noprivate <call> Send a message to all stations
3884 All the SEND commands will create a message which will be sent either
3885 toan individual callsign or to one of the 'bulletin' addresses. SEND
3886 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3887 will mark the message as personal and send it to the cluster node
3888 thatthat callsign is connected to. If the <call> you have specified is
3889 in facta known bulletin category on your node (eg: ALL) then the
3890 message shouldautomatically become a bulletin.You can have more than
3891 one callsign in all of the SEND commands.You can have multiple
3892 qualifiers so that you can have for example:-
3895 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3899 which should send a copy of message 123 to G1TLH and G0RDI and you
3900 willreceive a read receipt when they have read the message.SB is an
3901 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3902 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3903 tionally this should be no longer than 29 characters for compatibil-
3904 ity. Most modern clustersoftware should accept more.You will now be
3905 prompted to start entering your text. You finish the message by enter-
3906 ing '/EX' on a new line. For instance:
3909 ... bye then Jim 73 Dirk /ex
3913 If you have started a message and you don't want to keep it then you-
3914 can abandon the message with '/ABORT' on a new line, like:-
3917 line 1 line 2 oh I just can't be bothered with this /abort
3921 If you abort the message it will NOT be sent.When you are entering the
3922 text of your message, most normal output (suchas DX announcements and
3923 so on are suppressed and stored for latter display(upto 20 such lines
3924 are stored, as new ones come along, so the oldestlines are
3925 dropped).Also, you can enter normal commands commands (and get the
3926 output immediately) whilst in the middle of a message. You do this by
3927 typingthe command preceeded by a '/' character on a new line, so:-
3930 /dx g1tlh 144010 strong signal
3934 Will issue a dx annoucement to the rest of the cluster. Also, you can
3935 add the output of a command to your message by preceeding the command
3943 This will show YOU the output from SH/VHFTABLE and also store it in
3944 themessage. You can carry on with the message until you are ready to
3947 11.111. send private <call> (0)
3949 send private <call> Send a personal message
3952 11.112. send rr <call> (0)
3954 send rr <call> Send a message and ask for a read receipt
3957 11.113. set/address <your address> (0)
3959 set/address <your address> Record your postal address
3962 11.114. set/announce (0)
3964 set/announce Allow announce messages to come out on your terminal
3967 11.115. set/anntalk (0)
3969 set/anntalk Allow talk like announce messages on your terminal
3972 11.116. set/arcluster <call> [<call>..] (5)
3974 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
3977 11.117. set/baddx <call>.. (8)
3979 set/baddx <call>.. Stop callsigns in a dx spot being propagated
3982 11.118. set/badnode <call>.. (8)
3984 set/badnode <call>.. Stop spots from this node being propagated
3988 11.119. set/badspotter <call>.. (8)
3990 set/badspotter <call>.. Stop spots from this callsign being propagated
3993 11.120. set/badword <word>.. (8)
3995 set/badword <word>.. Stop things with this word being propagated
3998 11.121. set/bbs <call> [<call>..] (5)
4000 set/bbs <call> [<call>..] Make the callsign a BBS
4003 11.122. set/beep (0)
4005 set/beep Add a beep to DX and other messages on your terminal
4008 11.123. set/clx <call> [<call>..] (5)
4010 set/clx <call> [<call>..] Make the callsign an CLX node
4013 11.124. set/debug <name> (9)
4015 set/debug <name> Add a debug level to the debug set
4020 set/dx Allow DX messages to come out on your terminal
4023 11.126. set/dxcq (0)
4025 set/dxcq Show CQ Zones on the end of DX announcements
4028 11.127. set/dxgrid (0)
4030 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
4033 11.128. set/dxitu (0)
4035 set/dxitu Show ITU Zones on the end of DX announcements
4038 11.129. set/dxnet <call> [<call>..] (5)
4040 set/dxnet <call> [<call>..] Make the callsign an DXNet node
4043 11.130. set/echo (0)
4045 set/echo Make the cluster echo your input
4048 11.131. set/email <email> ... (0)
4050 set/email <email> ... Set email address(es) and forward your personals
4054 11.132. set/here (0)
4056 set/here Tell the system you are present at your terminal
4059 11.133. set/homenode <node> (0)
4061 set/homenode <node> Set your normal cluster callsign
4063 Tell the cluster system where you normally connect to. Any Messages
4064 sentto you will normally find their way there should you not be
4072 11.134. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
4074 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
4077 11.135. set/isolate (9)
4079 set/isolate Isolate a node from the rest of the network
4081 Connect a node to your system in such a way that you are a full
4082 protocolmember of its network and can see all spots on it, but nothing
4083 either leaksout from it nor goes back into from the rest of the nodes
4084 connected to you.You can potentially connect several nodes in this
4087 11.136. set/language <lang> (0)
4089 set/language <lang> Set the language you want to use
4091 You can select the language that you want the cluster to use.
4092 Currentlythe languages available are en (English), de (German), es
4093 (Spanish) and nl (Dutch).
4095 11.137. set/location <lat & long> (0)
4097 set/location <lat & long> Set your latitude and longitude
4100 11.138. set/lockout <call> (9)
4102 set/lockout <call> Stop a callsign connecting to the cluster
4105 11.139. set/logininfo (0)
4107 set/logininfo Inform when a station logs in locally
4110 11.140. set/name <your name> (0)
4112 set/name <your name> Set your name
4114 Tell the system what your name is eg:-
4119 11.141. set/node <call> [<call>..] (5)
4121 set/node <call> [<call>..] Make the callsign an AK1A cluster
4123 Tell the system that the call(s) are to be treated as AK1A cluster
4124 andfed PC Protocol rather normal user commands.
4126 11.142. set/obscount <count> <call> (8)
4128 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
4130 From 1.35 onwards neighbouring nodes are pinged at regular intervals
4131 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
4132 'pump-up'counter which is decremented on every outgoing ping and then
4133 reset tothe 'obscount' value on every incoming ping. The default value
4134 of thisparameter is 2. What this means is that a neighbouring node
4135 will be pinged twice at (default) 300 second intervals and if no reply
4136 has been heard just beforewhat would be the third attempt, that node
4137 is disconnected.If a ping is heard then the obscount is reset to the
4138 full value. Usingdefault values, if a node has not responded to a ping
4139 within 15 minutes,it is disconnected.You can set this parameter
4140 between 1 and 9.It is STRONGLY recommended that you don't change the
4143 11.143. set/page <lines per page> (0)
4145 set/page <lines per page> Set the lines per page
4147 Tell the system how many lines you wish on a page when the number of
4148 lineof output from a command is more than this. The default is 20.
4149 Setting itexplicitly to 0 will disable paging.
4152 SET/PAGE 30 SET/PAGE 0
4156 The setting is stored in your user profile.
4158 11.144. set/password (0)
4160 set/password Set your own password
4162 This command only works for a 'telnet' user (currently). It willonly
4163 work if you have a password already set. This initial passwordcan only
4164 be set by the sysop.When you execute this command it will ask you for
4165 your old password,then ask you to type in your new password twice (to
4166 make sure youget it right). You may or may not see the data echoed on
4167 the screenas you type, depending on the type of telnet client you
4170 11.145. set/password <callsign> <string> (9)
4172 set/password <callsign> <string> Set a users password
4174 The password for a user can only be set by a full sysop. The stringcan
4175 contain any characters. The way this field is used depends on context.
4176 If it is being used inthe SYSOP command context then you are offered 5
4177 random numbers and youhave to supply the corresponding letters. This
4178 is now mainly for ax25connections.If it is being used on incoming
4179 telnet connections then, if a passwordis set or the:
4182 set/var $main::passwdreq = 1
4185 command is executed in the startup script, then a password prompt
4186 isgiven after the normal 'login: ' prompt.
4188 11.146. set/pinginterval <time> <nodecall> (9)
4190 set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes
4192 As from release 1.35 all neighbouring nodes are pinged at regular
4193 intervalsin order to determine the rolling quality of the link and, in
4194 future, toaffect routing decisions. The default interval is 300 secs
4195 or 5 minutes.You can use this command to set a different interval.
4196 Please don't. But if you do the value you enter is treated as minutes
4197 up 30 and secondsfor numbers greater than that.This is used also to
4198 help determine when a link is down at the far end(as certain cluster
4199 software doesn't always notice), see SET/OBSCOUNTfor more
4200 information.If you must change it (and it may be useful for internet
4201 connected nodeson dynamic IP addresses that go away after a set time
4202 of usage) the timecan be specified as:-
4205 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
4209 Please be aware that this causes traffic to occur on the link, setting
4210 this value too low may annoy your neighbours beyond the point of
4211 endurance!You can switch this off by setting it to 0.
4213 11.147. set/privilege <n> <call> [<call..] (9)
4215 set/privilege <n> <call> [<call..] Set privilege level on a call
4217 Set the privilege level on a callsign. The privilege levels that
4218 pertainto commands are as default:-
4221 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.
4225 If you are a sysop and you come in as a normal user on a remote con-
4226 nectionyour privilege will automatically be set to 0.
4228 11.148. set/prompt <string> (0)
4230 set/prompt <string> Set your prompt to <string>
4233 11.149. set/qra <locator> (0)
4235 set/qra <locator> Set your QRA Grid locator
4237 Tell the system what your QRA (or Maidenhead) locator is. If you have
4238 notdone a SET/LOCATION then your latitude and longitude will be set
4239 roughlycorrectly (assuming your locator is correct ;-). For example:-
4246 11.150. set/qth <your qth> (0)
4248 set/qth <your qth> Set your QTH
4250 Tell the system where you are. For example:-
4253 SET/QTH East Dereham, Norfolk
4257 11.151. set/register <call> ... (9)
4259 set/register <call> ... Mark a user as registered
4262 11.152. set/spider <call> [<call>..] (5)
4264 set/spider <call> [<call>..] Make the callsign an DXSpider node
4266 Tell the system that the call(s) are to be treated as DXSpider node
4267 andfed new style DX Protocol rather normal user commands.
4269 11.153. set/sys_location <lat & long> (9)
4271 set/sys_location <lat & long> Set your cluster latitude and longitude
4273 In order to get accurate headings and such like you must tell the
4274 systemwhat your latitude and longitude is. If you have not yet done a
4275 SET/QRAthen this command will set your QRA locator for you. For
4279 SET/LOCATION 52 22 N 0 57 E
4283 11.154. set/sys_qra <locator> (9)
4285 set/sys_qra <locator> Set your cluster QRA Grid locator
4288 11.155. set/talk (0)
4290 set/talk Allow TALK messages to come out on your terminal
4293 11.156. set/usdb <call> <state> <city> (9)
4295 set/usdb <call> <state> <city> add/update a US DB callsign
4297 This command allows you to add or alter a callsign in the US
4298 statedatabase. Use with extreme caution. Anything you do here will
4299 beoverwritten by any weekly updates that affect this callsign
4302 set/usdb g1tlh nh downtown rindge
4306 see also DELETE/USDB
4308 11.157. set/usstate (0)
4310 set/usstate Allow US State info on the end of DX announcements
4316 set/wcy Allow WCY messages to come out on your terminal
4321 set/wwv Allow WWV messages to come out on your terminal
4326 set/wx Allow WX messages to come out on your terminal
4329 11.161. show/baddx (1)
4331 show/baddx Show all the bad dx calls in the system
4333 Display all the bad dx callsigns in the system, see SET/BADDXfor more
4336 11.162. show/badnode (1)
4338 show/badnode Show all the bad nodes in the system
4340 Display all the bad node callsigns in the system, see SET/BADNODEfor
4343 11.163. show/badspotter (1)
4345 show/badspotter Show all the bad spotters in the system
4347 Display all the bad spotter's callsigns in the system, see
4348 SET/BADSPOTTERfor more information.
4350 11.164. show/badword (1)
4352 show/badword Show all the bad words in the system
4354 Display all the bad words in the system, see SET/BADWORDfor more
4357 11.165. show/configuration [<node>] (0)
4359 show/configuration [<node>] Show all the nodes and users visible
4361 This command allows you to see all the users that can be seenand the
4362 nodes to which they are connected.This command is normally abbreviated
4363 to: sh/cNormally, the list returned will be just for the nodes from
4364 your country (because the list otherwise will be very long).
4371 will produce a complete list of all nodes. BE WARNED: the list that is
4372 returned can be VERY longIt is possible to supply a node or part of a
4373 prefix and you will get a list of the users for that node or list of
4374 nodes starting withthat prefix.
4384 11.166. show/configuration/node (0)
4386 show/configuration/node Show all the nodes connected locally
4388 Show all the nodes connected to this node.
4390 11.167. show/connect (1)
4392 show/connect Show all the active connections
4394 This command shows information on all the active connections known
4395 tothe node. This command gives slightly more information than WHO.
4397 11.168. show/contest <year and month> (0)
4399 show/contest <year and month> Show all the contests for a month
4401 Show all known contests which are maintained at
4402 http://www.sk3bg.se/contest/for a particular month or year. The format
4403 is reasonably flexible.For example:-
4406 SH/CONTEST sep2003 SH/CONTEST 03 march
4410 11.169. show/date [<prefix>|<callsign>] (0)
4412 show/date [<prefix>|<callsign>] Show the local time
4414 This is very nearly the same as SHOW/TIME, the only difference the
4415 formatof the date string if no arguments are given.If no prefixes or
4416 callsigns are given then this command returns the localtime and UTC as
4417 the computer has it right now. If you give some prefixesthen it will
4418 show UTC and UTC + the local offset (not including DST) atthe prefixes
4419 or callsigns that you specify.
4421 11.170. show/db0sdx <callsign> (0)
4423 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
4425 This command queries the DB0SDX QSL server on the internetand returns
4426 any information available for that callsign. This serviceis provided
4427 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
4430 11.171. show/debug (9)
4432 show/debug Show what levels of debug information you are logging
4437 show/dx Interrogate the spot database
4439 If you just type SHOW/DX you will get the last so many spots(sysop
4440 configurable, but usually 10).In addition you can add any number of
4441 these commands in very nearlyany order to the basic SHOW/DX command,
4444 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>
4448 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
4452 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
4456 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
4460 info <text> - any spots containing <text> in the info or remarks
4464 by <call> - any spots spotted by <call> (spotter <call> is the same).
4468 qsl - this automatically looks for any qsl info on the call held in the spot database.
4472 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.
4476 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
4480 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
4484 You can also use this with the 'by' keyword so eg by W dxcc
4492 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
4496 11.173. show/dxcc <prefix> (0)
4498 show/dxcc <prefix> Interrogate the spot database by country
4500 This command takes the <prefix> (which can be a full or partial
4501 callsign if desired), looks up which internal country number it isand
4502 then displays all the spots as per SH/DX for that country.This is now
4503 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
4507 SH/DXCC G SH/DXCC W on 20m iota
4511 This can be done with the SHOW/DX command like this:-
4514 SH/DX dxcc g SH/DX dxcc w on 20m iota
4518 11.174. show/dxqsl <callsign> (0)
4520 show/dxqsl <callsign> Show any QSL info gathered from spots
4522 The node collects information from the comment fields in spots
4523 (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a
4524 database.This command allows you to interrogate that database and if
4525 the callsignis found will display the manager(s) that people have
4526 spotted. This information is NOT reliable, but it is normally
4527 reasonably accurate ifit is spotted enough times.For example:-
4534 You can check the raw input spots yourself with:-
4541 This gives you more background information.
4543 11.175. show/dxstats [days] [date] (0)
4545 show/dxstats [days] [date] Show the DX Statistics
4547 Show the total DX spots for the last <days> no of days (default is
4548 31), starting from a <date> (default: today).
4550 11.176. show/files [<filearea> [<string>]] (0)
4552 show/files [<filearea> [<string>]] List the contents of a filearea
4554 SHOW/FILES on its own will show you a list of the various
4555 fileareasavailable on the system. To see the contents of a particular
4563 where <filearea> is the name of the filearea you want to see the con-
4564 tents of.You can also use shell globbing characters like '*' and '?'
4565 in astring to see a selection of files in a filearea eg:-
4568 SH/FILES bulletins arld*
4572 See also TYPE - to see the contents of a file.
4574 11.177. show/filter (0)
4576 show/filter Show the contents of all the filters you have set
4578 Show the contents of all the filters that are set. This command
4579 displaysall the filters set - for all the various categories.
4581 11.178. show/hfstats [days] [date] (0)
4583 show/hfstats [days] [date] Show the HF DX Statistics
4585 Show the HF DX spots breakdown by band for the last <days> no of days
4586 (default is 31), starting from a <date> (default: today).
4588 11.179. show/hftable [days] [date] [prefix ...] (0)
4590 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4592 Show the HF DX Spotter table for the list of prefixes for the last
4593 <days> no of days (default is 31), starting from a <date> (default:
4594 today).If there are no prefixes then it will show the table for your
4595 country.Remember that some countries have more than one "DXCC country"
4596 in them(eg G :-), to show them (assuming you are not in G already
4597 which isspecially treated in the code) you must list all the relevant
4601 sh/hftable g gm gd gi gj gw gu
4605 Note that the prefixes are converted into country codes so you don't
4606 haveto list all possible prefixes for each country.If you want more or
4607 less days than the default simply include thenumber you require:-
4614 If you want to start at a different day, simply add the date in some
4616 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4620 This will show the stats for your DXCC for that CQWW contest weekend.
4621 You can specify either prefixes or full callsigns (so you can see how
4622 youdid against all your mates). You can also say 'all' which will then
4623 printthe worldwide statistics.
4630 11.180. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4632 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4635 This command shows the hop counts set up for a node. You can
4636 specifywhich category you want to see. If you leave the category out
4637 then all the categories will be listed.
4639 11.181. show/isolate (1)
4641 show/isolate Show list of ISOLATED nodes
4644 11.182. show/lockout <prefix>|all (9)
4646 show/lockout <prefix>|all Show the list of locked out or excluded
4650 11.183. show/log [<callsign>] (8)
4652 show/log [<callsign>] Show excerpts from the system log
4654 This command outputs a short section of the system log. On its ownit
4655 will output a general logfile. With the optional callsign it willshow
4656 output from the log associated with that callsign.
4658 11.184. show/moon [ndays] [<prefix>|<callsign>] (0)
4660 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4662 Show the Moon rise and set times for a (list of) prefixes or
4663 callsigns, together with the azimuth and elevation of the sun
4664 currently at thoselocations.If you don't specify any prefixes or
4665 callsigns, it will show the times foryour QTH (assuming you have set
4666 it with either SET/LOCATION or SET/QRA),together with the current
4667 azimuth and elevation.In addition, it will show the illuminated
4668 fraction of the moons disk.If all else fails it will show the Moonrise
4669 and set times for the nodethat you are connected to. For example:-
4672 SH/MOON SH/MOON G1TLH W5UN
4676 You can also use this command to see into the past or the future, soif
4677 you want to see yesterday's times then do:-
4685 or in three days time:-
4692 Upto 366 days can be checked both in the past and in the future.Please
4693 note that the rise and set times are given as the UT times of rise and
4694 set on the requested UT day.
4696 11.185. show/muf <prefix> [<hours>][long] (0)
4698 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4701 This command allow you to estimate the likelihood of you contactinga
4702 station with the prefix you have specified. The output assumes a
4703 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4704 0.15muV/10dB SINAD)The result predicts the most likely operating
4705 frequencies and signallevels for high frequency (shortwave) radio
4706 propagation paths onspecified days of the year and hours of the day.
4707 It is most useful forpaths between 250 km and 6000 km, but can be used
4708 with reduced accuracyfor paths shorter or longer than this.The command
4709 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4710 predict the MUF given the predicted flux, day of the year,hour of the
4711 day and geographic coordinates of the transmitter andreceiver. This
4712 routine is reasonably accurate for the purposes here,with a claimed
4713 RMS error of 3.8 MHz, but much smaller and less complexthan the
4714 programs used by major shortwave broadcasting organizations,such as
4715 the Voice of America.The command will display some header information
4716 detailing itsassumptions, together with the locations, latitude and
4717 longitudes andbearings. It will then show UTC (UT), local time at the
4718 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4719 the path(Zen) and the likely signal strengths. Then for each frequency
4720 for whichthe system thinks there is a likelihood of a circuit it
4721 prints a value.The value is currently a likely S meter reading based
4722 on the conventional6dB / S point scale. If the value has a '+'
4723 appended it means that it is1/2 an S point stronger. If the value is
4724 preceeded by an 'm' it means thatthere is likely to be much fading and
4725 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4726 will show the next two hours worth of data. Youcan specify anything up
4727 to 24 hours worth of data by appending the no ofhours required after
4728 the prefix. For example:-
4738 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
4742 indicating that you will have weak, fading circuits on top band and
4743 80m but usable signals on 40m (about S3).inputing:-
4751 will get you the above display, but with the next 24 hours worth
4755 SH/MUF W L 24 SH/MUF W 24 Long
4759 Gives you an estimate of the long path propagation characterics.
4760 Itshould be noted that the figures will probably not be very useful,
4761 norterrible accurate, but it is included for completeness.
4763 11.186. show/newconfiguration [<node>] (0)
4765 show/newconfiguration [<node>] Show all the nodes and users visible
4767 This command allows you to see all the users that can be seenand the
4768 nodes to which they are connected. This command produces essentially
4769 the same information as SHOW/CONFIGURATION except that it shows all
4770 the duplication ofany routes that might be present It also uses a
4771 different formatwhich may not take up quite as much space if you don't
4772 have anyloops.BE WARNED: the list that is returned can be VERY long
4774 11.187. show/newconfiguration/node (0)
4776 show/newconfiguration/node Show all the nodes connected locally
4778 Show all the nodes connected to this node in the new format.
4780 11.188. show/node [<callsign> ...] (1)
4782 show/node [<callsign> ...] Show the type and version number of nodes
4784 Show the type and version (if connected) of the nodes specified on
4785 thecommand line. If no callsigns are specified then a sorted list of
4786 allthe non-user callsigns known to the system will be displayed.
4788 11.189. show/prefix <callsign> (0)
4790 show/prefix <callsign> Interrogate the prefix database
4792 This command takes the <callsign> (which can be a full or partial
4793 callsign or a prefix), looks up which internal country number it is
4794 and then displays all the relevant prefixes for that countrytogether
4795 with the internal country no, the CQ and ITU regions. See also
4798 11.190. show/program (5)
4800 show/program Show the locations of all the included program modules
4802 Show the name and location where every program module was load from.
4803 Thisis useful for checking where you think you have loaded a .pm file
4806 11.191. show/qra <lat> <long> (0)
4808 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4810 This is a multipurpose command that allows you either to calculate
4811 thedistance and bearing between two locators or (if only one locator
4812 isgiven on the command line) the distance and beraing from your
4813 stationto the locator. For example:-
4816 SH/QRA IO92QL SH/QRA JN06 IN73
4820 The first example will show the distance and bearing to the locator
4821 fromyourself, the second example will calculate the distance and bear-
4822 ing fromthe first locator to the second. You can use 4 or 6 character
4823 locators.It is also possible to convert a latitude and longitude to a
4824 locator by using this command with a latitude and longitude as an
4825 argument, forexample:-
4828 SH/QRA 52 41 N 0 58 E
4832 11.192. show/qra <locator> [<locator>] (0)
4834 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4837 11.193. show/qrz <callsign> (0)
4839 show/qrz <callsign> Show any callbook details on a callsign
4841 This command queries the QRZ callbook server on the internetand
4842 returns any information available for that callsign. This serviceis
4843 provided for users of this software by http://www.qrz.com See also
4844 SHOW/WM7D for an alternative.
4846 11.194. show/registered [<prefix>] (9)
4848 show/registered [<prefix>] Show the registered users
4851 11.195. show/route <callsign> ... (0)
4853 show/route <callsign> ... Show the route to the callsign
4855 This command allows you to see to which node the callsigns specified
4856 areconnected. It is a sort of inverse sh/config.
4863 11.196. show/satellite <name> [<hours> <interval>] (0)
4865 show/satellite <name> [<hours> <interval>] Show tracking data
4867 Show the tracking data from your location to the satellite of your
4868 choicefrom now on for the next few hours.If you use this command
4869 without a satellite name it will display a listof all the satellites
4870 known currently to the system. If you give a name then you can obtain
4871 tracking data of all the passesthat start and finish 5 degrees below
4872 the horizon. As default it willgive information for the next three
4873 hours for every five minute period.You can alter the number of hours
4874 and the step size, within certain limits. Each pass in a period is
4875 separated with a row of '-----' charactersSo for example:-
4877 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4881 11.197. show/station all [<regex>] (6)
4883 show/station all [<regex>] Show list of users in the system
4886 11.198. show/station [<callsign> ..] (0)
4888 show/station [<callsign> ..] Show information about a callsign
4890 Show the information known about a callsign and whether (and
4891 where)that callsign is connected to the cluster.
4898 If no callsign is given then show the information for yourself.
4900 11.199. show/sun [ndays] [<prefix>|<callsign>] (0)
4902 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
4904 Show the sun rise and set times for a (list of) prefixes or callsigns,
4905 together with the azimuth and elevation of the sun currently at
4906 thoselocations.If you don't specify any prefixes or callsigns, it will
4907 show the times foryour QTH (assuming you have set it with either
4908 SET/LOCATION or SET/QRA),together with the current azimuth and
4909 elevation.If all else fails it will show the sunrise and set times for
4910 the nodethat you are connected to. For example:-
4913 SH/SUN SH/SUN G1TLH K9CW ZS
4917 You can also use this command to see into the past or the future, soif
4918 you want to see yesterday's times then do:-
4925 or in three days time:-
4932 Upto 366 days can be checked both in the past and in the future.Please
4933 note that the rise and set times are given as the UT times of rise and
4934 set on the requested UT day.
4936 11.200. show/time [<prefix>|<callsign>] (0)
4938 show/time [<prefix>|<callsign>] Show the local time
4940 If no prefixes or callsigns are given then this command returns the
4941 localtime and UTC as the computer has it right now. If you give some
4942 prefixesthen it will show UTC and UTC + the local offset (not
4943 including DST) atthe prefixes or callsigns that you specify.
4945 11.201. show/usdb [call ..] (0)
4947 show/usdb [call ..] Show information held on the FCC Call database
4949 Show the City and State of a Callsign held on the FCC database ifhis
4950 is being run on this system, eg:-
4957 11.202. show/vhfstats [days] [date] (0)
4959 show/vhfstats [days] [date] Show the VHF DX Statistics
4961 Show the VHF DX spots breakdown by band for the last <days> no of days
4962 (default is 31), starting from a date (default: today).
4964 11.203. show/vhftable [days] [date] [prefix ...] (0)
4966 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
4968 Show the VHF DX Spotter table for the list of prefixes for the last
4969 <days> no of days (default is 31), starting from a date (default:
4970 today).If there are no prefixes then it will show the table for your
4971 country.Remember that some countries have more than one "DXCC country"
4972 in them(eg G :-), to show them (assuming you are not in G already
4973 which isspecially treated in the code) you must list all the relevant
4977 sh/vhftable g gm gd gi gj gw gu
4981 Note that the prefixes are converted into country codes so you don't
4982 haveto list all possible prefixes for each country.If you want more or
4983 less days than the default simply include thenumber you require:-
4990 If you want to start at a different day, simply add the date in some
4994 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
4998 This will show the stats for your DXCC for that CQWW contest weekend.
4999 You can specify either prefixes or full callsigns (so you can see how
5000 youdid against all your mates). You can also say 'all' which will then
5001 printthe worldwide statistics.
5007 11.204. show/wcy (0)
5009 show/wcy Show last 10 WCY broadcasts
5012 11.205. show/wcy <n> (0)
5014 show/wcy <n> Show last <n> WCY broadcasts
5016 Display the most recent WCY information that has been received by the
5019 11.206. show/wm7d <callsign> (0)
5021 show/wm7d <callsign> Show callbook details on a US callsigns
5023 This command queries the WM7D callbook server on the internetand
5024 returns any information available for that US callsign. This serviceis
5025 provided for users of this software by http://www.wm7d.net.See also
5028 11.207. show/wwv (0)
5030 show/wwv Show last 10 WWV broadcasts
5033 11.208. show/wwv <n> (0)
5035 show/wwv <n> Show last <n> WWV broadcasts
5037 Display the most recent WWV information that has been received by the
5040 11.209. shutdown (5)
5042 shutdown Shutdown the cluster
5044 Shutdown the cluster and disconnect all the users
5046 11.210. spoof <call> <command> (9)
5048 spoof <call> <command> Do a command as though you are another user
5050 This command is provided so that sysops can set a user's parameters
5051 withoutme having to write a special 'sysop' version for every user
5052 command. Itallows you to pretend that you are doing the command as the
5053 user you specify.eg:-
5056 SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
5060 11.211. stat/channel [<callsign>] (5)
5062 stat/channel [<callsign>] Show the status of a channel on the cluster
5064 Show the internal status of the channel object either for the channel
5065 that you are on or else for the callsign that you asked for.Only the
5066 fields that are defined (in perl term) will be displayed.
5068 11.212. stat/db <dbname> (5)
5070 stat/db <dbname> Show the status of a database
5072 Show the internal status of a database descriptor.Depending on your
5073 privilege level you will see more or less information. This command is
5074 unlikely to be of much use to anyone other than a sysop.
5076 11.213. stat/msg (1)
5078 stat/msg Show the status of the message system
5081 11.214. stat/msg <msgno> (1)
5083 stat/msg <msgno> Show the status of a message
5085 This command shows the internal status of a message and includes
5086 informationsuch as to whom it has been forwarded, its size, origin etc
5087 etc.If no message number is given then the status of the message
5088 system is displayed.
5090 11.215. stat/route_node <callsign> (5)
5092 stat/route_node <callsign> Show the data in a Route::Node object
5095 11.216. stat/route_node all (5)
5097 stat/route_node all Show list of all Route::Node objects
5100 11.217. stat/route_user <callsign> (5)
5102 stat/route_user <callsign> Show the data in a Route::User object
5105 11.218. stat/route_user all (5)
5107 stat/route_user all Show list of all Route::User objects
5110 11.219. stat/user [<callsign>] (5)
5112 stat/user [<callsign>] Show the full status of a user
5114 Shows the full contents of a user record including all the secret
5115 flagsand stuff.Only the fields that are defined (in perl term) will be
5120 sysop Regain your privileges if you login remotely
5122 The system automatically reduces your privilege level to that of
5123 anormal user if you login in remotely. This command allows you
5124 toregain your normal privilege level. It uses the normal system:
5125 fivenumbers are returned that are indexes into the character array
5126 that isyour assigned password (see SET/PASSWORD). The indexes start
5127 fromzero.You are expected to return a string which contains the
5128 charactersrequired in the correct order. You may intersperse those
5129 characterswith others to obscure your reply for any watchers. For
5130 example (andthese values are for explanation :-):
5133 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
5140 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
5144 They will all match. If there is no password you will still be
5145 offerednumbers but nothing will happen when you input a string. Any
5146 match iscase sensitive.
5148 11.221. talk <call> > <node> [<text>] (0)
5150 talk <call> > <node> [<text>] Send a text message to another station
5153 Send a short message to any other station that is visible on the
5154 clustersystem. You can send it to anyone you can see with a
5155 SHOW/CONFIGURATION command, they don't have to be connected
5156 locally.The second form of TALK is used when other cluster nodes are
5157 connectedwith restricted information. This usually means that they
5158 don't send the user information usually associated with logging on and
5159 off the cluster.If you know that G3JNB is likely to be present on
5160 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
5161 then you would use thesecond form of the talk message.If you want to
5162 have a ragchew with someone you can leave the text messageout and the
5163 system will go into 'Talk' mode. What this means is that ashort
5164 message is sent to the recipient telling them that you are in
5165 a'Talking' frame of mind and then you just type - everything you send
5166 willgo to the station that you asked for. All the usual announcements,
5167 spots and so on will still come out on yourterminal.If you want to do
5168 something (such as send a spot) you preceed the normal command with a
5172 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
5176 To leave talk mode type:
5183 If you are in 'Talk' mode, there is an extention to the '/' command
5184 whichallows you to send the output to all the people you are talking
5185 to. You do with the '//' command. For example:-
5192 will send the hftable as you have it to all the people you are cur-
5195 11.222. talk <call> [<text>] (0)
5197 talk <call> [<text>] Send a text message to another station
5201 11.223. type <filearea>/<name> (0)
5203 type <filearea>/<name> Look at the contents of a file in one of the
5206 Type out the contents of a file in a filearea. So, for example, in
5207 filearea 'bulletins' you want to look at file 'arld051' you would
5211 TYPE bulletins/arld051
5215 See also SHOW/FILES to see what fileareas are available and a list of
5218 11.224. uncatchup <node call> all|[msgno> ...] (5)
5220 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
5222 When you send messages the fact that you have forwarded it to another
5223 node is remembered so that it isn't sent again. When you have a new
5224 partnernode and you add their callsign to your /spider/msg/forward.pl
5225 file, alloutstanding non-private messages will be forwarded to them.
5226 This may wellbe ALL the non-private messages. You can prevent this by
5227 using these commmands:-
5230 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
5234 and to undo what you have just done:-
5237 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
5241 which will arrange for them to be forward candidates again.Order is
5244 11.225. unset/announce (0)
5246 unset/announce Stop announce messages coming out on your terminal
5249 11.226. unset/anntalk (0)
5251 unset/anntalk Stop talk like announce messages on your terminal
5253 The announce system on legacy cluster nodes is used as a talk
5254 substitute because the network is so poorly connected. If you:
5261 you will suppress several of these announces, you may miss the odd
5262 useful one as well, but you would probably miss them anyway in thewel-
5263 ter of useless ones.
5271 allows you to see them again. This is the default.
5273 11.227. unset/baddx <call>.. (8)
5275 unset/baddx <call>.. Propagate a dx spot with this callsign again
5277 Setting a word as 'baddx' will prevent spots with that word in
5278 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
5279 anyfurther. They will not be displayed and they will not be sent
5280 ontoother nodes.The word must be written in full, no wild cards are
5284 set/baddx FORSALE VIDEO FR0G
5288 To allow a word again, use the following command ...
5295 11.228. unset/badnode <call>.. (8)
5297 unset/badnode <call>.. Allow spots from this node again
5299 Setting a callsign as a 'badnode' will prevent spots from that node
5300 going any further. They will not be displayed and they will not be
5301 sent onto other nodes.The call must be a full eg:-
5308 will stop anything from K1TTT. If you want SSIDs as well then you mus-
5309 tenter them specifically.
5316 will allow spots from him again.Use with extreme care. This command
5317 may well be superceeded by FILTERing.
5319 11.229. unset/badspotter <call>.. (8)
5321 unset/badspotter <call>.. Allow spots from this callsign again
5323 Setting a callsign as a 'badspotter' will prevent spots from this
5324 callsign going any further. They will not be displayed and they will
5325 not be sent onto other nodes.The call must be written in full, no wild
5326 cards are allowed eg:-
5329 set/badspotter VE2STN
5332 will stop anything from VE2STN. This command will automaticallystop
5333 spots from this user, regardless of whether or which SSID he uses. DO
5334 NOT USE SSIDs in the callsign, just use the callsignas above or below.
5337 unset/badspotter VE2STN
5341 will allow spots from him again.Use with extreme care. This command
5342 may well be superceded by FILTERing.
5344 11.230. unset/badword <word>.. (8)
5346 unset/badword <word>.. Propagate things with this word again
5348 Setting a word as a 'badword' will prevent things like spots,announces
5349 or talks with this word in the the text part from going anyfurther.
5350 They will not be displayed and they will not be sent ontoother
5351 nodes.The word must be written in full, no wild cards are allowed eg:-
5354 set/badword annihilate annihilated annihilation
5358 will stop anything with these words in the text.
5361 unset/badword annihilated
5365 will allow text with this word again.
5367 11.231. unset/beep (0)
5369 unset/beep Stop beeps for DX and other messages on your terminal
5372 11.232. unset/debug <name> (9)
5374 unset/debug <name> Remove a debug level from the debug set
5376 You can choose to log several different levels. The levels are
5379 chan state msg cron connect
5383 You can show what levels you are logging with SHOW/DEBUG
5385 11.233. unset/dx (0)
5387 unset/dx Stop DX messages coming out on your terminal
5390 11.234. unset/dxcq (0)
5392 unset/dxcq Stop CQ Zones on the end of DX announcements
5394 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
5395 announcement (there is just enough room). Some user programscannot
5396 cope with this. The Spotter's CQ is on the RHS of the time, the
5397 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
5398 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5401 11.235. unset/dxgrid (0)
5403 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
5405 A standard feature which is enabled in version 1.43 and above is that
5406 if the spotter's grid square is known it is output on the endof a DX
5407 announcement (there is just enough room). Some user programscannot
5408 cope with this. You can use this command to reset (or set)this
5409 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
5410 flags you have set if you are confused.
5412 11.236. unset/dxitu (0)
5414 unset/dxitu Stop ITU Zones on the end of DX announcements
5416 Display both the Spotter's and the Spotted's ITU Zone on the endof a
5417 DX announcement (there is just enough room). Some user programscannot
5418 cope with this. The Spotter's ITU is on the RHS of the time, the
5419 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
5420 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5423 11.237. unset/echo (0)
5425 unset/echo Stop the cluster echoing your input
5427 If you are connected via a telnet session, different implimentationsof
5428 telnet handle echo differently depending on whether you are connected
5429 via port 23 or some other port. You can use this commandto change the
5430 setting appropriately. The setting is stored in your user profile.YOU
5431 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
5433 11.238. unset/email (0)
5435 unset/email Stop personal msgs being forwarded by email
5437 If any personal messages come in for your callsign then you can
5438 usethese commands to control whether they are forwarded onto your
5439 emailaddress. To enable the forwarding do something like:-
5442 SET/EMAIL mike.tubby@somewhere.com
5446 You can have more than one email address (each one separated by a
5447 space).Emails are forwarded to all the email addresses you specify.You
5448 can disable forwarding by:-
5455 11.239. unset/here (0)
5457 unset/here Tell the system you are absent from your terminal
5461 11.240. unset/hops <call> ann|spots|route|wwv|wcy (8)
5463 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
5465 Set the hop count for a particular type of broadcast for a node.This
5466 command allows you to set up special hop counts for a node for
5467 currently: announce, spots, wwv and wcy broadcasts.eg:
5470 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
5474 Set SHOW/HOPS for information on what is already set. This commandcre-
5475 ates a filter and works in conjunction with the filter system. You can
5476 unset the hops with command UNSET/HOPS. For example:-
5479 unset/hops gb7djk ann unset/hops gb7mbc spots
5483 11.241. unset/isolate (9)
5485 unset/isolate Stop Isolation of a node from the rest of the network
5487 Remove isolation from a node - SET/ISOLATE
5489 11.242. unset/lockout <call> (9)
5491 unset/lockout <call> Allow a callsign to connect to the cluster
5494 11.243. unset/logininfo (0)
5496 unset/logininfo Inform when a station logs out locally
5499 11.244. unset/password <call> ... (9)
5501 unset/password <call> ... Delete (remove) a user's password
5503 This command allows the sysop to completely delete and remove a
5504 password for a user.
5506 11.245. unset/privilege (0)
5508 unset/privilege Remove any privilege for this session
5510 You can use this command to 'protect' this session from
5511 unauthoriseduse. If you want to get your normal privilege back you
5512 will need toeither logout and login again (if you are on a console) or
5513 use theSYSOP command.
5515 11.246. unset/prompt (0)
5517 unset/prompt Set your prompt back to default
5519 This command will set your user prompt to exactly the string that you
5520 say. The point of this command to enable a user to interface to
5521 programsthat are looking for a specific prompt (or else you just want
5522 a differentfixed prompt).
5530 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
5533 11.247. unset/register <call> ... (9)
5535 unset/register <call> ... Mark a user as not registered
5537 Registration is a concept that you can switch on by executing the
5540 set/var $main::regreq = 1
5544 command (usually in your startup file)If a user is NOT registered
5545 then, firstly, instead of the normalmotd file (/spider/data/motd)
5546 being sent to the user at startup, theuser is sent the motd_nor file
5547 instead. Secondly, the non registereduser only has READ-ONLY access to
5548 the node. The non-registered usercannot use DX, ANN etc. The only
5549 exception to this is that a non-registered user can TALK orSEND mes-
5552 11.248. unset/talk (0)
5554 unset/talk Stop TALK messages coming out on your terminal
5557 11.249. unset/usstate (0)
5559 unset/usstate Stop US State info on the end of DX announcements
5561 If the spotter's or spotted's US State is known it is output on the
5562 end of a DX announcement (there is just enough room). A spotter's
5563 state will appear on the RHS of the time (like SET/DXGRID) and the
5564 spotted's State will appear on the LHS of thetime field. Any
5565 information found will override any locator information from
5566 SET/DXGRID.Some user programs cannot cope with this. You can use this
5567 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
5568 SET/DXITUDo a STAT/USER to see which flags you have set if you are
5571 11.250. unset/wcy (0)
5573 unset/wcy Stop WCY messages coming out on your terminal
5576 11.251. unset/wwv (0)
5578 unset/wwv Stop WWV messages coming out on your terminal
5581 11.252. unset/wx (0)
5583 unset/wx Stop WX messages coming out on your terminal
5588 who Show who is physically connected
5590 This is a quick listing that shows which callsigns are connected
5591 andwhat sort of connection they have
5592 11.254. wx <text> (0)
5594 wx <text> Send a weather message to local users
5597 11.255. wx full <text> (0)
5599 wx full <text> Send a weather message to all cluster users
5602 11.256. wx sysop <text> (5)
5604 wx sysop <text> Send a weather message to other clusters only
5606 Weather messages can sometimes be useful if you are experiencing an
5607 extremethat may indicate enhanced conditions