1 The DXSpider Administration Manual v1.51
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
6 A reference for SysOps of the DXSpider DXCluster program.
7 ______________________________________________________________________
13 1. Routing and Filtering
16 1.3 The node_default filter
17 1.4 General route filtering
18 1.5 General filter rules
22 1.9 Advanced filtering
23 1.10 Basic hop control
24 1.11 Hop Control on Specific Nodes
25 1.12 Isolating networks
26 1.13 A DXSpider Filtering Tutorial
30 2.2 Filtering words from text fields in Announce, Talk and DX spots
31 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
40 3.7 Distribution lists
45 5.1 Creating databases
46 5.2 Importing databases
47 5.3 Checking available databases
48 5.4 Looking up databases
49 5.5 Removing databases
51 6. Information, files and useful programs
55 6.4 Other text messages
58 6.7 Updating kepler data
60 6.9 Connecting logging programs
63 8. Web based statistics
69 10.1 CVS from a Linux platform
70 10.2 CVS from a Windows platform
72 11. The DXSpider Command Reference
74 11.2 accept/announce <call> [input] [0-9] <pattern> (8)
75 11.3 accept/announce [0-9] <pattern> (0)
76 11.4 accept/route <call> [0-9] <pattern> (8)
77 11.5 accept/spots <call> [input] [0-9] <pattern> (8)
78 11.6 accept/spots [0-9] <pattern> (0)
79 11.7 accept/wcy <call> [input] [0-9] <pattern> (8)
80 11.8 accept/wcy [0-9] <pattern> (0)
81 11.9 accept/wwv <call> [input] [0-9] <pattern> (8)
82 11.10 accept/wwv [0-9] <pattern> (0)
83 11.11 announce <text> (0)
84 11.12 announce full <text> (0)
85 11.13 announce sysop <text> (5)
86 11.14 apropos <string> (0)
87 11.15 blank [<string>] [<nn>] (0)
89 11.17 catchup <node call> all|[<msgno> ...] (5)
90 11.18 chat <group> <text> (0)
91 11.19 clear/announce <callsign> [input] [0-9|all] (8)
92 11.20 clear/announce [1|all] (0)
93 11.21 clear/route <callsign> [input] [0-9|all] (8)
94 11.22 clear/route [1|all] (0)
95 11.23 clear/spots <callsign> [input] [0-9|all] (8)
96 11.24 clear/spots [0-9|all] (0)
97 11.25 clear/wcy <callsign> [input] [0-9|all] (8)
98 11.26 clear/wcy [1|all] (0)
99 11.27 clear/wwv <callsign> [input] [0-9|all] (8)
100 11.28 clear/wwv [1|all] (0)
101 11.29 connect <callsign> (5)
103 11.31 dbcreate <name> (9)
104 11.32 dbcreate <name> chain <name> [<name>..] (9)
105 11.33 dbcreate <name> cmd <dxspider command> (9)
106 11.34 dbcreate <name> remote <node> (9)
107 11.35 dbimport <dbname> <filename> (9)
108 11.36 dbremove <dbname> (9)
109 11.37 dbshow <dbname> <key> (0)
111 11.39 delete/usdb <callsign> ... (9)
112 11.40 delete/user <callsign> ... (9)
113 11.41 demonstrate <call> <command> (9)
115 11.43 directory <from>-<to> (0)
116 11.44 directory <nn> (0)
117 11.45 directory all (0)
118 11.46 directory from <call> (0)
119 11.47 directory new (0)
120 11.48 directory own (0)
121 11.49 directory subject <string> (0)
122 11.50 directory to <call> (0)
124 11.52 disconnect <call> [<call> ...] (8)
125 11.53 dx [by <call>] <freq> <call> <remarks> (0)
126 11.54 echo <line> (0)
127 11.55 export <msgno> <filename> (9)
128 11.56 export_users [<filename>] (9)
129 11.57 filtering... (0)
130 11.58 forward/latlong <node_call> (8)
131 11.59 forward/opernam <call> (1)
133 11.61 init <node> (5)
134 11.62 join <group> (0)
136 11.64 kill <from msgno>-<to msgno> (0)
137 11.65 kill <from>-<to> (5)
138 11.66 kill <msgno> [<msgno..] (0)
139 11.67 kill <msgno> [<msgno> ...] (0)
140 11.68 kill expunge <msgno> [<msgno..] (6)
141 11.69 kill from <call> (5)
142 11.70 kill full <msgno> [<msgno..] (5)
143 11.71 kill full <msgno> [<msgno] (5)
144 11.72 kill to <call> (5)
145 11.73 kill from <regex> (0)
146 11.74 kill to <regex> (0)
147 11.75 leave <group> (0)
149 11.77 load/aliases (9)
150 11.78 load/badmsg (9)
151 11.79 load/badwords (9)
153 11.81 load/cmd_cache (9)
154 11.82 load/forward (9)
156 11.84 load/keps [nn] (5)
157 11.85 load/messages (9)
158 11.86 load/prefixes (9)
159 11.87 merge <node> [<no spots>/<no wwv>] (5)
160 11.88 msg <cmd> <msgno> [data ... ] (9)
161 11.89 pc <call> <text> (8)
162 11.90 ping <node call> (1)
163 11.91 rcmd <node call> <cmd> (1)
165 11.93 read <msgno> (0)
168 11.96 reject/announce <call> [input] [0-9] <pattern> (8)
169 11.97 reject/announce [0-9] <pattern> (0)
170 11.98 reject/route <call> [0-9] <pattern> (8)
171 11.99 reject/spots <call> [input] [0-9] <pattern> (8)
172 11.100 reject/spots [0-9] <pattern> (0)
173 11.101 reject/wcy <call> [input] [0-9] <pattern> (8)
174 11.102 reject/wcy [0-9] <pattern> (0)
175 11.103 reject/wwv <call> [input] [0-9] <pattern> (8)
176 11.104 reject/wwv [0-9] <pattern> (0)
178 11.106 reply <msgno> (0)
179 11.107 reply b <msgno> (0)
180 11.108 reply noprivate <msgno> (0)
181 11.109 reply rr <msgno> (0)
182 11.110 save [-d -t -a] <filename> "<cmd>" [...] (9)
183 11.111 send <call> [<call> ...] (0)
184 11.112 send copy <msgno> <call> (0)
185 11.113 send noprivate <call> (0)
186 11.114 send private <call> (0)
187 11.115 send rr <call> (0)
188 11.116 set/address <your address> (0)
189 11.117 set/announce (0)
190 11.118 set/anntalk (0)
191 11.119 set/arcluster <call> [<call>..] (5)
192 11.120 set/baddx <call>.. (8)
193 11.121 set/badnode <call>.. (8)
194 11.122 set/badspotter <call>.. (8)
195 11.123 set/badword <word>.. (8)
196 11.124 set/bbs <call> [<call>..] (5)
198 11.126 set/clx <call> [<call>..] (5)
199 11.127 set/debug <name> (9)
202 11.130 set/dxgrid (0)
204 11.132 set/dxnet <call> [<call>..] (5)
206 11.134 set/email <email> ... (0)
208 11.136 set/homenode <node> (0)
209 11.137 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
210 11.138 set/isolate (9)
211 11.139 set/language <lang> (0)
212 11.140 set/location <lat & long> (0)
213 11.141 set/lockout <call> (9)
214 11.142 set/logininfo (0)
215 11.143 set/name <your name> (0)
216 11.144 set/node <call> [<call>..] (5)
217 11.145 set/obscount <count> <call> (8)
218 11.146 set/page <lines per page> (0)
219 11.147 set/password (0)
220 11.148 set/password <callsign> <string> (9)
221 11.149 set/pinginterval <time> <nodecall> (9)
222 11.150 set/privilege <n> <call> [<call..] (9)
223 11.151 set/prompt <string> (0)
224 11.152 set/qra <locator> (0)
225 11.153 set/qth <your qth> (0)
226 11.154 set/register <call> ... (9)
227 11.155 set/spider <call> [<call>..] (5)
228 11.156 set/sys_location <lat & long> (9)
229 11.157 set/sys_qra <locator> (9)
231 11.159 set/usdb <call> <state> <city> (9)
232 11.160 set/usstate (0)
236 11.164 show/baddx (1)
237 11.165 show/badnode (1)
238 11.166 show/badspotter (1)
239 11.167 show/badword (1)
240 11.168 show/chat [<group>] [<lines>] (0)
241 11.169 show/configuration [<node>] (0)
242 11.170 show/configuration/node (0)
243 11.171 show/connect (1)
244 11.172 show/contest <year and month> (0)
245 11.173 show/date [<prefix>|<callsign>] (0)
246 11.174 show/db0sdx <callsign> (0)
247 11.175 show/debug (9)
249 11.177 show/dxcc <prefix> (0)
250 11.178 show/dxqsl <callsign> (0)
251 11.179 show/dxstats [days] [date] (0)
253 11.181 show/files [<filearea> [<string>]] (0)
254 11.182 show/filter (0)
255 11.183 show/hfstats [days] [date] (0)
256 11.184 show/hftable [days] [date] [prefix ...] (0)
257 11.185 show/hops <call> [ann|spots|route|wcy|wwv] (8)
258 11.186 show/isolate (1)
259 11.187 show/lockout <prefix>|all (9)
260 11.188 show/log [<callsign>] (8)
261 11.189 show/moon [ndays] [<prefix>|<callsign>] (0)
262 11.190 show/muf <prefix> [<hours>][long] (0)
264 11.192 show/newconfiguration [<node>] (0)
265 11.193 show/newconfiguration/node (0)
266 11.194 show/node [<callsign> ...] (1)
267 11.195 show/prefix <callsign> (0)
268 11.196 show/program (5)
269 11.197 show/qra <lat> <long> (0)
270 11.198 show/qra <locator> [<locator>] (0)
271 11.199 show/qrz <callsign> (0)
272 11.200 show/registered [<prefix>] (9)
273 11.201 show/route <callsign> ... (0)
274 11.202 show/satellite <name> [<hours> <interval>] (0)
275 11.203 show/station all [<regex>] (6)
276 11.204 show/station [<callsign> ..] (0)
277 11.205 show/sun [ndays] [<prefix>|<callsign>] (0)
278 11.206 show/time [<prefix>|<callsign>] (0)
279 11.207 show/usdb [call ..] (0)
280 11.208 show/vhfstats [days] [date] (0)
281 11.209 show/vhftable [days] [date] [prefix ...] (0)
283 11.211 show/wcy <n> (0)
284 11.212 show/wm7d <callsign> (0)
286 11.214 show/wwv <n> (0)
288 11.216 spoof <call> <command> (9)
289 11.217 stat/channel [<callsign>] (5)
290 11.218 stat/db <dbname> (5)
292 11.220 stat/msg <msgno> (1)
293 11.221 stat/route_node <callsign> (5)
294 11.222 stat/route_node all (5)
295 11.223 stat/route_user <callsign> (5)
296 11.224 stat/route_user all (5)
297 11.225 stat/user [<callsign>] (5)
299 11.227 talk <call> > <node> [<text>] (0)
300 11.228 talk <call> [<text>] (0)
301 11.229 type <filearea>/<name> (0)
302 11.230 uncatchup <node call> all|[msgno> ...] (5)
303 11.231 unset/announce (0)
304 11.232 unset/anntalk (0)
305 11.233 unset/baddx <call>.. (8)
306 11.234 unset/badnode <call>.. (8)
307 11.235 unset/badspotter <call>.. (8)
308 11.236 unset/badword <word>.. (8)
309 11.237 unset/beep (0)
310 11.238 unset/debug <name> (9)
312 11.240 unset/dxcq (0)
313 11.241 unset/dxgrid (0)
314 11.242 unset/dxitu (0)
315 11.243 unset/echo (0)
316 11.244 unset/email (0)
317 11.245 unset/here (0)
318 11.246 unset/hops <call> ann|spots|route|wwv|wcy (8)
319 11.247 unset/isolate (9)
320 11.248 unset/lockout <call> (9)
321 11.249 unset/logininfo (0)
322 11.250 unset/password <call> ... (9)
323 11.251 unset/privilege (0)
324 11.252 unset/prompt (0)
325 11.253 unset/register <call> ... (9)
326 11.254 unset/talk (0)
327 11.255 unset/usstate (0)
333 11.261 wx full <text> (0)
334 11.262 wx sysop <text> (5)
337 ______________________________________________________________________
339 \e[1m1. Routing and Filtering
\e[0m
343 \e[1m1.1. Introduction
\e[0m
345 From DXSpider version 1.48, major changes were introduced to the way
346 node connections are treated. This is part of an ongoing process to
347 remove problems with loops and to enable talk and other functions to
348 propagate across the whole of the worldwide cluster network. In fact,
349 in a Spider network, it would be useful, perhaps even necessary to
350 have loops. This would give real resilience to the network, meaning
351 that if a link dropped, the information flow would simply come in and
352 go out via a different route. Of course, we do not have a complete
353 network of Spider nodes, there are other programs out there. Some of
354 these do not have any protection from loops. Certainly AK1A does not
355 handle loops well at all. It is therefore necessary to have some form
356 of protection for these nodes.
359 In fact DXSpider has had a simple system for some time which is called
360 \e[4misolation
\e[24m. This is similar to what in other systems such as
\e[1mclx
\e[22m, is
361 called
\e[4mpassive
\e[24m
\e[4mmode
\e[24m. A more detailed explanation of
\e[4misolation
\e[24m is given
362 further below. This system is still available and, for simple
363 networks, is probably all that you need.
366 The new functionality introduced in version 1.48 allows filtering the
367 node and user protocol frames on a "per interface" basis. We call this
368 \e[4mroute
\e[24m
\e[4mfiltering
\e[24m. This is used
\e[1minstead of
\e[4m
\e[22misolation
\e[24m.
371 What this really means is that you can control more or less completely
372 which user and node management PC protocol frames pass to each of your
373 partner nodes. You can also limit what comes into your node from your
374 partners. It is even possible to control the settings that your
375 partner node has for the routing information that it sends to you
376 (using the
\e[4mrcmd
\e[24m command).
379 \e[1m1.2. Route Filters
\e[0m
381 Initially when route filters were being tested we generated a
382 "default" filter. Unfortunately it quickly became apparent that this
383 might suit the UK cluster network but didn't really fit anybody else.
384 However using a default filter is an appropriate thing to do. How, is
385 explained further on.
388 The first thing that you must do is determine whether you need to use
389 route filtering
\e[1mat all
\e[22m. If you are a "normal" node with two or three
390 partners and you arranged in an "official" non-looping tree type
391 network, then
\e[1myou do not need to do route filtering
\e[22mand you will feel
392 a lot better for not getting involved. If you are successfully using
393 \e[4misolation
\e[24m then you also probably don't need to use route filtering.
396 To put it simply, you should not mix Isolation and Route Filtering.
397 It will work, of sorts, but you will not get the expected results. If
398 you are using Isolation sucessfully at the moment, do not get involved
399 in Route Filtering unless you have a good supply of aspirin! Once you
400 have started down the road of Route Filtering, do not use Isolation
401 either. Use one or the other, not both.
404 You will only require this functionality if you are "well-connected".
405 What that means is that you are connected to several different parts
406 of (say) the EU cluster and, at the same time, also connected to two
407 or three places in the US which, in turn are connected back to the EU.
408 This is called a "loop" and if you are seriously looped then you need
412 I should at this stage give a little bit of background on filters.
413 All the filters in Spider work in basically the same way. You can
414 either accept or reject various options in order to create the filter
415 rules you wish to achieve. Some filters are user settable, others can
416 only be altered by the sysop. Route filtering can only be done by the
421 Anyway, without further discouragement, let me start the process of
425 \e[1m1.3. The node_default filter
\e[0m
427 All normal systems should have a default routing filter and it should
428 usually be set to send only the normal, unlooped, view of your
429 "national" network. Here in the UK that means nodes from the UK and
430 Eire, in EU it is more complex as the networks there grew up in a more
435 The generic commands are:-
439 reject/route node_default <filter_option>
443 accept/route node_default <filter_option>
447 where filter_option is one of the following ...
456 channel_dxcc <numbers>
457 channel_itu <numbers>
458 channel_zone <numbers>
462 Please be careful if you alter this setting, it will affect
\e[4mALL
\e[24m your
463 links! Remember, this is a
\e[4mdefault
\e[24m filter for node connections, not a
464 \e[4mper
\e[24m
\e[4mlink
\e[24m default.
467 For the default routing filter then you have two real choices: either
468 a "national" view or the "safe" option of only your own callsign.
469 Examples of each (for my node: GB7DJK) are:-
473 acc/route node_default call_dxcc 61,38
474 acc/route node_default call gb7djk
478 GB7DJK uses the first of these. The DXCC countries can be obtained
479 from the
\e[4mshow/prefix
\e[24m command.
482 The example filters shown control
\e[4moutput
\e[24m
\e[1mTO
\e[22mall your partner nodes
483 unless they have a specific filter applied to them (see next section).
486 It is also possible to control the
\e[4mincoming
\e[24m routing information that
487 you are prepared to accept
\e[1mFROM
\e[22myour partner nodes. The reason this is
488 necessary is to make sure that stuff like mail, pings and similar
489 commands a) go down the correct links and b) don't loop around
490 excessively. Again using GB7DJK as an example a typical default input
491 filter would be something like:
495 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
499 What this does is accept node and user information for our national
500 network from nodes that are in our national network, but rejects such
501 information from anyone else. Although it doesn't explicitly say so,
502 by implication, any other node information (not from the UK and Eire)
506 As I imagine it will take a little while to get one's head around all
507 of this you can study the effect of any rules that you try by watching
508 the debug output after having done:-
516 After you have got tired of that, to put it back the way it was:-
524 \e[1m1.4. General route filtering
\e[0m
526 Exactly the same rules apply for general route filtering. You would
527 use either an accept filter or a reject filter like this ...
531 reject/route <node_call> <filter_option>
535 accept/route <node_call> <filter_option>
539 Here are some examples of route filters ...
543 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
544 rej/route all (equiv to [very] restricted mode)
545 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
546 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
550 In practice you will either be opening the default filter out for a
551 partner by defining a specific filter for that callsign:-
556 acc/route gb7baa input all
560 or restricting it quite a lot, in fact making it very nearly like an
561 \e[4misolated
\e[24m node, like this:-
565 acc/route pi4ehv-8 call gb7djk
566 rej/route pi4ehv-8 input call_dxcc 61,38
570 This last example takes everything except UK and Eire from PI4EHV-8
571 but only sends him my local configuration (just a PC19 for GB7DJK and
572 PC16s for my local users).
575 It is possible to write
\e[1mmuch
\e[22mmore complex rules, there are up to 10
576 accept/reject pairs per callsign per filter. For more information see
581 \e[1m1.5. General filter rules
\e[0m
583 Upto v1.44 it was not possible for the user to set their own filters.
584 From v1.45 though that has all changed. It is now possible to set
585 filters for just about anything you wish. If you have just updated
586 from an older version of DXSpider you will need to update your new
587 filters. You do not need to do anything with your old filters, they
588 will be renamed as you update.
592 There are 3 basic commands involved in setting and manipulating
593 filters. These are
\e[4maccept
\e[24m,
\e[4mreject
\e[24m and
\e[4mclear
\e[24m. First we will look
594 generally at filtering. There are a number of things you can filter in
595 the DXSpider system. They all use the same general mechanism.
598 In general terms you can create a "reject" or an "accept" filter which
599 can have up to 10 lines in it. You do this using, for example ...
608 where ..... are the specific commands for that type of filter. There
609 are filters for spots, wwv, announce, wcy and (for sysops) connects.
610 See each different accept or reject command reference for more
613 There is also a command to clear out one or more lines in a filter.
623 There is clear/xxxx command for each type of filter.
626 and you can check that your filters have worked by the command ...
634 For now we are going to use spots for the examples, but you can apply
635 the same principles to all types of filter.
638 \e[1m1.6. Types of filter
\e[0m
640 There are two main types of filter,
\e[4maccept
\e[24m or
\e[4mreject
\e[24m. You can use
641 either to achieve the result you want dependent on your own preference
642 and which is more simple to do. It is pointless writing 8 lines of
643 reject filters when 1 accept filter would do the same thing! Each
644 filter has 10 lines (of any length) which are tried in order. If a
645 line matches then the action you have specified is taken (ie reject
646 means ignore it and accept means take it)
649 If you specify reject filters, then any lines that arrive that match
650 the filter will be dumped but all else will be accepted. If you use
651 an accept filter, then ONLY the lines in the filter will be accepted
652 and all else will be dumped. For example if you have a single line
653 \e[4maccept
\e[24m filter ...
657 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
661 then you will
\e[4mONLY
\e[24m get VHF spots
\e[4mfrom
\e[24m or
\e[4mto
\e[24m CQ zones 14, 15 and 16.
664 If you set a reject filter like this ...
668 reject/spots on hf/cw
672 Then you will get everything
\e[4mEXCEPT
\e[24m HF CW spots. You could make this
673 single filter even more flexible. For example, if you are interested
674 in IOTA and will work it even on CW even though normally you are not
675 interested in CW, then you could say ...
679 reject/spots on hf/cw and not info iota
683 But in that case you might only be interested in iota and say:-
687 accept/spots not on hf/cw or info iota
691 which achieves exactly the same thing. You should choose one or the
692 other until you are comfortable with the way it works. You can mix
693 them if you wish (actually you can have an accept AND a reject on the
694 same line) but don't attempt this until you are sure you know what you
698 You can arrange your filter lines into logical units, either for your
699 own understanding or simply convenience. Here is an example ...
703 reject/spots 1 on hf/cw
704 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
708 What this does is to ignore all HF CW spots and also rejects any spots
709 on VHF which don't either originate or spot someone in Europe.
713 This is an example where you would use a line number (1 and 2 in this
714 case), if you leave the digit out, the system assumes '1'. Digits
715 '0'-'9' are available. This make it easier to see just what filters
716 you have set. It also makes it more simple to remove individual
717 filters, during a contest for example.
720 You will notice in the above example that the second line has
721 brackets. Look at the line logically. You can see there are 2
722 separate sections to it. We are saying reject spots that are VHF or
723 above
\e[4mAPART
\e[24m from those in zones 14, 15 and 16 (either spotted there or
724 originated there). If you did not have the brackets to separate the 2
725 sections, then Spider would read it logically from the front and see a
726 different expression entirely ...
730 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
734 The simple way to remember this is, if you use OR - use brackets.
735 Whilst we are here CASE is not important. 'And BY_Zone' is just the
736 same as 'and by_zone'.
738 As mentioned earlier, setting several filters can be more flexible
739 than simply setting one complex one. Doing it in this way means that
740 if you want to alter your filter you can just redefine or remove one
741 or more lines of it or one line. For example ...
745 reject/spots 1 on hf/ssb
749 would redefine our earlier example, or
757 To remove all the filter lines in the spot filter ...
765 \e[1m1.7. Filter options
\e[0m
767 You can filter in several different ways. The options are listed in
768 the various helpfiles for accept, reject and filter.
772 \e[1m1.8. Default filters
\e[0m
774 Sometimes all that is needed is a general rule for node connects.
775 This can be done with a node_default filter. This rule will always be
776 followed, even if the link is isolated, unless another filter is set
777 specifically. Default rules can be set for nodes and users. They can
778 be set for spots, announces, WWV and WCY. They can also be used for
779 hops. An example might look like this ...
783 accept/spot node_default by_zone 14,15,16,20,33
784 set/hops node_default spot 50
788 This filter is for spots only, you could set others for announce, WWV
789 and WCY. This filter would work for ALL nodes unless a specific
790 filter is written to override it for a particular node. You can also
791 set a user_default should you require. It is important to note that
792 default filters should be considered to be "connected". By this I
793 mean that should you override the default filter for spots, you need
794 to add a rule for the hops for spots also.
797 \e[1m1.9. Advanced filtering
\e[0m
799 Once you are happy with the results you get, you may like to
803 The previous example that filters hf/cw spots and accepts vhf/uhf
804 spots from EU can be written with a mixed filter, for example ...
810 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
814 Note that the first filter has not been specified with a number. This
815 will automatically be assumed to be number 1. In this case, we have
816 said
\e[4mreject
\e[24m
\e[4mall
\e[24m
\e[4mHF
\e[24m
\e[4mspots
\e[24m
\e[4min
\e[24m
\e[4mthe
\e[24m
\e[4mCW
\e[24m
\e[4msection
\e[24m
\e[4mof
\e[24m
\e[4mthe
\e[24m
\e[4mbands
\e[24m
\e[4mbut
\e[24m
\e[4maccept
\e[24m
\e[4mall
\e[0m
817 \e[4mothers
\e[24m
\e[4mat
\e[24m
\e[4mHF.
\e[24m
\e[4mAlso
\e[24m
\e[4maccept
\e[24m
\e[4manything
\e[24m
\e[4min
\e[24m
\e[4mVHF
\e[24m
\e[4mand
\e[24m
\e[4mabove
\e[24m
\e[4mspotted
\e[24m
\e[4min
\e[24m
\e[4mor
\e[24m
\e[4mby
\e[0m
818 \e[4moperators
\e[24m
\e[4min
\e[24m
\e[4mthe
\e[24m
\e[4mzones
\e[24m
\e[4m14,
\e[24m
\e[4m15
\e[24m
\e[4mand
\e[24m
\e[4m16
\e[24m. Each filter slot actually has a
819 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
823 It was mentioned earlier that after a reject test that doesn't match,
824 the default for following tests is 'accept', the reverse is true for
825 'accept'. In the example what happens is that the reject is executed
826 first, any non hf/cw spot is passed to the accept line, which lets
827 through everything else on HF. The next filter line lets through just
828 VHF/UHF spots from EU.
831 \e[1m1.10. Basic hop control
\e[0m
833 In /spider/data you will find a file called hop_table.pl. This is the
834 file that controls your hop count settings. It has a set of default
835 hops on the various PC frames and also a set for each node you want to
836 alter the hops for. You may be happy with the default settings of
837 course, but this powerful tool can help to protect and improve the
838 network. The file will look something like this ...
843 # hop table construction
848 # default hopcount to use
851 # some variable hop counts based on message type
862 # the per node hop control thingy
894 Each set of hops is contained within a pair of curly braces and
895 contains a series of PC frame types. PC11 for example is a DX spot.
896 The figures here are not exhaustive but should give you a good idea of
900 SHould any of the nodecalls include an ssid, it is important to wrap
901 the whole call in single quotes, like this ...
916 If you do not do this, you will get errors and the file will not work
920 You can alter this file at any time, including whilst the cluster is
921 running. If you alter the file during runtime, the command
\e[4mload/hops
\e[0m
922 will bring your changes into effect.
925 \e[1m1.11. Hop Control on Specific Nodes
\e[0m
927 You can set a callsign specific hop count for any of the standard
932 set/hops gb7djk spot 4
933 set/hops node_default route 10
934 set/hops gb7baa wcy 5
938 all work on their specific area of the protocol.
941 The
\e[4mset/hops
\e[24m command overrides any hops that you have set otherwise.
944 You can show what hops have been set using the
\e[4mshow/hops
\e[24m command.
947 \e[1m1.12. Isolating networks
\e[0m
949 It is possible to isolate networks from each other on a "gateway" node
950 using the
\e[4mset/isolate
\e[24m
\e[4m<node_call>
\e[24m command.
953 The effect of this is to partition an isolated network completely from
954 another node connected to your node. Your node will appear on and
955 otherwise behave normally on every network to which you are connected,
956 but data from an isolated network will not cross onto any other
957 network or vice versa. However all the spot, announce and WWV traffic
958 and personal messages will still be handled locally (because you are a
959 real node on all connected networks), that is locally connected users
960 will appear on all networks and will be able to access and receive
961 information from all networks transparently. All routed messages will
962 be sent as normal, so if a user on one network knows that you are a
963 gateway for another network, he can still still send a talk/announce
964 etc message via your node and it will be routed across.
967 If you use isolate on a node connection you will continue to receive
968 all information from the isolated partner, however you will not pass
969 any information back to the isolated node. There are times when you
970 would like to forward only spots across a link (maybe during a contest
971 for example). To do this, isolate the node in the normal way and use
972 an
\e[4macc/spot
\e[24m
\e[4m>call<
\e[24m
\e[4mall
\e[24m filter to override the isolate.
975 \e[1m1.13. A DXSpider Filtering Tutorial
\e[0m
977 There is now an excellent primer/tutorial on filtering written by Jim
978 Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
979 suggest you read. You can read it here The DXSpider User Filtering
983 \e[1m2. Other filters
\e[0m
985 \e[1m2.1. Filtering Mail
\e[0m
987 In the /spider/msg directory you will find a file called
988 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
989 original looks something like this ....
993 # the list of regexes for messages that we won't store having
994 # received them (bear in mind that we must receive them fully before
998 # The format of each line is as follows
1000 # type source pattern
1001 # P/B/F T/F/O/S regex
1003 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1004 # source: T - to field, F - from field, O - origin, S - subject
1005 # pattern: a perl regex on the field requested
1007 # Currently only type B and P msgs are affected by this code.
1009 # The list is read from the top down, the first pattern that matches
1010 # causes the action to be taken.
1012 # The pattern can be undef or 0 in which case it will always be selected
1013 # for the action specified
1024 I think this is fairly self explanatory. It is simply a list of
1025 subject headers that we do not want to pass on to either the users of
1026 the cluster or the other cluster nodes that we are linked to. This is
1027 usually because of rules and regulations pertaining to items for sale
1028 etc in a particular country.
1032 \e[1m2.2. Filtering words from text fields in Announce, Talk and DX spots
\e[0m
1034 From version 1.48 onwards the interface to this has changed. You can
1035 now use the commands
\e[4mset/badword
\e[24m to add words that you are not
1036 prepared to see on the cluster,
\e[4munset/badword
\e[24m to allow that word again
1037 and
\e[4mshow/badword
\e[24m to list the words that you have set.
1040 If you have a previous
\e[4m/spider/data/badwords
\e[24m, the first time you start
1041 the node, it will read and convert this file to the new commands. The
1042 old style file will then be removed.
1045 \e[1m2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
\e[0m
1048 There are a number of commands that control whether a spot progresses
1049 any further by regarding it as "bad" in some way.
1052 A DX Spot has a number of fields which can be checked to see whether
1053 they contain "bad" values, they are: the DX callsign itself, the
1054 Spotter and the Originating Node.
1057 There are a set of commands which allow the sysop to control whether a
1068 These work in the same as the
\e[4mset/badword
\e[24m command, you can add any
1069 words or callsigns or whatever to the appropriate database. For
1070 example, to stop a spot from a particular node you do:
1074 set/badnode gb7djk gb7dxc
1082 set/badspotter b0mb p1rat nocall
1090 set/baddx video wsjt
1094 You can remove a word using the appropriate unset command
1095 (
\e[4munset/baddx,
\e[24m
\e[4munset/badspotter,
\e[24m
\e[4munset/badnode
\e[24m) or list them using one
1096 of
\e[4mshow/baddx,
\e[24m
\e[4mshow/badspotter
\e[24m and
\e[4mshow/badnode
\e[24m.
1101 DXSpider deals seamlessly with standard AK1A type mail. It supports
1102 both personal and bulletin mail and the sysop has additional commands
1103 to ensure that mail gets to where it is meant. DXSpider will send
1104 mail almost immediately, assuming that the target is on line.
1105 However, only one mail message is dealt with at any one time. If a
1106 mail message is already being sent or recieved, then the new message
1107 will be queued until it has finished.
1109 The cluster mail is automatically deleted after 30 days unless the
1110 sysop sets the "keep" flag using the
\e[4mmsg
\e[24m command.
1113 \e[1m3.1. Personal mail
\e[0m
1115 Personal mail is sent using the
\e[4msp
\e[24m command. This is actually the
1116 default method of sending mail and so a simple
\e[4ms
\e[24m for send will do. A
1117 full list of the send commands and options is in the
\e[4mcommand
\e[24m
\e[4mset
\e[0m
1118 section, so I will not duplicate them here.
1121 \e[1m3.2. Bulletin mail
\e[0m
1123 Bulletin mail is sent by using the
\e[4msb
\e[24m command. This is one of the
1124 most common mistakes users make when sending mail. They send a
1125 bulletin mail with
\e[4ms
\e[24m or
\e[4msp
\e[24m instead of
\e[4msb
\e[24m and of course the message
1126 never leaves the cluster. This can be rectified by the sysop by using
1127 the
\e[4mmsg
\e[24m command.
1130 Bulletin addresses can be set using the Forward.pl file.
1133 \e[1m3.3. Forward.pl
\e[0m
1135 DXSpider receives all and any mail sent to it without any alterations
1136 needed in files. Because personal and bulletin mail are treated
1137 differently, there is no need for a list of accepted bulletin
1138 addresses. It is necessary, however, to tell the program which links
1139 accept which bulletins. For example, it is pointless sending
1140 bulletins addresses to "UK" to any links other than UK ones. The file
1141 that does this is called forward.pl and lives in /spider/msg. At
1142 default, like other spider files it is named forward.pl.issue. Rename
1143 it to forward.pl and edit the file to match your requirements. The
1149 # this is an example message forwarding file for the system
1151 # The format of each line is as follows
1153 # type to/from/at pattern action destinations
1154 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1156 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1157 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1158 # pattern: a perl regex on the field requested
1159 # action: I - ignore, F - forward
1160 # destinations: a reference to an array containing node callsigns
1162 # if it is non-private and isn't in here then it won't get forwarded
1164 # Currently only type B msgs are affected by this code.
1166 # The list is read from the top down, the first pattern that matches
1167 # causes the action to be taken.
1169 # The pattern can be undef or 0 in which case it will always be selected
1170 # for the action specified
1172 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1173 # pattern) then it will always be forwarded to every node that doesn't have
1174 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1175 # you allow a new link with this on EVERY bull will be forwarded immediately
1176 # on first connection)
1186 Simply insert a bulletin address and state in the brackets where you
1187 wish that mail to go. For example, you can see here that mail sent to
1188 "UK" will only be sent to the UK links and not to PA4AB-14.
1191 To force the cluster to reread the file use load/forward
1194 NB: If a user tries to send mail to a bulletin address that does not
1195 exist in this file, they will get an error.
1198 \e[1m3.4. The msg command
\e[0m
1200 The
\e[4mmsg
\e[24m command is a very powerful and flexible tool for the sysop.
1201 It allows the sysop to alter to and from fields and make other changes
1202 to manage the cluster mail.
1204 Here is a full list of the various options ...
1208 MSG TO <msgno> <call> - change TO callsign to <call>
1209 MSG FRom <msgno> <call> - change FROM callsign to <call>
1210 MSG PRrivate <msgno> - set private flag
1211 MSG NOPRrivate <msgno> - unset private flag
1212 MSG RR <msgno> - set RR flag
1213 MSG NORR <msgno> - unset RR flag
1214 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1215 MSG NOKEep <msgno> - unset the keep flag
1216 MSG SUbject <msgno> <new> - change the subject to <new>
1217 MSG WAittime <msgno> - remove any waiting time for this message
1218 MSG NOREad <msgno> - mark message as unread
1219 MSG REad <msgno> - mark message as read
1220 MSG QUeue - queue any outstanding bulletins
1221 MSG QUeue 1 - queue any outstanding private messages
1225 These commands are simply typed from within the cluster as the sysop
1229 \e[1m3.5. Message status
\e[0m
1231 You can check on a message from within the cluster by using the
1232 command
\e[4mstat/msg
\e[24m. This will give you additional information on the
1233 message number including which nodes have received it, which node it
1234 was received from and when etc. Here is an example of the output of
1239 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1242 Msg Time: 26-Jan-2001 1302Z
1246 Subject: AMSAT 2line KEPS 01025.AMSAT
1248 Got it Nodes: GB7BAA, GB7ADX
1252 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1256 \e[1m3.6. Filtering mail
\e[0m
1258 This is described in the section on
\e[4mOther
\e[24m
\e[4mfilters
\e[24m so I will not
1262 \e[1m3.7. Distribution lists
\e[0m
1264 Distribution lists are simply a list of users to send certain types of
1265 mail to. An example of this is mail you only wish to send to other
1266 sysops. In /spider/msg there is a directory called
\e[4mdistro
\e[24m. You put
1267 any distibution lists in here. For example, here is a file called
1268 SYSOP.pl that caters for the UK sysops.
1271 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1272 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1273 GB7DXK GB7DXI GB7DXS)
1277 Any mail sent to "sysop" would only be sent to the callsigns in this
1281 \e[1m3.8. BBS interface
\e[0m
1283 Spider provides a simple BBS interface. No input is required from the
1284 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1285 and pushes any required mail to the cluster. No mail can flow from
1286 Spider to the BBS, the interface is one-way.
1289 Please be careful not to flood the cluster network with unnecessary
1290 mail. Make sure you only send mail to the clusters that want it by
1291 using the Forward.pl file very carefully.
1294 \e[1m4. Scripts
\e[0m
1296 From 1.48 onwards it will become increasingly possible to control
1297 DXSpider's operation with scripts of various kinds.
1300 The directory /spider/scripts is where it all happens and is used for
1301 several things. Firstly it contains a file called startup that can be
1302 used to call in any changes to the cluster from the default settings
1303 on startup. This script is executed immediately after all
1304 initialisation of the node is done but before any connections are
1305 possible. Examples of this include how many spots it is possible to
1306 get with the sh/dx command, whether you want registration/passwords to
1307 be permanently on etc. An example file is shown below and is included
1308 in the distribution as startup.issue.
1313 # startup script example
1315 # set maximum no of spots allowed to 100
1316 # set/var $Spot::maxspots = 100
1318 # Set registration on
1319 # set/var $main::reqreg = 1
1322 # set/var $main::passwdreq = 1
1327 As usual, any text behind a # is treated as a comment and not read.
1328 To use this file, simply rename it from startup.issue to startup. In
1329 our example above there are three options. The first option is the
1330 amount of spots that a user can request with the
\e[4msh/dx
\e[24m command.
1331 Normally the default is to give 10 spots unless the user specifies
1332 more. Without this line enabled, the maximum a user can request is
1333 100 spots. Depending on your link quality you may wish to enable more
1334 or less by specifying the number.
1337 The other 2 options are dealt with more fully in the security section.
1340 Secondly, it is used to store the login scripts for users and nodes.
1341 Currently this can only be done by the sysop but it is envisaged that
1342 eventually users will be able to set their own. An example is
1343 included in the distibution but here is a further example.
1360 The lines in between commands can simply insert a blank line or a
1361 character such as a + sign to make the output easier to read. Simply
1362 create this script with your favourite editor and save it with the
1363 callsign of the user as the filename. Filenames should always be in
1367 Commands can be inserted in the same way for nodes. A node may wish a
1368 series of commands to be issued on login, such as a merge command for
1372 Thirdly, there are 2 default scripts for users and nodes who do not
1373 have a specifically defined script. These are
\e[4muser_default
\e[24m and
1374 \e[4mnode_default
\e[0m
1377 \e[1m5. Databases
\e[0m
1379 Spider allows the creation of local or remote databases. It supports
1380 chained databases, allowing several different databases to be scanned
1381 with one simple command. Importing of databases is limited at present
1382 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1383 database but will expand with time.
1386 \e[1m5.1. Creating databases
\e[0m
1388 Creating a database could not be more simple. All the commands are
1389 sent from the cluster prompt as the
\e[4msysop
\e[24m user.
1391 To create a database you use the command
\e[4mdbcreate
\e[24m. It can be used in
1392 3 different ways like so ..
1399 To simply create a database locally, you just tell the command the
1400 name of the database. This does not create the actual database, it
1401 simply defines it to say that it exists.
1405 dbcreate <name> chain <name> [<name>...]
1409 This creates a chained database entry. The first database will be
1410 scanned, then the second, the third etc...
1414 dbcreate <name> remote <name>
1418 This creates a remote entry. the first name field is the database
1419 name at the remote node, then the remote switch, then the actual
1420 node_call of the remote node, for example...
1424 dbcreate buckmaster remote gb7dxc
1428 Remote databases cannot be chained, however, the last database in a
1429 chain can be a remote database.
1432 \e[1m5.2. Importing databases
\e[0m
1434 The only databases that Spider can currently import are the standard
1435 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1436 This will be added to with time.
1438 To import such a database, first put the file somewhere useful like
1439 /tmp and then issue the following command ...
1443 dbimport oblast /tmp/OBLAST.FUL
1447 This will update the existing local oblast database or create it if it
1451 \e[1m5.3. Checking available databases
\e[0m
1453 Once a database is created, you will want to check that it has been
1454 added. To do this use the
\e[4mdbavail
\e[24m command. This will output the
1455 available databases. For example ...
1460 DB Name Location Chain
1464 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1468 \e[1m5.4. Looking up databases
\e[0m
1470 To look for information in a defined database, simply use the
\e[4mdbshow
\e[0m
1471 command, for example ...
1475 dbshow buckmaster G0YLM
1479 will show the information for the callsign G0YLM from the buckmaster
1480 database if it exists. To make things more standard for the users you
1481 can add an entry in the Aliases file so that it looks like a standard
1482 \e[4mshow
\e[24m command like this ...
1486 Now you can simply use show/buckmaster or an abreviation.
1489 \e[1m5.5. Removing databases
\e[0m
1491 To delete an existing database you use the
\e[4mdbremove
\e[24m command. For
1500 would remove the oblast database and its associated datafile from the
1501 system. There are no warnings or recovery possible from this command.
1502 If you remove a database it ceases to exist and would have to be
1503 created from scratch if you still required it.
1506 \e[1m6. Information, files and useful programs
\e[0m
1510 One of the more important things a cluster sysop needs to do is to get
1511 information to his users. The simplest way to do this is to have a
1512 banner that is sent to the user on login. This is know as a "message
1513 of the day" or "motd". To set this up, simply create a file in
1514 /spider/data called motd and edit it to say whatever you want. It is
1515 purely a text file and will be sent automatically to anyone logging in
1517 \e[1m6.2. MOTD_NOR
\e[0m
1519 This message of the day file lives in the same directory as the
1520 standard motd file but is only sent to non-registered users. Once
1521 registered they will receive the same message as any other user.
1524 \e[1m6.3. Downtime message
\e[0m
1526 If for any reason the cluster is down, maybe for upgrade or
1527 maintenance but the machine is still running, a message can be sent to
1528 the user advising them of the fact. This message lives in the
1529 /spider/data directory and is called "offline". Simply create the
1530 file and edit it to say whatever you wish. This file will be sent to
1531 a user attempting to log into the cluster when DXSpider is not
1535 \e[1m6.4. Other text messages
\e[0m
1537 You can set other text messages to be read by the user if they input
1538 the file name. This could be for news items or maybe information for
1539 new users. To set this up, make a directory under /spider called
1540 \e[4mpackclus
\e[24m. Under this directory you can create files called
\e[4mnews
\e[24m or
1541 \e[4mnewuser
\e[24m for example. In fact you can create files with any names you
1542 like. These can be listed by the user with the command ....
1550 They can be read by the user by typing the command ....
1558 If the file they want to read is called
\e[4mnews
\e[24m. You could also set an
1559 alias for this in the Alias file to allow them just to type
\e[4mnews
\e[0m
1562 You can also store other information in this directory, either
1563 directly or nested under directories. One use for this would be to
1564 store DX bulletins such as the OPDX bulletins. These can be listed
1565 and read by the user. To keep things tidy, make a directory under
1566 /spider/packclus called
\e[4mbulletin
\e[24m. Now copy any OPDX or similar
1567 bulletins into it. These can be listed by the user in the same way as
1568 above using the
\e[4mshow/files
\e[24m command with an extension for the bulletin
1569 directory you have just created, like this ....
1577 An example would look like this ....
1580 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1584 You can see that in the files area (basically the packclus directory)
1585 there is a file called
\e[4mnews
\e[24m and a directory called
\e[4mbulletin
\e[24m. You can
1586 also see that dates they were created. In the case of the file
\e[4mnews
\e[24m,
1587 you can also see the time it was last modified, a good clue as to
1588 whether the file has been updated since you last read it. To read the
1589 file called
\e[4mnews
\e[24m you would simply issue the command ....
1597 To look what is in the bulletin directory you issue the command ....
1602 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1603 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1604 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1605 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1606 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1607 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1608 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1609 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1610 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1611 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1612 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1613 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1614 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1615 Press Enter to continue, A to abort (16 lines) >
1619 You can now read any file in this directory using the type command,
1624 type bulletin/opdx391
1625 Ohio/Penn DX Bulletin No. 391
1626 The Ohio/Penn Dx PacketCluster
1630 Editor Tedd Mirgliotta, KB8NW
1631 Provided by BARF-80 BBS Cleveland, Ohio
1632 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1633 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1634 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1635 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1636 Press Enter to continue, A to abort (508 lines) >
1640 The page length will of course depend on what you have it set to!
1643 \e[1m6.5. The Aliases file
\e[0m
1645 You will find a file in /spider/cmd/ called Aliases. This is the file
1646 that controls what a user gets when issuing a command. It is also
1647 possible to create your own aliases for databases and files you create
1651 You should not alter the original file in /spider/cmd/ but create a
1652 new file with the same name in /spider/local_cmd. This means that any
1653 new Aliases files that is downloaded will not overwrite your self
1654 created Aliases and also that you do not override any new Aliases with
1655 your copy in /spider/local_cmd/. You must remember that any files you
1656 store in /spider/local/ or /spider/local_cmd override the originals if
1657 the same lines are used in both files.
1660 The best way of dealing with all this then is to only put your own
1661 locally created Aliases in the copy in /spider/local_cmd. The example
1662 below is currently in use at GB7MBC.
1667 # Local Aliases File
1674 '^news$', 'type news', 'type',
1677 '^sh\w*/buck$', 'show/qrz', 'show',
1678 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1679 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1680 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1681 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1687 Each alphabetical section should be preceded by the initial letter and
1688 the section should be wrapped in square brackets as you can see. The
1689 syntax is straightforward. The first section on each line is the new
1690 command that will be allowed once the alias is included. The second
1691 section is the command it is replacing and the last section is the
1692 actual command that is being used.
1695 The eagle-eyed amongst you will have noticed that in the first
1696 section, the new alias command has a '^' at the start and a '$' at the
1697 end. Basically these force a perfect match on the alias. The '^'
1698 says match the beginning exactly and the with similar commands.
1701 I have 3 different types of alias in this file. At the top is an
1702 alias for 'news'. This is a file I have created in the
1703 /spider/packclus/ directory where I can inform users of new
1704 developments or points of interest. In it's initial form a user would
1705 have to use the command
\e[4mtype
\e[24m
\e[4mnews
\e[24m. The alias allows them to simply
1706 type
\e[4mnews
\e[24m to get the info. Second is an alias for the
\e[4mshow/qrz
\e[0m
1707 command so that those users used to the original
\e[4mshow/buck
\e[24m command in
1708 AK1A will not get an error, and the rest of the lines are for locally
1709 created databases so that a user can type
\e[4mshow/hftest
\e[24m instead of
1710 having to use the command
\e[4mdbshow
\e[24m
\e[4mhftest
\e[24m which is not as intuitive.
1713 This file is just an example and you should edit it to your own
1714 requirements. Once created, simply issue the command
\e[4mload/alias
\e[24m at
1715 the cluster prompt as the sysop user and the aliases should be
1720 \e[1m6.6. Console.pl
\e[0m
1722 In later versions of Spider a simple console program is provided for
1723 the sysop. This has a type ahead buffer with line editing facilities
1724 and colour for spots, announces etc. To use this program, simply use
1725 console.pl instead of client.
1728 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1729 edit the file with your favourite editor.
1732 \e[1m6.7. Updating kepler data
\e[0m
1734 Spider has a powerful and flexible show/satellite command. In order
1735 for this to be accurate, the kepler data has to be updated regularly.
1736 In general, this data is available as an email or via cluster mail.
1737 Updating it is simple. First you need to export the mail message as a
1738 file. You do this with the
\e[4mexport
\e[24m command from the cluster prompt as
1739 the sysop. For example ...
1743 export 5467 /spider/perl/keps.in
1747 would export message number 5467 as a file called keps.in in the
1748 /spider/perl directory.
1751 Now login to a VT as sysop and cd /spider/perl. There is a command in
1752 the perl directory called
\e[4mconvkeps.pl
\e[24m. All we need to do now is
1753 convert the file like so ...
1757 ./convkeps.pl keps.in
1761 Now go back to the cluster and issue the command ...
1769 That is it! the kepler data has been updated.
1772 \e[1m6.8. The QRZ callbook
\e[0m
1774 The command
\e[4msh/qrz
\e[24m will only work once you have followed a few simple
1775 steps. First you need to get a user ID and password from qrz.com.
1776 Simply go to the site and create one. Secondly you need to copy the
1777 file /spider/perl/Internet.pm to /spider/local and alter it to match
1778 your user ID and password. You also at this point need to set
1779 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1780 proprieter of qrz.com for allowing this access.
1783 \e[1m6.9. Connecting logging programs
\e[0m
1785 There appear to be very few logging programs out there that support
1786 telnet especially the popular ones like LogEQF, Turbolog etc. This
1787 can make it difficult to connect to your own cluster! The way to do
1788 it is to make the logging program think it has a TNC attached to a com
1789 port on the logging PC and 'push' a linux login out to it. This is
1790 achieved very simply by the use of
\e[4magetty
\e[24m.
1793 All that is required is to add a line in /etc/inittab to have the
1794 client ready for a connection on the com port of your choice.
1795 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1800 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1804 Add this after the standard runlevel lines in /etc/inittab. The above
1805 line works on ttyS1 (com2). Now as root, issue the command
\e[4mtelinit
\e[24m
\e[4mq
\e[0m
1806 and it should be ready for connection. All that is required is a 3
1807 wire serial lead (tx, rx and signal ground). Tell you logging program
1808 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1809 Login as normal and then telnet from there to the cluster.
1812 \e[1m7. Java Web applet
\e[0m
1814 In the spider tree will be a directory
\e[4mspider-web
\e[24m. This is a neat
1815 little java web applet that can be run from a website. The applet
1816 must run on the same machine as the cluster. The included README file
1820 I should comment here that the applet is precompiled, that is, ready
1821 to go. It was compiled using JDK1.3.1. If your version is earlier
1822 than this then it may not work. Should that be the case you need to
1823 recompile or update your JDK. To recompile do the following ...
1827 cd /spider/spider-web
1829 /usr/bin/javac spiderclient.java
1833 I have used /usr/bin/javac as an example, your path to javac may be
1839 Completely based on a clx web client written in Java by dl6dbh
1840 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1842 The webserver has to run on the same machine as your DxSpider software!
1844 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1846 Installation instructions (Performed as root):
1848 Put all the files in the spider-web directory into a newly created directory
1849 under the DocumentRoot of your websever for instance 'client'. In my case
1850 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1851 path should be /usr/local/httpd/htdocs/client/ for example.
1853 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1854 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1855 /usr/local/httpd/cgi-bin/ for example.
1857 Change the permissions of the files to ensure they are correct, obviously you
1858 will need to use the correct path the the files according to your system:
1860 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1861 chmod -R 755 /home/httpd/html/client/
1863 By default the spider.cgi script should pick up your hostname (As long as this
1864 is set correctly). If it does not or your hostname differs from the name that
1865 you attach to the public address that you are using, then edit spider.cgi :
1867 # Uncomment and set the hostname manually here if the above fails.
1868 # $HOSTNAME = "gb7mbc.spoo.org" ;
1872 telnet (see Listeners.pm)
1874 NOTE: If you can start the console but cannot connect to the cluster from it,
1875 then it is possible that the machine you are on cannot resolve the hostname of
1876 your cluster machine. If this is the case, you need to set your hostname
1879 You also need to set the $NODECALL variable. This prints the name of your
1880 choosing (probably your cluster callsign) on the html page.
1882 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1886 \e[1m8. Web based statistics
\e[0m
1888 From version 1.50, you can use the freeware software MRTG to produce
1889 really nice graphical statistics on your web site. For an example try
1890 http://www.gb7mbc.net/mrtg/stats.html.
1893 The following should help you get it all working.
1896 First you need to download the latest version of MRTG from
1897 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1898 the following files..
1902 libpng-1.0.14.tar.gz
1908 Login to your machine as the root user, put all the downloaded files
1909 in /usr/local/src/ (or wherever you prefer) and untar and compile
1910 them. All the information to compile and install these sources come
1911 with them. After compilation and installation, you will find MRTG in
1915 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1919 You now need to make 2 symbolic links like below...
1923 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1924 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1928 Now login to the cluster with your sysop callsign and run the command
1932 Now you are nearly there! Login as the sysop user and change to the
1933 /spider/html/mrtg/ directory. Now run the command
\e[4mindexmaker
\e[24m as shown
1938 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1942 Changing the callsign for your own cluster callsign of course!
1945 And finally you need to login as the root user and create one last
1946 symbolic link. Where this points will depend on where your html
1947 documents are kept. For RedHat systems you use...
1951 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1955 and for SuSE systems...
1959 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1963 If you now point your browser to your website as below it should all
1968 http://www.xxx.xxx/mrtg/stats.html
1972 Of course, to get the stats to update, you need to add some
1973 information in the spider crontab file as below...
1977 # Update stats for mrtg on website
1978 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1982 This will update the site every 5 minutes.
1985 \e[1m9. Security
\e[0m
1987 From version 1.49 DXSpider has some additional security features.
1988 These are not by any means meant to be exhaustive, however they do
1989 afford some security against piracy. These two new features can be
1990 used independently of each other or in concert to tighten the
1994 \e[1m9.1. Registration
\e[0m
1996 The basic principle of registration is simple. If a user is not
1997 registered by the sysop, then they have read-only access to the
1998 cluster. The only thing they can actually send is a talk or a message
1999 to the sysop. In order for them to be able to spot, send announces or
2000 talks etc the sysop must register them with the
\e[4mset/register
\e[24m command,
2009 The user g0vgs can now fully use the cluster. In order to enable
2010 registration, you can issue the command ...
2012 set/var $main::reqreg = 1
2016 Any users that are not registered will now see the motd_nor file
2017 rather than the motd file as discussed in the Information, files and
2018 useful programs section.
2021 Entering this line at the prompt will only last for the time the
2022 cluster is running of course and would not be present on a restart.
2023 To make the change permanent, add the above line to
2024 /spider/scripts/startup. To read more on the startup file, see the
2025 section on Information, files and useful programs.
2028 To unregister a user use
\e[4munset/register
\e[24m and to show the list of
2029 registered users, use the command
\e[4mshow/register
\e[24m.
2032 \e[1m9.2. Passwords
\e[0m
2034 At the moment, passwords only affect users who login to a DXSpider
2035 cluster node via telnet. If a user requires a password, they can
2036 either set it themselves or have the sysop enter it for them by using
2037 the
\e[4mset/password
\e[24m command. Any users who already have passwords, such
2038 as remote sysops, will be asked for their passwords automatically by
2039 the cluster. Using passwords in this way means that the user has a
2040 choice on whether to have a password or not. To force the use of
2041 passwords at login, issue the command ...
2045 set/var $main::passwdreq = 1
2049 at the cluster prompt. This can also be added to the
2050 /spider/scripts/startup file as above to make the change permanent.
2053 Of course, if you do this you will have to assign a password for each
2054 of your users. If you were asking them to register, it is anticipated
2055 that you would ask them to send you a message both to ask to be
2056 registered and to give you the password they wish to use.
2059 Should a user forget their password, it can be reset by the sysop by
2060 first removing the existing password and then setting a new one like
2065 unset/password g0vgs
2066 set/password g0vgs new_password
2074 \e[1m10.1. CVS from a Linux platform
\e[0m
2076 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2077 is held at Sourceforge. This means that it is possible to update your
2078 DXSpider installation to the latest sources by using a few simple
2079 commands. A graphical interface to CVS for Windows is explained in
2083 Please be aware that if you update your system using CVS, it is
2084 possible that you could be running code that is very beta and not
2085 fully tested. There is a possibility that it could be unstable.
2088 I am of course assuming that you have a machine with both DXSpider and
2089 Internet access running.
2092 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2093 ENTIRE SPIDER TREE!!
2096 Assuming you are connected to the Internet, you need to login to the
2097 CVS repository and then update your Spider source. There are several
2098 steps which are listed below ...
2101 First login as the user
\e[4msysop
\e[24m. Next you need to connect to the CVS
2102 repository. You do this with the command below ...
2105 cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dxspider login
2109 You will get a password prompt. Simply hit return here and your
2110 machine should return to a normal linux prompt.
2113 What happens next depends on whether you have an existing installation
2114 that you want to update with the latest and greatest or whether you
2115 just want to see what is there and/or run it on a new machine for
2118 If you are installing Spider from CVS then change directory to
2121 If you are wanting to update Spider then cd to /tmp
2124 The next step will create a brand new 'spider' directory in your
2128 cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dxspider co spider
2132 This command is all on one line.
2135 Hopefully your screen should show you downloading files. The -z3
2136 simply compresses the download to improve speed. When this has
2137 finished, you will have exactly the same as if you had untarred a full
2138 tarball PLUS some extra directories and files that CVS needs to do the
2140 Now if you are doing a new installation, that's it. Carry on as if
2141 you have just downloaded and untarred the lastest tarball.
2144 If you want to upgrade your current installation then do this ...
2148 tar cvfz /tmp/s.tgz spider
2150 tar xvfzp /tmp/s.tgz
2154 This is assuming you downloaded to the /tmp directory of course.
2157 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2158 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2161 Remember to recompile the C client (cd /spider/src; make)
2164 At this point the files have been upgraded. You can (usually) restart
2165 the cluster in your own time. However, if you attempt to use any new
2166 commands or features expect it to be fatal! At least your cluster
2167 will have been restarted then so it will be too late to worry about
2171 Now the magic part! From now on when you want to update, simply
2172 connect to the Internet and then, as the user
\e[4msysop
\e[24m ...
2181 and your files will be updated. As above, remember to recompile the
2182 "C" client if it has been updated (CVS will tell you) and restart if
2183 any of the perl scripts have been altered or added, again, CVS will
2187 You will find any changes documented in the /spider/Changes file.
2190 \e[1m10.2. CVS from a Windows platform
\e[0m
2192 After the initial setup, an update to your DXSpider software is no
2193 more than a couple of clicks away. This section is intended to
2194 explain and illustrate the use of the WinCVS application to update
2195 your DXSpider software. The current stable version of WinCVS is Ver.
2196 1.2. You can get this software at:
2198 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2200 Pick your download mirror and then install WinCVS after the download
2204 In this next section I have included a series of links to .jpg files
2205 to take advantage of the picture and 1000 words equivalency. The .jpg
2206 files are in the C:\spider\html directory. If someone using a Linux
2207 system is reading this section from boredom, the files are in
2208 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2209 of gcvs and do your updates graphically as opposed to from the command
2210 line. The following descriptions are almost identical between WinCvs
2211 and gcvs. The following screen shots have duplicate links, depending
2212 upon whether you are viewing this information under the Windows or
2213 Linux operating system.
2215 When WinCVS is installed, running, and you are connected to the
2216 internet, the initial screen looks like:
2220 If you want, you can also look at these .jpg files with another viewer
2221 that might provide some better clarity to the image. On the left is
2222 the directory tree for your hard disk. Notice that the spider
2223 directory has a gray highlight.
2225 To start configuring WinCVS, click on Admin at the top of the screen
2226 and then Preferences. This should get you:
2230 In the top line for CVSROOT, enter:
2233 anonymous@cvs.sourceforge.net:/cvsroot/dxspider login
2240 "passwd" file on the cvs server
2244 for Authentication on the General tab.
2246 Next, move to the right to the Ports tab.
2250 In here, check the box on the second line down for the "pserver" port.
2251 Enter a port number of 2401.
2253 Finally, go to the WinCvs tab all the way to the right.
2257 Enter Notepad as the viewer to open files. For the HOME folder, put
2258 "C:\spider" and click OK because the configuration is now complete.
2260 You are now ready to upgrade your copy of DXSpider. Click on the
2261 greyed Spider folder shown in the directory tree on the left of the
2262 WinCVS display. Two things should happen. The Spider folder will be
2263 selected and the greyed-out arrow located just below the word Query in
2264 the top line will turn to solid green.
2266 For anyone using gcvs under Linux, the green arrow is located on the
2267 extreme left of the display, under the word File. A gcvs screen looks
2272 Click on the now green arrow to start the download process. An Update
2273 Settings box will be displayed to which you can simply say OK.
2277 For future reference, the Update Settings box is the place where you
2278 can enter information to revert to a prior version of DXSpider.
2279 Information on reverting to a Before Date is contained in the WinCVS
2282 After a short period of time, a series of file names will scroll by in
2283 the lower pane of the WinCVS window. Eventually you should see
2286 *****CVS exited normally with code 0*****
2290 appear in the lower pane. You're done. The updated files are in
2291 place ready for you to stop and then restart your DXSpider. After the
2292 restart, you're running with the latest version of DXSpider.
2296 To paraphrase from the CVS section... Now the magic part! From now on
2297 when you want to update, simply connect to the Internet and start
2301 Click on the greyed-out Spider directory in the left screen
2302 Click on the green down arrow
2303 Click OK on the Update Settings dialog box
2304 Restart your Spider software
2308 \e[1m11. The DXSpider Command Reference
\e[0m
2310 \e[1m11.1. accept (0)
\e[0m
2312 \e[1maccept
\e[22mSet a filter to accept something
2314 Create a filter to accept somethingThere are 2 types of filter, accept
2315 and reject. See HELP FILTERING for moreinfo.
2317 \e[1m11.2. accept/announce <call> [input] [0-9] <pattern> (8)
\e[0m
2319 \e[1maccept/announce <call> [input] [0-9] <pattern>
\e[22mAnnounce filter sysop
2322 This version allows a sysop to set a filter for a callsign as well as
2323 thedefault for nodes and users eg:-
2326 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2330 \e[1m11.3. accept/announce [0-9] <pattern> (0)
\e[0m
2332 \e[1maccept/announce [0-9] <pattern>
\e[22mSet an 'accept' filter line for
2335 Create an 'accept this announce' line for a filter. An accept filter
2336 line means that if the announce matches this filter it ispassed onto
2337 the user. See HELP FILTERING for more info. Please read thisto
2338 understand how filters work - it will save a lot of grief later on.You
2339 can use any of the following things in this line:-
2342 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)
2349 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)
2363 acc/ann by_state va,nh,ri,nh
2367 You can use the tag 'all' to accept everything eg:
2374 but this probably for advanced users...
2376 \e[1m11.4. accept/route <call> [0-9] <pattern> (8)
\e[0m
2378 \e[1maccept/route <call> [0-9] <pattern>
\e[22mSet an 'accept' filter line for
2381 Create an 'accept this routing PC Protocol' line for a filter. An
2382 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2383 filter it is passed thru that interface. See HELP FILTERING for more
2384 info. Please read thisto understand how filters work - it will save a
2385 lot of grief later on.You can use any of the following things in this
2389 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
2396 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2400 you can now use 'by' as a synonym for 'call' so:
2403 by = call by_dxcc = call_dxcc
2407 and so onYou can use the tag 'all' to accept everything eg:
2414 \e[1m11.5. accept/spots <call> [input] [0-9] <pattern> (8)
\e[0m
2416 \e[1maccept/spots <call> [input] [0-9] <pattern>
\e[22mSpot filter sysop version
2418 This version allows a sysop to set a filter for a callsign as well as
2419 thedefault for nodes and users eg:-
2422 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2426 accept/spot user_default by G,M,2
2430 \e[1m11.6. accept/spots [0-9] <pattern> (0)
\e[0m
2432 \e[1maccept/spots [0-9] <pattern>
\e[22mSet an 'accept' filter line for spots
2434 Create an 'accept this spot' line for a filter. An accept filter line
2435 means that if the spot matches this filter it ispassed onto the user.
2436 See HELP FILTERING for more info. Please read thisto understand how
2437 filters work - it will save a lot of grief later on.You can use any of
2438 the following things in this line:-
2441 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>
2445 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2449 You can use the tag 'all' to accept everything, eg:
2459 acc/spots by_state VA,NH,RI,MA,ME
2463 but this probably for advanced users...
2465 \e[1m11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
\e[0m
2467 \e[1maccept/wcy <call> [input] [0-9] <pattern>
\e[22mWCY filter sysop version
2469 This version allows a sysop to set a filter for a callsign as well as
2470 thedefault for nodes and users eg:-
2473 accept/wcy node_default all set/hops node_default 10
2477 \e[1m11.8. accept/wcy [0-9] <pattern> (0)
\e[0m
2479 \e[1maccept/wcy [0-9] <pattern>
\e[22mset an 'accept' WCY filter
2481 It is unlikely that you will want to do this, but if you do then you
2482 canfilter on the following fields:-
2485 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>
2489 There are no examples because WCY Broadcasts only come from one place
2490 andyou either want them or not (see UNSET/WCY if you don't want
2491 them).This command is really provided for future use.See HELP FILTER
2494 \e[1m11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
\e[0m
2496 \e[1maccept/wwv <call> [input] [0-9] <pattern>
\e[22mWWV filter sysop version
2498 This version allows a sysop to set a filter for a callsign as well as
2499 thedefault for nodes and users eg:-
2502 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2506 accept/wwv user_default by W,K
2510 \e[1m11.10. accept/wwv [0-9] <pattern> (0)
\e[0m
2512 \e[1maccept/wwv [0-9] <pattern>
\e[22mset an 'accept' WWV filter
2514 It is unlikely that you will want to do this, but if you do then you
2515 canfilter on the following fields:-
2518 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>
2525 accept/wwv by_zone 4
2529 is probably the only useful thing to do (which will only show WWV
2530 broadcastsby stations in the US).See HELP FILTER for information.
2532 \e[1m11.11. announce <text> (0)
\e[0m
2534 \e[1mannounce <text>
\e[22mSend an announcement to LOCAL users only
2536 <text> is the text of the announcement you wish to broadcast
2538 \e[1m11.12. announce full <text> (0)
\e[0m
2540 \e[1mannounce full <text>
\e[22mSend an announcement cluster wide
2542 This will send your announcement cluster wide
2544 \e[1m11.13. announce sysop <text> (5)
\e[0m
2546 \e[1mannounce sysop <text>
\e[22mSend an announcement to Sysops only
2549 \e[1m11.14. apropos <string> (0)
\e[0m
2551 \e[1mapropos <string>
\e[22mSearch help database for <string>
2553 Search the help database for <string> (it isn't case sensitive), and
2554 printthe names of all the commands that may be relevant.
2556 \e[1m11.15. blank [<string>] [<nn>] (0)
\e[0m
2558 \e[1mblank [<string>] [<nn>]
\e[22mPrint nn (default 1) blank lines (or strings)
2560 In its basic form this command prints one or more blank lines. However
2561 ifyou pass it a string it will replicate the string for the width of
2562 the screen (default 80) and then print that one or more times, so:
2569 prints two blank lines
2576 prints a row of - characters once.
2583 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2584 script file and you can print a maximumof 9 lines.
2586 \e[1m11.16. bye (0)
\e[0m
2588 \e[1mbye
\e[22mExit from the cluster
2590 This will disconnect you from the cluster
2592 \e[1m11.17. catchup <node call> all|[<msgno> ...] (5)
\e[0m
2594 \e[1mcatchup <node call> all|[<msgno> ...]
\e[22mMark a message as sent
2597 \e[1m11.18. chat <group> <text> (0)
\e[0m
2599 \e[1mchat <group> <text>
\e[22mChat or Conference to a group
2601 It is now possible to JOIN a group and have network wide conferencing
2602 to thatgroup. DXSpider does not (and probably will not) implement the
2603 AK1A conference mode as this seems very limiting, is hardly used and
2604 doesn't seemto work too well anyway.This system uses the existing ANN
2605 system and is compatible with both otherDXSpider nodes and AK1A
2606 clusters (they use ANN/<group>). You can be a member of as many
2607 "groups" as you want. To join a group type:-
2610 JOIN FOC (where FOC is the group name)
2614 To leave a group type:-
2621 You can see which groups you are in by typing:-
2628 and you can see whether your mate is in the group, if he connects to
2629 thesame node as you, by typing:-
2636 To send a message to a group type:-
2639 CHAT FOC hello everyone
2646 CH #9000 hello I am back
2649 See also JOIN, LEAVE, SHOW/CHAT
2651 \e[1m11.19. clear/announce <callsign> [input] [0-9|all] (8)
\e[0m
2653 \e[1mclear/announce <callsign> [input] [0-9|all]
\e[22mClear a announce filter
2656 A sysop can clear an input or normal output filter for a user or
2657 thenode_default or user_default.
2659 \e[1m11.20. clear/announce [1|all] (0)
\e[0m
2661 \e[1mclear/announce [1|all]
\e[22mClear a announce filter line
2663 This command allows you to clear (remove) a line in a annouce filter
2664 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2667 \e[1m11.21. clear/route <callsign> [input] [0-9|all] (8)
\e[0m
2669 \e[1mclear/route <callsign> [input] [0-9|all]
\e[22mClear a route filter line
2671 A sysop can clear an input or normal output filter for a user or
2672 thenode_default or user_default.
2674 \e[1m11.22. clear/route [1|all] (0)
\e[0m
2676 \e[1mclear/route [1|all]
\e[22mClear a route filter line
2678 This command allows you to clear (remove) a line in a route filter or
2679 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2682 \e[1m11.23. clear/spots <callsign> [input] [0-9|all] (8)
\e[0m
2684 \e[1mclear/spots <callsign> [input] [0-9|all]
\e[22mClear a spot filter line
2686 A sysop can clear an input or normal output filter for a user or
2687 thenode_default or user_default.
2689 \e[1m11.24. clear/spots [0-9|all] (0)
\e[0m
2691 \e[1mclear/spots [0-9|all]
\e[22mClear a spot filter line
2693 This command allows you to clear (remove) a line in a spot filter or
2694 to remove the whole filter.If you have a filter:-
2697 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2708 you will be left with:-
2711 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2722 the filter will be completely removed.
2724 \e[1m11.25. clear/wcy <callsign> [input] [0-9|all] (8)
\e[0m
2726 \e[1mclear/wcy <callsign> [input] [0-9|all]
\e[22mClear a WCY filter line
2728 A sysop can clear an input or normal output filter for a user or
2729 thenode_default or user_default.
2731 \e[1m11.26. clear/wcy [1|all] (0)
\e[0m
2733 \e[1mclear/wcy [1|all]
\e[22mClear a WCY filter line
2735 This command allows you to clear (remove) a line in a WCY filter or to
2736 remove the whole filter.see CLEAR/SPOTS for a more detailed
2739 \e[1m11.27. clear/wwv <callsign> [input] [0-9|all] (8)
\e[0m
2741 \e[1mclear/wwv <callsign> [input] [0-9|all]
\e[22mClear a WWV filter line
2743 A sysop can clear an input or normal output filter for a user or
2744 thenode_default or user_default.
2746 \e[1m11.28. clear/wwv [1|all] (0)
\e[0m
2748 \e[1mclear/wwv [1|all]
\e[22mClear a WWV filter line
2750 This command allows you to clear (remove) a line in a WWV filter or to
2751 remove the whole filter.see CLEAR/SPOTS for a more detailed
2754 \e[1m11.29. connect <callsign> (5)
\e[0m
2756 \e[1mconnect <callsign>
\e[22mStart a connection to another DX Cluster
2758 Start a connection process that will culminate in a new connection to
2759 theDX cluster <callsign>. This process creates a new 'client' process
2760 which willuse the script in /spider/connect/<callsign> to effect the
2761 'chat' exchangenecessary to traverse the network(s) to logon to the
2764 \e[1m11.30. dbavail (0)
\e[0m
2766 \e[1mdbavail
\e[22mShow a list of all the Databases in the system
2768 Title says it all really, this command lists all the databases
2769 definedin the system. It is also aliased to SHOW/COMMAND.
2771 \e[1m11.31. dbcreate <name> (9)
\e[0m
2773 \e[1mdbcreate <name>
\e[22mCreate a database entry
2776 \e[1m11.32. dbcreate <name> chain <name> [<name>..] (9)
\e[0m
2778 \e[1mdbcreate <name> chain <name> [<name>..]
\e[22mCreate a chained database
2781 \e[1m11.33. dbcreate <name> cmd <dxspider command> (9)
\e[0m
2783 \e[1mdbcreate <name> cmd <dxspider command>
\e[22mmake a local command available
2786 DBCREATE allows you to define a database in the system. It doesn't
2787 actuallycreate anything, just defines it.The databases that are
2788 created are simple DB_File hash databases, they are therefore already
2789 'indexed'.You can define a local database with the first form of the
2797 You can also chain databases with the addition of the 'chain' keyword.
2798 This will search each database one after the other. A typical example
2802 DBCREATE sdx_qsl chain sql_ad
2806 No checking is done to see if the any of the chained databases exist,
2807 infact it is usually better to do the above staement first then do
2808 each ofthe chained databases.Databases can exist offsite. To define a
2809 database that lives on another node do:
2812 DBCREATE buckmaster remote gb7dxc
2816 Remote databases cannot be chained; however, the last database in a a
2817 chain can be a remote database eg:
2820 DBCREATE qsl chain gb7dxc
2824 To see what databases have been defined do:
2827 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2831 It would be normal for you to add an entry into your local Aliases
2832 fileto allow people to use the 'SHOW/<dbname>' style syntax. So you
2833 wouldneed to add a line like:-
2836 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
2847 to work as they may be used to.You can also make local commands avail-
2848 able as 'pseudo' databases. Youcan therefore make spider special com-
2849 mands available as a database. Iimagine that this will be primarily
2850 useful for remote access from legacy nodes. For example:-
2853 DBCREATE dxqsl cmd show/dxqsl
2857 You also use one of these databases in a chain. This may be useful
2858 locally. See DBIMPORT for the importing of existing AK1A format data
2859 to databases.See DBSHOW for generic database enquiry
2861 \e[1m11.34. dbcreate <name> remote <node> (9)
\e[0m
2863 \e[1mdbcreate <name> remote <node>
\e[22mCreate a remote database entry
2866 \e[1m11.35. dbimport <dbname> <filename> (9)
\e[0m
2868 \e[1mdbimport <dbname> <filename>
\e[22mImport AK1A data into a database
2870 If you want to import or update data in bulk to a database you can
2871 usethis command. It will either create or update entries into an
2872 existingdatabase. For example:-
2875 DBIMPORT oblast /tmp/OBLAST.FUL
2879 will import the standard OBLAST database that comes with AK1A into
2880 theoblast database held locally.
2882 \e[1m11.36. dbremove <dbname> (9)
\e[0m
2884 \e[1mdbremove <dbname>
\e[22mDelete a database
2886 DBREMOVE will completely remove a database entry and also delete any
2887 datafile that is associated with it. There is no warning, no comeback,
2888 no safety net. For example:
2895 will remove the oblast database from the system and it will also
2896 removethe associated datafile.I repeat:There is no warning, no come-
2897 back, no safety net.You have been warned.
2899 \e[1m11.37. dbshow <dbname> <key> (0)
\e[0m
2901 \e[1mdbshow <dbname> <key>
\e[22mDisplay an entry, if it exists, in a database
2903 This is the generic user interface to the database to the database
2904 system.It is expected that the sysop will add an entry to the local
2905 Aliases fileso that users can use the more familiar AK1A style of
2913 but if he hasn't and the database really does exist (use DBAVAIL
2914 orSHOW/COMMAND to find out) you can do the same thing with:
2921 \e[1m11.38. debug (9)
\e[0m
2923 \e[1mdebug
\e[22mSet the cluster program into debug mode
2925 Executing this command will only have an effect if you are running the
2926 clusterin debug mode i.e.
2933 It will interrupt the cluster just after the debug command has fin-
2936 \e[1m11.39. delete/usdb <callsign> ... (9)
\e[0m
2938 \e[1mdelete/usdb <callsign> ...
\e[22mDelete this user from the US State Database
2940 This command will completely remove a one or more callsignsfrom the US
2941 States database.There is NO SECOND CHANCE.It goes without saying that
2942 you should use this command CAREFULLY!Note that these callsign may be
2943 re-instated by any weekly updates from the FCC.
2945 \e[1m11.40. delete/user <callsign> ... (9)
\e[0m
2947 \e[1mdelete/user <callsign> ...
\e[22mDelete this user from the User Database
2949 This command will completely remove a one or more users from the
2950 database.There is NO SECOND CHANCE.It goes without saying that you
2951 should use this command CAREFULLY!
2953 \e[1m11.41. demonstrate <call> <command> (9)
\e[0m
2955 \e[1mdemonstrate <call> <command>
\e[22mDemonstrate a command to another user
2957 This command is provided so that sysops can demonstrate commands to
2958 other users. It runs a command as though that user had typed it in
2959 andthen sends the output to that user, together with the command that
2963 DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
2967 Note that this command is similar to SPOOF and will have the same
2968 sideeffects. Commands are run at the privilege of the user which is
2969 beingdemonstrated to.
2971 \e[1m11.42. directory (0)
\e[0m
2973 \e[1mdirectory
\e[22mList messages
2977 \e[1m11.43. directory <from>-<to> (0)
\e[0m
2979 \e[1mdirectory <from>-<to>
\e[22mList messages <from> message <to> message
2981 List the messages in the messages directory.If there is a 'p' one
2982 space after the message number then it is a personal message. If there
2983 is a '-' between the message number and the'p' then this indicates
2984 that the message has been read.You can use shell escape characters
2985 such as '*' and '?' in the <call>fields.You can combine some of the
2986 various directory commands together eg:-
2996 DIR SUBJECT IOTA 200-250
3000 You can abbreviate all the commands to one letter and use ak1a syn-
3004 DIR/T G1* 10 DIR/S QSL 10-100 5
3008 \e[1m11.44. directory <nn> (0)
\e[0m
3010 \e[1mdirectory <nn>
\e[22mList last <nn> messages
3013 \e[1m11.45. directory all (0)
\e[0m
3015 \e[1mdirectory all
\e[22mList all messages
3018 \e[1m11.46. directory from <call> (0)
\e[0m
3020 \e[1mdirectory from <call>
\e[22mList all messages from <call>
3023 \e[1m11.47. directory new (0)
\e[0m
3025 \e[1mdirectory new
\e[22mList all new messages
3028 \e[1m11.48. directory own (0)
\e[0m
3030 \e[1mdirectory own
\e[22mList your own messages
3033 \e[1m11.49. directory subject <string> (0)
\e[0m
3035 \e[1mdirectory subject <string>
\e[22mList all messages with <string> in subject
3038 \e[1m11.50. directory to <call> (0)
\e[0m
3040 \e[1mdirectory to <call>
\e[22mList all messages to <call>
3042 \e[1m11.51. directory- (5)
\e[0m
3044 \e[1mdirectory-
\e[0m
3046 Sysops can see all users' messages.
3048 \e[1m11.52. disconnect <call> [<call> ...] (8)
\e[0m
3050 \e[1mdisconnect <call> [<call> ...]
\e[22mDisconnect a user or cluster
3052 Disconnect any <call> connected locally
3054 \e[1m11.53. dx [by <call>] <freq> <call> <remarks> (0)
\e[0m
3056 \e[1mdx [by <call>] <freq> <call> <remarks>
\e[22mSend a DX spot
3058 This is how you send a DX Spot to other users. You can, in fact,
3059 nowenter the <freq> and the <call> either way round.
3062 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
3066 will all give the same result. You can add some remarks to the endof
3067 the command and they will be added to the spot.
3070 DX FR0G 144600 this is a test
3074 You can credit someone else by saying:-
3077 DX by G1TLH FR0G 144.600 he isn't on the cluster
3081 The <freq> is compared against the available bands set up in the clus-
3082 ter. See SHOW/BANDS for more information.
3084 \e[1m11.54. echo <line> (0)
\e[0m
3086 \e[1mecho <line>
\e[22mEcho the line to the output
3088 This command is useful in scripts and so forth for printing theline
3089 that you give to the command to the output. You can use thisin
3090 user_default scripts and the SAVE command for titling and so forthThe
3091 script will interpret certain standard "escape" sequences as follows:-
3094 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
3098 So the following example:-
3101 echo GB7DJK is a dxcluster
3108 GB7DJK is a dxcluster
3112 on the output. You don't need a \n on the end of the line you want to
3113 send.A more complex example:-
3116 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
3123 GB7DJK g1tlh Dirk g3xvf Richard
3129 \e[1m11.55. export <msgno> <filename> (9)
\e[0m
3131 \e[1mexport <msgno> <filename>
\e[22mExport a message to a file
3133 Export a message to a file. This command can only be executed on a
3134 localconsole with a fully privileged user. The file produced will be
3135 in a formready to be imported back into the cluster by placing it in
3136 the import directory (/spider/msg/import).This command cannot
3137 overwrite an existing file. This is to provide some measure of
3138 security. Any files written will owned by the same user as the main
3139 cluster, otherwise you can put the new files anywhere the cluster
3140 canaccess. For example:-
3147 \e[1m11.56. export_users [<filename>] (9)
\e[0m
3149 \e[1mexport_users [<filename>]
\e[22mExport the users database to ascii
3151 Export the users database to a file in ascii format. If no filenameis
3152 given then it will export the file to /spider/data/user_asc.If the
3153 file already exists it will be renamed to <filename>.o. In factup to 5
3154 generations of the file can be kept each one with an extra 'o' on
3155 thesuffix. BE WARNED: this will write to any file you have write
3156 access to. No check ismade on the filename (if any) that you specify.
3158 \e[1m11.57. filtering... (0)
\e[0m
3160 \e[1mfiltering...
\e[22mFiltering things in DXSpider
3162 There are a number of things you can filter in the DXSpider system.
3163 Theyall use the same general mechanism.In general terms you can create
3164 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
3165 You do this using, for example:-
3168 accept/spots ..... reject/spots .....
3172 where ..... are the specific commands for that type of filter. There-
3173 are filters for spots, wwv, announce, wcy and (for sysops)connects.
3174 See each different accept or reject command reference formore
3175 details.There is also a command to clear out one or more lines in a
3176 filter andone to show you what you have set. They are:-
3179 clear/spots 1 clear/spots all
3190 There is clear/xxxx command for each type of filter.For now we are
3191 going to use spots for the examples, but you can applythe principles
3192 to all types of filter.There are two main types of filter 'accept' or
3193 'reject'; which you usedepends entirely on how you look at the world
3194 and what is leastwriting to achieve what you want. Each filter has 10
3195 lines (of anylength) which are tried in order. If a line matches then
3196 the actionyou have specified is taken (ie reject means ignore it and
3197 acceptmeans gimme it).The important thing to remember is that if you
3198 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
3199 instance)) then ifa spot comes in that doesn't match any of the lines
3200 then you will getit BUT if you specify an 'accept' filter then any
3201 spots that don'tmatch are dumped. For example if I have a one line
3205 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
3209 then automatically you will ONLY get VHF spots from or to CQ zones
3210 1415 and 16. If you set a reject filter like:
3213 reject/spots on hf/cw
3217 Then you will get everything EXCEPT HF CW spots, If you am interested
3218 in IOTAand will work it even on CW then you could say:-
3221 reject/spots on hf/cw and not info iota
3225 But in that case you might only be interested in iota and say:-
3228 accept/spots not on hf/cw or info iota
3232 which is exactly the same. You should choose one or the other untilyou
3233 are confortable with the way it works. Yes, you can mix them(actually
3234 you can have an accept AND a reject on the same line) butdon't try
3235 this at home until you can analyse the results that you getwithout
3236 ringing up the sysop for help.Another useful addition now is filtering
3238 accept/spots by_state VA,NH,RI,ME
3242 You can arrange your filter lines into logical units, either for
3243 yourown understanding or simply convenience. I have one set fre-
3247 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
3251 What this does is to ignore all HF CW spots (being a class B I
3252 can'tread any CW and couldn't possibly be interested in HF :-) and
3253 alsorejects any spots on VHF which don't either originate or spot
3254 someonein Europe.This is an exmaple where you would use the line num-
3255 ber (1 and 2 inthis case), if you leave the digit out, the system
3256 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
3257 out if you want, it is implied. You canuse any number of brackets to
3258 make the 'expression' as you wantit. There are things called prece-
3259 dence rules working here which meanthat you will NEED brackets in a
3260 situation like line 2 because,without it, will assume:-
3263 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
3267 annoying, but that is the way it is. If you use OR - usebrackets.
3268 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
3269 by_zone'.If you want to alter your filter you can just redefine one or
3270 morelines of it or clear out one line. For example:-
3273 reject/spots 1 on hf/ssb
3284 To remove the filter in its entirty:-
3291 There are similar CLEAR commands for the other filters:-
3294 clear/announce clear/wcy clear/wwv
3298 ADVANCED USERS:-Once you are happy with the results you get, you may
3299 like to experiment. my example that filters hf/cw spots and accepts
3300 vhf/uhf spots from EUcan be written with a mixed filter, eg:
3304 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)
3308 each filter slot actually has a 'reject' slot and an 'accept'slot. The
3309 reject slot is executed BEFORE the accept slot.It was mentioned ear-
3310 lier that after a reject test that doesn't match,the default for fol-
3311 lowing tests is 'accept', the reverse is true for'accept'. In the
3312 example what happens is that the reject is executedfirst, any non
3313 hf/cw spot is passed to the accept line, which letsthru everything
3314 else on HF.The next filter line lets through just VHF/UHF spots from
3317 \e[1m11.58. forward/latlong <node_call> (8)
\e[0m
3319 \e[1mforward/latlong <node_call>
\e[22mSend latitude and longitude information to
3322 This command sends all the latitude and longitude information that
3323 yourcluster is holding against callsigns. One advantage of recieving
3324 thisinformation is that more locator information is held by you.
3325 Thismeans that more locators are given on the DX line assuming you
3326 haveSET/DXGRID enabled. This could be a LOT of information though,
3327 soit is not recommended on slow links.
3329 \e[1m11.59. forward/opernam <call> (1)
\e[0m
3331 \e[1mforward/opernam <call>
\e[22mSend out information on this <call> to all
3334 This command sends out any information held in the user file which can
3335 be broadcast in PC41 protocol packets. This information is Name, QTH,
3336 Locationand Homenode. PC41s are only sent for the information that is
3339 \e[1m11.60. help (0)
\e[0m
3341 \e[1mhelp
\e[22mThe HELP Command
3343 HELP is available for a number of commands. The syntax is:-
3350 Where <cmd> is the name of the command you want help on.All commands
3351 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3352 can be shortened to AN and so on.Look at the APROPOS <string> command
3353 which will search the help databasefor the <string> you specify and
3354 give you a list of likely commandsto look at with HELP.
3356 \e[1m11.61. init <node> (5)
\e[0m
3358 \e[1minit <node>
\e[22mRe-initialise a link to an AK1A compatible node
3360 This command attempts to re-initialise a link to a (usually) AK1A
3361 nodethat has got confused, usually by a protocol loop of some kind. It
3362 maywork - but you usually will be better off simply disconnecting it
3363 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3364 <yournode>).Best of luck - you will need it.
3366 \e[1m11.62. join <group> (0)
\e[0m
3368 \e[1mjoin <group>
\e[22mJoin a chat or conference group
3370 JOIN allows you to join a network wide conference group. To join
3371 agroup (called FOC in this case) type:-
3378 See also CHAT, LEAVE, SHOW/CHAT
3380 \e[1m11.63. kill (5)
\e[0m
3384 As a sysop you can kill any message on the system.
3386 \e[1m11.64. kill <from msgno>-<to msgno> (0)
\e[0m
3388 \e[1mkill <from msgno>-<to msgno>
\e[22mDelete a range of messages
3391 \e[1m11.65. kill <from>-<to> (5)
\e[0m
3393 \e[1mkill <from>-<to>
\e[22mRemove a range of messages from the system
3396 \e[1m11.66. kill <msgno> [<msgno..] (0)
\e[0m
3398 \e[1mkill <msgno> [<msgno..]
\e[22mDelete a message from the local system
3401 \e[1m11.67. kill <msgno> [<msgno> ...] (0)
\e[0m
3403 \e[1mkill <msgno> [<msgno> ...]
\e[22mRemove or erase a message from the system
3405 You can get rid of any message to or originating from your callsign
3406 using this command. You can remove more than one message at a time.
3408 \e[1m11.68. kill expunge <msgno> [<msgno..] (6)
\e[0m
3410 \e[1mkill expunge <msgno> [<msgno..]
\e[22mExpunge a message
3412 Deleting a message using the normal KILL commands only marks that
3413 messagefor deletion. The actual deletion only happens later (usually
3414 two days later).The KILL EXPUNGE command causes the message to be
3415 truly deleted more or lessimmediately.It otherwise is used in the same
3416 way as the KILL command.
3418 \e[1m11.69. kill from <call> (5)
\e[0m
3420 \e[1mkill from <call>
\e[22mRemove all messages from a callsign
3423 \e[1m11.70. kill full <msgno> [<msgno..] (5)
\e[0m
3425 \e[1mkill full <msgno> [<msgno..]
\e[22mDelete a message from the whole cluster
3427 Delete a message from the local system. You will only be able todelete
3428 messages that you have originated or been sent (unless you arethe
3436 Will delete all the messages that you own between msgnos 1234 and
3444 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3451 will delete all messages to g1tlh.
3458 will delete a message (usually a 'bulletin') from the whole cluster
3459 system. This uses the subject field, so any messages that have exactly
3460 thesame subject will be deleted. Beware!
3462 \e[1m11.71. kill full <msgno> [<msgno] (5)
\e[0m
3464 \e[1mkill full <msgno> [<msgno]
\e[22mRemove a message from the entire cluster
3466 Remove this message from the entire cluster system as well as your
3469 \e[1m11.72. kill to <call> (5)
\e[0m
3471 \e[1mkill to <call>
\e[22mRemove all messages to a callsign
3474 \e[1m11.73. kill from <regex> (0)
\e[0m
3476 \e[1mkill from <regex>
\e[22mDelete messages FROM a callsign or pattern
3479 \e[1m11.74. kill to <regex> (0)
\e[0m
3481 \e[1mkill to <regex>
\e[22mDelete messages TO a callsign or pattern
3484 \e[1m11.75. leave <group> (0)
\e[0m
3486 \e[1mleave <group>
\e[22mLeave a chat or conference group
3488 LEAVE allows you to leave a network wide conference group. To leave
3489 agroup (called FOC in this case) type:-
3496 See also CHAT, JOIN, SHOW/CHAT
3498 \e[1m11.76. links (0)
\e[0m
3500 \e[1mlinks
\e[22mShow which nodes is physically connected
3502 This is a quick listing that shows which links are connected andsome
3503 information about them. See WHO for a list of all connections.
3505 \e[1m11.77. load/aliases (9)
\e[0m
3507 \e[1mload/aliases
\e[22mReload the command alias table
3509 Reload the /spider/cmd/Aliases file after you have editted it. Youwill
3510 need to do this if you change this file whilst the cluster isrunning
3511 in order for the changes to take effect.
3513 \e[1m11.78. load/badmsg (9)
\e[0m
3515 \e[1mload/badmsg
\e[22mReload the bad msg table
3517 Reload the /spider/msg/badmsg.pl file if you have changed it manually
3518 whilstthe cluster is running. This table contains a number of perl
3519 regular expressions which are searched for in the fields targetted of
3520 each message. If any of them match then that message is immediately
3523 \e[1m11.79. load/badwords (9)
\e[0m
3525 \e[1mload/badwords
\e[22mReload the bad words table
3527 Reload the /spider/data/badwords file if you have changed it manually
3528 whilstthe cluster is running. This file contains a list of words
3529 which, if foundon certain text portions of PC protocol, will cause
3530 those protocol framesto be rejected. It will all put out a message if
3531 any of these words areused on the announce, dx and talk commands. The
3532 words can be one or more on a line, lines starting with '#' are
3535 \e[1m11.80. load/bands (9)
\e[0m
3537 \e[1mload/bands
\e[22mReload the band limits table
3539 Reload the /spider/data/bands.pl file if you have changed it manually
3540 whilstthe cluster is running.
3542 \e[1m11.81. load/cmd_cache (9)
\e[0m
3544 \e[1mload/cmd_cache
\e[22mReload the automatic command cache
3546 Normally, if you change a command file in the cmd or local_cmd tree
3547 itwill automatially be picked up by the cluster program. Sometimes
3548 itcan get confused if you are doing a lot of moving commands about
3549 ordelete a command in the local_cmd tree and want to use the normal
3550 oneagain. Execute this command to reset everything back to the state
3551 itwas just after a cluster restart.
3553 \e[1m11.82. load/forward (9)
\e[0m
3555 \e[1mload/forward
\e[22mReload the msg forwarding routing table
3557 Reload the /spider/msg/forward.pl file if you have changed itmanually
3558 whilst the cluster is running.
3560 \e[1m11.83. load/keps (5)
\e[0m
3562 \e[1mload/keps
\e[22mLoad new keps data
3566 \e[1m11.84. load/keps [nn] (5)
\e[0m
3568 \e[1mload/keps [nn]
\e[22mLoad new keps data from message
3570 If there is no message number then reload the current Keps data
3571 fromthe Keps.pm data file. You create this file by running
3574 /spider/perl/convkeps.pl <filename>
3578 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3579 there is a message number, then it will take the message, runcon-
3580 vkeps.pl on it and then load the data, all in one step.These messages
3581 are sent to ALL by GB7DJK (and others) from time to time.
3583 \e[1m11.85. load/messages (9)
\e[0m
3585 \e[1mload/messages
\e[22mReload the system messages file
3587 If you change the /spider/perl/Messages file (usually
3588 whilstfiddling/writing new commands) you can have them take effect
3589 during acluster session by executing this command. You need to do this
3590 if getsomething like :-unknown message 'xxxx' in lang 'en'
3592 \e[1m11.86. load/prefixes (9)
\e[0m
3594 \e[1mload/prefixes
\e[22mReload the prefix table
3596 Reload the /spider/data/prefix_data.pl file if you have changed
3597 itmanually whilst the cluster is running.
3599 \e[1m11.87. merge <node> [<no spots>/<no wwv>] (5)
\e[0m
3601 \e[1mmerge <node> [<no spots>/<no wwv>]
\e[22mAsk for the latest spots and WWV
3603 MERGE allows you to bring your spot and wwv database up to date. By
3604 defaultit will request the last 10 spots and 5 WWVs from the node you
3605 select. The node must be connected locally.You can request any number
3606 of spots or wwv and although they will be appendedto your databases
3607 they will not duplicate any that have recently been added (the last 2
3608 days for spots and last month for WWV data).
3610 \e[1m11.88. msg <cmd> <msgno> [data ... ] (9)
\e[0m
3612 \e[1mmsg <cmd> <msgno> [data ... ]
\e[22mAlter various message parameters
3614 Alter message parameters like To, From, Subject, whether private or
3615 bulletinor return receipt (RR) is required or whether to keep this
3616 message from timingout.
3619 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
3623 You can look at the status of a message by using:-
3630 This will display more information on the message than DIR does.
3632 \e[1m11.89. pc <call> <text> (8)
\e[0m
3634 \e[1mpc <call> <text>
\e[22mSend arbitrary text to a connected callsign
3636 Send some arbitrary text to a locally connected callsign. Noprocessing
3637 is done on the text. This command allows you to send PCProtocol to
3638 unstick things if problems arise (messages get stucketc). eg:-
3641 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3648 pc G1TLH Try doing that properly!!!
3652 Send any text you like to the callsign requested. This is used mainly
3653 to sendPC protocol to connected nodes either for testing or to unstick
3654 things. You can also use in the same way as a talk command to a con-
3655 nected user butwithout any processing, added of "from <blah> to <blah"
3658 \e[1m11.90. ping <node call> (1)
\e[0m
3660 \e[1mping <node call>
\e[22mCheck the link quality between nodes
3662 This command allows you to send a frame to another cluster node onthe
3663 network and get a return frame. The time it takes to do thisis a good
3664 indication of the quality of the link. The actual timeit takes is
3665 output to the console in seconds.Any visible cluster node can be
3668 \e[1m11.91. rcmd <node call> <cmd> (1)
\e[0m
3670 \e[1mrcmd <node call> <cmd>
\e[22mSend a command to another DX Cluster
3672 This command allows you to send nearly any command to another DX
3673 Clusternode that is connected to the system. Whether you get any
3674 output is dependant on a) whether the other system knowsthat the node
3675 callsign of this cluster is in fact a node b) whether theother system
3676 is allowing RCMDs from this node and c) whether you havepermission to
3677 send this command at all.
3679 \e[1m11.92. read (0)
\e[0m
3681 \e[1mread
\e[22mRead the next unread personal message addressed to you
3684 \e[1m11.93. read <msgno> (0)
\e[0m
3686 \e[1mread <msgno>
\e[22mRead the specified message
3688 You can read any messages that are sent as 'non-personal' and also
3689 anymessage either sent by or sent to your callsign.
3691 \e[1m11.94. read- (5)
\e[0m
3695 As a sysop you may read any message on the system
3698 \e[1m11.95. reject (0)
\e[0m
3700 \e[1mreject
\e[22mSet a filter to reject something
3702 Create a filter to reject somethingThere are 2 types of filter, accept
3703 and reject. See HELP FILTERING for moreinfo.
3705 \e[1m11.96. reject/announce <call> [input] [0-9] <pattern> (8)
\e[0m
3707 \e[1mreject/announce <call> [input] [0-9] <pattern>
\e[22mAnnounce filter sysop
3710 This version allows a sysop to set a filter for a callsign as well as
3711 thedefault for nodes and users eg:-
3714 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3718 \e[1m11.97. reject/announce [0-9] <pattern> (0)
\e[0m
3720 \e[1mreject/announce [0-9] <pattern>
\e[22mSet a 'reject' filter line for
3723 Create an 'reject this announce' line for a filter. A reject filter
3724 line means that if the announce matches this filter it ispassed onto
3725 the user. See HELP FILTERING for more info. Please read thisto
3726 understand how filters work - it will save a lot of grief later on.You
3727 can use any of the following things in this line:-
3730 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)
3737 rej/ann by_zone 14,15,16 and not by G,M,2
3741 You can use the tag 'all' to reject everything eg:
3748 but this probably for advanced users...
3750 \e[1m11.98. reject/route <call> [0-9] <pattern> (8)
\e[0m
3752 \e[1mreject/route <call> [0-9] <pattern>
\e[22mSet an 'reject' filter line for
3755 Create an 'reject this routing PC Protocol' line for a filter. An
3756 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3757 filter it is NOT passed thru that interface. See HELP FILTERING for
3758 more info. Please read this to understand how filters work - it will
3759 save a lot of grief later on.You can use any of the following things
3763 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
3770 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3774 You can use the tag 'all' to reject everything eg:
3777 rej/route all (equiv to [very] restricted mode)
3781 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3783 \e[1m11.99. reject/spots <call> [input] [0-9] <pattern> (8)
\e[0m
3785 \e[1mreject/spots <call> [input] [0-9] <pattern>
\e[22mSpot filter sysop version
3787 This version allows a sysop to set a filter for a callsign as well as
3788 thedefault for nodes and users eg:-
3791 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3795 reject/spot user_default by G,M,2
3799 \e[1m11.100. reject/spots [0-9] <pattern> (0)
\e[0m
3801 \e[1mreject/spots [0-9] <pattern>
\e[22mSet a 'reject' filter line for spots
3803 Create a 'reject this spot' line for a filter. A reject filter line
3804 means that if the spot matches this filter it isdumped (not passed
3805 on). See HELP FILTERING for more info. Please read thisto understand
3806 how filters work - it will save a lot of grief later on.You can use
3807 any of the following things in this line:-
3810 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>
3814 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3818 You can use the tag 'all' to reject everything eg:
3824 but this probably for advanced users...
3826 \e[1m11.101. reject/wcy <call> [input] [0-9] <pattern> (8)
\e[0m
3828 \e[1mreject/wcy <call> [input] [0-9] <pattern>
\e[22mWCY filter sysop version
3830 This version allows a sysop to set a filter for a callsign as well as
3831 thedefault for nodes and users eg:-
3834 reject/wcy gb7djk all
3838 \e[1m11.102. reject/wcy [0-9] <pattern> (0)
\e[0m
3840 \e[1mreject/wcy [0-9] <pattern>
\e[22mset a 'reject' WCY filter
3842 It is unlikely that you will want to do this, but if you do then you
3843 canfilter on the following fields:-
3846 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>
3850 There are no examples because WCY Broadcasts only come from one place
3851 andyou either want them or not (see UNSET/WCY if you don't want
3852 them).This command is really provided for future use.See HELP FILTER
3855 \e[1m11.103. reject/wwv <call> [input] [0-9] <pattern> (8)
\e[0m
3857 \e[1mreject/wwv <call> [input] [0-9] <pattern>
\e[22mWWV filter sysop version
3859 This version allows a sysop to set a filter for a callsign as well as
3860 thedefault for nodes and users eg:-
3863 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3867 reject/wwv user_default by W
3871 \e[1m11.104. reject/wwv [0-9] <pattern> (0)
\e[0m
3873 \e[1mreject/wwv [0-9] <pattern>
\e[22mset a 'reject' WWV filter
3875 It is unlikely that you will want to do this, but if you do then you
3876 canfilter on the following fields:-
3879 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>
3886 reject/wwv by_zone 14,15,16
3890 is probably the only useful thing to do (which will only show WWV
3891 broadcastsby stations in the US).See HELP FILTER for information.
3893 \e[1m11.105. reply (0)
\e[0m
3895 \e[1mreply
\e[22mReply (privately) to the last message that you have read
3898 \e[1m11.106. reply <msgno> (0)
\e[0m
3900 \e[1mreply <msgno>
\e[22mReply (privately) to the specified message
3903 \e[1m11.107. reply b <msgno> (0)
\e[0m
3905 \e[1mreply b <msgno>
\e[22mReply as a Bulletin to the specified message
3908 \e[1m11.108. reply noprivate <msgno> (0)
\e[0m
3910 \e[1mreply noprivate <msgno>
\e[22mReply as a Bulletin to the specified message
3913 \e[1m11.109. reply rr <msgno> (0)
\e[0m
3915 \e[1mreply rr <msgno>
\e[22mReply to the specified message with read receipt
3917 You can reply to a message and the subject will automatically
3918 have"Re:" inserted in front of it, if it isn't already present.You can
3919 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3920 that you can use with the SEND command (see SENDfor further details)
3922 \e[1m11.110. save [-d -t -a] <filename> "<cmd>" [...] (9)
\e[0m
3924 \e[1msave [-d -t -a] <filename> "<cmd>" [...]
\e[22mSave command output to a file
3926 This sysop only cammand allows you to save the output of one or
3927 morecommands to a file. For example:-
3930 save /spider/packclus/dxstats show/dxstat
3934 will save the output of the normal command "show/dxstat" to the
3935 file"dxstats" in the files area.You can have some extra flags to the
3936 save which will either date stamp or time stamp or both the filename
3940 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
3944 The -a flag means append to the file instead of overwriting it.You can
3945 have more than one command on the line, to do this you MUSTenclose
3946 each command in double quotes (") eg:-
3949 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
3955 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
3959 You can only write into places that the cluster has permission for
3960 (whichis that of the "sysop" user [which had BETTER NOT BE "root"]),
3961 you will need to create any directories you want to put stuff in
3962 beforehand as well.It is likely that you will want to run these com-
3963 mands in a crontab type situation. You would do that something like:-
3966 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
3970 Note that you still enclose each command with (") characters but you
3971 mustenclose the entire save command in (') characters. Now in fact,
3972 this can be varied if you know what you are doing. See theadmin manual
3975 \e[1m11.111. send <call> [<call> ...] (0)
\e[0m
3977 \e[1msend <call> [<call> ...]
\e[22mSend a message to one or more callsigns
3980 \e[1m11.112. send copy <msgno> <call> (0)
\e[0m
3982 \e[1msend copy <msgno> <call>
\e[22mSend a copy of a message to someone
3985 \e[1m11.113. send noprivate <call> (0)
\e[0m
3987 \e[1msend noprivate <call>
\e[22mSend a message to all stations
3989 All the SEND commands will create a message which will be sent either
3990 toan individual callsign or to one of the 'bulletin' addresses. SEND
3991 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3992 will mark the message as personal and send it to the cluster node
3993 thatthat callsign is connected to. If the <call> you have specified is
3994 in facta known bulletin category on your node (eg: ALL) then the
3995 message shouldautomatically become a bulletin.You can have more than
3996 one callsign in all of the SEND commands.You can have multiple
3997 qualifiers so that you can have for example:-
4000 SEND RR COPY 123 PRIVATE G1TLH G0RDI
4004 which should send a copy of message 123 to G1TLH and G0RDI and you
4005 willreceive a read receipt when they have read the message.SB is an
4006 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
4007 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
4008 tionally this should be no longer than 29 characters for compatibil-
4009 ity. Most modern clustersoftware should accept more.You will now be
4010 prompted to start entering your text. You finish the message by enter-
4011 ing '/EX' on a new line. For instance:
4014 ... bye then Jim 73 Dirk /ex
4018 If you have started a message and you don't want to keep it then you-
4019 can abandon the message with '/ABORT' on a new line, like:-
4022 line 1 line 2 oh I just can't be bothered with this /abort
4026 If you abort the message it will NOT be sent.When you are entering the
4027 text of your message, most normal output (suchas DX announcements and
4028 so on are suppressed and stored for latter display(upto 20 such lines
4029 are stored, as new ones come along, so the oldestlines are
4030 dropped).Also, you can enter normal commands commands (and get the
4031 output immediately) whilst in the middle of a message. You do this by
4032 typingthe command preceeded by a '/' character on a new line, so:-
4035 /dx g1tlh 144010 strong signal
4039 Will issue a dx annoucement to the rest of the cluster. Also, you can
4040 add the output of a command to your message by preceeding the command
4048 This will show YOU the output from SH/VHFTABLE and also store it in
4049 themessage. You can carry on with the message until you are ready to
4052 \e[1m11.114. send private <call> (0)
\e[0m
4054 \e[1msend private <call>
\e[22mSend a personal message
4057 \e[1m11.115. send rr <call> (0)
\e[0m
4059 \e[1msend rr <call>
\e[22mSend a message and ask for a read receipt
4062 \e[1m11.116. set/address <your address> (0)
\e[0m
4064 \e[1mset/address <your address>
\e[22mRecord your postal address
4067 \e[1m11.117. set/announce (0)
\e[0m
4069 \e[1mset/announce
\e[22mAllow announce messages to come out on your terminal
4072 \e[1m11.118. set/anntalk (0)
\e[0m
4074 \e[1mset/anntalk
\e[22mAllow talk like announce messages on your terminal
4077 \e[1m11.119. set/arcluster <call> [<call>..] (5)
\e[0m
4079 \e[1mset/arcluster <call> [<call>..]
\e[22mMake the callsign an AR-Cluster node
4083 \e[1m11.120. set/baddx <call>.. (8)
\e[0m
4085 \e[1mset/baddx <call>..
\e[22mStop callsigns in a dx spot being propagated
4088 \e[1m11.121. set/badnode <call>.. (8)
\e[0m
4090 \e[1mset/badnode <call>..
\e[22mStop spots from this node being propagated
4093 \e[1m11.122. set/badspotter <call>.. (8)
\e[0m
4095 \e[1mset/badspotter <call>..
\e[22mStop spots from this callsign being propagated
4098 \e[1m11.123. set/badword <word>.. (8)
\e[0m
4100 \e[1mset/badword <word>..
\e[22mStop things with this word being propagated
4103 \e[1m11.124. set/bbs <call> [<call>..] (5)
\e[0m
4105 \e[1mset/bbs <call> [<call>..]
\e[22mMake the callsign a BBS
4108 \e[1m11.125. set/beep (0)
\e[0m
4110 \e[1mset/beep
\e[22mAdd a beep to DX and other messages on your terminal
4113 \e[1m11.126. set/clx <call> [<call>..] (5)
\e[0m
4115 \e[1mset/clx <call> [<call>..]
\e[22mMake the callsign an CLX node
4118 \e[1m11.127. set/debug <name> (9)
\e[0m
4120 \e[1mset/debug <name>
\e[22mAdd a debug level to the debug set
4123 \e[1m11.128. set/dx (0)
\e[0m
4125 \e[1mset/dx
\e[22mAllow DX messages to come out on your terminal
4128 \e[1m11.129. set/dxcq (0)
\e[0m
4130 \e[1mset/dxcq
\e[22mShow CQ Zones on the end of DX announcements
4133 \e[1m11.130. set/dxgrid (0)
\e[0m
4135 \e[1mset/dxgrid
\e[22mAllow QRA Grid Squares on the end of DX announcements
4138 \e[1m11.131. set/dxitu (0)
\e[0m
4140 \e[1mset/dxitu
\e[22mShow ITU Zones on the end of DX announcements
4143 \e[1m11.132. set/dxnet <call> [<call>..] (5)
\e[0m
4145 \e[1mset/dxnet <call> [<call>..]
\e[22mMake the callsign an DXNet node
4149 \e[1m11.133. set/echo (0)
\e[0m
4151 \e[1mset/echo
\e[22mMake the cluster echo your input
4154 \e[1m11.134. set/email <email> ... (0)
\e[0m
4156 \e[1mset/email <email> ...
\e[22mSet email address(es) and forward your personals
4159 \e[1m11.135. set/here (0)
\e[0m
4161 \e[1mset/here
\e[22mTell the system you are present at your terminal
4164 \e[1m11.136. set/homenode <node> (0)
\e[0m
4166 \e[1mset/homenode <node>
\e[22mSet your normal cluster callsign
4168 Tell the cluster system where you normally connect to. Any Messages
4169 sentto you will normally find their way there should you not be
4177 \e[1m11.137. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
\e[0m
4179 \e[1mset/hops <call> ann|spots|route|wwv|wcy <n>
\e[22mSet hop count
4182 \e[1m11.138. set/isolate (9)
\e[0m
4184 \e[1mset/isolate
\e[22mIsolate a node from the rest of the network
4186 Connect a node to your system in such a way that you are a full
4187 protocolmember of its network and can see all spots on it, but nothing
4188 either leaksout from it nor goes back into from the rest of the nodes
4189 connected to you.You can potentially connect several nodes in this
4192 \e[1m11.139. set/language <lang> (0)
\e[0m
4194 \e[1mset/language <lang>
\e[22mSet the language you want to use
4196 You can select the language that you want the cluster to use.
4197 Currentlythe languages available are en (English), de (German), es
4198 (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and
4201 \e[1m11.140. set/location <lat & long> (0)
\e[0m
4203 \e[1mset/location <lat & long>
\e[22mSet your latitude and longitude
4206 \e[1m11.141. set/lockout <call> (9)
\e[0m
4208 \e[1mset/lockout <call>
\e[22mStop a callsign connecting to the cluster
4212 \e[1m11.142. set/logininfo (0)
\e[0m
4214 \e[1mset/logininfo
\e[22mInform when a station logs in locally
4217 \e[1m11.143. set/name <your name> (0)
\e[0m
4219 \e[1mset/name <your name>
\e[22mSet your name
4221 Tell the system what your name is eg:-
4228 \e[1m11.144. set/node <call> [<call>..] (5)
\e[0m
4230 \e[1mset/node <call> [<call>..]
\e[22mMake the callsign an AK1A cluster
4232 Tell the system that the call(s) are to be treated as AK1A cluster
4233 andfed PC Protocol rather normal user commands.
4235 \e[1m11.145. set/obscount <count> <call> (8)
\e[0m
4237 \e[1mset/obscount <count> <call>
\e[22mSet the 'pump-up' obscelence PING counter
4239 From 1.35 onwards neighbouring nodes are pinged at regular intervals
4240 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
4241 'pump-up'counter which is decremented on every outgoing ping and then
4242 reset tothe 'obscount' value on every incoming ping. The default value
4243 of thisparameter is 2. What this means is that a neighbouring node
4244 will be pinged twice at (default) 300 second intervals and if no reply
4245 has been heard just beforewhat would be the third attempt, that node
4246 is disconnected.If a ping is heard then the obscount is reset to the
4247 full value. Usingdefault values, if a node has not responded to a ping
4248 within 15 minutes,it is disconnected.You can set this parameter
4249 between 1 and 9.It is STRONGLY recommended that you don't change the
4252 \e[1m11.146. set/page <lines per page> (0)
\e[0m
4254 \e[1mset/page <lines per page>
\e[22mSet the lines per page
4256 Tell the system how many lines you wish on a page when the number of
4257 lineof output from a command is more than this. The default is 20.
4258 Setting itexplicitly to 0 will disable paging.
4261 SET/PAGE 30 SET/PAGE 0
4265 The setting is stored in your user profile.
4267 \e[1m11.147. set/password (0)
\e[0m
4269 \e[1mset/password
\e[22mSet your own password
4271 This command only works for a 'telnet' user (currently). It willonly
4272 work if you have a password already set. This initial passwordcan only
4273 be set by the sysop.When you execute this command it will ask you for
4274 your old password,then ask you to type in your new password twice (to
4275 make sure youget it right). You may or may not see the data echoed on
4276 the screenas you type, depending on the type of telnet client you
4279 \e[1m11.148. set/password <callsign> <string> (9)
\e[0m
4281 \e[1mset/password <callsign> <string>
\e[22mSet a users password
4283 The password for a user can only be set by a full sysop. The stringcan
4284 contain any characters. The way this field is used depends on context.
4285 If it is being used inthe SYSOP command context then you are offered 5
4286 random numbers and youhave to supply the corresponding letters. This
4287 is now mainly for ax25connections.If it is being used on incoming
4288 telnet connections then, if a passwordis set or the:
4291 set/var $main::passwdreq = 1
4295 command is executed in the startup script, then a password prompt
4296 isgiven after the normal 'login: ' prompt.
4298 \e[1m11.149. set/pinginterval <time> <nodecall> (9)
\e[0m
4300 \e[1mset/pinginterval <time> <nodecall>
\e[22mSet ping time to neighbouring nodes
4302 As from release 1.35 all neighbouring nodes are pinged at regular
4303 intervalsin order to determine the rolling quality of the link and, in
4304 future, toaffect routing decisions. The default interval is 300 secs
4305 or 5 minutes.You can use this command to set a different interval.
4306 Please don't. But if you do the value you enter is treated as minutes
4307 up 30 and secondsfor numbers greater than that.This is used also to
4308 help determine when a link is down at the far end(as certain cluster
4309 software doesn't always notice), see SET/OBSCOUNTfor more
4310 information.If you must change it (and it may be useful for internet
4311 connected nodeson dynamic IP addresses that go away after a set time
4312 of usage) the timecan be specified as:-
4315 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
4319 Please be aware that this causes traffic to occur on the link, setting
4320 this value too low may annoy your neighbours beyond the point of
4321 endurance!You can switch this off by setting it to 0.
4323 \e[1m11.150. set/privilege <n> <call> [<call..] (9)
\e[0m
4325 \e[1mset/privilege <n> <call> [<call..]
\e[22mSet privilege level on a call
4327 Set the privilege level on a callsign. The privilege levels that
4328 pertainto commands are as default:-
4331 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.
4335 If you are a sysop and you come in as a normal user on a remote con-
4336 nectionyour privilege will automatically be set to 0.
4338 \e[1m11.151. set/prompt <string> (0)
\e[0m
4340 \e[1mset/prompt <string>
\e[22mSet your prompt to <string>
4343 \e[1m11.152. set/qra <locator> (0)
\e[0m
4345 \e[1mset/qra <locator>
\e[22mSet your QRA Grid locator
4347 Tell the system what your QRA (or Maidenhead) locator is. If you have
4348 notdone a SET/LOCATION then your latitude and longitude will be set
4349 roughlycorrectly (assuming your locator is correct ;-). For example:-
4356 \e[1m11.153. set/qth <your qth> (0)
\e[0m
4358 \e[1mset/qth <your qth>
\e[22mSet your QTH
4360 Tell the system where you are. For example:-
4363 SET/QTH East Dereham, Norfolk
4367 \e[1m11.154. set/register <call> ... (9)
\e[0m
4369 \e[1mset/register <call> ...
\e[22mMark a user as registered
4372 \e[1m11.155. set/spider <call> [<call>..] (5)
\e[0m
4374 \e[1mset/spider <call> [<call>..]
\e[22mMake the callsign an DXSpider node
4376 Tell the system that the call(s) are to be treated as DXSpider node
4377 andfed new style DX Protocol rather normal user commands.
4379 \e[1m11.156. set/sys_location <lat & long> (9)
\e[0m
4381 \e[1mset/sys_location <lat & long>
\e[22mSet your cluster latitude and longitude
4383 In order to get accurate headings and such like you must tell the
4384 systemwhat your latitude and longitude is. If you have not yet done a
4385 SET/QRAthen this command will set your QRA locator for you. For
4389 SET/LOCATION 52 22 N 0 57 E
4393 \e[1m11.157. set/sys_qra <locator> (9)
\e[0m
4395 \e[1mset/sys_qra <locator>
\e[22mSet your cluster QRA Grid locator
4398 \e[1m11.158. set/talk (0)
\e[0m
4400 \e[1mset/talk
\e[22mAllow TALK messages to come out on your terminal
4404 \e[1m11.159. set/usdb <call> <state> <city> (9)
\e[0m
4406 \e[1mset/usdb <call> <state> <city>
\e[22madd/update a US DB callsign
4408 This command allows you to add or alter a callsign in the US
4409 statedatabase. Use with extreme caution. Anything you do here will
4410 beoverwritten by any weekly updates that affect this callsign
4413 set/usdb g1tlh nh downtown rindge
4417 see also DELETE/USDB
4419 \e[1m11.160. set/usstate (0)
\e[0m
4421 \e[1mset/usstate
\e[22mAllow US State info on the end of DX announcements
4424 \e[1m11.161. set/wcy (0)
\e[0m
4426 \e[1mset/wcy
\e[22mAllow WCY messages to come out on your terminal
4429 \e[1m11.162. set/wwv (0)
\e[0m
4431 \e[1mset/wwv
\e[22mAllow WWV messages to come out on your terminal
4434 \e[1m11.163. set/wx (0)
\e[0m
4436 \e[1mset/wx
\e[22mAllow WX messages to come out on your terminal
4439 \e[1m11.164. show/baddx (1)
\e[0m
4441 \e[1mshow/baddx
\e[22mShow all the bad dx calls in the system
4443 Display all the bad dx callsigns in the system, see SET/BADDXfor more
4446 \e[1m11.165. show/badnode (1)
\e[0m
4448 \e[1mshow/badnode
\e[22mShow all the bad nodes in the system
4450 Display all the bad node callsigns in the system, see SET/BADNODEfor
4453 \e[1m11.166. show/badspotter (1)
\e[0m
4455 \e[1mshow/badspotter
\e[22mShow all the bad spotters in the system
4457 Display all the bad spotter's callsigns in the system, see
4458 SET/BADSPOTTERfor more information.
4460 \e[1m11.167. show/badword (1)
\e[0m
4462 \e[1mshow/badword
\e[22mShow all the bad words in the system
4464 Display all the bad words in the system, see SET/BADWORDfor more
4469 \e[1m11.168. show/chat [<group>] [<lines>] (0)
\e[0m
4471 \e[1mshow/chat [<group>] [<lines>]
\e[22mShow any chat or conferencing
4473 This command allows you to see any chat or conferencing that has
4474 occurred whilst you were away. SHOW/CHAT on its own will show data
4475 forall groups. If you use a group name then it will show only chat
4478 \e[1m11.169. show/configuration [<node>] (0)
\e[0m
4480 \e[1mshow/configuration [<node>]
\e[22mShow all the nodes and users visible
4482 This command allows you to see all the users that can be seenand the
4483 nodes to which they are connected.This command is normally abbreviated
4484 to: sh/cNormally, the list returned will be just for the nodes from
4485 your country (because the list otherwise will be very long).
4492 will produce a complete list of all nodes. BE WARNED: the list that is
4493 returned can be VERY longIt is possible to supply a node or part of a
4494 prefix and you will get a list of the users for that node or list of
4495 nodes starting withthat prefix.
4506 \e[1m11.170. show/configuration/node (0)
\e[0m
4508 \e[1mshow/configuration/node
\e[22mShow all the nodes connected locally
4510 Show all the nodes connected to this node.
4512 \e[1m11.171. show/connect (1)
\e[0m
4514 \e[1mshow/connect
\e[22mShow all the active connections
4516 This command shows information on all the active connections known
4517 tothe node. This command gives slightly more information than WHO.
4519 \e[1m11.172. show/contest <year and month> (0)
\e[0m
4521 \e[1mshow/contest <year and month>
\e[22mShow all the contests for a month
4523 Show all known contests which are maintained at
4524 http://www.sk3bg.se/contest/for a particular month or year. The format
4525 is reasonably flexible.For example:-
4528 SH/CONTEST sep2003 SH/CONTEST 03 march
4532 \e[1m11.173. show/date [<prefix>|<callsign>] (0)
\e[0m
4534 \e[1mshow/date [<prefix>|<callsign>]
\e[22mShow the local time
4536 This is very nearly the same as SHOW/TIME, the only difference the
4537 formatof the date string if no arguments are given.If no prefixes or
4538 callsigns are given then this command returns the localtime and UTC as
4539 the computer has it right now. If you give some prefixesthen it will
4540 show UTC and UTC + the local offset (not including DST) atthe prefixes
4541 or callsigns that you specify.
4543 \e[1m11.174. show/db0sdx <callsign> (0)
\e[0m
4545 \e[1mshow/db0sdx <callsign>
\e[22mShow QSL infomation from DB0SDX database
4547 This command queries the DB0SDX QSL server on the internetand returns
4548 any information available for that callsign. This serviceis provided
4549 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
4552 \e[1m11.175. show/debug (9)
\e[0m
4554 \e[1mshow/debug
\e[22mShow what levels of debug information you are logging
4557 \e[1m11.176. show/dx (0)
\e[0m
4559 \e[1mshow/dx
\e[22mInterrogate the spot database
4561 If you just type SHOW/DX you will get the last so many spots(sysop
4562 configurable, but usually 10).In addition you can add any number of
4563 these commands in very nearlyany order to the basic SHOW/DX command,
4567 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>
4571 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
4575 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
4579 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
4583 info <text> - any spots containing <text> in the info or remarks
4587 by <call> - any spots spotted by <call> (spotter <call> is the same).
4591 qsl - this automatically looks for any qsl info on the call held in the spot database.
4595 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.
4599 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
4603 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
4607 You can also use this with the 'by' keyword so eg by W dxcc
4611 real or rt - Format the output the same as for real time spots. The formats are deliberately different (so you can tell one sort from the other). This is useful for some logging programs that can't cope with normal sh/dx output. An alias of SHOW/FDX is available.
4615 filter - Filter the spots, before output, with the user's spot filter. An alias of SHOW/MYDX is available.
4619 zone <zones> - look for spots in the cq zone (or zones) specified. zones are numbers separated by commas.
4623 by_zone <zones> - look for spots spotted by people in the cq zone specified.
4627 itu <itus> - look for spots in the itu zone (or zones) specified itu zones are numbers separated by commas.
4631 by_itu <itus> - look for spots spotted by people in the itu zone specified.
4635 state <list> - look for spots in the US state (or states) specified The list is two letter state codes separated by commas.
4639 by_state <list> - look for spots spotted by people in the US state specified.
4647 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 SH/DX zone 4,5,6 SH/DX by_zone 4,5,6 SH/DX state in,oh SH/DX by_state in,oh
4651 \e[1m11.177. show/dxcc <prefix> (0)
\e[0m
4653 \e[1mshow/dxcc <prefix>
\e[22mInterrogate the spot database by country
4655 This command takes the <prefix> (which can be a full or partial
4656 callsign if desired), looks up which internal country number it isand
4657 then displays all the spots as per SH/DX for that country.This is now
4658 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
4662 SH/DXCC G SH/DXCC W on 20m iota
4666 This can be done with the SHOW/DX command like this:-
4669 SH/DX dxcc g SH/DX dxcc w on 20m iota
4673 This is an alias for: SH/DX dxcc
4675 \e[1m11.178. show/dxqsl <callsign> (0)
\e[0m
4677 \e[1mshow/dxqsl <callsign>
\e[22mShow any QSL info gathered from spots
4679 The node collects information from the comment fields in spots
4680 (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a
4681 database.This command allows you to interrogate that database and if
4682 the callsignis found will display the manager(s) that people have
4683 spotted. This information is NOT reliable, but it is normally
4684 reasonably accurate ifit is spotted enough times.For example:-
4692 You can check the raw input spots yourself with:-
4699 This gives you more background information.
4701 \e[1m11.179. show/dxstats [days] [date] (0)
\e[0m
4703 \e[1mshow/dxstats [days] [date]
\e[22mShow the DX Statistics
4705 Show the total DX spots for the last <days> no of days (default is
4706 31), starting from a <date> (default: today).
4708 \e[1m11.180. show/fdx (0)
\e[0m
4710 \e[1mshow/fdx
\e[22mShow the DX data in realtime format.
4712 Normally SHOW/DX outputs spot data in a different format to
4713 therealtime data. This is a deliberate policy (so you can tell the
4714 difference between the two). Some logging programs cannot handlethis
4715 so SHOW/FDX outputs historical data in real time format.This is an
4716 alias for: SHOW/DX real
4718 \e[1m11.181. show/files [<filearea> [<string>]] (0)
\e[0m
4720 \e[1mshow/files [<filearea> [<string>]]
\e[22mList the contents of a filearea
4722 SHOW/FILES on its own will show you a list of the various
4723 fileareasavailable on the system. To see the contents of a particular
4731 where <filearea> is the name of the filearea you want to see the con-
4732 tents of.You can also use shell globbing characters like '*' and '?'
4733 in astring to see a selection of files in a filearea eg:-
4736 SH/FILES bulletins arld*
4740 See also TYPE - to see the contents of a file.
4742 \e[1m11.182. show/filter (0)
\e[0m
4744 \e[1mshow/filter
\e[22mShow the contents of all the filters you have set
4746 Show the contents of all the filters that are set. This command
4747 displaysall the filters set - for all the various categories.
4749 \e[1m11.183. show/hfstats [days] [date] (0)
\e[0m
4751 \e[1mshow/hfstats [days] [date]
\e[22mShow the HF DX Statistics
4754 Show the HF DX spots breakdown by band for the last <days> no of days
4755 (default is 31), starting from a <date> (default: today).
4757 \e[1m11.184. show/hftable [days] [date] [prefix ...] (0)
\e[0m
4759 \e[1mshow/hftable [days] [date] [prefix ...]
\e[22mShow the HF DX Spotter Table
4761 Show the HF DX Spotter table for the list of prefixes for the last
4762 <days> no of days (default is 31), starting from a <date> (default:
4763 today).If there are no prefixes then it will show the table for your
4764 country.Remember that some countries have more than one "DXCC country"
4765 in them(eg G :-), to show them (assuming you are not in G already
4766 which isspecially treated in the code) you must list all the relevant
4770 sh/hftable g gm gd gi gj gw gu
4774 Note that the prefixes are converted into country codes so you don't
4775 haveto list all possible prefixes for each country.If you want more or
4776 less days than the default simply include thenumber you require:-
4783 If you want to start at a different day, simply add the date in some
4787 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4791 This will show the stats for your DXCC for that CQWW contest weekend.
4792 You can specify either prefixes or full callsigns (so you can see how
4793 youdid against all your mates). You can also say 'all' which will then
4794 printthe worldwide statistics.
4801 \e[1m11.185. show/hops <call> [ann|spots|route|wcy|wwv] (8)
\e[0m
4803 \e[1mshow/hops <call> [ann|spots|route|wcy|wwv]
\e[22mShow the hop counts for a
4806 This command shows the hop counts set up for a node. You can
4807 specifywhich category you want to see. If you leave the category out
4808 then all the categories will be listed.
4810 \e[1m11.186. show/isolate (1)
\e[0m
4812 \e[1mshow/isolate
\e[22mShow list of ISOLATED nodes
4815 \e[1m11.187. show/lockout <prefix>|all (9)
\e[0m
4817 \e[1mshow/lockout <prefix>|all
\e[22mShow the list of locked out or excluded
4819 \e[1m11.188. show/log [<callsign>] (8)
\e[0m
4821 \e[1mshow/log [<callsign>]
\e[22mShow excerpts from the system log
4823 This command outputs a short section of the system log. On its ownit
4824 will output a general logfile. With the optional callsign it willshow
4825 output from the log associated with that callsign.
4827 \e[1m11.189. show/moon [ndays] [<prefix>|<callsign>] (0)
\e[0m
4829 \e[1mshow/moon [ndays] [<prefix>|<callsign>]
\e[22mShow Moon rise and set times
4831 Show the Moon rise and set times for a (list of) prefixes or
4832 callsigns, together with the azimuth and elevation of the sun
4833 currently at thoselocations.If you don't specify any prefixes or
4834 callsigns, it will show the times foryour QTH (assuming you have set
4835 it with either SET/LOCATION or SET/QRA),together with the current
4836 azimuth and elevation.In addition, it will show the illuminated
4837 fraction of the moons disk.If all else fails it will show the Moonrise
4838 and set times for the nodethat you are connected to. For example:-
4841 SH/MOON SH/MOON G1TLH W5UN
4845 You can also use this command to see into the past or the future, soif
4846 you want to see yesterday's times then do:-
4853 or in three days time:-
4860 Upto 366 days can be checked both in the past and in the future.Please
4861 note that the rise and set times are given as the UT times of rise and
4862 set on the requested UT day.
4864 \e[1m11.190. show/muf <prefix> [<hours>][long] (0)
\e[0m
4866 \e[1mshow/muf <prefix> [<hours>][long]
\e[22mShow the likely propagation to a
4869 This command allow you to estimate the likelihood of you contactinga
4870 station with the prefix you have specified. The output assumes a
4871 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4872 0.15muV/10dB SINAD)The result predicts the most likely operating
4873 frequencies and signallevels for high frequency (shortwave) radio
4874 propagation paths onspecified days of the year and hours of the day.
4875 It is most useful forpaths between 250 km and 6000 km, but can be used
4876 with reduced accuracyfor paths shorter or longer than this.The command
4877 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4878 predict the MUF given the predicted flux, day of the year,hour of the
4879 day and geographic coordinates of the transmitter andreceiver. This
4880 routine is reasonably accurate for the purposes here,with a claimed
4881 RMS error of 3.8 MHz, but much smaller and less complexthan the
4882 programs used by major shortwave broadcasting organizations,such as
4883 the Voice of America.The command will display some header information
4884 detailing itsassumptions, together with the locations, latitude and
4885 longitudes andbearings. It will then show UTC (UT), local time at the
4886 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4887 the path(Zen) and the likely signal strengths. Then for each frequency
4888 for whichthe system thinks there is a likelihood of a circuit it
4889 prints a value.The value is currently a likely S meter reading based
4890 on the conventional6dB / S point scale. If the value has a '+'
4891 appended it means that it is1/2 an S point stronger. If the value is
4892 preceeded by an 'm' it means thatthere is likely to be much fading and
4893 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4894 will show the next two hours worth of data. Youcan specify anything up
4895 to 24 hours worth of data by appending the no ofhours required after
4896 the prefix. For example:-
4906 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
4910 indicating that you will have weak, fading circuits on top band and
4911 80m but usable signals on 40m (about S3).inputing:-
4918 will get you the above display, but with the next 24 hours worth
4922 SH/MUF W L 24 SH/MUF W 24 Long
4926 Gives you an estimate of the long path propagation characterics.
4927 Itshould be noted that the figures will probably not be very useful,
4928 norterrible accurate, but it is included for completeness.
4930 \e[1m11.191. show/mydx (0)
\e[0m
4932 \e[1mshow/mydx
\e[22mShow the DX data filtered with your spot filter.
4934 SHOW/DX potentially shows all the spots available in the system.
4935 UsingSHOW/MYDX will, instead, filter the availble spots using any spot
4936 filter that you have set, first. This command, together with
4937 ACCEPT/SPOT or REJECT/SPOT, will allowyou to customise the spots that
4938 you receive.So if you have said: ACC/SPOT on hfDoing a SHOW/MYDX will
4939 now only, ever, show HF spots. All the other options on SH/DX can
4942 \e[1m11.192. show/newconfiguration [<node>] (0)
\e[0m
4944 \e[1mshow/newconfiguration [<node>]
\e[22mShow all the nodes and users visible
4946 This command allows you to see all the users that can be seenand the
4947 nodes to which they are connected. This command produces essentially
4948 the same information as SHOW/CONFIGURATION except that it shows all
4949 the duplication ofany routes that might be present It also uses a
4950 different formatwhich may not take up quite as much space if you don't
4951 have anyloops.BE WARNED: the list that is returned can be VERY long
4953 \e[1m11.193. show/newconfiguration/node (0)
\e[0m
4955 \e[1mshow/newconfiguration/node
\e[22mShow all the nodes connected locally
4957 Show all the nodes connected to this node in the new format.
4959 \e[1m11.194. show/node [<callsign> ...] (1)
\e[0m
4961 \e[1mshow/node [<callsign> ...]
\e[22mShow the type and version number of nodes
4963 Show the type and version (if connected) of the nodes specified on
4964 thecommand line. If no callsigns are specified then a sorted list of
4965 allthe non-user callsigns known to the system will be displayed.
4967 \e[1m11.195. show/prefix <callsign> (0)
\e[0m
4969 \e[1mshow/prefix <callsign>
\e[22mInterrogate the prefix database
4971 This command takes the <callsign> (which can be a full or partial
4972 callsign or a prefix), looks up which internal country number it is
4973 and then displays all the relevant prefixes for that countrytogether
4974 with the internal country no, the CQ and ITU regions. See also
4977 \e[1m11.196. show/program (5)
\e[0m
4979 \e[1mshow/program
\e[22mShow the locations of all the included program modules
4981 Show the name and location where every program module was load from.
4982 Thisis useful for checking where you think you have loaded a .pm file
4985 \e[1m11.197. show/qra <lat> <long> (0)
\e[0m
4987 \e[1mshow/qra <lat> <long>
\e[22mConvert lat/long to a QRA Grid locator
4989 This is a multipurpose command that allows you either to calculate
4990 thedistance and bearing between two locators or (if only one locator
4991 isgiven on the command line) the distance and beraing from your
4992 stationto the locator. For example:-
4995 SH/QRA IO92QL SH/QRA JN06 IN73
4999 The first example will show the distance and bearing to the locator
5000 fromyourself, the second example will calculate the distance and bear-
5001 ing fromthe first locator to the second. You can use 4 or 6 character
5002 locators.It is also possible to convert a latitude and longitude to a
5003 locator by using this command with a latitude and longitude as an
5004 argument, forexample:-
5007 SH/QRA 52 41 N 0 58 E
5011 \e[1m11.198. show/qra <locator> [<locator>] (0)
\e[0m
5013 \e[1mshow/qra <locator> [<locator>]
\e[22mShow distance between QRA Grid locators
5016 \e[1m11.199. show/qrz <callsign> (0)
\e[0m
5018 \e[1mshow/qrz <callsign>
\e[22mShow any callbook details on a callsign
5020 This command queries the QRZ callbook server on the internetand
5021 returns any information available for that callsign. This serviceis
5022 provided for users of this software by http://www.qrz.com See also
5023 SHOW/WM7D for an alternative.
5025 \e[1m11.200. show/registered [<prefix>] (9)
\e[0m
5027 \e[1mshow/registered [<prefix>]
\e[22mShow the registered users
5030 \e[1m11.201. show/route <callsign> ... (0)
\e[0m
5032 \e[1mshow/route <callsign> ...
\e[22mShow the route to the callsign
5034 This command allows you to see to which node the callsigns specified
5035 areconnected. It is a sort of inverse sh/config.
5042 \e[1m11.202. show/satellite <name> [<hours> <interval>] (0)
\e[0m
5044 \e[1mshow/satellite <name> [<hours> <interval>]
\e[22mShow tracking data
5046 Show the tracking data from your location to the satellite of your
5047 choicefrom now on for the next few hours.If you use this command
5048 without a satellite name it will display a listof all the satellites
5049 known currently to the system. If you give a name then you can obtain
5050 tracking data of all the passesthat start and finish 5 degrees below
5051 the horizon. As default it willgive information for the next three
5052 hours for every five minute period.You can alter the number of hours
5053 and the step size, within certain limits. Each pass in a period is
5054 separated with a row of '-----' charactersSo for example:-
5057 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
5061 \e[1m11.203. show/station all [<regex>] (6)
\e[0m
5063 \e[1mshow/station all [<regex>]
\e[22mShow list of users in the system
5066 \e[1m11.204. show/station [<callsign> ..] (0)
\e[0m
5068 \e[1mshow/station [<callsign> ..]
\e[22mShow information about a callsign
5070 Show the information known about a callsign and whether (and
5071 where)that callsign is connected to the cluster.
5078 If no callsign is given then show the information for yourself.
5080 \e[1m11.205. show/sun [ndays] [<prefix>|<callsign>] (0)
\e[0m
5082 \e[1mshow/sun [ndays] [<prefix>|<callsign>]
\e[22mShow sun rise and set times
5084 Show the sun rise and set times for a (list of) prefixes or callsigns,
5085 together with the azimuth and elevation of the sun currently at
5086 thoselocations.If you don't specify any prefixes or callsigns, it will
5087 show the times foryour QTH (assuming you have set it with either
5088 SET/LOCATION or SET/QRA),together with the current azimuth and
5089 elevation.If all else fails it will show the sunrise and set times for
5090 the nodethat you are connected to. For example:-
5093 SH/SUN SH/SUN G1TLH K9CW ZS
5097 You can also use this command to see into the past or the future, soif
5098 you want to see yesterday's times then do:-
5105 or in three days time:-
5112 Upto 366 days can be checked both in the past and in the future.Please
5113 note that the rise and set times are given as the UT times of rise and
5114 set on the requested UT day.
5116 \e[1m11.206. show/time [<prefix>|<callsign>] (0)
\e[0m
5118 \e[1mshow/time [<prefix>|<callsign>]
\e[22mShow the local time
5120 If no prefixes or callsigns are given then this command returns the
5121 localtime and UTC as the computer has it right now. If you give some
5122 prefixesthen it will show UTC and UTC + the local offset (not
5123 including DST) atthe prefixes or callsigns that you specify.
5125 \e[1m11.207. show/usdb [call ..] (0)
\e[0m
5127 \e[1mshow/usdb [call ..]
\e[22mShow information held on the FCC Call database
5129 Show the City and State of a Callsign held on the FCC database ifhis
5130 is being run on this system, eg:-
5137 \e[1m11.208. show/vhfstats [days] [date] (0)
\e[0m
5139 \e[1mshow/vhfstats [days] [date]
\e[22mShow the VHF DX Statistics
5141 Show the VHF DX spots breakdown by band for the last <days> no of days
5142 (default is 31), starting from a date (default: today).
5145 \e[1m11.209. show/vhftable [days] [date] [prefix ...] (0)
\e[0m
5147 \e[1mshow/vhftable [days] [date] [prefix ...]
\e[22mShow the VHF DX Spotter Table
5149 Show the VHF DX Spotter table for the list of prefixes for the last
5150 <days> no of days (default is 31), starting from a date (default:
5151 today).If there are no prefixes then it will show the table for your
5152 country.Remember that some countries have more than one "DXCC country"
5153 in them(eg G :-), to show them (assuming you are not in G already
5154 which isspecially treated in the code) you must list all the relevant
5158 sh/vhftable g gm gd gi gj gw gu
5162 Note that the prefixes are converted into country codes so you don't
5163 haveto list all possible prefixes for each country.If you want more or
5164 less days than the default simply include thenumber you require:-
5171 If you want to start at a different day, simply add the date in some
5175 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
5179 This will show the stats for your DXCC for that CQWW contest weekend.
5180 You can specify either prefixes or full callsigns (so you can see how
5181 youdid against all your mates). You can also say 'all' which will then
5182 printthe worldwide statistics.
5189 \e[1m11.210. show/wcy (0)
\e[0m
5191 \e[1mshow/wcy
\e[22mShow last 10 WCY broadcasts
5194 \e[1m11.211. show/wcy <n> (0)
\e[0m
5196 \e[1mshow/wcy <n>
\e[22mShow last <n> WCY broadcasts
5198 Display the most recent WCY information that has been received by the
5201 \e[1m11.212. show/wm7d <callsign> (0)
\e[0m
5203 \e[1mshow/wm7d <callsign>
\e[22mShow callbook details on a US callsigns
5205 This command queries the WM7D callbook server on the internetand
5206 returns any information available for that US callsign. This serviceis
5207 provided for users of this software by http://www.wm7d.net.See also
5210 \e[1m11.213. show/wwv (0)
\e[0m
5212 \e[1mshow/wwv
\e[22mShow last 10 WWV broadcasts
5215 \e[1m11.214. show/wwv <n> (0)
\e[0m
5217 \e[1mshow/wwv <n>
\e[22mShow last <n> WWV broadcasts
5219 Display the most recent WWV information that has been received by the
5222 \e[1m11.215. shutdown (5)
\e[0m
5224 \e[1mshutdown
\e[22mShutdown the cluster
5226 Shutdown the cluster and disconnect all the users
5228 \e[1m11.216. spoof <call> <command> (9)
\e[0m
5230 \e[1mspoof <call> <command>
\e[22mDo a command as though you are another user
5232 This command is provided so that sysops can set a user's parameters
5233 withoutme having to write a special 'sysop' version for every user
5234 command. Itallows you to pretend that you are doing the command as the
5235 user you specify.eg:-
5238 SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
5242 \e[1m11.217. stat/channel [<callsign>] (5)
\e[0m
5244 \e[1mstat/channel [<callsign>]
\e[22mShow the status of a channel on the cluster
5246 Show the internal status of the channel object either for the channel
5247 that you are on or else for the callsign that you asked for.Only the
5248 fields that are defined (in perl term) will be displayed.
5250 \e[1m11.218. stat/db <dbname> (5)
\e[0m
5252 \e[1mstat/db <dbname>
\e[22mShow the status of a database
5254 Show the internal status of a database descriptor.Depending on your
5255 privilege level you will see more or less information. This command is
5256 unlikely to be of much use to anyone other than a sysop.
5258 \e[1m11.219. stat/msg (1)
\e[0m
5260 \e[1mstat/msg
\e[22mShow the status of the message system
5263 \e[1m11.220. stat/msg <msgno> (1)
\e[0m
5265 \e[1mstat/msg <msgno>
\e[22mShow the status of a message
5267 This command shows the internal status of a message and includes
5268 informationsuch as to whom it has been forwarded, its size, origin etc
5269 etc.If no message number is given then the status of the message
5270 system is displayed.
5274 \e[1m11.221. stat/route_node <callsign> (5)
\e[0m
5276 \e[1mstat/route_node <callsign>
\e[22mShow the data in a Route::Node object
5279 \e[1m11.222. stat/route_node all (5)
\e[0m
5281 \e[1mstat/route_node all
\e[22mShow list of all Route::Node objects
5284 \e[1m11.223. stat/route_user <callsign> (5)
\e[0m
5286 \e[1mstat/route_user <callsign>
\e[22mShow the data in a Route::User object
5289 \e[1m11.224. stat/route_user all (5)
\e[0m
5291 \e[1mstat/route_user all
\e[22mShow list of all Route::User objects
5294 \e[1m11.225. stat/user [<callsign>] (5)
\e[0m
5296 \e[1mstat/user [<callsign>]
\e[22mShow the full status of a user
5298 Shows the full contents of a user record including all the secret
5299 flagsand stuff.Only the fields that are defined (in perl term) will be
5302 \e[1m11.226. sysop (0)
\e[0m
5304 \e[1msysop
\e[22mRegain your privileges if you login remotely
5306 The system automatically reduces your privilege level to that of
5307 anormal user if you login in remotely. This command allows you
5308 toregain your normal privilege level. It uses the normal system:
5309 fivenumbers are returned that are indexes into the character array
5310 that isyour assigned password (see SET/PASSWORD). The indexes start
5311 fromzero.You are expected to return a string which contains the
5312 charactersrequired in the correct order. You may intersperse those
5313 characterswith others to obscure your reply for any watchers. For
5314 example (andthese values are for explanation :-):
5317 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
5324 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
5328 They will all match. If there is no password you will still be
5329 offerednumbers but nothing will happen when you input a string. Any
5330 match iscase sensitive.
5332 \e[1m11.227. talk <call> > <node> [<text>] (0)
\e[0m
5334 \e[1mtalk <call> > <node> [<text>]
\e[22mSend a text message to another station
5337 Send a short message to any other station that is visible on the
5338 clustersystem. You can send it to anyone you can see with a
5339 SHOW/CONFIGURATION command, they don't have to be connected
5340 locally.The second form of TALK is used when other cluster nodes are
5341 connectedwith restricted information. This usually means that they
5342 don't send the user information usually associated with logging on and
5343 off the cluster.If you know that G3JNB is likely to be present on
5344 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
5345 then you would use thesecond form of the talk message.If you want to
5346 have a ragchew with someone you can leave the text messageout and the
5347 system will go into 'Talk' mode. What this means is that ashort
5348 message is sent to the recipient telling them that you are in
5349 a'Talking' frame of mind and then you just type - everything you send
5350 willgo to the station that you asked for. All the usual announcements,
5351 spots and so on will still come out on yourterminal.If you want to do
5352 something (such as send a spot) you preceed the normal command with a
5356 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
5360 To leave talk mode type:
5367 If you are in 'Talk' mode, there is an extention to the '/' command
5368 whichallows you to send the output to all the people you are talking
5369 to. You do with the '//' command. For example:-
5376 will send the hftable as you have it to all the people you are cur-
5379 \e[1m11.228. talk <call> [<text>] (0)
\e[0m
5381 \e[1mtalk <call> [<text>]
\e[22mSend a text message to another station
5384 \e[1m11.229. type <filearea>/<name> (0)
\e[0m
5386 \e[1mtype <filearea>/<name>
\e[22mLook at the contents of a file in one of the
5389 Type out the contents of a file in a filearea. So, for example, in
5390 filearea 'bulletins' you want to look at file 'arld051' you would
5394 TYPE bulletins/arld051
5398 See also SHOW/FILES to see what fileareas are available and a list of
5401 \e[1m11.230. uncatchup <node call> all|[msgno> ...] (5)
\e[0m
5403 \e[1muncatchup <node call> all|[msgno> ...]
\e[22mUnmark a message as sent
5406 When you send messages the fact that you have forwarded it to another
5407 node is remembered so that it isn't sent again. When you have a new
5408 partnernode and you add their callsign to your /spider/msg/forward.pl
5409 file, alloutstanding non-private messages will be forwarded to them.
5410 This may wellbe ALL the non-private messages. You can prevent this by
5411 using these commmands:-
5414 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
5418 and to undo what you have just done:-
5421 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
5425 which will arrange for them to be forward candidates again.Order is
5428 \e[1m11.231. unset/announce (0)
\e[0m
5430 \e[1munset/announce
\e[22mStop announce messages coming out on your terminal
5433 \e[1m11.232. unset/anntalk (0)
\e[0m
5435 \e[1munset/anntalk
\e[22mStop talk like announce messages on your terminal
5437 The announce system on legacy cluster nodes is used as a talk
5438 substitute because the network is so poorly connected. If you:
5445 you will suppress several of these announces, you may miss the odd
5446 useful one as well, but you would probably miss them anyway in thewel-
5447 ter of useless ones.
5454 allows you to see them again. This is the default.
5456 \e[1m11.233. unset/baddx <call>.. (8)
\e[0m
5458 \e[1munset/baddx <call>..
\e[22mPropagate a dx spot with this callsign again
5460 Setting a word as 'baddx' will prevent spots with that word in
5461 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
5462 anyfurther. They will not be displayed and they will not be sent
5463 ontoother nodes.The word must be written in full, no wild cards are
5467 set/baddx FORSALE VIDEO FR0G
5471 To allow a word again, use the following command ...
5478 \e[1m11.234. unset/badnode <call>.. (8)
\e[0m
5480 \e[1munset/badnode <call>..
\e[22mAllow spots from this node again
5482 Setting a callsign as a 'badnode' will prevent spots from that node
5483 going any further. They will not be displayed and they will not be
5484 sent onto other nodes.The call must be a full eg:-
5491 will stop anything from K1TTT. If you want SSIDs as well then you mus-
5492 tenter them specifically.
5499 will allow spots from him again.Use with extreme care. This command
5500 may well be superceeded by FILTERing.
5502 \e[1m11.235. unset/badspotter <call>.. (8)
\e[0m
5504 \e[1munset/badspotter <call>..
\e[22mAllow spots from this callsign again
5506 Setting a callsign as a 'badspotter' will prevent spots from this
5507 callsign going any further. They will not be displayed and they will
5508 not be sent onto other nodes.The call must be written in full, no wild
5509 cards are allowed eg:-
5512 set/badspotter VE2STN
5516 will stop anything from VE2STN. This command will automaticallystop
5517 spots from this user, regardless of whether or which SSID he uses. DO
5518 NOT USE SSIDs in the callsign, just use the callsignas above or below.
5521 unset/badspotter VE2STN
5525 will allow spots from him again.Use with extreme care. This command
5526 may well be superceded by FILTERing.
5528 \e[1m11.236. unset/badword <word>.. (8)
\e[0m
5530 \e[1munset/badword <word>..
\e[22mPropagate things with this word again
5532 Setting a word as a 'badword' will prevent things like spots,announces
5533 or talks with this word in the the text part from going anyfurther.
5534 They will not be displayed and they will not be sent ontoother
5535 nodes.The word must be written in full, no wild cards are allowed eg:-
5536 set/badword annihilate annihilated annihilation
5540 will stop anything with these words in the text.
5543 unset/badword annihilated
5547 will allow text with this word again.
5549 \e[1m11.237. unset/beep (0)
\e[0m
5551 \e[1munset/beep
\e[22mStop beeps for DX and other messages on your terminal
5554 \e[1m11.238. unset/debug <name> (9)
\e[0m
5556 \e[1munset/debug <name>
\e[22mRemove a debug level from the debug set
5558 You can choose to log several different levels. The levels are
5561 chan state msg cron connect
5565 You can show what levels you are logging with SHOW/DEBUG
5567 \e[1m11.239. unset/dx (0)
\e[0m
5569 \e[1munset/dx
\e[22mStop DX messages coming out on your terminal
5572 \e[1m11.240. unset/dxcq (0)
\e[0m
5574 \e[1munset/dxcq
\e[22mStop CQ Zones on the end of DX announcements
5576 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
5577 announcement (there is just enough room). Some user programscannot
5578 cope with this. The Spotter's CQ is on the RHS of the time, the
5579 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
5580 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5583 \e[1m11.241. unset/dxgrid (0)
\e[0m
5585 \e[1munset/dxgrid
\e[22mStop QRA Grid Squares on the end of DX announcements
5587 A standard feature which is enabled in version 1.43 and above is that
5588 if the spotter's grid square is known it is output on the endof a DX
5589 announcement (there is just enough room). Some user programscannot
5590 cope with this. You can use this command to reset (or set)this
5591 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
5592 flags you have set if you are confused.
5594 \e[1m11.242. unset/dxitu (0)
\e[0m
5596 \e[1munset/dxitu
\e[22mStop ITU Zones on the end of DX announcements
5598 Display both the Spotter's and the Spotted's ITU Zone on the endof a
5599 DX announcement (there is just enough room). Some user programscannot
5600 cope with this. The Spotter's ITU is on the RHS of the time, the
5601 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
5602 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
5605 \e[1m11.243. unset/echo (0)
\e[0m
5607 \e[1munset/echo
\e[22mStop the cluster echoing your input
5609 If you are connected via a telnet session, different implimentationsof
5610 telnet handle echo differently depending on whether you are connected
5611 via port 23 or some other port. You can use this commandto change the
5612 setting appropriately. The setting is stored in your user profile.YOU
5613 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
5615 \e[1m11.244. unset/email (0)
\e[0m
5617 \e[1munset/email
\e[22mStop personal msgs being forwarded by email
5619 If any personal messages come in for your callsign then you can
5620 usethese commands to control whether they are forwarded onto your
5621 emailaddress. To enable the forwarding do something like:-
5624 SET/EMAIL mike.tubby@somewhere.com
5628 You can have more than one email address (each one separated by a
5629 space).Emails are forwarded to all the email addresses you specify.You
5630 can disable forwarding by:-
5637 \e[1m11.245. unset/here (0)
\e[0m
5639 \e[1munset/here
\e[22mTell the system you are absent from your terminal
5642 \e[1m11.246. unset/hops <call> ann|spots|route|wwv|wcy (8)
\e[0m
5644 \e[1munset/hops <call> ann|spots|route|wwv|wcy
\e[22mUnset hop count
5646 Set the hop count for a particular type of broadcast for a node.This
5647 command allows you to set up special hop counts for a node for
5648 currently: announce, spots, wwv and wcy broadcasts.eg:
5651 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
5655 Set SHOW/HOPS for information on what is already set. This commandcre-
5656 ates a filter and works in conjunction with the filter system. You can
5657 unset the hops with command UNSET/HOPS. For example:-
5660 unset/hops gb7djk ann unset/hops gb7mbc spots
5664 \e[1m11.247. unset/isolate (9)
\e[0m
5666 \e[1munset/isolate
\e[22mStop Isolation of a node from the rest of the network
5668 Remove isolation from a node - SET/ISOLATE
5670 \e[1m11.248. unset/lockout <call> (9)
\e[0m
5672 \e[1munset/lockout <call>
\e[22mAllow a callsign to connect to the cluster
5675 \e[1m11.249. unset/logininfo (0)
\e[0m
5677 \e[1munset/logininfo
\e[22mInform when a station logs out locally
5680 \e[1m11.250. unset/password <call> ... (9)
\e[0m
5682 \e[1munset/password <call> ...
\e[22mDelete (remove) a user's password
5684 This command allows the sysop to completely delete and remove a
5685 password for a user.
5687 \e[1m11.251. unset/privilege (0)
\e[0m
5689 \e[1munset/privilege
\e[22mRemove any privilege for this session
5691 You can use this command to 'protect' this session from
5692 unauthoriseduse. If you want to get your normal privilege back you
5693 will need toeither logout and login again (if you are on a console) or
5694 use theSYSOP command.
5696 \e[1m11.252. unset/prompt (0)
\e[0m
5698 \e[1munset/prompt
\e[22mSet your prompt back to default
5700 This command will set your user prompt to exactly the string that you
5701 say. The point of this command to enable a user to interface to
5702 programsthat are looking for a specific prompt (or else you just want
5703 a differentfixed prompt).
5710 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
5713 \e[1m11.253. unset/register <call> ... (9)
\e[0m
5715 \e[1munset/register <call> ...
\e[22mMark a user as not registered
5717 Registration is a concept that you can switch on by executing the
5720 set/var $main::regreq = 1
5724 command (usually in your startup file)If a user is NOT registered
5725 then, firstly, instead of the normalmotd file (/spider/data/motd)
5726 being sent to the user at startup, theuser is sent the motd_nor file
5727 instead. Secondly, the non registereduser only has READ-ONLY access to
5728 the node. The non-registered usercannot use DX, ANN etc. The only
5729 exception to this is that a non-registered user can TALK orSEND
5730 messages to the sysop.
5732 \e[1m11.254. unset/talk (0)
\e[0m
5734 \e[1munset/talk
\e[22mStop TALK messages coming out on your terminal
5737 \e[1m11.255. unset/usstate (0)
\e[0m
5739 \e[1munset/usstate
\e[22mStop US State info on the end of DX announcements
5741 If the spotter's or spotted's US State is known it is output on the
5742 end of a DX announcement (there is just enough room). A spotter's
5743 state will appear on the RHS of the time (like SET/DXGRID) and the
5744 spotted's State will appear on the LHS of thetime field. Any
5745 information found will override any locator information from
5746 SET/DXGRID.Some user programs cannot cope with this. You can use this
5747 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
5748 SET/DXITUDo a STAT/USER to see which flags you have set if you are
5751 \e[1m11.256. unset/wcy (0)
\e[0m
5753 \e[1munset/wcy
\e[22mStop WCY messages coming out on your terminal
5756 \e[1m11.257. unset/wwv (0)
\e[0m
5758 \e[1munset/wwv
\e[22mStop WWV messages coming out on your terminal
5761 \e[1m11.258. unset/wx (0)
\e[0m
5763 \e[1munset/wx
\e[22mStop WX messages coming out on your terminal
5766 \e[1m11.259. who (0)
\e[0m
5768 \e[1mwho
\e[22mShow who is physically connected
5770 This is a quick listing that shows which callsigns are connected
5771 andwhat sort of connection they have
5773 \e[1m11.260. wx <text> (0)
\e[0m
5775 \e[1mwx <text>
\e[22mSend a weather message to local users
5778 \e[1m11.261. wx full <text> (0)
\e[0m
5780 \e[1mwx full <text>
\e[22mSend a weather message to all cluster users
5783 \e[1m11.262. wx sysop <text> (5)
\e[0m
5785 \e[1mwx sysop <text>
\e[22mSend a weather message to other clusters only
5787 Weather messages can sometimes be useful if you are experiencing an
5788 extremethat may indicate enhanced conditions