1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 February 2003 revision 0.4
6 A reference for SysOps of the DXSpider DXCluster program.
7 ______________________________________________________________________
13 1. Routing and Filtering
16 1.3 The node_default filter
17 1.4 General route filtering
18 1.5 General filter rules
22 1.9 Advanced filtering
23 1.10 Basic hop control
24 1.11 Hop Control on Specific Nodes
25 1.12 Isolating networks
29 2.2 Filtering words from text fields in Announce, Talk and DX spots
30 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
39 3.7 Distribution lists
44 5.1 Creating databases
45 5.2 Importing databases
46 5.3 Checking available databases
47 5.4 Looking up databases
48 5.5 Removing databases
50 6. Information, files and useful programs
54 6.4 Other text messages
57 6.7 Updating kepler data
59 6.9 Connecting logging programs
62 8. Web based statistics
68 10.1 CVS from a Linux platform
69 10.2 CVS from a Windows platform
71 11. The DXSpider command set
73 11.2 accept/announce <call> [input] [0-9] <pattern> (8)
74 11.3 accept/announce [0-9] <pattern> (0)
75 11.4 accept/route <call> [0-9] <pattern> (8)
76 11.5 accept/spots <call> [input] [0-9] <pattern> (8)
77 11.6 accept/spots [0-9] <pattern> (0)
78 11.7 accept/wcy <call> [input] [0-9] <pattern> (8)
79 11.8 accept/wcy [0-9] <pattern> (0)
80 11.9 accept/wwv <call> [input] [0-9] <pattern> (8)
81 11.10 accept/wwv [0-9] <pattern> (0)
82 11.11 announce <text> (0)
83 11.12 announce full <text> (0)
84 11.13 announce sysop <text> (5)
85 11.14 apropos <string> (0)
86 11.15 blank [<string>] [<nn>] (0)
88 11.17 catchup <node call> all|[<msgno> ...] (5)
89 11.18 clear/announce <callsign> [input] [0-9|all] (8)
90 11.19 clear/announce [1|all] (0)
91 11.20 clear/route <callsign> [input] [0-9|all] (8)
92 11.21 clear/route [1|all] (0)
93 11.22 clear/spots <callsign> [input] [0-9|all] (8)
94 11.23 clear/spots [0-9|all] (0)
95 11.24 clear/wcy <callsign> [input] [0-9|all] (8)
96 11.25 clear/wcy [1|all] (0)
97 11.26 clear/wwv <callsign> [input] [0-9|all] (8)
98 11.27 clear/wwv [1|all] (0)
99 11.28 connect <callsign> (5)
101 11.30 dbshow <dbname> <key> (0)
103 11.32 directory <from>-<to> (0)
104 11.33 directory <nn> (0)
105 11.34 directory all (0)
106 11.35 directory from <call> (0)
107 11.36 directory new (0)
108 11.37 directory own (0)
109 11.38 directory subject <string> (0)
110 11.39 directory to <call> (0)
112 11.41 disconnect <call> [<call> ...] (8)
113 11.42 dx [by <call>] <freq> <call> <remarks> (0)
114 11.43 echo <line> (0)
115 11.44 filtering... (0)
116 11.45 forward/latlong <node_call> (8)
117 11.46 forward/opernam <call> (1)
119 11.48 init <node> (5)
121 11.50 kill <from msgno>-<to msgno> (0)
122 11.51 kill <from>-<to> (5)
123 11.52 kill <msgno> [<msgno..] (0)
124 11.53 kill <msgno> [<msgno> ...] (0)
125 11.54 kill expunge <msgno> [<msgno..] (6)
126 11.55 kill from <call> (5)
127 11.56 kill full <msgno> [<msgno..] (5)
128 11.57 kill full <msgno> [<msgno] (5)
129 11.58 kill to <call> (5)
130 11.59 kill from <regex> (0)
131 11.60 kill to <regex> (0)
134 11.63 load/keps [nn] (5)
135 11.64 merge <node> [<no spots>/<no wwv>] (5)
136 11.65 pc <call> <text> (8)
137 11.66 ping <node call> (1)
138 11.67 rcmd <node call> <cmd> (1)
140 11.69 read <msgno> (0)
143 11.72 reject/announce <call> [input] [0-9] <pattern> (8)
144 11.73 reject/announce [0-9] <pattern> (0)
145 11.74 reject/route <call> [0-9] <pattern> (8)
146 11.75 reject/spots <call> [input] [0-9] <pattern> (8)
147 11.76 reject/spots [0-9] <pattern> (0)
148 11.77 reject/wcy <call> [input] [0-9] <pattern> (8)
149 11.78 reject/wcy [0-9] <pattern> (0)
150 11.79 reject/wwv <call> [input] [0-9] <pattern> (8)
151 11.80 reject/wwv [0-9] <pattern> (0)
153 11.82 reply <msgno> (0)
154 11.83 reply b <msgno> (0)
155 11.84 reply noprivate <msgno> (0)
156 11.85 reply rr <msgno> (0)
157 11.86 send <call> [<call> ...] (0)
158 11.87 send copy <msgno> <call> (0)
159 11.88 send noprivate <call> (0)
160 11.89 send private <call> (0)
161 11.90 send rr <call> (0)
162 11.91 set/address <your address> (0)
163 11.92 set/announce (0)
164 11.93 set/anntalk (0)
165 11.94 set/arcluster <call> [<call>..] (5)
166 11.95 set/baddx <call>.. (8)
167 11.96 set/badnode <call>.. (8)
168 11.97 set/badspotter <call>.. (8)
169 11.98 set/badword <word>.. (8)
170 11.99 set/bbs <call> [<call>..] (5)
172 11.101 set/clx <call> [<call>..] (5)
175 11.104 set/dxgrid (0)
177 11.106 set/dxnet <call> [<call>..] (5)
179 11.108 set/email <email> ... (0)
181 11.110 set/homenode <node> (0)
182 11.111 set/hops <call> ann|spots|route|wwv|wcy <n> (8)
183 11.112 set/language <lang> (0)
184 11.113 set/location <lat & long> (0)
185 11.114 set/logininfo (0)
186 11.115 set/name <your name> (0)
187 11.116 set/node <call> [<call>..] (5)
188 11.117 set/obscount <count> <call> (8)
189 11.118 set/page <lines per page> (0)
190 11.119 set/password (0)
191 11.120 set/prompt <string> (0)
192 11.121 set/qra <locator> (0)
193 11.122 set/qth <your qth> (0)
194 11.123 set/spider <call> [<call>..] (5)
196 11.125 set/usstate (0)
200 11.129 show/baddx (1)
201 11.130 show/badnode (1)
202 11.131 show/badspotter (1)
203 11.132 show/badword (1)
204 11.133 show/configuration [<node>] (0)
205 11.134 show/configuration/node (0)
206 11.135 show/connect (1)
207 11.136 show/date [<prefix>|<callsign>] (0)
208 11.137 show/db0sdx <callsign> (0)
210 11.139 show/dxcc <prefix> (0)
211 11.140 show/dxstats [days] [date] (0)
212 11.141 show/files [<filearea> [<string>]] (0)
213 11.142 show/filter (0)
214 11.143 show/hfstats [days] [date] (0)
215 11.144 show/hftable [days] [date] [prefix ...] (0)
216 11.145 show/hops <call> [ann|spots|route|wcy|wwv] (8)
217 11.146 show/isolate (1)
218 11.147 show/log [<callsign>] (8)
219 11.148 show/moon [ndays] [<prefix>|<callsign>] (0)
220 11.149 show/muf <prefix> [<hours>][long] (0)
221 11.150 show/newconfiguration [<node>] (0)
222 11.151 show/newconfiguration/node (0)
223 11.152 show/node [<callsign> ...] (1)
224 11.153 show/prefix <callsign> (0)
225 11.154 show/program (5)
226 11.155 show/qra <lat> <long> (0)
227 11.156 show/qra <locator> [<locator>] (0)
228 11.157 show/qrz <callsign> (0)
229 11.158 show/route <callsign> ... (0)
230 11.159 show/satellite <name> [<hours> <interval>] (0)
231 11.160 show/station all [<regex>] (6)
232 11.161 show/station [<callsign> ..] (0)
233 11.162 show/sun [ndays] [<prefix>|<callsign>] (0)
234 11.163 show/time [<prefix>|<callsign>] (0)
235 11.164 show/usdb [call ..] (0)
236 11.165 show/vhfstats [days] [date] (0)
237 11.166 show/vhftable [days] [date] [prefix ...] (0)
239 11.168 show/wcy <n> (0)
240 11.169 show/wm7d <callsign> (0)
242 11.171 show/wwv <n> (0)
244 11.173 stat/channel [<callsign>] (5)
245 11.174 stat/db <dbname> (5)
247 11.176 stat/msg <msgno> (1)
248 11.177 stat/route_node <callsign> (5)
249 11.178 stat/route_node all (5)
250 11.179 stat/route_user <callsign> (5)
251 11.180 stat/route_user all (5)
252 11.181 stat/user [<callsign>] (5)
254 11.183 talk <call> > <node> [<text>] (0)
255 11.184 talk <call> [<text>] (0)
256 11.185 type <filearea>/<name> (0)
257 11.186 uncatchup <node call> all|[msgno> ...] (5)
258 11.187 unset/announce (0)
259 11.188 unset/anntalk (0)
260 11.189 unset/baddx <call>.. (8)
261 11.190 unset/badnode <call>.. (8)
262 11.191 unset/badspotter <call>.. (8)
263 11.192 unset/badword <word>.. (8)
264 11.193 unset/beep (0)
266 11.195 unset/dxcq (0)
267 11.196 unset/dxgrid (0)
268 11.197 unset/dxitu (0)
269 11.198 unset/echo (0)
270 11.199 unset/email (0)
271 11.200 unset/here (0)
272 11.201 unset/hops <call> ann|spots|route|wwv|wcy (8)
273 11.202 unset/logininfo (0)
274 11.203 unset/privilege (0)
275 11.204 unset/prompt (0)
276 11.205 unset/talk (0)
277 11.206 unset/usstate (0)
283 11.212 wx full <text> (0)
284 11.213 wx sysop <text> (5)
287 ______________________________________________________________________
289 1. Routing and Filtering
293 From DXSpider version 1.48, major changes were introduced to the way
294 node connections are treated. This is part of an ongoing process to
295 remove problems with loops and to enable talk and other functions to
296 propagate across the whole of the worldwide cluster network. In fact,
297 in a Spider network, it would be useful, perhaps even necessary to
298 have loops. This would give real resilience to the network, meaning
299 that if a link dropped, the information flow would simply come in and
300 go out via a different route. Of course, we do not have a complete
301 network of Spider nodes, there are other programs out there. Some of
302 these do not have any protection from loops. Certainly AK1A does not
303 handle loops well at all. It is therefore necessary to have some form
304 of protection for these nodes.
307 In fact DXSpider has had a simple system for some time which is called
308 isolation. This is similar to what in other systems such as clx, is
309 called passive mode. A more detailed explanation of isolation is given
310 further below. This system is still available and, for simple
311 networks, is probably all that you need.
314 The new functionality introduced in version 1.48 allows filtering the
315 node and user protocol frames on a "per interface" basis. We call this
316 route filtering. This is used instead of isolation.
319 What this really means is that you can control more or less completely
320 which user and node management PC protocol frames pass to each of your
321 partner nodes. You can also limit what comes into your node from your
322 partners. It is even possible to control the settings that your
323 partner node has for the routing information that it sends to you
324 (using the rcmd command).
329 Initially when route filters were being tested we generated a
330 "default" filter. Unfortunately it quickly became apparent that this
331 might suit the UK cluster network but didn't really fit anybody else.
332 However using a default filter is an appropriate thing to do. How, is
333 explained further on.
336 The first thing that you must do is determine whether you need to use
337 route filtering at all. If you are a "normal" node with two or three
338 partners and you arranged in an "official" non-looping tree type
339 network, then you do not need to do route filtering and you will feel
340 a lot better for not getting involved. If you are successfully using
341 isolation then you also probably don't need to use route filtering.
343 To put it simply, you should not mix Isolation and Route Filtering.
344 It will work, of sorts, but you will not get the expected results. If
345 you are using Isolation sucessfully at the moment, do not get involved
346 in Route Filtering unless you have a good supply of aspirin! Once you
347 have started down the road of Route Filtering, do not use Isolation
348 either. Use one or the other, not both.
351 You will only require this functionality if you are "well-connected".
352 What that means is that you are connected to several different parts
353 of (say) the EU cluster and, at the same time, also connected to two
354 or three places in the US which, in turn are connected back to the EU.
355 This is called a "loop" and if you are seriously looped then you need
359 I should at this stage give a little bit of background on filters.
360 All the filters in Spider work in basically the same way. You can
361 either accept or reject various options in order to create the filter
362 rules you wish to achieve. Some filters are user settable, others can
363 only be altered by the sysop. Route filtering can only be done by the
368 Anyway, without further discouragement, let me start the process of
372 1.3. The node_default filter
374 All normal systems should have a default routing filter and it should
375 usually be set to send only the normal, unlooped, view of your
376 "national" network. Here in the UK that means nodes from the UK and
377 Eire, in EU it is more complex as the networks there grew up in a more
382 The generic commands are:-
386 reject/route node_default <filter_option>
390 accept/route node_default <filter_option>
394 where filter_option is one of the following ...
403 channel_dxcc <numbers>
404 channel_itu <numbers>
405 channel_zone <numbers>
408 Please be careful if you alter this setting, it will affect ALL your
409 links! Remember, this is a default filter for node connections, not a
413 For the default routing filter then you have two real choices: either
414 a "national" view or the "safe" option of only your own callsign.
415 Examples of each (for my node: GB7DJK) are:-
419 acc/route node_default call_dxcc 61,38
420 acc/route node_default call gb7djk
424 GB7DJK uses the first of these. The DXCC countries can be obtained
425 from the show/prefix command.
428 The example filters shown control output TO all your partner nodes
429 unless they have a specific filter applied to them (see next section).
432 It is also possible to control the incoming routing information that
433 you are prepared to accept FROM your partner nodes. The reason this is
434 necessary is to make sure that stuff like mail, pings and similar
435 commands a) go down the correct links and b) don't loop around
436 excessively. Again using GB7DJK as an example a typical default input
437 filter would be something like:
441 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
445 What this does is accept node and user information for our national
446 network from nodes that are in our national network, but rejects such
447 information from anyone else. Although it doesn't explicitly say so,
448 by implication, any other node information (not from the UK and Eire)
452 As I imagine it will take a little while to get one's head around all
453 of this you can study the effect of any rules that you try by watching
454 the debug output after having done:-
462 After you have got tired of that, to put it back the way it was:-
470 1.4. General route filtering
472 Exactly the same rules apply for general route filtering. You would
473 use either an accept filter or a reject filter like this ...
477 reject/route <node_call> <filter_option>
481 accept/route <node_call> <filter_option>
485 Here are some examples of route filters ...
489 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
490 rej/route all (equiv to [very] restricted mode)
491 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
492 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
496 In practice you will either be opening the default filter out for a
497 partner by defining a specific filter for that callsign:-
502 acc/route gb7baa input all
506 or restricting it quite a lot, in fact making it very nearly like an
507 isolated node, like this:-
511 acc/route pi4ehv-8 call gb7djk
512 rej/route pi4ehv-8 input call_dxcc 61,38
516 This last example takes everything except UK and Eire from PI4EHV-8
517 but only sends him my local configuration (just a PC19 for GB7DJK and
518 PC16s for my local users).
521 It is possible to write much more complex rules, there are up to 10
522 accept/reject pairs per callsign per filter. For more information see
527 1.5. General filter rules
529 Upto v1.44 it was not possible for the user to set their own filters.
530 From v1.45 though that has all changed. It is now possible to set
531 filters for just about anything you wish. If you have just updated
532 from an older version of DXSpider you will need to update your new
533 filters. You do not need to do anything with your old filters, they
534 will be renamed as you update.
537 There are 3 basic commands involved in setting and manipulating
538 filters. These are accept, reject and clear. First we will look
539 generally at filtering. There are a number of things you can filter in
540 the DXSpider system. They all use the same general mechanism.
543 In general terms you can create a "reject" or an "accept" filter which
544 can have up to 10 lines in it. You do this using, for example ...
553 where ..... are the specific commands for that type of filter. There
554 are filters for spots, wwv, announce, wcy and (for sysops) connects.
555 See each different accept or reject command reference for more
558 There is also a command to clear out one or more lines in a filter.
568 There is clear/xxxx command for each type of filter.
571 and you can check that your filters have worked by the command ...
579 For now we are going to use spots for the examples, but you can apply
580 the same principles to all types of filter.
585 There are two main types of filter, accept or reject. You can use
586 either to achieve the result you want dependent on your own preference
587 and which is more simple to do. It is pointless writing 8 lines of
588 reject filters when 1 accept filter would do the same thing! Each
589 filter has 10 lines (of any length) which are tried in order. If a
590 line matches then the action you have specified is taken (ie reject
591 means ignore it and accept means take it)
594 If you specify reject filters, then any lines that arrive that match
595 the filter will be dumped but all else will be accepted. If you use
596 an accept filter, then ONLY the lines in the filter will be accepted
597 and all else will be dumped. For example if you have a single line
602 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
606 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
609 If you set a reject filter like this ...
613 reject/spots on hf/cw
617 Then you will get everything EXCEPT HF CW spots. You could make this
618 single filter even more flexible. For example, if you are interested
619 in IOTA and will work it even on CW even though normally you are not
620 interested in CW, then you could say ...
624 reject/spots on hf/cw and not info iota
628 But in that case you might only be interested in iota and say:-
632 accept/spots not on hf/cw or info iota
636 which achieves exactly the same thing. You should choose one or the
637 other until you are comfortable with the way it works. You can mix
638 them if you wish (actually you can have an accept AND a reject on the
639 same line) but don't attempt this until you are sure you know what you
643 You can arrange your filter lines into logical units, either for your
644 own understanding or simply convenience. Here is an example ...
648 reject/spots 1 on hf/cw
649 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
653 What this does is to ignore all HF CW spots and also rejects any spots
654 on VHF which don't either originate or spot someone in Europe.
657 This is an example where you would use a line number (1 and 2 in this
658 case), if you leave the digit out, the system assumes '1'. Digits
659 '0'-'9' are available. This make it easier to see just what filters
660 you have set. It also makes it more simple to remove individual
661 filters, during a contest for example.
664 You will notice in the above example that the second line has
665 brackets. Look at the line logically. You can see there are 2
666 separate sections to it. We are saying reject spots that are VHF or
667 above APART from those in zones 14, 15 and 16 (either spotted there or
668 originated there). If you did not have the brackets to separate the 2
669 sections, then Spider would read it logically from the front and see a
670 different expression entirely ...
674 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
678 The simple way to remember this is, if you use OR - use brackets.
679 Whilst we are here CASE is not important. 'And BY_Zone' is just the
680 same as 'and by_zone'.
682 As mentioned earlier, setting several filters can be more flexible
683 than simply setting one complex one. Doing it in this way means that
684 if you want to alter your filter you can just redefine or remove one
685 or more lines of it or one line. For example ...
689 reject/spots 1 on hf/ssb
693 would redefine our earlier example, or
701 To remove all the filter lines in the spot filter ...
711 You can filter in several different ways. The options are listed in
712 the various helpfiles for accept, reject and filter.
716 Sometimes all that is needed is a general rule for node connects.
717 This can be done with a node_default filter. This rule will always be
718 followed, even if the link is isolated, unless another filter is set
719 specifically. Default rules can be set for nodes and users. They can
720 be set for spots, announces, WWV and WCY. They can also be used for
721 hops. An example might look like this ...
725 accept/spot node_default by_zone 14,15,16,20,33
726 set/hops node_default spot 50
730 This filter is for spots only, you could set others for announce, WWV
731 and WCY. This filter would work for ALL nodes unless a specific
732 filter is written to override it for a particular node. You can also
733 set a user_default should you require. It is important to note that
734 default filters should be considered to be "connected". By this I
735 mean that should you override the default filter for spots, you need
736 to add a rule for the hops for spots also.
739 1.9. Advanced filtering
741 Once you are happy with the results you get, you may like to
745 The previous example that filters hf/cw spots and accepts vhf/uhf
746 spots from EU can be written with a mixed filter, for example ...
752 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
756 Note that the first filter has not been specified with a number. This
757 will automatically be assumed to be number 1. In this case, we have
758 said reject all HF spots in the CW section of the bands but accept all
759 others at HF. Also accept anything in VHF and above spotted in or by
760 operators in the zones 14, 15 and 16. Each filter slot actually has a
761 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
765 It was mentioned earlier that after a reject test that doesn't match,
766 the default for following tests is 'accept', the reverse is true for
767 'accept'. In the example what happens is that the reject is executed
768 first, any non hf/cw spot is passed to the accept line, which lets
769 through everything else on HF. The next filter line lets through just
770 VHF/UHF spots from EU.
773 1.10. Basic hop control
775 In /spider/data you will find a file called hop_table.pl. This is the
776 file that controls your hop count settings. It has a set of default
777 hops on the various PC frames and also a set for each node you want to
778 alter the hops for. You may be happy with the default settings of
779 course, but this powerful tool can help to protect and improve the
780 network. The file will look something like this ...
785 # hop table construction
790 # default hopcount to use
793 # some variable hop counts based on message type
804 # the per node hop control thingy
836 Each set of hops is contained within a pair of curly braces and
837 contains a series of PC frame types. PC11 for example is a DX spot.
838 The figures here are not exhaustive but should give you a good idea of
842 SHould any of the nodecalls include an ssid, it is important to wrap
843 the whole call in single quotes, like this ...
858 If you do not do this, you will get errors and the file will not work
862 You can alter this file at any time, including whilst the cluster is
863 running. If you alter the file during runtime, the command load/hops
864 will bring your changes into effect.
867 1.11. Hop Control on Specific Nodes
869 You can set a callsign specific hop count for any of the standard
874 set/hops gb7djk spot 4
875 set/hops node_default route 10
876 set/hops gb7baa wcy 5
880 all work on their specific area of the protocol.
883 The set/hops command overrides any hops that you have set otherwise.
886 You can show what hops have been set using the show/hops command.
889 1.12. Isolating networks
891 It is possible to isolate networks from each other on a "gateway" node
892 using the set/isolate <node_call> command.
895 The effect of this is to partition an isolated network completely from
896 another node connected to your node. Your node will appear on and
897 otherwise behave normally on every network to which you are connected,
898 but data from an isolated network will not cross onto any other
899 network or vice versa. However all the spot, announce and WWV traffic
900 and personal messages will still be handled locally (because you are a
901 real node on all connected networks), that is locally connected users
902 will appear on all networks and will be able to access and receive
903 information from all networks transparently. All routed messages will
904 be sent as normal, so if a user on one network knows that you are a
905 gateway for another network, he can still still send a talk/announce
906 etc message via your node and it will be routed across.
909 If you use isolate on a node connection you will continue to receive
910 all information from the isolated partner, however you will not pass
911 any information back to the isolated node. There are times when you
912 would like to forward only spots across a link (maybe during a contest
913 for example). To do this, isolate the node in the normal way and use
914 an acc/spot >call< all filter to override the isolate.
921 In the /spider/msg directory you will find a file called
922 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
923 original looks something like this ....
927 # the list of regexes for messages that we won't store having
928 # received them (bear in mind that we must receive them fully before
932 # The format of each line is as follows
934 # type source pattern
935 # P/B/F T/F/O/S regex
937 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
938 # source: T - to field, F - from field, O - origin, S - subject
939 # pattern: a perl regex on the field requested
941 # Currently only type B and P msgs are affected by this code.
943 # The list is read from the top down, the first pattern that matches
944 # causes the action to be taken.
946 # The pattern can be undef or 0 in which case it will always be selected
947 # for the action specified
958 I think this is fairly self explanatory. It is simply a list of
959 subject headers that we do not want to pass on to either the users of
960 the cluster or the other cluster nodes that we are linked to. This is
961 usually because of rules and regulations pertaining to items for sale
962 etc in a particular country.
966 2.2. Filtering words from text fields in Announce, Talk and DX spots
968 From version 1.48 onwards the interface to this has changed. You can
969 now use the commands set/badword to add words that you are not
970 prepared to see on the cluster, unset/badword to allow that word again
971 and show/badword to list the words that you have set.
974 If you have a previous /spider/data/badwords, the first time you start
975 the node, it will read and convert this file to the new commands. The
976 old style file will then be removed.
979 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
982 There are a number of commands that control whether a spot progresses
983 any further by regarding it as "bad" in some way.
986 A DX Spot has a number of fields which can be checked to see whether
987 they contain "bad" values, they are: the DX callsign itself, the
988 Spotter and the Originating Node.
991 There are a set of commands which allow the sysop to control whether a
1002 These work in the same as the set/badword command, you can add any
1003 words or callsigns or whatever to the appropriate database. For
1004 example, to stop a spot from a particular node you do:
1008 set/badnode gb7djk gb7dxc
1016 set/badspotter b0mb p1rat nocall
1024 set/baddx video wsjt
1028 You can remove a word using the appropriate unset command
1029 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1030 of show/baddx, show/badspotter and show/badnode.
1035 DXSpider deals seamlessly with standard AK1A type mail. It supports
1036 both personal and bulletin mail and the sysop has additional commands
1037 to ensure that mail gets to where it is meant. DXSpider will send
1038 mail almost immediately, assuming that the target is on line.
1039 However, only one mail message is dealt with at any one time. If a
1040 mail message is already being sent or recieved, then the new message
1041 will be queued until it has finished.
1043 The cluster mail is automatically deleted after 30 days unless the
1044 sysop sets the "keep" flag using the msg command.
1049 Personal mail is sent using the sp command. This is actually the
1050 default method of sending mail and so a simple s for send will do. A
1051 full list of the send commands and options is in the command set
1052 section, so I will not duplicate them here.
1057 Bulletin mail is sent by using the sb command. This is one of the
1058 most common mistakes users make when sending mail. They send a
1059 bulletin mail with s or sp instead of sb and of course the message
1060 never leaves the cluster. This can be rectified by the sysop by using
1064 Bulletin addresses can be set using the Forward.pl file.
1069 DXSpider receives all and any mail sent to it without any alterations
1070 needed in files. Because personal and bulletin mail are treated
1071 differently, there is no need for a list of accepted bulletin
1072 addresses. It is necessary, however, to tell the program which links
1073 accept which bulletins. For example, it is pointless sending
1074 bulletins addresses to "UK" to any links other than UK ones. The file
1075 that does this is called forward.pl and lives in /spider/msg. At
1076 default, like other spider files it is named forward.pl.issue. Rename
1077 it to forward.pl and edit the file to match your requirements. The
1083 # this is an example message forwarding file for the system
1085 # The format of each line is as follows
1087 # type to/from/at pattern action destinations
1088 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1090 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1091 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1092 # pattern: a perl regex on the field requested
1093 # action: I - ignore, F - forward
1094 # destinations: a reference to an array containing node callsigns
1096 # if it is non-private and isn't in here then it won't get forwarded
1098 # Currently only type B msgs are affected by this code.
1100 # The list is read from the top down, the first pattern that matches
1101 # causes the action to be taken.
1103 # The pattern can be undef or 0 in which case it will always be selected
1104 # for the action specified
1106 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1107 # pattern) then it will always be forwarded to every node that doesn't have
1108 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1109 # you allow a new link with this on EVERY bull will be forwarded immediately
1110 # on first connection)
1120 Simply insert a bulletin address and state in the brackets where you
1121 wish that mail to go. For example, you can see here that mail sent to
1122 "UK" will only be sent to the UK links and not to PA4AB-14.
1125 To force the cluster to reread the file use load/forward
1128 NB: If a user tries to send mail to a bulletin address that does not
1129 exist in this file, they will get an error.
1132 3.4. The msg command
1134 The msg command is a very powerful and flexible tool for the sysop.
1135 It allows the sysop to alter to and from fields and make other changes
1136 to manage the cluster mail.
1138 Here is a full list of the various options ...
1142 MSG TO <msgno> <call> - change TO callsign to <call>
1143 MSG FRom <msgno> <call> - change FROM callsign to <call>
1144 MSG PRrivate <msgno> - set private flag
1145 MSG NOPRrivate <msgno> - unset private flag
1146 MSG RR <msgno> - set RR flag
1147 MSG NORR <msgno> - unset RR flag
1148 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1149 MSG NOKEep <msgno> - unset the keep flag
1150 MSG SUbject <msgno> <new> - change the subject to <new>
1151 MSG WAittime <msgno> - remove any waiting time for this message
1152 MSG NOREad <msgno> - mark message as unread
1153 MSG REad <msgno> - mark message as read
1154 MSG QUeue - queue any outstanding bulletins
1155 MSG QUeue 1 - queue any outstanding private messages
1159 These commands are simply typed from within the cluster as the sysop
1165 You can check on a message from within the cluster by using the
1166 command stat/msg. This will give you additional information on the
1167 message number including which nodes have received it, which node it
1168 was received from and when etc. Here is an example of the output of
1173 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1176 Msg Time: 26-Jan-2001 1302Z
1180 Subject: AMSAT 2line KEPS 01025.AMSAT
1182 Got it Nodes: GB7BAA, GB7ADX
1186 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1192 This is described in the section on Other filters so I will not
1196 3.7. Distribution lists
1198 Distribution lists are simply a list of users to send certain types of
1199 mail to. An example of this is mail you only wish to send to other
1200 sysops. In /spider/msg there is a directory called distro. You put
1201 any distibution lists in here. For example, here is a file called
1202 SYSOP.pl that caters for the UK sysops.
1205 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1206 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1207 GB7DXK GB7DXI GB7DXS)
1211 Any mail sent to "sysop" would only be sent to the callsigns in this
1217 Spider provides a simple BBS interface. No input is required from the
1218 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1219 and pushes any required mail to the cluster. No mail can flow from
1220 Spider to the BBS, the interface is one-way.
1223 Please be careful not to flood the cluster network with unnecessary
1224 mail. Make sure you only send mail to the clusters that want it by
1225 using the Forward.pl file very carefully.
1230 From 1.48 onwards it will become increasingly possible to control
1231 DXSpider's operation with scripts of various kinds.
1234 The directory /spider/scripts is where it all happens and is used for
1235 several things. Firstly it contains a file called startup that can be
1236 used to call in any changes to the cluster from the default settings
1237 on startup. This script is executed immediately after all
1238 initialisation of the node is done but before any connections are
1239 possible. Examples of this include how many spots it is possible to
1240 get with the sh/dx command, whether you want registration/passwords to
1241 be permanently on etc. An example file is shown below and is included
1242 in the distribution as startup.issue.
1247 # startup script example
1249 # set maximum no of spots allowed to 100
1250 # set/var $Spot::maxspots = 100
1252 # Set registration on
1253 # set/var $main::reqreg = 1
1256 # set/var $main::passwdreq = 1
1261 As usual, any text behind a # is treated as a comment and not read.
1262 To use this file, simply rename it from startup.issue to startup. In
1263 our example above there are three options. The first option is the
1264 amount of spots that a user can request with the sh/dx command.
1265 Normally the default is to give 10 spots unless the user specifies
1266 more. Without this line enabled, the maximum a user can request is
1267 100 spots. Depending on your link quality you may wish to enable more
1268 or less by specifying the number.
1271 The other 2 options are dealt with more fully in the security section.
1274 Secondly, it is used to store the login scripts for users and nodes.
1275 Currently this can only be done by the sysop but it is envisaged that
1276 eventually users will be able to set their own. An example is
1277 included in the distibution but here is a further example.
1294 The lines in between commands can simply insert a blank line or a
1295 character such as a + sign to make the output easier to read. Simply
1296 create this script with your favourite editor and save it with the
1297 callsign of the user as the filename. Filenames should always be in
1301 Commands can be inserted in the same way for nodes. A node may wish a
1302 series of commands to be issued on login, such as a merge command for
1306 Thirdly, there are 2 default scripts for users and nodes who do not
1307 have a specifically defined script. These are user_default and
1313 Spider allows the creation of local or remote databases. It supports
1314 chained databases, allowing several different databases to be scanned
1315 with one simple command. Importing of databases is limited at present
1316 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1317 database but will expand with time.
1320 5.1. Creating databases
1322 Creating a database could not be more simple. All the commands are
1323 sent from the cluster prompt as the sysop user.
1325 To create a database you use the command dbcreate. It can be used in
1326 3 different ways like so ..
1333 To simply create a database locally, you just tell the command the
1334 name of the database. This does not create the actual database, it
1335 simply defines it to say that it exists.
1339 dbcreate <name> chain <name> [<name>...]
1343 This creates a chained database entry. The first database will be
1344 scanned, then the second, the third etc...
1348 dbcreate <name> remote <name>
1352 This creates a remote entry. the first name field is the database
1353 name at the remote node, then the remote switch, then the actual
1354 node_call of the remote node, for example...
1358 dbcreate buckmaster remote gb7dxc
1362 Remote databases cannot be chained, however, the last database in a
1363 chain can be a remote database.
1366 5.2. Importing databases
1368 The only databases that Spider can currently import are the standard
1369 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1370 This will be added to with time.
1372 To import such a database, first put the file somewhere useful like
1373 /tmp and then issue the following command ...
1377 dbimport oblast /tmp/OBLAST.FUL
1381 This will update the existing local oblast database or create it if it
1385 5.3. Checking available databases
1387 Once a database is created, you will want to check that it has been
1388 added. To do this use the dbavail command. This will output the
1389 available databases. For example ...
1394 DB Name Location Chain
1398 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1402 5.4. Looking up databases
1404 To look for information in a defined database, simply use the dbshow
1405 command, for example ...
1409 dbshow buckmaster G0YLM
1413 will show the information for the callsign G0YLM from the buckmaster
1414 database if it exists. To make things more standard for the users you
1415 can add an entry in the Aliases file so that it looks like a standard
1416 show command like this ...
1420 Now you can simply use show/buckmaster or an abreviation.
1423 5.5. Removing databases
1425 To delete an existing database you use the dbremove command. For
1434 would remove the oblast database and its associated datafile from the
1435 system. There are no warnings or recovery possible from this command.
1436 If you remove a database it ceases to exist and would have to be
1437 created from scratch if you still required it.
1440 6. Information, files and useful programs
1444 One of the more important things a cluster sysop needs to do is to get
1445 information to his users. The simplest way to do this is to have a
1446 banner that is sent to the user on login. This is know as a "message
1447 of the day" or "motd". To set this up, simply create a file in
1448 /spider/data called motd and edit it to say whatever you want. It is
1449 purely a text file and will be sent automatically to anyone logging in
1453 This message of the day file lives in the same directory as the
1454 standard motd file but is only sent to non-registered users. Once
1455 registered they will receive the same message as any other user.
1458 6.3. Downtime message
1460 If for any reason the cluster is down, maybe for upgrade or
1461 maintenance but the machine is still running, a message can be sent to
1462 the user advising them of the fact. This message lives in the
1463 /spider/data directory and is called "offline". Simply create the
1464 file and edit it to say whatever you wish. This file will be sent to
1465 a user attempting to log into the cluster when DXSpider is not
1469 6.4. Other text messages
1471 You can set other text messages to be read by the user if they input
1472 the file name. This could be for news items or maybe information for
1473 new users. To set this up, make a directory under /spider called
1474 packclus. Under this directory you can create files called news or
1475 newuser for example. In fact you can create files with any names you
1476 like. These can be listed by the user with the command ....
1484 They can be read by the user by typing the command ....
1492 If the file they want to read is called news. You could also set an
1493 alias for this in the Alias file to allow them just to type news
1496 You can also store other information in this directory, either
1497 directly or nested under directories. One use for this would be to
1498 store DX bulletins such as the OPDX bulletins. These can be listed
1499 and read by the user. To keep things tidy, make a directory under
1500 /spider/packclus called bulletin. Now copy any OPDX or similar
1501 bulletins into it. These can be listed by the user in the same way as
1502 above using the show/files command with an extension for the bulletin
1503 directory you have just created, like this ....
1511 An example would look like this ....
1514 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1518 You can see that in the files area (basically the packclus directory)
1519 there is a file called news and a directory called bulletin. You can
1520 also see that dates they were created. In the case of the file news,
1521 you can also see the time it was last modified, a good clue as to
1522 whether the file has been updated since you last read it. To read the
1523 file called news you would simply issue the command ....
1531 To look what is in the bulletin directory you issue the command ....
1536 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1537 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1538 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1539 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1540 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1541 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1542 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1543 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1544 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1545 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1546 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1547 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1548 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1549 Press Enter to continue, A to abort (16 lines) >
1553 You can now read any file in this directory using the type command,
1558 type bulletin/opdx391
1559 Ohio/Penn DX Bulletin No. 391
1560 The Ohio/Penn Dx PacketCluster
1564 Editor Tedd Mirgliotta, KB8NW
1565 Provided by BARF-80 BBS Cleveland, Ohio
1566 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1567 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1568 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1569 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1570 Press Enter to continue, A to abort (508 lines) >
1574 The page length will of course depend on what you have it set to!
1577 6.5. The Aliases file
1579 You will find a file in /spider/cmd/ called Aliases. This is the file
1580 that controls what a user gets when issuing a command. It is also
1581 possible to create your own aliases for databases and files you create
1585 You should not alter the original file in /spider/cmd/ but create a
1586 new file with the same name in /spider/local_cmd. This means that any
1587 new Aliases files that is downloaded will not overwrite your self
1588 created Aliases and also that you do not override any new Aliases with
1589 your copy in /spider/local_cmd/. You must remember that any files you
1590 store in /spider/local/ or /spider/local_cmd override the originals if
1591 the same lines are used in both files.
1594 The best way of dealing with all this then is to only put your own
1595 locally created Aliases in the copy in /spider/local_cmd. The example
1596 below is currently in use at GB7MBC.
1601 # Local Aliases File
1608 '^news$', 'type news', 'type',
1611 '^sh\w*/buck$', 'show/qrz', 'show',
1612 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1613 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1614 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1615 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1621 Each alphabetical section should be preceded by the initial letter and
1622 the section should be wrapped in square brackets as you can see. The
1623 syntax is straightforward. The first section on each line is the new
1624 command that will be allowed once the alias is included. The second
1625 section is the command it is replacing and the last section is the
1626 actual command that is being used.
1629 The eagle-eyed amongst you will have noticed that in the first
1630 section, the new alias command has a '^' at the start and a '$' at the
1631 end. Basically these force a perfect match on the alias. The '^'
1632 says match the beginning exactly and the with similar commands.
1635 I have 3 different types of alias in this file. At the top is an
1636 alias for 'news'. This is a file I have created in the
1637 /spider/packclus/ directory where I can inform users of new
1638 developments or points of interest. In it's initial form a user would
1639 have to use the command type news. The alias allows them to simply
1640 type news to get the info. Second is an alias for the show/qrz
1641 command so that those users used to the original show/buck command in
1642 AK1A will not get an error, and the rest of the lines are for locally
1643 created databases so that a user can type show/hftest instead of
1644 having to use the command dbshow hftest which is not as intuitive.
1647 This file is just an example and you should edit it to your own
1648 requirements. Once created, simply issue the command load/alias at
1649 the cluster prompt as the sysop user and the aliases should be
1656 In later versions of Spider a simple console program is provided for
1657 the sysop. This has a type ahead buffer with line editing facilities
1658 and colour for spots, announces etc. To use this program, simply use
1659 console.pl instead of client.
1662 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1663 edit the file with your favourite editor.
1666 6.7. Updating kepler data
1668 Spider has a powerful and flexible show/satellite command. In order
1669 for this to be accurate, the kepler data has to be updated regularly.
1670 In general, this data is available as an email or via cluster mail.
1671 Updating it is simple. First you need to export the mail message as a
1672 file. You do this with the export command from the cluster prompt as
1673 the sysop. For example ...
1677 export 5467 /spider/perl/keps.in
1681 would export message number 5467 as a file called keps.in in the
1682 /spider/perl directory.
1685 Now login to a VT as sysop and cd /spider/perl. There is a command in
1686 the perl directory called convkeps.pl. All we need to do now is
1687 convert the file like so ...
1691 ./convkeps.pl keps.in
1695 Now go back to the cluster and issue the command ...
1703 That is it! the kepler data has been updated.
1706 6.8. The QRZ callbook
1708 The command sh/qrz will only work once you have followed a few simple
1709 steps. First you need to get a user ID and password from qrz.com.
1710 Simply go to the site and create one. Secondly you need to copy the
1711 file /spider/perl/Internet.pm to /spider/local and alter it to match
1712 your user ID and password. You also at this point need to set
1713 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1714 proprieter of qrz.com for allowing this access.
1717 6.9. Connecting logging programs
1719 There appear to be very few logging programs out there that support
1720 telnet especially the popular ones like LogEQF, Turbolog etc. This
1721 can make it difficult to connect to your own cluster! The way to do
1722 it is to make the logging program think it has a TNC attached to a com
1723 port on the logging PC and 'push' a linux login out to it. This is
1724 achieved very simply by the use of agetty.
1727 All that is required is to add a line in /etc/inittab to have the
1728 client ready for a connection on the com port of your choice.
1729 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1734 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1738 Add this after the standard runlevel lines in /etc/inittab. The above
1739 line works on ttyS1 (com2). Now as root, issue the command telinit q
1740 and it should be ready for connection. All that is required is a 3
1741 wire serial lead (tx, rx and signal ground). Tell you logging program
1742 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1743 Login as normal and then telnet from there to the cluster.
1748 In the spider tree will be a directory spider-web. This is a neat
1749 little java web applet that can be run from a website. The applet
1750 must run on the same machine as the cluster. The included README file
1754 I should comment here that the applet is precompiled, that is, ready
1755 to go. It was compiled using JDK1.3.1. If your version is earlier
1756 than this then it may not work. Should that be the case you need to
1757 recompile or update your JDK. To recompile do the following ...
1761 cd /spider/spider-web
1763 /usr/bin/javac spiderclient.java
1767 I have used /usr/bin/javac as an example, your path to javac may be
1773 Completely based on a clx web client written in Java by dl6dbh
1774 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1776 The webserver has to run on the same machine as your DxSpider software!
1778 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1780 Installation instructions (Performed as root):
1782 Put all the files in the spider-web directory into a newly created directory
1783 under the DocumentRoot of your websever for instance 'client'. In my case
1784 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1785 path should be /usr/local/httpd/htdocs/client/ for example.
1787 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1788 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1789 /usr/local/httpd/cgi-bin/ for example.
1791 Change the permissions of the files to ensure they are correct, obviously you
1792 will need to use the correct path the the files according to your system:
1794 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1795 chmod -R 755 /home/httpd/html/client/
1797 By default the spider.cgi script should pick up your hostname (As long as this
1798 is set correctly). If it does not or your hostname differs from the name that
1799 you attach to the public address that you are using, then edit spider.cgi :
1801 # Uncomment and set the hostname manually here if the above fails.
1802 # $HOSTNAME = "gb7mbc.spoo.org" ;
1806 telnet (see Listeners.pm)
1808 NOTE: If you can start the console but cannot connect to the cluster from it,
1809 then it is possible that the machine you are on cannot resolve the hostname of
1810 your cluster machine. If this is the case, you need to set your hostname
1813 You also need to set the $NODECALL variable. This prints the name of your
1814 choosing (probably your cluster callsign) on the html page.
1816 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1820 8. Web based statistics
1822 From version 1.50, you can use the freeware software MRTG to produce
1823 really nice graphical statistics on your web site. For an example try
1824 http://www.gb7mbc.net/mrtg/stats.html.
1827 The following should help you get it all working.
1830 First you need to download the latest version of MRTG from
1831 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1832 the following files..
1836 libpng-1.0.14.tar.gz
1842 Login to your machine as the root user, put all the downloaded files
1843 in /usr/local/src/ (or wherever you prefer) and untar and compile
1844 them. All the information to compile and install these sources come
1845 with them. After compilation and installation, you will find MRTG in
1849 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1853 You now need to make 2 symbolic links like below...
1857 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1858 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1862 Now login to the cluster with your sysop callsign and run the command
1866 Now you are nearly there! Login as the sysop user and change to the
1867 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1872 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1876 Changing the callsign for your own cluster callsign of course!
1879 And finally you need to login as the root user and create one last
1880 symbolic link. Where this points will depend on where your html
1881 documents are kept. For RedHat systems you use...
1885 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1889 and for SuSE systems...
1893 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1897 If you now point your browser to your website as below it should all
1902 http://www.xxx.xxx/mrtg/stats.html
1906 Of course, to get the stats to update, you need to add some
1907 information in the spider crontab file as below...
1911 # Update stats for mrtg on website
1912 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1916 This will update the site every 5 minutes.
1921 From version 1.49 DXSpider has some additional security features.
1922 These are not by any means meant to be exhaustive, however they do
1923 afford some security against piracy. These two new features can be
1924 used independently of each other or in concert to tighten the
1930 The basic principle of registration is simple. If a user is not
1931 registered by the sysop, then they have read-only access to the
1932 cluster. The only thing they can actually send is a talk or a message
1933 to the sysop. In order for them to be able to spot, send announces or
1934 talks etc the sysop must register them with the set/register command,
1943 The user g0vgs can now fully use the cluster. In order to enable
1944 registration, you can issue the command ...
1946 set/var $main::reqreg = 1
1950 Any users that are not registered will now see the motd_nor file
1951 rather than the motd file as discussed in the Information, files and
1952 useful programs section.
1955 Entering this line at the prompt will only last for the time the
1956 cluster is running of course and would not be present on a restart.
1957 To make the change permanent, add the above line to
1958 /spider/scripts/startup. To read more on the startup file, see the
1959 section on Information, files and useful programs.
1962 To unregister a user use unset/register and to show the list of
1963 registered users, use the command show/register.
1968 At the moment, passwords only affect users who login to a DXSpider
1969 cluster node via telnet. If a user requires a password, they can
1970 either set it themselves or have the sysop enter it for them by using
1971 the set/password command. Any users who already have passwords, such
1972 as remote sysops, will be asked for their passwords automatically by
1973 the cluster. Using passwords in this way means that the user has a
1974 choice on whether to have a password or not. To force the use of
1975 passwords at login, issue the command ...
1979 set/var $main::passwdreq = 1
1983 at the cluster prompt. This can also be added to the
1984 /spider/scripts/startup file as above to make the change permanent.
1987 Of course, if you do this you will have to assign a password for each
1988 of your users. If you were asking them to register, it is anticipated
1989 that you would ask them to send you a message both to ask to be
1990 registered and to give you the password they wish to use.
1993 Should a user forget their password, it can be reset by the sysop by
1994 first removing the existing password and then setting a new one like
1999 unset/password g0vgs
2000 set/password g0vgs new_password
2008 10.1. CVS from a Linux platform
2010 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2011 is held at Sourceforge. This means that it is possible to update your
2012 DXSpider installation to the latest sources by using a few simple
2013 commands. A graphical interface to CVS for Windows is explained in
2017 Please be aware that if you update your system using CVS, it is
2018 possible that you could be running code that is very beta and not
2019 fully tested. There is a possibility that it could be unstable.
2022 I am of course assuming that you have a machine with both DXSpider and
2023 Internet access running.
2026 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2027 ENTIRE SPIDER TREE!!
2030 Assuming you are connected to the Internet, you need to login to the
2031 CVS repository and then update your Spider source. There are several
2032 steps which are listed below ...
2035 First login as the user sysop. Next you need to connect to the CVS
2036 repository. You do this with the command below ...
2039 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2043 You will get a password prompt. Simply hit return here and your
2044 machine should return to a normal linux prompt.
2047 What happens next depends on whether you have an existing installation
2048 that you want to update with the latest and greatest or whether you
2049 just want to see what is there and/or run it on a new machine for
2052 If you are installing Spider from CVS then change directory to
2055 If you are wanting to update Spider then cd to /tmp
2058 The next step will create a brand new 'spider' directory in your
2062 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2066 This command is all on one line.
2069 Hopefully your screen should show you downloading files. The -z3
2070 simply compresses the download to improve speed. When this has
2071 finished, you will have exactly the same as if you had untarred a full
2072 tarball PLUS some extra directories and files that CVS needs to do the
2074 Now if you are doing a new installation, that's it. Carry on as if
2075 you have just downloaded and untarred the lastest tarball.
2078 If you want to upgrade your current installation then do this ...
2082 tar cvfz /tmp/s.tgz spider
2084 tar xvfzp /tmp/s.tgz
2088 This is assuming you downloaded to the /tmp directory of course.
2091 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2092 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2095 Remember to recompile the C client (cd /spider/src; make)
2098 At this point the files have been upgraded. You can (usually) restart
2099 the cluster in your own time. However, if you attempt to use any new
2100 commands or features expect it to be fatal! At least your cluster
2101 will have been restarted then so it will be too late to worry about
2105 Now the magic part! From now on when you want to update, simply
2106 connect to the Internet and then, as the user sysop ...
2115 and your files will be updated. As above, remember to recompile the
2116 "C" client if it has been updated (CVS will tell you) and restart if
2117 any of the perl scripts have been altered or added, again, CVS will
2121 You will find any changes documented in the /spider/Changes file.
2124 10.2. CVS from a Windows platform
2126 After the initial setup, an update to your DXSpider software is no
2127 more than a couple of clicks away. This section is intended to
2128 explain and illustrate the use of the WinCVS application to update
2129 your DXSpider software. The current stable version of WinCVS is Ver.
2130 1.2. You can get this software at:
2132 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2134 Pick your download mirror and then install WinCVS after the download
2138 In this next section I have included a series of links to .jpg files
2139 to take advantage of the picture and 1000 words equivalency. The .jpg
2140 files are in the C:\spider\html directory. If someone using a Linux
2141 system is reading this section from boredom, the files are in
2142 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2143 of gcvs and do your updates graphically as opposed to from the command
2144 line. The following descriptions are almost identical between WinCvs
2145 and gcvs. The following screen shots have duplicate links, depending
2146 upon whether you are viewing this information under the Windows or
2147 Linux operating system.
2149 When WinCVS is installed, running, and you are connected to the
2150 internet, the initial screen looks like:
2154 If you want, you can also look at these .jpg files with another viewer
2155 that might provide some better clarity to the image. On the left is
2156 the directory tree for your hard disk. Notice that the spider
2157 directory has a gray highlight.
2159 To start configuring WinCVS, click on Admin at the top of the screen
2160 and then Preferences. This should get you:
2164 In the top line for CVSROOT, enter:
2167 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2174 "passwd" file on the cvs server
2178 for Authentication on the General tab.
2180 Next, move to the right to the Ports tab.
2184 In here, check the box on the second line down for the "pserver" port.
2185 Enter a port number of 2401.
2187 Finally, go to the WinCvs tab all the way to the right.
2191 Enter Notepad as the viewer to open files. For the HOME folder, put
2192 "C:\spider" and click OK because the configuration is now complete.
2194 You are now ready to upgrade your copy of DXSpider. Click on the
2195 greyed Spider folder shown in the directory tree on the left of the
2196 WinCVS display. Two things should happen. The Spider folder will be
2197 selected and the greyed-out arrow located just below the word Query in
2198 the top line will turn to solid green.
2200 For anyone using gcvs under Linux, the green arrow is located on the
2201 extreme left of the display, under the word File. A gcvs screen looks
2206 Click on the now green arrow to start the download process. An Update
2207 Settings box will be displayed to which you can simply say OK.
2211 For future reference, the Update Settings box is the place where you
2212 can enter information to revert to a prior version of DXSpider.
2213 Information on reverting to a Before Date is contained in the WinCVS
2216 After a short period of time, a series of file names will scroll by in
2217 the lower pane of the WinCVS window. Eventually you should see
2220 *****CVS exited normally with code 0*****
2224 appear in the lower pane. You're done. The updated files are in
2225 place ready for you to stop and then restart your DXSpider. After the
2226 restart, you're running with the latest version of DXSpider.
2230 To paraphrase from the CVS section... Now the magic part! From now on
2231 when you want to update, simply connect to the Internet and start
2235 Click on the greyed-out Spider directory in the left screen
2236 Click on the green down arrow
2237 Click OK on the Update Settings dialog box
2238 Restart your Spider software
2242 11. The DXSpider command set
2246 accept Set a filter to accept something
2248 Create a filter to accept somethingThere are 2 types of filter, accept
2249 and reject. See HELP FILTERING for moreinfo.
2251 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
2253 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2256 This version allows a sysop to set a filter for a callsign as well as
2257 thedefault for nodes and users eg:-
2260 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2264 11.3. accept/announce [0-9] <pattern> (0)
2266 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2269 Create an 'accept this announce' line for a filter. An accept filter
2270 line means that if the announce matches this filter it ispassed onto
2271 the user. See HELP FILTERING for more info. Please read thisto
2272 understand how filters work - it will save a lot of grief later on.You
2273 can use any of the following things in this line:-
2276 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)
2283 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)
2297 acc/ann by_state va,nh,ri,nh
2301 You can use the tag 'all' to accept everything eg:
2308 but this probably for advanced users...
2310 11.4. accept/route <call> [0-9] <pattern> (8)
2312 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2315 Create an 'accept this routing PC Protocol' line for a filter. An
2316 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2317 filter it is passed thru that interface. See HELP FILTERING for more
2318 info. Please read thisto understand how filters work - it will save a
2319 lot of grief later on.You can use any of the following things in this
2323 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
2330 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2334 you can now use 'by' as a synonym for 'call' so:
2337 by = call by_dxcc = call_dxcc
2341 and so onYou can use the tag 'all' to accept everything eg:
2348 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
2350 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2352 This version allows a sysop to set a filter for a callsign as well as
2353 thedefault for nodes and users eg:-
2356 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2360 accept/spot user_default by G,M,2
2364 11.6. accept/spots [0-9] <pattern> (0)
2366 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2368 Create an 'accept this spot' line for a filter. An accept filter line
2369 means that if the spot matches this filter it ispassed onto the user.
2370 See HELP FILTERING for more info. Please read thisto understand how
2371 filters work - it will save a lot of grief later on.You can use any of
2372 the following things in this line:-
2375 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>
2379 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2383 You can use the tag 'all' to accept everything, eg:
2393 acc/spots by_state VA,NH,RI,MA,ME
2397 but this probably for advanced users...
2399 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
2401 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2403 This version allows a sysop to set a filter for a callsign as well as
2404 thedefault for nodes and users eg:-
2407 accept/wcy node_default all set/hops node_default 10
2411 11.8. accept/wcy [0-9] <pattern> (0)
2413 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2415 It is unlikely that you will want to do this, but if you do then you
2416 canfilter on the following fields:-
2419 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>
2423 There are no examples because WCY Broadcasts only come from one place
2424 andyou either want them or not (see UNSET/WCY if you don't want
2425 them).This command is really provided for future use.See HELP FILTER
2428 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
2430 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2432 This version allows a sysop to set a filter for a callsign as well as
2433 thedefault for nodes and users eg:-
2436 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2440 accept/wwv user_default by W,K
2444 11.10. accept/wwv [0-9] <pattern> (0)
2446 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2448 It is unlikely that you will want to do this, but if you do then you
2449 canfilter on the following fields:-
2452 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>
2459 accept/wwv by_zone 4
2463 is probably the only useful thing to do (which will only show WWV
2464 broadcastsby stations in the US).See HELP FILTER for information.
2466 11.11. announce <text> (0)
2468 announce <text> Send an announcement to LOCAL users only
2470 <text> is the text of the announcement you wish to broadcast
2472 11.12. announce full <text> (0)
2474 announce full <text> Send an announcement cluster wide
2476 This will send your announcement cluster wide
2478 11.13. announce sysop <text> (5)
2480 announce sysop <text> Send an announcement to Sysops only
2483 11.14. apropos <string> (0)
2485 apropos <string> Search help database for <string>
2487 Search the help database for <string> (it isn't case sensitive), and
2488 printthe names of all the commands that may be relevant.
2490 11.15. blank [<string>] [<nn>] (0)
2492 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2494 In its basic form this command prints one or more blank lines. However
2495 ifyou pass it a string it will replicate the string for the width of
2496 the screen (default 80) and then print that one or more times, so:
2503 prints two blank lines
2510 prints a row of - characters once.
2517 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2518 script file and you can print a maximumof 9 lines.
2522 bye Exit from the cluster
2524 This will disconnect you from the cluster
2526 11.17. catchup <node call> all|[<msgno> ...] (5)
2528 catchup <node call> all|[<msgno> ...] Mark a message as sent
2531 11.18. clear/announce <callsign> [input] [0-9|all] (8)
2533 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2536 A sysop can clear an input or normal output filter for a user or
2537 thenode_default or user_default.
2539 11.19. clear/announce [1|all] (0)
2541 clear/announce [1|all] Clear a announce filter line
2543 This command allows you to clear (remove) a line in a annouce filter
2544 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2547 11.20. clear/route <callsign> [input] [0-9|all] (8)
2549 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2551 A sysop can clear an input or normal output filter for a user or
2552 thenode_default or user_default.
2554 11.21. clear/route [1|all] (0)
2556 clear/route [1|all] Clear a route filter line
2558 This command allows you to clear (remove) a line in a route filter or
2559 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2562 11.22. clear/spots <callsign> [input] [0-9|all] (8)
2564 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2566 A sysop can clear an input or normal output filter for a user or
2567 thenode_default or user_default.
2569 11.23. clear/spots [0-9|all] (0)
2571 clear/spots [0-9|all] Clear a spot filter line
2573 This command allows you to clear (remove) a line in a spot filter or
2574 to remove the whole filter.If you have a filter:-
2577 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2587 you will be left with:-
2590 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2601 the filter will be completely removed.
2603 11.24. clear/wcy <callsign> [input] [0-9|all] (8)
2605 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2607 A sysop can clear an input or normal output filter for a user or
2608 thenode_default or user_default.
2610 11.25. clear/wcy [1|all] (0)
2612 clear/wcy [1|all] Clear a WCY filter line
2614 This command allows you to clear (remove) a line in a WCY filter or to
2615 remove the whole filter.see CLEAR/SPOTS for a more detailed
2618 11.26. clear/wwv <callsign> [input] [0-9|all] (8)
2620 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2622 A sysop can clear an input or normal output filter for a user or
2623 thenode_default or user_default.
2625 11.27. clear/wwv [1|all] (0)
2627 clear/wwv [1|all] Clear a WWV filter line
2629 This command allows you to clear (remove) a line in a WWV filter or to
2630 remove the whole filter.see CLEAR/SPOTS for a more detailed
2633 11.28. connect <callsign> (5)
2635 connect <callsign> Start a connection to another DX Cluster
2637 Start a connection process that will culminate in a new connection to
2638 theDX cluster <callsign>. This process creates a new 'client' process
2639 which willuse the script in /spider/connect/<callsign> to effect the
2640 'chat' exchangenecessary to traverse the network(s) to logon to the
2645 dbavail Show a list of all the Databases in the system
2647 Title says it all really, this command lists all the databases
2648 definedin the system. It is also aliased to SHOW/COMMAND.
2649 11.30. dbshow <dbname> <key> (0)
2651 dbshow <dbname> <key> Display an entry, if it exists, in a database
2653 This is the generic user interface to the database to the database
2654 system.It is expected that the sysop will add an entry to the local
2655 Aliases fileso that users can use the more familiar AK1A style of
2663 but if he hasn't and the database really does exist (use DBAVAIL
2664 orSHOW/COMMAND to find out) you can do the same thing with:
2671 11.31. directory (0)
2673 directory List messages
2676 11.32. directory <from>-<to> (0)
2678 directory <from>-<to> List messages <from> message <to> message
2680 List the messages in the messages directory.If there is a 'p' one
2681 space after the message number then it is a personal message. If there
2682 is a '-' between the message number and the'p' then this indicates
2683 that the message has been read.You can use shell escape characters
2684 such as '*' and '?' in the <call>fields.You can combine some of the
2685 various directory commands together eg:-
2695 DIR SUBJECT IOTA 200-250
2699 You can abbreviate all the commands to one letter and use ak1a syn-
2703 DIR/T G1* 10 DIR/S QSL 10-100 5
2707 11.33. directory <nn> (0)
2709 directory <nn> List last <nn> messages
2713 11.34. directory all (0)
2715 directory all List all messages
2718 11.35. directory from <call> (0)
2720 directory from <call> List all messages from <call>
2723 11.36. directory new (0)
2725 directory new List all new messages
2728 11.37. directory own (0)
2730 directory own List your own messages
2733 11.38. directory subject <string> (0)
2735 directory subject <string> List all messages with <string> in subject
2738 11.39. directory to <call> (0)
2740 directory to <call> List all messages to <call>
2743 11.40. directory- (5)
2747 Sysops can see all users' messages.
2749 11.41. disconnect <call> [<call> ...] (8)
2751 disconnect <call> [<call> ...] Disconnect a user or cluster
2753 Disconnect any <call> connected locally
2755 11.42. dx [by <call>] <freq> <call> <remarks> (0)
2757 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2759 This is how you send a DX Spot to other users. You can, in fact,
2760 nowenter the <freq> and the <call> either way round.
2763 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
2767 will all give the same result. You can add some remarks to the endof
2768 the command and they will be added to the spot.
2771 DX FR0G 144600 this is a test
2775 You can credit someone else by saying:-
2779 DX by G1TLH FR0G 144.600 he isn't on the cluster
2783 The <freq> is compared against the available bands set up in the clus-
2784 ter. See SHOW/BANDS for more information.
2786 11.43. echo <line> (0)
2788 echo <line> Echo the line to the output
2790 This command is useful in scripts and so forth for printing theline
2791 that you give to the command to the output. You can use thisin
2792 user_default scripts and the SAVE command for titling and so forthThe
2793 script will interpret certain standard "escape" sequences as follows:-
2796 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
2800 So the following example:-
2803 echo GB7DJK is a dxcluster
2810 GB7DJK is a dxcluster
2814 on the output. You don't need a \n on the end of the line you want to
2815 send.A more complex example:-
2818 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
2825 GB7DJK g1tlh Dirk g3xvf Richard
2831 11.44. filtering... (0)
2833 filtering... Filtering things in DXSpider
2835 There are a number of things you can filter in the DXSpider system.
2836 Theyall use the same general mechanism.In general terms you can create
2837 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
2838 You do this using, for example:-
2841 accept/spots ..... reject/spots .....
2845 where ..... are the specific commands for that type of filter. There-
2846 are filters for spots, wwv, announce, wcy and (for sysops)connects.
2847 See each different accept or reject command reference formore
2848 details.There is also a command to clear out one or more lines in a
2849 filter andone to show you what you have set. They are:-
2852 clear/spots 1 clear/spots all
2863 There is clear/xxxx command for each type of filter.For now we are
2864 going to use spots for the examples, but you can applythe principles
2865 to all types of filter.There are two main types of filter 'accept' or
2866 'reject'; which you usedepends entirely on how you look at the world
2867 and what is leastwriting to achieve what you want. Each filter has 10
2868 lines (of anylength) which are tried in order. If a line matches then
2869 the actionyou have specified is taken (ie reject means ignore it and
2870 acceptmeans gimme it).The important thing to remember is that if you
2871 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
2872 instance)) then ifa spot comes in that doesn't match any of the lines
2873 then you will getit BUT if you specify an 'accept' filter then any
2874 spots that don'tmatch are dumped. For example if I have a one line
2878 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2882 then automatically you will ONLY get VHF spots from or to CQ zones
2883 1415 and 16. If you set a reject filter like:
2886 reject/spots on hf/cw
2890 Then you will get everything EXCEPT HF CW spots, If you am interested
2891 in IOTAand will work it even on CW then you could say:-
2894 reject/spots on hf/cw and not info iota
2898 But in that case you might only be interested in iota and say:-
2901 accept/spots not on hf/cw or info iota
2905 which is exactly the same. You should choose one or the other untilyou
2906 are confortable with the way it works. Yes, you can mix them(actually
2907 you can have an accept AND a reject on the same line) butdon't try
2908 this at home until you can analyse the results that you getwithout
2909 ringing up the sysop for help.Another useful addition now is filtering
2911 accept/spots by_state VA,NH,RI,ME
2915 You can arrange your filter lines into logical units, either for
2916 yourown understanding or simply convenience. I have one set fre-
2920 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2924 What this does is to ignore all HF CW spots (being a class B I
2925 can'tread any CW and couldn't possibly be interested in HF :-) and
2926 alsorejects any spots on VHF which don't either originate or spot
2927 someonein Europe.This is an exmaple where you would use the line num-
2928 ber (1 and 2 inthis case), if you leave the digit out, the system
2929 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
2930 out if you want, it is implied. You canuse any number of brackets to
2931 make the 'expression' as you wantit. There are things called prece-
2932 dence rules working here which meanthat you will NEED brackets in a
2933 situation like line 2 because,without it, will assume:-
2936 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2940 annoying, but that is the way it is. If you use OR - usebrackets.
2941 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
2942 by_zone'.If you want to alter your filter you can just redefine one or
2943 morelines of it or clear out one line. For example:-
2946 reject/spots 1 on hf/ssb
2957 To remove the filter in its entirty:-
2964 There are similar CLEAR commands for the other filters:-
2967 clear/announce clear/wcy clear/wwv
2971 ADVANCED USERS:-Once you are happy with the results you get, you may
2972 like to experiment. my example that filters hf/cw spots and accepts
2973 vhf/uhf spots from EUcan be written with a mixed filter, eg:
2977 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)
2981 each filter slot actually has a 'reject' slot and an 'accept'slot. The
2982 reject slot is executed BEFORE the accept slot.It was mentioned ear-
2983 lier that after a reject test that doesn't match,the default for fol-
2984 lowing tests is 'accept', the reverse is true for'accept'. In the
2985 example what happens is that the reject is executedfirst, any non
2986 hf/cw spot is passed to the accept line, which letsthru everything
2987 else on HF.The next filter line lets through just VHF/UHF spots from
2990 11.45. forward/latlong <node_call> (8)
2992 forward/latlong <node_call> Send latitude and longitude information to
2995 This command sends all the latitude and longitude information that
2996 yourcluster is holding against callsigns. One advantage of recieving
2997 thisinformation is that more locator information is held by you.
2998 Thismeans that more locators are given on the DX line assuming you
2999 haveSET/DXGRID enabled. This could be a LOT of information though,
3000 soit is not recommended on slow links.
3002 11.46. forward/opernam <call> (1)
3004 forward/opernam <call> Send out information on this <call> to all
3007 This command sends out any information held in the user file which can
3008 be broadcast in PC41 protocol packets. This information is Name, QTH,
3009 Locationand Homenode. PC41s are only sent for the information that is
3014 help The HELP Command
3016 HELP is available for a number of commands. The syntax is:-
3023 Where <cmd> is the name of the command you want help on.All commands
3024 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3025 can be shortened to AN and so on.Look at the APROPOS <string> command
3026 which will search the help databasefor the <string> you specify and
3027 give you a list of likely commandsto look at with HELP.
3029 11.48. init <node> (5)
3031 init <node> Re-initialise a link to an AK1A compatible node
3033 This command attempts to re-initialise a link to a (usually) AK1A
3034 nodethat has got confused, usually by a protocol loop of some kind. It
3035 maywork - but you usually will be better off simply disconnecting it
3036 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3037 <yournode>).Best of luck - you will need it.
3043 As a sysop you can kill any message on the system.
3045 11.50. kill <from msgno>-<to msgno> (0)
3047 kill <from msgno>-<to msgno> Delete a range of messages
3050 11.51. kill <from>-<to> (5)
3052 kill <from>-<to> Remove a range of messages from the system
3055 11.52. kill <msgno> [<msgno..] (0)
3057 kill <msgno> [<msgno..] Delete a message from the local system
3060 11.53. kill <msgno> [<msgno> ...] (0)
3062 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3064 You can get rid of any message to or originating from your callsign
3065 using this command. You can remove more than one message at a time.
3067 11.54. kill expunge <msgno> [<msgno..] (6)
3069 kill expunge <msgno> [<msgno..] Expunge a message
3071 Deleting a message using the normal KILL commands only marks that
3072 messagefor deletion. The actual deletion only happens later (usually
3073 two days later).The KILL EXPUNGE command causes the message to be
3074 truly deleted more or lessimmediately.It otherwise is used in the same
3075 way as the KILL command.
3077 11.55. kill from <call> (5)
3079 kill from <call> Remove all messages from a callsign
3082 11.56. kill full <msgno> [<msgno..] (5)
3084 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3086 Delete a message from the local system. You will only be able todelete
3087 messages that you have originated or been sent (unless you arethe
3095 Will delete all the messages that you own between msgnos 1234 and
3103 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3109 will delete all messages to g1tlh.
3116 will delete a message (usually a 'bulletin') from the whole cluster
3117 system. This uses the subject field, so any messages that have exactly
3118 thesame subject will be deleted. Beware!
3120 11.57. kill full <msgno> [<msgno] (5)
3122 kill full <msgno> [<msgno] Remove a message from the entire cluster
3124 Remove this message from the entire cluster system as well as your
3127 11.58. kill to <call> (5)
3129 kill to <call> Remove all messages to a callsign
3132 11.59. kill from <regex> (0)
3134 kill from <regex> Delete messages FROM a callsign or pattern
3137 11.60. kill to <regex> (0)
3139 kill to <regex> Delete messages TO a callsign or pattern
3144 links Show which nodes is physically connected
3146 This is a quick listing that shows which links are connected andsome
3147 information about them. See WHO for a list of all connections.
3149 11.62. load/keps (5)
3151 load/keps Load new keps data
3154 11.63. load/keps [nn] (5)
3156 load/keps [nn] Load new keps data from message
3158 If there is no message number then reload the current Keps data
3159 fromthe Keps.pm data file. You create this file by running
3162 /spider/perl/convkeps.pl <filename>
3166 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3167 there is a message number, then it will take the message, runcon-
3168 vkeps.pl on it and then load the data, all in one step.These messages
3169 are sent to ALL by GB7DJK (and others) from time to time.
3171 11.64. merge <node> [<no spots>/<no wwv>] (5)
3173 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3175 MERGE allows you to bring your spot and wwv database up to date. By
3176 defaultit will request the last 10 spots and 5 WWVs from the node you
3177 select. The node must be connected locally.You can request any number
3178 of spots or wwv and although they will be appendedto your databases
3179 they will not duplicate any that have recently been added (the last 2
3180 days for spots and last month for WWV data).
3182 11.65. pc <call> <text> (8)
3184 pc <call> <text> Send arbitrary text to a connected callsign
3186 Send some arbitrary text to a locally connected callsign. Noprocessing
3187 is done on the text. This command allows you to send PCProtocol to
3188 unstick things if problems arise (messages get stucketc). eg:-
3191 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3198 pc G1TLH Try doing that properly!!!
3202 Send any text you like to the callsign requested. This is used mainly
3203 to sendPC protocol to connected nodes either for testing or to unstick
3204 things. You can also use in the same way as a talk command to a con-
3205 nected user butwithout any processing, added of "from <blah> to <blah"
3208 11.66. ping <node call> (1)
3210 ping <node call> Check the link quality between nodes
3212 This command allows you to send a frame to another cluster node onthe
3213 network and get a return frame. The time it takes to do thisis a good
3214 indication of the quality of the link. The actual timeit takes is
3215 output to the console in seconds.Any visible cluster node can be
3218 11.67. rcmd <node call> <cmd> (1)
3220 rcmd <node call> <cmd> Send a command to another DX Cluster
3222 This command allows you to send nearly any command to another DX
3223 Clusternode that is connected to the system. Whether you get any
3224 output is dependant on a) whether the other system knowsthat the node
3225 callsign of this cluster is in fact a node b) whether theother system
3226 is allowing RCMDs from this node and c) whether you havepermission to
3227 send this command at all.
3231 read Read the next unread personal message addressed to you
3234 11.69. read <msgno> (0)
3236 read <msgno> Read the specified message
3238 You can read any messages that are sent as 'non-personal' and also
3239 anymessage either sent by or sent to your callsign.
3245 As a sysop you may read any message on the system
3249 reject Set a filter to reject something
3251 Create a filter to reject somethingThere are 2 types of filter, accept
3252 and reject. See HELP FILTERING for moreinfo.
3254 11.72. reject/announce <call> [input] [0-9] <pattern> (8)
3256 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3259 This version allows a sysop to set a filter for a callsign as well as
3260 thedefault for nodes and users eg:-
3263 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3267 11.73. reject/announce [0-9] <pattern> (0)
3269 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3272 Create an 'reject this announce' line for a filter. A reject filter
3273 line means that if the announce matches this filter it ispassed onto
3274 the user. See HELP FILTERING for more info. Please read thisto
3275 understand how filters work - it will save a lot of grief later on.You
3276 can use any of the following things in this line:-
3279 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)
3286 rej/ann by_zone 14,15,16 and not by G,M,2
3290 You can use the tag 'all' to reject everything eg:
3297 but this probably for advanced users...
3299 11.74. reject/route <call> [0-9] <pattern> (8)
3301 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3304 Create an 'reject this routing PC Protocol' line for a filter. An
3305 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3306 filter it is NOT passed thru that interface. See HELP FILTERING for
3307 more info. Please read this to understand how filters work - it will
3308 save a lot of grief later on.You can use any of the following things
3312 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
3319 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3323 You can use the tag 'all' to reject everything eg:
3326 rej/route all (equiv to [very] restricted mode)
3330 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3332 11.75. reject/spots <call> [input] [0-9] <pattern> (8)
3334 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3336 This version allows a sysop to set a filter for a callsign as well as
3337 thedefault for nodes and users eg:-
3340 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3344 reject/spot user_default by G,M,2
3348 11.76. reject/spots [0-9] <pattern> (0)
3350 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3352 Create a 'reject this spot' line for a filter. A reject filter line
3353 means that if the spot matches this filter it isdumped (not passed
3354 on). See HELP FILTERING for more info. Please read thisto understand
3355 how filters work - it will save a lot of grief later on.You can use
3356 any of the following things in this line:-
3359 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>
3363 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3367 You can use the tag 'all' to reject everything eg:
3374 but this probably for advanced users...
3376 11.77. reject/wcy <call> [input] [0-9] <pattern> (8)
3378 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3380 This version allows a sysop to set a filter for a callsign as well as
3381 thedefault for nodes and users eg:-
3384 reject/wcy gb7djk all
3388 11.78. reject/wcy [0-9] <pattern> (0)
3390 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3392 It is unlikely that you will want to do this, but if you do then you
3393 canfilter on the following fields:-
3396 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>
3400 There are no examples because WCY Broadcasts only come from one place
3401 andyou either want them or not (see UNSET/WCY if you don't want
3402 them).This command is really provided for future use.See HELP FILTER
3405 11.79. reject/wwv <call> [input] [0-9] <pattern> (8)
3407 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3409 This version allows a sysop to set a filter for a callsign as well as
3410 thedefault for nodes and users eg:-
3413 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3417 reject/wwv user_default by W
3421 11.80. reject/wwv [0-9] <pattern> (0)
3423 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3425 It is unlikely that you will want to do this, but if you do then you
3426 canfilter on the following fields:-
3429 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>
3436 reject/wwv by_zone 14,15,16
3440 is probably the only useful thing to do (which will only show WWV
3441 broadcastsby stations in the US).See HELP FILTER for information.
3445 reply Reply (privately) to the last message that you have read
3448 11.82. reply <msgno> (0)
3450 reply <msgno> Reply (privately) to the specified message
3453 11.83. reply b <msgno> (0)
3455 reply b <msgno> Reply as a Bulletin to the specified message
3458 11.84. reply noprivate <msgno> (0)
3460 reply noprivate <msgno> Reply as a Bulletin to the specified message
3463 11.85. reply rr <msgno> (0)
3465 reply rr <msgno> Reply to the specified message with read receipt
3467 You can reply to a message and the subject will automatically
3468 have"Re:" inserted in front of it, if it isn't already present.You can
3469 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3470 that you can use with the SEND command (see SENDfor further details)
3472 11.86. send <call> [<call> ...] (0)
3474 send <call> [<call> ...] Send a message to one or more callsigns
3477 11.87. send copy <msgno> <call> (0)
3479 send copy <msgno> <call> Send a copy of a message to someone
3482 11.88. send noprivate <call> (0)
3484 send noprivate <call> Send a message to all stations
3486 All the SEND commands will create a message which will be sent either
3487 toan individual callsign or to one of the 'bulletin' addresses. SEND
3488 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3489 will mark the message as personal and send it to the cluster node
3490 thatthat callsign is connected to. If the <call> you have specified is
3491 in facta known bulletin category on your node (eg: ALL) then the
3492 message shouldautomatically become a bulletin.You can have more than
3493 one callsign in all of the SEND commands.You can have multiple
3494 qualifiers so that you can have for example:-
3495 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3499 which should send a copy of message 123 to G1TLH and G0RDI and you
3500 willreceive a read receipt when they have read the message.SB is an
3501 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3502 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3503 tionally this should be no longer than 29 characters for compatibil-
3504 ity. Most modern clustersoftware should accept more.You will now be
3505 prompted to start entering your text. You finish the message by enter-
3506 ing '/EX' on a new line. For instance:
3509 ... bye then Jim 73 Dirk /ex
3513 If you have started a message and you don't want to keep it then you-
3514 can abandon the message with '/ABORT' on a new line, like:-
3517 line 1 line 2 oh I just can't be bothered with this /abort
3521 If you abort the message it will NOT be sent.When you are entering the
3522 text of your message, most normal output (suchas DX announcements and
3523 so on are suppressed and stored for latter display(upto 20 such lines
3524 are stored, as new ones come along, so the oldestlines are
3525 dropped).Also, you can enter normal commands commands (and get the
3526 output immediately) whilst in the middle of a message. You do this by
3527 typingthe command preceeded by a '/' character on a new line, so:-
3530 /dx g1tlh 144010 strong signal
3534 Will issue a dx annoucement to the rest of the cluster. Also, you can
3535 add the output of a command to your message by preceeding the command
3543 This will show YOU the output from SH/VHFTABLE and also store it in
3544 themessage. You can carry on with the message until you are ready to
3547 11.89. send private <call> (0)
3549 send private <call> Send a personal message
3552 11.90. send rr <call> (0)
3554 send rr <call> Send a message and ask for a read receipt
3557 11.91. set/address <your address> (0)
3559 set/address <your address> Record your postal address
3561 11.92. set/announce (0)
3563 set/announce Allow announce messages to come out on your terminal
3566 11.93. set/anntalk (0)
3568 set/anntalk Allow talk like announce messages on your terminal
3571 11.94. set/arcluster <call> [<call>..] (5)
3573 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
3576 11.95. set/baddx <call>.. (8)
3578 set/baddx <call>.. Stop callsigns in a dx spot being propagated
3581 11.96. set/badnode <call>.. (8)
3583 set/badnode <call>.. Stop spots from this node being propagated
3586 11.97. set/badspotter <call>.. (8)
3588 set/badspotter <call>.. Stop spots from this callsign being propagated
3591 11.98. set/badword <word>.. (8)
3593 set/badword <word>.. Stop things with this word being propagated
3596 11.99. set/bbs <call> [<call>..] (5)
3598 set/bbs <call> [<call>..] Make the callsign a BBS
3601 11.100. set/beep (0)
3603 set/beep Add a beep to DX and other messages on your terminal
3606 11.101. set/clx <call> [<call>..] (5)
3608 set/clx <call> [<call>..] Make the callsign an CLX node
3613 set/dx Allow DX messages to come out on your terminal
3616 11.103. set/dxcq (0)
3618 set/dxcq Show CQ Zones on the end of DX announcements
3621 11.104. set/dxgrid (0)
3623 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
3627 11.105. set/dxitu (0)
3629 set/dxitu Show ITU Zones on the end of DX announcements
3632 11.106. set/dxnet <call> [<call>..] (5)
3634 set/dxnet <call> [<call>..] Make the callsign an DXNet node
3637 11.107. set/echo (0)
3639 set/echo Make the cluster echo your input
3642 11.108. set/email <email> ... (0)
3644 set/email <email> ... Set email address(es) and forward your personals
3647 11.109. set/here (0)
3649 set/here Tell the system you are present at your terminal
3652 11.110. set/homenode <node> (0)
3654 set/homenode <node> Set your normal cluster callsign
3656 Tell the cluster system where you normally connect to. Any Messages
3657 sentto you will normally find their way there should you not be
3665 11.111. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
3667 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
3670 11.112. set/language <lang> (0)
3672 set/language <lang> Set the language you want to use
3674 You can select the language that you want the cluster to use.
3675 Currentlythe languages available are en (English), de (German), es
3676 (Spanish) and nl (Dutch).
3678 11.113. set/location <lat & long> (0)
3680 set/location <lat & long> Set your latitude and longitude
3683 11.114. set/logininfo (0)
3685 set/logininfo Inform when a station logs in locally
3688 11.115. set/name <your name> (0)
3690 set/name <your name> Set your name
3692 Tell the system what your name is eg:-
3699 11.116. set/node <call> [<call>..] (5)
3701 set/node <call> [<call>..] Make the callsign an AK1A cluster
3703 Tell the system that the call(s) are to be treated as AK1A cluster
3704 andfed PC Protocol rather normal user commands.
3706 11.117. set/obscount <count> <call> (8)
3708 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
3710 From 1.35 onwards neighbouring nodes are pinged at regular intervals
3711 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
3712 'pump-up'counter which is decremented on every outgoing ping and then
3713 reset tothe 'obscount' value on every incoming ping. The default value
3714 of thisparameter is 2. What this means is that a neighbouring node
3715 will be pinged twice at (default) 300 second intervals and if no reply
3716 has been heard just beforewhat would be the third attempt, that node
3717 is disconnected.If a ping is heard then the obscount is reset to the
3718 full value. Usingdefault values, if a node has not responded to a ping
3719 within 15 minutes,it is disconnected.You can set this parameter
3720 between 1 and 9.It is STRONGLY recommended that you don't change the
3723 11.118. set/page <lines per page> (0)
3725 set/page <lines per page> Set the lines per page
3727 Tell the system how many lines you wish on a page when the number of
3728 lineof output from a command is more than this. The default is 20.
3729 Setting itexplicitly to 0 will disable paging.
3732 SET/PAGE 30 SET/PAGE 0
3736 The setting is stored in your user profile.
3738 11.119. set/password (0)
3740 set/password Set your own password
3742 This command only works for a 'telnet' user (currently). It willonly
3743 work if you have a password already set. This initial passwordcan only
3744 be set by the sysop.When you execute this command it will ask you for
3745 your old password,then ask you to type in your new password twice (to
3746 make sure youget it right). You may or may not see the data echoed on
3747 the screenas you type, depending on the type of telnet client you
3750 11.120. set/prompt <string> (0)
3752 set/prompt <string> Set your prompt to <string>
3756 11.121. set/qra <locator> (0)
3758 set/qra <locator> Set your QRA Grid locator
3760 Tell the system what your QRA (or Maidenhead) locator is. If you have
3761 notdone a SET/LOCATION then your latitude and longitude will be set
3762 roughlycorrectly (assuming your locator is correct ;-). For example:-
3769 11.122. set/qth <your qth> (0)
3771 set/qth <your qth> Set your QTH
3773 Tell the system where you are. For example:-
3776 SET/QTH East Dereham, Norfolk
3780 11.123. set/spider <call> [<call>..] (5)
3782 set/spider <call> [<call>..] Make the callsign an DXSpider node
3784 Tell the system that the call(s) are to be treated as DXSpider node
3785 andfed new style DX Protocol rather normal user commands.
3787 11.124. set/talk (0)
3789 set/talk Allow TALK messages to come out on your terminal
3792 11.125. set/usstate (0)
3794 set/usstate Allow US State info on the end of DX announcements
3799 set/wcy Allow WCY messages to come out on your terminal
3804 set/wwv Allow WWV messages to come out on your terminal
3809 set/wx Allow WX messages to come out on your terminal
3812 11.129. show/baddx (1)
3814 show/baddx Show all the bad dx calls in the system
3816 Display all the bad dx callsigns in the system, see SET/BADDXfor more
3820 11.130. show/badnode (1)
3822 show/badnode Show all the bad nodes in the system
3824 Display all the bad node callsigns in the system, see SET/BADNODEfor
3827 11.131. show/badspotter (1)
3829 show/badspotter Show all the bad spotters in the system
3831 Display all the bad spotter's callsigns in the system, see
3832 SET/BADSPOTTERfor more information.
3834 11.132. show/badword (1)
3836 show/badword Show all the bad words in the system
3838 Display all the bad words in the system, see SET/BADWORDfor more
3841 11.133. show/configuration [<node>] (0)
3843 show/configuration [<node>] Show all the nodes and users visible
3845 This command allows you to see all the users that can be seenand the
3846 nodes to which they are connected.This command is normally abbreviated
3847 to: sh/cNormally, the list returned will be just for the nodes from
3848 your country (because the list otherwise will be very long).
3855 will produce a complete list of all nodes. BE WARNED: the list that is
3856 returned can be VERY longIt is possible to supply a node or part of a
3857 prefix and you will get a list of the users for that node or list of
3858 nodes starting withthat prefix.
3869 11.134. show/configuration/node (0)
3871 show/configuration/node Show all the nodes connected locally
3873 Show all the nodes connected to this node.
3875 11.135. show/connect (1)
3877 show/connect Show all the active connections
3879 This command shows information on all the active connections known
3880 tothe node. This command gives slightly more information than WHO.
3883 11.136. show/date [<prefix>|<callsign>] (0)
3885 show/date [<prefix>|<callsign>] Show the local time
3887 This is very nearly the same as SHOW/TIME, the only difference the
3888 formatof the date string if no arguments are given.If no prefixes or
3889 callsigns are given then this command returns the localtime and UTC as
3890 the computer has it right now. If you give some prefixesthen it will
3891 show UTC and UTC + the local offset (not including DST) atthe prefixes
3892 or callsigns that you specify.
3894 11.137. show/db0sdx <callsign> (0)
3896 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
3898 This command queries the DB0SDX QSL server on the internetand returns
3899 any information available for that callsign. This serviceis provided
3900 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
3905 show/dx Interrogate the spot database
3907 If you just type SHOW/DX you will get the last so many spots(sysop
3908 configurable, but usually 10).In addition you can add any number of
3909 these commands in very nearlyany order to the basic SHOW/DX command,
3913 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>
3917 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
3921 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
3925 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
3929 info <text> - any spots containing <text> in the info or remarks
3933 by <call> - any spots spotted by <call> (spotter <call> is the same).
3937 qsl - this automatically looks for any qsl info on the call held in the spot database.
3941 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.
3945 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
3949 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
3953 You can also use this with the 'by' keyword so eg by W dxcc
3961 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
3965 11.139. show/dxcc <prefix> (0)
3967 show/dxcc <prefix> Interrogate the spot database by country
3969 This command takes the <prefix> (which can be a full or partial
3970 callsign if desired), looks up which internal country number it isand
3971 then displays all the spots as per SH/DX for that country.This is now
3972 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
3976 SH/DXCC G SH/DXCC W on 20m iota
3980 This can be done with the SHOW/DX command like this:-
3983 SH/DX dxcc g SH/DX dxcc w on 20m iota
3987 11.140. show/dxstats [days] [date] (0)
3989 show/dxstats [days] [date] Show the DX Statistics
3991 Show the total DX spots for the last <days> no of days (default is
3992 31), starting from a <date> (default: today).
3994 11.141. show/files [<filearea> [<string>]] (0)
3996 show/files [<filearea> [<string>]] List the contents of a filearea
3998 SHOW/FILES on its own will show you a list of the various
3999 fileareasavailable on the system. To see the contents of a particular
4007 where <filearea> is the name of the filearea you want to see the con-
4008 tents of.You can also use shell globbing characters like '*' and '?'
4009 in astring to see a selection of files in a filearea eg:-
4012 SH/FILES bulletins arld*
4016 See also TYPE - to see the contents of a file.
4018 11.142. show/filter (0)
4020 show/filter Show the contents of all the filters you have set
4022 Show the contents of all the filters that are set. This command
4023 displaysall the filters set - for all the various categories.
4025 11.143. show/hfstats [days] [date] (0)
4027 show/hfstats [days] [date] Show the HF DX Statistics
4029 Show the HF DX spots breakdown by band for the last <days> no of days
4030 (default is 31), starting from a <date> (default: today).
4032 11.144. show/hftable [days] [date] [prefix ...] (0)
4034 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4036 Show the HF DX Spotter table for the list of prefixes for the last
4037 <days> no of days (default is 31), starting from a <date> (default:
4038 today).If there are no prefixes then it will show the table for your
4039 country.Remember that some countries have more than one "DXCC country"
4040 in them(eg G :-), to show them (assuming you are not in G already
4041 which isspecially treated in the code) you must list all the relevant
4045 sh/hftable g gm gd gi gj gw gu
4049 Note that the prefixes are converted into country codes so you don't
4050 haveto list all possible prefixes for each country.If you want more or
4051 less days than the default simply include thenumber you require:-
4057 If you want to start at a different day, simply add the date in some
4061 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4065 This will show the stats for your DXCC for that CQWW contest weekend.
4066 You can specify either prefixes or full callsigns (so you can see how
4067 youdid against all your mates). You can also say 'all' which will then
4068 printthe worldwide statistics.
4075 11.145. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4077 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4080 This command shows the hop counts set up for a node. You can
4081 specifywhich category you want to see. If you leave the category out
4082 then all the categories will be listed.
4084 11.146. show/isolate (1)
4086 show/isolate Show list of ISOLATED nodes
4089 11.147. show/log [<callsign>] (8)
4091 show/log [<callsign>] Show excerpts from the system log
4093 This command outputs a short section of the system log. On its ownit
4094 will output a general logfile. With the optional callsign it willshow
4095 output from the log associated with that callsign.
4097 11.148. show/moon [ndays] [<prefix>|<callsign>] (0)
4099 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4101 Show the Moon rise and set times for a (list of) prefixes or
4102 callsigns, together with the azimuth and elevation of the sun
4103 currently at thoselocations.If you don't specify any prefixes or
4104 callsigns, it will show the times foryour QTH (assuming you have set
4105 it with either SET/LOCATION or SET/QRA),together with the current
4106 azimuth and elevation.In addition, it will show the illuminated
4107 fraction of the moons disk.If all else fails it will show the Moonrise
4108 and set times for the nodethat you are connected to. For example:-
4111 SH/MOON SH/MOON G1TLH W5UN
4115 You can also use this command to see into the past or the future, soif
4116 you want to see yesterday's times then do:-
4122 or in three days time:-
4129 Upto 366 days can be checked both in the past and in the future.Please
4130 note that the rise and set times are given as the UT times of rise and
4131 set on the requested UT day.
4133 11.149. show/muf <prefix> [<hours>][long] (0)
4135 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4138 This command allow you to estimate the likelihood of you contactinga
4139 station with the prefix you have specified. The output assumes a
4140 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4141 0.15muV/10dB SINAD)The result predicts the most likely operating
4142 frequencies and signallevels for high frequency (shortwave) radio
4143 propagation paths onspecified days of the year and hours of the day.
4144 It is most useful forpaths between 250 km and 6000 km, but can be used
4145 with reduced accuracyfor paths shorter or longer than this.The command
4146 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4147 predict the MUF given the predicted flux, day of the year,hour of the
4148 day and geographic coordinates of the transmitter andreceiver. This
4149 routine is reasonably accurate for the purposes here,with a claimed
4150 RMS error of 3.8 MHz, but much smaller and less complexthan the
4151 programs used by major shortwave broadcasting organizations,such as
4152 the Voice of America.The command will display some header information
4153 detailing itsassumptions, together with the locations, latitude and
4154 longitudes andbearings. It will then show UTC (UT), local time at the
4155 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4156 the path(Zen) and the likely signal strengths. Then for each frequency
4157 for whichthe system thinks there is a likelihood of a circuit it
4158 prints a value.The value is currently a likely S meter reading based
4159 on the conventional6dB / S point scale. If the value has a '+'
4160 appended it means that it is1/2 an S point stronger. If the value is
4161 preceeded by an 'm' it means thatthere is likely to be much fading and
4162 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4163 will show the next two hours worth of data. Youcan specify anything up
4164 to 24 hours worth of data by appending the no ofhours required after
4165 the prefix. For example:-
4175 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
4179 indicating that you will have weak, fading circuits on top band and
4180 80m but usable signals on 40m (about S3).inputing:-
4188 will get you the above display, but with the next 24 hours worth
4192 SH/MUF W L 24 SH/MUF W 24 Long
4196 Gives you an estimate of the long path propagation characterics.
4197 Itshould be noted that the figures will probably not be very useful,
4198 norterrible accurate, but it is included for completeness.
4200 11.150. show/newconfiguration [<node>] (0)
4202 show/newconfiguration [<node>] Show all the nodes and users visible
4204 This command allows you to see all the users that can be seenand the
4205 nodes to which they are connected. This command produces essentially
4206 the same information as SHOW/CONFIGURATION except that it shows all
4207 the duplication ofany routes that might be present It also uses a
4208 different formatwhich may not take up quite as much space if you don't
4209 have anyloops.BE WARNED: the list that is returned can be VERY long
4211 11.151. show/newconfiguration/node (0)
4213 show/newconfiguration/node Show all the nodes connected locally
4215 Show all the nodes connected to this node in the new format.
4217 11.152. show/node [<callsign> ...] (1)
4219 show/node [<callsign> ...] Show the type and version number of nodes
4221 Show the type and version (if connected) of the nodes specified on
4222 thecommand line. If no callsigns are specified then a sorted list of
4223 allthe non-user callsigns known to the system will be displayed.
4225 11.153. show/prefix <callsign> (0)
4227 show/prefix <callsign> Interrogate the prefix database
4229 This command takes the <callsign> (which can be a full or partial
4230 callsign or a prefix), looks up which internal country number it is
4231 and then displays all the relevant prefixes for that countrytogether
4232 with the internal country no, the CQ and ITU regions. See also
4235 11.154. show/program (5)
4237 show/program Show the locations of all the included program modules
4239 Show the name and location where every program module was load from.
4240 Thisis useful for checking where you think you have loaded a .pm file
4243 11.155. show/qra <lat> <long> (0)
4245 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4247 This is a multipurpose command that allows you either to calculate
4248 thedistance and bearing between two locators or (if only one locator
4249 isgiven on the command line) the distance and beraing from your
4250 stationto the locator. For example:-
4253 SH/QRA IO92QL SH/QRA JN06 IN73
4257 The first example will show the distance and bearing to the locator
4258 fromyourself, the second example will calculate the distance and bear-
4259 ing fromthe first locator to the second. You can use 4 or 6 character
4260 locators.It is also possible to convert a latitude and longitude to a
4261 locator by using this command with a latitude and longitude as an
4262 argument, forexample:-
4265 SH/QRA 52 41 N 0 58 E
4269 11.156. show/qra <locator> [<locator>] (0)
4271 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4274 11.157. show/qrz <callsign> (0)
4276 show/qrz <callsign> Show any callbook details on a callsign
4278 This command queries the QRZ callbook server on the internetand
4279 returns any information available for that callsign. This serviceis
4280 provided for users of this software by http://www.qrz.com See also
4281 SHOW/WM7D for an alternative.
4283 11.158. show/route <callsign> ... (0)
4285 show/route <callsign> ... Show the route to the callsign
4287 This command allows you to see to which node the callsigns specified
4288 areconnected. It is a sort of inverse sh/config.
4295 11.159. show/satellite <name> [<hours> <interval>] (0)
4297 show/satellite <name> [<hours> <interval>] Show tracking data
4299 Show the tracking data from your location to the satellite of your
4300 choicefrom now on for the next few hours.If you use this command
4301 without a satellite name it will display a listof all the satellites
4302 known currently to the system. If you give a name then you can obtain
4303 tracking data of all the passesthat start and finish 5 degrees below
4304 the horizon. As default it willgive information for the next three
4305 hours for every five minute period.You can alter the number of hours
4306 and the step size, within certain limits. Each pass in a period is
4307 separated with a row of '-----' charactersSo for example:-
4310 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4314 11.160. show/station all [<regex>] (6)
4316 show/station all [<regex>] Show list of users in the system
4319 11.161. show/station [<callsign> ..] (0)
4321 show/station [<callsign> ..] Show information about a callsign
4323 Show the information known about a callsign and whether (and
4324 where)that callsign is connected to the cluster.
4331 If no callsign is given then show the information for yourself.
4333 11.162. show/sun [ndays] [<prefix>|<callsign>] (0)
4335 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
4337 Show the sun rise and set times for a (list of) prefixes or callsigns,
4338 together with the azimuth and elevation of the sun currently at
4339 thoselocations.If you don't specify any prefixes or callsigns, it will
4340 show the times foryour QTH (assuming you have set it with either
4341 SET/LOCATION or SET/QRA),together with the current azimuth and
4342 elevation.If all else fails it will show the sunrise and set times for
4343 the nodethat you are connected to. For example:-
4346 SH/SUN SH/SUN G1TLH K9CW ZS
4350 You can also use this command to see into the past or the future, soif
4351 you want to see yesterday's times then do:-
4358 or in three days time:-
4365 Upto 366 days can be checked both in the past and in the future.Please
4366 note that the rise and set times are given as the UT times of rise and
4367 set on the requested UT day.
4369 11.163. show/time [<prefix>|<callsign>] (0)
4371 show/time [<prefix>|<callsign>] Show the local time
4373 If no prefixes or callsigns are given then this command returns the
4374 localtime and UTC as the computer has it right now. If you give some
4375 prefixesthen it will show UTC and UTC + the local offset (not
4376 including DST) atthe prefixes or callsigns that you specify.
4380 11.164. show/usdb [call ..] (0)
4382 show/usdb [call ..] Show information held on the FCC Call database
4384 Show the City and State of a Callsign held on the FCC database ifhis
4385 is being run on this system, eg:-
4392 11.165. show/vhfstats [days] [date] (0)
4394 show/vhfstats [days] [date] Show the VHF DX Statistics
4396 Show the VHF DX spots breakdown by band for the last <days> no of days
4397 (default is 31), starting from a date (default: today).
4399 11.166. show/vhftable [days] [date] [prefix ...] (0)
4401 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
4403 Show the VHF DX Spotter table for the list of prefixes for the last
4404 <days> no of days (default is 31), starting from a date (default:
4405 today).If there are no prefixes then it will show the table for your
4406 country.Remember that some countries have more than one "DXCC country"
4407 in them(eg G :-), to show them (assuming you are not in G already
4408 which isspecially treated in the code) you must list all the relevant
4412 sh/vhftable g gm gd gi gj gw gu
4416 Note that the prefixes are converted into country codes so you don't
4417 haveto list all possible prefixes for each country.If you want more or
4418 less days than the default simply include thenumber you require:-
4425 If you want to start at a different day, simply add the date in some
4429 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
4433 This will show the stats for your DXCC for that CQWW contest weekend.
4434 You can specify either prefixes or full callsigns (so you can see how
4435 youdid against all your mates). You can also say 'all' which will then
4436 printthe worldwide statistics.
4443 11.167. show/wcy (0)
4445 show/wcy Show last 10 WCY broadcasts
4448 11.168. show/wcy <n> (0)
4450 show/wcy <n> Show last <n> WCY broadcasts
4452 Display the most recent WCY information that has been received by the
4455 11.169. show/wm7d <callsign> (0)
4457 show/wm7d <callsign> Show callbook details on a US callsigns
4459 This command queries the WM7D callbook server on the internetand
4460 returns any information available for that US callsign. This serviceis
4461 provided for users of this software by http://www.wm7d.net.See also
4464 11.170. show/wwv (0)
4466 show/wwv Show last 10 WWV broadcasts
4469 11.171. show/wwv <n> (0)
4471 show/wwv <n> Show last <n> WWV broadcasts
4473 Display the most recent WWV information that has been received by the
4476 11.172. shutdown (5)
4478 shutdown Shutdown the cluster
4480 Shutdown the cluster and disconnect all the users
4482 11.173. stat/channel [<callsign>] (5)
4484 stat/channel [<callsign>] Show the status of a channel on the cluster
4486 Show the internal status of the channel object either for the channel
4487 that you are on or else for the callsign that you asked for.Only the
4488 fields that are defined (in perl term) will be displayed.
4490 11.174. stat/db <dbname> (5)
4492 stat/db <dbname> Show the status of a database
4494 Show the internal status of a database descriptor.Depending on your
4495 privilege level you will see more or less information. This command is
4496 unlikely to be of much use to anyone other than a sysop.
4498 11.175. stat/msg (1)
4500 stat/msg Show the status of the message system
4503 11.176. stat/msg <msgno> (1)
4505 stat/msg <msgno> Show the status of a message
4507 This command shows the internal status of a message and includes
4508 informationsuch as to whom it has been forwarded, its size, origin etc
4509 etc.If no message number is given then the status of the message
4510 system is displayed.
4512 11.177. stat/route_node <callsign> (5)
4514 stat/route_node <callsign> Show the data in a Route::Node object
4517 11.178. stat/route_node all (5)
4519 stat/route_node all Show list of all Route::Node objects
4522 11.179. stat/route_user <callsign> (5)
4524 stat/route_user <callsign> Show the data in a Route::User object
4527 11.180. stat/route_user all (5)
4529 stat/route_user all Show list of all Route::User objects
4532 11.181. stat/user [<callsign>] (5)
4534 stat/user [<callsign>] Show the full status of a user
4536 Shows the full contents of a user record including all the secret
4537 flagsand stuff.Only the fields that are defined (in perl term) will be
4542 sysop Regain your privileges if you login remotely
4544 The system automatically reduces your privilege level to that of
4545 anormal user if you login in remotely. This command allows you
4546 toregain your normal privilege level. It uses the normal system:
4547 fivenumbers are returned that are indexes into the character array
4548 that isyour assigned password (see SET/PASSWORD). The indexes start
4549 fromzero.You are expected to return a string which contains the
4550 charactersrequired in the correct order. You may intersperse those
4551 characterswith others to obscure your reply for any watchers. For
4552 example (andthese values are for explanation :-):
4555 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
4562 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
4566 They will all match. If there is no password you will still be
4567 offerednumbers but nothing will happen when you input a string. Any
4568 match iscase sensitive.
4570 11.183. talk <call> > <node> [<text>] (0)
4572 talk <call> > <node> [<text>] Send a text message to another station
4575 Send a short message to any other station that is visible on the
4576 clustersystem. You can send it to anyone you can see with a
4577 SHOW/CONFIGURATION command, they don't have to be connected
4578 locally.The second form of TALK is used when other cluster nodes are
4579 connectedwith restricted information. This usually means that they
4580 don't send the user information usually associated with logging on and
4581 off the cluster.If you know that G3JNB is likely to be present on
4582 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
4583 then you would use thesecond form of the talk message.If you want to
4584 have a ragchew with someone you can leave the text messageout and the
4585 system will go into 'Talk' mode. What this means is that ashort
4586 message is sent to the recipient telling them that you are in
4587 a'Talking' frame of mind and then you just type - everything you send
4588 willgo to the station that you asked for. All the usual announcements,
4589 spots and so on will still come out on yourterminal.If you want to do
4590 something (such as send a spot) you preceed the normal command with a
4594 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
4598 To leave talk mode type:
4605 If you are in 'Talk' mode, there is an extention to the '/' command
4606 whichallows you to send the output to all the people you are talking
4607 to. You do with the '//' command. For example:-
4614 will send the hftable as you have it to all the people you are cur-
4617 11.184. talk <call> [<text>] (0)
4619 talk <call> [<text>] Send a text message to another station
4622 11.185. type <filearea>/<name> (0)
4624 type <filearea>/<name> Look at the contents of a file in one of the
4627 Type out the contents of a file in a filearea. So, for example, in
4628 filearea 'bulletins' you want to look at file 'arld051' you would
4632 TYPE bulletins/arld051
4636 See also SHOW/FILES to see what fileareas are available and a list of
4641 11.186. uncatchup <node call> all|[msgno> ...] (5)
4643 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
4645 When you send messages the fact that you have forwarded it to another
4646 node is remembered so that it isn't sent again. When you have a new
4647 partnernode and you add their callsign to your /spider/msg/forward.pl
4648 file, alloutstanding non-private messages will be forwarded to them.
4649 This may wellbe ALL the non-private messages. You can prevent this by
4650 using these commmands:-
4653 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
4657 and to undo what you have just done:-
4660 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
4664 which will arrange for them to be forward candidates again.Order is
4667 11.187. unset/announce (0)
4669 unset/announce Stop announce messages coming out on your terminal
4672 11.188. unset/anntalk (0)
4674 unset/anntalk Stop talk like announce messages on your terminal
4676 The announce system on legacy cluster nodes is used as a talk
4677 substitute because the network is so poorly connected. If you:
4684 you will suppress several of these announces, you may miss the odd
4685 useful one as well, but you would probably miss them anyway in thewel-
4686 ter of useless ones.
4693 allows you to see them again. This is the default.
4695 11.189. unset/baddx <call>.. (8)
4697 unset/baddx <call>.. Propagate a dx spot with this callsign again
4699 Setting a word as 'baddx' will prevent spots with that word in
4700 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
4701 anyfurther. They will not be displayed and they will not be sent
4702 ontoother nodes.The word must be written in full, no wild cards are
4707 set/baddx FORSALE VIDEO FR0G
4711 To allow a word again, use the following command ...
4718 11.190. unset/badnode <call>.. (8)
4720 unset/badnode <call>.. Allow spots from this node again
4722 Setting a callsign as a 'badnode' will prevent spots from that node
4723 going any further. They will not be displayed and they will not be
4724 sent onto other nodes.The call must be a full eg:-
4731 will stop anything from K1TTT. If you want SSIDs as well then you mus-
4732 tenter them specifically.
4739 will allow spots from him again.Use with extreme care. This command
4740 may well be superceeded by FILTERing.
4742 11.191. unset/badspotter <call>.. (8)
4744 unset/badspotter <call>.. Allow spots from this callsign again
4746 Setting a callsign as a 'badspotter' will prevent spots from this
4747 callsign going any further. They will not be displayed and they will
4748 not be sent onto other nodes.The call must be written in full, no wild
4749 cards are allowed eg:-
4752 set/badspotter VE2STN
4756 will stop anything from VE2STN. This command will automaticallystop
4757 spots from this user, regardless of whether or which SSID he uses. DO
4758 NOT USE SSIDs in the callsign, just use the callsignas above or below.
4761 unset/badspotter VE2STN
4765 will allow spots from him again.Use with extreme care. This command
4766 may well be superceded by FILTERing.
4768 11.192. unset/badword <word>.. (8)
4770 unset/badword <word>.. Propagate things with this word again
4772 Setting a word as a 'badword' will prevent things like spots,announces
4773 or talks with this word in the the text part from going anyfurther.
4774 They will not be displayed and they will not be sent ontoother
4775 nodes.The word must be written in full, no wild cards are allowed eg:-
4778 set/badword annihilate annihilated annihilation
4782 will stop anything with these words in the text.
4785 unset/badword annihilated
4789 will allow text with this word again.
4791 11.193. unset/beep (0)
4793 unset/beep Stop beeps for DX and other messages on your terminal
4796 11.194. unset/dx (0)
4798 unset/dx Stop DX messages coming out on your terminal
4801 11.195. unset/dxcq (0)
4803 unset/dxcq Stop CQ Zones on the end of DX announcements
4805 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
4806 announcement (there is just enough room). Some user programscannot
4807 cope with this. The Spotter's CQ is on the RHS of the time, the
4808 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
4809 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
4812 11.196. unset/dxgrid (0)
4814 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
4816 A standard feature which is enabled in version 1.43 and above is that
4817 if the spotter's grid square is known it is output on the endof a DX
4818 announcement (there is just enough room). Some user programscannot
4819 cope with this. You can use this command to reset (or set)this
4820 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
4821 flags you have set if you are confused.
4823 11.197. unset/dxitu (0)
4825 unset/dxitu Stop ITU Zones on the end of DX announcements
4827 Display both the Spotter's and the Spotted's ITU Zone on the endof a
4828 DX announcement (there is just enough room). Some user programscannot
4829 cope with this. The Spotter's ITU is on the RHS of the time, the
4830 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
4831 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
4834 11.198. unset/echo (0)
4836 unset/echo Stop the cluster echoing your input
4838 If you are connected via a telnet session, different implimentationsof
4839 telnet handle echo differently depending on whether you are connected
4840 via port 23 or some other port. You can use this commandto change the
4841 setting appropriately. The setting is stored in your user profile.YOU
4842 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
4844 11.199. unset/email (0)
4846 unset/email Stop personal msgs being forwarded by email
4848 If any personal messages come in for your callsign then you can
4849 usethese commands to control whether they are forwarded onto your
4850 emailaddress. To enable the forwarding do something like:-
4853 SET/EMAIL mike.tubby@somewhere.com
4857 You can have more than one email address (each one separated by a
4858 space).Emails are forwarded to all the email addresses you specify.You
4859 can disable forwarding by:-
4866 11.200. unset/here (0)
4868 unset/here Tell the system you are absent from your terminal
4871 11.201. unset/hops <call> ann|spots|route|wwv|wcy (8)
4873 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
4875 Set the hop count for a particular type of broadcast for a node.This
4876 command allows you to set up special hop counts for a node for
4877 currently: announce, spots, wwv and wcy broadcasts.eg:
4880 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
4884 Set SHOW/HOPS for information on what is already set. This commandcre-
4885 ates a filter and works in conjunction with the filter system. You can
4886 unset the hops with command UNSET/HOPS. For example:-
4889 unset/hops gb7djk ann unset/hops gb7mbc spots
4893 11.202. unset/logininfo (0)
4895 unset/logininfo Inform when a station logs out locally
4898 11.203. unset/privilege (0)
4900 unset/privilege Remove any privilege for this session
4902 You can use this command to 'protect' this session from
4903 unauthoriseduse. If you want to get your normal privilege back you
4904 will need toeither logout and login again (if you are on a console) or
4905 use theSYSOP command.
4907 11.204. unset/prompt (0)
4909 unset/prompt Set your prompt back to default
4911 This command will set your user prompt to exactly the string that you
4912 say. The point of this command to enable a user to interface to
4913 programsthat are looking for a specific prompt (or else you just want
4914 a differentfixed prompt).
4921 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
4924 11.205. unset/talk (0)
4926 unset/talk Stop TALK messages coming out on your terminal
4929 11.206. unset/usstate (0)
4931 unset/usstate Stop US State info on the end of DX announcements
4933 If the spotter's or spotted's US State is known it is output on the
4934 end of a DX announcement (there is just enough room). A spotter's
4935 state will appear on the RHS of the time (like SET/DXGRID) and the
4936 spotted's State will appear on the LHS of thetime field. Any
4937 information found will override any locator information from
4938 SET/DXGRID.Some user programs cannot cope with this. You can use this
4939 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
4940 SET/DXITUDo a STAT/USER to see which flags you have set if you are
4943 11.207. unset/wcy (0)
4945 unset/wcy Stop WCY messages coming out on your terminal
4948 11.208. unset/wwv (0)
4950 unset/wwv Stop WWV messages coming out on your terminal
4953 11.209. unset/wx (0)
4955 unset/wx Stop WX messages coming out on your terminal
4960 who Show who is physically connected
4962 This is a quick listing that shows which callsigns are connected
4963 andwhat sort of connection they have
4967 11.211. wx <text> (0)
4969 wx <text> Send a weather message to local users
4972 11.212. wx full <text> (0)
4974 wx full <text> Send a weather message to all cluster users
4977 11.213. wx sysop <text> (5)
4979 wx sysop <text> Send a weather message to other clusters only
4981 Weather messages can sometimes be useful if you are experiencing an
4982 extremethat may indicate enhanced conditions