1 <!doctype linuxdoc system>
\r
5 <!-- Title information -->
\r
7 <title>The DXSpider Administration Manual v1.50</title>
\r
8 <author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and
\r
9 Charlie Carroll, K1XX, (k1xx@ptcnh.net)</author>
\r
10 <date>February 2003 revision 0.3</date>
\r
13 A reference for SysOps of the DXSpider DXCluster program.
\r
16 <!-- Table of contents -->
\r
19 <!-- Begin the document -->
\r
21 <sect>Routing and Filtering
\r
26 From DXSpider version 1.48, major changes were introduced to the way
\r
27 node connections are treated. This is part of an ongoing process to
\r
28 remove problems with loops and to enable talk and other functions to
\r
29 propagate across the whole of the worldwide cluster network. In fact,
\r
30 in a Spider network, it would be useful, perhaps even necessary to
\r
31 have loops. This would give real resilience to the network, meaning
\r
32 that if a link dropped, the information flow would simply come in and
\r
33 go out via a different route. Of course, we do not have a complete
\r
34 network of Spider nodes, there are other programs out there. Some of
\r
35 these do not have any protection from loops. Certainly AK1A does not
\r
36 handle loops well at all. It is therefore necessary to have some form
\r
37 of protection for these nodes.
\r
40 In fact DXSpider has had a simple system for some time which is called
\r
41 <it>isolation</it>. This is similar to what in other systems such as
\r
42 <bf>clx</bf>, is called <it>passive mode</it>. A more detailed explanation
\r
43 of <it>isolation</it> is given further below. This system is still available
\r
44 and, for simple networks, is probably all that you need.
\r
47 The new functionality introduced in version 1.48 allows filtering the node
\r
48 and user protocol frames on a "per interface" basis. We call this
\r
49 <it>route filtering</it>. This is used <bf>instead of</bf>
\r
50 <it>isolation</it>.
\r
53 What this really means is that you can control more or less completely
\r
54 which user and node management PC protocol frames pass to each of your
\r
55 partner nodes. You can also limit what comes into your node from your
\r
56 partners. It is even possible to control the settings that your partner
\r
57 node has for the routing information that it sends to you
\r
58 (using the <it>rcmd</it> command).
\r
60 <sect1>Route Filters
\r
63 Initially when route filters were being tested we generated a
\r
64 "default" filter. Unfortunately it quickly became apparent that this
\r
65 might suit the UK cluster network but didn't really fit anybody else.
\r
66 However using a default filter is an appropriate thing to do. How, is
\r
67 explained further on.
\r
70 The first thing that you must do is determine whether you need to use
\r
71 route filtering <bf>at all</bf>. If you are a "normal" node with two or
\r
72 three partners and you arranged in an "official" non-looping tree type
\r
73 network, then <bf>you do not need to do route filtering</bf> and you will
\r
74 feel a lot better for not getting involved. If you are successfully using
\r
75 <it>isolation</it> then you also probably don't need to use route filtering.
\r
78 To put it simply, you should not mix Isolation and Route Filtering. It
\r
79 will work, of sorts, but you will not get the expected results. If you
\r
80 are using Isolation sucessfully at the moment, do not get involved in
\r
81 Route Filtering unless you have a good supply of aspirin! Once you have
\r
82 started down the road of Route Filtering, do not use Isolation either.
\r
83 Use one or the other, not both.
\r
86 You will only require this functionality if you are "well-connected". What
\r
87 that means is that you are connected to several different parts of (say)
\r
88 the EU cluster and, at the same time, also connected to two or three places
\r
89 in the US which, in turn are connected back to the EU. This is called a
\r
90 "loop" and if you are seriously looped then you need filtering.
\r
93 I should at this stage give a little bit of background on filters. All
\r
94 the filters in Spider work in basically the same way. You can either
\r
95 accept or reject various options in order to create the filter rules
\r
96 you wish to achieve. Some filters are user settable, others can only
\r
97 be altered by the sysop. Route filtering can only be done by the sysop.
\r
100 Anyway, without further discouragement, let me start the process
\r
103 <sect1>The node_default filter
\r
106 All normal systems should have a default routing filter and it should
\r
107 usually be set to send only the normal, unlooped, view of your
\r
108 "national" network. Here in the UK that means nodes from the UK and
\r
109 Eire, in EU it is more complex as the networks there grew up in a more
\r
113 The generic commands are:-
\r
116 reject/route node_default <filter_option>
\r
120 accept/route node_default <filter_option>
\r
123 where filter_option is one of the following ...
\r
126 call <prefixes>
\r
127 call_dxcc <numbers>
\r
128 call_itu <numbers>
\r
129 call_zone <numbers>
\r
130 channel <prefixes>
\r
131 channel_dxcc <numbers>
\r
132 channel_itu <numbers>
\r
133 channel_zone <numbers>
\r
136 Please be careful if you alter this setting, it will affect
\r
137 <bf><it>ALL</it></bf> your links! Remember, this is a <it>default</it>
\r
138 filter for node connections, not a <it>per link</it> default.
\r
141 For the default routing filter then you have two real choices: either
\r
142 a "national" view or the "safe" option of only your own
\r
143 callsign. Examples of each (for my node: GB7DJK) are:-
\r
146 acc/route node_default call_dxcc 61,38
\r
147 acc/route node_default call gb7djk
\r
150 GB7DJK uses the first of these. The DXCC countries can be obtained from the
\r
151 <it>show/prefix</it> command.
\r
154 The example filters shown control <it>output</it> <bf>TO</bf> all your
\r
155 partner nodes unless they have a specific filter applied to them (see
\r
159 It is also possible to control the <it>incoming</it> routing
\r
160 information that you are prepared to accept <bf>FROM</bf> your partner
\r
161 nodes. The reason this is necessary is to make sure that stuff like
\r
162 mail, pings and similar commands a) go down the correct links and b)
\r
163 don't loop around excessively. Again using GB7DJK as an example a typical
\r
164 default input filter would be something like:
\r
167 rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
\r
170 What this does is accept node and user information for our national
\r
171 network from nodes that are in our national network, but rejects such
\r
172 information from anyone else. Although it doesn't explicitly say so,
\r
173 by implication, any other node information (not from the UK and Eire)
\r
177 As I imagine it will take a little while to get one's head around all of
\r
178 this you can study the effect of any rules that you try by watching the
\r
179 debug output after having done:-
\r
185 After you have got tired of that, to put it back the way it was:-
\r
191 <sect1>General route filtering
\r
194 Exactly the same rules apply for general route filtering. You would
\r
195 use either an accept filter or a reject filter like this ...
\r
198 reject/route <node_call> <filter_option>
\r
202 accept/route <node_call> <filter_option>
\r
206 Here are some examples of route filters ...
\r
209 rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
\r
210 rej/route all (equiv to [very] restricted mode)
\r
211 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
\r
212 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
\r
215 In practice you will either be opening the default filter out for a
\r
216 partner by defining a specific filter for that callsign:-
\r
219 acc/route gb7baa all
\r
220 acc/route gb7baa input all
\r
223 or restricting it quite a lot, in fact making it very nearly like an
\r
224 <it>isolated</it> node, like this:-
\r
227 acc/route pi4ehv-8 call gb7djk
\r
228 rej/route pi4ehv-8 input call_dxcc 61,38
\r
231 This last example takes everything except UK and Eire from PI4EHV-8
\r
232 but only sends him my local configuration (just a PC19 for GB7DJK and
\r
233 PC16s for my local users).
\r
236 It is possible to write <bf>much</bf> more complex rules, there are up
\r
237 to 10 accept/reject pairs per callsign per filter. For more information
\r
238 see the next section.
\r
241 <sect1>General filter rules
\r
244 Upto v1.44 it was not possible for the user to set their own filters. From
\r
245 v1.45 though that has all changed. It is now possible to set filters for just
\r
246 about anything you wish. If you have just updated from an older version of
\r
247 DXSpider you will need to update your new filters. You do not need to do
\r
248 anything with your old filters, they will be renamed as you update.
\r
251 There are 3 basic commands involved in setting and manipulating filters. These
\r
252 are <em>accept</em>, <em>reject</em> and <em>clear</em>. First we will look
\r
253 generally at filtering. There are a number of things you can filter in the
\r
254 DXSpider system. They all use the same general mechanism.
\r
257 In general terms you can create a "reject" or an "accept" filter which can have
\r
258 up to 10 lines in it. You do this using, for example ...
\r
265 where ..... are the specific commands for that type of filter. There are filters
\r
266 for spots, wwv, announce, wcy and (for sysops) connects. See each different
\r
267 accept or reject command reference for more details.
\r
269 There is also a command to clear out one or more lines in a filter. They are ...
\r
276 There is clear/xxxx command for each type of filter.
\r
279 and you can check that your filters have worked by the command ...
\r
286 For now we are going to use spots for the examples, but you can apply the same
\r
287 principles to all types of filter.
\r
289 <sect1>Types of filter
\r
292 There are two main types of filter, <em>accept</em> or <em>reject</em>. You
\r
293 can use either to achieve the result you want dependent on your own preference
\r
294 and which is more simple to do. It is pointless writing 8 lines of reject
\r
295 filters when 1 accept filter would do the same thing! Each filter has 10
\r
296 lines (of any length) which are tried in order. If a line matches then the
\r
297 action you have specified is taken (ie reject means ignore it and accept
\r
301 If you specify reject filters, then any lines that arrive that match the filter
\r
302 will be dumped but all else will be accepted. If you use an accept filter,
\r
303 then ONLY the lines in the filter will be accepted and all else will be dumped.
\r
304 For example if you have a single line <em>accept</em> filter ...
\r
307 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
\r
310 then you will <em>ONLY</em> get VHF spots <em>from</em> or <em>to</em> CQ zones
\r
314 If you set a reject filter like this ...
\r
317 reject/spots on hf/cw
\r
320 Then you will get everything <em>EXCEPT</em> HF CW spots. You could make this
\r
321 single filter even more flexible. For example, if you are interested in IOTA
\r
322 and will work it even on CW even though normally you are not interested in
\r
323 CW, then you could say ...
\r
326 reject/spots on hf/cw and not info iota
\r
329 But in that case you might only be interested in iota and say:-
\r
332 accept/spots not on hf/cw or info iota
\r
335 which achieves exactly the same thing. You should choose one or the other
\r
336 until you are comfortable with the way it works. You can mix them if you
\r
337 wish (actually you can have an accept AND a reject on the same line) but
\r
338 don't attempt this until you are sure you know what you are doing!
\r
341 You can arrange your filter lines into logical units, either for your own
\r
342 understanding or simply convenience. Here is an example ...
\r
345 reject/spots 1 on hf/cw
\r
346 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
\r
349 What this does is to ignore all HF CW spots and also rejects any spots on VHF
\r
350 which don't either originate or spot someone in Europe.
\r
353 This is an example where you would use a line number (1 and 2 in this case), if
\r
354 you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
\r
355 This make it easier to see just what filters you have set. It also makes it
\r
356 more simple to remove individual filters, during a contest for example.
\r
359 You will notice in the above example that the second line has brackets. Look
\r
360 at the line logically. You can see there are 2 separate sections to it. We
\r
361 are saying reject spots that are VHF or above <em>APART</em> from those in
\r
362 zones 14, 15 and 16 (either spotted there or originated there). If you did
\r
363 not have the brackets to separate the 2 sections, then Spider would read it
\r
364 logically from the front and see a different expression entirely ...
\r
367 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
\r
370 The simple way to remember this is, if you use OR - use brackets. Whilst we are
\r
371 here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
\r
373 As mentioned earlier, setting several filters can be more flexible than
\r
374 simply setting one complex one. Doing it in this way means that if you want
\r
375 to alter your filter you can just redefine or remove one or more lines of it or
\r
376 one line. For example ...
\r
379 reject/spots 1 on hf/ssb
\r
382 would redefine our earlier example, or
\r
388 To remove all the filter lines in the spot filter ...
\r
394 <sect1>Filter options
\r
397 You can filter in several different ways. The options are listed in the
\r
398 various helpfiles for accept, reject and filter.
\r
400 <sect1>Default filters
\r
403 Sometimes all that is needed is a general rule for node connects. This can
\r
404 be done with a node_default filter. This rule will always be followed, even
\r
405 if the link is isolated, unless another filter is set specifically. Default
\r
406 rules can be set for nodes and users. They can be set for spots, announces,
\r
407 WWV and WCY. They can also be used for hops. An example might look like
\r
411 accept/spot node_default by_zone 14,15,16,20,33
\r
412 set/hops node_default spot 50
\r
415 This filter is for spots only, you could set others for announce, WWV and WCY.
\r
416 This filter would work for ALL nodes unless a specific filter is written to
\r
417 override it for a particular node. You can also set a user_default should
\r
418 you require. It is important to note that default filters should be
\r
419 considered to be "connected". By this I mean that should you override the
\r
420 default filter for spots, you need to add a rule for the hops for spots also.
\r
422 <sect1>Advanced filtering
\r
425 Once you are happy with the results you get, you may like to experiment.
\r
428 The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
\r
429 can be written with a mixed filter, for example ...
\r
433 acc/spot on 0/30000
\r
434 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
\r
437 Note that the first filter has not been specified with a number. This will
\r
438 automatically be assumed to be number 1. In this case, we have said <em>reject all
\r
439 HF spots in the CW section of the bands but accept all others at HF. Also
\r
440 accept anything in VHF and above spotted in or by operators in the zones
\r
441 14, 15 and 16</em>. Each filter slot actually has a 'reject' slot and
\r
442 an 'accept' slot. The reject slot is executed BEFORE the accept slot.
\r
445 It was mentioned earlier that after a reject test that doesn't match, the default
\r
446 for following tests is 'accept', the reverse is true for 'accept'. In the example
\r
447 what happens is that the reject is executed first, any non hf/cw spot is passed
\r
448 to the accept line, which lets through everything else on HF. The next filter line
\r
449 lets through just VHF/UHF spots from EU.
\r
451 <sect1>Basic hop control
\r
454 In /spider/data you will find a file called hop_table.pl. This is the file
\r
455 that controls your hop count settings. It has a set of default hops on the
\r
456 various PC frames and also a set for each node you want to alter the hops for.
\r
457 You may be happy with the default settings of course, but this powerful tool
\r
458 can help to protect and improve the network. The file will look something
\r
463 # hop table construction
\r
468 # default hopcount to use
\r
471 # some variable hop counts based on message type
\r
482 # the per node hop control thingy
\r
487 GB7ADX => { 11 => 8,
\r
495 GB7UDX => { 11 => 8,
\r
514 Each set of hops is contained within a pair of curly braces and contains a
\r
515 series of PC frame types. PC11 for example is a DX spot. The figures here
\r
516 are not exhaustive but should give you a good idea of how the file works.
\r
519 SHould any of the nodecalls include an ssid, it is important to wrap the
\r
520 whole call in single quotes, like this ...
\r
533 If you do not do this, you will get errors and the file will not work as
\r
537 You can alter this file at any time, including whilst the cluster is running.
\r
538 If you alter the file during runtime, the command <em>load/hops</em> will
\r
539 bring your changes into effect.
\r
541 <sect1>Hop Control on Specific Nodes
\r
543 <p>You can set a callsign specific hop count for any of the standard filter
\r
547 set/hops gb7djk spot 4
\r
548 set/hops node_default route 10
\r
549 set/hops gb7baa wcy 5
\r
552 all work on their specific area of the protocol.
\r
555 The <em>set/hops</em> command overrides any hops that you have set otherwise.
\r
558 You can show what hops have been set using the <em>show/hops</em> command.
\r
560 <sect1>Isolating networks
\r
563 It is possible to isolate networks from each other on a "gateway" node using the
\r
564 <em>set/isolate <node_call></em> command.
\r
567 The effect of this is to partition an isolated network completely from another
\r
568 node connected to your node. Your node will appear on and otherwise behave
\r
569 normally on every network to which you are connected, but data from an isolated
\r
570 network will not cross onto any other network or vice versa. However all the
\r
571 spot, announce and WWV traffic and personal messages will still be handled
\r
572 locally (because you are a real node on all connected networks), that is locally
\r
573 connected users will appear on all networks and will be able to access and
\r
574 receive information from all networks transparently. All routed messages will
\r
575 be sent as normal, so if a user on one network knows that you are a gateway for
\r
576 another network, he can still still send a talk/announce etc message via your
\r
577 node and it will be routed across.
\r
580 If you use isolate on a node connection you will continue to receive
\r
581 all information from the isolated partner, however you will not pass
\r
582 any information back to the isolated node. There are times when you
\r
583 would like to forward only spots across a link (maybe during a contest
\r
584 for example). To do this, isolate the node in the normal way and use
\r
585 an <em>acc/spot >call< all</em> filter to override the isolate.
\r
587 <sect>Other filters
\r
589 <sect1>Filtering Mail
\r
592 In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
\r
593 this to badmsg.pl and edit the file. The original looks something like this ....
\r
597 # the list of regexes for messages that we won't store having
\r
598 # received them (bear in mind that we must receive them fully before
\r
602 # The format of each line is as follows
\r
604 # type source pattern
\r
605 # P/B/F T/F/O/S regex
\r
607 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
\r
608 # source: T - to field, F - from field, O - origin, S - subject
\r
609 # pattern: a perl regex on the field requested
\r
611 # Currently only type B and P msgs are affected by this code.
\r
613 # The list is read from the top down, the first pattern that matches
\r
614 # causes the action to be taken.
\r
616 # The pattern can be undef or 0 in which case it will always be selected
\r
617 # for the action specified
\r
625 'B', 'T', 'WANTED',
\r
626 'B', 'S', 'WANTED',
\r
635 I think this is fairly self explanatory. It is simply a list of subject
\r
636 headers that we do not want to pass on to either the users of the cluster or
\r
637 the other cluster nodes that we are linked to. This is usually because of
\r
638 rules and regulations pertaining to items for sale etc in a particular country.
\r
641 <sect1>Filtering words from text fields in Announce, Talk and DX spots
\r
644 From version 1.48 onwards the interface to this has changed. You can now
\r
645 use the commands <em>set/badword</em> to add words that you are not prepared
\r
646 to see on the cluster, <em>unset/badword</em> to allow that word again and
\r
647 <em>show/badword</em> to list the words that you have set.
\r
650 If you have a previous <em>/spider/data/badwords</em>, the first time you start
\r
651 the node, it will read and convert this file to the new commands. The old style
\r
652 file will then be removed.
\r
654 <sect1>Stopping (possibly bad) DX Spots from Nodes or Spotters
\r
657 There are a number of commands that control whether a spot progresses
\r
658 any further by regarding it as "bad" in some way.
\r
661 A DX Spot has a number of fields which can be checked to see whether they
\r
662 contain "bad" values, they are: the DX callsign itself, the Spotter and
\r
663 the Originating Node.
\r
666 There are a set of commands which allow the sysop to control whether a
\r
675 These work in the same as the <em>set/badword</em> command, you can add
\r
676 any words or callsigns or whatever to the appropriate database. For
\r
677 example, to stop a spot from a particular node you do:
\r
680 set/badnode gb7djk gb7dxc
\r
686 set/badspotter b0mb p1rat nocall
\r
692 set/baddx video wsjt
\r
695 You can remove a word using the appropriate unset command
\r
696 (<em>unset/baddx, unset/badspotter, unset/badnode</em>) or list them
\r
697 using one of <em>show/baddx, show/badspotter</em> and
\r
698 <em>show/badnode</em>.
\r
703 DXSpider deals seamlessly with standard AK1A type mail. It supports both
\r
704 personal and bulletin mail and the sysop has additional commands to ensure
\r
705 that mail gets to where it is meant. DXSpider will send mail almost
\r
706 immediately, assuming that the target is on line. However, only one
\r
707 mail message is dealt with at any one time. If a mail message is already
\r
708 being sent or recieved, then the new message will be queued until it has
\r
711 The cluster mail is automatically deleted after 30 days unless the sysop
\r
712 sets the "keep" flag using the <em>msg</em> command.
\r
714 <sect1>Personal mail
\r
717 Personal mail is sent using the <em>sp</em> command. This is actually the
\r
718 default method of sending mail and so a simple <em>s</em> for send will do.
\r
719 A full list of the send commands and options is in the <em>command set</em>
\r
720 section, so I will not duplicate them here.
\r
722 <sect1>Bulletin mail
\r
725 Bulletin mail is sent by using the <em>sb</em> command. This is one of the
\r
726 most common mistakes users make when sending mail. They send a bulletin
\r
727 mail with <em>s</em> or <em>sp</em> instead of <em>sb</em> and of course
\r
728 the message never leaves the cluster. This can be rectified by the sysop
\r
729 by using the <em>msg</em> command.
\r
731 <P>Bulletin addresses can be set using the Forward.pl file.
\r
736 DXSpider receives all and any mail sent to it without any alterations needed
\r
737 in files. Because personal and bulletin mail are treated differently, there
\r
738 is no need for a list of accepted bulletin addresses. It is necessary, however,
\r
739 to tell the program which links accept which bulletins. For example, it is
\r
740 pointless sending bulletins addresses to "UK" to any links other than UK
\r
741 ones. The file that does this is called forward.pl and lives in /spider/msg.
\r
742 At default, like other spider files it is named forward.pl.issue. Rename it
\r
743 to forward.pl and edit the file to match your requirements.
\r
744 The format is below ...
\r
748 # this is an example message forwarding file for the system
\r
750 # The format of each line is as follows
\r
752 # type to/from/at pattern action destinations
\r
753 # P/B/F T/F/A regex I/F [ call [, call ...] ]
\r
755 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
\r
756 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
\r
757 # pattern: a perl regex on the field requested
\r
758 # action: I - ignore, F - forward
\r
759 # destinations: a reference to an array containing node callsigns
\r
761 # if it is non-private and isn't in here then it won't get forwarded
\r
763 # Currently only type B msgs are affected by this code.
\r
765 # The list is read from the top down, the first pattern that matches
\r
766 # causes the action to be taken.
\r
768 # The pattern can be undef or 0 in which case it will always be selected
\r
769 # for the action specified
\r
771 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
\r
772 # pattern) then it will always be forwarded to every node that doesn't have
\r
773 # it (I strongly recommend you don't use this unless you REALLY mean it, if
\r
774 # you allow a new link with this on EVERY bull will be forwarded immediately
\r
775 # on first connection)
\r
781 'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
\r
782 'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
783 'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
\r
784 'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
785 'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
786 'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
787 'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
788 'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
789 'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
790 'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
\r
791 'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
795 Simply insert a bulletin address and state in the brackets where you wish
\r
796 that mail to go. For example, you can see here that mail sent to "UK" will
\r
797 only be sent to the UK links and not to PA4AB-14.
\r
800 To force the cluster to reread the file use load/forward
\r
803 NB: If a user tries to send mail to a bulletin address that does not exist
\r
804 in this file, they will get an error.
\r
806 <sect1>The msg command
\r
809 The <em>msg</em> command is a very powerful and flexible tool for the
\r
810 sysop. It allows the sysop to alter to and from fields and make other
\r
811 changes to manage the cluster mail.
\r
813 Here is a full list of the various options ...
\r
816 MSG TO <msgno> <call> - change TO callsign to <call>
\r
817 MSG FRom <msgno> <call> - change FROM callsign to <call>
\r
818 MSG PRrivate <msgno> - set private flag
\r
819 MSG NOPRrivate <msgno> - unset private flag
\r
820 MSG RR <msgno> - set RR flag
\r
821 MSG NORR <msgno> - unset RR flag
\r
822 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
\r
823 MSG NOKEep <msgno> - unset the keep flag
\r
824 MSG SUbject <msgno> <new> - change the subject to <new>
\r
825 MSG WAittime <msgno> - remove any waiting time for this message
\r
826 MSG NOREad <msgno> - mark message as unread
\r
827 MSG REad <msgno> - mark message as read
\r
828 MSG QUeue - queue any outstanding bulletins
\r
829 MSG QUeue 1 - queue any outstanding private messages
\r
832 These commands are simply typed from within the cluster as the sysop user.
\r
834 <sect1>Message status
\r
837 You can check on a message from within the cluster by using the command
\r
838 <em>stat/msg</em>. This will give you additional information on the
\r
839 message number including which nodes have received it, which node it
\r
840 was received from and when etc. Here is an example of the output of
\r
844 G0VGS de GB7MBC 28-Jan-2001 1308Z >
\r
847 Msg Time: 26-Jan-2001 1302Z
\r
851 Subject: AMSAT 2line KEPS 01025.AMSAT
\r
853 Got it Nodes: GB7BAA, GB7ADX
\r
857 G0VGS de GB7MBC 28-Jan-2001 1308Z >
\r
860 <sect1>Filtering mail
\r
863 This is described in the section on <em>Other filters</em> so I will not
\r
866 <sect1>Distribution lists
\r
869 Distribution lists are simply a list of users to send certain types of
\r
870 mail to. An example of this is mail you only wish to send to other
\r
871 sysops. In /spider/msg there is a directory called <em>distro</em>. You
\r
872 put any distibution lists in here. For example, here is a file called
\r
873 SYSOP.pl that caters for the UK sysops.
\r
876 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
\r
877 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
\r
878 GB7DXK GB7DXI GB7DXS)
\r
881 Any mail sent to "sysop" would only be sent to the callsigns in this list.
\r
883 <sect1>BBS interface
\r
886 Spider provides a simple BBS interface. No input is required from the sysop
\r
887 of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
\r
888 any required mail to the cluster. No mail can flow from Spider to the BBS,
\r
889 the interface is one-way.
\r
892 Please be careful not to flood the cluster network with unnecessary mail.
\r
893 Make sure you only send mail to the clusters that want it by using the
\r
894 Forward.pl file very carefully.
\r
899 From 1.48 onwards it will become increasingly possible to control DXSpider's
\r
900 operation with scripts of various kinds.
\r
903 The directory /spider/scripts is where it all happens and is used for several
\r
904 things. Firstly it contains a file called startup that can be used to call
\r
905 in any changes to the cluster from the default settings on startup. This
\r
906 script is executed immediately after all initialisation of the node is done
\r
907 but before any connections are possible. Examples of this include how many
\r
908 spots it is possible to get with the sh/dx command, whether you want
\r
909 registration/passwords to be permanently on etc. An example file is shown
\r
910 below and is included in the distribution as startup.issue.
\r
914 # startup script example
\r
916 # set maximum no of spots allowed to 100
\r
917 # set/var $Spot::maxspots = 100
\r
919 # Set registration on
\r
920 # set/var $main::reqreg = 1
\r
923 # set/var $main::passwdreq = 1
\r
928 As usual, any text behind a # is treated as a comment and not read. To use
\r
929 this file, simply rename it from startup.issue to startup. In our example
\r
930 above there are three options. The first option is the amount of spots that
\r
931 a user can request with the <em>sh/dx</em> command. Normally the default is
\r
932 to give 10 spots unless the user specifies more. Without this line enabled,
\r
933 the maximum a user can request is 100 spots. Depending on your link quality
\r
934 you may wish to enable more or less by specifying the number.
\r
937 The other 2 options are dealt with more fully in the security section.
\r
940 Secondly, it is used to store the login scripts for users and nodes. Currently
\r
941 this can only be done by the sysop but it is envisaged that eventually users will
\r
942 be able to set their own. An example is included in the distibution but here is
\r
958 The lines in between commands can simply insert a blank line or a character
\r
959 such as a + sign to make the output easier to read. Simply create this script
\r
960 with your favourite editor and save it with the callsign of the user as the
\r
961 filename. Filenames should always be in lower case.
\r
964 Commands can be inserted in the same way for nodes. A node may wish a series
\r
965 of commands to be issued on login, such as a merge command for example.
\r
968 Thirdly, there are 2 default scripts for users and nodes who do not have a
\r
969 specifically defined script. These are <em>user_default</em> and
\r
970 <em>node_default</em>
\r
975 Spider allows the creation of local or remote databases. It supports
\r
976 chained databases, allowing several different databases to be scanned
\r
977 with one simple command. Importing of databases is limited at present
\r
978 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
\r
979 database but will expand with time.
\r
981 <sect1>Creating databases
\r
984 Creating a database could not be more simple. All the commands are
\r
985 sent from the cluster prompt as the <em>sysop</em> user.
\r
987 To create a database you use the command <em>dbcreate</em>. It can
\r
988 be used in 3 different ways like so ..
\r
994 To simply create a database locally, you just tell the command the
\r
995 name of the database. This does not create the actual database, it
\r
996 simply defines it to say that it exists.
\r
999 dbcreate <name> chain <name> [<name>...]
\r
1002 This creates a chained database entry. The first database will be
\r
1003 scanned, then the second, the third etc...
\r
1006 dbcreate <name> remote <name>
\r
1009 This creates a remote entry. the first name field is the database
\r
1010 name at the remote node, then the remote switch, then the actual
\r
1011 node_call of the remote node, for example...
\r
1014 dbcreate buckmaster remote gb7dxc
\r
1017 Remote databases cannot be chained, however, the last database in a
\r
1018 chain can be a remote database.
\r
1020 <sect1>Importing databases
\r
1023 The only databases that Spider can currently import are the standard
\r
1024 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
\r
1025 This will be added to with time.
\r
1027 To import such a database, first put the file somewhere useful like /tmp
\r
1028 and then issue the following command ...
\r
1031 dbimport oblast /tmp/OBLAST.FUL
\r
1034 This will update the existing local oblast database or create it if
\r
1035 it does not exist.
\r
1037 <sect1>Checking available databases
\r
1040 Once a database is created, you will want to check that it has been
\r
1041 added. To do this use the <em>dbavail</em> command. This will
\r
1042 output the available databases. For example ...
\r
1046 DB Name Location Chain
\r
1050 G0VGS de GB7MBC 3-Feb-2001 1925Z >
\r
1053 <sect1>Looking up databases
\r
1056 To look for information in a defined database, simply use the <em>dbshow</em>
\r
1057 command, for example ...
\r
1060 dbshow buckmaster G0YLM
\r
1063 will show the information for the callsign G0YLM from the buckmaster
\r
1064 database if it exists. To make things more standard for the users
\r
1065 you can add an entry in the Aliases file so that it looks like a standard
\r
1066 <em>show</em> command like this ...
\r
1069 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
\r
1072 Now you can simply use show/buckmaster or an abreviation.
\r
1074 <sect1>Removing databases
\r
1077 To delete an existing database you use the <em>dbremove</em> command.
\r
1084 would remove the oblast database and its associated datafile from the
\r
1085 system. There are no warnings or recovery possible from this command.
\r
1086 If you remove a database it ceases to exist and would have to be created
\r
1087 from scratch if you still required it.
\r
1089 <sect>Information, files and useful programs
\r
1094 One of the more important things a cluster sysop needs to do is to get
\r
1095 information to his users. The simplest way to do this is to have a banner
\r
1096 that is sent to the user on login. This is know as a "message of the day"
\r
1097 or "motd". To set this up, simply create a file in /spider/data called motd
\r
1098 and edit it to say whatever you want. It is purely a text file and will be
\r
1099 sent automatically to anyone logging in to the cluster.
\r
1104 This message of the day file lives in the same directory as the standard
\r
1105 motd file but is only sent to non-registered users. Once registered they
\r
1106 will receive the same message as any other user.
\r
1108 <sect1>Downtime message
\r
1111 If for any reason the cluster is down, maybe for upgrade or maintenance but
\r
1112 the machine is still running, a message can be sent to the user advising them
\r
1113 of the fact. This message lives in the /spider/data directory and is called
\r
1114 "offline". Simply create the file and edit it to say whatever you wish.
\r
1115 This file will be sent to a user attempting to log into the cluster when
\r
1116 DXSpider is not actually running.
\r
1118 <sect1>Other text messages
\r
1121 You can set other text messages to be read by the user if they input the file
\r
1122 name. This could be for news items or maybe information for new users.
\r
1123 To set this up, make a directory under /spider called <em>packclus</em>.
\r
1124 Under this directory you can create files called <em>news</em> or <em>newuser</em>
\r
1125 for example. In fact you can create files with any names you like. These can
\r
1126 be listed by the user with the command ....
\r
1132 They can be read by the user by typing the command ....
\r
1138 If the file they want to read is called <em>news</em>. You could also set
\r
1139 an alias for this in the Alias file to allow them just to type <em>news</em>
\r
1142 You can also store other information in this directory, either directly or
\r
1143 nested under directories. One use for this would be to store DX bulletins
\r
1144 such as the OPDX bulletins. These can be listed and read by the user.
\r
1145 To keep things tidy, make a directory under /spider/packclus called
\r
1146 <em>bulletin</em>. Now copy any OPDX or similar bulletins into it. These
\r
1147 can be listed by the user in the same way as above using the <em>show/files</em>
\r
1148 command with an extension for the bulletin directory you have just created,
\r
1152 show/files bulletin
\r
1156 An example would look like this ....
\r
1160 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
\r
1163 You can see that in the files area (basically the packclus directory) there is a
\r
1164 file called <em>news</em> and a directory called <em>bulletin</em>. You can
\r
1165 also see that dates they were created. In the case of the file <em>news</em>,
\r
1166 you can also see the time it was last modified, a good clue as to whether the
\r
1167 file has been updated since you last read it. To read the file called
\r
1168 <em>news</em> you would simply issue the command ....
\r
1174 To look what is in the bulletin directory you issue the command ....
\r
1177 show/files bulletin
\r
1178 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
\r
1179 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
\r
1180 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
\r
1181 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
\r
1182 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
\r
1183 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
\r
1184 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
\r
1185 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
\r
1186 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
\r
1187 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
\r
1188 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
\r
1189 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
\r
1190 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
\r
1191 Press Enter to continue, A to abort (16 lines) >
\r
1194 You can now read any file in this directory using the type command, like this ....
\r
1197 type bulletin/opdx391
\r
1198 Ohio/Penn DX Bulletin No. 391
\r
1199 The Ohio/Penn Dx PacketCluster
\r
1200 DX Bulletin No. 391
\r
1203 Editor Tedd Mirgliotta, KB8NW
\r
1204 Provided by BARF-80 BBS Cleveland, Ohio
\r
1205 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
\r
1206 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
\r
1207 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
\r
1208 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
\r
1209 Press Enter to continue, A to abort (508 lines) >
\r
1212 The page length will of course depend on what you have it set to!
\r
1214 <sect1>The Aliases file
\r
1217 You will find a file in /spider/cmd/ called Aliases. This is the file that
\r
1218 controls what a user gets when issuing a command. It is also possible to
\r
1219 create your own aliases for databases and files you create locally.
\r
1222 You should not alter the original file in /spider/cmd/ but create a new file
\r
1223 with the same name in /spider/local_cmd. This means that any new Aliases files
\r
1224 that is downloaded will not overwrite your self created Aliases and also that
\r
1225 you do not override any new Aliases with your copy in /spider/local_cmd/. You
\r
1226 must remember that any files you store in /spider/local/ or /spider/local_cmd
\r
1227 override the originals if the same lines are used in both files.
\r
1230 The best way of dealing with all this then is to only put your own locally
\r
1231 created Aliases in the copy in /spider/local_cmd. The example below is
\r
1232 currently in use at GB7MBC.
\r
1237 # Local Aliases File
\r
1244 '^news$', 'type news', 'type',
\r
1247 '^sh\w*/buck$', 'show/qrz', 'show',
\r
1248 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
\r
1249 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
\r
1250 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
\r
1251 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
\r
1258 Each alphabetical section should be preceded by the initial letter and the section
\r
1259 should be wrapped in square brackets as you can see. The syntax is straightforward.
\r
1260 The first section on each line is the new command that will be allowed once the
\r
1261 alias is included. The second section is the command it is replacing and the last
\r
1262 section is the actual command that is being used.
\r
1265 The eagle-eyed amongst you will have noticed that in the first section, the new
\r
1266 alias command has a '^' at the start and a '$' at the end. Basically these force
\r
1267 a perfect match on the alias. The '^' says match the beginning exactly and the
\r
1268 '$' says match the end exactly. This prevents unwanted and unintentional matches
\r
1269 with similar commands.
\r
1272 I have 3 different types of alias in this file. At the top is an alias for 'news'.
\r
1273 This is a file I have created in the /spider/packclus/ directory where I can inform
\r
1274 users of new developments or points of interest. In it's initial form a user would
\r
1275 have to use the command <em>type news</em>. The alias allows them to simply type
\r
1276 <em>news</em> to get the info. Second is an alias for the <em>show/qrz</em>
\r
1277 command so that those users used to the original <em>show/buck</em> command in
\r
1278 AK1A will not get an error, and the rest of the lines are for locally created
\r
1279 databases so that a user can type <em>show/hftest</em> instead of having to use
\r
1280 the command <em>dbshow hftest</em> which is not as intuitive.
\r
1283 This file is just an example and you should edit it to your own requirements.
\r
1284 Once created, simply issue the command <em>load/alias</em> at the cluster
\r
1285 prompt as the sysop user and the aliases should be available.
\r
1291 In later versions of Spider a simple console program is provided for the sysop.
\r
1292 This has a type ahead buffer with line editing facilities and colour for spots,
\r
1293 announces etc. To use this program, simply use console.pl instead of client.
\r
1296 To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
\r
1297 file with your favourite editor.
\r
1299 <sect1>Updating kepler data
\r
1302 Spider has a powerful and flexible show/satellite command. In order for
\r
1303 this to be accurate, the kepler data has to be updated regularly. In
\r
1304 general, this data is available as an email or via cluster mail.
\r
1305 Updating it is simple. First you need to export the mail message as a
\r
1306 file. You do this with the <em>export</em> command from the cluster prompt
\r
1307 as the sysop. For example ...
\r
1310 export 5467 /spider/perl/keps.in
\r
1314 would export message number 5467 as a file called keps.in in the
\r
1315 /spider/perl directory.
\r
1318 Now login to a VT as sysop and cd /spider/perl. There is a command in
\r
1319 the perl directory called <em>convkeps.pl</em>. All we need to do now is
\r
1320 convert the file like so ...
\r
1323 ./convkeps.pl keps.in
\r
1327 Now go back to the cluster and issue the command ...
\r
1334 That is it! the kepler data has been updated.
\r
1336 <sect1>The QRZ callbook
\r
1339 The command <em>sh/qrz</em> will only work once you have followed a few
\r
1340 simple steps. First you need to get a user ID and password from qrz.com.
\r
1341 Simply go to the site and create one. Secondly you need to copy the file
\r
1342 /spider/perl/Internet.pm to /spider/local and alter it to match your user
\r
1343 ID and password. You also at this point need to set $allow=1 to complete
\r
1344 the setup. Many thanks to Fred Lloyd, the proprieter of
\r
1345 <htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
\r
1347 <sect1>Connecting logging programs
\r
1350 There appear to be very few logging programs out there that support telnet
\r
1351 especially the popular ones like LogEQF, Turbolog etc. This can make it
\r
1352 difficult to connect to your own cluster!
\r
1353 The way to do it is to make the logging program think it has a TNC attached
\r
1354 to a com port on the logging PC and 'push' a linux login out to it.
\r
1355 This is achieved very simply by the use of <em>agetty</em>.
\r
1358 All that is required is to add a line in /etc/inittab to have the client
\r
1359 ready for a connection on the com port of your choice. Remember that in
\r
1360 Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.
\r
1363 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
\r
1367 Add this after the standard runlevel lines in /etc/inittab. The above
\r
1368 line works on ttyS1 (com2). Now as root, issue the command <em>telinit q</em>
\r
1369 and it should be ready for connection. All that is required is a 3 wire
\r
1370 serial lead (tx, rx and signal ground). Tell you logging program to use
\r
1371 8n1 at 9600 baud and you should see a Linux login prompt. Login as normal
\r
1372 and then telnet from there to the cluster.
\r
1374 <sect>Java Web applet
\r
1377 In the spider tree will be a directory <em>spider-web</em>. This is a
\r
1378 neat little java web applet that can be run from a website. The applet
\r
1379 must run on the same machine as the cluster. The included README file is
\r
1383 I should comment here that the applet is precompiled, that is, ready to go.
\r
1384 It was compiled using JDK1.3.1. If your version is earlier than this then it
\r
1385 may not work. Should that be the case you need to recompile or update your
\r
1386 JDK. To recompile do the following ...
\r
1389 cd /spider/spider-web
\r
1391 /usr/bin/javac spiderclient.java
\r
1395 I have used /usr/bin/javac as an example, your path to javac may be different.
\r
1400 Completely based on a clx web client written in Java by dl6dbh
\r
1401 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
\r
1403 The webserver has to run on the same machine as your DxSpider software!
\r
1405 It is assumed that you have Java installed. You need JDK1.3.1 at least.
\r
1407 Installation instructions (Performed as root):
\r
1409 Put all the files in the spider-web directory into a newly created directory
\r
1410 under the DocumentRoot of your websever for instance 'client'. In my case
\r
1411 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
\r
1412 path should be /usr/local/httpd/htdocs/client/ for example.
\r
1414 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
\r
1415 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
\r
1416 /usr/local/httpd/cgi-bin/ for example.
\r
1418 Change the permissions of the files to ensure they are correct, obviously you
\r
1419 will need to use the correct path the the files according to your system:
\r
1421 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
\r
1422 chmod -R 755 /home/httpd/html/client/
\r
1424 By default the spider.cgi script should pick up your hostname (As long as this
\r
1425 is set correctly). If it does not or your hostname differs from the name that
\r
1426 you attach to the public address that you are using, then edit spider.cgi :
\r
1428 # Uncomment and set the hostname manually here if the above fails.
\r
1429 # $HOSTNAME = "gb7mbc.spoo.org" ;
\r
1432 'HOSTNAME' is the hostname of your cluster.
\r
1434 'PORT' is the portnumber that you use to connect to your DxSpider via
\r
1435 telnet (see Listeners.pm)
\r
1437 NOTE: If you can start the console but cannot connect to the cluster from it,
\r
1438 then it is possible that the machine you are on cannot resolve the hostname of
\r
1439 your cluster machine. If this is the case, you need to set your hostname
\r
1440 manually as above.
\r
1442 You also need to set the $NODECALL variable. This prints the name of your
\r
1443 choosing (probably your cluster callsign) on the html page.
\r
1445 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
\r
1448 <sect>Web based statistics
\r
1451 From version 1.50, you can use the freeware software MRTG to produce
\r
1452 really nice graphical statistics on your web site. For an example
\r
1453 try <htmlurl url="http://www.gb7mbc.net/mrtg/stats.html" name="http://www.gb7mbc.net/mrtg/stats.html">.
\r
1456 The following should help you get it all working.
\r
1459 First you need to download the latest version of MRTG from <htmlurl url="http://people.ee.ethz.ch/~oetiker/webtools/mrtg/" name="http://people.ee.ethz.ch/~oetiker/webtools/mrtg/">.
\r
1460 You will also need the following files..
\r
1463 libpng-1.0.14.tar.gz
\r
1468 Login to your machine as the root user, put all the downloaded files
\r
1469 in /usr/local/src/ (or wherever you prefer) and untar and compile them.
\r
1470 All the information to compile and install these sources come with them.
\r
1471 After compilation and installation, you will find MRTG in /usr/local/mrtg-2.
\r
1474 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
\r
1475 /spider/html/mrtg/
\r
1478 You now need to make 2 symbolic links like below...
\r
1481 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
\r
1482 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
\r
1486 Now login to the cluster with your sysop callsign and run the command
\r
1489 <P>Now you are nearly there! Login as the sysop user and change to the
\r
1490 /spider/html/mrtg/ directory. Now run the command <em>indexmaker</em> as
\r
1494 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
\r
1497 Changing the callsign for your own cluster callsign of course!
\r
1500 And finally you need to login as the root user and create one last
\r
1501 symbolic link. Where this points will depend on where your html
\r
1502 documents are kept. For RedHat systems you use...
\r
1505 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
\r
1508 and for SuSE systems...
\r
1511 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
\r
1514 If you now point your browser to your website as below it should all
\r
1518 http://www.xxx.xxx/mrtg/stats.html
\r
1521 Of course, to get the stats to update, you need to add some information
\r
1522 in the spider crontab file as below...
\r
1525 # Update stats for mrtg on website
\r
1526 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
\r
1529 This will update the site every 5 minutes.
\r
1534 From version 1.49 DXSpider has some additional security features. These
\r
1535 are not by any means meant to be exhaustive, however they do afford some
\r
1536 security against piracy. These two new features can be used independently
\r
1537 of each other or in concert to tighten the security.
\r
1539 <sect1>Registration
\r
1542 The basic principle of registration is simple. If a user is not registered
\r
1543 by the sysop, then they have read-only access to the cluster. The only
\r
1544 thing they can actually send is a talk or a message to the sysop. In
\r
1545 order for them to be able to spot, send announces or talks etc the sysop
\r
1546 must register them with the <em>set/register</em> command, like this ...
\r
1549 set/register g0vgs
\r
1552 The user g0vgs can now fully use the cluster. In order to enable
\r
1553 registration, you can issue the command ...
\r
1556 set/var $main::reqreg = 1
\r
1559 Any users that are not registered will now see the motd_nor file rather
\r
1560 than the motd file as discussed in the Information, files and useful
\r
1564 Entering this line at the prompt will only last for the time the cluster
\r
1565 is running of course and would not be present on a restart. To make the
\r
1566 change permanent, add the above line to /spider/scripts/startup. To
\r
1567 read more on the startup file, see the section on Information, files
\r
1568 and useful programs.
\r
1571 To unregister a user use <em>unset/register</em> and to show the list
\r
1572 of registered users, use the command <em>show/register</em>.
\r
1577 At the moment, passwords only affect users who login to a DXSpider
\r
1578 cluster node via telnet. If a user requires a password, they can
\r
1579 either set it themselves or have the sysop enter it for them by using
\r
1580 the <em>set/password</em> command. Any users who already have passwords,
\r
1581 such as remote sysops, will be asked for their passwords automatically
\r
1582 by the cluster. Using passwords in this way means that the user has a
\r
1583 choice on whether to have a password or not. To force the use of
\r
1584 passwords at login, issue the command ...
\r
1587 set/var $main::passwdreq = 1
\r
1590 at the cluster prompt. This can also be added to the /spider/scripts/startup
\r
1591 file as above to make the change permanent.
\r
1594 Of course, if you do this you will have to assign a password for each of
\r
1595 your users. If you were asking them to register, it is anticipated that
\r
1596 you would ask them to send you a message both to ask to be registered and
\r
1597 to give you the password they wish to use.
\r
1600 Should a user forget their password, it can be reset by the sysop by
\r
1601 first removing the existing password and then setting a new one like so ...
\r
1604 unset/password g0vgs
\r
1605 set/password g0vgs new_password
\r
1610 <sect1>CVS from a Linux platform
\r
1613 CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
\r
1614 at <htmlurl url="http://www.sourceforge.net" name="Sourceforge">. This means
\r
1615 that it is possible to update your DXSpider installation to the latest
\r
1616 sources by using a few simple commands. A graphical interface to CVS for
\r
1617 Windows is explained in the next section.
\r
1620 Please be aware that if you update your system using CVS, it is possible that
\r
1621 you could be running code that is very beta and not fully tested. There is
\r
1622 a possibility that it could be unstable.
\r
1625 I am of course assuming that you have a machine with both DXSpider and
\r
1626 Internet access running.
\r
1629 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
\r
1630 ENTIRE SPIDER TREE!!
\r
1633 Assuming you are connected to the Internet, you need to login to the
\r
1634 CVS repository and then update your Spider source. There are several
\r
1635 steps which are listed below ...
\r
1638 First login as the user <em>sysop</em>. Next you need to connect to the CVS
\r
1639 repository. You do this with the command below ...
\r
1642 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
\r
1645 You will get a password prompt. Simply hit return here and your machine should
\r
1646 return to a normal linux prompt.
\r
1649 What happens next depends on whether you have an existing installation that
\r
1650 you want to update with the latest and greatest or whether you just want
\r
1651 to see what is there and/or run it on a new machine for testing.
\r
1653 If you are installing Spider from CVS then change directory to /home/sysop
\r
1655 If you are wanting to update Spider then cd to /tmp
\r
1658 The next step will create a brand new 'spider' directory in your current
\r
1662 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
\r
1665 This command is all on one line.
\r
1668 Hopefully your screen should show you downloading files. The -z3 simply compresses
\r
1669 the download to improve speed.
\r
1670 When this has finished, you will have exactly the same as if you had untarred a full
\r
1671 tarball PLUS some extra directories and files that CVS needs to do the magic that
\r
1675 Now if you are doing a new installation, that's it. Carry on as if you have
\r
1676 just downloaded and untarred the lastest tarball.
\r
1679 If you want to upgrade your current installation then do this ...
\r
1682 tar cvfz /tmp/s.tgz spider
\r
1684 tar xvfzp /tmp/s.tgz
\r
1687 This is assuming you downloaded to the /tmp directory of course.
\r
1690 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
\r
1691 correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
\r
1693 Remember to recompile the C client (cd /spider/src; make)
\r
1696 At this point the files have been upgraded. You can (usually) restart the cluster
\r
1697 in your own time. However, if you attempt to use any new commands or features
\r
1698 expect it to be fatal! At least your cluster will have been restarted then so it
\r
1699 will be too late to worry about it!
\r
1702 Now the magic part! From now on when you want to update, simply connect to the
\r
1703 Internet and then, as the user <em>sysop</em> ...
\r
1710 and your files will be updated. As above, remember to recompile the "C" client
\r
1711 if it has been updated (CVS will tell you) and restart if any of the perl scripts
\r
1712 have been altered or added, again, CVS will tell you.
\r
1715 You will find any changes documented in the /spider/Changes file.
\r
1717 <sect1>CVS from a Windows platform
\r
1720 After the initial setup, an update to your DXSpider software is no more than a couple
\r
1721 of clicks away. This section is intended to explain and illustrate the use of the
\r
1722 WinCVS application to update your DXSpider software. The current stable version of
\r
1723 WinCVS is Ver. 1.2. You can get this software at:
\r
1725 <htmlurl url="http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip" name="http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip">
\r
1727 Pick your download mirror and then install WinCVS after the download is complete.
\r
1729 In this next section I have included a series of links to .jpg files to take advantage of the
\r
1730 picture and 1000 words equivalency. The .jpg files are in the C:\spider\html directory. If
\r
1731 someone using a Linux system is reading this section from boredom, the files are in
\r
1732 /home/sysop/spider/html. One aside, a Linux user can also get a copy of gcvs and do your updates
\r
1733 graphically as opposed to from the command line. The following descriptions are almost identical
\r
1734 between WinCvs and gcvs. The following screen shots have duplicate links, depending upon whether
\r
1735 you are viewing this information under the Windows or Linux operating system.
\r
1737 When WinCVS is installed, running, and you are connected to the internet, the initial screen looks like:
\r
1739 <htmlurl url="initial.jpg" name="initial.jpg">
\r
1741 If you want, you can also look at these .jpg files with another viewer that might provide some
\r
1742 better clarity to the image. On the left is the directory tree for your hard disk. Notice that
\r
1743 the spider directory has a gray highlight.
\r
1745 To start configuring WinCVS, click on Admin at the top of the screen and then Preferences. This
\r
1748 <htmlurl url="pref-gen.jpg" name="pref-gen.jpg">
\r
1750 In the top line for CVSROOT, enter:
\r
1752 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
\r
1757 "passwd" file on the cvs server
\r
1760 for Authentication on the General tab.
\r
1762 Next, move to the right to the Ports tab.
\r
1764 <htmlurl url="pref-ports.jpg" name="pref-ports.jpg">
\r
1766 In here, check the box on the second line down for the "pserver" port. Enter a port number of 2401.
\r
1768 Finally, go to the WinCvs tab all the way to the right.
\r
1770 <htmlurl url="pref-wincvs.jpg" name="pref-wincvs.jpg">
\r
1772 Enter Notepad as the viewer to open files. For the HOME folder, put "C:\spider" and click OK
\r
1773 because the configuration is now complete.
\r
1775 You are now ready to upgrade your copy of DXSpider. Click on the greyed Spider folder
\r
1776 shown in the directory tree on the left of the WinCVS display. Two things should happen. The Spider
\r
1777 folder will be selected and the greyed-out arrow located just below the word Query in the top line will
\r
1778 turn to solid green.
\r
1780 For anyone using gcvs under Linux, the green arrow is located on the extreme left of the display,
\r
1781 under the word File. A gcvs screen looks like:
\r
1783 <htmlurl url="gcvs.jpg" name="gcvs.jpg">
\r
1785 Click on the now green arrow to start the download process. An Update Settings box will be displayed
\r
1786 to which you can simply say OK.
\r
1788 <htmlurl url="update-OK.jpg" name="update-OK.jpg">
\r
1790 For future reference, the Update Settings box is the place where you can enter information to revert
\r
1791 to a prior version of DXSpider. Information on reverting to a Before Date is contained in the WinCVS
\r
1794 After a short period of time, a series of file names will scroll by in the lower pane of the WinCVS
\r
1795 window. Eventually you should see
\r
1797 *****CVS exited normally with code 0*****
\r
1800 appear in the lower pane. You're done. The updated files are in place ready for you to stop and then
\r
1801 restart your DXSpider. After the restart, you're running with the latest version of DXSpider.
\r
1803 <htmlurl url="completed.jpg" name="completed.jpg">
\r
1805 To paraphrase from the CVS section... Now the magic part! From now on when you want to update, simply
\r
1806 connect to the Internet and start WinCVS.
\r
1808 Click on the greyed-out Spider directory in the left screen
\r
1809 Click on the green down arrow
\r
1810 Click OK on the Update Settings dialog box
\r
1811 Restart your Spider software
\r
1814 <sect>The DXSpider command set
\r
1821 <bf>accept</bf> Set a filter to accept something
1825 Create a filter to accept something
1827 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1829 <sect1>accept/announce <call> [input] [0-9] <pattern> (8)
1833 <bf>accept/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version
1837 This version allows a sysop to set a filter for a callsign as well as the
1838 default for nodes and users eg:-
1842 accept/ann input node_default by G,M,2
1843 accept/ann user_default by G,M,2
1846 <sect1>accept/announce [0-9] <pattern> (0)
1850 <bf>accept/announce [0-9] <pattern></bf> Set an 'accept' filter line for announce
1854 Create an 'accept this announce' line for a filter.
1856 An accept filter line means that if the announce matches this filter it is
1857 passed onto the user. See HELP FILTERING for more info. Please read this
1858 to understand how filters work - it will save a lot of grief later on.
1860 You can use any of the following things in this line:-
1863 info <string> eg: iota or qsl
1864 by <prefixes> eg: G,M,2
1865 origin <prefixes>
1866 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1867 origin_itu <prefixes or numbers> or: G,GM,GW
1868 origin_zone <prefixes or numbers>
1869 origin_state <states> eg: VA,NH,RI,NH
1870 by_dxcc <prefixes or numbers>
1871 by_itu <prefixes or numbers>
1872 by_zone <prefixes or numbers>
1873 by_state <states>
1874 channel <prefixes>
1875 wx 1 filter WX announces
1876 dest <prefixes> eg: 6MUK,WDX (distros)
1883 acc/ann 2 by_zone 14,15,16
1884 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1894 acc/ann by_state va,nh,ri,nh
1897 You can use the tag 'all' to accept everything eg:
1903 but this probably for advanced users...
1904 <sect1>accept/route <call> [0-9] <pattern> (8)
1908 <bf>accept/route <call> [0-9] <pattern></bf> Set an 'accept' filter line for routing
1912 Create an 'accept this routing PC Protocol' line for a filter.
1914 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1915 it is passed thru that interface. See HELP FILTERING for more info. Please read this
1916 to understand how filters work - it will save a lot of grief later on.
1918 You can use any of the following things in this line:-
1921 call <prefixes> the callsign of the thingy
1922 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1923 call_itu <prefixes or numbers> or: G,GM,GW
1924 call_zone <prefixes or numbers>
1925 call_state <states> eg: VA,NH,RI,NH
1926 origin <prefixes> really the interface it came in on
1927 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1928 origin_itu <prefixes or numbers> or: G,GM,GW
1929 origin_zone <prefixes or numbers>
1930 origin_state <states> eg: VA,NH,RI,NH
1936 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
1937 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
1940 you can now use 'by' as a synonym for 'call' so:
1949 You can use the tag 'all' to accept everything eg:
1955 <sect1>accept/spots <call> [input] [0-9] <pattern> (8)
1959 <bf>accept/spots <call> [input] [0-9] <pattern></bf> Spot filter sysop version
1963 This version allows a sysop to set a filter for a callsign as well as the
1964 default for nodes and users eg:-
1967 accept/spot db0sue-7 1 by_zone 14,15,16
1968 accept/spot node_default all
1969 set/hops node_default 10
1973 accept/spot user_default by G,M,2
1976 <sect1>accept/spots [0-9] <pattern> (0)
1980 <bf>accept/spots [0-9] <pattern></bf> Set an 'accept' filter line for spots
1984 Create an 'accept this spot' line for a filter.
1986 An accept filter line means that if the spot matches this filter it is
1987 passed onto the user. See HELP FILTERING for more info. Please read this
1988 to understand how filters work - it will save a lot of grief later on.
1990 You can use any of the following things in this line:-
1993 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1994 on <range> same as 'freq'
1995 call <prefixes> eg: G,PA,HB9
1996 info <string> eg: iota or qsl
1998 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1999 call_itu <prefixes or numbers> or: G,GM,GW
2000 call_zone <prefixes or numbers>
2001 call_state <states> eg: VA,NH,RI,ME
2002 by_dxcc <prefixes or numbers>
2003 by_itu <prefixes or numbers>
2004 by_zone <prefixes or numbers>
2005 by_state <states> eg: VA,NH,RI,ME
2006 origin <prefixes>
2007 channel <prefixes>
2010 'call' means the callsign that has spotted 'by' whoever.
2012 For frequencies, you can use any of the band names defined in
2013 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2014 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2015 this is more efficient than saying simply: freq HF (but don't get
2016 too hung up about that)
2022 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2025 You can use the tag 'all' to accept everything, eg:
2034 acc/spots by_state VA,NH,RI,MA,ME
2037 but this probably for advanced users...
2038 <sect1>accept/wcy <call> [input] [0-9] <pattern> (8)
2042 <bf>accept/wcy <call> [input] [0-9] <pattern></bf> WCY filter sysop version
2046 This version allows a sysop to set a filter for a callsign as well as the
2047 default for nodes and users eg:-
2050 accept/wcy node_default all
2051 set/hops node_default 10
2054 <sect1>accept/wcy [0-9] <pattern> (0)
2058 <bf>accept/wcy [0-9] <pattern></bf> set an 'accept' WCY filter
2062 It is unlikely that you will want to do this, but if you do then you can
2063 filter on the following fields:-
2066 by <prefixes> eg: G,M,2
2067 origin <prefixes>
2068 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2069 origin_itu <prefixes or numbers> or: G,GM,GW
2070 origin_zone <prefixes or numbers>
2071 by_dxcc <prefixes or numbers>
2072 by_itu <prefixes or numbers>
2073 by_zone <prefixes or numbers>
2074 channel <prefixes>
2077 There are no examples because WCY Broadcasts only come from one place and
2078 you either want them or not (see UNSET/WCY if you don't want them).
2080 This command is really provided for future use.
2082 See HELP FILTER for information.
2083 <sect1>accept/wwv <call> [input] [0-9] <pattern> (8)
2087 <bf>accept/wwv <call> [input] [0-9] <pattern></bf> WWV filter sysop version
2091 This version allows a sysop to set a filter for a callsign as well as the
2092 default for nodes and users eg:-
2095 accept/wwv db0sue-7 1 by_zone 4
2096 accept/wwv node_default all
2097 set/hops node_default 10
2101 accept/wwv user_default by W,K
2104 <sect1>accept/wwv [0-9] <pattern> (0)
2108 <bf>accept/wwv [0-9] <pattern></bf> set an 'accept' WWV filter
2112 It is unlikely that you will want to do this, but if you do then you can
2113 filter on the following fields:-
2116 by <prefixes> eg: G,M,2
2117 origin <prefixes>
2118 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2119 origin_itu <prefixes or numbers> or: G,GM,GW
2120 origin_zone <prefixes or numbers>
2121 by_dxcc <prefixes or numbers>
2122 by_itu <prefixes or numbers>
2123 by_zone <prefixes or numbers>
2124 channel <prefixes>
2130 accept/wwv by_zone 4
2133 is probably the only useful thing to do (which will only show WWV broadcasts
2134 by stations in the US).
2136 See HELP FILTER for information.
2137 <sect1>announce <text> (0)
2141 <bf>announce <text></bf> Send an announcement to LOCAL users only
2145 <text> is the text of the announcement you wish to broadcast
2146 <sect1>announce full <text> (0)
2150 <bf>announce full <text></bf> Send an announcement cluster wide
2154 This will send your announcement cluster wide
2155 <sect1>announce sysop <text> (5)
2159 <bf>announce sysop <text></bf> Send an announcement to Sysops only
2163 <sect1>apropos <string> (0)
2167 <bf>apropos <string></bf> Search help database for <string>
2171 Search the help database for <string> (it isn't case sensitive), and print
2172 the names of all the commands that may be relevant.
2173 <sect1>blank [<string>] [<nn>] (0)
2177 <bf>blank [<string>] [<nn>]</bf> Print nn (default 1) blank lines (or strings)
2181 In its basic form this command prints one or more blank lines. However if
2182 you pass it a string it will replicate the string for the width of the
2183 screen (default 80) and then print that one or more times, so:
2189 prints two blank lines
2195 prints a row of - characters once.
2201 prints 'abcabcabcabcabcabc....'
2203 This is really only of any use in a script file and you can print a maximum
2209 <bf>bye</bf> Exit from the cluster
2213 This will disconnect you from the cluster
2214 <sect1>catchup <node call> all|[<msgno> ...] (5)
2218 <bf>catchup <node call> all|[<msgno> ...]</bf> Mark a message as sent
2222 <sect1>clear/announce <callsign> [input] [0-9|all] (8)
2226 <bf>clear/announce <callsign> [input] [0-9|all]</bf> Clear a announce filter line
2230 A sysop can clear an input or normal output filter for a user or the
2231 node_default or user_default.
2232 <sect1>clear/announce [1|all] (0)
2236 <bf>clear/announce [1|all]</bf> Clear a announce filter line
2240 This command allows you to clear (remove) a line in a annouce filter or to
2241 remove the whole filter.
2243 see CLEAR/SPOTS for a more detailed explanation.
2244 <sect1>clear/route <callsign> [input] [0-9|all] (8)
2248 <bf>clear/route <callsign> [input] [0-9|all]</bf> Clear a route filter line
2252 A sysop can clear an input or normal output filter for a user or the
2253 node_default or user_default.
2254 <sect1>clear/route [1|all] (0)
2258 <bf>clear/route [1|all]</bf> Clear a route filter line
2262 This command allows you to clear (remove) a line in a route filter or to
2263 remove the whole filter.
2265 see CLEAR/SPOTS for a more detailed explanation.
2266 <sect1>clear/spots <callsign> [input] [0-9|all] (8)
2270 <bf>clear/spots <callsign> [input] [0-9|all]</bf> Clear a spot filter line
2274 A sysop can clear an input or normal output filter for a user or the
2275 node_default or user_default.
2276 <sect1>clear/spots [0-9|all] (0)
2280 <bf>clear/spots [0-9|all]</bf> Clear a spot filter line
2284 This command allows you to clear (remove) a line in a spot filter or to
2285 remove the whole filter.
2287 If you have a filter:-
2291 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2300 you will be left with:-
2303 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2312 the filter will be completely removed.
2313 <sect1>clear/wcy <callsign> [input] [0-9|all] (8)
2317 <bf>clear/wcy <callsign> [input] [0-9|all]</bf> Clear a WCY filter line
2321 A sysop can clear an input or normal output filter for a user or the
2322 node_default or user_default.
2323 <sect1>clear/wcy [1|all] (0)
2327 <bf>clear/wcy [1|all]</bf> Clear a WCY filter line
2331 This command allows you to clear (remove) a line in a WCY filter or to
2332 remove the whole filter.
2334 see CLEAR/SPOTS for a more detailed explanation.
2335 <sect1>clear/wwv <callsign> [input] [0-9|all] (8)
2339 <bf>clear/wwv <callsign> [input] [0-9|all]</bf> Clear a WWV filter line
2343 A sysop can clear an input or normal output filter for a user or the
2344 node_default or user_default.
2345 <sect1>clear/wwv [1|all] (0)
2349 <bf>clear/wwv [1|all]</bf> Clear a WWV filter line
2353 This command allows you to clear (remove) a line in a WWV filter or to
2354 remove the whole filter.
2356 see CLEAR/SPOTS for a more detailed explanation.
2357 <sect1>connect <callsign> (5)
2361 <bf>connect <callsign></bf> Start a connection to another DX Cluster
2365 Start a connection process that will culminate in a new connection to the
2366 DX cluster <callsign>. This process creates a new 'client' process which will
2367 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
2368 necessary to traverse the network(s) to logon to the cluster <callsign>.
2373 <bf>dbavail</bf> Show a list of all the Databases in the system
2377 Title says it all really, this command lists all the databases defined
2378 in the system. It is also aliased to SHOW/COMMAND.
2379 <sect1>dbshow <dbname> <key> (0)
2383 <bf>dbshow <dbname> <key></bf> Display an entry, if it exists, in a database
2387 This is the generic user interface to the database to the database system.
2388 It is expected that the sysop will add an entry to the local Aliases file
2389 so that users can use the more familiar AK1A style of enquiry such as:
2395 but if he hasn't and the database really does exist (use DBAVAIL or
2396 SHOW/COMMAND to find out) you can do the same thing with:
2402 <sect1>directory (0)
2406 <bf>directory</bf> List messages
2410 <sect1>directory <from>-<to> (0)
2414 <bf>directory <from>-<to></bf> List messages <from> message <to> message
2418 List the messages in the messages directory.
2420 If there is a 'p' one space after the message number then it is a
2421 personal message. If there is a '-' between the message number and the
2422 'p' then this indicates that the message has been read.
2424 You can use shell escape characters such as '*' and '?' in the <call>
2427 You can combine some of the various directory commands together eg:-
2434 DIR SUBJECT IOTA 200-250
2437 You can abbreviate all the commands to one letter and use ak1a syntax:-
2444 <sect1>directory <nn> (0)
2448 <bf>directory <nn></bf> List last <nn> messages
2452 <sect1>directory all (0)
2456 <bf>directory all</bf> List all messages
2460 <sect1>directory from <call> (0)
2464 <bf>directory from <call></bf> List all messages from <call>
2468 <sect1>directory new (0)
2472 <bf>directory new</bf> List all new messages
2476 <sect1>directory own (0)
2480 <bf>directory own</bf> List your own messages
2484 <sect1>directory subject <string> (0)
2488 <bf>directory subject <string></bf> List all messages with <string> in subject
2492 <sect1>directory to <call> (0)
2496 <bf>directory to <call></bf> List all messages to <call>
2500 <sect1>directory- (5)
2508 Sysops can see all users' messages.
2509 <sect1>disconnect <call> [<call> ...] (8)
2513 <bf>disconnect <call> [<call> ...]</bf> Disconnect a user or cluster
2517 Disconnect any <call> connected locally
2518 <sect1>dx [by <call>] <freq> <call> <remarks> (0)
2522 <bf>dx [by <call>] <freq> <call> <remarks></bf> Send a DX spot
2526 This is how you send a DX Spot to other users. You can, in fact, now
2527 enter the <freq> and the <call> either way round.
2535 will all give the same result. You can add some remarks to the end
2536 of the command and they will be added to the spot.
2539 DX FR0G 144600 this is a test
2542 You can credit someone else by saying:-
2545 DX by G1TLH FR0G 144.600 he isn't on the cluster
2548 The <freq> is compared against the available bands set up in the
2549 cluster. See SHOW/BANDS for more information.
2550 <sect1>echo <line> (0)
2554 <bf>echo <line></bf> Echo the line to the output
2558 This command is useful in scripts and so forth for printing the
2559 line that you give to the command to the output. You can use this
2560 in user_default scripts and the SAVE command for titling and so forth
2562 The script will interpret certain standard "escape" sequences as follows:-
2565 \t - becomes a TAB character (0x09 in ascii)
2566 \a - becomes a BEEP character (0x07 in ascii)
2567 \n - prints a new line
2570 So the following example:-
2573 echo GB7DJK is a dxcluster
2579 GB7DJK is a dxcluster
2582 on the output. You don't need a \n on the end of the line you want to send.
2584 A more complex example:-
2587 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
2600 <sect1>filtering... (0)
2604 <bf>filtering...</bf> Filtering things in DXSpider
2608 There are a number of things you can filter in the DXSpider system. They
2609 all use the same general mechanism.
2611 In general terms you can create a 'reject' or an 'accept' filter which
2612 can have up to 10 lines in it. You do this using, for example:-
2619 where ..... are the specific commands for that type of filter. There
2620 are filters for spots, wwv, announce, wcy and (for sysops)
2621 connects. See each different accept or reject command reference for
2624 There is also a command to clear out one or more lines in a filter and
2625 one to show you what you have set. They are:-
2638 There is clear/xxxx command for each type of filter.
2640 For now we are going to use spots for the examples, but you can apply
2641 the principles to all types of filter.
2643 There are two main types of filter 'accept' or 'reject'; which you use
2644 depends entirely on how you look at the world and what is least
2645 writing to achieve what you want. Each filter has 10 lines (of any
2646 length) which are tried in order. If a line matches then the action
2647 you have specified is taken (ie reject means ignore it and accept
2650 The important thing to remember is that if you specify a 'reject'
2651 filter (all the lines in it say 'reject/spots' (for instance)) then if
2652 a spot comes in that doesn't match any of the lines then you will get
2653 it BUT if you specify an 'accept' filter then any spots that don't
2654 match are dumped. For example if I have a one line accept filter:-
2657 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2660 then automatically you will ONLY get VHF spots from or to CQ zones 14
2661 15 and 16. If you set a reject filter like:
2664 reject/spots on hf/cw
2667 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
2668 and will work it even on CW then you could say:-
2671 reject/spots on hf/cw and not info iota
2674 But in that case you might only be interested in iota and say:-
2677 accept/spots not on hf/cw or info iota
2680 which is exactly the same. You should choose one or the other until
2681 you are confortable with the way it works. Yes, you can mix them
2682 (actually you can have an accept AND a reject on the same line) but
2683 don't try this at home until you can analyse the results that you get
2684 without ringing up the sysop for help.
2686 Another useful addition now is filtering by US state
2689 accept/spots by_state VA,NH,RI,ME
2692 You can arrange your filter lines into logical units, either for your
2693 own understanding or simply convenience. I have one set frequently:-
2696 reject/spots 1 on hf/cw
2697 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2700 What this does is to ignore all HF CW spots (being a class B I can't
2701 read any CW and couldn't possibly be interested in HF :-) and also
2702 rejects any spots on VHF which don't either originate or spot someone
2705 This is an exmaple where you would use the line number (1 and 2 in
2706 this case), if you leave the digit out, the system assumes '1'. Digits
2707 '0'-'9' are available.
2709 You can leave the word 'and' out if you want, it is implied. You can
2710 use any number of brackets to make the 'expression' as you want
2711 it. There are things called precedence rules working here which mean
2712 that you will NEED brackets in a situation like line 2 because,
2713 without it, will assume:-
2716 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2719 annoying, but that is the way it is. If you use OR - use
2720 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
2723 If you want to alter your filter you can just redefine one or more
2724 lines of it or clear out one line. For example:-
2727 reject/spots 1 on hf/ssb
2736 To remove the filter in its entirty:-
2742 There are similar CLEAR commands for the other filters:-
2752 Once you are happy with the results you get, you may like to experiment.
2754 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
2755 can be written with a mixed filter, eg:
2760 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
2763 each filter slot actually has a 'reject' slot and an 'accept'
2764 slot. The reject slot is executed BEFORE the accept slot.
2766 It was mentioned earlier that after a reject test that doesn't match,
2767 the default for following tests is 'accept', the reverse is true for
2768 'accept'. In the example what happens is that the reject is executed
2769 first, any non hf/cw spot is passed to the accept line, which lets
2770 thru everything else on HF.
2772 The next filter line lets through just VHF/UHF spots from EU.
2773 <sect1>forward/latlong <node_call> (8)
2777 <bf>forward/latlong <node_call></bf> Send latitude and longitude information to another cluster
2781 This command sends all the latitude and longitude information that your
2782 cluster is holding against callsigns. One advantage of recieving this
2783 information is that more locator information is held by you. This
2784 means that more locators are given on the DX line assuming you have
2785 SET/DXGRID enabled. This could be a LOT of information though, so
2786 it is not recommended on slow links.
2787 <sect1>forward/opernam <call> (1)
2791 <bf>forward/opernam <call></bf> Send out information on this <call> to all clusters
2795 This command sends out any information held in the user file which can
2796 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
2797 and Homenode. PC41s are only sent for the information that is available.
2803 <bf>help</bf> The HELP Command
2807 HELP is available for a number of commands. The syntax is:-
2813 Where <cmd> is the name of the command you want help on.
2815 All commands can be abbreviated, so SHOW/DX can be abbreviated
2816 to SH/DX, ANNOUNCE can be shortened to AN and so on.
2818 Look at the APROPOS <string> command which will search the help database
2819 for the <string> you specify and give you a list of likely commands
2820 to look at with HELP.
2821 <sect1>init <node> (5)
2825 <bf>init <node></bf> Re-initialise a link to an AK1A compatible node
2829 This command attempts to re-initialise a link to a (usually) AK1A node
2830 that has got confused, usually by a protocol loop of some kind. It may
2831 work - but you usually will be better off simply disconnecting it (or
2832 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
2835 Best of luck - you will need it.
2845 As a sysop you can kill any message on the system.
2846 <sect1>kill <from msgno>-<to msgno> (0)
2850 <bf>kill <from msgno>-<to msgno></bf> Delete a range of messages
2854 <sect1>kill <from>-<to> (5)
2858 <bf>kill <from>-<to></bf> Remove a range of messages from the system
2862 <sect1>kill <msgno> [<msgno..] (0)
2866 <bf>kill <msgno> [<msgno..]</bf> Delete a message from the local system
2870 <sect1>kill <msgno> [<msgno> ...] (0)
2874 <bf>kill <msgno> [<msgno> ...]</bf> Remove or erase a message from the system
2878 You can get rid of any message to or originating from your callsign using
2879 this command. You can remove more than one message at a time.
2880 <sect1>kill expunge <msgno> [<msgno..] (6)
2884 <bf>kill expunge <msgno> [<msgno..]</bf> Expunge a message
2888 Deleting a message using the normal KILL commands only marks that message
2889 for deletion. The actual deletion only happens later (usually two days later).
2891 The KILL EXPUNGE command causes the message to be truly deleted more or less
2894 It otherwise is used in the same way as the KILL command.
2895 <sect1>kill from <call> (5)
2899 <bf>kill from <call></bf> Remove all messages from a callsign
2903 <sect1>kill full <msgno> [<msgno..] (5)
2907 <bf>kill full <msgno> [<msgno..]</bf> Delete a message from the whole cluster
2911 Delete a message from the local system. You will only be able to
2912 delete messages that you have originated or been sent (unless you are
2919 Will delete all the messages that you own between msgnos 1234 and 1255.
2925 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
2931 will delete all messages to g1tlh.
2937 will delete a message (usually a 'bulletin') from the whole cluster system.
2939 This uses the subject field, so any messages that have exactly the
2940 same subject will be deleted. Beware!
2941 <sect1>kill full <msgno> [<msgno] (5)
2945 <bf>kill full <msgno> [<msgno]</bf> Remove a message from the entire cluster
2949 Remove this message from the entire cluster system as well as your node.
2950 <sect1>kill to <call> (5)
2954 <bf>kill to <call></bf> Remove all messages to a callsign
2958 <sect1>kill from <regex> (0)
2962 <bf>kill from <regex></bf> Delete messages FROM a callsign or pattern
2966 <sect1>kill to <regex> (0)
2970 <bf>kill to <regex></bf> Delete messages TO a callsign or pattern
2978 <bf>links</bf> Show which nodes is physically connected
2982 This is a quick listing that shows which links are connected and
2983 some information about them. See WHO for a list of all connections.
2984 <sect1>load/keps (5)
2988 <bf>load/keps</bf> Load new keps data
2992 <sect1>load/keps [nn] (5)
2996 <bf>load/keps [nn]</bf> Load new keps data from message
3000 If there is no message number then reload the current Keps data from
3001 the Keps.pm data file. You create this file by running
3004 /spider/perl/convkeps.pl <filename>
3007 on a file containing NASA 2 line keps as a message issued by AMSAT.
3009 If there is a message number, then it will take the message, run
3010 convkeps.pl on it and then load the data, all in one step.
3012 These messages are sent to ALL by GB7DJK (and others) from time to time.
3013 <sect1>merge <node> [<no spots>/<no wwv>] (5)
3017 <bf>merge <node> [<no spots>/<no wwv>]</bf> Ask for the latest spots and WWV
3021 MERGE allows you to bring your spot and wwv database up to date. By default
3022 it will request the last 10 spots and 5 WWVs from the node you select. The
3023 node must be connected locally.
3025 You can request any number of spots or wwv and although they will be appended
3026 to your databases they will not duplicate any that have recently been added
3027 (the last 2 days for spots and last month for WWV data).
3028 <sect1>pc <call> <text> (8)
3032 <bf>pc <call> <text></bf> Send arbitrary text to a connected callsign
3036 Send some arbitrary text to a locally connected callsign. No
3037 processing is done on the text. This command allows you to send PC
3038 Protocol to unstick things if problems arise (messages get stuck
3042 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3046 pc G1TLH Try doing that properly!!!
3049 Send any text you like to the callsign requested. This is used mainly to send
3050 PC protocol to connected nodes either for testing or to unstick things.
3052 You can also use in the same way as a talk command to a connected user but
3053 without any processing, added of "from <blah> to <blah" or whatever.
3055 <sect1>ping <node call> (1)
3059 <bf>ping <node call></bf> Check the link quality between nodes
3063 This command allows you to send a frame to another cluster node on
3064 the network and get a return frame. The time it takes to do this
3065 is a good indication of the quality of the link. The actual time
3066 it takes is output to the console in seconds.
3067 Any visible cluster node can be PINGed.
3068 <sect1>rcmd <node call> <cmd> (1)
3072 <bf>rcmd <node call> <cmd></bf> Send a command to another DX Cluster
3076 This command allows you to send nearly any command to another DX Cluster
3077 node that is connected to the system.
3079 Whether you get any output is dependant on a) whether the other system knows
3080 that the node callsign of this cluster is in fact a node b) whether the
3081 other system is allowing RCMDs from this node and c) whether you have
3082 permission to send this command at all.
3087 <bf>read</bf> Read the next unread personal message addressed to you
3091 <sect1>read <msgno> (0)
3095 <bf>read <msgno></bf> Read the specified message
3099 You can read any messages that are sent as 'non-personal' and also any
3100 message either sent by or sent to your callsign.
3109 As a sysop you may read any message on the system
3114 <bf>reject</bf> Set a filter to reject something
3118 Create a filter to reject something
3120 There are 2 types of filter, accept and reject. See HELP FILTERING for more
3122 <sect1>reject/announce <call> [input] [0-9] <pattern> (8)
3126 <bf>reject/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version
3130 This version allows a sysop to set a filter for a callsign as well as the
3131 default for nodes and users eg:-
3135 reject/ann input node_default by G,M,2
3136 reject/ann user_default by G,M,2
3139 <sect1>reject/announce [0-9] <pattern> (0)
3143 <bf>reject/announce [0-9] <pattern></bf> Set a 'reject' filter line for announce
3147 Create an 'reject this announce' line for a filter.
3149 A reject filter line means that if the announce matches this filter it is
3150 passed onto the user. See HELP FILTERING for more info. Please read this
3151 to understand how filters work - it will save a lot of grief later on.
3153 You can use any of the following things in this line:-
3156 info <string> eg: iota or qsl
3157 by <prefixes> eg: G,M,2
3158 origin <prefixes>
3159 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3160 origin_itu <prefixes or numbers> or: G,GM,GW
3161 origin_zone <prefixes or numbers>
3162 origin_state <states> eg: VA,NH,RI,ME
3163 by_dxcc <prefixes or numbers>
3164 by_itu <prefixes or numbers>
3165 by_zone <prefixes or numbers>
3166 by_state <states> eg: VA,NH,RI,ME
3167 channel <prefixes>
3168 wx 1 filter WX announces
3169 dest <prefixes> eg: 6MUK,WDX (distros)
3175 rej/ann by_zone 14,15,16 and not by G,M,2
3178 You can use the tag 'all' to reject everything eg:
3184 but this probably for advanced users...
3185 <sect1>reject/route <call> [0-9] <pattern> (8)
3189 <bf>reject/route <call> [0-9] <pattern></bf> Set an 'reject' filter line for routing
3193 Create an 'reject this routing PC Protocol' line for a filter.
3195 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
3196 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
3197 read this to understand how filters work - it will save a lot of grief later on.
3199 You can use any of the following things in this line:-
3202 call <prefixes> the callsign of the thingy
3203 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3204 call_itu <prefixes or numbers> or: G,GM,GW
3205 call_zone <prefixes or numbers>
3206 call_state <states> eg: VA,NH,RI,ME
3207 origin <prefixes> really the interface it came in on
3208 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3209 origin_itu <prefixes or numbers> or: G,GM,GW
3210 origin_zone <prefixes or numbers>
3211 origin_state <states> eg: VA,NH,RI,ME
3217 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3220 You can use the tag 'all' to reject everything eg:
3223 rej/route all (equiv to [very] restricted mode)
3226 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3227 <sect1>reject/spots <call> [input] [0-9] <pattern> (8)
3231 <bf>reject/spots <call> [input] [0-9] <pattern></bf> Spot filter sysop version
3235 This version allows a sysop to set a filter for a callsign as well as the
3236 default for nodes and users eg:-
3239 reject/spot db0sue-7 1 by_zone 14,15,16
3240 reject/spot node_default all
3241 set/hops node_default 10
3245 reject/spot user_default by G,M,2
3248 <sect1>reject/spots [0-9] <pattern> (0)
3252 <bf>reject/spots [0-9] <pattern></bf> Set a 'reject' filter line for spots
3256 Create a 'reject this spot' line for a filter.
3258 A reject filter line means that if the spot matches this filter it is
3259 dumped (not passed on). See HELP FILTERING for more info. Please read this
3260 to understand how filters work - it will save a lot of grief later on.
3262 You can use any of the following things in this line:-
3265 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
3266 on <range> same as 'freq'
3267 call <prefixes> eg: G,PA,HB9
3268 info <string> eg: iota or qsl
3270 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3271 call_itu <prefixes or numbers> or: G,GM,GW
3272 call_zone <prefixes or numbers>
3273 call_state <states> eg: VA,NH,RI,ME
3274 by_dxcc <prefixes or numbers>
3275 by_itu <prefixes or numbers>
3276 by_zone <prefixes or numbers>
3277 by_state <states> eg: VA,NH,RI,ME
3278 origin <prefixes>
3279 channel <prefixes>
3282 'call' means the callsign that has spotted 'by' whoever.
3284 For frequencies, you can use any of the band names defined in
3285 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
3286 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
3287 this is more efficient than saying simply: on HF (but don't get
3288 too hung up about that)
3294 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3297 You can use the tag 'all' to reject everything eg:
3303 but this probably for advanced users...
3304 <sect1>reject/wcy <call> [input] [0-9] <pattern> (8)
3308 <bf>reject/wcy <call> [input] [0-9] <pattern></bf> WCY filter sysop version
3312 This version allows a sysop to set a filter for a callsign as well as the
3313 default for nodes and users eg:-
3316 reject/wcy gb7djk all
3319 <sect1>reject/wcy [0-9] <pattern> (0)
3323 <bf>reject/wcy [0-9] <pattern></bf> set a 'reject' WCY filter
3327 It is unlikely that you will want to do this, but if you do then you can
3328 filter on the following fields:-
3331 by <prefixes> eg: G,M,2
3332 origin <prefixes>
3333 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3334 origin_itu <prefixes or numbers> or: G,GM,GW
3335 origin_zone <prefixes or numbers>
3336 by_dxcc <prefixes or numbers>
3337 by_itu <prefixes or numbers>
3338 by_zone <prefixes or numbers>
3339 channel <prefixes>
3342 There are no examples because WCY Broadcasts only come from one place and
3343 you either want them or not (see UNSET/WCY if you don't want them).
3345 This command is really provided for future use.
3347 See HELP FILTER for information.
3348 <sect1>reject/wwv <call> [input] [0-9] <pattern> (8)
3352 <bf>reject/wwv <call> [input] [0-9] <pattern></bf> WWV filter sysop version
3356 This version allows a sysop to set a filter for a callsign as well as the
3357 default for nodes and users eg:-
3360 reject/wwv db0sue-7 1 by_zone 4
3361 reject/wwv node_default all
3365 reject/wwv user_default by W
3368 <sect1>reject/wwv [0-9] <pattern> (0)
3372 <bf>reject/wwv [0-9] <pattern></bf> set a 'reject' WWV filter
3376 It is unlikely that you will want to do this, but if you do then you can
3377 filter on the following fields:-
3380 by <prefixes> eg: G,M,2
3381 origin <prefixes>
3382 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3383 origin_itu <prefixes or numbers> or: G,GM,GW
3384 origin_zone <prefixes or numbers>
3385 by_dxcc <prefixes or numbers>
3386 by_itu <prefixes or numbers>
3387 by_zone <prefixes or numbers>
3388 channel <prefixes>
3394 reject/wwv by_zone 14,15,16
3397 is probably the only useful thing to do (which will only show WWV broadcasts
3398 by stations in the US).
3400 See HELP FILTER for information.
3405 <bf>reply</bf> Reply (privately) to the last message that you have read
3409 <sect1>reply <msgno> (0)
3413 <bf>reply <msgno></bf> Reply (privately) to the specified message
3417 <sect1>reply b <msgno> (0)
3421 <bf>reply b <msgno></bf> Reply as a Bulletin to the specified message
3425 <sect1>reply noprivate <msgno> (0)
3429 <bf>reply noprivate <msgno></bf> Reply as a Bulletin to the specified message
3433 <sect1>reply rr <msgno> (0)
3437 <bf>reply rr <msgno></bf> Reply to the specified message with read receipt
3441 You can reply to a message and the subject will automatically have
3442 "Re:" inserted in front of it, if it isn't already present.
3444 You can also use all the extra qualifiers such as RR, PRIVATE,
3445 NOPRIVATE, B that you can use with the SEND command (see SEND
3446 for further details)
3447 <sect1>send <call> [<call> ...] (0)
3451 <bf>send <call> [<call> ...]</bf> Send a message to one or more callsigns
3455 <sect1>send copy <msgno> <call> (0)
3459 <bf>send copy <msgno> <call></bf> Send a copy of a message to someone
3463 <sect1>send noprivate <call> (0)
3467 <bf>send noprivate <call></bf> Send a message to all stations
3471 All the SEND commands will create a message which will be sent either to
3472 an individual callsign or to one of the 'bulletin' addresses.
3474 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
3475 it will mark the message as personal and send it to the cluster node that
3476 that callsign is connected to. If the <call> you have specified is in fact
3477 a known bulletin category on your node (eg: ALL) then the message should
3478 automatically become a bulletin.
3480 You can have more than one callsign in all of the SEND commands.
3482 You can have multiple qualifiers so that you can have for example:-
3485 SEND RR COPY 123 PRIVATE G1TLH G0RDI
3488 which should send a copy of message 123 to G1TLH and G0RDI and you will
3489 receive a read receipt when they have read the message.
3491 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
3492 SP is an alias for SEND PRIVATE
3494 The system will ask you for a subject. Conventionally this should be
3495 no longer than 29 characters for compatibility. Most modern cluster
3496 software should accept more.
3498 You will now be prompted to start entering your text.
3500 You finish the message by entering '/EX' on a new line. For instance:
3509 If you have started a message and you don't want to keep it then you
3510 can abandon the message with '/ABORT' on a new line, like:-
3515 oh I just can't be bothered with this
3519 If you abort the message it will NOT be sent.
3521 When you are entering the text of your message, most normal output (such
3522 as DX announcements and so on are suppressed and stored for latter display
3523 (upto 20 such lines are stored, as new ones come along, so the oldest
3526 Also, you can enter normal commands commands (and get the output
3527 immediately) whilst in the middle of a message. You do this by typing
3528 the command preceeded by a '/' character on a new line, so:-
3531 /dx g1tlh 144010 strong signal
3534 Will issue a dx annoucement to the rest of the cluster.
3536 Also, you can add the output of a command to your message by preceeding
3537 the command with '//', thus :-
3543 This will show YOU the output from SH/VHFTABLE and also store it in the
3546 You can carry on with the message until you are ready to send it.
3547 <sect1>send private <call> (0)
3551 <bf>send private <call></bf> Send a personal message
3555 <sect1>send rr <call> (0)
3559 <bf>send rr <call></bf> Send a message and ask for a read receipt
3563 <sect1>set/address <your address> (0)
3567 <bf>set/address <your address></bf> Record your postal address
3571 <sect1>set/announce (0)
3575 <bf>set/announce</bf> Allow announce messages to come out on your terminal
3579 <sect1>set/anntalk (0)
3583 <bf>set/anntalk</bf> Allow talk like announce messages on your terminal
3587 <sect1>set/arcluster <call> [<call>..] (5)
3591 <bf>set/arcluster <call> [<call>..]</bf> Make the callsign an AR-Cluster node
3595 <sect1>set/baddx <call>.. (8)
3599 <bf>set/baddx <call>..</bf> Stop callsigns in a dx spot being propagated
3603 <sect1>set/badnode <call>.. (8)
3607 <bf>set/badnode <call>..</bf> Stop spots from this node being propagated
3611 <sect1>set/badspotter <call>.. (8)
3615 <bf>set/badspotter <call>..</bf> Stop spots from this callsign being propagated
3619 <sect1>set/badword <word>.. (8)
3623 <bf>set/badword <word>..</bf> Stop things with this word being propagated
3627 <sect1>set/bbs <call> [<call>..] (5)
3631 <bf>set/bbs <call> [<call>..]</bf> Make the callsign a BBS
3639 <bf>set/beep</bf> Add a beep to DX and other messages on your terminal
3643 <sect1>set/clx <call> [<call>..] (5)
3647 <bf>set/clx <call> [<call>..]</bf> Make the callsign an CLX node
3655 <bf>set/dx</bf> Allow DX messages to come out on your terminal
3659 <sect1>set/dxgrid (0)
3663 <bf>set/dxgrid</bf> Allow QRA Grid Squares on the end of DX announcements
3667 <sect1>set/dxnet <call> [<call>..] (5)
3671 <bf>set/dxnet <call> [<call>..]</bf> Make the callsign an DXNet node
3679 <bf>set/echo</bf> Make the cluster echo your input
3683 <sect1>set/email <email> ... (0)
3687 <bf>set/email <email> ...</bf> Set email address(es) and forward your personals
3695 <bf>set/here</bf> Tell the system you are present at your terminal
3699 <sect1>set/homenode <node> (0)
3703 <bf>set/homenode <node> </bf> Set your normal cluster callsign
3707 Tell the cluster system where you normally connect to. Any Messages sent
3708 to you will normally find their way there should you not be connected.
3714 <sect1>set/hops <call> ann|spots|route|wwv|wcy <n> (8)
3718 <bf>set/hops <call> ann|spots|route|wwv|wcy <n></bf> Set hop count
3722 <sect1>set/language <lang> (0)
3726 <bf>set/language <lang></bf> Set the language you want to use
3730 You can select the language that you want the cluster to use. Currently
3731 the languages available are en (English), de (German), es (Spanish)
3733 <sect1>set/location <lat & long> (0)
3737 <bf>set/location <lat & long></bf> Set your latitude and longitude
3741 <sect1>set/logininfo (0)
3745 <bf>set/logininfo</bf> Inform when a station logs in locally
3749 <sect1>set/name <your name> (0)
3753 <bf>set/name <your name></bf> Set your name
3757 Tell the system what your name is eg:-
3762 <sect1>set/node <call> [<call>..] (5)
3766 <bf>set/node <call> [<call>..]</bf> Make the callsign an AK1A cluster
3770 Tell the system that the call(s) are to be treated as AK1A cluster and
3771 fed PC Protocol rather normal user commands.
3772 <sect1>set/obscount <count> <call> (8)
3776 <bf>set/obscount <count> <call></bf> Set the 'pump-up' obscelence PING counter
3780 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
3781 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
3782 counter which is decremented on every outgoing ping and then reset to
3783 the 'obscount' value on every incoming ping. The default value of this
3786 What this means is that a neighbouring node will be pinged twice at
3787 (default) 300 second intervals and if no reply has been heard just before
3788 what would be the third attempt, that node is disconnected.
3790 If a ping is heard then the obscount is reset to the full value. Using
3791 default values, if a node has not responded to a ping within 15 minutes,
3794 You can set this parameter between 1 and 9.
3796 It is STRONGLY recommended that you don't change the default.
3797 <sect1>set/page <lines per page> (0)
3801 <bf>set/page <lines per page></bf> Set the lines per page
3805 Tell the system how many lines you wish on a page when the number of line
3806 of output from a command is more than this. The default is 20. Setting it
3807 explicitly to 0 will disable paging.
3813 The setting is stored in your user profile.
3814 <sect1>set/password (0)
3818 <bf>set/password</bf> Set your own password
3822 This command only works for a 'telnet' user (currently). It will
3823 only work if you have a password already set. This initial password
3824 can only be set by the sysop.
3826 When you execute this command it will ask you for your old password,
3827 then ask you to type in your new password twice (to make sure you
3828 get it right). You may or may not see the data echoed on the screen
3829 as you type, depending on the type of telnet client you have.
3830 <sect1>set/prompt <string> (0)
3834 <bf>set/prompt <string></bf> Set your prompt to <string>
3838 <sect1>set/qra <locator> (0)
3842 <bf>set/qra <locator></bf> Set your QRA Grid locator
3846 Tell the system what your QRA (or Maidenhead) locator is. If you have not
3847 done a SET/LOCATION then your latitude and longitude will be set roughly
3848 correctly (assuming your locator is correct ;-). For example:-
3853 <sect1>set/qth <your qth> (0)
3857 <bf>set/qth <your qth></bf> Set your QTH
3861 Tell the system where you are. For example:-
3863 SET/QTH East Dereham, Norfolk
3866 <sect1>set/spider <call> [<call>..] (5)
3870 <bf>set/spider <call> [<call>..]</bf> Make the callsign an DXSpider node
3874 Tell the system that the call(s) are to be treated as DXSpider node and
3875 fed new style DX Protocol rather normal user commands.
3880 <bf>set/talk</bf> Allow TALK messages to come out on your terminal
3888 <bf>set/wcy</bf> Allow WCY messages to come out on your terminal
3896 <bf>set/wwv</bf> Allow WWV messages to come out on your terminal
3904 <bf>set/wx</bf> Allow WX messages to come out on your terminal
3908 <sect1>show/baddx (1)
3912 <bf>show/baddx</bf> Show all the bad dx calls in the system
3916 Display all the bad dx callsigns in the system, see SET/BADDX
3917 for more information.
3918 <sect1>show/badnode (1)
3922 <bf>show/badnode</bf> Show all the bad nodes in the system
3926 Display all the bad node callsigns in the system, see SET/BADNODE
3927 for more information.
3928 <sect1>show/badspotter (1)
3932 <bf>show/badspotter</bf> Show all the bad spotters in the system
3936 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
3937 for more information.
3938 <sect1>show/badword (1)
3942 <bf>show/badword</bf> Show all the bad words in the system
3946 Display all the bad words in the system, see SET/BADWORD
3947 for more information.
3948 <sect1>show/configuration [<node>] (0)
3952 <bf>show/configuration [<node>]</bf> Show all the nodes and users visible
3956 This command allows you to see all the users that can be seen
3957 and the nodes to which they are connected.
3959 This command is normally abbreviated to: sh/c
3961 Normally, the list returned will be just for the nodes from your
3962 country (because the list otherwise will be very long).
3968 will produce a complete list of all nodes.
3970 BE WARNED: the list that is returned can be VERY long
3972 It is possible to supply a node or part of a prefix and you will get
3973 a list of the users for that node or list of nodes starting with
3984 <sect1>show/configuration/node (0)
3988 <bf>show/configuration/node</bf> Show all the nodes connected locally
3992 Show all the nodes connected to this node.
3993 <sect1>show/connect (1)
3997 <bf>show/connect</bf> Show all the active connections
4001 This command shows information on all the active connections known to
4002 the node. This command gives slightly more information than WHO.
4003 <sect1>show/date [<prefix>|<callsign>] (0)
4007 <bf>show/date [<prefix>|<callsign>]</bf> Show the local time
4011 This is very nearly the same as SHOW/TIME, the only difference the format
4012 of the date string if no arguments are given.
4014 If no prefixes or callsigns are given then this command returns the local
4015 time and UTC as the computer has it right now. If you give some prefixes
4016 then it will show UTC and UTC + the local offset (not including DST) at
4017 the prefixes or callsigns that you specify.
4022 <bf>show/dx</bf> Interrogate the spot database
4026 If you just type SHOW/DX you will get the last so many spots
4027 (sysop configurable, but usually 10).
4029 In addition you can add any number of these commands in very nearly
4030 any order to the basic SHOW/DX command, they are:-
4033 on <band> - eg 160m 20m 2m 23cm 6mm
4034 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
4035 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
4036 <from>-<to>
4040 <number> - the number of spots you want
4041 <from>-<to> - <from> spot no <to> spot no in the selected list
4042 <from>/<to>
4046 <prefix> - for a spotted callsign beginning with <prefix>
4047 *<suffix> - for a spotted callsign ending in <suffix>
4048 *<string>* - for a spotted callsign containing <string>
4052 day <number> - starting <number> days ago
4053 day <from>-<to> - <from> days <to> days ago
4054 <from>/<to>
4058 info <text> - any spots containing <text> in the info or remarks
4062 by <call> - any spots spotted by <call> (spotter <call> is the
4067 qsl - this automatically looks for any qsl info on the call
4068 held in the spot database.
4072 iota [<iota>] - If the iota island number is missing it will look for
4073 the string iota and anything which looks like an iota
4074 island number. If you specify then it will look for
4079 qra [<locator>] - this will look for the specific locator if you specify
4080 one or else anything that looks like a locator.
4084 dxcc - treat the prefix as a 'country' and look for spots
4085 from that country regardless of actual prefix.
4090 You can also use this with the 'by' keyword so
4100 SH/DX on 20m info iota
4101 SH/DX 9a on vhf day 30
4107 SH/DX dxcc oq2 by w dxcc
4110 <sect1>show/dxcc <prefix> (0)
4114 <bf>show/dxcc <prefix></bf> Interrogate the spot database by country
4118 This command takes the <prefix> (which can be a full or partial
4119 callsign if desired), looks up which internal country number it is
4120 and then displays all the spots as per SH/DX for that country.
4122 This is now an alias for 'SHOW/DX DXCC'
4124 The options for SHOW/DX also apply to this command.
4129 SH/DXCC W on 20m iota
4132 This can be done with the SHOW/DX command like this:-
4136 SH/DX dxcc w on 20m iota
4139 <sect1>show/dxstats [days] [date] (0)
4143 <bf>show/dxstats [days] [date]</bf> Show the DX Statistics
4147 Show the total DX spots for the last <days> no of days (default is 31),
4148 starting from a <date> (default: today).
4149 <sect1>show/files [<filearea> [<string>]] (0)
4153 <bf>show/files [<filearea> [<string>]]</bf> List the contents of a filearea
4157 SHOW/FILES on its own will show you a list of the various fileareas
4158 available on the system. To see the contents of a particular file
4161 SH/FILES <filearea>
4163 where <filearea> is the name of the filearea you want to see the
4166 You can also use shell globbing characters like '*' and '?' in a
4167 string to see a selection of files in a filearea eg:-
4169 SH/FILES bulletins arld*
4172 See also TYPE - to see the contents of a file.
4173 <sect1>show/filter (0)
4177 <bf>show/filter</bf> Show the contents of all the filters you have set
4181 Show the contents of all the filters that are set. This command displays
4182 all the filters set - for all the various categories.
4183 <sect1>show/hfstats [days] [date] (0)
4187 <bf>show/hfstats [days] [date]</bf> Show the HF DX Statistics
4191 Show the HF DX spots breakdown by band for the last <days> no of days
4192 (default is 31), starting from a <date> (default: today).
4193 <sect1>show/hftable [days] [date] [prefix ...] (0)
4197 <bf>show/hftable [days] [date] [prefix ...]</bf> Show the HF DX Spotter Table
4201 Show the HF DX Spotter table for the list of prefixes for the last
4202 <days> no of days (default is 31), starting from a <date> (default: today).
4204 If there are no prefixes then it will show the table for your country.
4206 Remember that some countries have more than one "DXCC country" in them
4207 (eg G :-), to show them (assuming you are not in G already which is
4208 specially treated in the code) you must list all the relevant prefixes
4211 sh/hftable g gm gd gi gj gw gu
4214 Note that the prefixes are converted into country codes so you don't have
4215 to list all possible prefixes for each country.
4217 If you want more or less days than the default simply include the
4218 number you require:-
4224 If you want to start at a different day, simply add the date in some
4228 sh/hftable 2 25nov02
4229 sh/hftable 2 25-nov-02
4231 sh/hftable 2 25/11/02
4234 This will show the stats for your DXCC for that CQWW contest weekend.
4236 You can specify either prefixes or full callsigns (so you can see how you
4237 did against all your mates). You can also say 'all' which will then print
4238 the worldwide statistics.
4244 <sect1>show/hops <call> [ann|spots|route|wcy|wwv] (8)
4248 <bf>show/hops <call> [ann|spots|route|wcy|wwv]</bf> Show the hop counts for a node
4252 This command shows the hop counts set up for a node. You can specify
4253 which category you want to see. If you leave the category out then
4254 all the categories will be listed.
4256 <sect1>show/isolate (1)
4260 <bf>show/isolate</bf> Show list of ISOLATED nodes
4264 <sect1>show/log [<callsign>] (8)
4268 <bf>show/log [<callsign>]</bf> Show excerpts from the system log
4272 This command outputs a short section of the system log. On its own
4273 it will output a general logfile. With the optional callsign it will
4274 show output from the log associated with that callsign.
4275 <sect1>show/moon [ndays] [<prefix>|<callsign>] (0)
4279 <bf>show/moon [ndays] [<prefix>|<callsign>]</bf> Show Moon rise and set times
4283 Show the Moon rise and set times for a (list of) prefixes or callsigns,
4284 together with the azimuth and elevation of the sun currently at those
4287 If you don't specify any prefixes or callsigns, it will show the times for
4288 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
4289 together with the current azimuth and elevation.
4291 In addition, it will show the illuminated fraction of the moons disk.
4293 If all else fails it will show the Moonrise and set times for the node
4294 that you are connected to.
4303 You can also use this command to see into the past or the future, so
4304 if you want to see yesterday's times then do:-
4310 or in three days time:-
4316 Upto 366 days can be checked both in the past and in the future.
4318 Please note that the rise and set times are given as the UT times of rise and
4319 set on the requested UT day.
4320 <sect1>show/muf <prefix> [<hours>][long] (0)
4324 <bf>show/muf <prefix> [<hours>][long]</bf> Show the likely propagation to a prefix
4328 This command allow you to estimate the likelihood of you contacting
4329 a station with the prefix you have specified. The output assumes a modest
4330 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
4332 The result predicts the most likely operating frequencies and signal
4333 levels for high frequency (shortwave) radio propagation paths on
4334 specified days of the year and hours of the day. It is most useful for
4335 paths between 250 km and 6000 km, but can be used with reduced accuracy
4336 for paths shorter or longer than this.
4338 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
4339 used to predict the MUF given the predicted flux, day of the year,
4340 hour of the day and geographic coordinates of the transmitter and
4341 receiver. This routine is reasonably accurate for the purposes here,
4342 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
4343 than the programs used by major shortwave broadcasting organizations,
4344 such as the Voice of America.
4346 The command will display some header information detailing its
4347 assumptions, together with the locations, latitude and longitudes and
4348 bearings. It will then show UTC (UT), local time at the other end
4349 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
4350 (Zen) and the likely signal strengths. Then for each frequency for which
4351 the system thinks there is a likelihood of a circuit it prints a value.
4353 The value is currently a likely S meter reading based on the conventional
4354 6dB / S point scale. If the value has a '+' appended it means that it is
4355 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
4356 there is likely to be much fading and by an 's' that the signal is likely
4359 By default SHOW/MUF will show the next two hours worth of data. You
4360 can specify anything up to 24 hours worth of data by appending the no of
4361 hours required after the prefix. For example:-
4370 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
4371 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
4372 Location Lat / Long Azim
4373 East Dereham, Norfolk 52 41 N 0 57 E 47
4374 United-States-W 43 0 N 87 54 W 299
4375 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
4376 18 23 11.5 -35 mS0+ mS2 S3
4377 19 0 11.2 -41 mS0+ mS2 S3
4380 indicating that you will have weak, fading circuits on top band and
4381 80m but usable signals on 40m (about S3).
4389 will get you the above display, but with the next 24 hours worth of
4397 Gives you an estimate of the long path propagation characterics. It
4398 should be noted that the figures will probably not be very useful, nor
4399 terrible accurate, but it is included for completeness.
4400 <sect1>show/newconfiguration [<node>] (0)
4404 <bf>show/newconfiguration [<node>]</bf> Show all the nodes and users visible
4408 This command allows you to see all the users that can be seen
4409 and the nodes to which they are connected.
4411 This command produces essentially the same information as
4412 SHOW/CONFIGURATION except that it shows all the duplication of
4413 any routes that might be present It also uses a different format
4414 which may not take up quite as much space if you don't have any
4417 BE WARNED: the list that is returned can be VERY long
4418 <sect1>show/newconfiguration/node (0)
4422 <bf>show/newconfiguration/node</bf> Show all the nodes connected locally
4426 Show all the nodes connected to this node in the new format.
4427 <sect1>show/node [<callsign> ...] (1)
4431 <bf>show/node [<callsign> ...]</bf> Show the type and version number of nodes
4435 Show the type and version (if connected) of the nodes specified on the
4436 command line. If no callsigns are specified then a sorted list of all
4437 the non-user callsigns known to the system will be displayed.
4438 <sect1>show/prefix <callsign> (0)
4442 <bf>show/prefix <callsign></bf> Interrogate the prefix database
4446 This command takes the <callsign> (which can be a full or partial
4447 callsign or a prefix), looks up which internal country number
4448 it is and then displays all the relevant prefixes for that country
4449 together with the internal country no, the CQ and ITU regions.
4452 <sect1>show/program (5)
4456 <bf>show/program</bf> Show the locations of all the included program modules
4460 Show the name and location where every program module was load from. This
4461 is useful for checking where you think you have loaded a .pm file from.
4462 <sect1>show/qra <lat> <long> (0)
4466 <bf>show/qra <lat> <long></bf> Convert lat/long to a QRA Grid locator
4470 This is a multipurpose command that allows you either to calculate the
4471 distance and bearing between two locators or (if only one locator is
4472 given on the command line) the distance and beraing from your station
4473 to the locator. For example:-
4480 The first example will show the distance and bearing to the locator from
4481 yourself, the second example will calculate the distance and bearing from
4482 the first locator to the second. You can use 4 or 6 character locators.
4484 It is also possible to convert a latitude and longitude to a locator by
4485 using this command with a latitude and longitude as an argument, for
4489 SH/QRA 52 41 N 0 58 E
4492 <sect1>show/qra <locator> [<locator>] (0)
4496 <bf>show/qra <locator> [<locator>]</bf> Show distance between QRA Grid locators
4500 <sect1>show/qrz <callsign> (0)
4504 <bf>show/qrz <callsign></bf> Show any callbook details on a callsign
4508 This command queries the QRZ callbook server on the internet
4509 and returns any information available for that callsign. This service
4510 is provided for users of this software by http://www.qrz.com
4511 <sect1>show/route <callsign> ... (0)
4515 <bf>show/route <callsign> ...</bf> Show the route to the callsign
4519 This command allows you to see to which node the callsigns specified are
4520 connected. It is a sort of inverse sh/config.
4526 <sect1>show/satellite <name> [<hours> <interval>] (0)
4530 <bf>show/satellite <name> [<hours> <interval>]</bf> Show tracking data
4534 Show the tracking data from your location to the satellite of your choice
4535 from now on for the next few hours.
4537 If you use this command without a satellite name it will display a list
4538 of all the satellites known currently to the system.
4540 If you give a name then you can obtain tracking data of all the passes
4541 that start and finish 5 degrees below the horizon. As default it will
4542 give information for the next three hours for every five minute period.
4544 You can alter the number of hours and the step size, within certain
4547 Each pass in a period is separated with a row of '-----' characters
4553 SH/SAT FENGYUN1 12 2
4556 <sect1>show/station all [<regex>] (6)
4560 <bf>show/station all [<regex>]</bf> Show list of users in the system
4564 <sect1>show/station [<callsign> ..] (0)
4568 <bf>show/station [<callsign> ..]</bf> Show information about a callsign
4572 Show the information known about a callsign and whether (and where)
4573 that callsign is connected to the cluster.
4579 If no callsign is given then show the information for yourself.
4580 <sect1>show/sun [ndays] [<prefix>|<callsign>] (0)
4584 <bf>show/sun [ndays] [<prefix>|<callsign>]</bf> Show sun rise and set times
4588 Show the sun rise and set times for a (list of) prefixes or callsigns,
4589 together with the azimuth and elevation of the sun currently at those
4592 If you don't specify any prefixes or callsigns, it will show the times for
4593 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
4594 together with the current azimuth and elevation.
4596 If all else fails it will show the sunrise and set times for the node
4597 that you are connected to.
4603 SH/SUN G1TLH K9CW ZS
4606 You can also use this command to see into the past or the future, so
4607 if you want to see yesterday's times then do:-
4613 or in three days time:-
4619 Upto 366 days can be checked both in the past and in the future.
4621 Please note that the rise and set times are given as the UT times of rise
4622 and set on the requested UT day.
4623 <sect1>show/time [<prefix>|<callsign>] (0)
4627 <bf>show/time [<prefix>|<callsign>]</bf> Show the local time
4631 If no prefixes or callsigns are given then this command returns the local
4632 time and UTC as the computer has it right now. If you give some prefixes
4633 then it will show UTC and UTC + the local offset (not including DST) at
4634 the prefixes or callsigns that you specify.
4635 <sect1>show/usdb [call ..] (0)
4639 <bf>show/usdb [call ..]</bf> Show information held on the FCC Call database
4643 Show the City and State of a Callsign held on the FCC database if
4644 his is being run on this system, eg:-
4650 <sect1>show/vhfstats [days] [date] (0)
4654 <bf>show/vhfstats [days] [date]</bf> Show the VHF DX Statistics
4658 Show the VHF DX spots breakdown by band for the last
4659 <days> no of days (default is 31), starting from a date (default: today).
4660 <sect1>show/vhftable [days] [date] [prefix ...] (0)
4664 <bf>show/vhftable [days] [date] [prefix ...]</bf> Show the VHF DX Spotter Table
4668 Show the VHF DX Spotter table for the list of prefixes for the last
4669 <days> no of days (default is 31), starting from a date (default: today).
4671 If there are no prefixes then it will show the table for your country.
4673 Remember that some countries have more than one "DXCC country" in them
4674 (eg G :-), to show them (assuming you are not in G already which is
4675 specially treated in the code) you must list all the relevant prefixes
4678 sh/vhftable g gm gd gi gj gw gu
4681 Note that the prefixes are converted into country codes so you don't have
4682 to list all possible prefixes for each country.
4684 If you want more or less days than the default simply include the
4685 number you require:-
4691 If you want to start at a different day, simply add the date in some
4695 sh/vhftable 2 25nov02
4696 sh/vhftable 2 25-nov-02
4697 sh/vhftable 2 021125
4698 sh/vhftable 2 25/11/02
4701 This will show the stats for your DXCC for that CQWW contest weekend.
4703 You can specify either prefixes or full callsigns (so you can see how you
4704 did against all your mates). You can also say 'all' which will then print
4705 the worldwide statistics.
4715 <bf>show/wcy</bf> Show last 10 WCY broadcasts
4719 <sect1>show/wcy <n> (0)
4723 <bf>show/wcy <n></bf> Show last <n> WCY broadcasts
4727 Display the most recent WCY information that has been received by the system
4732 <bf>show/wwv</bf> Show last 10 WWV broadcasts
4736 <sect1>show/wwv <n> (0)
4740 <bf>show/wwv <n></bf> Show last <n> WWV broadcasts
4744 Display the most recent WWV information that has been received by the system
4749 <bf>shutdown</bf> Shutdown the cluster
4753 Shutdown the cluster and disconnect all the users
4754 <sect1>stat/channel [<callsign>] (5)
4758 <bf>stat/channel [<callsign>]</bf> Show the status of a channel on the cluster
4762 Show the internal status of the channel object either for the channel that
4763 you are on or else for the callsign that you asked for.
4765 Only the fields that are defined (in perl term) will be displayed.
4766 <sect1>stat/db <dbname> (5)
4770 <bf>stat/db <dbname></bf> Show the status of a database
4774 Show the internal status of a database descriptor.
4776 Depending on your privilege level you will see more or less information.
4777 This command is unlikely to be of much use to anyone other than a sysop.
4782 <bf>stat/msg</bf> Show the status of the message system
4786 <sect1>stat/msg <msgno> (1)
4790 <bf>stat/msg <msgno></bf> Show the status of a message
4794 This command shows the internal status of a message and includes information
4795 such as to whom it has been forwarded, its size, origin etc etc.
4797 If no message number is given then the status of the message system is
4799 <sect1>stat/route_node <callsign> (5)
4803 <bf>stat/route_node <callsign></bf> Show the data in a Route::Node object
4807 <sect1>stat/route_node all (5)
4811 <bf>stat/route_node all</bf> Show list of all Route::Node objects
4815 <sect1>stat/route_user <callsign> (5)
4819 <bf>stat/route_user <callsign></bf> Show the data in a Route::User object
4823 <sect1>stat/route_user all (5)
4827 <bf>stat/route_user all</bf> Show list of all Route::User objects
4831 <sect1>stat/user [<callsign>] (5)
4835 <bf>stat/user [<callsign>]</bf> Show the full status of a user
4839 Shows the full contents of a user record including all the secret flags
4842 Only the fields that are defined (in perl term) will be displayed.
4847 <bf>sysop</bf> Regain your privileges if you login remotely
4851 The system automatically reduces your privilege level to that of a
4852 normal user if you login in remotely. This command allows you to
4853 regain your normal privilege level. It uses the normal system: five
4854 numbers are returned that are indexes into the character array that is
4855 your assigned password (see SET/PASSWORD). The indexes start from
4858 You are expected to return a string which contains the characters
4859 required in the correct order. You may intersperse those characters
4860 with others to obscure your reply for any watchers. For example (and
4861 these values are for explanation :-):
4864 password = 012345678901234567890123456789
4870 aa2bbbb0ccc5ddd7xxx3n
4875 They will all match. If there is no password you will still be offered
4876 numbers but nothing will happen when you input a string. Any match is
4878 <sect1>talk <call> > <node> [<text>] (0)
4882 <bf>talk <call> > <node> [<text>]</bf> Send a text message to another station via a node
4886 Send a short message to any other station that is visible on the cluster
4887 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
4888 command, they don't have to be connected locally.
4890 The second form of TALK is used when other cluster nodes are connected
4891 with restricted information. This usually means that they don't send
4892 the user information usually associated with logging on and off the cluster.
4894 If you know that G3JNB is likely to be present on GB7TLH, but you can only
4895 see GB7TLH in the SH/C list but with no users, then you would use the
4896 second form of the talk message.
4898 If you want to have a ragchew with someone you can leave the text message
4899 out and the system will go into 'Talk' mode. What this means is that a
4900 short message is sent to the recipient telling them that you are in a
4901 'Talking' frame of mind and then you just type - everything you send will
4902 go to the station that you asked for.
4904 All the usual announcements, spots and so on will still come out on your
4907 If you want to do something (such as send a spot) you preceed the normal
4908 command with a '/' character, eg:-
4911 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
4915 To leave talk mode type:
4921 If you are in 'Talk' mode, there is an extention to the '/' command which
4922 allows you to send the output to all the people you are talking to. You do
4923 with the '//' command. For example:-
4929 will send the hftable as you have it to all the people you are currently
4931 <sect1>talk <call> [<text>] (0)
4935 <bf>talk <call> [<text>]</bf> Send a text message to another station
4939 <sect1>type <filearea>/<name> (0)
4943 <bf>type <filearea>/<name></bf> Look at the contents of a file in one of the fileareas
4947 Type out the contents of a file in a filearea. So, for example, in
4948 filearea 'bulletins' you want to look at file 'arld051' you would
4951 TYPE bulletins/arld051
4954 See also SHOW/FILES to see what fileareas are available and a
4956 <sect1>uncatchup <node call> all|[msgno> ...] (5)
4960 <bf>uncatchup <node call> all|[msgno> ...]</bf> Unmark a message as sent
4964 When you send messages the fact that you have forwarded it to another node
4965 is remembered so that it isn't sent again. When you have a new partner
4966 node and you add their callsign to your /spider/msg/forward.pl file, all
4967 outstanding non-private messages will be forwarded to them. This may well
4968 be ALL the non-private messages. You can prevent this by using these
4973 catchup GB7DJK 300 301 302 303 500-510
4976 and to undo what you have just done:-
4979 uncatchup GB7DJK all
4980 uncatchup GB7DJK 300 301 302 303 500-510
4983 which will arrange for them to be forward candidates again.
4985 Order is not important.
4986 <sect1>unset/announce (0)
4990 <bf>unset/announce</bf> Stop announce messages coming out on your terminal
4994 <sect1>unset/anntalk (0)
4998 <bf>unset/anntalk</bf> Stop talk like announce messages on your terminal
5002 The announce system on legacy cluster nodes is used as a talk
5003 substitute because the network is so poorly connected. If you:
5009 you will suppress several of these announces, you may miss the odd
5010 useful one as well, but you would probably miss them anyway in the
5011 welter of useless ones.
5017 allows you to see them again. This is the default.
5018 <sect1>unset/baddx <call>.. (8)
5022 <bf>unset/baddx <call>..</bf> Propagate a dx spot with this callsign again
5026 Setting a word as 'baddx' will prevent spots with that word in the
5027 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
5028 further. They will not be displayed and they will not be sent onto
5031 The word must be written in full, no wild cards are allowed eg:-
5034 set/baddx FORSALE VIDEO FR0G
5037 To allow a word again, use the following command ...
5043 <sect1>unset/badnode <call>.. (8)
5047 <bf>unset/badnode <call>..</bf> Allow spots from this node again
5051 Setting a callsign as a 'badnode' will prevent spots from that node
5052 going any further. They will not be displayed and they will not be
5053 sent onto other nodes.
5055 The call must be a full eg:-
5061 will stop anything from K1TTT. If you want SSIDs as well then you must
5062 enter them specifically.
5068 will allow spots from him again.
5070 Use with extreme care. This command may well be superceeded by FILTERing.
5071 <sect1>unset/badspotter <call>.. (8)
5075 <bf>unset/badspotter <call>..</bf> Allow spots from this callsign again
5079 Setting a callsign as a 'badspotter' will prevent spots from this callsign
5080 going any further. They will not be displayed and they will not be
5081 sent onto other nodes.
5083 The call must be written in full, no wild cards are allowed eg:-
5086 set/badspotter VE2STN
5089 will stop anything from VE2STN. This command will automatically
5090 stop spots from this user, regardless of whether or which SSID
5091 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
5095 unset/badspotter VE2STN
5098 will allow spots from him again.
5100 Use with extreme care. This command may well be superceded by FILTERing.
5101 <sect1>unset/badword <word>.. (8)
5105 <bf>unset/badword <word>..</bf> Propagate things with this word again
5109 Setting a word as a 'badword' will prevent things like spots,
5110 announces or talks with this word in the the text part from going any
5111 further. They will not be displayed and they will not be sent onto
5114 The word must be written in full, no wild cards are allowed eg:-
5117 set/badword annihilate annihilated annihilation
5120 will stop anything with these words in the text.
5123 unset/badword annihilated
5126 will allow text with this word again.
5127 <sect1>unset/beep (0)
5131 <bf>unset/beep</bf> Stop beeps for DX and other messages on your terminal
5139 <bf>unset/dx</bf> Stop DX messages coming out on your terminal
5143 <sect1>unset/dxgrid (0)
5147 <bf>unset/dxgrid</bf> Stop QRA Grid Squares on the end of DX announcements
5151 A standard feature which is enabled in version 1.43 and above is
5152 that if the spotter's grid square is known it is output on the end
5153 of a DX announcement (there is just enough room). Some user programs
5154 cannot cope with this. You can use this command to reset (or set)
5156 <sect1>unset/echo (0)
5160 <bf>unset/echo</bf> Stop the cluster echoing your input
5164 If you are connected via a telnet session, different implimentations
5165 of telnet handle echo differently depending on whether you are
5166 connected via port 23 or some other port. You can use this command
5167 to change the setting appropriately.
5169 The setting is stored in your user profile.
5171 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
5172 <sect1>unset/email (0)
5176 <bf>unset/email</bf> Stop personal msgs being forwarded by email
5180 If any personal messages come in for your callsign then you can use
5181 these commands to control whether they are forwarded onto your email
5182 address. To enable the forwarding do something like:-
5185 SET/EMAIL mike.tubby@somewhere.com
5188 You can have more than one email address (each one separated by a space).
5189 Emails are forwarded to all the email addresses you specify.
5191 You can disable forwarding by:-
5197 <sect1>unset/here (0)
5201 <bf>unset/here</bf> Tell the system you are absent from your terminal
5205 <sect1>unset/hops <call> ann|spots|route|wwv|wcy (8)
5209 <bf>unset/hops <call> ann|spots|route|wwv|wcy</bf> Unset hop count
5213 Set the hop count for a particular type of broadcast for a node.
5215 This command allows you to set up special hop counts for a node
5216 for currently: announce, spots, wwv and wcy broadcasts.
5220 set/hops gb7djk ann 10
5221 set/hops gb7mbc spots 20
5224 Set SHOW/HOPS for information on what is already set. This command
5225 creates a filter and works in conjunction with the filter system.
5227 You can unset the hops with command UNSET/HOPS. For example:-
5230 unset/hops gb7djk ann
5231 unset/hops gb7mbc spots
5234 <sect1>unset/logininfo (0)
5238 <bf>unset/logininfo</bf> Inform when a station logs out locally
5242 <sect1>unset/privilege (0)
5246 <bf>unset/privilege</bf> Remove any privilege for this session
5250 You can use this command to 'protect' this session from unauthorised
5251 use. If you want to get your normal privilege back you will need to
5252 either logout and login again (if you are on a console) or use the
5254 <sect1>unset/prompt (0)
5258 <bf>unset/prompt</bf> Set your prompt back to default
5262 This command will set your user prompt to exactly the string that you
5263 say. The point of this command to enable a user to interface to programs
5264 that are looking for a specific prompt (or else you just want a different
5271 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
5273 <sect1>unset/talk (0)
5277 <bf>unset/talk</bf> Stop TALK messages coming out on your terminal
5281 <sect1>unset/wcy (0)
5285 <bf>unset/wcy</bf> Stop WCY messages coming out on your terminal
5289 <sect1>unset/wwv (0)
5293 <bf>unset/wwv</bf> Stop WWV messages coming out on your terminal
5301 <bf>unset/wx</bf> Stop WX messages coming out on your terminal
5309 <bf>who</bf> Show who is physically connected
5313 This is a quick listing that shows which callsigns are connected and
5314 what sort of connection they have
5315 <sect1>wx <text> (0)
5319 <bf>wx <text></bf> Send a weather message to local users
5323 <sect1>wx full <text> (0)
5327 <bf>wx full <text></bf> Send a weather message to all cluster users
5331 <sect1>wx sysop <text> (5)
5335 <bf>wx sysop <text></bf> Send a weather message to other clusters only
5339 Weather messages can sometimes be useful if you are experiencing an extreme
5340 that may indicate enhanced conditions
projects / spider.git / blob