1 The DXSpider Administration Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
4 March 2003 revision 0.5
6 A reference for SysOps of the DXSpider DXCluster program.
7 ______________________________________________________________________
13 1. Routing and Filtering
16 1.3 The node_default filter
17 1.4 General route filtering
18 1.5 General filter rules
22 1.9 Advanced filtering
23 1.10 Basic hop control
24 1.11 Hop Control on Specific Nodes
25 1.12 Isolating networks
29 2.2 Filtering words from text fields in Announce, Talk and DX spots
30 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
39 3.7 Distribution lists
44 5.1 Creating databases
45 5.2 Importing databases
46 5.3 Checking available databases
47 5.4 Looking up databases
48 5.5 Removing databases
50 6. Information, files and useful programs
54 6.4 Other text messages
57 6.7 Updating kepler data
59 6.9 Connecting logging programs
62 8. Web based statistics
68 10.1 CVS from a Linux platform
69 10.2 CVS from a Windows platform
71 11. The DXSpider command set
73 11.2 accept/announce <call> [input] [0-9] <pattern> (8)
74 11.3 accept/announce [0-9] <pattern> (0)
75 11.4 accept/route <call> [0-9] <pattern> (8)
76 11.5 accept/spots <call> [input] [0-9] <pattern> (8)
77 11.6 accept/spots [0-9] <pattern> (0)
78 11.7 accept/wcy <call> [input] [0-9] <pattern> (8)
79 11.8 accept/wcy [0-9] <pattern> (0)
80 11.9 accept/wwv <call> [input] [0-9] <pattern> (8)
81 11.10 accept/wwv [0-9] <pattern> (0)
82 11.11 announce <text> (0)
83 11.12 announce full <text> (0)
84 11.13 announce sysop <text> (5)
85 11.14 apropos <string> (0)
86 11.15 blank [<string>] [<nn>] (0)
88 11.17 catchup <node call> all|[<msgno> ...] (5)
89 11.18 clear/announce <callsign> [input] [0-9|all] (8)
90 11.19 clear/announce [1|all] (0)
91 11.20 clear/route <callsign> [input] [0-9|all] (8)
92 11.21 clear/route [1|all] (0)
93 11.22 clear/spots <callsign> [input] [0-9|all] (8)
94 11.23 clear/spots [0-9|all] (0)
95 11.24 clear/wcy <callsign> [input] [0-9|all] (8)
96 11.25 clear/wcy [1|all] (0)
97 11.26 clear/wwv <callsign> [input] [0-9|all] (8)
98 11.27 clear/wwv [1|all] (0)
99 11.28 connect <callsign> (5)
101 11.30 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/contest <year and month> (0)
208 11.137 show/date [<prefix>|<callsign>] (0)
209 11.138 show/db0sdx <callsign> (0)
211 11.140 show/dxcc <prefix> (0)
212 11.141 show/dxqsl <callsign> (0)
213 11.142 show/dxstats [days] [date] (0)
214 11.143 show/files [<filearea> [<string>]] (0)
215 11.144 show/filter (0)
216 11.145 show/hfstats [days] [date] (0)
217 11.146 show/hftable [days] [date] [prefix ...] (0)
218 11.147 show/hops <call> [ann|spots|route|wcy|wwv] (8)
219 11.148 show/isolate (1)
220 11.149 show/log [<callsign>] (8)
221 11.150 show/moon [ndays] [<prefix>|<callsign>] (0)
222 11.151 show/muf <prefix> [<hours>][long] (0)
223 11.152 show/newconfiguration [<node>] (0)
224 11.153 show/newconfiguration/node (0)
225 11.154 show/node [<callsign> ...] (1)
226 11.155 show/prefix <callsign> (0)
227 11.156 show/program (5)
228 11.157 show/qra <lat> <long> (0)
229 11.158 show/qra <locator> [<locator>] (0)
230 11.159 show/qrz <callsign> (0)
231 11.160 show/route <callsign> ... (0)
232 11.161 show/satellite <name> [<hours> <interval>] (0)
233 11.162 show/station all [<regex>] (6)
234 11.163 show/station [<callsign> ..] (0)
235 11.164 show/sun [ndays] [<prefix>|<callsign>] (0)
236 11.165 show/time [<prefix>|<callsign>] (0)
237 11.166 show/usdb [call ..] (0)
238 11.167 show/vhfstats [days] [date] (0)
239 11.168 show/vhftable [days] [date] [prefix ...] (0)
241 11.170 show/wcy <n> (0)
242 11.171 show/wm7d <callsign> (0)
244 11.173 show/wwv <n> (0)
246 11.175 stat/channel [<callsign>] (5)
247 11.176 stat/db <dbname> (5)
249 11.178 stat/msg <msgno> (1)
250 11.179 stat/route_node <callsign> (5)
251 11.180 stat/route_node all (5)
252 11.181 stat/route_user <callsign> (5)
253 11.182 stat/route_user all (5)
254 11.183 stat/user [<callsign>] (5)
256 11.185 talk <call> > <node> [<text>] (0)
257 11.186 talk <call> [<text>] (0)
258 11.187 type <filearea>/<name> (0)
259 11.188 uncatchup <node call> all|[msgno> ...] (5)
260 11.189 unset/announce (0)
261 11.190 unset/anntalk (0)
262 11.191 unset/baddx <call>.. (8)
263 11.192 unset/badnode <call>.. (8)
264 11.193 unset/badspotter <call>.. (8)
265 11.194 unset/badword <word>.. (8)
266 11.195 unset/beep (0)
268 11.197 unset/dxcq (0)
269 11.198 unset/dxgrid (0)
270 11.199 unset/dxitu (0)
271 11.200 unset/echo (0)
272 11.201 unset/email (0)
273 11.202 unset/here (0)
274 11.203 unset/hops <call> ann|spots|route|wwv|wcy (8)
275 11.204 unset/logininfo (0)
276 11.205 unset/privilege (0)
277 11.206 unset/prompt (0)
278 11.207 unset/talk (0)
279 11.208 unset/usstate (0)
285 11.214 wx full <text> (0)
286 11.215 wx sysop <text> (5)
289 ______________________________________________________________________
291 1. Routing and Filtering
295 From DXSpider version 1.48, major changes were introduced to the way
296 node connections are treated. This is part of an ongoing process to
297 remove problems with loops and to enable talk and other functions to
298 propagate across the whole of the worldwide cluster network. In fact,
299 in a Spider network, it would be useful, perhaps even necessary to
300 have loops. This would give real resilience to the network, meaning
301 that if a link dropped, the information flow would simply come in and
302 go out via a different route. Of course, we do not have a complete
303 network of Spider nodes, there are other programs out there. Some of
304 these do not have any protection from loops. Certainly AK1A does not
305 handle loops well at all. It is therefore necessary to have some form
306 of protection for these nodes.
309 In fact DXSpider has had a simple system for some time which is called
310 isolation. This is similar to what in other systems such as clx, is
311 called passive mode. A more detailed explanation of isolation is given
312 further below. This system is still available and, for simple
313 networks, is probably all that you need.
316 The new functionality introduced in version 1.48 allows filtering the
317 node and user protocol frames on a "per interface" basis. We call this
318 route filtering. This is used instead of isolation.
321 What this really means is that you can control more or less completely
322 which user and node management PC protocol frames pass to each of your
323 partner nodes. You can also limit what comes into your node from your
324 partners. It is even possible to control the settings that your
325 partner node has for the routing information that it sends to you
326 (using the rcmd command).
331 Initially when route filters were being tested we generated a
332 "default" filter. Unfortunately it quickly became apparent that this
333 might suit the UK cluster network but didn't really fit anybody else.
334 However using a default filter is an appropriate thing to do. How, is
335 explained further on.
338 The first thing that you must do is determine whether you need to use
339 route filtering at all. If you are a "normal" node with two or three
340 partners and you arranged in an "official" non-looping tree type
341 network, then you do not need to do route filtering and you will feel
342 a lot better for not getting involved. If you are successfully using
343 isolation then you also probably don't need to use route filtering.
346 To put it simply, you should not mix Isolation and Route Filtering.
347 It will work, of sorts, but you will not get the expected results. If
348 you are using Isolation sucessfully at the moment, do not get involved
349 in Route Filtering unless you have a good supply of aspirin! Once you
350 have started down the road of Route Filtering, do not use Isolation
351 either. Use one or the other, not both.
354 You will only require this functionality if you are "well-connected".
355 What that means is that you are connected to several different parts
356 of (say) the EU cluster and, at the same time, also connected to two
357 or three places in the US which, in turn are connected back to the EU.
358 This is called a "loop" and if you are seriously looped then you need
362 I should at this stage give a little bit of background on filters.
363 All the filters in Spider work in basically the same way. You can
364 either accept or reject various options in order to create the filter
365 rules you wish to achieve. Some filters are user settable, others can
366 only be altered by the sysop. Route filtering can only be done by the
371 Anyway, without further discouragement, let me start the process of
375 1.3. The node_default filter
377 All normal systems should have a default routing filter and it should
378 usually be set to send only the normal, unlooped, view of your
379 "national" network. Here in the UK that means nodes from the UK and
380 Eire, in EU it is more complex as the networks there grew up in a more
385 The generic commands are:-
389 reject/route node_default <filter_option>
393 accept/route node_default <filter_option>
397 where filter_option is one of the following ...
406 channel_dxcc <numbers>
407 channel_itu <numbers>
408 channel_zone <numbers>
412 Please be careful if you alter this setting, it will affect ALL your
413 links! Remember, this is a default filter for node connections, not a
417 For the default routing filter then you have two real choices: either
418 a "national" view or the "safe" option of only your own callsign.
419 Examples of each (for my node: GB7DJK) are:-
423 acc/route node_default call_dxcc 61,38
424 acc/route node_default call gb7djk
428 GB7DJK uses the first of these. The DXCC countries can be obtained
429 from the show/prefix command.
432 The example filters shown control output TO all your partner nodes
433 unless they have a specific filter applied to them (see next section).
436 It is also possible to control the incoming routing information that
437 you are prepared to accept FROM your partner nodes. The reason this is
438 necessary is to make sure that stuff like mail, pings and similar
439 commands a) go down the correct links and b) don't loop around
440 excessively. Again using GB7DJK as an example a typical default input
441 filter would be something like:
445 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
449 What this does is accept node and user information for our national
450 network from nodes that are in our national network, but rejects such
451 information from anyone else. Although it doesn't explicitly say so,
452 by implication, any other node information (not from the UK and Eire)
456 As I imagine it will take a little while to get one's head around all
457 of this you can study the effect of any rules that you try by watching
458 the debug output after having done:-
464 After you have got tired of that, to put it back the way it was:-
472 1.4. General route filtering
474 Exactly the same rules apply for general route filtering. You would
475 use either an accept filter or a reject filter like this ...
479 reject/route <node_call> <filter_option>
483 accept/route <node_call> <filter_option>
487 Here are some examples of route filters ...
491 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
492 rej/route all (equiv to [very] restricted mode)
493 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
494 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
498 In practice you will either be opening the default filter out for a
499 partner by defining a specific filter for that callsign:-
504 acc/route gb7baa input all
508 or restricting it quite a lot, in fact making it very nearly like an
509 isolated node, like this:-
513 acc/route pi4ehv-8 call gb7djk
514 rej/route pi4ehv-8 input call_dxcc 61,38
518 This last example takes everything except UK and Eire from PI4EHV-8
519 but only sends him my local configuration (just a PC19 for GB7DJK and
520 PC16s for my local users).
523 It is possible to write much more complex rules, there are up to 10
524 accept/reject pairs per callsign per filter. For more information see
529 1.5. General filter rules
531 Upto v1.44 it was not possible for the user to set their own filters.
532 From v1.45 though that has all changed. It is now possible to set
533 filters for just about anything you wish. If you have just updated
534 from an older version of DXSpider you will need to update your new
535 filters. You do not need to do anything with your old filters, they
536 will be renamed as you update.
539 There are 3 basic commands involved in setting and manipulating
540 filters. These are accept, reject and clear. First we will look
541 generally at filtering. There are a number of things you can filter in
542 the DXSpider system. They all use the same general mechanism.
545 In general terms you can create a "reject" or an "accept" filter which
546 can have up to 10 lines in it. You do this using, for example ...
555 where ..... are the specific commands for that type of filter. There
556 are filters for spots, wwv, announce, wcy and (for sysops) connects.
557 See each different accept or reject command reference for more
560 There is also a command to clear out one or more lines in a filter.
570 There is clear/xxxx command for each type of filter.
573 and you can check that your filters have worked by the command ...
581 For now we are going to use spots for the examples, but you can apply
582 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 ...
645 reject/spots 1 on hf/cw
646 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
650 What this does is to ignore all HF CW spots and also rejects any spots
651 on VHF which don't either originate or spot someone in Europe.
654 This is an example where you would use a line number (1 and 2 in this
655 case), if you leave the digit out, the system assumes '1'. Digits
656 '0'-'9' are available. This make it easier to see just what filters
657 you have set. It also makes it more simple to remove individual
658 filters, during a contest for example.
661 You will notice in the above example that the second line has
662 brackets. Look at the line logically. You can see there are 2
663 separate sections to it. We are saying reject spots that are VHF or
664 above APART from those in zones 14, 15 and 16 (either spotted there or
665 originated there). If you did not have the brackets to separate the 2
666 sections, then Spider would read it logically from the front and see a
667 different expression entirely ...
671 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
675 The simple way to remember this is, if you use OR - use brackets.
676 Whilst we are here CASE is not important. 'And BY_Zone' is just the
677 same as 'and by_zone'.
679 As mentioned earlier, setting several filters can be more flexible
680 than simply setting one complex one. Doing it in this way means that
681 if you want to alter your filter you can just redefine or remove one
682 or more lines of it or one line. For example ...
686 reject/spots 1 on hf/ssb
690 would redefine our earlier example, or
698 To remove all the filter lines in the spot filter ...
708 You can filter in several different ways. The options are listed in
709 the various helpfiles for accept, reject and filter.
714 Sometimes all that is needed is a general rule for node connects.
715 This can be done with a node_default filter. This rule will always be
716 followed, even if the link is isolated, unless another filter is set
717 specifically. Default rules can be set for nodes and users. They can
718 be set for spots, announces, WWV and WCY. They can also be used for
719 hops. An example might look like this ...
723 accept/spot node_default by_zone 14,15,16,20,33
724 set/hops node_default spot 50
728 This filter is for spots only, you could set others for announce, WWV
729 and WCY. This filter would work for ALL nodes unless a specific
730 filter is written to override it for a particular node. You can also
731 set a user_default should you require. It is important to note that
732 default filters should be considered to be "connected". By this I
733 mean that should you override the default filter for spots, you need
734 to add a rule for the hops for spots also.
737 1.9. Advanced filtering
739 Once you are happy with the results you get, you may like to
743 The previous example that filters hf/cw spots and accepts vhf/uhf
744 spots from EU can be written with a mixed filter, for example ...
750 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
754 Note that the first filter has not been specified with a number. This
755 will automatically be assumed to be number 1. In this case, we have
756 said reject all HF spots in the CW section of the bands but accept all
757 others at HF. Also accept anything in VHF and above spotted in or by
758 operators in the zones 14, 15 and 16. Each filter slot actually has a
759 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
763 It was mentioned earlier that after a reject test that doesn't match,
764 the default for following tests is 'accept', the reverse is true for
765 'accept'. In the example what happens is that the reject is executed
766 first, any non hf/cw spot is passed to the accept line, which lets
767 through everything else on HF. The next filter line lets through just
768 VHF/UHF spots from EU.
770 1.10. Basic hop control
772 In /spider/data you will find a file called hop_table.pl. This is the
773 file that controls your hop count settings. It has a set of default
774 hops on the various PC frames and also a set for each node you want to
775 alter the hops for. You may be happy with the default settings of
776 course, but this powerful tool can help to protect and improve the
777 network. The file will look something like this ...
782 # hop table construction
787 # default hopcount to use
790 # some variable hop counts based on message type
801 # the per node hop control thingy
833 Each set of hops is contained within a pair of curly braces and
834 contains a series of PC frame types. PC11 for example is a DX spot.
835 The figures here are not exhaustive but should give you a good idea of
839 SHould any of the nodecalls include an ssid, it is important to wrap
840 the whole call in single quotes, like this ...
855 If you do not do this, you will get errors and the file will not work
859 You can alter this file at any time, including whilst the cluster is
860 running. If you alter the file during runtime, the command load/hops
861 will bring your changes into effect.
864 1.11. Hop Control on Specific Nodes
866 You can set a callsign specific hop count for any of the standard
871 set/hops gb7djk spot 4
872 set/hops node_default route 10
873 set/hops gb7baa wcy 5
877 all work on their specific area of the protocol.
880 The set/hops command overrides any hops that you have set otherwise.
883 You can show what hops have been set using the show/hops command.
886 1.12. Isolating networks
888 It is possible to isolate networks from each other on a "gateway" node
889 using the set/isolate <node_call> command.
892 The effect of this is to partition an isolated network completely from
893 another node connected to your node. Your node will appear on and
894 otherwise behave normally on every network to which you are connected,
895 but data from an isolated network will not cross onto any other
896 network or vice versa. However all the spot, announce and WWV traffic
897 and personal messages will still be handled locally (because you are a
898 real node on all connected networks), that is locally connected users
899 will appear on all networks and will be able to access and receive
900 information from all networks transparently. All routed messages will
901 be sent as normal, so if a user on one network knows that you are a
902 gateway for another network, he can still still send a talk/announce
903 etc message via your node and it will be routed across.
906 If you use isolate on a node connection you will continue to receive
907 all information from the isolated partner, however you will not pass
908 any information back to the isolated node. There are times when you
909 would like to forward only spots across a link (maybe during a contest
910 for example). To do this, isolate the node in the normal way and use
911 an acc/spot >call< all filter to override the isolate.
918 In the /spider/msg directory you will find a file called
919 badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
920 original looks something like this ....
924 # the list of regexes for messages that we won't store having
925 # received them (bear in mind that we must receive them fully before
929 # The format of each line is as follows
931 # type source pattern
932 # P/B/F T/F/O/S regex
934 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
935 # source: T - to field, F - from field, O - origin, S - subject
936 # pattern: a perl regex on the field requested
938 # Currently only type B and P msgs are affected by this code.
940 # The list is read from the top down, the first pattern that matches
941 # causes the action to be taken.
943 # The pattern can be undef or 0 in which case it will always be selected
944 # for the action specified
955 I think this is fairly self explanatory. It is simply a list of
956 subject headers that we do not want to pass on to either the users of
957 the cluster or the other cluster nodes that we are linked to. This is
958 usually because of rules and regulations pertaining to items for sale
959 etc in a particular country.
960 2.2. Filtering words from text fields in Announce, Talk and DX spots
962 From version 1.48 onwards the interface to this has changed. You can
963 now use the commands set/badword to add words that you are not
964 prepared to see on the cluster, unset/badword to allow that word again
965 and show/badword to list the words that you have set.
968 If you have a previous /spider/data/badwords, the first time you start
969 the node, it will read and convert this file to the new commands. The
970 old style file will then be removed.
973 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
976 There are a number of commands that control whether a spot progresses
977 any further by regarding it as "bad" in some way.
980 A DX Spot has a number of fields which can be checked to see whether
981 they contain "bad" values, they are: the DX callsign itself, the
982 Spotter and the Originating Node.
985 There are a set of commands which allow the sysop to control whether a
996 These work in the same as the set/badword command, you can add any
997 words or callsigns or whatever to the appropriate database. For
998 example, to stop a spot from a particular node you do:
1002 set/badnode gb7djk gb7dxc
1010 set/badspotter b0mb p1rat nocall
1018 set/baddx video wsjt
1022 You can remove a word using the appropriate unset command
1023 (unset/baddx, unset/badspotter, unset/badnode) or list them using one
1024 of show/baddx, show/badspotter and show/badnode.
1029 DXSpider deals seamlessly with standard AK1A type mail. It supports
1030 both personal and bulletin mail and the sysop has additional commands
1031 to ensure that mail gets to where it is meant. DXSpider will send
1032 mail almost immediately, assuming that the target is on line.
1033 However, only one mail message is dealt with at any one time. If a
1034 mail message is already being sent or recieved, then the new message
1035 will be queued until it has finished.
1037 The cluster mail is automatically deleted after 30 days unless the
1038 sysop sets the "keep" flag using the msg command.
1043 Personal mail is sent using the sp command. This is actually the
1044 default method of sending mail and so a simple s for send will do. A
1045 full list of the send commands and options is in the command set
1046 section, so I will not duplicate them here.
1051 Bulletin mail is sent by using the sb command. This is one of the
1052 most common mistakes users make when sending mail. They send a
1053 bulletin mail with s or sp instead of sb and of course the message
1054 never leaves the cluster. This can be rectified by the sysop by using
1058 Bulletin addresses can be set using the Forward.pl file.
1063 DXSpider receives all and any mail sent to it without any alterations
1064 needed in files. Because personal and bulletin mail are treated
1065 differently, there is no need for a list of accepted bulletin
1066 addresses. It is necessary, however, to tell the program which links
1067 accept which bulletins. For example, it is pointless sending
1068 bulletins addresses to "UK" to any links other than UK ones. The file
1069 that does this is called forward.pl and lives in /spider/msg. At
1070 default, like other spider files it is named forward.pl.issue. Rename
1071 it to forward.pl and edit the file to match your requirements. The
1077 # this is an example message forwarding file for the system
1079 # The format of each line is as follows
1081 # type to/from/at pattern action destinations
1082 # P/B/F T/F/A regex I/F [ call [, call ...] ]
1084 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
1085 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
1086 # pattern: a perl regex on the field requested
1087 # action: I - ignore, F - forward
1088 # destinations: a reference to an array containing node callsigns
1090 # if it is non-private and isn't in here then it won't get forwarded
1092 # Currently only type B msgs are affected by this code.
1094 # The list is read from the top down, the first pattern that matches
1095 # causes the action to be taken.
1097 # The pattern can be undef or 0 in which case it will always be selected
1098 # for the action specified
1100 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
1101 # pattern) then it will always be forwarded to every node that doesn't have
1102 # it (I strongly recommend you don't use this unless you REALLY mean it, if
1103 # you allow a new link with this on EVERY bull will be forwarded immediately
1104 # on first connection)
1114 Simply insert a bulletin address and state in the brackets where you
1115 wish that mail to go. For example, you can see here that mail sent to
1116 "UK" will only be sent to the UK links and not to PA4AB-14.
1119 To force the cluster to reread the file use load/forward
1122 NB: If a user tries to send mail to a bulletin address that does not
1123 exist in this file, they will get an error.
1126 3.4. The msg command
1128 The msg command is a very powerful and flexible tool for the sysop.
1129 It allows the sysop to alter to and from fields and make other changes
1130 to manage the cluster mail.
1132 Here is a full list of the various options ...
1136 MSG TO <msgno> <call> - change TO callsign to <call>
1137 MSG FRom <msgno> <call> - change FROM callsign to <call>
1138 MSG PRrivate <msgno> - set private flag
1139 MSG NOPRrivate <msgno> - unset private flag
1140 MSG RR <msgno> - set RR flag
1141 MSG NORR <msgno> - unset RR flag
1142 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1143 MSG NOKEep <msgno> - unset the keep flag
1144 MSG SUbject <msgno> <new> - change the subject to <new>
1145 MSG WAittime <msgno> - remove any waiting time for this message
1146 MSG NOREad <msgno> - mark message as unread
1147 MSG REad <msgno> - mark message as read
1148 MSG QUeue - queue any outstanding bulletins
1149 MSG QUeue 1 - queue any outstanding private messages
1153 These commands are simply typed from within the cluster as the sysop
1159 You can check on a message from within the cluster by using the
1160 command stat/msg. This will give you additional information on the
1161 message number including which nodes have received it, which node it
1162 was received from and when etc. Here is an example of the output of
1167 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1170 Msg Time: 26-Jan-2001 1302Z
1174 Subject: AMSAT 2line KEPS 01025.AMSAT
1176 Got it Nodes: GB7BAA, GB7ADX
1180 G0VGS de GB7MBC 28-Jan-2001 1308Z >
1186 This is described in the section on Other filters so I will not
1190 3.7. Distribution lists
1192 Distribution lists are simply a list of users to send certain types of
1193 mail to. An example of this is mail you only wish to send to other
1194 sysops. In /spider/msg there is a directory called distro. You put
1195 any distibution lists in here. For example, here is a file called
1196 SYSOP.pl that caters for the UK sysops.
1199 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
1200 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
1201 GB7DXK GB7DXI GB7DXS)
1205 Any mail sent to "sysop" would only be sent to the callsigns in this
1211 Spider provides a simple BBS interface. No input is required from the
1212 sysop of the cluster at all. The BBS simply sets the cluster as a BBS
1213 and pushes any required mail to the cluster. No mail can flow from
1214 Spider to the BBS, the interface is one-way.
1217 Please be careful not to flood the cluster network with unnecessary
1218 mail. Make sure you only send mail to the clusters that want it by
1219 using the Forward.pl file very carefully.
1224 From 1.48 onwards it will become increasingly possible to control
1225 DXSpider's operation with scripts of various kinds.
1228 The directory /spider/scripts is where it all happens and is used for
1229 several things. Firstly it contains a file called startup that can be
1230 used to call in any changes to the cluster from the default settings
1231 on startup. This script is executed immediately after all
1232 initialisation of the node is done but before any connections are
1233 possible. Examples of this include how many spots it is possible to
1234 get with the sh/dx command, whether you want registration/passwords to
1235 be permanently on etc. An example file is shown below and is included
1236 in the distribution as startup.issue.
1241 # startup script example
1243 # set maximum no of spots allowed to 100
1244 # set/var $Spot::maxspots = 100
1246 # Set registration on
1247 # set/var $main::reqreg = 1
1250 # set/var $main::passwdreq = 1
1255 As usual, any text behind a # is treated as a comment and not read.
1256 To use this file, simply rename it from startup.issue to startup. In
1257 our example above there are three options. The first option is the
1258 amount of spots that a user can request with the sh/dx command.
1259 Normally the default is to give 10 spots unless the user specifies
1260 more. Without this line enabled, the maximum a user can request is
1261 100 spots. Depending on your link quality you may wish to enable more
1262 or less by specifying the number.
1265 The other 2 options are dealt with more fully in the security section.
1268 Secondly, it is used to store the login scripts for users and nodes.
1269 Currently this can only be done by the sysop but it is envisaged that
1270 eventually users will be able to set their own. An example is
1271 included in the distibution but here is a further example.
1288 The lines in between commands can simply insert a blank line or a
1289 character such as a + sign to make the output easier to read. Simply
1290 create this script with your favourite editor and save it with the
1291 callsign of the user as the filename. Filenames should always be in
1295 Commands can be inserted in the same way for nodes. A node may wish a
1296 series of commands to be issued on login, such as a merge command for
1300 Thirdly, there are 2 default scripts for users and nodes who do not
1301 have a specifically defined script. These are user_default and
1307 Spider allows the creation of local or remote databases. It supports
1308 chained databases, allowing several different databases to be scanned
1309 with one simple command. Importing of databases is limited at present
1310 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
1311 database but will expand with time.
1314 5.1. Creating databases
1316 Creating a database could not be more simple. All the commands are
1317 sent from the cluster prompt as the sysop user.
1319 To create a database you use the command dbcreate. It can be used in
1320 3 different ways like so ..
1327 To simply create a database locally, you just tell the command the
1328 name of the database. This does not create the actual database, it
1329 simply defines it to say that it exists.
1333 dbcreate <name> chain <name> [<name>...]
1337 This creates a chained database entry. The first database will be
1338 scanned, then the second, the third etc...
1342 dbcreate <name> remote <name>
1346 This creates a remote entry. the first name field is the database
1347 name at the remote node, then the remote switch, then the actual
1348 node_call of the remote node, for example...
1352 dbcreate buckmaster remote gb7dxc
1356 Remote databases cannot be chained, however, the last database in a
1357 chain can be a remote database.
1360 5.2. Importing databases
1362 The only databases that Spider can currently import are the standard
1363 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
1364 This will be added to with time.
1366 To import such a database, first put the file somewhere useful like
1367 /tmp and then issue the following command ...
1371 dbimport oblast /tmp/OBLAST.FUL
1375 This will update the existing local oblast database or create it if it
1379 5.3. Checking available databases
1381 Once a database is created, you will want to check that it has been
1382 added. To do this use the dbavail command. This will output the
1383 available databases. For example ...
1388 DB Name Location Chain
1392 G0VGS de GB7MBC 3-Feb-2001 1925Z >
1396 5.4. Looking up databases
1398 To look for information in a defined database, simply use the dbshow
1399 command, for example ...
1403 dbshow buckmaster G0YLM
1407 will show the information for the callsign G0YLM from the buckmaster
1408 database if it exists. To make things more standard for the users you
1409 can add an entry in the Aliases file so that it looks like a standard
1410 show command like this ...
1414 Now you can simply use show/buckmaster or an abreviation.
1417 5.5. Removing databases
1419 To delete an existing database you use the dbremove command. For
1428 would remove the oblast database and its associated datafile from the
1429 system. There are no warnings or recovery possible from this command.
1430 If you remove a database it ceases to exist and would have to be
1431 created from scratch if you still required it.
1434 6. Information, files and useful programs
1438 One of the more important things a cluster sysop needs to do is to get
1439 information to his users. The simplest way to do this is to have a
1440 banner that is sent to the user on login. This is know as a "message
1441 of the day" or "motd". To set this up, simply create a file in
1442 /spider/data called motd and edit it to say whatever you want. It is
1443 purely a text file and will be sent automatically to anyone logging in
1447 This message of the day file lives in the same directory as the
1448 standard motd file but is only sent to non-registered users. Once
1449 registered they will receive the same message as any other user.
1452 6.3. Downtime message
1454 If for any reason the cluster is down, maybe for upgrade or
1455 maintenance but the machine is still running, a message can be sent to
1456 the user advising them of the fact. This message lives in the
1457 /spider/data directory and is called "offline". Simply create the
1458 file and edit it to say whatever you wish. This file will be sent to
1459 a user attempting to log into the cluster when DXSpider is not
1463 6.4. Other text messages
1465 You can set other text messages to be read by the user if they input
1466 the file name. This could be for news items or maybe information for
1467 new users. To set this up, make a directory under /spider called
1468 packclus. Under this directory you can create files called news or
1469 newuser for example. In fact you can create files with any names you
1470 like. These can be listed by the user with the command ....
1478 They can be read by the user by typing the command ....
1486 If the file they want to read is called news. You could also set an
1487 alias for this in the Alias file to allow them just to type news
1490 You can also store other information in this directory, either
1491 directly or nested under directories. One use for this would be to
1492 store DX bulletins such as the OPDX bulletins. These can be listed
1493 and read by the user. To keep things tidy, make a directory under
1494 /spider/packclus called bulletin. Now copy any OPDX or similar
1495 bulletins into it. These can be listed by the user in the same way as
1496 above using the show/files command with an extension for the bulletin
1497 directory you have just created, like this ....
1505 An example would look like this ....
1508 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
1512 You can see that in the files area (basically the packclus directory)
1513 there is a file called news and a directory called bulletin. You can
1514 also see that dates they were created. In the case of the file news,
1515 you can also see the time it was last modified, a good clue as to
1516 whether the file has been updated since you last read it. To read the
1517 file called news you would simply issue the command ....
1525 To look what is in the bulletin directory you issue the command ....
1530 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
1531 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
1532 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
1533 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
1534 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
1535 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
1536 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
1537 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
1538 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
1539 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
1540 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
1541 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
1542 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
1543 Press Enter to continue, A to abort (16 lines) >
1547 You can now read any file in this directory using the type command,
1552 type bulletin/opdx391
1553 Ohio/Penn DX Bulletin No. 391
1554 The Ohio/Penn Dx PacketCluster
1558 Editor Tedd Mirgliotta, KB8NW
1559 Provided by BARF-80 BBS Cleveland, Ohio
1560 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
1561 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
1562 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
1563 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
1564 Press Enter to continue, A to abort (508 lines) >
1568 The page length will of course depend on what you have it set to!
1571 6.5. The Aliases file
1573 You will find a file in /spider/cmd/ called Aliases. This is the file
1574 that controls what a user gets when issuing a command. It is also
1575 possible to create your own aliases for databases and files you create
1579 You should not alter the original file in /spider/cmd/ but create a
1580 new file with the same name in /spider/local_cmd. This means that any
1581 new Aliases files that is downloaded will not overwrite your self
1582 created Aliases and also that you do not override any new Aliases with
1583 your copy in /spider/local_cmd/. You must remember that any files you
1584 store in /spider/local/ or /spider/local_cmd override the originals if
1585 the same lines are used in both files.
1588 The best way of dealing with all this then is to only put your own
1589 locally created Aliases in the copy in /spider/local_cmd. The example
1590 below is currently in use at GB7MBC.
1595 # Local Aliases File
1602 '^news$', 'type news', 'type',
1605 '^sh\w*/buck$', 'show/qrz', 'show',
1606 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
1607 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
1608 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
1609 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
1615 Each alphabetical section should be preceded by the initial letter and
1616 the section should be wrapped in square brackets as you can see. The
1617 syntax is straightforward. The first section on each line is the new
1618 command that will be allowed once the alias is included. The second
1619 section is the command it is replacing and the last section is the
1620 actual command that is being used.
1623 The eagle-eyed amongst you will have noticed that in the first
1624 section, the new alias command has a '^' at the start and a '$' at the
1625 end. Basically these force a perfect match on the alias. The '^'
1626 says match the beginning exactly and the with similar commands.
1629 I have 3 different types of alias in this file. At the top is an
1630 alias for 'news'. This is a file I have created in the
1631 /spider/packclus/ directory where I can inform users of new
1632 developments or points of interest. In it's initial form a user would
1633 have to use the command type news. The alias allows them to simply
1634 type news to get the info. Second is an alias for the show/qrz
1635 command so that those users used to the original show/buck command in
1636 AK1A will not get an error, and the rest of the lines are for locally
1637 created databases so that a user can type show/hftest instead of
1638 having to use the command dbshow hftest which is not as intuitive.
1641 This file is just an example and you should edit it to your own
1642 requirements. Once created, simply issue the command load/alias at
1643 the cluster prompt as the sysop user and the aliases should be
1650 In later versions of Spider a simple console program is provided for
1651 the sysop. This has a type ahead buffer with line editing facilities
1652 and colour for spots, announces etc. To use this program, simply use
1653 console.pl instead of client.
1656 To edit the colours, copy /spider/perl/Console.pl to /spider/local and
1657 edit the file with your favourite editor.
1660 6.7. Updating kepler data
1662 Spider has a powerful and flexible show/satellite command. In order
1663 for this to be accurate, the kepler data has to be updated regularly.
1664 In general, this data is available as an email or via cluster mail.
1665 Updating it is simple. First you need to export the mail message as a
1666 file. You do this with the export command from the cluster prompt as
1667 the sysop. For example ...
1671 export 5467 /spider/perl/keps.in
1675 would export message number 5467 as a file called keps.in in the
1676 /spider/perl directory.
1679 Now login to a VT as sysop and cd /spider/perl. There is a command in
1680 the perl directory called convkeps.pl. All we need to do now is
1681 convert the file like so ...
1685 ./convkeps.pl keps.in
1689 Now go back to the cluster and issue the command ...
1697 That is it! the kepler data has been updated.
1700 6.8. The QRZ callbook
1702 The command sh/qrz will only work once you have followed a few simple
1703 steps. First you need to get a user ID and password from qrz.com.
1704 Simply go to the site and create one. Secondly you need to copy the
1705 file /spider/perl/Internet.pm to /spider/local and alter it to match
1706 your user ID and password. You also at this point need to set
1707 $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
1708 proprieter of qrz.com for allowing this access.
1711 6.9. Connecting logging programs
1713 There appear to be very few logging programs out there that support
1714 telnet especially the popular ones like LogEQF, Turbolog etc. This
1715 can make it difficult to connect to your own cluster! The way to do
1716 it is to make the logging program think it has a TNC attached to a com
1717 port on the logging PC and 'push' a linux login out to it. This is
1718 achieved very simply by the use of agetty.
1721 All that is required is to add a line in /etc/inittab to have the
1722 client ready for a connection on the com port of your choice.
1723 Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
1728 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
1732 Add this after the standard runlevel lines in /etc/inittab. The above
1733 line works on ttyS1 (com2). Now as root, issue the command telinit q
1734 and it should be ready for connection. All that is required is a 3
1735 wire serial lead (tx, rx and signal ground). Tell you logging program
1736 to use 8n1 at 9600 baud and you should see a Linux login prompt.
1737 Login as normal and then telnet from there to the cluster.
1742 In the spider tree will be a directory spider-web. This is a neat
1743 little java web applet that can be run from a website. The applet
1744 must run on the same machine as the cluster. The included README file
1748 I should comment here that the applet is precompiled, that is, ready
1749 to go. It was compiled using JDK1.3.1. If your version is earlier
1750 than this then it may not work. Should that be the case you need to
1751 recompile or update your JDK. To recompile do the following ...
1755 cd /spider/spider-web
1757 /usr/bin/javac spiderclient.java
1761 I have used /usr/bin/javac as an example, your path to javac may be
1767 Completely based on a clx web client written in Java by dl6dbh
1768 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
1770 The webserver has to run on the same machine as your DxSpider software!
1772 It is assumed that you have Java installed. You need JDK1.3.1 at least.
1774 Installation instructions (Performed as root):
1776 Put all the files in the spider-web directory into a newly created directory
1777 under the DocumentRoot of your websever for instance 'client'. In my case
1778 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
1779 path should be /usr/local/httpd/htdocs/client/ for example.
1781 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
1782 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
1783 /usr/local/httpd/cgi-bin/ for example.
1785 Change the permissions of the files to ensure they are correct, obviously you
1786 will need to use the correct path the the files according to your system:
1788 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
1789 chmod -R 755 /home/httpd/html/client/
1791 By default the spider.cgi script should pick up your hostname (As long as this
1792 is set correctly). If it does not or your hostname differs from the name that
1793 you attach to the public address that you are using, then edit spider.cgi :
1795 # Uncomment and set the hostname manually here if the above fails.
1796 # $HOSTNAME = "gb7mbc.spoo.org" ;
1800 telnet (see Listeners.pm)
1802 NOTE: If you can start the console but cannot connect to the cluster from it,
1803 then it is possible that the machine you are on cannot resolve the hostname of
1804 your cluster machine. If this is the case, you need to set your hostname
1807 You also need to set the $NODECALL variable. This prints the name of your
1808 choosing (probably your cluster callsign) on the html page.
1810 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
1814 8. Web based statistics
1816 From version 1.50, you can use the freeware software MRTG to produce
1817 really nice graphical statistics on your web site. For an example try
1818 http://www.gb7mbc.net/mrtg/stats.html.
1821 The following should help you get it all working.
1824 First you need to download the latest version of MRTG from
1825 http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
1826 the following files..
1830 libpng-1.0.14.tar.gz
1836 Login to your machine as the root user, put all the downloaded files
1837 in /usr/local/src/ (or wherever you prefer) and untar and compile
1838 them. All the information to compile and install these sources come
1839 with them. After compilation and installation, you will find MRTG in
1843 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
1847 You now need to make 2 symbolic links like below...
1851 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
1852 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
1856 Now login to the cluster with your sysop callsign and run the command
1860 Now you are nearly there! Login as the sysop user and change to the
1861 /spider/html/mrtg/ directory. Now run the command indexmaker as shown
1866 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
1870 Changing the callsign for your own cluster callsign of course!
1873 And finally you need to login as the root user and create one last
1874 symbolic link. Where this points will depend on where your html
1875 documents are kept. For RedHat systems you use...
1879 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
1883 and for SuSE systems...
1887 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
1891 If you now point your browser to your website as below it should all
1896 http://www.xxx.xxx/mrtg/stats.html
1900 Of course, to get the stats to update, you need to add some
1901 information in the spider crontab file as below...
1905 # Update stats for mrtg on website
1906 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
1910 This will update the site every 5 minutes.
1915 From version 1.49 DXSpider has some additional security features.
1916 These are not by any means meant to be exhaustive, however they do
1917 afford some security against piracy. These two new features can be
1918 used independently of each other or in concert to tighten the
1924 The basic principle of registration is simple. If a user is not
1925 registered by the sysop, then they have read-only access to the
1926 cluster. The only thing they can actually send is a talk or a message
1927 to the sysop. In order for them to be able to spot, send announces or
1928 talks etc the sysop must register them with the set/register command,
1937 The user g0vgs can now fully use the cluster. In order to enable
1938 registration, you can issue the command ...
1940 set/var $main::reqreg = 1
1944 Any users that are not registered will now see the motd_nor file
1945 rather than the motd file as discussed in the Information, files and
1946 useful programs section.
1949 Entering this line at the prompt will only last for the time the
1950 cluster is running of course and would not be present on a restart.
1951 To make the change permanent, add the above line to
1952 /spider/scripts/startup. To read more on the startup file, see the
1953 section on Information, files and useful programs.
1956 To unregister a user use unset/register and to show the list of
1957 registered users, use the command show/register.
1962 At the moment, passwords only affect users who login to a DXSpider
1963 cluster node via telnet. If a user requires a password, they can
1964 either set it themselves or have the sysop enter it for them by using
1965 the set/password command. Any users who already have passwords, such
1966 as remote sysops, will be asked for their passwords automatically by
1967 the cluster. Using passwords in this way means that the user has a
1968 choice on whether to have a password or not. To force the use of
1969 passwords at login, issue the command ...
1973 set/var $main::passwdreq = 1
1977 at the cluster prompt. This can also be added to the
1978 /spider/scripts/startup file as above to make the change permanent.
1981 Of course, if you do this you will have to assign a password for each
1982 of your users. If you were asking them to register, it is anticipated
1983 that you would ask them to send you a message both to ask to be
1984 registered and to give you the password they wish to use.
1987 Should a user forget their password, it can be reset by the sysop by
1988 first removing the existing password and then setting a new one like
1993 unset/password g0vgs
1994 set/password g0vgs new_password
2002 10.1. CVS from a Linux platform
2004 CVS stands for "Concurrent Versions System" and the CVS for DXSpider
2005 is held at Sourceforge. This means that it is possible to update your
2006 DXSpider installation to the latest sources by using a few simple
2007 commands. A graphical interface to CVS for Windows is explained in
2011 Please be aware that if you update your system using CVS, it is
2012 possible that you could be running code that is very beta and not
2013 fully tested. There is a possibility that it could be unstable.
2016 I am of course assuming that you have a machine with both DXSpider and
2017 Internet access running.
2020 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
2021 ENTIRE SPIDER TREE!!
2024 Assuming you are connected to the Internet, you need to login to the
2025 CVS repository and then update your Spider source. There are several
2026 steps which are listed below ...
2029 First login as the user sysop. Next you need to connect to the CVS
2030 repository. You do this with the command below ...
2033 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2037 You will get a password prompt. Simply hit return here and your
2038 machine should return to a normal linux prompt.
2041 What happens next depends on whether you have an existing installation
2042 that you want to update with the latest and greatest or whether you
2043 just want to see what is there and/or run it on a new machine for
2046 If you are installing Spider from CVS then change directory to
2049 If you are wanting to update Spider then cd to /tmp
2052 The next step will create a brand new 'spider' directory in your
2056 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
2060 This command is all on one line.
2063 Hopefully your screen should show you downloading files. The -z3
2064 simply compresses the download to improve speed. When this has
2065 finished, you will have exactly the same as if you had untarred a full
2066 tarball PLUS some extra directories and files that CVS needs to do the
2068 Now if you are doing a new installation, that's it. Carry on as if
2069 you have just downloaded and untarred the lastest tarball.
2072 If you want to upgrade your current installation then do this ...
2076 tar cvfz /tmp/s.tgz spider
2078 tar xvfzp /tmp/s.tgz
2082 This is assuming you downloaded to the /tmp directory of course.
2085 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
2086 permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
2089 Remember to recompile the C client (cd /spider/src; make)
2092 At this point the files have been upgraded. You can (usually) restart
2093 the cluster in your own time. However, if you attempt to use any new
2094 commands or features expect it to be fatal! At least your cluster
2095 will have been restarted then so it will be too late to worry about
2099 Now the magic part! From now on when you want to update, simply
2100 connect to the Internet and then, as the user sysop ...
2109 and your files will be updated. As above, remember to recompile the
2110 "C" client if it has been updated (CVS will tell you) and restart if
2111 any of the perl scripts have been altered or added, again, CVS will
2115 You will find any changes documented in the /spider/Changes file.
2118 10.2. CVS from a Windows platform
2120 After the initial setup, an update to your DXSpider software is no
2121 more than a couple of clicks away. This section is intended to
2122 explain and illustrate the use of the WinCVS application to update
2123 your DXSpider software. The current stable version of WinCVS is Ver.
2124 1.2. You can get this software at:
2126 http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
2128 Pick your download mirror and then install WinCVS after the download
2132 In this next section I have included a series of links to .jpg files
2133 to take advantage of the picture and 1000 words equivalency. The .jpg
2134 files are in the C:\spider\html directory. If someone using a Linux
2135 system is reading this section from boredom, the files are in
2136 /home/sysop/spider/html. One aside, a Linux user can also get a copy
2137 of gcvs and do your updates graphically as opposed to from the command
2138 line. The following descriptions are almost identical between WinCvs
2139 and gcvs. The following screen shots have duplicate links, depending
2140 upon whether you are viewing this information under the Windows or
2141 Linux operating system.
2143 When WinCVS is installed, running, and you are connected to the
2144 internet, the initial screen looks like:
2148 If you want, you can also look at these .jpg files with another viewer
2149 that might provide some better clarity to the image. On the left is
2150 the directory tree for your hard disk. Notice that the spider
2151 directory has a gray highlight.
2153 To start configuring WinCVS, click on Admin at the top of the screen
2154 and then Preferences. This should get you:
2158 In the top line for CVSROOT, enter:
2161 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
2168 "passwd" file on the cvs server
2172 for Authentication on the General tab.
2174 Next, move to the right to the Ports tab.
2178 In here, check the box on the second line down for the "pserver" port.
2179 Enter a port number of 2401.
2181 Finally, go to the WinCvs tab all the way to the right.
2185 Enter Notepad as the viewer to open files. For the HOME folder, put
2186 "C:\spider" and click OK because the configuration is now complete.
2188 You are now ready to upgrade your copy of DXSpider. Click on the
2189 greyed Spider folder shown in the directory tree on the left of the
2190 WinCVS display. Two things should happen. The Spider folder will be
2191 selected and the greyed-out arrow located just below the word Query in
2192 the top line will turn to solid green.
2194 For anyone using gcvs under Linux, the green arrow is located on the
2195 extreme left of the display, under the word File. A gcvs screen looks
2200 Click on the now green arrow to start the download process. An Update
2201 Settings box will be displayed to which you can simply say OK.
2205 For future reference, the Update Settings box is the place where you
2206 can enter information to revert to a prior version of DXSpider.
2207 Information on reverting to a Before Date is contained in the WinCVS
2210 After a short period of time, a series of file names will scroll by in
2211 the lower pane of the WinCVS window. Eventually you should see
2214 *****CVS exited normally with code 0*****
2218 appear in the lower pane. You're done. The updated files are in
2219 place ready for you to stop and then restart your DXSpider. After the
2220 restart, you're running with the latest version of DXSpider.
2224 To paraphrase from the CVS section... Now the magic part! From now on
2225 when you want to update, simply connect to the Internet and start
2229 Click on the greyed-out Spider directory in the left screen
2230 Click on the green down arrow
2231 Click OK on the Update Settings dialog box
2232 Restart your Spider software
2236 11. The DXSpider command set
2240 accept Set a filter to accept something
2242 Create a filter to accept somethingThere are 2 types of filter, accept
2243 and reject. See HELP FILTERING for moreinfo.
2245 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
2247 accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
2250 This version allows a sysop to set a filter for a callsign as well as
2251 thedefault for nodes and users eg:-
2254 accept/ann by G,M,2 accept/ann input node_default by G,M,2 accept/ann user_default by G,M,2
2258 11.3. accept/announce [0-9] <pattern> (0)
2260 accept/announce [0-9] <pattern> Set an 'accept' filter line for
2263 Create an 'accept this announce' line for a filter. An accept filter
2264 line means that if the announce matches this filter it ispassed onto
2265 the user. See HELP FILTERING for more info. Please read thisto
2266 understand how filters work - it will save a lot of grief later on.You
2267 can use any of the following things in this line:-
2270 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)
2277 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)
2291 acc/ann by_state va,nh,ri,nh
2295 You can use the tag 'all' to accept everything eg:
2302 but this probably for advanced users...
2304 11.4. accept/route <call> [0-9] <pattern> (8)
2306 accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
2309 Create an 'accept this routing PC Protocol' line for a filter. An
2310 accept filter line means that if a PC16/17/19/21/24/41/50 matches this
2311 filter it is passed thru that interface. See HELP FILTERING for more
2312 info. Please read thisto understand how filters work - it will save a
2313 lot of grief later on.You can use any of the following things in this
2317 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
2324 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
2328 you can now use 'by' as a synonym for 'call' so:
2331 by = call by_dxcc = call_dxcc
2335 and so onYou can use the tag 'all' to accept everything eg:
2342 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
2344 accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
2346 This version allows a sysop to set a filter for a callsign as well as
2347 thedefault for nodes and users eg:-
2350 accept/spot db0sue-7 1 by_zone 14,15,16 accept/spot node_default all set/hops node_default 10
2354 accept/spot user_default by G,M,2
2358 11.6. accept/spots [0-9] <pattern> (0)
2360 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
2362 Create an 'accept this spot' line for a filter. An accept filter line
2363 means that if the spot matches this filter it ispassed onto the user.
2364 See HELP FILTERING for more info. Please read thisto understand how
2365 filters work - it will save a lot of grief later on.You can use any of
2366 the following things in this line:-
2369 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>
2373 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2377 You can use the tag 'all' to accept everything, eg:
2387 acc/spots by_state VA,NH,RI,MA,ME
2391 but this probably for advanced users...
2393 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
2395 accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
2397 This version allows a sysop to set a filter for a callsign as well as
2398 thedefault for nodes and users eg:-
2401 accept/wcy node_default all set/hops node_default 10
2405 11.8. accept/wcy [0-9] <pattern> (0)
2407 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
2409 It is unlikely that you will want to do this, but if you do then you
2410 canfilter on the following fields:-
2413 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>
2417 There are no examples because WCY Broadcasts only come from one place
2418 andyou either want them or not (see UNSET/WCY if you don't want
2419 them).This command is really provided for future use.See HELP FILTER
2422 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
2424 accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
2426 This version allows a sysop to set a filter for a callsign as well as
2427 thedefault for nodes and users eg:-
2430 accept/wwv db0sue-7 1 by_zone 4 accept/wwv node_default all set/hops node_default 10
2434 accept/wwv user_default by W,K
2438 11.10. accept/wwv [0-9] <pattern> (0)
2440 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
2442 It is unlikely that you will want to do this, but if you do then you
2443 canfilter on the following fields:-
2446 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>
2453 accept/wwv by_zone 4
2457 is probably the only useful thing to do (which will only show WWV
2458 broadcastsby stations in the US).See HELP FILTER for information.
2460 11.11. announce <text> (0)
2462 announce <text> Send an announcement to LOCAL users only
2464 <text> is the text of the announcement you wish to broadcast
2466 11.12. announce full <text> (0)
2468 announce full <text> Send an announcement cluster wide
2470 This will send your announcement cluster wide
2472 11.13. announce sysop <text> (5)
2474 announce sysop <text> Send an announcement to Sysops only
2477 11.14. apropos <string> (0)
2479 apropos <string> Search help database for <string>
2481 Search the help database for <string> (it isn't case sensitive), and
2482 printthe names of all the commands that may be relevant.
2484 11.15. blank [<string>] [<nn>] (0)
2486 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
2488 In its basic form this command prints one or more blank lines. However
2489 ifyou pass it a string it will replicate the string for the width of
2490 the screen (default 80) and then print that one or more times, so:
2497 prints two blank lines
2504 prints a row of - characters once.
2511 prints 'abcabcabcabcabcabc....'This is really only of any use in a
2512 script file and you can print a maximumof 9 lines.
2516 bye Exit from the cluster
2518 This will disconnect you from the cluster
2520 11.17. catchup <node call> all|[<msgno> ...] (5)
2522 catchup <node call> all|[<msgno> ...] Mark a message as sent
2525 11.18. clear/announce <callsign> [input] [0-9|all] (8)
2527 clear/announce <callsign> [input] [0-9|all] Clear a announce filter
2530 A sysop can clear an input or normal output filter for a user or
2531 thenode_default or user_default.
2533 11.19. clear/announce [1|all] (0)
2535 clear/announce [1|all] Clear a announce filter line
2537 This command allows you to clear (remove) a line in a annouce filter
2538 or to remove the whole filter.see CLEAR/SPOTS for a more detailed
2541 11.20. clear/route <callsign> [input] [0-9|all] (8)
2543 clear/route <callsign> [input] [0-9|all] Clear a route filter line
2545 A sysop can clear an input or normal output filter for a user or
2546 thenode_default or user_default.
2548 11.21. clear/route [1|all] (0)
2550 clear/route [1|all] Clear a route filter line
2552 This command allows you to clear (remove) a line in a route filter or
2553 to remove the whole filter.see CLEAR/SPOTS for a more detailed
2556 11.22. clear/spots <callsign> [input] [0-9|all] (8)
2558 clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
2560 A sysop can clear an input or normal output filter for a user or
2561 thenode_default or user_default.
2563 11.23. clear/spots [0-9|all] (0)
2565 clear/spots [0-9|all] Clear a spot filter line
2567 This command allows you to clear (remove) a line in a spot filter or
2568 to remove the whole filter.If you have a filter:-
2571 acc/spot 1 on hf/cw acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2581 you will be left with:-
2584 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2595 the filter will be completely removed.
2597 11.24. clear/wcy <callsign> [input] [0-9|all] (8)
2599 clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
2601 A sysop can clear an input or normal output filter for a user or
2602 thenode_default or user_default.
2604 11.25. clear/wcy [1|all] (0)
2606 clear/wcy [1|all] Clear a WCY filter line
2608 This command allows you to clear (remove) a line in a WCY filter or to
2609 remove the whole filter.see CLEAR/SPOTS for a more detailed
2612 11.26. clear/wwv <callsign> [input] [0-9|all] (8)
2614 clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
2616 A sysop can clear an input or normal output filter for a user or
2617 thenode_default or user_default.
2619 11.27. clear/wwv [1|all] (0)
2621 clear/wwv [1|all] Clear a WWV filter line
2623 This command allows you to clear (remove) a line in a WWV filter or to
2624 remove the whole filter.see CLEAR/SPOTS for a more detailed
2627 11.28. connect <callsign> (5)
2629 connect <callsign> Start a connection to another DX Cluster
2631 Start a connection process that will culminate in a new connection to
2632 theDX cluster <callsign>. This process creates a new 'client' process
2633 which willuse the script in /spider/connect/<callsign> to effect the
2634 'chat' exchangenecessary to traverse the network(s) to logon to the
2639 dbavail Show a list of all the Databases in the system
2641 Title says it all really, this command lists all the databases
2642 definedin the system. It is also aliased to SHOW/COMMAND.
2643 11.30. dbshow <dbname> <key> (0)
2645 dbshow <dbname> <key> Display an entry, if it exists, in a database
2647 This is the generic user interface to the database to the database
2648 system.It is expected that the sysop will add an entry to the local
2649 Aliases fileso that users can use the more familiar AK1A style of
2657 but if he hasn't and the database really does exist (use DBAVAIL
2658 orSHOW/COMMAND to find out) you can do the same thing with:
2665 11.31. directory (0)
2667 directory List messages
2670 11.32. directory <from>-<to> (0)
2672 directory <from>-<to> List messages <from> message <to> message
2674 List the messages in the messages directory.If there is a 'p' one
2675 space after the message number then it is a personal message. If there
2676 is a '-' between the message number and the'p' then this indicates
2677 that the message has been read.You can use shell escape characters
2678 such as '*' and '?' in the <call>fields.You can combine some of the
2679 various directory commands together eg:-
2689 DIR SUBJECT IOTA 200-250
2693 You can abbreviate all the commands to one letter and use ak1a syn-
2697 DIR/T G1* 10 DIR/S QSL 10-100 5
2701 11.33. directory <nn> (0)
2703 directory <nn> List last <nn> messages
2707 11.34. directory all (0)
2709 directory all List all messages
2712 11.35. directory from <call> (0)
2714 directory from <call> List all messages from <call>
2717 11.36. directory new (0)
2719 directory new List all new messages
2722 11.37. directory own (0)
2724 directory own List your own messages
2727 11.38. directory subject <string> (0)
2729 directory subject <string> List all messages with <string> in subject
2732 11.39. directory to <call> (0)
2734 directory to <call> List all messages to <call>
2737 11.40. directory- (5)
2741 Sysops can see all users' messages.
2743 11.41. disconnect <call> [<call> ...] (8)
2745 disconnect <call> [<call> ...] Disconnect a user or cluster
2747 Disconnect any <call> connected locally
2749 11.42. dx [by <call>] <freq> <call> <remarks> (0)
2751 dx [by <call>] <freq> <call> <remarks> Send a DX spot
2753 This is how you send a DX Spot to other users. You can, in fact,
2754 nowenter the <freq> and the <call> either way round.
2757 DX FR0G 144.600 DX 144.600 FR0G DX 144600 FR0G
2761 will all give the same result. You can add some remarks to the endof
2762 the command and they will be added to the spot.
2765 DX FR0G 144600 this is a test
2769 You can credit someone else by saying:-
2773 DX by G1TLH FR0G 144.600 he isn't on the cluster
2777 The <freq> is compared against the available bands set up in the clus-
2778 ter. See SHOW/BANDS for more information.
2780 11.43. echo <line> (0)
2782 echo <line> Echo the line to the output
2784 This command is useful in scripts and so forth for printing theline
2785 that you give to the command to the output. You can use thisin
2786 user_default scripts and the SAVE command for titling and so forthThe
2787 script will interpret certain standard "escape" sequences as follows:-
2790 \t - becomes a TAB character (0x09 in ascii) \a - becomes a BEEP character (0x07 in ascii) \n - prints a new line
2794 So the following example:-
2797 echo GB7DJK is a dxcluster
2804 GB7DJK is a dxcluster
2808 on the output. You don't need a \n on the end of the line you want to
2809 send.A more complex example:-
2812 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
2819 GB7DJK g1tlh Dirk g3xvf Richard
2825 11.44. filtering... (0)
2827 filtering... Filtering things in DXSpider
2829 There are a number of things you can filter in the DXSpider system.
2830 Theyall use the same general mechanism.In general terms you can create
2831 a 'reject' or an 'accept' filter whichcan have up to 10 lines in it.
2832 You do this using, for example:-
2835 accept/spots ..... reject/spots .....
2839 where ..... are the specific commands for that type of filter. There-
2840 are filters for spots, wwv, announce, wcy and (for sysops)connects.
2841 See each different accept or reject command reference formore
2842 details.There is also a command to clear out one or more lines in a
2843 filter andone to show you what you have set. They are:-
2846 clear/spots 1 clear/spots all
2857 There is clear/xxxx command for each type of filter.For now we are
2858 going to use spots for the examples, but you can applythe principles
2859 to all types of filter.There are two main types of filter 'accept' or
2860 'reject'; which you usedepends entirely on how you look at the world
2861 and what is leastwriting to achieve what you want. Each filter has 10
2862 lines (of anylength) which are tried in order. If a line matches then
2863 the actionyou have specified is taken (ie reject means ignore it and
2864 acceptmeans gimme it).The important thing to remember is that if you
2865 specify a 'reject'filter (all the lines in it say 'reject/spots' (for
2866 instance)) then ifa spot comes in that doesn't match any of the lines
2867 then you will getit BUT if you specify an 'accept' filter then any
2868 spots that don'tmatch are dumped. For example if I have a one line
2872 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2876 then automatically you will ONLY get VHF spots from or to CQ zones
2877 1415 and 16. If you set a reject filter like:
2880 reject/spots on hf/cw
2884 Then you will get everything EXCEPT HF CW spots, If you am interested
2885 in IOTAand will work it even on CW then you could say:-
2888 reject/spots on hf/cw and not info iota
2892 But in that case you might only be interested in iota and say:-
2895 accept/spots not on hf/cw or info iota
2899 which is exactly the same. You should choose one or the other untilyou
2900 are confortable with the way it works. Yes, you can mix them(actually
2901 you can have an accept AND a reject on the same line) butdon't try
2902 this at home until you can analyse the results that you getwithout
2903 ringing up the sysop for help.Another useful addition now is filtering
2905 accept/spots by_state VA,NH,RI,ME
2909 You can arrange your filter lines into logical units, either for
2910 yourown understanding or simply convenience. I have one set fre-
2914 reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2918 What this does is to ignore all HF CW spots (being a class B I
2919 can'tread any CW and couldn't possibly be interested in HF :-) and
2920 alsorejects any spots on VHF which don't either originate or spot
2921 someonein Europe.This is an exmaple where you would use the line num-
2922 ber (1 and 2 inthis case), if you leave the digit out, the system
2923 assumes '1'. Digits'0'-'9' are available.You can leave the word 'and'
2924 out if you want, it is implied. You canuse any number of brackets to
2925 make the 'expression' as you wantit. There are things called prece-
2926 dence rules working here which meanthat you will NEED brackets in a
2927 situation like line 2 because,without it, will assume:-
2930 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2934 annoying, but that is the way it is. If you use OR - usebrackets.
2935 Whilst we are here CASE is not important. 'And BY_Zone' isjust 'and
2936 by_zone'.If you want to alter your filter you can just redefine one or
2937 morelines of it or clear out one line. For example:-
2940 reject/spots 1 on hf/ssb
2951 To remove the filter in its entirty:-
2958 There are similar CLEAR commands for the other filters:-
2961 clear/announce clear/wcy clear/wwv
2965 ADVANCED USERS:-Once you are happy with the results you get, you may
2966 like to experiment. my example that filters hf/cw spots and accepts
2967 vhf/uhf spots from EUcan be written with a mixed filter, eg:
2971 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)
2975 each filter slot actually has a 'reject' slot and an 'accept'slot. The
2976 reject slot is executed BEFORE the accept slot.It was mentioned ear-
2977 lier that after a reject test that doesn't match,the default for fol-
2978 lowing tests is 'accept', the reverse is true for'accept'. In the
2979 example what happens is that the reject is executedfirst, any non
2980 hf/cw spot is passed to the accept line, which letsthru everything
2981 else on HF.The next filter line lets through just VHF/UHF spots from
2984 11.45. forward/latlong <node_call> (8)
2986 forward/latlong <node_call> Send latitude and longitude information to
2989 This command sends all the latitude and longitude information that
2990 yourcluster is holding against callsigns. One advantage of recieving
2991 thisinformation is that more locator information is held by you.
2992 Thismeans that more locators are given on the DX line assuming you
2993 haveSET/DXGRID enabled. This could be a LOT of information though,
2994 soit is not recommended on slow links.
2996 11.46. forward/opernam <call> (1)
2998 forward/opernam <call> Send out information on this <call> to all
3001 This command sends out any information held in the user file which can
3002 be broadcast in PC41 protocol packets. This information is Name, QTH,
3003 Locationand Homenode. PC41s are only sent for the information that is
3008 help The HELP Command
3010 HELP is available for a number of commands. The syntax is:-
3017 Where <cmd> is the name of the command you want help on.All commands
3018 can be abbreviated, so SHOW/DX can be abbreviatedto SH/DX, ANNOUNCE
3019 can be shortened to AN and so on.Look at the APROPOS <string> command
3020 which will search the help databasefor the <string> you specify and
3021 give you a list of likely commandsto look at with HELP.
3023 11.48. init <node> (5)
3025 init <node> Re-initialise a link to an AK1A compatible node
3027 This command attempts to re-initialise a link to a (usually) AK1A
3028 nodethat has got confused, usually by a protocol loop of some kind. It
3029 maywork - but you usually will be better off simply disconnecting it
3030 (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
3031 <yournode>).Best of luck - you will need it.
3037 As a sysop you can kill any message on the system.
3039 11.50. kill <from msgno>-<to msgno> (0)
3041 kill <from msgno>-<to msgno> Delete a range of messages
3044 11.51. kill <from>-<to> (5)
3046 kill <from>-<to> Remove a range of messages from the system
3049 11.52. kill <msgno> [<msgno..] (0)
3051 kill <msgno> [<msgno..] Delete a message from the local system
3054 11.53. kill <msgno> [<msgno> ...] (0)
3056 kill <msgno> [<msgno> ...] Remove or erase a message from the system
3058 You can get rid of any message to or originating from your callsign
3059 using this command. You can remove more than one message at a time.
3061 11.54. kill expunge <msgno> [<msgno..] (6)
3063 kill expunge <msgno> [<msgno..] Expunge a message
3065 Deleting a message using the normal KILL commands only marks that
3066 messagefor deletion. The actual deletion only happens later (usually
3067 two days later).The KILL EXPUNGE command causes the message to be
3068 truly deleted more or lessimmediately.It otherwise is used in the same
3069 way as the KILL command.
3071 11.55. kill from <call> (5)
3073 kill from <call> Remove all messages from a callsign
3076 11.56. kill full <msgno> [<msgno..] (5)
3078 kill full <msgno> [<msgno..] Delete a message from the whole cluster
3080 Delete a message from the local system. You will only be able todelete
3081 messages that you have originated or been sent (unless you arethe
3089 Will delete all the messages that you own between msgnos 1234 and
3097 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3103 will delete all messages to g1tlh.
3110 will delete a message (usually a 'bulletin') from the whole cluster
3111 system. This uses the subject field, so any messages that have exactly
3112 thesame subject will be deleted. Beware!
3114 11.57. kill full <msgno> [<msgno] (5)
3116 kill full <msgno> [<msgno] Remove a message from the entire cluster
3118 Remove this message from the entire cluster system as well as your
3121 11.58. kill to <call> (5)
3123 kill to <call> Remove all messages to a callsign
3126 11.59. kill from <regex> (0)
3128 kill from <regex> Delete messages FROM a callsign or pattern
3131 11.60. kill to <regex> (0)
3133 kill to <regex> Delete messages TO a callsign or pattern
3138 links Show which nodes is physically connected
3140 This is a quick listing that shows which links are connected andsome
3141 information about them. See WHO for a list of all connections.
3143 11.62. load/keps (5)
3145 load/keps Load new keps data
3148 11.63. load/keps [nn] (5)
3150 load/keps [nn] Load new keps data from message
3152 If there is no message number then reload the current Keps data
3153 fromthe Keps.pm data file. You create this file by running
3156 /spider/perl/convkeps.pl <filename>
3160 on a file containing NASA 2 line keps as a message issued by AMSAT. If
3161 there is a message number, then it will take the message, runcon-
3162 vkeps.pl on it and then load the data, all in one step.These messages
3163 are sent to ALL by GB7DJK (and others) from time to time.
3165 11.64. merge <node> [<no spots>/<no wwv>] (5)
3167 merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
3169 MERGE allows you to bring your spot and wwv database up to date. By
3170 defaultit will request the last 10 spots and 5 WWVs from the node you
3171 select. The node must be connected locally.You can request any number
3172 of spots or wwv and although they will be appendedto your databases
3173 they will not duplicate any that have recently been added (the last 2
3174 days for spots and last month for WWV data).
3176 11.65. pc <call> <text> (8)
3178 pc <call> <text> Send arbitrary text to a connected callsign
3180 Send some arbitrary text to a locally connected callsign. Noprocessing
3181 is done on the text. This command allows you to send PCProtocol to
3182 unstick things if problems arise (messages get stucketc). eg:-
3185 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3192 pc G1TLH Try doing that properly!!!
3196 Send any text you like to the callsign requested. This is used mainly
3197 to sendPC protocol to connected nodes either for testing or to unstick
3198 things. You can also use in the same way as a talk command to a con-
3199 nected user butwithout any processing, added of "from <blah> to <blah"
3202 11.66. ping <node call> (1)
3204 ping <node call> Check the link quality between nodes
3206 This command allows you to send a frame to another cluster node onthe
3207 network and get a return frame. The time it takes to do thisis a good
3208 indication of the quality of the link. The actual timeit takes is
3209 output to the console in seconds.Any visible cluster node can be
3212 11.67. rcmd <node call> <cmd> (1)
3214 rcmd <node call> <cmd> Send a command to another DX Cluster
3216 This command allows you to send nearly any command to another DX
3217 Clusternode that is connected to the system. Whether you get any
3218 output is dependant on a) whether the other system knowsthat the node
3219 callsign of this cluster is in fact a node b) whether theother system
3220 is allowing RCMDs from this node and c) whether you havepermission to
3221 send this command at all.
3225 read Read the next unread personal message addressed to you
3228 11.69. read <msgno> (0)
3230 read <msgno> Read the specified message
3232 You can read any messages that are sent as 'non-personal' and also
3233 anymessage either sent by or sent to your callsign.
3239 As a sysop you may read any message on the system
3243 reject Set a filter to reject something
3245 Create a filter to reject somethingThere are 2 types of filter, accept
3246 and reject. See HELP FILTERING for moreinfo.
3248 11.72. reject/announce <call> [input] [0-9] <pattern> (8)
3250 reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
3253 This version allows a sysop to set a filter for a callsign as well as
3254 thedefault for nodes and users eg:-
3257 reject/ann by G,M,2 reject/ann input node_default by G,M,2 reject/ann user_default by G,M,2
3261 11.73. reject/announce [0-9] <pattern> (0)
3263 reject/announce [0-9] <pattern> Set a 'reject' filter line for
3266 Create an 'reject this announce' line for a filter. A reject filter
3267 line means that if the announce matches this filter it ispassed onto
3268 the user. See HELP FILTERING for more info. Please read thisto
3269 understand how filters work - it will save a lot of grief later on.You
3270 can use any of the following things in this line:-
3273 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)
3280 rej/ann by_zone 14,15,16 and not by G,M,2
3284 You can use the tag 'all' to reject everything eg:
3291 but this probably for advanced users...
3293 11.74. reject/route <call> [0-9] <pattern> (8)
3295 reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
3298 Create an 'reject this routing PC Protocol' line for a filter. An
3299 reject filter line means that if a PC16/17/19/21/24/41/50 matches this
3300 filter it is NOT passed thru that interface. See HELP FILTERING for
3301 more info. Please read this to understand how filters work - it will
3302 save a lot of grief later on.You can use any of the following things
3306 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
3313 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3317 You can use the tag 'all' to reject everything eg:
3320 rej/route all (equiv to [very] restricted mode)
3324 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3326 11.75. reject/spots <call> [input] [0-9] <pattern> (8)
3328 reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
3330 This version allows a sysop to set a filter for a callsign as well as
3331 thedefault for nodes and users eg:-
3334 reject/spot db0sue-7 1 by_zone 14,15,16 reject/spot node_default all set/hops node_default 10
3338 reject/spot user_default by G,M,2
3342 11.76. reject/spots [0-9] <pattern> (0)
3344 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
3346 Create a 'reject this spot' line for a filter. A reject filter line
3347 means that if the spot matches this filter it isdumped (not passed
3348 on). See HELP FILTERING for more info. Please read thisto understand
3349 how filters work - it will save a lot of grief later on.You can use
3350 any of the following things in this line:-
3353 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>
3357 rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3361 You can use the tag 'all' to reject everything eg:
3368 but this probably for advanced users...
3370 11.77. reject/wcy <call> [input] [0-9] <pattern> (8)
3372 reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
3374 This version allows a sysop to set a filter for a callsign as well as
3375 thedefault for nodes and users eg:-
3378 reject/wcy gb7djk all
3382 11.78. reject/wcy [0-9] <pattern> (0)
3384 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
3386 It is unlikely that you will want to do this, but if you do then you
3387 canfilter on the following fields:-
3390 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>
3394 There are no examples because WCY Broadcasts only come from one place
3395 andyou either want them or not (see UNSET/WCY if you don't want
3396 them).This command is really provided for future use.See HELP FILTER
3399 11.79. reject/wwv <call> [input] [0-9] <pattern> (8)
3401 reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
3403 This version allows a sysop to set a filter for a callsign as well as
3404 thedefault for nodes and users eg:-
3407 reject/wwv db0sue-7 1 by_zone 4 reject/wwv node_default all
3411 reject/wwv user_default by W
3415 11.80. reject/wwv [0-9] <pattern> (0)
3417 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
3419 It is unlikely that you will want to do this, but if you do then you
3420 canfilter on the following fields:-
3423 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>
3430 reject/wwv by_zone 14,15,16
3434 is probably the only useful thing to do (which will only show WWV
3435 broadcastsby stations in the US).See HELP FILTER for information.
3439 reply Reply (privately) to the last message that you have read
3442 11.82. reply <msgno> (0)
3444 reply <msgno> Reply (privately) to the specified message
3447 11.83. reply b <msgno> (0)
3449 reply b <msgno> Reply as a Bulletin to the specified message
3452 11.84. reply noprivate <msgno> (0)
3454 reply noprivate <msgno> Reply as a Bulletin to the specified message
3457 11.85. reply rr <msgno> (0)
3459 reply rr <msgno> Reply to the specified message with read receipt
3461 You can reply to a message and the subject will automatically
3462 have"Re:" inserted in front of it, if it isn't already present.You can
3463 also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B
3464 that you can use with the SEND command (see SENDfor further details)
3466 11.86. send <call> [<call> ...] (0)
3468 send <call> [<call> ...] Send a message to one or more callsigns
3471 11.87. send copy <msgno> <call> (0)
3473 send copy <msgno> <call> Send a copy of a message to someone
3476 11.88. send noprivate <call> (0)
3478 send noprivate <call> Send a message to all stations
3480 All the SEND commands will create a message which will be sent either
3481 toan individual callsign or to one of the 'bulletin' addresses. SEND
3482 <call> on its own acts as though you had typed SEND PRIVATE, that isit
3483 will mark the message as personal and send it to the cluster node
3484 thatthat callsign is connected to. If the <call> you have specified is
3485 in facta known bulletin category on your node (eg: ALL) then the
3486 message shouldautomatically become a bulletin.You can have more than
3487 one callsign in all of the SEND commands.You can have multiple
3488 qualifiers so that you can have for example:-
3489 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3493 which should send a copy of message 123 to G1TLH and G0RDI and you
3494 willreceive a read receipt when they have read the message.SB is an
3495 alias for SEND NOPRIVATE (or send a bulletin in BBS speak)SP is an
3496 alias for SEND PRIVATEThe system will ask you for a subject. Conven-
3497 tionally this should be no longer than 29 characters for compatibil-
3498 ity. Most modern clustersoftware should accept more.You will now be
3499 prompted to start entering your text. You finish the message by enter-
3500 ing '/EX' on a new line. For instance:
3503 ... bye then Jim 73 Dirk /ex
3507 If you have started a message and you don't want to keep it then you-
3508 can abandon the message with '/ABORT' on a new line, like:-
3511 line 1 line 2 oh I just can't be bothered with this /abort
3515 If you abort the message it will NOT be sent.When you are entering the
3516 text of your message, most normal output (suchas DX announcements and
3517 so on are suppressed and stored for latter display(upto 20 such lines
3518 are stored, as new ones come along, so the oldestlines are
3519 dropped).Also, you can enter normal commands commands (and get the
3520 output immediately) whilst in the middle of a message. You do this by
3521 typingthe command preceeded by a '/' character on a new line, so:-
3524 /dx g1tlh 144010 strong signal
3528 Will issue a dx annoucement to the rest of the cluster. Also, you can
3529 add the output of a command to your message by preceeding the command
3537 This will show YOU the output from SH/VHFTABLE and also store it in
3538 themessage. You can carry on with the message until you are ready to
3541 11.89. send private <call> (0)
3543 send private <call> Send a personal message
3546 11.90. send rr <call> (0)
3548 send rr <call> Send a message and ask for a read receipt
3551 11.91. set/address <your address> (0)
3553 set/address <your address> Record your postal address
3555 11.92. set/announce (0)
3557 set/announce Allow announce messages to come out on your terminal
3560 11.93. set/anntalk (0)
3562 set/anntalk Allow talk like announce messages on your terminal
3565 11.94. set/arcluster <call> [<call>..] (5)
3567 set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
3570 11.95. set/baddx <call>.. (8)
3572 set/baddx <call>.. Stop callsigns in a dx spot being propagated
3575 11.96. set/badnode <call>.. (8)
3577 set/badnode <call>.. Stop spots from this node being propagated
3580 11.97. set/badspotter <call>.. (8)
3582 set/badspotter <call>.. Stop spots from this callsign being propagated
3585 11.98. set/badword <word>.. (8)
3587 set/badword <word>.. Stop things with this word being propagated
3590 11.99. set/bbs <call> [<call>..] (5)
3592 set/bbs <call> [<call>..] Make the callsign a BBS
3595 11.100. set/beep (0)
3597 set/beep Add a beep to DX and other messages on your terminal
3600 11.101. set/clx <call> [<call>..] (5)
3602 set/clx <call> [<call>..] Make the callsign an CLX node
3607 set/dx Allow DX messages to come out on your terminal
3610 11.103. set/dxcq (0)
3612 set/dxcq Show CQ Zones on the end of DX announcements
3615 11.104. set/dxgrid (0)
3617 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
3621 11.105. set/dxitu (0)
3623 set/dxitu Show ITU Zones on the end of DX announcements
3626 11.106. set/dxnet <call> [<call>..] (5)
3628 set/dxnet <call> [<call>..] Make the callsign an DXNet node
3631 11.107. set/echo (0)
3633 set/echo Make the cluster echo your input
3636 11.108. set/email <email> ... (0)
3638 set/email <email> ... Set email address(es) and forward your personals
3641 11.109. set/here (0)
3643 set/here Tell the system you are present at your terminal
3646 11.110. set/homenode <node> (0)
3648 set/homenode <node> Set your normal cluster callsign
3650 Tell the cluster system where you normally connect to. Any Messages
3651 sentto you will normally find their way there should you not be
3659 11.111. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
3661 set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
3664 11.112. set/language <lang> (0)
3666 set/language <lang> Set the language you want to use
3668 You can select the language that you want the cluster to use.
3669 Currentlythe languages available are en (English), de (German), es
3670 (Spanish) and nl (Dutch).
3672 11.113. set/location <lat & long> (0)
3674 set/location <lat & long> Set your latitude and longitude
3677 11.114. set/logininfo (0)
3679 set/logininfo Inform when a station logs in locally
3682 11.115. set/name <your name> (0)
3684 set/name <your name> Set your name
3686 Tell the system what your name is eg:-
3693 11.116. set/node <call> [<call>..] (5)
3695 set/node <call> [<call>..] Make the callsign an AK1A cluster
3697 Tell the system that the call(s) are to be treated as AK1A cluster
3698 andfed PC Protocol rather normal user commands.
3700 11.117. set/obscount <count> <call> (8)
3702 set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
3704 From 1.35 onwards neighbouring nodes are pinged at regular intervals
3705 (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a
3706 'pump-up'counter which is decremented on every outgoing ping and then
3707 reset tothe 'obscount' value on every incoming ping. The default value
3708 of thisparameter is 2. What this means is that a neighbouring node
3709 will be pinged twice at (default) 300 second intervals and if no reply
3710 has been heard just beforewhat would be the third attempt, that node
3711 is disconnected.If a ping is heard then the obscount is reset to the
3712 full value. Usingdefault values, if a node has not responded to a ping
3713 within 15 minutes,it is disconnected.You can set this parameter
3714 between 1 and 9.It is STRONGLY recommended that you don't change the
3717 11.118. set/page <lines per page> (0)
3719 set/page <lines per page> Set the lines per page
3721 Tell the system how many lines you wish on a page when the number of
3722 lineof output from a command is more than this. The default is 20.
3723 Setting itexplicitly to 0 will disable paging.
3726 SET/PAGE 30 SET/PAGE 0
3730 The setting is stored in your user profile.
3732 11.119. set/password (0)
3734 set/password Set your own password
3736 This command only works for a 'telnet' user (currently). It willonly
3737 work if you have a password already set. This initial passwordcan only
3738 be set by the sysop.When you execute this command it will ask you for
3739 your old password,then ask you to type in your new password twice (to
3740 make sure youget it right). You may or may not see the data echoed on
3741 the screenas you type, depending on the type of telnet client you
3744 11.120. set/prompt <string> (0)
3746 set/prompt <string> Set your prompt to <string>
3750 11.121. set/qra <locator> (0)
3752 set/qra <locator> Set your QRA Grid locator
3754 Tell the system what your QRA (or Maidenhead) locator is. If you have
3755 notdone a SET/LOCATION then your latitude and longitude will be set
3756 roughlycorrectly (assuming your locator is correct ;-). For example:-
3763 11.122. set/qth <your qth> (0)
3765 set/qth <your qth> Set your QTH
3767 Tell the system where you are. For example:-
3770 SET/QTH East Dereham, Norfolk
3774 11.123. set/spider <call> [<call>..] (5)
3776 set/spider <call> [<call>..] Make the callsign an DXSpider node
3778 Tell the system that the call(s) are to be treated as DXSpider node
3779 andfed new style DX Protocol rather normal user commands.
3781 11.124. set/talk (0)
3783 set/talk Allow TALK messages to come out on your terminal
3786 11.125. set/usstate (0)
3788 set/usstate Allow US State info on the end of DX announcements
3793 set/wcy Allow WCY messages to come out on your terminal
3798 set/wwv Allow WWV messages to come out on your terminal
3803 set/wx Allow WX messages to come out on your terminal
3806 11.129. show/baddx (1)
3808 show/baddx Show all the bad dx calls in the system
3810 Display all the bad dx callsigns in the system, see SET/BADDXfor more
3814 11.130. show/badnode (1)
3816 show/badnode Show all the bad nodes in the system
3818 Display all the bad node callsigns in the system, see SET/BADNODEfor
3821 11.131. show/badspotter (1)
3823 show/badspotter Show all the bad spotters in the system
3825 Display all the bad spotter's callsigns in the system, see
3826 SET/BADSPOTTERfor more information.
3828 11.132. show/badword (1)
3830 show/badword Show all the bad words in the system
3832 Display all the bad words in the system, see SET/BADWORDfor more
3835 11.133. show/configuration [<node>] (0)
3837 show/configuration [<node>] Show all the nodes and users visible
3839 This command allows you to see all the users that can be seenand the
3840 nodes to which they are connected.This command is normally abbreviated
3841 to: sh/cNormally, the list returned will be just for the nodes from
3842 your country (because the list otherwise will be very long).
3849 will produce a complete list of all nodes. BE WARNED: the list that is
3850 returned can be VERY longIt is possible to supply a node or part of a
3851 prefix and you will get a list of the users for that node or list of
3852 nodes starting withthat prefix.
3863 11.134. show/configuration/node (0)
3865 show/configuration/node Show all the nodes connected locally
3867 Show all the nodes connected to this node.
3869 11.135. show/connect (1)
3871 show/connect Show all the active connections
3873 This command shows information on all the active connections known
3874 tothe node. This command gives slightly more information than WHO.
3877 11.136. show/contest <year and month> (0)
3879 show/contest <year and month> Show all the contests for a month
3881 Show all known contests which are maintained at
3882 http://www.sk3bg.se/contest/for a particular month or year. The format
3883 is reasonably flexible.For example:-
3886 SH/CONTEST sep2003 SH/CONTEST 03 march
3890 11.137. show/date [<prefix>|<callsign>] (0)
3892 show/date [<prefix>|<callsign>] Show the local time
3894 This is very nearly the same as SHOW/TIME, the only difference the
3895 formatof the date string if no arguments are given.If no prefixes or
3896 callsigns are given then this command returns the localtime and UTC as
3897 the computer has it right now. If you give some prefixesthen it will
3898 show UTC and UTC + the local offset (not including DST) atthe prefixes
3899 or callsigns that you specify.
3901 11.138. show/db0sdx <callsign> (0)
3903 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
3905 This command queries the DB0SDX QSL server on the internetand returns
3906 any information available for that callsign. This serviceis provided
3907 for users of this software by http://www.qslinfo.de.See also SHOW/QRZ,
3912 show/dx Interrogate the spot database
3914 If you just type SHOW/DX you will get the last so many spots(sysop
3915 configurable, but usually 10).In addition you can add any number of
3916 these commands in very nearlyany order to the basic SHOW/DX command,
3920 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>
3924 <number> - the number of spots you want <from>-<to> - <from> spot no <to> spot no in the selected list <from>/<to>
3928 <prefix> - for a spotted callsign beginning with <prefix> *<suffix> - for a spotted callsign ending in <suffix> *<string>* - for a spotted callsign containing <string>
3932 day <number> - starting <number> days ago day <from>-<to> - <from> days <to> days ago <from>/<to>
3936 info <text> - any spots containing <text> in the info or remarks
3940 by <call> - any spots spotted by <call> (spotter <call> is the same).
3944 qsl - this automatically looks for any qsl info on the call held in the spot database.
3948 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.
3952 qra [<locator>] - this will look for the specific locator if you specify one or else anything that looks like a locator.
3956 dxcc - treat the prefix as a 'country' and look for spots from that country regardless of actual prefix. eg dxcc oq2
3960 You can also use this with the 'by' keyword so eg by W dxcc
3968 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
3972 11.140. show/dxcc <prefix> (0)
3974 show/dxcc <prefix> Interrogate the spot database by country
3976 This command takes the <prefix> (which can be a full or partial
3977 callsign if desired), looks up which internal country number it isand
3978 then displays all the spots as per SH/DX for that country.This is now
3979 an alias for 'SHOW/DX DXCC' The options for SHOW/DX also apply to this
3983 SH/DXCC G SH/DXCC W on 20m iota
3985 This can be done with the SHOW/DX command like this:-
3988 SH/DX dxcc g SH/DX dxcc w on 20m iota
3992 11.141. show/dxqsl <callsign> (0)
3994 show/dxqsl <callsign> Show any QSL info gathered from spots
3996 The node collects information from the comment fields in spots
3997 (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a
3998 database.This command allows you to interrogate that database and if
3999 the callsignis found will display the manager(s) that people have
4000 spotted. This information is NOT reliable, but it is normally
4001 reasonably accurate ifit is spotted enough times.For example:-
4008 You can check the raw input spots yourself with:-
4015 This gives you more background information.
4017 11.142. show/dxstats [days] [date] (0)
4019 show/dxstats [days] [date] Show the DX Statistics
4021 Show the total DX spots for the last <days> no of days (default is
4022 31), starting from a <date> (default: today).
4024 11.143. show/files [<filearea> [<string>]] (0)
4026 show/files [<filearea> [<string>]] List the contents of a filearea
4028 SHOW/FILES on its own will show you a list of the various
4029 fileareasavailable on the system. To see the contents of a particular
4037 where <filearea> is the name of the filearea you want to see the con-
4038 tents of.You can also use shell globbing characters like '*' and '?'
4039 in astring to see a selection of files in a filearea eg:-
4042 SH/FILES bulletins arld*
4046 See also TYPE - to see the contents of a file.
4050 11.144. show/filter (0)
4052 show/filter Show the contents of all the filters you have set
4054 Show the contents of all the filters that are set. This command
4055 displaysall the filters set - for all the various categories.
4057 11.145. show/hfstats [days] [date] (0)
4059 show/hfstats [days] [date] Show the HF DX Statistics
4061 Show the HF DX spots breakdown by band for the last <days> no of days
4062 (default is 31), starting from a <date> (default: today).
4064 11.146. show/hftable [days] [date] [prefix ...] (0)
4066 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
4068 Show the HF DX Spotter table for the list of prefixes for the last
4069 <days> no of days (default is 31), starting from a <date> (default:
4070 today).If there are no prefixes then it will show the table for your
4071 country.Remember that some countries have more than one "DXCC country"
4072 in them(eg G :-), to show them (assuming you are not in G already
4073 which isspecially treated in the code) you must list all the relevant
4077 sh/hftable g gm gd gi gj gw gu
4081 Note that the prefixes are converted into country codes so you don't
4082 haveto list all possible prefixes for each country.If you want more or
4083 less days than the default simply include thenumber you require:-
4090 If you want to start at a different day, simply add the date in some
4094 sh/hftable 2 25nov02 sh/hftable 2 25-nov-02 sh/hftable 2 021125 sh/hftable 2 25/11/02
4098 This will show the stats for your DXCC for that CQWW contest weekend.
4099 You can specify either prefixes or full callsigns (so you can see how
4100 youdid against all your mates). You can also say 'all' which will then
4101 printthe worldwide statistics.
4108 11.147. show/hops <call> [ann|spots|route|wcy|wwv] (8)
4110 show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
4113 This command shows the hop counts set up for a node. You can
4114 specifywhich category you want to see. If you leave the category out
4115 then all the categories will be listed.
4117 11.148. show/isolate (1)
4119 show/isolate Show list of ISOLATED nodes
4122 11.149. show/log [<callsign>] (8)
4124 show/log [<callsign>] Show excerpts from the system log
4126 This command outputs a short section of the system log. On its ownit
4127 will output a general logfile. With the optional callsign it willshow
4128 output from the log associated with that callsign.
4130 11.150. show/moon [ndays] [<prefix>|<callsign>] (0)
4132 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
4134 Show the Moon rise and set times for a (list of) prefixes or
4135 callsigns, together with the azimuth and elevation of the sun
4136 currently at thoselocations.If you don't specify any prefixes or
4137 callsigns, it will show the times foryour QTH (assuming you have set
4138 it with either SET/LOCATION or SET/QRA),together with the current
4139 azimuth and elevation.In addition, it will show the illuminated
4140 fraction of the moons disk.If all else fails it will show the Moonrise
4141 and set times for the nodethat you are connected to. For example:-
4144 SH/MOON SH/MOON G1TLH W5UN
4148 You can also use this command to see into the past or the future, soif
4149 you want to see yesterday's times then do:-
4156 or in three days time:-
4163 Upto 366 days can be checked both in the past and in the future.Please
4164 note that the rise and set times are given as the UT times of rise and
4165 set on the requested UT day.
4167 11.151. show/muf <prefix> [<hours>][long] (0)
4169 show/muf <prefix> [<hours>][long] Show the likely propagation to a
4172 This command allow you to estimate the likelihood of you contactinga
4173 station with the prefix you have specified. The output assumes a
4174 modestpower of 20dBW and receiver sensitivity of -123dBm (about
4175 0.15muV/10dB SINAD)The result predicts the most likely operating
4176 frequencies and signallevels for high frequency (shortwave) radio
4177 propagation paths onspecified days of the year and hours of the day.
4178 It is most useful forpaths between 250 km and 6000 km, but can be used
4179 with reduced accuracyfor paths shorter or longer than this.The command
4180 uses a routine MINIMUF 3.5 developed by the U.S. Navy andused to
4181 predict the MUF given the predicted flux, day of the year,hour of the
4182 day and geographic coordinates of the transmitter andreceiver. This
4183 routine is reasonably accurate for the purposes here,with a claimed
4184 RMS error of 3.8 MHz, but much smaller and less complexthan the
4185 programs used by major shortwave broadcasting organizations,such as
4186 the Voice of America.The command will display some header information
4187 detailing itsassumptions, together with the locations, latitude and
4188 longitudes andbearings. It will then show UTC (UT), local time at the
4189 other end(LT), calculate the MUFs, Sun zenith angle at the midpoint of
4190 the path(Zen) and the likely signal strengths. Then for each frequency
4191 for whichthe system thinks there is a likelihood of a circuit it
4192 prints a value.The value is currently a likely S meter reading based
4193 on the conventional6dB / S point scale. If the value has a '+'
4194 appended it means that it is1/2 an S point stronger. If the value is
4195 preceeded by an 'm' it means thatthere is likely to be much fading and
4196 by an 's' that the signal is likelyto be noisy. By default SHOW/MUF
4197 will show the next two hours worth of data. Youcan specify anything up
4198 to 24 hours worth of data by appending the no ofhours required after
4199 the prefix. For example:-
4209 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
4213 indicating that you will have weak, fading circuits on top band and
4214 80m but usable signals on 40m (about S3).inputing:-
4221 will get you the above display, but with the next 24 hours worth
4225 SH/MUF W L 24 SH/MUF W 24 Long
4229 Gives you an estimate of the long path propagation characterics.
4230 Itshould be noted that the figures will probably not be very useful,
4231 norterrible accurate, but it is included for completeness.
4233 11.152. show/newconfiguration [<node>] (0)
4235 show/newconfiguration [<node>] Show all the nodes and users visible
4237 This command allows you to see all the users that can be seenand the
4238 nodes to which they are connected. This command produces essentially
4239 the same information as SHOW/CONFIGURATION except that it shows all
4240 the duplication ofany routes that might be present It also uses a
4241 different formatwhich may not take up quite as much space if you don't
4242 have anyloops.BE WARNED: the list that is returned can be VERY long
4246 11.153. show/newconfiguration/node (0)
4248 show/newconfiguration/node Show all the nodes connected locally
4250 Show all the nodes connected to this node in the new format.
4252 11.154. show/node [<callsign> ...] (1)
4254 show/node [<callsign> ...] Show the type and version number of nodes
4256 Show the type and version (if connected) of the nodes specified on
4257 thecommand line. If no callsigns are specified then a sorted list of
4258 allthe non-user callsigns known to the system will be displayed.
4260 11.155. show/prefix <callsign> (0)
4262 show/prefix <callsign> Interrogate the prefix database
4264 This command takes the <callsign> (which can be a full or partial
4265 callsign or a prefix), looks up which internal country number it is
4266 and then displays all the relevant prefixes for that countrytogether
4267 with the internal country no, the CQ and ITU regions. See also
4270 11.156. show/program (5)
4272 show/program Show the locations of all the included program modules
4274 Show the name and location where every program module was load from.
4275 Thisis useful for checking where you think you have loaded a .pm file
4278 11.157. show/qra <lat> <long> (0)
4280 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
4282 This is a multipurpose command that allows you either to calculate
4283 thedistance and bearing between two locators or (if only one locator
4284 isgiven on the command line) the distance and beraing from your
4285 stationto the locator. For example:-
4288 SH/QRA IO92QL SH/QRA JN06 IN73
4292 The first example will show the distance and bearing to the locator
4293 fromyourself, the second example will calculate the distance and bear-
4294 ing fromthe first locator to the second. You can use 4 or 6 character
4295 locators.It is also possible to convert a latitude and longitude to a
4296 locator by using this command with a latitude and longitude as an
4297 argument, forexample:-
4300 SH/QRA 52 41 N 0 58 E
4304 11.158. show/qra <locator> [<locator>] (0)
4306 show/qra <locator> [<locator>] Show distance between QRA Grid locators
4310 11.159. show/qrz <callsign> (0)
4312 show/qrz <callsign> Show any callbook details on a callsign
4314 This command queries the QRZ callbook server on the internetand
4315 returns any information available for that callsign. This serviceis
4316 provided for users of this software by http://www.qrz.com See also
4317 SHOW/WM7D for an alternative.
4319 11.160. show/route <callsign> ... (0)
4321 show/route <callsign> ... Show the route to the callsign
4323 This command allows you to see to which node the callsigns specified
4324 areconnected. It is a sort of inverse sh/config.
4331 11.161. show/satellite <name> [<hours> <interval>] (0)
4333 show/satellite <name> [<hours> <interval>] Show tracking data
4335 Show the tracking data from your location to the satellite of your
4336 choicefrom now on for the next few hours.If you use this command
4337 without a satellite name it will display a listof all the satellites
4338 known currently to the system. If you give a name then you can obtain
4339 tracking data of all the passesthat start and finish 5 degrees below
4340 the horizon. As default it willgive information for the next three
4341 hours for every five minute period.You can alter the number of hours
4342 and the step size, within certain limits. Each pass in a period is
4343 separated with a row of '-----' charactersSo for example:-
4346 SH/SAT AO-10 SH/SAT FENGYUN1 12 2
4350 11.162. show/station all [<regex>] (6)
4352 show/station all [<regex>] Show list of users in the system
4355 11.163. show/station [<callsign> ..] (0)
4357 show/station [<callsign> ..] Show information about a callsign
4359 Show the information known about a callsign and whether (and
4360 where)that callsign is connected to the cluster.
4367 If no callsign is given then show the information for yourself.
4369 11.164. show/sun [ndays] [<prefix>|<callsign>] (0)
4371 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
4374 Show the sun rise and set times for a (list of) prefixes or callsigns,
4375 together with the azimuth and elevation of the sun currently at
4376 thoselocations.If you don't specify any prefixes or callsigns, it will
4377 show the times foryour QTH (assuming you have set it with either
4378 SET/LOCATION or SET/QRA),together with the current azimuth and
4379 elevation.If all else fails it will show the sunrise and set times for
4380 the nodethat you are connected to. For example:-
4383 SH/SUN SH/SUN G1TLH K9CW ZS
4387 You can also use this command to see into the past or the future, soif
4388 you want to see yesterday's times then do:-
4395 or in three days time:-
4402 Upto 366 days can be checked both in the past and in the future.Please
4403 note that the rise and set times are given as the UT times of rise and
4404 set on the requested UT day.
4406 11.165. show/time [<prefix>|<callsign>] (0)
4408 show/time [<prefix>|<callsign>] Show the local time
4410 If no prefixes or callsigns are given then this command returns the
4411 localtime and UTC as the computer has it right now. If you give some
4412 prefixesthen it will show UTC and UTC + the local offset (not
4413 including DST) atthe prefixes or callsigns that you specify.
4415 11.166. show/usdb [call ..] (0)
4417 show/usdb [call ..] Show information held on the FCC Call database
4419 Show the City and State of a Callsign held on the FCC database ifhis
4420 is being run on this system, eg:-
4427 11.167. show/vhfstats [days] [date] (0)
4429 show/vhfstats [days] [date] Show the VHF DX Statistics
4431 Show the VHF DX spots breakdown by band for the last <days> no of days
4432 (default is 31), starting from a date (default: today).
4434 11.168. show/vhftable [days] [date] [prefix ...] (0)
4436 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
4439 Show the VHF DX Spotter table for the list of prefixes for the last
4440 <days> no of days (default is 31), starting from a date (default:
4441 today).If there are no prefixes then it will show the table for your
4442 country.Remember that some countries have more than one "DXCC country"
4443 in them(eg G :-), to show them (assuming you are not in G already
4444 which isspecially treated in the code) you must list all the relevant
4448 sh/vhftable g gm gd gi gj gw gu
4452 Note that the prefixes are converted into country codes so you don't
4453 haveto list all possible prefixes for each country.If you want more or
4454 less days than the default simply include thenumber you require:-
4461 If you want to start at a different day, simply add the date in some
4465 sh/vhftable 2 25nov02 sh/vhftable 2 25-nov-02 sh/vhftable 2 021125 sh/vhftable 2 25/11/02
4469 This will show the stats for your DXCC for that CQWW contest weekend.
4470 You can specify either prefixes or full callsigns (so you can see how
4471 youdid against all your mates). You can also say 'all' which will then
4472 printthe worldwide statistics.
4479 11.169. show/wcy (0)
4481 show/wcy Show last 10 WCY broadcasts
4484 11.170. show/wcy <n> (0)
4486 show/wcy <n> Show last <n> WCY broadcasts
4488 Display the most recent WCY information that has been received by the
4491 11.171. show/wm7d <callsign> (0)
4493 show/wm7d <callsign> Show callbook details on a US callsigns
4495 This command queries the WM7D callbook server on the internetand
4496 returns any information available for that US callsign. This serviceis
4497 provided for users of this software by http://www.wm7d.net.See also
4500 11.172. show/wwv (0)
4502 show/wwv Show last 10 WWV broadcasts
4504 11.173. show/wwv <n> (0)
4506 show/wwv <n> Show last <n> WWV broadcasts
4508 Display the most recent WWV information that has been received by the
4511 11.174. shutdown (5)
4513 shutdown Shutdown the cluster
4515 Shutdown the cluster and disconnect all the users
4517 11.175. stat/channel [<callsign>] (5)
4519 stat/channel [<callsign>] Show the status of a channel on the cluster
4521 Show the internal status of the channel object either for the channel
4522 that you are on or else for the callsign that you asked for.Only the
4523 fields that are defined (in perl term) will be displayed.
4525 11.176. stat/db <dbname> (5)
4527 stat/db <dbname> Show the status of a database
4529 Show the internal status of a database descriptor.Depending on your
4530 privilege level you will see more or less information. This command is
4531 unlikely to be of much use to anyone other than a sysop.
4533 11.177. stat/msg (1)
4535 stat/msg Show the status of the message system
4538 11.178. stat/msg <msgno> (1)
4540 stat/msg <msgno> Show the status of a message
4542 This command shows the internal status of a message and includes
4543 informationsuch as to whom it has been forwarded, its size, origin etc
4544 etc.If no message number is given then the status of the message
4545 system is displayed.
4547 11.179. stat/route_node <callsign> (5)
4549 stat/route_node <callsign> Show the data in a Route::Node object
4552 11.180. stat/route_node all (5)
4554 stat/route_node all Show list of all Route::Node objects
4557 11.181. stat/route_user <callsign> (5)
4559 stat/route_user <callsign> Show the data in a Route::User object
4562 11.182. stat/route_user all (5)
4564 stat/route_user all Show list of all Route::User objects
4568 11.183. stat/user [<callsign>] (5)
4570 stat/user [<callsign>] Show the full status of a user
4572 Shows the full contents of a user record including all the secret
4573 flagsand stuff.Only the fields that are defined (in perl term) will be
4578 sysop Regain your privileges if you login remotely
4580 The system automatically reduces your privilege level to that of
4581 anormal user if you login in remotely. This command allows you
4582 toregain your normal privilege level. It uses the normal system:
4583 fivenumbers are returned that are indexes into the character array
4584 that isyour assigned password (see SET/PASSWORD). The indexes start
4585 fromzero.You are expected to return a string which contains the
4586 charactersrequired in the correct order. You may intersperse those
4587 characterswith others to obscure your reply for any watchers. For
4588 example (andthese values are for explanation :-):
4591 password = 012345678901234567890123456789 > sysop 22 10 15 17 3
4598 aa2bbbb0ccc5ddd7xxx3n or 2 0 5 7 3 or 20573
4602 They will all match. If there is no password you will still be
4603 offerednumbers but nothing will happen when you input a string. Any
4604 match iscase sensitive.
4606 11.185. talk <call> > <node> [<text>] (0)
4608 talk <call> > <node> [<text>] Send a text message to another station
4611 Send a short message to any other station that is visible on the
4612 clustersystem. You can send it to anyone you can see with a
4613 SHOW/CONFIGURATION command, they don't have to be connected
4614 locally.The second form of TALK is used when other cluster nodes are
4615 connectedwith restricted information. This usually means that they
4616 don't send the user information usually associated with logging on and
4617 off the cluster.If you know that G3JNB is likely to be present on
4618 GB7TLH, but you can onlysee GB7TLH in the SH/C list but with no users,
4619 then you would use thesecond form of the talk message.If you want to
4620 have a ragchew with someone you can leave the text messageout and the
4621 system will go into 'Talk' mode. What this means is that ashort
4622 message is sent to the recipient telling them that you are in
4623 a'Talking' frame of mind and then you just type - everything you send
4624 willgo to the station that you asked for. All the usual announcements,
4625 spots and so on will still come out on yourterminal.If you want to do
4626 something (such as send a spot) you preceed the normal command with a
4630 /DX 14001 G1TLH What's a B class licensee doing on 20m CW? /HELP talk
4634 To leave talk mode type:
4641 If you are in 'Talk' mode, there is an extention to the '/' command
4642 whichallows you to send the output to all the people you are talking
4643 to. You do with the '//' command. For example:-
4650 will send the hftable as you have it to all the people you are cur-
4653 11.186. talk <call> [<text>] (0)
4655 talk <call> [<text>] Send a text message to another station
4658 11.187. type <filearea>/<name> (0)
4660 type <filearea>/<name> Look at the contents of a file in one of the
4663 Type out the contents of a file in a filearea. So, for example, in
4664 filearea 'bulletins' you want to look at file 'arld051' you would
4668 TYPE bulletins/arld051
4672 See also SHOW/FILES to see what fileareas are available and a list of
4675 11.188. uncatchup <node call> all|[msgno> ...] (5)
4677 uncatchup <node call> all|[msgno> ...] Unmark a message as sent
4679 When you send messages the fact that you have forwarded it to another
4680 node is remembered so that it isn't sent again. When you have a new
4681 partnernode and you add their callsign to your /spider/msg/forward.pl
4682 file, alloutstanding non-private messages will be forwarded to them.
4683 This may wellbe ALL the non-private messages. You can prevent this by
4684 using these commmands:-
4687 catchup GB7DJK all catchup GB7DJK 300 301 302 303 500-510
4691 and to undo what you have just done:-
4694 uncatchup GB7DJK all uncatchup GB7DJK 300 301 302 303 500-510
4698 which will arrange for them to be forward candidates again.Order is
4700 11.189. unset/announce (0)
4702 unset/announce Stop announce messages coming out on your terminal
4705 11.190. unset/anntalk (0)
4707 unset/anntalk Stop talk like announce messages on your terminal
4709 The announce system on legacy cluster nodes is used as a talk
4710 substitute because the network is so poorly connected. If you:
4717 you will suppress several of these announces, you may miss the odd
4718 useful one as well, but you would probably miss them anyway in thewel-
4719 ter of useless ones.
4726 allows you to see them again. This is the default.
4728 11.191. unset/baddx <call>.. (8)
4730 unset/baddx <call>.. Propagate a dx spot with this callsign again
4732 Setting a word as 'baddx' will prevent spots with that word in
4733 the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
4734 anyfurther. They will not be displayed and they will not be sent
4735 ontoother nodes.The word must be written in full, no wild cards are
4739 set/baddx FORSALE VIDEO FR0G
4743 To allow a word again, use the following command ...
4750 11.192. unset/badnode <call>.. (8)
4752 unset/badnode <call>.. Allow spots from this node again
4754 Setting a callsign as a 'badnode' will prevent spots from that node
4755 going any further. They will not be displayed and they will not be
4756 sent onto other nodes.The call must be a full eg:-
4763 will stop anything from K1TTT. If you want SSIDs as well then you mus-
4764 tenter them specifically.
4769 will allow spots from him again.Use with extreme care. This command
4770 may well be superceeded by FILTERing.
4772 11.193. unset/badspotter <call>.. (8)
4774 unset/badspotter <call>.. Allow spots from this callsign again
4776 Setting a callsign as a 'badspotter' will prevent spots from this
4777 callsign going any further. They will not be displayed and they will
4778 not be sent onto other nodes.The call must be written in full, no wild
4779 cards are allowed eg:-
4782 set/badspotter VE2STN
4786 will stop anything from VE2STN. This command will automaticallystop
4787 spots from this user, regardless of whether or which SSID he uses. DO
4788 NOT USE SSIDs in the callsign, just use the callsignas above or below.
4791 unset/badspotter VE2STN
4795 will allow spots from him again.Use with extreme care. This command
4796 may well be superceded by FILTERing.
4798 11.194. unset/badword <word>.. (8)
4800 unset/badword <word>.. Propagate things with this word again
4802 Setting a word as a 'badword' will prevent things like spots,announces
4803 or talks with this word in the the text part from going anyfurther.
4804 They will not be displayed and they will not be sent ontoother
4805 nodes.The word must be written in full, no wild cards are allowed eg:-
4808 set/badword annihilate annihilated annihilation
4812 will stop anything with these words in the text.
4815 unset/badword annihilated
4819 will allow text with this word again.
4821 11.195. unset/beep (0)
4823 unset/beep Stop beeps for DX and other messages on your terminal
4826 11.196. unset/dx (0)
4828 unset/dx Stop DX messages coming out on your terminal
4831 11.197. unset/dxcq (0)
4833 unset/dxcq Stop CQ Zones on the end of DX announcements
4835 Display both the Spotter's and the Spotted's CQ Zone on the endof a DX
4836 announcement (there is just enough room). Some user programscannot
4837 cope with this. The Spotter's CQ is on the RHS of the time, the
4838 Spotted's CQ is on the LHS.Conflicts with: SET/DXGRID, SET/DXITU,
4839 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
4842 11.198. unset/dxgrid (0)
4844 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
4846 A standard feature which is enabled in version 1.43 and above is that
4847 if the spotter's grid square is known it is output on the endof a DX
4848 announcement (there is just enough room). Some user programscannot
4849 cope with this. You can use this command to reset (or set)this
4850 feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
4851 flags you have set if you are confused.
4853 11.199. unset/dxitu (0)
4855 unset/dxitu Stop ITU Zones on the end of DX announcements
4857 Display both the Spotter's and the Spotted's ITU Zone on the endof a
4858 DX announcement (there is just enough room). Some user programscannot
4859 cope with this. The Spotter's ITU is on the RHS of the time, the
4860 Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ,
4861 SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
4864 11.200. unset/echo (0)
4866 unset/echo Stop the cluster echoing your input
4868 If you are connected via a telnet session, different implimentationsof
4869 telnet handle echo differently depending on whether you are connected
4870 via port 23 or some other port. You can use this commandto change the
4871 setting appropriately. The setting is stored in your user profile.YOU
4872 DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
4874 11.201. unset/email (0)
4876 unset/email Stop personal msgs being forwarded by email
4878 If any personal messages come in for your callsign then you can
4879 usethese commands to control whether they are forwarded onto your
4880 emailaddress. To enable the forwarding do something like:-
4883 SET/EMAIL mike.tubby@somewhere.com
4887 You can have more than one email address (each one separated by a
4888 space).Emails are forwarded to all the email addresses you specify.You
4889 can disable forwarding by:-
4896 11.202. unset/here (0)
4898 unset/here Tell the system you are absent from your terminal
4901 11.203. unset/hops <call> ann|spots|route|wwv|wcy (8)
4903 unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
4905 Set the hop count for a particular type of broadcast for a node.This
4906 command allows you to set up special hop counts for a node for
4907 currently: announce, spots, wwv and wcy broadcasts.eg:
4910 set/hops gb7djk ann 10 set/hops gb7mbc spots 20
4914 Set SHOW/HOPS for information on what is already set. This commandcre-
4915 ates a filter and works in conjunction with the filter system. You can
4916 unset the hops with command UNSET/HOPS. For example:-
4919 unset/hops gb7djk ann unset/hops gb7mbc spots
4923 11.204. unset/logininfo (0)
4925 unset/logininfo Inform when a station logs out locally
4928 11.205. unset/privilege (0)
4930 unset/privilege Remove any privilege for this session
4932 You can use this command to 'protect' this session from
4933 unauthoriseduse. If you want to get your normal privilege back you
4934 will need toeither logout and login again (if you are on a console) or
4935 use theSYSOP command.
4937 11.206. unset/prompt (0)
4939 unset/prompt Set your prompt back to default
4941 This command will set your user prompt to exactly the string that you
4942 say. The point of this command to enable a user to interface to
4943 programsthat are looking for a specific prompt (or else you just want
4944 a differentfixed prompt).
4951 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
4954 11.207. unset/talk (0)
4956 unset/talk Stop TALK messages coming out on your terminal
4960 11.208. unset/usstate (0)
4962 unset/usstate Stop US State info on the end of DX announcements
4964 If the spotter's or spotted's US State is known it is output on the
4965 end of a DX announcement (there is just enough room). A spotter's
4966 state will appear on the RHS of the time (like SET/DXGRID) and the
4967 spotted's State will appear on the LHS of thetime field. Any
4968 information found will override any locator information from
4969 SET/DXGRID.Some user programs cannot cope with this. You can use this
4970 command to reset (or set) this feature.Conflicts with: SET/DXCQ,
4971 SET/DXITUDo a STAT/USER to see which flags you have set if you are
4974 11.209. unset/wcy (0)
4976 unset/wcy Stop WCY messages coming out on your terminal
4979 11.210. unset/wwv (0)
4981 unset/wwv Stop WWV messages coming out on your terminal
4984 11.211. unset/wx (0)
4986 unset/wx Stop WX messages coming out on your terminal
4991 who Show who is physically connected
4993 This is a quick listing that shows which callsigns are connected
4994 andwhat sort of connection they have
4996 11.213. wx <text> (0)
4998 wx <text> Send a weather message to local users
5001 11.214. wx full <text> (0)
5003 wx full <text> Send a weather message to all cluster users
5006 11.215. wx sysop <text> (5)
5008 wx sysop <text> Send a weather message to other clusters only
5010 Weather messages can sometimes be useful if you are experiencing an
5011 extremethat may indicate enhanced conditions