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>April 2003 revision 0.7</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 <sect1>A DXSpider Filtering Tutorial
\r
590 There is now an excellent primer/tutorial on filtering written by Jim
\r
591 Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
\r
592 suggest you read. You can read it here
\r
593 <htmlurl url="filtering_en.html" name="The DXSpider User Filtering Primer">
\r
595 <sect>Other filters
\r
597 <sect1>Filtering Mail
\r
600 In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
\r
601 this to badmsg.pl and edit the file. The original looks something like this ....
\r
605 # the list of regexes for messages that we won't store having
\r
606 # received them (bear in mind that we must receive them fully before
\r
610 # The format of each line is as follows
\r
612 # type source pattern
\r
613 # P/B/F T/F/O/S regex
\r
615 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
\r
616 # source: T - to field, F - from field, O - origin, S - subject
\r
617 # pattern: a perl regex on the field requested
\r
619 # Currently only type B and P msgs are affected by this code.
\r
621 # The list is read from the top down, the first pattern that matches
\r
622 # causes the action to be taken.
\r
624 # The pattern can be undef or 0 in which case it will always be selected
\r
625 # for the action specified
\r
633 'B', 'T', 'WANTED',
\r
634 'B', 'S', 'WANTED',
\r
643 I think this is fairly self explanatory. It is simply a list of subject
\r
644 headers that we do not want to pass on to either the users of the cluster or
\r
645 the other cluster nodes that we are linked to. This is usually because of
\r
646 rules and regulations pertaining to items for sale etc in a particular country.
\r
649 <sect1>Filtering words from text fields in Announce, Talk and DX spots
\r
652 From version 1.48 onwards the interface to this has changed. You can now
\r
653 use the commands <em>set/badword</em> to add words that you are not prepared
\r
654 to see on the cluster, <em>unset/badword</em> to allow that word again and
\r
655 <em>show/badword</em> to list the words that you have set.
\r
658 If you have a previous <em>/spider/data/badwords</em>, the first time you start
\r
659 the node, it will read and convert this file to the new commands. The old style
\r
660 file will then be removed.
\r
662 <sect1>Stopping (possibly bad) DX Spots from Nodes or Spotters
\r
665 There are a number of commands that control whether a spot progresses
\r
666 any further by regarding it as "bad" in some way.
\r
669 A DX Spot has a number of fields which can be checked to see whether they
\r
670 contain "bad" values, they are: the DX callsign itself, the Spotter and
\r
671 the Originating Node.
\r
674 There are a set of commands which allow the sysop to control whether a
\r
683 These work in the same as the <em>set/badword</em> command, you can add
\r
684 any words or callsigns or whatever to the appropriate database. For
\r
685 example, to stop a spot from a particular node you do:
\r
688 set/badnode gb7djk gb7dxc
\r
694 set/badspotter b0mb p1rat nocall
\r
700 set/baddx video wsjt
\r
703 You can remove a word using the appropriate unset command
\r
704 (<em>unset/baddx, unset/badspotter, unset/badnode</em>) or list them
\r
705 using one of <em>show/baddx, show/badspotter</em> and
\r
706 <em>show/badnode</em>.
\r
711 DXSpider deals seamlessly with standard AK1A type mail. It supports both
\r
712 personal and bulletin mail and the sysop has additional commands to ensure
\r
713 that mail gets to where it is meant. DXSpider will send mail almost
\r
714 immediately, assuming that the target is on line. However, only one
\r
715 mail message is dealt with at any one time. If a mail message is already
\r
716 being sent or recieved, then the new message will be queued until it has
\r
719 The cluster mail is automatically deleted after 30 days unless the sysop
\r
720 sets the "keep" flag using the <em>msg</em> command.
\r
722 <sect1>Personal mail
\r
725 Personal mail is sent using the <em>sp</em> command. This is actually the
\r
726 default method of sending mail and so a simple <em>s</em> for send will do.
\r
727 A full list of the send commands and options is in the <em>command set</em>
\r
728 section, so I will not duplicate them here.
\r
730 <sect1>Bulletin mail
\r
733 Bulletin mail is sent by using the <em>sb</em> command. This is one of the
\r
734 most common mistakes users make when sending mail. They send a bulletin
\r
735 mail with <em>s</em> or <em>sp</em> instead of <em>sb</em> and of course
\r
736 the message never leaves the cluster. This can be rectified by the sysop
\r
737 by using the <em>msg</em> command.
\r
739 <P>Bulletin addresses can be set using the Forward.pl file.
\r
744 DXSpider receives all and any mail sent to it without any alterations needed
\r
745 in files. Because personal and bulletin mail are treated differently, there
\r
746 is no need for a list of accepted bulletin addresses. It is necessary, however,
\r
747 to tell the program which links accept which bulletins. For example, it is
\r
748 pointless sending bulletins addresses to "UK" to any links other than UK
\r
749 ones. The file that does this is called forward.pl and lives in /spider/msg.
\r
750 At default, like other spider files it is named forward.pl.issue. Rename it
\r
751 to forward.pl and edit the file to match your requirements.
\r
752 The format is below ...
\r
756 # this is an example message forwarding file for the system
\r
758 # The format of each line is as follows
\r
760 # type to/from/at pattern action destinations
\r
761 # P/B/F T/F/A regex I/F [ call [, call ...] ]
\r
763 # type: P - private, B - bulletin (msg), F - file (ak1a bull)
\r
764 # to/from/at: T - to field, F - from field, A - home bbs, O - origin
\r
765 # pattern: a perl regex on the field requested
\r
766 # action: I - ignore, F - forward
\r
767 # destinations: a reference to an array containing node callsigns
\r
769 # if it is non-private and isn't in here then it won't get forwarded
\r
771 # Currently only type B msgs are affected by this code.
\r
773 # The list is read from the top down, the first pattern that matches
\r
774 # causes the action to be taken.
\r
776 # The pattern can be undef or 0 in which case it will always be selected
\r
777 # for the action specified
\r
779 # If the BBS list is undef or 0 and the action is 'F' (and it matches the
\r
780 # pattern) then it will always be forwarded to every node that doesn't have
\r
781 # it (I strongly recommend you don't use this unless you REALLY mean it, if
\r
782 # you allow a new link with this on EVERY bull will be forwarded immediately
\r
783 # on first connection)
\r
789 'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
\r
790 'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
791 'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
\r
792 'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
793 'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
794 'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
795 'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
796 'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
797 'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
798 'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
\r
799 'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
\r
803 Simply insert a bulletin address and state in the brackets where you wish
\r
804 that mail to go. For example, you can see here that mail sent to "UK" will
\r
805 only be sent to the UK links and not to PA4AB-14.
\r
808 To force the cluster to reread the file use load/forward
\r
811 NB: If a user tries to send mail to a bulletin address that does not exist
\r
812 in this file, they will get an error.
\r
814 <sect1>The msg command
\r
817 The <em>msg</em> command is a very powerful and flexible tool for the
\r
818 sysop. It allows the sysop to alter to and from fields and make other
\r
819 changes to manage the cluster mail.
\r
821 Here is a full list of the various options ...
\r
824 MSG TO <msgno> <call> - change TO callsign to <call>
\r
825 MSG FRom <msgno> <call> - change FROM callsign to <call>
\r
826 MSG PRrivate <msgno> - set private flag
\r
827 MSG NOPRrivate <msgno> - unset private flag
\r
828 MSG RR <msgno> - set RR flag
\r
829 MSG NORR <msgno> - unset RR flag
\r
830 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
\r
831 MSG NOKEep <msgno> - unset the keep flag
\r
832 MSG SUbject <msgno> <new> - change the subject to <new>
\r
833 MSG WAittime <msgno> - remove any waiting time for this message
\r
834 MSG NOREad <msgno> - mark message as unread
\r
835 MSG REad <msgno> - mark message as read
\r
836 MSG QUeue - queue any outstanding bulletins
\r
837 MSG QUeue 1 - queue any outstanding private messages
\r
840 These commands are simply typed from within the cluster as the sysop user.
\r
842 <sect1>Message status
\r
845 You can check on a message from within the cluster by using the command
\r
846 <em>stat/msg</em>. This will give you additional information on the
\r
847 message number including which nodes have received it, which node it
\r
848 was received from and when etc. Here is an example of the output of
\r
852 G0VGS de GB7MBC 28-Jan-2001 1308Z >
\r
855 Msg Time: 26-Jan-2001 1302Z
\r
859 Subject: AMSAT 2line KEPS 01025.AMSAT
\r
861 Got it Nodes: GB7BAA, GB7ADX
\r
865 G0VGS de GB7MBC 28-Jan-2001 1308Z >
\r
868 <sect1>Filtering mail
\r
871 This is described in the section on <em>Other filters</em> so I will not
\r
874 <sect1>Distribution lists
\r
877 Distribution lists are simply a list of users to send certain types of
\r
878 mail to. An example of this is mail you only wish to send to other
\r
879 sysops. In /spider/msg there is a directory called <em>distro</em>. You
\r
880 put any distibution lists in here. For example, here is a file called
\r
881 SYSOP.pl that caters for the UK sysops.
\r
884 qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
\r
885 GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
\r
886 GB7DXK GB7DXI GB7DXS)
\r
889 Any mail sent to "sysop" would only be sent to the callsigns in this list.
\r
891 <sect1>BBS interface
\r
894 Spider provides a simple BBS interface. No input is required from the sysop
\r
895 of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
\r
896 any required mail to the cluster. No mail can flow from Spider to the BBS,
\r
897 the interface is one-way.
\r
900 Please be careful not to flood the cluster network with unnecessary mail.
\r
901 Make sure you only send mail to the clusters that want it by using the
\r
902 Forward.pl file very carefully.
\r
907 From 1.48 onwards it will become increasingly possible to control DXSpider's
\r
908 operation with scripts of various kinds.
\r
911 The directory /spider/scripts is where it all happens and is used for several
\r
912 things. Firstly it contains a file called startup that can be used to call
\r
913 in any changes to the cluster from the default settings on startup. This
\r
914 script is executed immediately after all initialisation of the node is done
\r
915 but before any connections are possible. Examples of this include how many
\r
916 spots it is possible to get with the sh/dx command, whether you want
\r
917 registration/passwords to be permanently on etc. An example file is shown
\r
918 below and is included in the distribution as startup.issue.
\r
922 # startup script example
\r
924 # set maximum no of spots allowed to 100
\r
925 # set/var $Spot::maxspots = 100
\r
927 # Set registration on
\r
928 # set/var $main::reqreg = 1
\r
931 # set/var $main::passwdreq = 1
\r
936 As usual, any text behind a # is treated as a comment and not read. To use
\r
937 this file, simply rename it from startup.issue to startup. In our example
\r
938 above there are three options. The first option is the amount of spots that
\r
939 a user can request with the <em>sh/dx</em> command. Normally the default is
\r
940 to give 10 spots unless the user specifies more. Without this line enabled,
\r
941 the maximum a user can request is 100 spots. Depending on your link quality
\r
942 you may wish to enable more or less by specifying the number.
\r
945 The other 2 options are dealt with more fully in the security section.
\r
948 Secondly, it is used to store the login scripts for users and nodes. Currently
\r
949 this can only be done by the sysop but it is envisaged that eventually users will
\r
950 be able to set their own. An example is included in the distibution but here is
\r
966 The lines in between commands can simply insert a blank line or a character
\r
967 such as a + sign to make the output easier to read. Simply create this script
\r
968 with your favourite editor and save it with the callsign of the user as the
\r
969 filename. Filenames should always be in lower case.
\r
972 Commands can be inserted in the same way for nodes. A node may wish a series
\r
973 of commands to be issued on login, such as a merge command for example.
\r
976 Thirdly, there are 2 default scripts for users and nodes who do not have a
\r
977 specifically defined script. These are <em>user_default</em> and
\r
978 <em>node_default</em>
\r
983 Spider allows the creation of local or remote databases. It supports
\r
984 chained databases, allowing several different databases to be scanned
\r
985 with one simple command. Importing of databases is limited at present
\r
986 to the standard AK1A databases such as OBLAST and the DB0SDX QSL
\r
987 database but will expand with time.
\r
989 <sect1>Creating databases
\r
992 Creating a database could not be more simple. All the commands are
\r
993 sent from the cluster prompt as the <em>sysop</em> user.
\r
995 To create a database you use the command <em>dbcreate</em>. It can
\r
996 be used in 3 different ways like so ..
\r
1002 To simply create a database locally, you just tell the command the
\r
1003 name of the database. This does not create the actual database, it
\r
1004 simply defines it to say that it exists.
\r
1007 dbcreate <name> chain <name> [<name>...]
\r
1010 This creates a chained database entry. The first database will be
\r
1011 scanned, then the second, the third etc...
\r
1014 dbcreate <name> remote <name>
\r
1017 This creates a remote entry. the first name field is the database
\r
1018 name at the remote node, then the remote switch, then the actual
\r
1019 node_call of the remote node, for example...
\r
1022 dbcreate buckmaster remote gb7dxc
\r
1025 Remote databases cannot be chained, however, the last database in a
\r
1026 chain can be a remote database.
\r
1028 <sect1>Importing databases
\r
1031 The only databases that Spider can currently import are the standard
\r
1032 AK1A databases such as OBLAST or the DB0SDX qsl and address database.
\r
1033 This will be added to with time.
\r
1035 To import such a database, first put the file somewhere useful like /tmp
\r
1036 and then issue the following command ...
\r
1039 dbimport oblast /tmp/OBLAST.FUL
\r
1042 This will update the existing local oblast database or create it if
\r
1043 it does not exist.
\r
1045 <sect1>Checking available databases
\r
1048 Once a database is created, you will want to check that it has been
\r
1049 added. To do this use the <em>dbavail</em> command. This will
\r
1050 output the available databases. For example ...
\r
1054 DB Name Location Chain
\r
1058 G0VGS de GB7MBC 3-Feb-2001 1925Z >
\r
1061 <sect1>Looking up databases
\r
1064 To look for information in a defined database, simply use the <em>dbshow</em>
\r
1065 command, for example ...
\r
1068 dbshow buckmaster G0YLM
\r
1071 will show the information for the callsign G0YLM from the buckmaster
\r
1072 database if it exists. To make things more standard for the users
\r
1073 you can add an entry in the Aliases file so that it looks like a standard
\r
1074 <em>show</em> command like this ...
\r
1077 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
\r
1080 Now you can simply use show/buckmaster or an abreviation.
\r
1082 <sect1>Removing databases
\r
1085 To delete an existing database you use the <em>dbremove</em> command.
\r
1092 would remove the oblast database and its associated datafile from the
\r
1093 system. There are no warnings or recovery possible from this command.
\r
1094 If you remove a database it ceases to exist and would have to be created
\r
1095 from scratch if you still required it.
\r
1097 <sect>Information, files and useful programs
\r
1102 One of the more important things a cluster sysop needs to do is to get
\r
1103 information to his users. The simplest way to do this is to have a banner
\r
1104 that is sent to the user on login. This is know as a "message of the day"
\r
1105 or "motd". To set this up, simply create a file in /spider/data called motd
\r
1106 and edit it to say whatever you want. It is purely a text file and will be
\r
1107 sent automatically to anyone logging in to the cluster.
\r
1112 This message of the day file lives in the same directory as the standard
\r
1113 motd file but is only sent to non-registered users. Once registered they
\r
1114 will receive the same message as any other user.
\r
1116 <sect1>Downtime message
\r
1119 If for any reason the cluster is down, maybe for upgrade or maintenance but
\r
1120 the machine is still running, a message can be sent to the user advising them
\r
1121 of the fact. This message lives in the /spider/data directory and is called
\r
1122 "offline". Simply create the file and edit it to say whatever you wish.
\r
1123 This file will be sent to a user attempting to log into the cluster when
\r
1124 DXSpider is not actually running.
\r
1126 <sect1>Other text messages
\r
1129 You can set other text messages to be read by the user if they input the file
\r
1130 name. This could be for news items or maybe information for new users.
\r
1131 To set this up, make a directory under /spider called <em>packclus</em>.
\r
1132 Under this directory you can create files called <em>news</em> or <em>newuser</em>
\r
1133 for example. In fact you can create files with any names you like. These can
\r
1134 be listed by the user with the command ....
\r
1140 They can be read by the user by typing the command ....
\r
1146 If the file they want to read is called <em>news</em>. You could also set
\r
1147 an alias for this in the Alias file to allow them just to type <em>news</em>
\r
1150 You can also store other information in this directory, either directly or
\r
1151 nested under directories. One use for this would be to store DX bulletins
\r
1152 such as the OPDX bulletins. These can be listed and read by the user.
\r
1153 To keep things tidy, make a directory under /spider/packclus called
\r
1154 <em>bulletin</em>. Now copy any OPDX or similar bulletins into it. These
\r
1155 can be listed by the user in the same way as above using the <em>show/files</em>
\r
1156 command with an extension for the bulletin directory you have just created,
\r
1160 show/files bulletin
\r
1164 An example would look like this ....
\r
1168 bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
\r
1171 You can see that in the files area (basically the packclus directory) there is a
\r
1172 file called <em>news</em> and a directory called <em>bulletin</em>. You can
\r
1173 also see that dates they were created. In the case of the file <em>news</em>,
\r
1174 you can also see the time it was last modified, a good clue as to whether the
\r
1175 file has been updated since you last read it. To read the file called
\r
1176 <em>news</em> you would simply issue the command ....
\r
1182 To look what is in the bulletin directory you issue the command ....
\r
1185 show/files bulletin
\r
1186 opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
\r
1187 opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
\r
1188 opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
\r
1189 opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
\r
1190 opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
\r
1191 opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
\r
1192 opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
\r
1193 opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
\r
1194 opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
\r
1195 opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
\r
1196 opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
\r
1197 opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
\r
1198 opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
\r
1199 Press Enter to continue, A to abort (16 lines) >
\r
1202 You can now read any file in this directory using the type command, like this ....
\r
1205 type bulletin/opdx391
\r
1206 Ohio/Penn DX Bulletin No. 391
\r
1207 The Ohio/Penn Dx PacketCluster
\r
1208 DX Bulletin No. 391
\r
1211 Editor Tedd Mirgliotta, KB8NW
\r
1212 Provided by BARF-80 BBS Cleveland, Ohio
\r
1213 Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
\r
1214 Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
\r
1215 Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
\r
1216 & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
\r
1217 Press Enter to continue, A to abort (508 lines) >
\r
1220 The page length will of course depend on what you have it set to!
\r
1222 <sect1>The Aliases file
\r
1225 You will find a file in /spider/cmd/ called Aliases. This is the file that
\r
1226 controls what a user gets when issuing a command. It is also possible to
\r
1227 create your own aliases for databases and files you create locally.
\r
1230 You should not alter the original file in /spider/cmd/ but create a new file
\r
1231 with the same name in /spider/local_cmd. This means that any new Aliases files
\r
1232 that is downloaded will not overwrite your self created Aliases and also that
\r
1233 you do not override any new Aliases with your copy in /spider/local_cmd/. You
\r
1234 must remember that any files you store in /spider/local/ or /spider/local_cmd
\r
1235 override the originals if the same lines are used in both files.
\r
1238 The best way of dealing with all this then is to only put your own locally
\r
1239 created Aliases in the copy in /spider/local_cmd. The example below is
\r
1240 currently in use at GB7MBC.
\r
1245 # Local Aliases File
\r
1252 '^news$', 'type news', 'type',
\r
1255 '^sh\w*/buck$', 'show/qrz', 'show',
\r
1256 '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
\r
1257 '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
\r
1258 '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
\r
1259 '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
\r
1266 Each alphabetical section should be preceded by the initial letter and the section
\r
1267 should be wrapped in square brackets as you can see. The syntax is straightforward.
\r
1268 The first section on each line is the new command that will be allowed once the
\r
1269 alias is included. The second section is the command it is replacing and the last
\r
1270 section is the actual command that is being used.
\r
1273 The eagle-eyed amongst you will have noticed that in the first section, the new
\r
1274 alias command has a '^' at the start and a '$' at the end. Basically these force
\r
1275 a perfect match on the alias. The '^' says match the beginning exactly and the
\r
1276 '$' says match the end exactly. This prevents unwanted and unintentional matches
\r
1277 with similar commands.
\r
1280 I have 3 different types of alias in this file. At the top is an alias for 'news'.
\r
1281 This is a file I have created in the /spider/packclus/ directory where I can inform
\r
1282 users of new developments or points of interest. In it's initial form a user would
\r
1283 have to use the command <em>type news</em>. The alias allows them to simply type
\r
1284 <em>news</em> to get the info. Second is an alias for the <em>show/qrz</em>
\r
1285 command so that those users used to the original <em>show/buck</em> command in
\r
1286 AK1A will not get an error, and the rest of the lines are for locally created
\r
1287 databases so that a user can type <em>show/hftest</em> instead of having to use
\r
1288 the command <em>dbshow hftest</em> which is not as intuitive.
\r
1291 This file is just an example and you should edit it to your own requirements.
\r
1292 Once created, simply issue the command <em>load/alias</em> at the cluster
\r
1293 prompt as the sysop user and the aliases should be available.
\r
1299 In later versions of Spider a simple console program is provided for the sysop.
\r
1300 This has a type ahead buffer with line editing facilities and colour for spots,
\r
1301 announces etc. To use this program, simply use console.pl instead of client.
\r
1304 To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
\r
1305 file with your favourite editor.
\r
1307 <sect1>Updating kepler data
\r
1310 Spider has a powerful and flexible show/satellite command. In order for
\r
1311 this to be accurate, the kepler data has to be updated regularly. In
\r
1312 general, this data is available as an email or via cluster mail.
\r
1313 Updating it is simple. First you need to export the mail message as a
\r
1314 file. You do this with the <em>export</em> command from the cluster prompt
\r
1315 as the sysop. For example ...
\r
1318 export 5467 /spider/perl/keps.in
\r
1322 would export message number 5467 as a file called keps.in in the
\r
1323 /spider/perl directory.
\r
1326 Now login to a VT as sysop and cd /spider/perl. There is a command in
\r
1327 the perl directory called <em>convkeps.pl</em>. All we need to do now is
\r
1328 convert the file like so ...
\r
1331 ./convkeps.pl keps.in
\r
1335 Now go back to the cluster and issue the command ...
\r
1342 That is it! the kepler data has been updated.
\r
1344 <sect1>The QRZ callbook
\r
1347 The command <em>sh/qrz</em> will only work once you have followed a few
\r
1348 simple steps. First you need to get a user ID and password from qrz.com.
\r
1349 Simply go to the site and create one. Secondly you need to copy the file
\r
1350 /spider/perl/Internet.pm to /spider/local and alter it to match your user
\r
1351 ID and password. You also at this point need to set $allow=1 to complete
\r
1352 the setup. Many thanks to Fred Lloyd, the proprieter of
\r
1353 <htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
\r
1355 <sect1>Connecting logging programs
\r
1358 There appear to be very few logging programs out there that support telnet
\r
1359 especially the popular ones like LogEQF, Turbolog etc. This can make it
\r
1360 difficult to connect to your own cluster!
\r
1361 The way to do it is to make the logging program think it has a TNC attached
\r
1362 to a com port on the logging PC and 'push' a linux login out to it.
\r
1363 This is achieved very simply by the use of <em>agetty</em>.
\r
1366 All that is required is to add a line in /etc/inittab to have the client
\r
1367 ready for a connection on the com port of your choice. Remember that in
\r
1368 Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.
\r
1371 c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
\r
1375 Add this after the standard runlevel lines in /etc/inittab. The above
\r
1376 line works on ttyS1 (com2). Now as root, issue the command <em>telinit q</em>
\r
1377 and it should be ready for connection. All that is required is a 3 wire
\r
1378 serial lead (tx, rx and signal ground). Tell you logging program to use
\r
1379 8n1 at 9600 baud and you should see a Linux login prompt. Login as normal
\r
1380 and then telnet from there to the cluster.
\r
1382 <sect>Java Web applet
\r
1385 In the spider tree will be a directory <em>spider-web</em>. This is a
\r
1386 neat little java web applet that can be run from a website. The applet
\r
1387 must run on the same machine as the cluster. The included README file is
\r
1391 I should comment here that the applet is precompiled, that is, ready to go.
\r
1392 It was compiled using JDK1.3.1. If your version is earlier than this then it
\r
1393 may not work. Should that be the case you need to recompile or update your
\r
1394 JDK. To recompile do the following ...
\r
1397 cd /spider/spider-web
\r
1399 /usr/bin/javac spiderclient.java
\r
1403 I have used /usr/bin/javac as an example, your path to javac may be different.
\r
1408 Completely based on a clx web client written in Java by dl6dbh
\r
1409 (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
\r
1411 The webserver has to run on the same machine as your DxSpider software!
\r
1413 It is assumed that you have Java installed. You need JDK1.3.1 at least.
\r
1415 Installation instructions (Performed as root):
\r
1417 Put all the files in the spider-web directory into a newly created directory
\r
1418 under the DocumentRoot of your websever for instance 'client'. In my case
\r
1419 this is: /home/httpd/html/client/ although ymmv. For Suse the correct
\r
1420 path should be /usr/local/httpd/htdocs/client/ for example.
\r
1422 Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
\r
1423 /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
\r
1424 /usr/local/httpd/cgi-bin/ for example.
\r
1426 Change the permissions of the files to ensure they are correct, obviously you
\r
1427 will need to use the correct path the the files according to your system:
\r
1429 chmod 755 /home/httpd/html/cgi-bin/spider.cgi
\r
1430 chmod -R 755 /home/httpd/html/client/
\r
1432 By default the spider.cgi script should pick up your hostname (As long as this
\r
1433 is set correctly). If it does not or your hostname differs from the name that
\r
1434 you attach to the public address that you are using, then edit spider.cgi :
\r
1436 # Uncomment and set the hostname manually here if the above fails.
\r
1437 # $HOSTNAME = "gb7mbc.spoo.org" ;
\r
1440 'HOSTNAME' is the hostname of your cluster.
\r
1442 'PORT' is the portnumber that you use to connect to your DxSpider via
\r
1443 telnet (see Listeners.pm)
\r
1445 NOTE: If you can start the console but cannot connect to the cluster from it,
\r
1446 then it is possible that the machine you are on cannot resolve the hostname of
\r
1447 your cluster machine. If this is the case, you need to set your hostname
\r
1448 manually as above.
\r
1450 You also need to set the $NODECALL variable. This prints the name of your
\r
1451 choosing (probably your cluster callsign) on the html page.
\r
1453 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
\r
1456 <sect>Web based statistics
\r
1459 From version 1.50, you can use the freeware software MRTG to produce
\r
1460 really nice graphical statistics on your web site. For an example
\r
1461 try <htmlurl url="http://www.gb7mbc.net/mrtg/stats.html" name="http://www.gb7mbc.net/mrtg/stats.html">.
\r
1464 The following should help you get it all working.
\r
1467 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
1468 You will also need the following files..
\r
1471 libpng-1.0.14.tar.gz
\r
1476 Login to your machine as the root user, put all the downloaded files
\r
1477 in /usr/local/src/ (or wherever you prefer) and untar and compile them.
\r
1478 All the information to compile and install these sources come with them.
\r
1479 After compilation and installation, you will find MRTG in /usr/local/mrtg-2.
\r
1482 Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
\r
1483 /spider/html/mrtg/
\r
1486 You now need to make 2 symbolic links like below...
\r
1489 ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
\r
1490 ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
\r
1494 Now login to the cluster with your sysop callsign and run the command
\r
1497 <P>Now you are nearly there! Login as the sysop user and change to the
\r
1498 /spider/html/mrtg/ directory. Now run the command <em>indexmaker</em> as
\r
1502 indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
\r
1505 Changing the callsign for your own cluster callsign of course!
\r
1508 And finally you need to login as the root user and create one last
\r
1509 symbolic link. Where this points will depend on where your html
\r
1510 documents are kept. For RedHat systems you use...
\r
1513 ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
\r
1516 and for SuSE systems...
\r
1519 ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
\r
1522 If you now point your browser to your website as below it should all
\r
1526 http://www.xxx.xxx/mrtg/stats.html
\r
1529 Of course, to get the stats to update, you need to add some information
\r
1530 in the spider crontab file as below...
\r
1533 # Update stats for mrtg on website
\r
1534 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
\r
1537 This will update the site every 5 minutes.
\r
1542 From version 1.49 DXSpider has some additional security features. These
\r
1543 are not by any means meant to be exhaustive, however they do afford some
\r
1544 security against piracy. These two new features can be used independently
\r
1545 of each other or in concert to tighten the security.
\r
1547 <sect1>Registration
\r
1550 The basic principle of registration is simple. If a user is not registered
\r
1551 by the sysop, then they have read-only access to the cluster. The only
\r
1552 thing they can actually send is a talk or a message to the sysop. In
\r
1553 order for them to be able to spot, send announces or talks etc the sysop
\r
1554 must register them with the <em>set/register</em> command, like this ...
\r
1557 set/register g0vgs
\r
1560 The user g0vgs can now fully use the cluster. In order to enable
\r
1561 registration, you can issue the command ...
\r
1564 set/var $main::reqreg = 1
\r
1567 Any users that are not registered will now see the motd_nor file rather
\r
1568 than the motd file as discussed in the Information, files and useful
\r
1572 Entering this line at the prompt will only last for the time the cluster
\r
1573 is running of course and would not be present on a restart. To make the
\r
1574 change permanent, add the above line to /spider/scripts/startup. To
\r
1575 read more on the startup file, see the section on Information, files
\r
1576 and useful programs.
\r
1579 To unregister a user use <em>unset/register</em> and to show the list
\r
1580 of registered users, use the command <em>show/register</em>.
\r
1585 At the moment, passwords only affect users who login to a DXSpider
\r
1586 cluster node via telnet. If a user requires a password, they can
\r
1587 either set it themselves or have the sysop enter it for them by using
\r
1588 the <em>set/password</em> command. Any users who already have passwords,
\r
1589 such as remote sysops, will be asked for their passwords automatically
\r
1590 by the cluster. Using passwords in this way means that the user has a
\r
1591 choice on whether to have a password or not. To force the use of
\r
1592 passwords at login, issue the command ...
\r
1595 set/var $main::passwdreq = 1
\r
1598 at the cluster prompt. This can also be added to the /spider/scripts/startup
\r
1599 file as above to make the change permanent.
\r
1602 Of course, if you do this you will have to assign a password for each of
\r
1603 your users. If you were asking them to register, it is anticipated that
\r
1604 you would ask them to send you a message both to ask to be registered and
\r
1605 to give you the password they wish to use.
\r
1608 Should a user forget their password, it can be reset by the sysop by
\r
1609 first removing the existing password and then setting a new one like so ...
\r
1612 unset/password g0vgs
\r
1613 set/password g0vgs new_password
\r
1618 <sect1>CVS from a Linux platform
\r
1621 CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
\r
1622 at <htmlurl url="http://www.sourceforge.net" name="Sourceforge">. This means
\r
1623 that it is possible to update your DXSpider installation to the latest
\r
1624 sources by using a few simple commands. A graphical interface to CVS for
\r
1625 Windows is explained in the next section.
\r
1628 Please be aware that if you update your system using CVS, it is possible that
\r
1629 you could be running code that is very beta and not fully tested. There is
\r
1630 a possibility that it could be unstable.
\r
1633 I am of course assuming that you have a machine with both DXSpider and
\r
1634 Internet access running.
\r
1637 BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
\r
1638 ENTIRE SPIDER TREE!!
\r
1641 Assuming you are connected to the Internet, you need to login to the
\r
1642 CVS repository and then update your Spider source. There are several
\r
1643 steps which are listed below ...
\r
1646 First login as the user <em>sysop</em>. Next you need to connect to the CVS
\r
1647 repository. You do this with the command below ...
\r
1650 cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
\r
1653 You will get a password prompt. Simply hit return here and your machine should
\r
1654 return to a normal linux prompt.
\r
1657 What happens next depends on whether you have an existing installation that
\r
1658 you want to update with the latest and greatest or whether you just want
\r
1659 to see what is there and/or run it on a new machine for testing.
\r
1661 If you are installing Spider from CVS then change directory to /home/sysop
\r
1663 If you are wanting to update Spider then cd to /tmp
\r
1666 The next step will create a brand new 'spider' directory in your current
\r
1670 cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
\r
1673 This command is all on one line.
\r
1676 Hopefully your screen should show you downloading files. The -z3 simply compresses
\r
1677 the download to improve speed.
\r
1678 When this has finished, you will have exactly the same as if you had untarred a full
\r
1679 tarball PLUS some extra directories and files that CVS needs to do the magic that
\r
1683 Now if you are doing a new installation, that's it. Carry on as if you have
\r
1684 just downloaded and untarred the lastest tarball.
\r
1687 If you want to upgrade your current installation then do this ...
\r
1690 tar cvfz /tmp/s.tgz spider
\r
1692 tar xvfzp /tmp/s.tgz
\r
1695 This is assuming you downloaded to the /tmp directory of course.
\r
1698 NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
\r
1699 correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
\r
1701 Remember to recompile the C client (cd /spider/src; make)
\r
1704 At this point the files have been upgraded. You can (usually) restart the cluster
\r
1705 in your own time. However, if you attempt to use any new commands or features
\r
1706 expect it to be fatal! At least your cluster will have been restarted then so it
\r
1707 will be too late to worry about it!
\r
1710 Now the magic part! From now on when you want to update, simply connect to the
\r
1711 Internet and then, as the user <em>sysop</em> ...
\r
1718 and your files will be updated. As above, remember to recompile the "C" client
\r
1719 if it has been updated (CVS will tell you) and restart if any of the perl scripts
\r
1720 have been altered or added, again, CVS will tell you.
\r
1723 You will find any changes documented in the /spider/Changes file.
\r
1725 <sect1>CVS from a Windows platform
\r
1728 After the initial setup, an update to your DXSpider software is no more than a couple
\r
1729 of clicks away. This section is intended to explain and illustrate the use of the
\r
1730 WinCVS application to update your DXSpider software. The current stable version of
\r
1731 WinCVS is Ver. 1.2. You can get this software at:
\r
1733 <htmlurl url="http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip" name="http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip">
\r
1735 Pick your download mirror and then install WinCVS after the download is complete.
\r
1737 In this next section I have included a series of links to .jpg files to take advantage of the
\r
1738 picture and 1000 words equivalency. The .jpg files are in the C:\spider\html directory. If
\r
1739 someone using a Linux system is reading this section from boredom, the files are in
\r
1740 /home/sysop/spider/html. One aside, a Linux user can also get a copy of gcvs and do your updates
\r
1741 graphically as opposed to from the command line. The following descriptions are almost identical
\r
1742 between WinCvs and gcvs. The following screen shots have duplicate links, depending upon whether
\r
1743 you are viewing this information under the Windows or Linux operating system.
\r
1745 When WinCVS is installed, running, and you are connected to the internet, the initial screen looks like:
\r
1747 <htmlurl url="initial.jpg" name="initial.jpg">
\r
1749 If you want, you can also look at these .jpg files with another viewer that might provide some
\r
1750 better clarity to the image. On the left is the directory tree for your hard disk. Notice that
\r
1751 the spider directory has a gray highlight.
\r
1753 To start configuring WinCVS, click on Admin at the top of the screen and then Preferences. This
\r
1756 <htmlurl url="pref-gen.jpg" name="pref-gen.jpg">
\r
1758 In the top line for CVSROOT, enter:
\r
1760 anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
\r
1765 "passwd" file on the cvs server
\r
1768 for Authentication on the General tab.
\r
1770 Next, move to the right to the Ports tab.
\r
1772 <htmlurl url="pref-ports.jpg" name="pref-ports.jpg">
\r
1774 In here, check the box on the second line down for the "pserver" port. Enter a port number of 2401.
\r
1776 Finally, go to the WinCvs tab all the way to the right.
\r
1778 <htmlurl url="pref-wincvs.jpg" name="pref-wincvs.jpg">
\r
1780 Enter Notepad as the viewer to open files. For the HOME folder, put "C:\spider" and click OK
\r
1781 because the configuration is now complete.
\r
1783 You are now ready to upgrade your copy of DXSpider. Click on the greyed Spider folder
\r
1784 shown in the directory tree on the left of the WinCVS display. Two things should happen. The Spider
\r
1785 folder will be selected and the greyed-out arrow located just below the word Query in the top line will
\r
1786 turn to solid green.
\r
1788 For anyone using gcvs under Linux, the green arrow is located on the extreme left of the display,
\r
1789 under the word File. A gcvs screen looks like:
\r
1791 <htmlurl url="gcvs.jpg" name="gcvs.jpg">
\r
1793 Click on the now green arrow to start the download process. An Update Settings box will be displayed
\r
1794 to which you can simply say OK.
\r
1796 <htmlurl url="update-OK.jpg" name="update-OK.jpg">
\r
1798 For future reference, the Update Settings box is the place where you can enter information to revert
\r
1799 to a prior version of DXSpider. Information on reverting to a Before Date is contained in the WinCVS
\r
1802 After a short period of time, a series of file names will scroll by in the lower pane of the WinCVS
\r
1803 window. Eventually you should see
\r
1805 *****CVS exited normally with code 0*****
\r
1808 appear in the lower pane. You're done. The updated files are in place ready for you to stop and then
\r
1809 restart your DXSpider. After the restart, you're running with the latest version of DXSpider.
\r
1811 <htmlurl url="completed.jpg" name="completed.jpg">
\r
1813 To paraphrase from the CVS section... Now the magic part! From now on when you want to update, simply
\r
1814 connect to the Internet and start WinCVS.
\r
1816 Click on the greyed-out Spider directory in the left screen
\r
1817 Click on the green down arrow
\r
1818 Click OK on the Update Settings dialog box
\r
1819 Restart your Spider software
\r
1822 <sect>The DXSpider Command Reference
\r
1828 <bf>accept</bf> Set a filter to accept something
1832 Create a filter to accept something
1834 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1836 <sect1>accept/announce <call> [input] [0-9] <pattern> (8)
1840 <bf>accept/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version
1844 This version allows a sysop to set a filter for a callsign as well as the
1845 default for nodes and users eg:-
1849 accept/ann input node_default by G,M,2
1850 accept/ann user_default by G,M,2
1853 <sect1>accept/announce [0-9] <pattern> (0)
1857 <bf>accept/announce [0-9] <pattern></bf> Set an 'accept' filter line for announce
1861 Create an 'accept this announce' line for a filter.
1863 An accept filter line means that if the announce matches this filter it is
1864 passed onto the user. See HELP FILTERING for more info. Please read this
1865 to understand how filters work - it will save a lot of grief later on.
1867 You can use any of the following things in this line:-
1870 info <string> eg: iota or qsl
1871 by <prefixes> eg: G,M,2
1872 origin <prefixes>
1873 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1874 origin_itu <prefixes or numbers> or: G,GM,GW
1875 origin_zone <prefixes or numbers>
1876 origin_state <states> eg: VA,NH,RI,NH
1877 by_dxcc <prefixes or numbers>
1878 by_itu <prefixes or numbers>
1879 by_zone <prefixes or numbers>
1880 by_state <states>
1881 channel <prefixes>
1882 wx 1 filter WX announces
1883 dest <prefixes> eg: 6MUK,WDX (distros)
1890 acc/ann 2 by_zone 14,15,16
1891 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1901 acc/ann by_state va,nh,ri,nh
1904 You can use the tag 'all' to accept everything eg:
1910 but this probably for advanced users...
1911 <sect1>accept/route <call> [0-9] <pattern> (8)
1915 <bf>accept/route <call> [0-9] <pattern></bf> Set an 'accept' filter line for routing
1919 Create an 'accept this routing PC Protocol' line for a filter.
1921 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1922 it is passed thru that interface. See HELP FILTERING for more info. Please read this
1923 to understand how filters work - it will save a lot of grief later on.
1925 You can use any of the following things in this line:-
1928 call <prefixes> the callsign of the thingy
1929 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1930 call_itu <prefixes or numbers> or: G,GM,GW
1931 call_zone <prefixes or numbers>
1932 call_state <states> eg: VA,NH,RI,NH
1933 origin <prefixes> really the interface it came in on
1934 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1935 origin_itu <prefixes or numbers> or: G,GM,GW
1936 origin_zone <prefixes or numbers>
1937 origin_state <states> eg: VA,NH,RI,NH
1943 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
1944 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
1947 you can now use 'by' as a synonym for 'call' so:
1956 You can use the tag 'all' to accept everything eg:
1962 <sect1>accept/spots <call> [input] [0-9] <pattern> (8)
1966 <bf>accept/spots <call> [input] [0-9] <pattern></bf> Spot filter sysop version
1970 This version allows a sysop to set a filter for a callsign as well as the
1971 default for nodes and users eg:-
1974 accept/spot db0sue-7 1 by_zone 14,15,16
1975 accept/spot node_default all
1976 set/hops node_default 10
1980 accept/spot user_default by G,M,2
1983 <sect1>accept/spots [0-9] <pattern> (0)
1987 <bf>accept/spots [0-9] <pattern></bf> Set an 'accept' filter line for spots
1991 Create an 'accept this spot' line for a filter.
1993 An accept filter line means that if the spot matches this filter it is
1994 passed onto the user. See HELP FILTERING for more info. Please read this
1995 to understand how filters work - it will save a lot of grief later on.
1997 You can use any of the following things in this line:-
2000 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2001 on <range> same as 'freq'
2002 call <prefixes> eg: G,PA,HB9
2003 info <string> eg: iota or qsl
2005 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2006 call_itu <prefixes or numbers> or: G,GM,GW
2007 call_zone <prefixes or numbers>
2008 call_state <states> eg: VA,NH,RI,ME
2009 by_dxcc <prefixes or numbers>
2010 by_itu <prefixes or numbers>
2011 by_zone <prefixes or numbers>
2012 by_state <states> eg: VA,NH,RI,ME
2013 origin <prefixes>
2014 channel <prefixes>
2017 'call' means the callsign that has spotted 'by' whoever.
2019 For frequencies, you can use any of the band names defined in
2020 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2021 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2022 this is more efficient than saying simply: freq HF (but don't get
2023 too hung up about that)
2029 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2032 You can use the tag 'all' to accept everything, eg:
2041 acc/spots by_state VA,NH,RI,MA,ME
2044 but this probably for advanced users...
2045 <sect1>accept/wcy <call> [input] [0-9] <pattern> (8)
2049 <bf>accept/wcy <call> [input] [0-9] <pattern></bf> WCY filter sysop version
2053 This version allows a sysop to set a filter for a callsign as well as the
2054 default for nodes and users eg:-
2057 accept/wcy node_default all
2058 set/hops node_default 10
2061 <sect1>accept/wcy [0-9] <pattern> (0)
2065 <bf>accept/wcy [0-9] <pattern></bf> set an 'accept' WCY filter
2069 It is unlikely that you will want to do this, but if you do then you can
2070 filter on the following fields:-
2073 by <prefixes> eg: G,M,2
2074 origin <prefixes>
2075 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2076 origin_itu <prefixes or numbers> or: G,GM,GW
2077 origin_zone <prefixes or numbers>
2078 by_dxcc <prefixes or numbers>
2079 by_itu <prefixes or numbers>
2080 by_zone <prefixes or numbers>
2081 channel <prefixes>
2084 There are no examples because WCY Broadcasts only come from one place and
2085 you either want them or not (see UNSET/WCY if you don't want them).
2087 This command is really provided for future use.
2089 See HELP FILTER for information.
2090 <sect1>accept/wwv <call> [input] [0-9] <pattern> (8)
2094 <bf>accept/wwv <call> [input] [0-9] <pattern></bf> WWV filter sysop version
2098 This version allows a sysop to set a filter for a callsign as well as the
2099 default for nodes and users eg:-
2102 accept/wwv db0sue-7 1 by_zone 4
2103 accept/wwv node_default all
2104 set/hops node_default 10
2108 accept/wwv user_default by W,K
2111 <sect1>accept/wwv [0-9] <pattern> (0)
2115 <bf>accept/wwv [0-9] <pattern></bf> set an 'accept' WWV filter
2119 It is unlikely that you will want to do this, but if you do then you can
2120 filter on the following fields:-
2123 by <prefixes> eg: G,M,2
2124 origin <prefixes>
2125 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2126 origin_itu <prefixes or numbers> or: G,GM,GW
2127 origin_zone <prefixes or numbers>
2128 by_dxcc <prefixes or numbers>
2129 by_itu <prefixes or numbers>
2130 by_zone <prefixes or numbers>
2131 channel <prefixes>
2137 accept/wwv by_zone 4
2140 is probably the only useful thing to do (which will only show WWV broadcasts
2141 by stations in the US).
2143 See HELP FILTER for information.
2144 <sect1>announce <text> (0)
2148 <bf>announce <text></bf> Send an announcement to LOCAL users only
2152 <text> is the text of the announcement you wish to broadcast
2153 <sect1>announce full <text> (0)
2157 <bf>announce full <text></bf> Send an announcement cluster wide
2161 This will send your announcement cluster wide
2162 <sect1>announce sysop <text> (5)
2166 <bf>announce sysop <text></bf> Send an announcement to Sysops only
2170 <sect1>apropos <string> (0)
2174 <bf>apropos <string></bf> Search help database for <string>
2178 Search the help database for <string> (it isn't case sensitive), and print
2179 the names of all the commands that may be relevant.
2180 <sect1>blank [<string>] [<nn>] (0)
2184 <bf>blank [<string>] [<nn>]</bf> Print nn (default 1) blank lines (or strings)
2188 In its basic form this command prints one or more blank lines. However if
2189 you pass it a string it will replicate the string for the width of the
2190 screen (default 80) and then print that one or more times, so:
2196 prints two blank lines
2202 prints a row of - characters once.
2208 prints 'abcabcabcabcabcabc....'
2210 This is really only of any use in a script file and you can print a maximum
2216 <bf>bye</bf> Exit from the cluster
2220 This will disconnect you from the cluster
2221 <sect1>catchup <node call> all|[<msgno> ...] (5)
2225 <bf>catchup <node call> all|[<msgno> ...]</bf> Mark a message as sent
2229 <sect1>chat <group> <text> (0)
2233 <bf>chat <group> <text></bf> Chat or Conference to a group
2237 It is now possible to JOIN a group and have network wide conferencing to that
2238 group. DXSpider does not (and probably will not) implement the AK1A
2239 conference mode as this seems very limiting, is hardly used and doesn't seem
2240 to work too well anyway.
2242 This system uses the existing ANN system and is compatible with both other
2243 DXSpider nodes and AK1A clusters (they use ANN/<group>).
2245 You can be a member of as many "groups" as you want. To join a group type:-
2248 JOIN FOC (where FOC is the group name)
2251 To leave a group type:-
2257 You can see which groups you are in by typing:-
2263 and you can see whether your mate is in the group, if he connects to the
2264 same node as you, by typing:-
2270 To send a message to a group type:-
2273 CHAT FOC hello everyone
2279 CH #9000 hello I am back
2282 See also JOIN, LEAVE, SHOW/CHAT
2283 <sect1>clear/announce <callsign> [input] [0-9|all] (8)
2287 <bf>clear/announce <callsign> [input] [0-9|all]</bf> Clear a announce filter line
2291 A sysop can clear an input or normal output filter for a user or the
2292 node_default or user_default.
2293 <sect1>clear/announce [1|all] (0)
2297 <bf>clear/announce [1|all]</bf> Clear a announce filter line
2301 This command allows you to clear (remove) a line in a annouce filter or to
2302 remove the whole filter.
2304 see CLEAR/SPOTS for a more detailed explanation.
2305 <sect1>clear/route <callsign> [input] [0-9|all] (8)
2309 <bf>clear/route <callsign> [input] [0-9|all]</bf> Clear a route filter line
2313 A sysop can clear an input or normal output filter for a user or the
2314 node_default or user_default.
2315 <sect1>clear/route [1|all] (0)
2319 <bf>clear/route [1|all]</bf> Clear a route filter line
2323 This command allows you to clear (remove) a line in a route filter or to
2324 remove the whole filter.
2326 see CLEAR/SPOTS for a more detailed explanation.
2327 <sect1>clear/spots <callsign> [input] [0-9|all] (8)
2331 <bf>clear/spots <callsign> [input] [0-9|all]</bf> Clear a spot filter line
2335 A sysop can clear an input or normal output filter for a user or the
2336 node_default or user_default.
2337 <sect1>clear/spots [0-9|all] (0)
2341 <bf>clear/spots [0-9|all]</bf> Clear a spot filter line
2345 This command allows you to clear (remove) a line in a spot filter or to
2346 remove the whole filter.
2348 If you have a filter:-
2352 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2361 you will be left with:-
2364 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2373 the filter will be completely removed.
2374 <sect1>clear/wcy <callsign> [input] [0-9|all] (8)
2378 <bf>clear/wcy <callsign> [input] [0-9|all]</bf> Clear a WCY filter line
2382 A sysop can clear an input or normal output filter for a user or the
2383 node_default or user_default.
2384 <sect1>clear/wcy [1|all] (0)
2388 <bf>clear/wcy [1|all]</bf> Clear a WCY filter line
2392 This command allows you to clear (remove) a line in a WCY filter or to
2393 remove the whole filter.
2395 see CLEAR/SPOTS for a more detailed explanation.
2396 <sect1>clear/wwv <callsign> [input] [0-9|all] (8)
2400 <bf>clear/wwv <callsign> [input] [0-9|all]</bf> Clear a WWV filter line
2404 A sysop can clear an input or normal output filter for a user or the
2405 node_default or user_default.
2406 <sect1>clear/wwv [1|all] (0)
2410 <bf>clear/wwv [1|all]</bf> Clear a WWV filter line
2414 This command allows you to clear (remove) a line in a WWV filter or to
2415 remove the whole filter.
2417 see CLEAR/SPOTS for a more detailed explanation.
2418 <sect1>connect <callsign> (5)
2422 <bf>connect <callsign></bf> Start a connection to another DX Cluster
2426 Start a connection process that will culminate in a new connection to the
2427 DX cluster <callsign>. This process creates a new 'client' process which will
2428 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
2429 necessary to traverse the network(s) to logon to the cluster <callsign>.
2434 <bf>dbavail</bf> Show a list of all the Databases in the system
2438 Title says it all really, this command lists all the databases defined
2439 in the system. It is also aliased to SHOW/COMMAND.
2440 <sect1>dbcreate <name> (9)
2444 <bf>dbcreate <name></bf> Create a database entry
2448 <sect1>dbcreate <name> chain <name> [<name>..] (9)
2452 <bf>dbcreate <name> chain <name> [<name>..]</bf> Create a chained database entry
2456 <sect1>dbcreate <name> cmd <dxspider command> (9)
2460 <bf>dbcreate <name> cmd <dxspider command></bf> make a local command available as a DB
2464 DBCREATE allows you to define a database in the system. It doesn't actually
2465 create anything, just defines it.
2467 The databases that are created are simple DB_File hash databases, they are
2468 therefore already 'indexed'.
2470 You can define a local database with the first form of the command eg:
2476 You can also chain databases with the addition of the 'chain' keyword.
2477 This will search each database one after the other. A typical example
2481 DBCREATE sdx_qsl chain sql_ad
2484 No checking is done to see if the any of the chained databases exist, in
2485 fact it is usually better to do the above staement first then do each of
2486 the chained databases.
2488 Databases can exist offsite. To define a database that lives on another
2492 DBCREATE buckmaster remote gb7dxc
2495 Remote databases cannot be chained; however, the last database in a
2496 a chain can be a remote database eg:
2499 DBCREATE qsl chain gb7dxc
2502 To see what databases have been defined do:
2505 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
2508 It would be normal for you to add an entry into your local Aliases file
2509 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
2510 need to add a line like:-
2516 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
2528 to work as they may be used to.
2530 You can also make local commands available as 'pseudo' databases. You
2531 can therefore make spider special commands available as a database. I
2532 imagine that this will be primarily useful for remote access from
2533 legacy nodes. For example:-
2536 DBCREATE dxqsl cmd show/dxqsl
2539 You also use one of these databases in a chain. This may be useful
2542 See DBIMPORT for the importing of existing AK1A format data to databases.
2543 See DBSHOW for generic database enquiry
2545 <sect1>dbcreate <name> remote <node> (9)
2549 <bf>dbcreate <name> remote <node></bf> Create a remote database entry
2553 <sect1>dbimport <dbname> <filename> (9)
2557 <bf>dbimport <dbname> <filename></bf> Import AK1A data into a database
2561 If you want to import or update data in bulk to a database you can use
2562 this command. It will either create or update entries into an existing
2563 database. For example:-
2566 DBIMPORT oblast /tmp/OBLAST.FUL
2569 will import the standard OBLAST database that comes with AK1A into the
2570 oblast database held locally.
2571 <sect1>dbremove <dbname> (9)
2575 <bf>dbremove <dbname></bf> Delete a database
2579 DBREMOVE will completely remove a database entry and also delete any data
2580 file that is associated with it.
2582 There is no warning, no comeback, no safety net.
2590 will remove the oblast database from the system and it will also remove
2591 the associated datafile.
2595 There is no warning, no comeback, no safety net.
2597 You have been warned.
2598 <sect1>dbshow <dbname> <key> (0)
2602 <bf>dbshow <dbname> <key></bf> Display an entry, if it exists, in a database
2606 This is the generic user interface to the database to the database system.
2607 It is expected that the sysop will add an entry to the local Aliases file
2608 so that users can use the more familiar AK1A style of enquiry such as:
2614 but if he hasn't and the database really does exist (use DBAVAIL or
2615 SHOW/COMMAND to find out) you can do the same thing with:
2625 <bf>debug</bf> Set the cluster program into debug mode
2629 Executing this command will only have an effect if you are running the cluster
2636 It will interrupt the cluster just after the debug command has finished.
2637 <sect1>delete/usdb <callsign> ... (9)
2641 <bf>delete/usdb <callsign> ...</bf> Delete this user from the US State Database
2645 This command will completely remove a one or more callsigns
2646 from the US States database.
2648 There is NO SECOND CHANCE.
2650 It goes without saying that you should use this command CAREFULLY!
2652 Note that these callsign may be re-instated by any weekly updates from
2654 <sect1>delete/user <callsign> ... (9)
2658 <bf>delete/user <callsign> ...</bf> Delete this user from the User Database
2662 This command will completely remove a one or more users from the database.
2664 There is NO SECOND CHANCE.
2666 It goes without saying that you should use this command CAREFULLY!
2667 <sect1>demonstrate <call> <command> (9)
2671 <bf>demonstrate <call> <command></bf> Demonstrate a command to another user
2675 This command is provided so that sysops can demonstrate commands to
2676 other users. It runs a command as though that user had typed it in and
2677 then sends the output to that user, together with the command that
2681 DEMO g7brn sh/dx iota oc209
2685 Note that this command is similar to SPOOF and will have the same side
2686 effects. Commands are run at the privilege of the user which is being
2688 <sect1>directory (0)
2692 <bf>directory</bf> List messages
2696 <sect1>directory <from>-<to> (0)
2700 <bf>directory <from>-<to></bf> List messages <from> message <to> message
2704 List the messages in the messages directory.
2706 If there is a 'p' one space after the message number then it is a
2707 personal message. If there is a '-' between the message number and the
2708 'p' then this indicates that the message has been read.
2710 You can use shell escape characters such as '*' and '?' in the <call>
2713 You can combine some of the various directory commands together eg:-
2720 DIR SUBJECT IOTA 200-250
2723 You can abbreviate all the commands to one letter and use ak1a syntax:-
2730 <sect1>directory <nn> (0)
2734 <bf>directory <nn></bf> List last <nn> messages
2738 <sect1>directory all (0)
2742 <bf>directory all</bf> List all messages
2746 <sect1>directory from <call> (0)
2750 <bf>directory from <call></bf> List all messages from <call>
2754 <sect1>directory new (0)
2758 <bf>directory new</bf> List all new messages
2762 <sect1>directory own (0)
2766 <bf>directory own</bf> List your own messages
2770 <sect1>directory subject <string> (0)
2774 <bf>directory subject <string></bf> List all messages with <string> in subject
2778 <sect1>directory to <call> (0)
2782 <bf>directory to <call></bf> List all messages to <call>
2786 <sect1>directory- (5)
2794 Sysops can see all users' messages.
2795 <sect1>disconnect <call> [<call> ...] (8)
2799 <bf>disconnect <call> [<call> ...]</bf> Disconnect a user or cluster
2803 Disconnect any <call> connected locally
2804 <sect1>dx [by <call>] <freq> <call> <remarks> (0)
2808 <bf>dx [by <call>] <freq> <call> <remarks></bf> Send a DX spot
2812 This is how you send a DX Spot to other users. You can, in fact, now
2813 enter the <freq> and the <call> either way round.
2821 will all give the same result. You can add some remarks to the end
2822 of the command and they will be added to the spot.
2825 DX FR0G 144600 this is a test
2828 You can credit someone else by saying:-
2831 DX by G1TLH FR0G 144.600 he isn't on the cluster
2834 The <freq> is compared against the available bands set up in the
2835 cluster. See SHOW/BANDS for more information.
2836 <sect1>echo <line> (0)
2840 <bf>echo <line></bf> Echo the line to the output
2844 This command is useful in scripts and so forth for printing the
2845 line that you give to the command to the output. You can use this
2846 in user_default scripts and the SAVE command for titling and so forth
2848 The script will interpret certain standard "escape" sequences as follows:-
2851 \t - becomes a TAB character (0x09 in ascii)
2852 \a - becomes a BEEP character (0x07 in ascii)
2853 \n - prints a new line
2856 So the following example:-
2859 echo GB7DJK is a dxcluster
2865 GB7DJK is a dxcluster
2868 on the output. You don't need a \n on the end of the line you want to send.
2870 A more complex example:-
2873 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
2886 <sect1>export <msgno> <filename> (9)
2890 <bf>export <msgno> <filename></bf> Export a message to a file
2894 Export a message to a file. This command can only be executed on a local
2895 console with a fully privileged user. The file produced will be in a form
2896 ready to be imported back into the cluster by placing it in the import
2897 directory (/spider/msg/import).
2899 This command cannot overwrite an existing file. This is to provide some
2900 measure of security. Any files written will owned by the same user as the
2901 main cluster, otherwise you can put the new files anywhere the cluster can
2902 access. For example:-
2908 <sect1>export_users [<filename>] (9)
2912 <bf>export_users [<filename>]</bf> Export the users database to ascii
2916 Export the users database to a file in ascii format. If no filename
2917 is given then it will export the file to /spider/data/user_asc.
2919 If the file already exists it will be renamed to <filename>.o. In fact
2920 up to 5 generations of the file can be kept each one with an extra 'o' on the
2923 BE WARNED: this will write to any file you have write access to. No check is
2924 made on the filename (if any) that you specify.
2925 <sect1>filtering... (0)
2929 <bf>filtering...</bf> Filtering things in DXSpider
2933 There are a number of things you can filter in the DXSpider system. They
2934 all use the same general mechanism.
2936 In general terms you can create a 'reject' or an 'accept' filter which
2937 can have up to 10 lines in it. You do this using, for example:-
2944 where ..... are the specific commands for that type of filter. There
2945 are filters for spots, wwv, announce, wcy and (for sysops)
2946 connects. See each different accept or reject command reference for
2949 There is also a command to clear out one or more lines in a filter and
2950 one to show you what you have set. They are:-
2963 There is clear/xxxx command for each type of filter.
2965 For now we are going to use spots for the examples, but you can apply
2966 the principles to all types of filter.
2968 There are two main types of filter 'accept' or 'reject'; which you use
2969 depends entirely on how you look at the world and what is least
2970 writing to achieve what you want. Each filter has 10 lines (of any
2971 length) which are tried in order. If a line matches then the action
2972 you have specified is taken (ie reject means ignore it and accept
2975 The important thing to remember is that if you specify a 'reject'
2976 filter (all the lines in it say 'reject/spots' (for instance)) then if
2977 a spot comes in that doesn't match any of the lines then you will get
2978 it BUT if you specify an 'accept' filter then any spots that don't
2979 match are dumped. For example if I have a one line accept filter:-
2982 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
2985 then automatically you will ONLY get VHF spots from or to CQ zones 14
2986 15 and 16. If you set a reject filter like:
2989 reject/spots on hf/cw
2992 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
2993 and will work it even on CW then you could say:-
2996 reject/spots on hf/cw and not info iota
2999 But in that case you might only be interested in iota and say:-
3002 accept/spots not on hf/cw or info iota
3005 which is exactly the same. You should choose one or the other until
3006 you are confortable with the way it works. Yes, you can mix them
3007 (actually you can have an accept AND a reject on the same line) but
3008 don't try this at home until you can analyse the results that you get
3009 without ringing up the sysop for help.
3011 Another useful addition now is filtering by US state
3014 accept/spots by_state VA,NH,RI,ME
3017 You can arrange your filter lines into logical units, either for your
3018 own understanding or simply convenience. I have one set frequently:-
3021 reject/spots 1 on hf/cw
3022 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
3025 What this does is to ignore all HF CW spots (being a class B I can't
3026 read any CW and couldn't possibly be interested in HF :-) and also
3027 rejects any spots on VHF which don't either originate or spot someone
3030 This is an exmaple where you would use the line number (1 and 2 in
3031 this case), if you leave the digit out, the system assumes '1'. Digits
3032 '0'-'9' are available.
3034 You can leave the word 'and' out if you want, it is implied. You can
3035 use any number of brackets to make the 'expression' as you want
3036 it. There are things called precedence rules working here which mean
3037 that you will NEED brackets in a situation like line 2 because,
3038 without it, will assume:-
3041 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
3044 annoying, but that is the way it is. If you use OR - use
3045 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
3048 If you want to alter your filter you can just redefine one or more
3049 lines of it or clear out one line. For example:-
3052 reject/spots 1 on hf/ssb
3061 To remove the filter in its entirty:-
3067 There are similar CLEAR commands for the other filters:-
3077 Once you are happy with the results you get, you may like to experiment.
3079 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
3080 can be written with a mixed filter, eg:
3085 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
3088 each filter slot actually has a 'reject' slot and an 'accept'
3089 slot. The reject slot is executed BEFORE the accept slot.
3091 It was mentioned earlier that after a reject test that doesn't match,
3092 the default for following tests is 'accept', the reverse is true for
3093 'accept'. In the example what happens is that the reject is executed
3094 first, any non hf/cw spot is passed to the accept line, which lets
3095 thru everything else on HF.
3097 The next filter line lets through just VHF/UHF spots from EU.
3098 <sect1>forward/latlong <node_call> (8)
3102 <bf>forward/latlong <node_call></bf> Send latitude and longitude information to another cluster
3106 This command sends all the latitude and longitude information that your
3107 cluster is holding against callsigns. One advantage of recieving this
3108 information is that more locator information is held by you. This
3109 means that more locators are given on the DX line assuming you have
3110 SET/DXGRID enabled. This could be a LOT of information though, so
3111 it is not recommended on slow links.
3112 <sect1>forward/opernam <call> (1)
3116 <bf>forward/opernam <call></bf> Send out information on this <call> to all clusters
3120 This command sends out any information held in the user file which can
3121 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
3122 and Homenode. PC41s are only sent for the information that is available.
3128 <bf>help</bf> The HELP Command
3132 HELP is available for a number of commands. The syntax is:-
3138 Where <cmd> is the name of the command you want help on.
3140 All commands can be abbreviated, so SHOW/DX can be abbreviated
3141 to SH/DX, ANNOUNCE can be shortened to AN and so on.
3143 Look at the APROPOS <string> command which will search the help database
3144 for the <string> you specify and give you a list of likely commands
3145 to look at with HELP.
3146 <sect1>init <node> (5)
3150 <bf>init <node></bf> Re-initialise a link to an AK1A compatible node
3154 This command attempts to re-initialise a link to a (usually) AK1A node
3155 that has got confused, usually by a protocol loop of some kind. It may
3156 work - but you usually will be better off simply disconnecting it (or
3157 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
3160 Best of luck - you will need it.
3162 <sect1>join <group> (0)
3166 <bf>join <group></bf> Join a chat or conference group
3170 JOIN allows you to join a network wide conference group. To join a
3171 group (called FOC in this case) type:-
3177 See also CHAT, LEAVE, SHOW/CHAT
3186 As a sysop you can kill any message on the system.
3187 <sect1>kill <from msgno>-<to msgno> (0)
3191 <bf>kill <from msgno>-<to msgno></bf> Delete a range of messages
3195 <sect1>kill <from>-<to> (5)
3199 <bf>kill <from>-<to></bf> Remove a range of messages from the system
3203 <sect1>kill <msgno> [<msgno..] (0)
3207 <bf>kill <msgno> [<msgno..]</bf> Delete a message from the local system
3211 <sect1>kill <msgno> [<msgno> ...] (0)
3215 <bf>kill <msgno> [<msgno> ...]</bf> Remove or erase a message from the system
3219 You can get rid of any message to or originating from your callsign using
3220 this command. You can remove more than one message at a time.
3221 <sect1>kill expunge <msgno> [<msgno..] (6)
3225 <bf>kill expunge <msgno> [<msgno..]</bf> Expunge a message
3229 Deleting a message using the normal KILL commands only marks that message
3230 for deletion. The actual deletion only happens later (usually two days later).
3232 The KILL EXPUNGE command causes the message to be truly deleted more or less
3235 It otherwise is used in the same way as the KILL command.
3236 <sect1>kill from <call> (5)
3240 <bf>kill from <call></bf> Remove all messages from a callsign
3244 <sect1>kill full <msgno> [<msgno..] (5)
3248 <bf>kill full <msgno> [<msgno..]</bf> Delete a message from the whole cluster
3252 Delete a message from the local system. You will only be able to
3253 delete messages that you have originated or been sent (unless you are
3260 Will delete all the messages that you own between msgnos 1234 and 1255.
3266 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
3272 will delete all messages to g1tlh.
3278 will delete a message (usually a 'bulletin') from the whole cluster system.
3280 This uses the subject field, so any messages that have exactly the
3281 same subject will be deleted. Beware!
3282 <sect1>kill full <msgno> [<msgno] (5)
3286 <bf>kill full <msgno> [<msgno]</bf> Remove a message from the entire cluster
3290 Remove this message from the entire cluster system as well as your node.
3291 <sect1>kill to <call> (5)
3295 <bf>kill to <call></bf> Remove all messages to a callsign
3299 <sect1>kill from <regex> (0)
3303 <bf>kill from <regex></bf> Delete messages FROM a callsign or pattern
3307 <sect1>kill to <regex> (0)
3311 <bf>kill to <regex></bf> Delete messages TO a callsign or pattern
3315 <sect1>leave <group> (0)
3319 <bf>leave <group></bf> Leave a chat or conference group
3323 LEAVE allows you to leave a network wide conference group. To leave a
3324 group (called FOC in this case) type:-
3330 See also CHAT, JOIN, SHOW/CHAT
3335 <bf>links</bf> Show which nodes is physically connected
3339 This is a quick listing that shows which links are connected and
3340 some information about them. See WHO for a list of all connections.
3341 <sect1>load/aliases (9)
3345 <bf>load/aliases</bf> Reload the command alias table
3349 Reload the /spider/cmd/Aliases file after you have editted it. You
3350 will need to do this if you change this file whilst the cluster is
3351 running in order for the changes to take effect.
3352 <sect1>load/badmsg (9)
3356 <bf>load/badmsg</bf> Reload the bad msg table
3360 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
3361 the cluster is running. This table contains a number of perl regular
3362 expressions which are searched for in the fields targetted of each message.
3363 If any of them match then that message is immediately deleted on receipt.
3364 <sect1>load/badwords (9)
3368 <bf>load/badwords</bf> Reload the bad words table
3372 Reload the /spider/data/badwords file if you have changed it manually whilst
3373 the cluster is running. This file contains a list of words which, if found
3374 on certain text portions of PC protocol, will cause those protocol frames
3375 to be rejected. It will all put out a message if any of these words are
3376 used on the announce, dx and talk commands. The words can be one or
3377 more on a line, lines starting with '#' are ignored.
3378 <sect1>load/bands (9)
3382 <bf>load/bands</bf> Reload the band limits table
3386 Reload the /spider/data/bands.pl file if you have changed it manually whilst
3387 the cluster is running.
3388 <sect1>load/cmd_cache (9)
3392 <bf>load/cmd_cache</bf> Reload the automatic command cache
3396 Normally, if you change a command file in the cmd or local_cmd tree it
3397 will automatially be picked up by the cluster program. Sometimes it
3398 can get confused if you are doing a lot of moving commands about or
3399 delete a command in the local_cmd tree and want to use the normal one
3400 again. Execute this command to reset everything back to the state it
3401 was just after a cluster restart.
3402 <sect1>load/forward (9)
3406 <bf>load/forward</bf> Reload the msg forwarding routing table
3410 Reload the /spider/msg/forward.pl file if you have changed it
3411 manually whilst the cluster is running.
3412 <sect1>load/keps (5)
3416 <bf>load/keps</bf> Load new keps data
3420 <sect1>load/keps [nn] (5)
3424 <bf>load/keps [nn]</bf> Load new keps data from message
3428 If there is no message number then reload the current Keps data from
3429 the Keps.pm data file. You create this file by running
3432 /spider/perl/convkeps.pl <filename>
3435 on a file containing NASA 2 line keps as a message issued by AMSAT.
3437 If there is a message number, then it will take the message, run
3438 convkeps.pl on it and then load the data, all in one step.
3440 These messages are sent to ALL by GB7DJK (and others) from time to time.
3441 <sect1>load/messages (9)
3445 <bf>load/messages</bf> Reload the system messages file
3449 If you change the /spider/perl/Messages file (usually whilst
3450 fiddling/writing new commands) you can have them take effect during a
3451 cluster session by executing this command. You need to do this if get
3454 unknown message 'xxxx' in lang 'en'
3455 <sect1>load/prefixes (9)
3459 <bf>load/prefixes</bf> Reload the prefix table
3463 Reload the /spider/data/prefix_data.pl file if you have changed it
3464 manually whilst the cluster is running.
3465 <sect1>merge <node> [<no spots>/<no wwv>] (5)
3469 <bf>merge <node> [<no spots>/<no wwv>]</bf> Ask for the latest spots and WWV
3473 MERGE allows you to bring your spot and wwv database up to date. By default
3474 it will request the last 10 spots and 5 WWVs from the node you select. The
3475 node must be connected locally.
3477 You can request any number of spots or wwv and although they will be appended
3478 to your databases they will not duplicate any that have recently been added
3479 (the last 2 days for spots and last month for WWV data).
3480 <sect1>msg <cmd> <msgno> [data ... ] (9)
3484 <bf>msg <cmd> <msgno> [data ... ]</bf> Alter various message parameters
3488 Alter message parameters like To, From, Subject, whether private or bulletin
3489 or return receipt (RR) is required or whether to keep this message from timing
3493 MSG TO <msgno> <call> - change TO callsign to <call>
3494 MSG FRom <msgno> <call> - change FROM callsign to <call>
3495 MSG PRrivate <msgno> - set private flag
3496 MSG NOPRrivate <msgno> - unset private flag
3497 MSG RR <msgno> - set RR flag
3498 MSG NORR <msgno> - unset RR flag
3499 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
3500 MSG NOKEep <msgno> - unset the keep flag
3501 MSG SUbject <msgno> <new> - change the subject to <new>
3502 MSG WAittime <msgno> - remove any waitting time for this message
3503 MSG NOREad <msgno> - mark message as unread
3504 MSG REad <msgno> - mark message as read
3505 MSG QUeue - queue any outstanding bulletins
3506 MSG QUeue 1 - queue any outstanding private messages
3509 You can look at the status of a message by using:-
3512 STAT/MSG <msgno>
3515 This will display more information on the message than DIR does.
3517 <sect1>pc <call> <text> (8)
3521 <bf>pc <call> <text></bf> Send arbitrary text to a connected callsign
3525 Send some arbitrary text to a locally connected callsign. No
3526 processing is done on the text. This command allows you to send PC
3527 Protocol to unstick things if problems arise (messages get stuck
3531 pc gb7djk PC33^GB7TLH^GB7DJK^400^
3535 pc G1TLH Try doing that properly!!!
3538 Send any text you like to the callsign requested. This is used mainly to send
3539 PC protocol to connected nodes either for testing or to unstick things.
3541 You can also use in the same way as a talk command to a connected user but
3542 without any processing, added of "from <blah> to <blah" or whatever.
3544 <sect1>ping <node call> (1)
3548 <bf>ping <node call></bf> Check the link quality between nodes
3552 This command allows you to send a frame to another cluster node on
3553 the network and get a return frame. The time it takes to do this
3554 is a good indication of the quality of the link. The actual time
3555 it takes is output to the console in seconds.
3556 Any visible cluster node can be PINGed.
3557 <sect1>rcmd <node call> <cmd> (1)
3561 <bf>rcmd <node call> <cmd></bf> Send a command to another DX Cluster
3565 This command allows you to send nearly any command to another DX Cluster
3566 node that is connected to the system.
3568 Whether you get any output is dependant on a) whether the other system knows
3569 that the node callsign of this cluster is in fact a node b) whether the
3570 other system is allowing RCMDs from this node and c) whether you have
3571 permission to send this command at all.
3576 <bf>read</bf> Read the next unread personal message addressed to you
3580 <sect1>read <msgno> (0)
3584 <bf>read <msgno></bf> Read the specified message
3588 You can read any messages that are sent as 'non-personal' and also any
3589 message either sent by or sent to your callsign.
3598 As a sysop you may read any message on the system
3603 <bf>reject</bf> Set a filter to reject something
3607 Create a filter to reject something
3609 There are 2 types of filter, accept and reject. See HELP FILTERING for more
3611 <sect1>reject/announce <call> [input] [0-9] <pattern> (8)
3615 <bf>reject/announce <call> [input] [0-9] <pattern></bf> Announce filter sysop version
3619 This version allows a sysop to set a filter for a callsign as well as the
3620 default for nodes and users eg:-
3624 reject/ann input node_default by G,M,2
3625 reject/ann user_default by G,M,2
3628 <sect1>reject/announce [0-9] <pattern> (0)
3632 <bf>reject/announce [0-9] <pattern></bf> Set a 'reject' filter line for announce
3636 Create an 'reject this announce' line for a filter.
3638 A reject filter line means that if the announce matches this filter it is
3639 passed onto the user. See HELP FILTERING for more info. Please read this
3640 to understand how filters work - it will save a lot of grief later on.
3642 You can use any of the following things in this line:-
3645 info <string> eg: iota or qsl
3646 by <prefixes> eg: G,M,2
3647 origin <prefixes>
3648 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3649 origin_itu <prefixes or numbers> or: G,GM,GW
3650 origin_zone <prefixes or numbers>
3651 origin_state <states> eg: VA,NH,RI,ME
3652 by_dxcc <prefixes or numbers>
3653 by_itu <prefixes or numbers>
3654 by_zone <prefixes or numbers>
3655 by_state <states> eg: VA,NH,RI,ME
3656 channel <prefixes>
3657 wx 1 filter WX announces
3658 dest <prefixes> eg: 6MUK,WDX (distros)
3664 rej/ann by_zone 14,15,16 and not by G,M,2
3667 You can use the tag 'all' to reject everything eg:
3673 but this probably for advanced users...
3674 <sect1>reject/route <call> [0-9] <pattern> (8)
3678 <bf>reject/route <call> [0-9] <pattern></bf> Set an 'reject' filter line for routing
3682 Create an 'reject this routing PC Protocol' line for a filter.
3684 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
3685 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
3686 read this to understand how filters work - it will save a lot of grief later on.
3688 You can use any of the following things in this line:-
3691 call <prefixes> the callsign of the thingy
3692 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3693 call_itu <prefixes or numbers> or: G,GM,GW
3694 call_zone <prefixes or numbers>
3695 call_state <states> eg: VA,NH,RI,ME
3696 origin <prefixes> really the interface it came in on
3697 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3698 origin_itu <prefixes or numbers> or: G,GM,GW
3699 origin_zone <prefixes or numbers>
3700 origin_state <states> eg: VA,NH,RI,ME
3706 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
3709 You can use the tag 'all' to reject everything eg:
3712 rej/route all (equiv to [very] restricted mode)
3715 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
3716 <sect1>reject/spots <call> [input] [0-9] <pattern> (8)
3720 <bf>reject/spots <call> [input] [0-9] <pattern></bf> Spot filter sysop version
3724 This version allows a sysop to set a filter for a callsign as well as the
3725 default for nodes and users eg:-
3728 reject/spot db0sue-7 1 by_zone 14,15,16
3729 reject/spot node_default all
3730 set/hops node_default 10
3734 reject/spot user_default by G,M,2
3737 <sect1>reject/spots [0-9] <pattern> (0)
3741 <bf>reject/spots [0-9] <pattern></bf> Set a 'reject' filter line for spots
3745 Create a 'reject this spot' line for a filter.
3747 A reject filter line means that if the spot matches this filter it is
3748 dumped (not passed on). See HELP FILTERING for more info. Please read this
3749 to understand how filters work - it will save a lot of grief later on.
3751 You can use any of the following things in this line:-
3754 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
3755 on <range> same as 'freq'
3756 call <prefixes> eg: G,PA,HB9
3757 info <string> eg: iota or qsl
3759 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3760 call_itu <prefixes or numbers> or: G,GM,GW
3761 call_zone <prefixes or numbers>
3762 call_state <states> eg: VA,NH,RI,ME
3763 by_dxcc <prefixes or numbers>
3764 by_itu <prefixes or numbers>
3765 by_zone <prefixes or numbers>
3766 by_state <states> eg: VA,NH,RI,ME
3767 origin <prefixes>
3768 channel <prefixes>
3771 'call' means the callsign that has spotted 'by' whoever.
3773 For frequencies, you can use any of the band names defined in
3774 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
3775 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
3776 this is more efficient than saying simply: on HF (but don't get
3777 too hung up about that)
3783 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
3786 You can use the tag 'all' to reject everything eg:
3792 but this probably for advanced users...
3793 <sect1>reject/wcy <call> [input] [0-9] <pattern> (8)
3797 <bf>reject/wcy <call> [input] [0-9] <pattern></bf> WCY filter sysop version
3801 This version allows a sysop to set a filter for a callsign as well as the
3802 default for nodes and users eg:-
3805 reject/wcy gb7djk all
3808 <sect1>reject/wcy [0-9] <pattern> (0)
3812 <bf>reject/wcy [0-9] <pattern></bf> set a 'reject' WCY filter
3816 It is unlikely that you will want to do this, but if you do then you can
3817 filter on the following fields:-
3820 by <prefixes> eg: G,M,2
3821 origin <prefixes>
3822 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3823 origin_itu <prefixes or numbers> or: G,GM,GW
3824 origin_zone <prefixes or numbers>
3825 by_dxcc <prefixes or numbers>
3826 by_itu <prefixes or numbers>
3827 by_zone <prefixes or numbers>
3828 channel <prefixes>
3831 There are no examples because WCY Broadcasts only come from one place and
3832 you either want them or not (see UNSET/WCY if you don't want them).
3834 This command is really provided for future use.
3836 See HELP FILTER for information.
3837 <sect1>reject/wwv <call> [input] [0-9] <pattern> (8)
3841 <bf>reject/wwv <call> [input] [0-9] <pattern></bf> WWV filter sysop version
3845 This version allows a sysop to set a filter for a callsign as well as the
3846 default for nodes and users eg:-
3849 reject/wwv db0sue-7 1 by_zone 4
3850 reject/wwv node_default all
3854 reject/wwv user_default by W
3857 <sect1>reject/wwv [0-9] <pattern> (0)
3861 <bf>reject/wwv [0-9] <pattern></bf> set a 'reject' WWV filter
3865 It is unlikely that you will want to do this, but if you do then you can
3866 filter on the following fields:-
3869 by <prefixes> eg: G,M,2
3870 origin <prefixes>
3871 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
3872 origin_itu <prefixes or numbers> or: G,GM,GW
3873 origin_zone <prefixes or numbers>
3874 by_dxcc <prefixes or numbers>
3875 by_itu <prefixes or numbers>
3876 by_zone <prefixes or numbers>
3877 channel <prefixes>
3883 reject/wwv by_zone 14,15,16
3886 is probably the only useful thing to do (which will only show WWV broadcasts
3887 by stations in the US).
3889 See HELP FILTER for information.
3894 <bf>reply</bf> Reply (privately) to the last message that you have read
3898 <sect1>reply <msgno> (0)
3902 <bf>reply <msgno></bf> Reply (privately) to the specified message
3906 <sect1>reply b <msgno> (0)
3910 <bf>reply b <msgno></bf> Reply as a Bulletin to the specified message
3914 <sect1>reply noprivate <msgno> (0)
3918 <bf>reply noprivate <msgno></bf> Reply as a Bulletin to the specified message
3922 <sect1>reply rr <msgno> (0)
3926 <bf>reply rr <msgno></bf> Reply to the specified message with read receipt
3930 You can reply to a message and the subject will automatically have
3931 "Re:" inserted in front of it, if it isn't already present.
3933 You can also use all the extra qualifiers such as RR, PRIVATE,
3934 NOPRIVATE, B that you can use with the SEND command (see SEND
3935 for further details)
3936 <sect1>save [-d -t -a] <filename> "<cmd>" [...] (9)
3940 <bf>save [-d -t -a] <filename> "<cmd>" [...]</bf> Save command output to a file
3944 This sysop only cammand allows you to save the output of one or more
3945 commands to a file. For example:-
3948 save /spider/packclus/dxstats show/dxstat
3951 will save the output of the normal command "show/dxstat" to the file
3952 "dxstats" in the files area.
3954 You can have some extra flags to the save which will either
3955 date stamp or time stamp or both the filename so:-
3958 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
3959 save -t /tmp/a <cmd> creates /tmp/a_2301Z
3960 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
3963 The -a flag means append to the file instead of overwriting it.
3965 You can have more than one command on the line, to do this you MUST
3966 enclose each command in double quotes (") eg:-
3969 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
3975 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
3978 You can only write into places that the cluster has permission for (which
3979 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
3980 need to create any directories you want to put stuff in beforehand as well.
3982 It is likely that you will want to run these commands in a crontab type
3983 situation. You would do that something like:-
3986 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
3989 Note that you still enclose each command with (") characters but you must
3990 enclose the entire save command in (') characters.
3992 Now in fact, this can be varied if you know what you are doing. See the
3993 admin manual for more details.
3995 <sect1>send <call> [<call> ...] (0)
3999 <bf>send <call> [<call> ...]</bf> Send a message to one or more callsigns
4003 <sect1>send copy <msgno> <call> (0)
4007 <bf>send copy <msgno> <call></bf> Send a copy of a message to someone
4011 <sect1>send noprivate <call> (0)
4015 <bf>send noprivate <call></bf> Send a message to all stations
4019 All the SEND commands will create a message which will be sent either to
4020 an individual callsign or to one of the 'bulletin' addresses.
4022 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
4023 it will mark the message as personal and send it to the cluster node that
4024 that callsign is connected to. If the <call> you have specified is in fact
4025 a known bulletin category on your node (eg: ALL) then the message should
4026 automatically become a bulletin.
4028 You can have more than one callsign in all of the SEND commands.
4030 You can have multiple qualifiers so that you can have for example:-
4033 SEND RR COPY 123 PRIVATE G1TLH G0RDI
4036 which should send a copy of message 123 to G1TLH and G0RDI and you will
4037 receive a read receipt when they have read the message.
4039 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
4040 SP is an alias for SEND PRIVATE
4042 The system will ask you for a subject. Conventionally this should be
4043 no longer than 29 characters for compatibility. Most modern cluster
4044 software should accept more.
4046 You will now be prompted to start entering your text.
4048 You finish the message by entering '/EX' on a new line. For instance:
4057 If you have started a message and you don't want to keep it then you
4058 can abandon the message with '/ABORT' on a new line, like:-
4063 oh I just can't be bothered with this
4067 If you abort the message it will NOT be sent.
4069 When you are entering the text of your message, most normal output (such
4070 as DX announcements and so on are suppressed and stored for latter display
4071 (upto 20 such lines are stored, as new ones come along, so the oldest
4074 Also, you can enter normal commands commands (and get the output
4075 immediately) whilst in the middle of a message. You do this by typing
4076 the command preceeded by a '/' character on a new line, so:-
4079 /dx g1tlh 144010 strong signal
4082 Will issue a dx annoucement to the rest of the cluster.
4084 Also, you can add the output of a command to your message by preceeding
4085 the command with '//', thus :-
4091 This will show YOU the output from SH/VHFTABLE and also store it in the
4094 You can carry on with the message until you are ready to send it.
4095 <sect1>send private <call> (0)
4099 <bf>send private <call></bf> Send a personal message
4103 <sect1>send rr <call> (0)
4107 <bf>send rr <call></bf> Send a message and ask for a read receipt
4111 <sect1>set/address <your address> (0)
4115 <bf>set/address <your address></bf> Record your postal address
4119 <sect1>set/announce (0)
4123 <bf>set/announce</bf> Allow announce messages to come out on your terminal
4127 <sect1>set/anntalk (0)
4131 <bf>set/anntalk</bf> Allow talk like announce messages on your terminal
4135 <sect1>set/arcluster <call> [<call>..] (5)
4139 <bf>set/arcluster <call> [<call>..]</bf> Make the callsign an AR-Cluster node
4143 <sect1>set/baddx <call>.. (8)
4147 <bf>set/baddx <call>..</bf> Stop callsigns in a dx spot being propagated
4151 <sect1>set/badnode <call>.. (8)
4155 <bf>set/badnode <call>..</bf> Stop spots from this node being propagated
4159 <sect1>set/badspotter <call>.. (8)
4163 <bf>set/badspotter <call>..</bf> Stop spots from this callsign being propagated
4167 <sect1>set/badword <word>.. (8)
4171 <bf>set/badword <word>..</bf> Stop things with this word being propagated
4175 <sect1>set/bbs <call> [<call>..] (5)
4179 <bf>set/bbs <call> [<call>..]</bf> Make the callsign a BBS
4187 <bf>set/beep</bf> Add a beep to DX and other messages on your terminal
4191 <sect1>set/clx <call> [<call>..] (5)
4195 <bf>set/clx <call> [<call>..]</bf> Make the callsign an CLX node
4199 <sect1>set/debug <name> (9)
4203 <bf>set/debug <name></bf> Add a debug level to the debug set
4211 <bf>set/dx</bf> Allow DX messages to come out on your terminal
4219 <bf>set/dxcq</bf> Show CQ Zones on the end of DX announcements
4223 <sect1>set/dxgrid (0)
4227 <bf>set/dxgrid</bf> Allow QRA Grid Squares on the end of DX announcements
4231 <sect1>set/dxitu (0)
4235 <bf>set/dxitu</bf> Show ITU Zones on the end of DX announcements
4239 <sect1>set/dxnet <call> [<call>..] (5)
4243 <bf>set/dxnet <call> [<call>..]</bf> Make the callsign an DXNet node
4251 <bf>set/echo</bf> Make the cluster echo your input
4255 <sect1>set/email <email> ... (0)
4259 <bf>set/email <email> ...</bf> Set email address(es) and forward your personals
4267 <bf>set/here</bf> Tell the system you are present at your terminal
4271 <sect1>set/homenode <node> (0)
4275 <bf>set/homenode <node> </bf> Set your normal cluster callsign
4279 Tell the cluster system where you normally connect to. Any Messages sent
4280 to you will normally find their way there should you not be connected.
4286 <sect1>set/hops <call> ann|spots|route|wwv|wcy <n> (8)
4290 <bf>set/hops <call> ann|spots|route|wwv|wcy <n></bf> Set hop count
4294 <sect1>set/isolate (9)
4298 <bf>set/isolate</bf> Isolate a node from the rest of the network
4302 Connect a node to your system in such a way that you are a full protocol
4303 member of its network and can see all spots on it, but nothing either leaks
4304 out from it nor goes back into from the rest of the nodes connected to you.
4306 You can potentially connect several nodes in this way.
4308 <sect1>set/language <lang> (0)
4312 <bf>set/language <lang></bf> Set the language you want to use
4316 You can select the language that you want the cluster to use. Currently
4317 the languages available are en (English), de (German), es (Spanish),
4318 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
4319 <sect1>set/location <lat & long> (0)
4323 <bf>set/location <lat & long></bf> Set your latitude and longitude
4327 <sect1>set/lockout <call> (9)
4331 <bf>set/lockout <call></bf> Stop a callsign connecting to the cluster
4335 <sect1>set/logininfo (0)
4339 <bf>set/logininfo</bf> Inform when a station logs in locally
4343 <sect1>set/name <your name> (0)
4347 <bf>set/name <your name></bf> Set your name
4351 Tell the system what your name is eg:-
4356 <sect1>set/node <call> [<call>..] (5)
4360 <bf>set/node <call> [<call>..]</bf> Make the callsign an AK1A cluster
4364 Tell the system that the call(s) are to be treated as AK1A cluster and
4365 fed PC Protocol rather normal user commands.
4366 <sect1>set/obscount <count> <call> (8)
4370 <bf>set/obscount <count> <call></bf> Set the 'pump-up' obscelence PING counter
4374 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
4375 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
4376 counter which is decremented on every outgoing ping and then reset to
4377 the 'obscount' value on every incoming ping. The default value of this
4380 What this means is that a neighbouring node will be pinged twice at
4381 (default) 300 second intervals and if no reply has been heard just before
4382 what would be the third attempt, that node is disconnected.
4384 If a ping is heard then the obscount is reset to the full value. Using
4385 default values, if a node has not responded to a ping within 15 minutes,
4388 You can set this parameter between 1 and 9.
4390 It is STRONGLY recommended that you don't change the default.
4391 <sect1>set/page <lines per page> (0)
4395 <bf>set/page <lines per page></bf> Set the lines per page
4399 Tell the system how many lines you wish on a page when the number of line
4400 of output from a command is more than this. The default is 20. Setting it
4401 explicitly to 0 will disable paging.
4407 The setting is stored in your user profile.
4408 <sect1>set/password (0)
4412 <bf>set/password</bf> Set your own password
4416 This command only works for a 'telnet' user (currently). It will
4417 only work if you have a password already set. This initial password
4418 can only be set by the sysop.
4420 When you execute this command it will ask you for your old password,
4421 then ask you to type in your new password twice (to make sure you
4422 get it right). You may or may not see the data echoed on the screen
4423 as you type, depending on the type of telnet client you have.
4424 <sect1>set/password <callsign> <string> (9)
4428 <bf>set/password <callsign> <string></bf> Set a users password
4432 The password for a user can only be set by a full sysop. The string
4433 can contain any characters.
4435 The way this field is used depends on context. If it is being used in
4436 the SYSOP command context then you are offered 5 random numbers and you
4437 have to supply the corresponding letters. This is now mainly for ax25
4440 If it is being used on incoming telnet connections then, if a password
4444 set/var $main::passwdreq = 1
4447 command is executed in the startup script, then a password prompt is
4448 given after the normal 'login: ' prompt.
4449 <sect1>set/pinginterval <time> <nodecall> (9)
4453 <bf>set/pinginterval <time> <nodecall></bf> Set ping time to neighbouring nodes
4457 As from release 1.35 all neighbouring nodes are pinged at regular intervals
4458 in order to determine the rolling quality of the link and, in future, to
4459 affect routing decisions. The default interval is 300 secs or 5 minutes.
4461 You can use this command to set a different interval. Please don't.
4463 But if you do the value you enter is treated as minutes up 30 and seconds
4464 for numbers greater than that.
4466 This is used also to help determine when a link is down at the far end
4467 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
4468 for more information.
4470 If you must change it (and it may be useful for internet connected nodes
4471 on dynamic IP addresses that go away after a set time of usage) the time
4472 can be specified as:-
4475 5 which if less than 30 is converted to minutes otherwise is
4476 taken as the no of seconds between pings.
4482 Please be aware that this causes traffic to occur on the link, setting
4483 this value too low may annoy your neighbours beyond the point of
4486 You can switch this off by setting it to 0.
4487 <sect1>set/privilege <n> <call> [<call..] (9)
4491 <bf>set/privilege <n> <call> [<call..]</bf> Set privilege level on a call
4495 Set the privilege level on a callsign. The privilege levels that pertain
4496 to commands are as default:-
4499 1 - allow remote nodes normal user RCMDs
4500 5 - various privileged commands (including shutdown, but not disc-
4501 connect), the normal level for another node.
4502 8 - more privileged commands (including disconnect)
4503 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
4506 If you are a sysop and you come in as a normal user on a remote connection
4507 your privilege will automatically be set to 0.
4508 <sect1>set/prompt <string> (0)
4512 <bf>set/prompt <string></bf> Set your prompt to <string>
4516 <sect1>set/qra <locator> (0)
4520 <bf>set/qra <locator></bf> Set your QRA Grid locator
4524 Tell the system what your QRA (or Maidenhead) locator is. If you have not
4525 done a SET/LOCATION then your latitude and longitude will be set roughly
4526 correctly (assuming your locator is correct ;-). For example:-
4531 <sect1>set/qth <your qth> (0)
4535 <bf>set/qth <your qth></bf> Set your QTH
4539 Tell the system where you are. For example:-
4541 SET/QTH East Dereham, Norfolk
4544 <sect1>set/register <call> ... (9)
4548 <bf>set/register <call> ...</bf> Mark a user as registered
4552 <sect1>set/spider <call> [<call>..] (5)
4556 <bf>set/spider <call> [<call>..]</bf> Make the callsign an DXSpider node
4560 Tell the system that the call(s) are to be treated as DXSpider node and
4561 fed new style DX Protocol rather normal user commands.
4562 <sect1>set/sys_location <lat & long> (9)
4566 <bf>set/sys_location <lat & long></bf> Set your cluster latitude and longitude
4570 In order to get accurate headings and such like you must tell the system
4571 what your latitude and longitude is. If you have not yet done a SET/QRA
4572 then this command will set your QRA locator for you. For example:-
4574 SET/LOCATION 52 22 N 0 57 E
4577 <sect1>set/sys_qra <locator> (9)
4581 <bf>set/sys_qra <locator></bf> Set your cluster QRA Grid locator
4589 <bf>set/talk</bf> Allow TALK messages to come out on your terminal
4593 <sect1>set/usdb <call> <state> <city> (9)
4597 <bf>set/usdb <call> <state> <city></bf> add/update a US DB callsign
4601 This command allows you to add or alter a callsign in the US state
4602 database. Use with extreme caution. Anything you do here will be
4603 overwritten by any weekly updates that affect this callsign
4606 set/usdb g1tlh nh downtown rindge
4609 see also DELETE/USDB
4610 <sect1>set/usstate (0)
4614 <bf>set/usstate</bf> Allow US State info on the end of DX announcements
4622 <bf>set/wcy</bf> Allow WCY messages to come out on your terminal
4630 <bf>set/wwv</bf> Allow WWV messages to come out on your terminal
4638 <bf>set/wx</bf> Allow WX messages to come out on your terminal
4642 <sect1>show/baddx (1)
4646 <bf>show/baddx</bf> Show all the bad dx calls in the system
4650 Display all the bad dx callsigns in the system, see SET/BADDX
4651 for more information.
4652 <sect1>show/badnode (1)
4656 <bf>show/badnode</bf> Show all the bad nodes in the system
4660 Display all the bad node callsigns in the system, see SET/BADNODE
4661 for more information.
4662 <sect1>show/badspotter (1)
4666 <bf>show/badspotter</bf> Show all the bad spotters in the system
4670 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
4671 for more information.
4672 <sect1>show/badword (1)
4676 <bf>show/badword</bf> Show all the bad words in the system
4680 Display all the bad words in the system, see SET/BADWORD
4681 for more information.
4682 <sect1>show/chat [<group>] [<lines>] (0)
4686 <bf>show/chat [<group>] [<lines>]</bf> Show any chat or conferencing
4690 This command allows you to see any chat or conferencing that has
4691 occurred whilst you were away. SHOW/CHAT on its own will show data for
4692 all groups. If you use a group name then it will show only chat for
4694 <sect1>show/configuration [<node>] (0)
4698 <bf>show/configuration [<node>]</bf> Show all the nodes and users visible
4702 This command allows you to see all the users that can be seen
4703 and the nodes to which they are connected.
4705 This command is normally abbreviated to: sh/c
4707 Normally, the list returned will be just for the nodes from your
4708 country (because the list otherwise will be very long).
4714 will produce a complete list of all nodes.
4716 BE WARNED: the list that is returned can be VERY long
4718 It is possible to supply a node or part of a prefix and you will get
4719 a list of the users for that node or list of nodes starting with
4730 <sect1>show/configuration/node (0)
4734 <bf>show/configuration/node</bf> Show all the nodes connected locally
4738 Show all the nodes connected to this node.
4739 <sect1>show/connect (1)
4743 <bf>show/connect</bf> Show all the active connections
4747 This command shows information on all the active connections known to
4748 the node. This command gives slightly more information than WHO.
4749 <sect1>show/contest <year and month> (0)
4753 <bf>show/contest <year and month></bf> Show all the contests for a month
4757 Show all known contests which are maintained at http://www.sk3bg.se/contest/
4758 for a particular month or year. The format is reasonably flexible.
4766 <sect1>show/date [<prefix>|<callsign>] (0)
4770 <bf>show/date [<prefix>|<callsign>]</bf> Show the local time
4774 This is very nearly the same as SHOW/TIME, the only difference the format
4775 of the date string if no arguments are given.
4777 If no prefixes or callsigns are given then this command returns the local
4778 time and UTC as the computer has it right now. If you give some prefixes
4779 then it will show UTC and UTC + the local offset (not including DST) at
4780 the prefixes or callsigns that you specify.
4781 <sect1>show/db0sdx <callsign> (0)
4785 <bf>show/db0sdx <callsign></bf> Show QSL infomation from DB0SDX database
4789 This command queries the DB0SDX QSL server on the internet
4790 and returns any information available for that callsign. This service
4791 is provided for users of this software by http://www.qslinfo.de.
4793 See also SHOW/QRZ, SHOW/WM7D.
4794 <sect1>show/debug (9)
4798 <bf>show/debug</bf> Show what levels of debug information you are logging
4806 <bf>show/dx</bf> Interrogate the spot database
4810 If you just type SHOW/DX you will get the last so many spots
4811 (sysop configurable, but usually 10).
4813 In addition you can add any number of these commands in very nearly
4814 any order to the basic SHOW/DX command, they are:-
4817 on <band> - eg 160m 20m 2m 23cm 6mm
4818 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
4819 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
4820 <from>-<to>
4824 <number> - the number of spots you want
4825 <from>-<to> - <from> spot no <to> spot no in the selected list
4826 <from>/<to>
4830 <prefix> - for a spotted callsign beginning with <prefix>
4831 *<suffix> - for a spotted callsign ending in <suffix>
4832 *<string>* - for a spotted callsign containing <string>
4836 day <number> - starting <number> days ago
4837 day <from>-<to> - <from> days <to> days ago
4838 <from>/<to>
4842 info <text> - any spots containing <text> in the info or remarks
4846 by <call> - any spots spotted by <call> (spotter <call> is the
4851 qsl - this automatically looks for any qsl info on the call
4852 held in the spot database.
4856 iota [<iota>] - If the iota island number is missing it will look for
4857 the string iota and anything which looks like an iota
4858 island number. If you specify then it will look for
4863 qra [<locator>] - this will look for the specific locator if you specify
4864 one or else anything that looks like a locator.
4868 dxcc - treat the prefix as a 'country' and look for spots
4869 from that country regardless of actual prefix.
4874 You can also use this with the 'by' keyword so
4884 SH/DX on 20m info iota
4885 SH/DX 9a on vhf day 30
4891 SH/DX dxcc oq2 by w dxcc
4894 <sect1>show/dxcc <prefix> (0)
4898 <bf>show/dxcc <prefix></bf> Interrogate the spot database by country
4902 This command takes the <prefix> (which can be a full or partial
4903 callsign if desired), looks up which internal country number it is
4904 and then displays all the spots as per SH/DX for that country.
4906 This is now an alias for 'SHOW/DX DXCC'
4908 The options for SHOW/DX also apply to this command.
4913 SH/DXCC W on 20m iota
4916 This can be done with the SHOW/DX command like this:-
4920 SH/DX dxcc w on 20m iota
4923 <sect1>show/dxqsl <callsign> (0)
4927 <bf>show/dxqsl <callsign></bf> Show any QSL info gathered from spots
4931 The node collects information from the comment fields in spots (things
4932 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
4934 This command allows you to interrogate that database and if the callsign
4935 is found will display the manager(s) that people have spotted. This
4936 information is NOT reliable, but it is normally reasonably accurate if
4937 it is spotted enough times.
4945 You can check the raw input spots yourself with:-
4951 This gives you more background information.
4952 <sect1>show/dxstats [days] [date] (0)
4956 <bf>show/dxstats [days] [date]</bf> Show the DX Statistics
4960 Show the total DX spots for the last <days> no of days (default is 31),
4961 starting from a <date> (default: today).
4962 <sect1>show/files [<filearea> [<string>]] (0)
4966 <bf>show/files [<filearea> [<string>]]</bf> List the contents of a filearea
4970 SHOW/FILES on its own will show you a list of the various fileareas
4971 available on the system. To see the contents of a particular file
4974 SH/FILES <filearea>
4976 where <filearea> is the name of the filearea you want to see the
4979 You can also use shell globbing characters like '*' and '?' in a
4980 string to see a selection of files in a filearea eg:-
4982 SH/FILES bulletins arld*
4985 See also TYPE - to see the contents of a file.
4986 <sect1>show/filter (0)
4990 <bf>show/filter</bf> Show the contents of all the filters you have set
4994 Show the contents of all the filters that are set. This command displays
4995 all the filters set - for all the various categories.
4996 <sect1>show/hfstats [days] [date] (0)
5000 <bf>show/hfstats [days] [date]</bf> Show the HF DX Statistics
5004 Show the HF DX spots breakdown by band for the last <days> no of days
5005 (default is 31), starting from a <date> (default: today).
5006 <sect1>show/hftable [days] [date] [prefix ...] (0)
5010 <bf>show/hftable [days] [date] [prefix ...]</bf> Show the HF DX Spotter Table
5014 Show the HF DX Spotter table for the list of prefixes for the last
5015 <days> no of days (default is 31), starting from a <date> (default: today).
5017 If there are no prefixes then it will show the table for your country.
5019 Remember that some countries have more than one "DXCC country" in them
5020 (eg G :-), to show them (assuming you are not in G already which is
5021 specially treated in the code) you must list all the relevant prefixes
5024 sh/hftable g gm gd gi gj gw gu
5027 Note that the prefixes are converted into country codes so you don't have
5028 to list all possible prefixes for each country.
5030 If you want more or less days than the default simply include the
5031 number you require:-
5037 If you want to start at a different day, simply add the date in some
5041 sh/hftable 2 25nov02
5042 sh/hftable 2 25-nov-02
5044 sh/hftable 2 25/11/02
5047 This will show the stats for your DXCC for that CQWW contest weekend.
5049 You can specify either prefixes or full callsigns (so you can see how you
5050 did against all your mates). You can also say 'all' which will then print
5051 the worldwide statistics.
5057 <sect1>show/hops <call> [ann|spots|route|wcy|wwv] (8)
5061 <bf>show/hops <call> [ann|spots|route|wcy|wwv]</bf> Show the hop counts for a node
5065 This command shows the hop counts set up for a node. You can specify
5066 which category you want to see. If you leave the category out then
5067 all the categories will be listed.
5069 <sect1>show/isolate (1)
5073 <bf>show/isolate</bf> Show list of ISOLATED nodes
5077 <sect1>show/lockout <prefix>|all (9)
5081 <bf>show/lockout <prefix>|all</bf> Show the list of locked out or excluded callsigns
5085 <sect1>show/log [<callsign>] (8)
5089 <bf>show/log [<callsign>]</bf> Show excerpts from the system log
5093 This command outputs a short section of the system log. On its own
5094 it will output a general logfile. With the optional callsign it will
5095 show output from the log associated with that callsign.
5096 <sect1>show/moon [ndays] [<prefix>|<callsign>] (0)
5100 <bf>show/moon [ndays] [<prefix>|<callsign>]</bf> Show Moon rise and set times
5104 Show the Moon rise and set times for a (list of) prefixes or callsigns,
5105 together with the azimuth and elevation of the sun currently at those
5108 If you don't specify any prefixes or callsigns, it will show the times for
5109 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
5110 together with the current azimuth and elevation.
5112 In addition, it will show the illuminated fraction of the moons disk.
5114 If all else fails it will show the Moonrise and set times for the node
5115 that you are connected to.
5124 You can also use this command to see into the past or the future, so
5125 if you want to see yesterday's times then do:-
5131 or in three days time:-
5137 Upto 366 days can be checked both in the past and in the future.
5139 Please note that the rise and set times are given as the UT times of rise and
5140 set on the requested UT day.
5141 <sect1>show/muf <prefix> [<hours>][long] (0)
5145 <bf>show/muf <prefix> [<hours>][long]</bf> Show the likely propagation to a prefix
5149 This command allow you to estimate the likelihood of you contacting
5150 a station with the prefix you have specified. The output assumes a modest
5151 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
5153 The result predicts the most likely operating frequencies and signal
5154 levels for high frequency (shortwave) radio propagation paths on
5155 specified days of the year and hours of the day. It is most useful for
5156 paths between 250 km and 6000 km, but can be used with reduced accuracy
5157 for paths shorter or longer than this.
5159 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
5160 used to predict the MUF given the predicted flux, day of the year,
5161 hour of the day and geographic coordinates of the transmitter and
5162 receiver. This routine is reasonably accurate for the purposes here,
5163 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
5164 than the programs used by major shortwave broadcasting organizations,
5165 such as the Voice of America.
5167 The command will display some header information detailing its
5168 assumptions, together with the locations, latitude and longitudes and
5169 bearings. It will then show UTC (UT), local time at the other end
5170 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
5171 (Zen) and the likely signal strengths. Then for each frequency for which
5172 the system thinks there is a likelihood of a circuit it prints a value.
5174 The value is currently a likely S meter reading based on the conventional
5175 6dB / S point scale. If the value has a '+' appended it means that it is
5176 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
5177 there is likely to be much fading and by an 's' that the signal is likely
5180 By default SHOW/MUF will show the next two hours worth of data. You
5181 can specify anything up to 24 hours worth of data by appending the no of
5182 hours required after the prefix. For example:-
5191 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
5192 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
5193 Location Lat / Long Azim
5194 East Dereham, Norfolk 52 41 N 0 57 E 47
5195 United-States-W 43 0 N 87 54 W 299
5196 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
5197 18 23 11.5 -35 mS0+ mS2 S3
5198 19 0 11.2 -41 mS0+ mS2 S3
5201 indicating that you will have weak, fading circuits on top band and
5202 80m but usable signals on 40m (about S3).
5210 will get you the above display, but with the next 24 hours worth of
5218 Gives you an estimate of the long path propagation characterics. It
5219 should be noted that the figures will probably not be very useful, nor
5220 terrible accurate, but it is included for completeness.
5221 <sect1>show/newconfiguration [<node>] (0)
5225 <bf>show/newconfiguration [<node>]</bf> Show all the nodes and users visible
5229 This command allows you to see all the users that can be seen
5230 and the nodes to which they are connected.
5232 This command produces essentially the same information as
5233 SHOW/CONFIGURATION except that it shows all the duplication of
5234 any routes that might be present It also uses a different format
5235 which may not take up quite as much space if you don't have any
5238 BE WARNED: the list that is returned can be VERY long
5239 <sect1>show/newconfiguration/node (0)
5243 <bf>show/newconfiguration/node</bf> Show all the nodes connected locally
5247 Show all the nodes connected to this node in the new format.
5248 <sect1>show/node [<callsign> ...] (1)
5252 <bf>show/node [<callsign> ...]</bf> Show the type and version number of nodes
5256 Show the type and version (if connected) of the nodes specified on the
5257 command line. If no callsigns are specified then a sorted list of all
5258 the non-user callsigns known to the system will be displayed.
5259 <sect1>show/prefix <callsign> (0)
5263 <bf>show/prefix <callsign></bf> Interrogate the prefix database
5267 This command takes the <callsign> (which can be a full or partial
5268 callsign or a prefix), looks up which internal country number
5269 it is and then displays all the relevant prefixes for that country
5270 together with the internal country no, the CQ and ITU regions.
5273 <sect1>show/program (5)
5277 <bf>show/program</bf> Show the locations of all the included program modules
5281 Show the name and location where every program module was load from. This
5282 is useful for checking where you think you have loaded a .pm file from.
5283 <sect1>show/qra <lat> <long> (0)
5287 <bf>show/qra <lat> <long></bf> Convert lat/long to a QRA Grid locator
5291 This is a multipurpose command that allows you either to calculate the
5292 distance and bearing between two locators or (if only one locator is
5293 given on the command line) the distance and beraing from your station
5294 to the locator. For example:-
5301 The first example will show the distance and bearing to the locator from
5302 yourself, the second example will calculate the distance and bearing from
5303 the first locator to the second. You can use 4 or 6 character locators.
5305 It is also possible to convert a latitude and longitude to a locator by
5306 using this command with a latitude and longitude as an argument, for
5310 SH/QRA 52 41 N 0 58 E
5313 <sect1>show/qra <locator> [<locator>] (0)
5317 <bf>show/qra <locator> [<locator>]</bf> Show distance between QRA Grid locators
5321 <sect1>show/qrz <callsign> (0)
5325 <bf>show/qrz <callsign></bf> Show any callbook details on a callsign
5329 This command queries the QRZ callbook server on the internet
5330 and returns any information available for that callsign. This service
5331 is provided for users of this software by http://www.qrz.com
5333 See also SHOW/WM7D for an alternative.
5334 <sect1>show/registered [<prefix>] (9)
5338 <bf>show/registered [<prefix>]</bf> Show the registered users
5342 <sect1>show/route <callsign> ... (0)
5346 <bf>show/route <callsign> ...</bf> Show the route to the callsign
5350 This command allows you to see to which node the callsigns specified are
5351 connected. It is a sort of inverse sh/config.
5357 <sect1>show/satellite <name> [<hours> <interval>] (0)
5361 <bf>show/satellite <name> [<hours> <interval>]</bf> Show tracking data
5365 Show the tracking data from your location to the satellite of your choice
5366 from now on for the next few hours.
5368 If you use this command without a satellite name it will display a list
5369 of all the satellites known currently to the system.
5371 If you give a name then you can obtain tracking data of all the passes
5372 that start and finish 5 degrees below the horizon. As default it will
5373 give information for the next three hours for every five minute period.
5375 You can alter the number of hours and the step size, within certain
5378 Each pass in a period is separated with a row of '-----' characters
5384 SH/SAT FENGYUN1 12 2
5387 <sect1>show/station all [<regex>] (6)
5391 <bf>show/station all [<regex>]</bf> Show list of users in the system
5395 <sect1>show/station [<callsign> ..] (0)
5399 <bf>show/station [<callsign> ..]</bf> Show information about a callsign
5403 Show the information known about a callsign and whether (and where)
5404 that callsign is connected to the cluster.
5410 If no callsign is given then show the information for yourself.
5411 <sect1>show/sun [ndays] [<prefix>|<callsign>] (0)
5415 <bf>show/sun [ndays] [<prefix>|<callsign>]</bf> Show sun rise and set times
5419 Show the sun rise and set times for a (list of) prefixes or callsigns,
5420 together with the azimuth and elevation of the sun currently at those
5423 If you don't specify any prefixes or callsigns, it will show the times for
5424 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
5425 together with the current azimuth and elevation.
5427 If all else fails it will show the sunrise and set times for the node
5428 that you are connected to.
5434 SH/SUN G1TLH K9CW ZS
5437 You can also use this command to see into the past or the future, so
5438 if you want to see yesterday's times then do:-
5444 or in three days time:-
5450 Upto 366 days can be checked both in the past and in the future.
5452 Please note that the rise and set times are given as the UT times of rise
5453 and set on the requested UT day.
5454 <sect1>show/time [<prefix>|<callsign>] (0)
5458 <bf>show/time [<prefix>|<callsign>]</bf> Show the local time
5462 If no prefixes or callsigns are given then this command returns the local
5463 time and UTC as the computer has it right now. If you give some prefixes
5464 then it will show UTC and UTC + the local offset (not including DST) at
5465 the prefixes or callsigns that you specify.
5466 <sect1>show/usdb [call ..] (0)
5470 <bf>show/usdb [call ..]</bf> Show information held on the FCC Call database
5474 Show the City and State of a Callsign held on the FCC database if
5475 his is being run on this system, eg:-
5481 <sect1>show/vhfstats [days] [date] (0)
5485 <bf>show/vhfstats [days] [date]</bf> Show the VHF DX Statistics
5489 Show the VHF DX spots breakdown by band for the last
5490 <days> no of days (default is 31), starting from a date (default: today).
5491 <sect1>show/vhftable [days] [date] [prefix ...] (0)
5495 <bf>show/vhftable [days] [date] [prefix ...]</bf> Show the VHF DX Spotter Table
5499 Show the VHF DX Spotter table for the list of prefixes for the last
5500 <days> no of days (default is 31), starting from a date (default: today).
5502 If there are no prefixes then it will show the table for your country.
5504 Remember that some countries have more than one "DXCC country" in them
5505 (eg G :-), to show them (assuming you are not in G already which is
5506 specially treated in the code) you must list all the relevant prefixes
5509 sh/vhftable g gm gd gi gj gw gu
5512 Note that the prefixes are converted into country codes so you don't have
5513 to list all possible prefixes for each country.
5515 If you want more or less days than the default simply include the
5516 number you require:-
5522 If you want to start at a different day, simply add the date in some
5526 sh/vhftable 2 25nov02
5527 sh/vhftable 2 25-nov-02
5528 sh/vhftable 2 021125
5529 sh/vhftable 2 25/11/02
5532 This will show the stats for your DXCC for that CQWW contest weekend.
5534 You can specify either prefixes or full callsigns (so you can see how you
5535 did against all your mates). You can also say 'all' which will then print
5536 the worldwide statistics.
5546 <bf>show/wcy</bf> Show last 10 WCY broadcasts
5550 <sect1>show/wcy <n> (0)
5554 <bf>show/wcy <n></bf> Show last <n> WCY broadcasts
5558 Display the most recent WCY information that has been received by the system
5560 <sect1>show/wm7d <callsign> (0)
5564 <bf>show/wm7d <callsign></bf> Show callbook details on a US callsigns
5568 This command queries the WM7D callbook server on the internet
5569 and returns any information available for that US callsign. This service
5570 is provided for users of this software by http://www.wm7d.net.
5577 <bf>show/wwv</bf> Show last 10 WWV broadcasts
5581 <sect1>show/wwv <n> (0)
5585 <bf>show/wwv <n></bf> Show last <n> WWV broadcasts
5589 Display the most recent WWV information that has been received by the system
5594 <bf>shutdown</bf> Shutdown the cluster
5598 Shutdown the cluster and disconnect all the users
5599 <sect1>spoof <call> <command> (9)
5603 <bf>spoof <call> <command></bf> Do a command as though you are another user
5607 This command is provided so that sysops can set a user's parameters without
5608 me having to write a special 'sysop' version for every user command. It
5609 allows you to pretend that you are doing the command as the user you specify.
5614 SPOOF G1TLH set/name Dirk
5615 SPOOF G1TLH set/qra JO02LQ
5618 <sect1>stat/channel [<callsign>] (5)
5622 <bf>stat/channel [<callsign>]</bf> Show the status of a channel on the cluster
5626 Show the internal status of the channel object either for the channel that
5627 you are on or else for the callsign that you asked for.
5629 Only the fields that are defined (in perl term) will be displayed.
5630 <sect1>stat/db <dbname> (5)
5634 <bf>stat/db <dbname></bf> Show the status of a database
5638 Show the internal status of a database descriptor.
5640 Depending on your privilege level you will see more or less information.
5641 This command is unlikely to be of much use to anyone other than a sysop.
5646 <bf>stat/msg</bf> Show the status of the message system
5650 <sect1>stat/msg <msgno> (1)
5654 <bf>stat/msg <msgno></bf> Show the status of a message
5658 This command shows the internal status of a message and includes information
5659 such as to whom it has been forwarded, its size, origin etc etc.
5661 If no message number is given then the status of the message system is
5663 <sect1>stat/route_node <callsign> (5)
5667 <bf>stat/route_node <callsign></bf> Show the data in a Route::Node object
5671 <sect1>stat/route_node all (5)
5675 <bf>stat/route_node all</bf> Show list of all Route::Node objects
5679 <sect1>stat/route_user <callsign> (5)
5683 <bf>stat/route_user <callsign></bf> Show the data in a Route::User object
5687 <sect1>stat/route_user all (5)
5691 <bf>stat/route_user all</bf> Show list of all Route::User objects
5695 <sect1>stat/user [<callsign>] (5)
5699 <bf>stat/user [<callsign>]</bf> Show the full status of a user
5703 Shows the full contents of a user record including all the secret flags
5706 Only the fields that are defined (in perl term) will be displayed.
5711 <bf>sysop</bf> Regain your privileges if you login remotely
5715 The system automatically reduces your privilege level to that of a
5716 normal user if you login in remotely. This command allows you to
5717 regain your normal privilege level. It uses the normal system: five
5718 numbers are returned that are indexes into the character array that is
5719 your assigned password (see SET/PASSWORD). The indexes start from
5722 You are expected to return a string which contains the characters
5723 required in the correct order. You may intersperse those characters
5724 with others to obscure your reply for any watchers. For example (and
5725 these values are for explanation :-):
5728 password = 012345678901234567890123456789
5734 aa2bbbb0ccc5ddd7xxx3n
5739 They will all match. If there is no password you will still be offered
5740 numbers but nothing will happen when you input a string. Any match is
5742 <sect1>talk <call> > <node> [<text>] (0)
5746 <bf>talk <call> > <node> [<text>]</bf> Send a text message to another station via a node
5750 Send a short message to any other station that is visible on the cluster
5751 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
5752 command, they don't have to be connected locally.
5754 The second form of TALK is used when other cluster nodes are connected
5755 with restricted information. This usually means that they don't send
5756 the user information usually associated with logging on and off the cluster.
5758 If you know that G3JNB is likely to be present on GB7TLH, but you can only
5759 see GB7TLH in the SH/C list but with no users, then you would use the
5760 second form of the talk message.
5762 If you want to have a ragchew with someone you can leave the text message
5763 out and the system will go into 'Talk' mode. What this means is that a
5764 short message is sent to the recipient telling them that you are in a
5765 'Talking' frame of mind and then you just type - everything you send will
5766 go to the station that you asked for.
5768 All the usual announcements, spots and so on will still come out on your
5771 If you want to do something (such as send a spot) you preceed the normal
5772 command with a '/' character, eg:-
5775 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
5779 To leave talk mode type:
5785 If you are in 'Talk' mode, there is an extention to the '/' command which
5786 allows you to send the output to all the people you are talking to. You do
5787 with the '//' command. For example:-
5793 will send the hftable as you have it to all the people you are currently
5795 <sect1>talk <call> [<text>] (0)
5799 <bf>talk <call> [<text>]</bf> Send a text message to another station
5803 <sect1>type <filearea>/<name> (0)
5807 <bf>type <filearea>/<name></bf> Look at the contents of a file in one of the fileareas
5811 Type out the contents of a file in a filearea. So, for example, in
5812 filearea 'bulletins' you want to look at file 'arld051' you would
5815 TYPE bulletins/arld051
5818 See also SHOW/FILES to see what fileareas are available and a
5820 <sect1>uncatchup <node call> all|[msgno> ...] (5)
5824 <bf>uncatchup <node call> all|[msgno> ...]</bf> Unmark a message as sent
5828 When you send messages the fact that you have forwarded it to another node
5829 is remembered so that it isn't sent again. When you have a new partner
5830 node and you add their callsign to your /spider/msg/forward.pl file, all
5831 outstanding non-private messages will be forwarded to them. This may well
5832 be ALL the non-private messages. You can prevent this by using these
5837 catchup GB7DJK 300 301 302 303 500-510
5840 and to undo what you have just done:-
5843 uncatchup GB7DJK all
5844 uncatchup GB7DJK 300 301 302 303 500-510
5847 which will arrange for them to be forward candidates again.
5849 Order is not important.
5850 <sect1>unset/announce (0)
5854 <bf>unset/announce</bf> Stop announce messages coming out on your terminal
5858 <sect1>unset/anntalk (0)
5862 <bf>unset/anntalk</bf> Stop talk like announce messages on your terminal
5866 The announce system on legacy cluster nodes is used as a talk
5867 substitute because the network is so poorly connected. If you:
5873 you will suppress several of these announces, you may miss the odd
5874 useful one as well, but you would probably miss them anyway in the
5875 welter of useless ones.
5881 allows you to see them again. This is the default.
5882 <sect1>unset/baddx <call>.. (8)
5886 <bf>unset/baddx <call>..</bf> Propagate a dx spot with this callsign again
5890 Setting a word as 'baddx' will prevent spots with that word in the
5891 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
5892 further. They will not be displayed and they will not be sent onto
5895 The word must be written in full, no wild cards are allowed eg:-
5898 set/baddx FORSALE VIDEO FR0G
5901 To allow a word again, use the following command ...
5907 <sect1>unset/badnode <call>.. (8)
5911 <bf>unset/badnode <call>..</bf> Allow spots from this node again
5915 Setting a callsign as a 'badnode' will prevent spots from that node
5916 going any further. They will not be displayed and they will not be
5917 sent onto other nodes.
5919 The call must be a full eg:-
5925 will stop anything from K1TTT. If you want SSIDs as well then you must
5926 enter them specifically.
5932 will allow spots from him again.
5934 Use with extreme care. This command may well be superceeded by FILTERing.
5935 <sect1>unset/badspotter <call>.. (8)
5939 <bf>unset/badspotter <call>..</bf> Allow spots from this callsign again
5943 Setting a callsign as a 'badspotter' will prevent spots from this callsign
5944 going any further. They will not be displayed and they will not be
5945 sent onto other nodes.
5947 The call must be written in full, no wild cards are allowed eg:-
5950 set/badspotter VE2STN
5953 will stop anything from VE2STN. This command will automatically
5954 stop spots from this user, regardless of whether or which SSID
5955 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
5959 unset/badspotter VE2STN
5962 will allow spots from him again.
5964 Use with extreme care. This command may well be superceded by FILTERing.
5965 <sect1>unset/badword <word>.. (8)
5969 <bf>unset/badword <word>..</bf> Propagate things with this word again
5973 Setting a word as a 'badword' will prevent things like spots,
5974 announces or talks with this word in the the text part from going any
5975 further. They will not be displayed and they will not be sent onto
5978 The word must be written in full, no wild cards are allowed eg:-
5981 set/badword annihilate annihilated annihilation
5984 will stop anything with these words in the text.
5987 unset/badword annihilated
5990 will allow text with this word again.
5991 <sect1>unset/beep (0)
5995 <bf>unset/beep</bf> Stop beeps for DX and other messages on your terminal
5999 <sect1>unset/debug <name> (9)
6003 <bf>unset/debug <name></bf> Remove a debug level from the debug set
6007 You can choose to log several different levels. The levels are
6017 You can show what levels you are logging with SHOW/DEBUG
6022 <bf>unset/dx</bf> Stop DX messages coming out on your terminal
6026 <sect1>unset/dxcq (0)
6030 <bf>unset/dxcq</bf> Stop CQ Zones on the end of DX announcements
6034 Display both the Spotter's and the Spotted's CQ Zone on the end
6035 of a DX announcement (there is just enough room). Some user programs
6036 cannot cope with this. The Spotter's CQ is on the RHS of the
6037 time, the Spotted's CQ is on the LHS.
6039 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
6041 Do a STAT/USER to see which flags you have set if you are confused.
6042 <sect1>unset/dxgrid (0)
6046 <bf>unset/dxgrid</bf> Stop QRA Grid Squares on the end of DX announcements
6050 A standard feature which is enabled in version 1.43 and above is
6051 that if the spotter's grid square is known it is output on the end
6052 of a DX announcement (there is just enough room). Some user programs
6053 cannot cope with this. You can use this command to reset (or set)
6056 Conflicts with: SET/DXCQ, SET/DXITU
6058 Do a STAT/USER to see which flags you have set if you are confused.
6059 <sect1>unset/dxitu (0)
6063 <bf>unset/dxitu</bf> Stop ITU Zones on the end of DX announcements
6067 Display both the Spotter's and the Spotted's ITU Zone on the end
6068 of a DX announcement (there is just enough room). Some user programs
6069 cannot cope with this. The Spotter's ITU is on the RHS of the
6070 time, the Spotted's ITU is on the LHS.
6072 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
6074 Do a STAT/USER to see which flags you have set if you are confused.
6075 <sect1>unset/echo (0)
6079 <bf>unset/echo</bf> Stop the cluster echoing your input
6083 If you are connected via a telnet session, different implimentations
6084 of telnet handle echo differently depending on whether you are
6085 connected via port 23 or some other port. You can use this command
6086 to change the setting appropriately.
6088 The setting is stored in your user profile.
6090 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
6091 <sect1>unset/email (0)
6095 <bf>unset/email</bf> Stop personal msgs being forwarded by email
6099 If any personal messages come in for your callsign then you can use
6100 these commands to control whether they are forwarded onto your email
6101 address. To enable the forwarding do something like:-
6104 SET/EMAIL mike.tubby@somewhere.com
6107 You can have more than one email address (each one separated by a space).
6108 Emails are forwarded to all the email addresses you specify.
6110 You can disable forwarding by:-
6116 <sect1>unset/here (0)
6120 <bf>unset/here</bf> Tell the system you are absent from your terminal
6124 <sect1>unset/hops <call> ann|spots|route|wwv|wcy (8)
6128 <bf>unset/hops <call> ann|spots|route|wwv|wcy</bf> Unset hop count
6132 Set the hop count for a particular type of broadcast for a node.
6134 This command allows you to set up special hop counts for a node
6135 for currently: announce, spots, wwv and wcy broadcasts.
6139 set/hops gb7djk ann 10
6140 set/hops gb7mbc spots 20
6143 Set SHOW/HOPS for information on what is already set. This command
6144 creates a filter and works in conjunction with the filter system.
6146 You can unset the hops with command UNSET/HOPS. For example:-
6149 unset/hops gb7djk ann
6150 unset/hops gb7mbc spots
6153 <sect1>unset/isolate (9)
6157 <bf>unset/isolate</bf> Stop Isolation of a node from the rest of the network
6161 Remove isolation from a node - SET/ISOLATE
6162 <sect1>unset/lockout <call> (9)
6166 <bf>unset/lockout <call></bf> Allow a callsign to connect to the cluster
6170 <sect1>unset/logininfo (0)
6174 <bf>unset/logininfo</bf> Inform when a station logs out locally
6178 <sect1>unset/password <call> ... (9)
6182 <bf>unset/password <call> ...</bf> Delete (remove) a user's password
6186 This command allows the sysop to completely delete and remove a
6187 password for a user.
6188 <sect1>unset/privilege (0)
6192 <bf>unset/privilege</bf> Remove any privilege for this session
6196 You can use this command to 'protect' this session from unauthorised
6197 use. If you want to get your normal privilege back you will need to
6198 either logout and login again (if you are on a console) or use the
6200 <sect1>unset/prompt (0)
6204 <bf>unset/prompt</bf> Set your prompt back to default
6208 This command will set your user prompt to exactly the string that you
6209 say. The point of this command to enable a user to interface to programs
6210 that are looking for a specific prompt (or else you just want a different
6217 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
6219 <sect1>unset/register <call> ... (9)
6223 <bf>unset/register <call> ...</bf> Mark a user as not registered
6227 Registration is a concept that you can switch on by executing the
6230 set/var $main::regreq = 1
6233 command (usually in your startup file)
6235 If a user is NOT registered then, firstly, instead of the normal
6236 motd file (/spider/data/motd) being sent to the user at startup, the
6237 user is sent the motd_nor file instead. Secondly, the non registered
6238 user only has READ-ONLY access to the node. The non-registered user
6239 cannot use DX, ANN etc.
6241 The only exception to this is that a non-registered user can TALK or
6242 SEND messages to the sysop.
6244 <sect1>unset/talk (0)
6248 <bf>unset/talk</bf> Stop TALK messages coming out on your terminal
6252 <sect1>unset/usstate (0)
6256 <bf>unset/usstate</bf> Stop US State info on the end of DX announcements
6260 If the spotter's or spotted's US State is known it is output on the
6261 end of a DX announcement (there is just enough room).
6263 A spotter's state will appear on the RHS of the time (like
6264 SET/DXGRID) and the spotted's State will appear on the LHS of the
6265 time field. Any information found will override any locator
6266 information from SET/DXGRID.
6268 Some user programs cannot cope with this. You can use this command
6269 to reset (or set) this feature.
6271 Conflicts with: SET/DXCQ, SET/DXITU
6273 Do a STAT/USER to see which flags you have set if you are confused.
6274 <sect1>unset/wcy (0)
6278 <bf>unset/wcy</bf> Stop WCY messages coming out on your terminal
6282 <sect1>unset/wwv (0)
6286 <bf>unset/wwv</bf> Stop WWV messages coming out on your terminal
6294 <bf>unset/wx</bf> Stop WX messages coming out on your terminal
6302 <bf>who</bf> Show who is physically connected
6306 This is a quick listing that shows which callsigns are connected and
6307 what sort of connection they have
6308 <sect1>wx <text> (0)
6312 <bf>wx <text></bf> Send a weather message to local users
6316 <sect1>wx full <text> (0)
6320 <bf>wx full <text></bf> Send a weather message to all cluster users
6324 <sect1>wx sysop <text> (5)
6328 <bf>wx sysop <text></bf> Send a weather message to other clusters only
6332 Weather messages can sometimes be useful if you are experiencing an extreme
6333 that may indicate enhanced conditions
projects / spider.git / blob