+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Routing and Filtering</TITLE>
- <LINK HREF="adminmanual-2.html" REL=next>
-
- <LINK HREF="adminmanual.html#toc1" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-2.html">Next</A>
-Previous
-<A HREF="adminmanual.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="s1">1.</A> <A HREF="adminmanual.html#toc1">Routing and Filtering</A></H2>
-
-<H2><A NAME="ss1.1">1.1</A> <A HREF="adminmanual.html#toc1.1">Introduction</A>
-</H2>
-
-<P>From DXSpider version 1.48, major changes were introduced to the way
-node connections are treated. This is part of an ongoing process to
-remove problems with loops and to enable talk and other functions to
-propagate across the whole of the worldwide cluster network. In fact,
-in a Spider network, it would be useful, perhaps even necessary to
-have loops. This would give real resilience to the network, meaning
-that if a link dropped, the information flow would simply come in and
-go out via a different route. Of course, we do not have a complete
-network of Spider nodes, there are other programs out there. Some of
-these do not have any protection from loops. Certainly AK1A does not
-handle loops well at all. It is therefore necessary to have some form
-of protection for these nodes.</P>
-
-<P>In fact DXSpider has had a simple system for some time which is called
-<I>isolation</I>. This is similar to what in other systems such as
-<B>clx</B>, is called <I>passive mode</I>. A more detailed explanation
-of <I>isolation</I> is given further below. This system is still available
-and, for simple networks, is probably all that you need.</P>
-
-<P>The new functionality introduced in version 1.48 allows filtering the node
-and user protocol frames on a "per interface" basis. We call this
-<I>route filtering</I>. This is used <B>instead of</B>
-<I>isolation</I>. </P>
-
-<P>What this really means is that you can control more or less completely
-which user and node management PC protocol frames pass to each of your
-partner nodes. You can also limit what comes into your node from your
-partners. It is even possible to control the settings that your partner
-node has for the routing information that it sends to you
-(using the <I>rcmd</I> command).</P>
-
-<H2><A NAME="ss1.2">1.2</A> <A HREF="adminmanual.html#toc1.2">Route Filters</A>
-</H2>
-
-<P>Initially when route filters were being tested we generated a
-"default" filter. Unfortunately it quickly became apparent that this
-might suit the UK cluster network but didn't really fit anybody else.
-However using a default filter is an appropriate thing to do. How, is
-explained further on.</P>
-
-<P>The first thing that you must do is determine whether you need to use
-route filtering <B>at all</B>. If you are a "normal" node with two or
-three partners and you arranged in an "official" non-looping tree type
-network, then <B>you do not need to do route filtering</B> and you will
-feel a lot better for not getting involved. If you are successfully using
-<I>isolation</I> then you also probably don't need to use route filtering.</P>
-
-<P>To put it simply, you should not mix Isolation and Route Filtering. It
-will work, of sorts, but you will not get the expected results. If you
-are using Isolation sucessfully at the moment, do not get involved in
-Route Filtering unless you have a good supply of aspirin! Once you have
-started down the road of Route Filtering, do not use Isolation either.
-Use one or the other, not both.</P>
-
-<P>You will only require this functionality if you are "well-connected". What
-that means is that you are connected to several different parts of (say)
-the EU cluster and, at the same time, also connected to two or three places
-in the US which, in turn are connected back to the EU. This is called a
-"loop" and if you are seriously looped then you need filtering.</P>
-
-<P>I should at this stage give a little bit of background on filters. All
-the filters in Spider work in basically the same way. You can either
-accept or reject various options in order to create the filter rules
-you wish to achieve. Some filters are user settable, others can only
-be altered by the sysop. Route filtering can only be done by the sysop.</P>
-
-<P>
-Anyway, without further discouragement, let me start the process
-of explanation.</P>
-
-<H2><A NAME="ss1.3">1.3</A> <A HREF="adminmanual.html#toc1.3">The node_default filter</A>
-</H2>
-
-<P>All normal systems should have a default routing filter and it should
-usually be set to send only the normal, unlooped, view of your
-"national" network. Here in the UK that means nodes from the UK and
-Eire, in EU it is more complex as the networks there grew up in a more
-intertwined way.</P>
-
-<P>
-The generic commands are:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/route node_default <filter_option>
-
-or
-
-accept/route node_default <filter_option>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>where filter_option is one of the following ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-call <prefixes>
-call_dxcc <numbers>
-call_itu <numbers>
-call_zone <numbers>
-channel <prefixes>
-channel_dxcc <numbers>
-channel_itu <numbers>
-channel_zone <numbers>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Please be careful if you alter this setting, it will affect
-<B><I>ALL</I></B> your links! Remember, this is a <I>default</I>
-filter for node connections, not a <I>per link</I> default.</P>
-
-<P>For the default routing filter then you have two real choices: either
-a "national" view or the "safe" option of only your own
-callsign. Examples of each (for my node: GB7DJK) are:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-acc/route node_default call_dxcc 61,38
-acc/route node_default call gb7djk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>GB7DJK uses the first of these. The DXCC countries can be obtained from the
-<I>show/prefix</I> command.</P>
-
-<P>The example filters shown control <I>output</I> <B>TO</B> all your
-partner nodes unless they have a specific filter applied to them (see
-next section).</P>
-
-<P>It is also possible to control the <I>incoming</I> routing
-information that you are prepared to accept <B>FROM</B> your partner
-nodes. The reason this is necessary is to make sure that stuff like
-mail, pings and similar commands a) go down the correct links and b)
-don't loop around excessively. Again using GB7DJK as an example a typical
-default input filter would be something like:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>What this does is accept node and user information for our national
-network from nodes that are in our national network, but rejects such
-information from anyone else. Although it doesn't explicitly say so,
-by implication, any other node information (not from the UK and Eire)
-is accepted.</P>
-
-<P>As I imagine it will take a little while to get one's head around all of
-this you can study the effect of any rules that you try by watching the
-debug output after having done:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/debug filter
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>After you have got tired of that, to put it back the way it was:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-unset/debug filter
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss1.4">1.4</A> <A HREF="adminmanual.html#toc1.4">General route filtering</A>
-</H2>
-
-<P>Exactly the same rules apply for general route filtering. You would
-use either an accept filter or a reject filter like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/route <node_call> <filter_option>
-
-or
-
-accept/route <node_call> <filter_option>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Here are some examples of route filters ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
-rej/route all (equiv to [very] restricted mode)
-acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
-acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>In practice you will either be opening the default filter out for a
-partner by defining a specific filter for that callsign:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-acc/route gb7baa all
-acc/route gb7baa input all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>or restricting it quite a lot, in fact making it very nearly like an
-<I>isolated</I> node, like this:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-acc/route pi4ehv-8 call gb7djk
-rej/route pi4ehv-8 input call_dxcc 61,38
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This last example takes everything except UK and Eire from PI4EHV-8
-but only sends him my local configuration (just a PC19 for GB7DJK and
-PC16s for my local users).</P>
-
-<P>It is possible to write <B>much</B> more complex rules, there are up
-to 10 accept/reject pairs per callsign per filter. For more information
-see the next section. </P>
-
-
-<H2><A NAME="ss1.5">1.5</A> <A HREF="adminmanual.html#toc1.5">General filter rules</A>
-</H2>
-
-<P>Upto v1.44 it was not possible for the user to set their own filters. From
-v1.45 though that has all changed. It is now possible to set filters for just
-about anything you wish. If you have just updated from an older version of
-DXSpider you will need to update your new filters. You do not need to do
-anything with your old filters, they will be renamed as you update.</P>
-
-<P>There are 3 basic commands involved in setting and manipulating filters. These
-are <EM>accept</EM>, <EM>reject</EM> and <EM>clear</EM>. First we will look
-generally at filtering. There are a number of things you can filter in the
-DXSpider system. They all use the same general mechanism.</P>
-
-<P>In general terms you can create a "reject" or an "accept" filter which can have
-up to 10 lines in it. You do this using, for example ... </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-accept/spots .....
-reject/spots .....
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>where ..... are the specific commands for that type of filter. There are filters
-for spots, wwv, announce, wcy and (for sysops) connects. See each different
-accept or reject command reference for more details.</P>
-<P>There is also a command to clear out one or more lines in a filter. They are ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>There is clear/xxxx command for each type of filter.</P>
-
-<P>and you can check that your filters have worked by the command ... </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-show/filter
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For now we are going to use spots for the examples, but you can apply the same
-principles to all types of filter.</P>
-
-<H2><A NAME="ss1.6">1.6</A> <A HREF="adminmanual.html#toc1.6">Types of filter</A>
-</H2>
-
-<P>There are two main types of filter, <EM>accept</EM> or <EM>reject</EM>. You
-can use either to achieve the result you want dependent on your own preference
-and which is more simple to do. It is pointless writing 8 lines of reject
-filters when 1 accept filter would do the same thing! Each filter has 10
-lines (of any length) which are tried in order. If a line matches then the
-action you have specified is taken (ie reject means ignore it and accept
-means take it)</P>
-
-<P>If you specify reject filters, then any lines that arrive that match the filter
-will be dumped but all else will be accepted. If you use an accept filter,
-then ONLY the lines in the filter will be accepted and all else will be dumped.
-For example if you have a single line <EM>accept</EM> filter ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>then you will <EM>ONLY</EM> get VHF spots <EM>from</EM> or <EM>to</EM> CQ zones
-14, 15 and 16.</P>
-
-<P>If you set a reject filter like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Then you will get everything <EM>EXCEPT</EM> HF CW spots. You could make this
-single filter even more flexible. For example, if you are interested in IOTA
-and will work it even on CW even though normally you are not interested in
-CW, then you could say ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw and not info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>But in that case you might only be interested in iota and say:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots not on hf/cw or info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>which achieves exactly the same thing. You should choose one or the other
-until you are comfortable with the way it works. You can mix them if you
-wish (actually you can have an accept AND a reject on the same line) but
-don't attempt this until you are sure you know what you are doing!</P>
-
-<P>You can arrange your filter lines into logical units, either for your own
-understanding or simply convenience. Here is an example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots 1 on hf/cw
-reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>What this does is to ignore all HF CW spots and also rejects any spots on VHF
-which don't either originate or spot someone in Europe. </P>
-
-<P>This is an example where you would use a line number (1 and 2 in this case), if
-you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
-This make it easier to see just what filters you have set. It also makes it
-more simple to remove individual filters, during a contest for example.</P>
-
-<P>You will notice in the above example that the second line has brackets. Look
-at the line logically. You can see there are 2 separate sections to it. We
-are saying reject spots that are VHF or above <EM>APART</EM> from those in
-zones 14, 15 and 16 (either spotted there or originated there). If you did
-not have the brackets to separate the 2 sections, then Spider would read it
-logically from the front and see a different expression entirely ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The simple way to remember this is, if you use OR - use brackets. Whilst we are
-here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.</P>
-<P>As mentioned earlier, setting several filters can be more flexible than
-simply setting one complex one. Doing it in this way means that if you want
-to alter your filter you can just redefine or remove one or more lines of it or
-one line. For example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots 1 on hf/ssb
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>would redefine our earlier example, or </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To remove all the filter lines in the spot filter ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss1.7">1.7</A> <A HREF="adminmanual.html#toc1.7">Filter options</A>
-</H2>
-
-<P>You can filter in several different ways. The options are listed in the
-various helpfiles for accept, reject and filter.</P>
-
-<H2><A NAME="ss1.8">1.8</A> <A HREF="adminmanual.html#toc1.8">Default filters</A>
-</H2>
-
-<P>Sometimes all that is needed is a general rule for node connects. This can
-be done with a node_default filter. This rule will always be followed, even
-if the link is isolated, unless another filter is set specifically. Default
-rules can be set for nodes and users. They can be set for spots, announces,
-WWV and WCY. They can also be used for hops. An example might look like
-this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spot node_default by_zone 14,15,16,20,33
-set/hops node_default spot 50
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This filter is for spots only, you could set others for announce, WWV and WCY.
-This filter would work for ALL nodes unless a specific filter is written to
-override it for a particular node. You can also set a user_default should
-you require. It is important to note that default filters should be
-considered to be "connected". By this I mean that should you override the
-default filter for spots, you need to add a rule for the hops for spots also.</P>
-
-<H2><A NAME="ss1.9">1.9</A> <A HREF="adminmanual.html#toc1.9">Advanced filtering</A>
-</H2>
-
-<P>Once you are happy with the results you get, you may like to experiment. </P>
-
-<P>The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, for example ... </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rej/spot on hf/cw
-acc/spot on 0/30000
-acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Note that the first filter has not been specified with a number. This will
-automatically be assumed to be number 1. In this case, we have said <EM>reject all
-HF spots in the CW section of the bands but accept all others at HF. Also
-accept anything in VHF and above spotted in or by operators in the zones
-14, 15 and 16</EM>. Each filter slot actually has a 'reject' slot and
-an 'accept' slot. The reject slot is executed BEFORE the accept slot.</P>
-
-<P>It was mentioned earlier that after a reject test that doesn't match, the default
-for following tests is 'accept', the reverse is true for 'accept'. In the example
-what happens is that the reject is executed first, any non hf/cw spot is passed
-to the accept line, which lets through everything else on HF. The next filter line
-lets through just VHF/UHF spots from EU.</P>
-
-<H2><A NAME="ss1.10">1.10</A> <A HREF="adminmanual.html#toc1.10">Basic hop control</A>
-</H2>
-
-<P>In /spider/data you will find a file called hop_table.pl. This is the file
-that controls your hop count settings. It has a set of default hops on the
-various PC frames and also a set for each node you want to alter the hops for.
-You may be happy with the default settings of course, but this powerful tool
-can help to protect and improve the network. The file will look something
-like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# hop table construction
-#
-
-package DXProt;
-
-# default hopcount to use
-$def_hopcount = 5;
-
-# some variable hop counts based on message type
-%hopcount =
-(
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
-);
-
-
-# the per node hop control thingy
-
-
-%nodehops =
-(
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Each set of hops is contained within a pair of curly braces and contains a
-series of PC frame types. PC11 for example is a DX spot. The figures here
-are not exhaustive but should give you a good idea of how the file works.</P>
-
-<P>SHould any of the nodecalls include an ssid, it is important to wrap the
-whole call in single quotes, like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- 'DB0FHF-15' => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you do not do this, you will get errors and the file will not work as
-expected.</P>
-
-<P>You can alter this file at any time, including whilst the cluster is running.
-If you alter the file during runtime, the command <EM>load/hops</EM> will
-bring your changes into effect.</P>
-
-<H2><A NAME="ss1.11">1.11</A> <A HREF="adminmanual.html#toc1.11">Hop Control on Specific Nodes</A>
-</H2>
-
-<P>You can set a callsign specific hop count for any of the standard filter
-options so:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/hops gb7djk spot 4
-set/hops node_default route 10
-set/hops gb7baa wcy 5
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>all work on their specific area of the protocol.</P>
-
-<P>The <EM>set/hops</EM> command overrides any hops that you have set otherwise.</P>
-
-<P>You can show what hops have been set using the <EM>show/hops</EM> command.</P>
-
-<H2><A NAME="ss1.12">1.12</A> <A HREF="adminmanual.html#toc1.12">Isolating networks</A>
-</H2>
-
-<P>It is possible to isolate networks from each other on a "gateway" node using the
-<EM>set/isolate <node_call></EM> command.</P>
-
-<P>The effect of this is to partition an isolated network completely from another
-node connected to your node. Your node will appear on and otherwise behave
-normally on every network to which you are connected, but data from an isolated
-network will not cross onto any other network or vice versa. However all the
-spot, announce and WWV traffic and personal messages will still be handled
-locally (because you are a real node on all connected networks), that is locally
-connected users will appear on all networks and will be able to access and
-receive information from all networks transparently. All routed messages will
-be sent as normal, so if a user on one network knows that you are a gateway for
-another network, he can still still send a talk/announce etc message via your
-node and it will be routed across.</P>
-
-<P>If you use isolate on a node connection you will continue to receive
-all information from the isolated partner, however you will not pass
-any information back to the isolated node. There are times when you
-would like to forward only spots across a link (maybe during a contest
-for example). To do this, isolate the node in the normal way and use
-an <EM>acc/spot >call< all</EM> filter to override the isolate. </P>
-
-<HR>
-<A HREF="adminmanual-2.html">Next</A>
-Previous
-<A HREF="adminmanual.html#toc1">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: CVS</TITLE>
- <LINK HREF="adminmanual-11.html" REL=next>
- <LINK HREF="adminmanual-9.html" REL=previous>
- <LINK HREF="adminmanual.html#toc10" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-11.html">Next</A>
-<A HREF="adminmanual-9.html">Previous</A>
-<A HREF="adminmanual.html#toc10">Contents</A>
-<HR>
-<H2><A NAME="s10">10.</A> <A HREF="adminmanual.html#toc10">CVS</A></H2>
-
-<H2><A NAME="ss10.1">10.1</A> <A HREF="adminmanual.html#toc10.1">CVS from a Linux platform</A>
-</H2>
-
-<P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
-at
-<A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
-that it is possible to update your DXSpider installation to the latest
-sources by using a few simple commands. A graphical interface to CVS for
-Windows is explained in the next section.</P>
-
-<P>Please be aware that if you update your system using CVS, it is possible that
-you could be running code that is very beta and not fully tested. There is
-a possibility that it could be unstable.</P>
-
-<P>I am of course assuming that you have a machine with both DXSpider and
-Internet access running.</P>
-
-<P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
-ENTIRE SPIDER TREE!!</P>
-
-<P>Assuming you are connected to the Internet, you need to login to the
-CVS repository and then update your Spider source. There are several
-steps which are listed below ...</P>
-
-<P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
-repository. You do this with the command below ...</P>
-<P>
-<PRE>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-</PRE>
-</P>
-<P>You will get a password prompt. Simply hit return here and your machine should
-return to a normal linux prompt.</P>
-
-<P>What happens next depends on whether you have an existing installation that
-you want to update with the latest and greatest or whether you just want
-to see what is there and/or run it on a new machine for testing.</P>
-<P>If you are installing Spider from CVS then change directory to /home/sysop</P>
-<P>If you are wanting to update Spider then cd to /tmp</P>
-
-<P>The next step will create a brand new 'spider' directory in your current
-directory.</P>
-<P>
-<PRE>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
-</PRE>
-</P>
-<P>This command is all on one line.</P>
-
-<P>Hopefully your screen should show you downloading files. The -z3 simply compresses
-the download to improve speed.
-When this has finished, you will have exactly the same as if you had untarred a full
-tarball PLUS some extra directories and files that CVS needs to do the magic that
-it does.</P>
-
-<P>Now if you are doing a new installation, that's it. Carry on as if you have
-just downloaded and untarred the lastest tarball.</P>
-
-<P>If you want to upgrade your current installation then do this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This is assuming you downloaded to the /tmp directory of course.</P>
-
-<P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
-correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????</P>
-<P>Remember to recompile the C client (cd /spider/src; make)</P>
-
-<P>At this point the files have been upgraded. You can (usually) restart the cluster
-in your own time. However, if you attempt to use any new commands or features
-expect it to be fatal! At least your cluster will have been restarted then so it
-will be too late to worry about it!</P>
-
-<P>Now the magic part! From now on when you want to update, simply connect to the
-Internet and then, as the user <EM>sysop</EM> ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd /spider
-cvs -z3 update -d
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and your files will be updated. As above, remember to recompile the "C" client
-if it has been updated (CVS will tell you) and restart if any of the perl scripts
-have been altered or added, again, CVS will tell you.</P>
-
-<P>You will find any changes documented in the /spider/Changes file.</P>
-
-<H2><A NAME="ss10.2">10.2</A> <A HREF="adminmanual.html#toc10.2">CVS from a Windows platform</A>
-</H2>
-
-<P>After the initial setup, an update to your DXSpider software is no more than a couple
-of clicks away. This section is intended to explain and illustrate the use of the
-WinCVS application to update your DXSpider software. The current stable version of
-WinCVS is Ver. 1.2. You can get this software at:</P>
-<P>
-<A HREF="http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip">http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip</A></P>
-<P>Pick your download mirror and then install WinCVS after the download is complete.</P>
-<P>In this next section I have included a series of links to .jpg files to take advantage of the
-picture and 1000 words equivalency. The .jpg files are in the C:\spider\html directory. If
-someone using a Linux system is reading this section from boredom, the files are in
-/home/sysop/spider/html. One aside, a Linux user can also get a copy of gcvs and do your updates
-graphically as opposed to from the command line. The following descriptions are almost identical
-between WinCvs and gcvs. The following screen shots have duplicate links, depending upon whether
-you are viewing this information under the Windows or Linux operating system.</P>
-<P>When WinCVS is installed, running, and you are connected to the internet, the initial screen looks like:</P>
-<P>
-<A HREF="initial.jpg">initial.jpg</A></P>
-<P>If you want, you can also look at these .jpg files with another viewer that might provide some
-better clarity to the image. On the left is the directory tree for your hard disk. Notice that
-the spider directory has a gray highlight.</P>
-<P>To start configuring WinCVS, click on Admin at the top of the screen and then Preferences. This
-should get you:</P>
-<P>
-<A HREF="pref-gen.jpg">pref-gen.jpg</A></P>
-<P>In the top line for CVSROOT, enter:
-<BLOCKQUOTE><CODE>
-<PRE>
-anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and select
-<BLOCKQUOTE><CODE>
-<PRE>
-"passwd" file on the cvs server
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>for Authentication on the General tab.</P>
-<P>Next, move to the right to the Ports tab.</P>
-<P>
-<A HREF="pref-ports.jpg">pref-ports.jpg</A></P>
-<P>In here, check the box on the second line down for the "pserver" port. Enter a port number of 2401.</P>
-<P>Finally, go to the WinCvs tab all the way to the right.</P>
-<P>
-<A HREF="pref-wincvs.jpg">pref-wincvs.jpg</A></P>
-<P>Enter Notepad as the viewer to open files. For the HOME folder, put "C:\spider" and click OK
-because the configuration is now complete.</P>
-<P>You are now ready to upgrade your copy of DXSpider. Click on the greyed Spider folder
-shown in the directory tree on the left of the WinCVS display. Two things should happen. The Spider
-folder will be selected and the greyed-out arrow located just below the word Query in the top line will
-turn to solid green.</P>
-<P>For anyone using gcvs under Linux, the green arrow is located on the extreme left of the display,
-under the word File. A gcvs screen looks like:</P>
-<P>
-<A HREF="gcvs.jpg">gcvs.jpg</A></P>
-<P>Click on the now green arrow to start the download process. An Update Settings box will be displayed
-to which you can simply say OK.</P>
-<P>
-<A HREF="update-OK.jpg">update-OK.jpg</A></P>
-<P>For future reference, the Update Settings box is the place where you can enter information to revert
-to a prior version of DXSpider. Information on reverting to a Before Date is contained in the WinCVS
-manual.</P>
-<P>After a short period of time, a series of file names will scroll by in the lower pane of the WinCVS
-window. Eventually you should see
-<BLOCKQUOTE><CODE>
-<PRE>
-*****CVS exited normally with code 0*****
-</PRE>
-</CODE></BLOCKQUOTE>
-
-appear in the lower pane. You're done. The updated files are in place ready for you to stop and then
-restart your DXSpider. After the restart, you're running with the latest version of DXSpider.</P>
-<P>
-<A HREF="completed.jpg">completed.jpg</A></P>
-<P>To paraphrase from the CVS section... Now the magic part! From now on when you want to update, simply
-connect to the Internet and start WinCVS.
-<BLOCKQUOTE><CODE>
-<PRE>
-Click on the greyed-out Spider directory in the left screen
-Click on the green down arrow
-Click OK on the Update Settings dialog box
-Restart your Spider software
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<HR>
-<A HREF="adminmanual-11.html">Next</A>
-<A HREF="adminmanual-9.html">Previous</A>
-<A HREF="adminmanual.html#toc10">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: The DXSpider command set</TITLE>
- <LINK HREF="adminmanual-10.html" REL=previous>
- <LINK HREF="adminmanual.html#toc11" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-<A HREF="adminmanual-10.html">Previous</A>
-<A HREF="adminmanual.html#toc11">Contents</A>
-<HR>
-<H2><A NAME="s11">11.</A> <A HREF="adminmanual.html#toc11">The DXSpider command set</A></H2>
-
-<P>Below is a complete list of commands available from the cluster prompt.
-Most maintenance tasks are automatic but there are some commands that are useful
-for a sysop. These are listed below in alphabetical order. The number in
-brackets following the command name is the permissions level needed to use
-the command</P>
-
-<H2><A NAME="ss11.1">11.1</A> <A HREF="adminmanual.html#toc11.1">accept/announce (0)</A>
-</H2>
-
-<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
-line for announce</CODE></P>
-
-<P>Create an 'accept this announce' line for a filter.</P>
-<P>An accept filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann dest 6MUK
- acc/ann 2 by_zone 14,15,16
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>or</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This filter would only allow announces that were posted buy UK stations.
-You can use the tag 'all' to accept everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss11.2">11.2</A> <A HREF="adminmanual.html#toc11.2">accept/announce (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/ann by G,M,2
- accept/ann input node_default by G,M,2
- accept/ann user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.3">11.3</A> <A HREF="adminmanual.html#toc11.3">accept/route (8)</A>
-</H2>
-
-<P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE></P>
-
-<P>Create an 'accept this routing PC Protocol' line for a filter. </P>
-
-<P>An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is passed thru that interface. See HELP FILTERING for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You can use the tag 'all' to accept everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/route all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.4">11.4</A> <A HREF="adminmanual.html#toc11.4">accept/spots (0)</A>
-</H2>
-
-<P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE></P>
-
-<P>Create an 'accept this spot' line for a filter.</P>
-
-<P>An accept filter line means that if the spot matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>Please read the following section carefully. Though it looks similar,
-reformatting, corrections, and hopefully clarifications have been added.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Filters for the station being spotted:
- call <letters of the prefix, but NOT country inclusive>
- call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted
- call K --> K1XX, K1XXX will be spotted
- W1XX, W1XXX will NOT be spotted
- call PA --> PA3EZL will be spotted
- PB2FG will NOT be spotted
-
- call_dxcc <numbers or prefixes>
- call_dxcc G --> G1AAA will be spotted
- GU1AAA will NOT be spotted (different country)
- call_dxcc K --> K1XX, W1XX will be spotted (same country)
- call_dxcc 139 --> PA3EZL and PB2FG will be spotted
-
- call_itu <numbers>
- call_zone <numbers>
-
-Filters for the callsign of the station doing the spotting:
- by <letters of the prefix, but NOT country inclusive>
- by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted
- by K --> spots from K1XX, K1XXX will be spotted
- spots from W1XX, W1XXX will NOT be spotted
-
- by_dxcc <numbers or prefixes>
- by_dxcc G --> spots from G1AAA will be spotted
- spots from GU1AAA will NOT be spotted (different
-country)
- by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)
- by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted
-
- by_itu <numbers>
- by_zone <numbers>
-
-Filters for the callsign of the "node" doing the spotting:
- origin <letters of the prefix, but NOT country inclusive>
- origin K --> spots from a node starting with K will be spotted
- spots from a node starting with KK will NOT be spotted
- spots from a node starting with W will NOT be spotted
-
-Filters for the callsign of the connected node or user (channel) doing the spotting:
- channel <prefixes>
- channel W1HR --> spots from the connected node W1HR will be spotted
- channel K1QX --> spots from the connected user K1QX will be spotted
-
- info <string> eg: iota or qsl
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: freq HF (but don't get
-too hung up about that)</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can use the tag 'all' to accept everything, eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 3 all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss11.5">11.5</A> <A HREF="adminmanual.html#toc11.5">accept/spots (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/spot db0sue-7 1 by_zone 14,15,16
- accept/spot node_default all
- set/hops node_default 10
-
- accept/spot user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.6">11.6</A> <A HREF="adminmanual.html#toc11.6">accept/wcy (0)</A>
-</H2>
-
-<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).</P>
-<P>This command is really provided for future use.</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss11.7">11.7</A> <A HREF="adminmanual.html#toc11.7">accept/wcy (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
-WCY filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wcy node_default all
- set/hops node_default 10
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.8">11.8</A> <A HREF="adminmanual.html#toc11.8">accept/wwv (0)</A>
-</H2>
-
-<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>for example </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wwv by_zone 4
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>is probably the only useful thing to do (which will only show WWV broadcasts
-by stations in the US).</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss11.9">11.9</A> <A HREF="adminmanual.html#toc11.9">accept/wwv (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
-WWV filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wwv db0sue-7 1 by_zone 4
- accept/wwv node_default all
- set/hops node_default 10
-
- accept/wwv user_default by W,K
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.10">11.10</A> <A HREF="adminmanual.html#toc11.10">announce (0)</A>
-</H2>
-
-<P><CODE><B>announce <text></B> Send an announcement to local users</CODE></P>
-
-<P>Send an announcement to LOCAL users only, where <text> is the text
-of the announcement you wish to broadcast. If you do not wish to receive
-announces, use the <EM>set/noannounce</EM> command. Any announces made by
-a sysop will override set/noannounce.</P>
-
-<H2><A NAME="ss11.11">11.11</A> <A HREF="adminmanual.html#toc11.11">announce full (0)</A>
-</H2>
-
-<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
-
-<P>This command will send your announcement across the whole cluster
-network.</P>
-
-
-<H2><A NAME="ss11.12">11.12</A> <A HREF="adminmanual.html#toc11.12">announce sysop (5)</A>
-</H2>
-
-<P><CODE><B>announce sysop <text></B></CODE></P>
-
-<P>Send an announcement to Sysops only</P>
-
-<H2><A NAME="ss11.13">11.13</A> <A HREF="adminmanual.html#toc11.13">apropos (0)</A>
-</H2>
-
-<P><CODE><B>apropos <string></B> Search the help database</CODE></P>
-
-<P>Search the help database for <string> (it isn't case sensitive),
-and print the names of all the commands that may be relevant.</P>
-
-<H2><A NAME="ss11.14">11.14</A> <A HREF="adminmanual.html#toc11.14">bye (0)</A>
-</H2>
-
-<P><CODE><B>bye</B> Exit from the cluster</CODE></P>
-
-<P>This will disconnect you from the cluster</P>
-
-<H2><A NAME="ss11.15">11.15</A> <A HREF="adminmanual.html#toc11.15">catchup (5)</A>
-</H2>
-
-<P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE></P>
-
-<P>When you send messages the fact that you have forwarded it to another node
-is remembered so that it isn't sent again. When you have a new partner
-node and you add their callsign to your /spider/msg/forward.pl file, all
-outstanding non-private messages will be forwarded to them. This may well
-be ALL the non-private messages. You can prevent this by using these
-commmands:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- catchup GB7DJK all
- catchup GB7DJK 300 301 302 303 500-510
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and to undo what you have just done:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- uncatchup GB7DJK all
- uncatchup GB7DJK 300 301 302 303 500-510
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>which will arrange for them to be forward candidates again.</P>
-<P>Order is not important.</P>
-
-<H2><A NAME="ss11.16">11.16</A> <A HREF="adminmanual.html#toc11.16">clear/announce (8)</A>
-</H2>
-
-<P><CODE><B>clear/announce <callsign> [input] [0-9|all]</B> Clear an announce filter line</CODE></P>
-
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default. </P>
-
-<H2><A NAME="ss11.17">11.17</A> <A HREF="adminmanual.html#toc11.17">clear/route (8)</A>
-</H2>
-
-<P><CODE><B>clear/route <callsign> [input] [0-9|all]</B> Clear a route filter line</CODE></P>
-
-<P>This command allows you to clear (remove) a line in a route filter or to
-remove the whole filter.</P>
-<P>see CLEAR/SPOTS for a more detailed explanation.</P>
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default. </P>
-
-<H2><A NAME="ss11.18">11.18</A> <A HREF="adminmanual.html#toc11.18">clear/spots (0)</A>
-</H2>
-
-<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE></P>
-
-<P>This command allows you to clear (remove) a line in a spot filter or to
-remove the whole filter.</P>
-<P>If you have a filter:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and you say:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- clear/spot 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>you will be left with:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you do:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- clear/spot all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>the filter will be completely removed.</P>
-
-<H2><A NAME="ss11.19">11.19</A> <A HREF="adminmanual.html#toc11.19">clear/spots (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>clear/spots <callsign> [input] [0-9|all]</B> Clear a spot filter line</CODE></P>
-
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default. </P>
-
-<H2><A NAME="ss11.20">11.20</A> <A HREF="adminmanual.html#toc11.20">clear/wcy (0)</A>
-</H2>
-
-<P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE></P>
-
-<P>This command allows you to clear (remove) a line in a WCY filter or to
-remove the whole filter.</P>
-<P>see CLEAR/SPOTS for a more detailed explanation.</P>
-
-<H2><A NAME="ss11.21">11.21</A> <A HREF="adminmanual.html#toc11.21">clear/wcy (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>clear/wcy <callsign> [input] [0-9|all]</B> Clear a WCY filter line</CODE></P>
-
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default. </P>
-
-<H2><A NAME="ss11.22">11.22</A> <A HREF="adminmanual.html#toc11.22">clear/wwv (0)</A>
-</H2>
-
-<P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE></P>
-
-<P>This command allows you to clear (remove) a line in a WWV filter or to
-remove the whole filter.</P>
-<P>see CLEAR/SPOTS for a more detailed explanation.</P>
-
-<H2><A NAME="ss11.23">11.23</A> <A HREF="adminmanual.html#toc11.23">clear/wwv (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>clear/wwv <callsign> [input] [0-9|all]</B> Clear a WWV filter line</CODE></P>
-
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.</P>
-
-<H2><A NAME="ss11.24">11.24</A> <A HREF="adminmanual.html#toc11.24">connect (5) </A>
-</H2>
-
-<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE></P>
-
-<P>Start a connection process that will culminate in a new connection to the
-DX cluster <callsign>. This process creates a new 'client' process which will
-use the script in /spider/connect/<callsign> to effect the 'chat' exchange
-necessary to traverse the network(s) to logon to the cluster <callsign>.</P>
-
-<H2><A NAME="ss11.25">11.25</A> <A HREF="adminmanual.html#toc11.25">dbavail (0)</A>
-</H2>
-
-<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE></P>
-
-<P>The title says it all really, this command lists all the databases defined
-in the system. It is also aliased to SHOW/COMMAND.</P>
-
-<H2><A NAME="ss11.26">11.26</A> <A HREF="adminmanual.html#toc11.26">dbcreate (9)</A>
-</H2>
-
-<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
-<B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
-<B>dbcreate <name> remote <node></B> Create a remote database
-entry<BR></CODE></P>
-
-<P>DBCREATE allows you to define a database in the system. It doesn't actually
-create anything, just defines it.</P>
-<P>The databases that are created are simple DB_File hash databases, they are
-therefore already 'indexed'.</P>
-<P>You can define a local database with the first form of the command eg:</P>
-<P>DBCREATE oblast</P>
-<P>You can also chain databases with the addition of the 'chain' keyword.
-This will search each database one after the other. A typical example
-is:</P>
-<P>DBCREATE sdx_qsl chain sql_ad</P>
-<P>No checking is done to see if the any of the chained databases exist, in
-fact it is usually better to do the above statement first then do each of
-the chained databases.</P>
-<P>Databases can exist offsite. To define a database that lives on another
-node do:</P>
-<P>DBCREATE buckmaster remote gb7dxc</P>
-<P>Remote databases cannot be chained; however, the last database in a
-a chain can be a remote database eg:</P>
-<P>DBCREATE qsl chain gb7dxc</P>
-<P>To see what databases have been defined do:</P>
-<P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)</P>
-<P>It would be normal for you to add an entry into your local Aliases file
-to allow people to use the 'SHOW/<dbname>' style syntax. So you would
-need to add a line like:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- 's' => [
- ..
- ..
- '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
- ..
- ..
- ],
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>to allow </P>
-<P>SH/BUCK g1tlh</P>
-<P>to work as they may be used to.</P>
-<P>See DBIMPORT for the importing of existing AK1A format data to databases.
-See DBSHOW for generic database enquiry</P>
-
-<H2><A NAME="ss11.27">11.27</A> <A HREF="adminmanual.html#toc11.27">dbimport (9)</A>
-</H2>
-
-<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE></P>
-
-<P>If you want to import or update data in bulk to a database you can use
-this command. It will either create or update entries into an existing
-database. For example:-</P>
-<P>DBIMPORT oblast /tmp/OBLAST.FUL</P>
-<P>will import the standard OBLAST database that comes with AK1A into the
-oblast database held locally.</P>
-
-<H2><A NAME="ss11.28">11.28</A> <A HREF="adminmanual.html#toc11.28">dbremove (9)</A>
-</H2>
-
-<P><CODE><B>dbremove <dbname></B> Delete a database</CODE></P>
-
-<P>DBREMOVE will completely remove a database entry and also delete any data
-file that is associated with it. </P>
-<P>There is no warning, no comeback, no safety net. </P>
-<P>For example:</P>
-<P>DBREMOVE oblast </P>
-<P>will remove the oblast database from the system and it will also remove
-the associated datafile.</P>
-<P>I repeat:</P>
-<P>There is no warning, no comeback, no safety net.</P>
-<P>You have been warned.</P>
-
-<H2><A NAME="ss11.29">11.29</A> <A HREF="adminmanual.html#toc11.29">dbshow (0)</A>
-</H2>
-
-<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
-
-<P>This is the generic user interface to the database to the database system.
-It is expected that the sysop will add an entry to the local Aliases file
-so that users can use the more familiar AK1A style of enquiry such as:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/BUCK G1TLH
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but if he hasn't and the database really does exist (use DBAVAIL or
-SHOW/COMMAND to find out) you can do the same thing with:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DBSHOW buck G1TLH
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="ss11.30">11.30</A> <A HREF="adminmanual.html#toc11.30">debug (9)</A>
-</H2>
-
-<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE></P>
-
-<P>Executing this command will only have an effect if you are running the cluster
-in debug mode i.e.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- perl -d cluster.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>It will interrupt the cluster just after the debug command has finished.</P>
-
-<H2><A NAME="ss11.31">11.31</A> <A HREF="adminmanual.html#toc11.31">delete/user (9)</A>
-</H2>
-
-<P><CODE><B>delete/user <callsign></B> Delete a user from the User Database</CODE></P>
-
-<P>This command will completely remove a one or more users from the database.</P>
-<P>There is NO SECOND CHANCE.</P>
-<P>It goes without saying that you should use this command CAREFULLY!</P>
-
-<H2><A NAME="ss11.32">11.32</A> <A HREF="adminmanual.html#toc11.32">demonstrate (9)</A>
-</H2>
-
-<P><CODE><B>demonstrate <call> <command></B> Demonstrate a command to another user</CODE></P>
-
-<P>This command is provided so that sysops can demonstrate commands to
-other users. It runs a command as though that user had typed it in and
-then sends the output to that user, together with the command that
-caused it.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DEMO g7brn sh/dx iota oc209
- DEMO g1tlh set/here
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Note that this command is similar to SPOOF and will have the same side
-effects. Commands are run at the privilege of the user which is being
-demonstrated to.</P>
-
-<H2><A NAME="ss11.33">11.33</A> <A HREF="adminmanual.html#toc11.33">directory (0)</A>
-</H2>
-
-<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
-<B>directory own</B> List your own messages<BR>
-<B>directory new</B> List all new messages<BR>
-<B>directory to <call></B> List all messages to <call><BR>
-<B>directory from <call></B> List all messages from <call><BR>
-<B>directory subject <string></B> List all messages with <string> in subject<BR>
-<B>directory <nn></B> List last <nn> messages<BR>
-<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE></P>
-
-<P>List the messages in the messages directory.</P>
-<P>If there is a 'p' one space after the message number then it is a
-personal message. If there is a '-' between the message number and the
-'p' then this indicates that the message has been read.</P>
-<P>You can use shell escape characters such as '*' and '?' in the <call>
-fields.</P>
-<P>You can combine some of the various directory commands together eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DIR TO G1TLH 5
-or
- DIR SUBJECT IOTA 200-250
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can abbreviate all the commands to one letter and use ak1a syntax:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DIR/T G1* 10
- DIR/S QSL 10-100 5
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="ss11.34">11.34</A> <A HREF="adminmanual.html#toc11.34">directory (extended for sysops) (5)</A>
-</H2>
-
-<P>Works just like the user command except that sysops can see ALL messages.</P>
-
-<H2><A NAME="ss11.35">11.35</A> <A HREF="adminmanual.html#toc11.35">disconnect (8)</A>
-</H2>
-
-<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE></P>
-
-<P>Disconnect any <call> connected locally</P>
-
-<H2><A NAME="ss11.36">11.36</A> <A HREF="adminmanual.html#toc11.36">dx (0)</A>
-</H2>
-
-<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
-
-<P>This is how you send a DX Spot to other users. You can, in fact, now
-enter the <freq> and the <call> either way round. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will all give the same result. You can add some remarks to the end
-of the command and they will be added to the spot.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX FR0G 144600 this is a test
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can credit someone else by saying:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX by G1TLH FR0G 144.600 he isn't on the cluster
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The <freq> is compared against the available bands set up in the
-cluster. See SHOW/BANDS for more information.</P>
-
-<H2><A NAME="ss11.37">11.37</A> <A HREF="adminmanual.html#toc11.37">export (9)</A>
-</H2>
-
-<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE></P>
-
-<P>Export a message to a file. This command can only be executed on a local
-console with a fully privileged user. The file produced will be in a form
-ready to be imported back into the cluster by placing it in the import
-directory (/spider/msg/import).</P>
-<P>This command cannot overwrite an existing file. This is to provide some
-measure of security. Any files written will owned by the same user as the
-main cluster, otherwise you can put the new files anywhere the cluster can
-access. For example:-</P>
-<P>EXPORT 2345 /tmp/a</P>
-
-<H2><A NAME="ss11.38">11.38</A> <A HREF="adminmanual.html#toc11.38">export_users (9)</A>
-</H2>
-
-<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE></P>
-
-<P>Export the users database to a file in ascii format. If no filename
-is given then it will export the file to /spider/data/user_asc.</P>
-<P>If the file already exists it will be renamed to <filename>.o. In fact
-up to 5 generations of the file can be kept each one with an extra 'o' on the
-suffix. </P>
-<P>BE WARNED: this will write to any file you have write access to. No check is
-made on the filename (if any) that you specify.</P>
-
-<H2><A NAME="ss11.39">11.39</A> <A HREF="adminmanual.html#toc11.39">filtering (0)</A>
-</H2>
-
-<P><CODE><B>filtering</B> Filtering things in DXSpider</CODE></P>
-
-<P>There are a number of things you can filter in the DXSpider system. They
-all use the same general mechanism.</P>
-<P>In general terms you can create a 'reject' or an 'accept' filter which
-can have up to 10 lines in it. You do this using, for example:-</P>
-<P>accept/spots .....
-reject/spots .....</P>
-<P>where ..... are the specific commands for that type of filter. There
-are filters for spots, wwv, announce, wcy and (for sysops)
-connects. See each different accept or reject command reference for
-more details.</P>
-<P>There is also a command to clear out one or more lines in a filter and
-one to show you what you have set. They are:-</P>
-<P>clear/spots 1
-clear/spots all</P>
-<P>and </P>
-<P>show/filter</P>
-<P>There is clear/xxxx command for each type of filter.</P>
-<P>For now we are going to use spots for the examples, but you can apply
-the principles to all types of filter.</P>
-<P>There are two main types of filter 'accept' or 'reject'; which you use
-depends entirely on how you look at the world and what is least
-writing to achieve what you want. Each filter has 10 lines (of any
-length) which are tried in order. If a line matches then the action
-you have specified is taken (ie reject means ignore it and accept
-means gimme it).</P>
-<P>The important thing to remember is that if you specify a 'reject'
-filter (all the lines in it say 'reject/spots' (for instance) then if
-a spot comes in that doesn't match any of the lines then you will get
-it BUT if you specify an 'accept' filter then any spots that don't
-match are dumped. For example if I have a one line accept filter:-</P>
-<P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)</P>
-<P>then automatically you will ONLY get VHF spots from or to CQ zones 14
-15 and 16. If you set a reject filter like:</P>
-<P>reject/spots on hf/cw</P>
-<P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
-and will work it even on CW then you could say:-</P>
-<P>reject/spots on hf/cw and not info iota</P>
-<P>But in that case you might only be interested in iota and say:-</P>
-<P>accept/spots not on hf/cw or info iota</P>
-<P>which is exactly the same. You should choose one or the other until
-you are confortable with the way it works. Yes, you can mix them
-(actually you can have an accept AND a reject on the same line) but
-don't try this at home until you can analyse the results that you get
-without ringing up the sysop for help.</P>
-<P>You can arrange your filter lines into logical units, either for your
-own understanding or simply convenience. I have one set frequently:-</P>
-<P>reject/spots 1 on hf/cw
-reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) </P>
-<P>What this does is to ignore all HF CW spots (being a class B I can't
-read any CW and couldn't possibly be interested in HF :-) and also
-rejects any spots on VHF which don't either originate or spot someone
-in Europe.</P>
-<P>This is an exmaple where you would use the line number (1 and 2 in
-this case), if you leave the digit out, the system assumes '1'. Digits
-'0'-'9' are available.</P>
-<P>You can leave the word 'and' out if you want, it is implied. You can
-use any number of brackets to make the 'expression' as you want
-it. There are things called precedence rules working here which mean
-that you will NEED brackets in a situation like line 2 because,
-without it, will assume:-</P>
-<P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 </P>
-<P>annoying, but that is the way it is. If you use OR - use
-brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
-just 'and by_zone'.</P>
-<P>If you want to alter your filter you can just redefine one or more
-lines of it or clear out one line. For example:-</P>
-<P>reject/spots 1 on hf/ssb</P>
-<P>or </P>
-<P>clear/spots 1</P>
-<P>To remove the filter in its entirty:-</P>
-<P>clear/spots all</P>
-<P>There are similar CLEAR commands for the other filters:-</P>
-<P>clear/announce
-clear/wcy
-clear/wwv</P>
-<P>ADVANCED USERS:-</P>
-<P>Once you are happy with the results you get, you may like to experiment. </P>
-<P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, eg:</P>
-<P>rej/spot on hf/cw
-acc/spot on 0/30000
-acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)</P>
-<P>each filter slot actually has a 'reject' slot and an 'accept'
-slot. The reject slot is executed BEFORE the accept slot.</P>
-<P>It was mentioned earlier that after a reject test that doesn't match,
-the default for following tests is 'accept', the reverse is true for
-'accept'. In the example what happens is that the reject is executed
-first, any non hf/cw spot is passed to the accept line, which lets
-thru everything else on HF.</P>
-<P>The next filter line lets through just VHF/UHF spots from EU.</P>
-
-<H2><A NAME="ss11.40">11.40</A> <A HREF="adminmanual.html#toc11.40">forward/latlong (8)</A>
-</H2>
-
-<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE></P>
-
-<P>This command sends all the latitude and longitude information that your
-cluster is holding against callsigns. One advantage of recieving this
-information is that more locator information is held by you. This
-means that more locators are given on the DX line assuming you have
-<EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
-it is not recommended on slow links.</P>
-
-<H2><A NAME="ss11.41">11.41</A> <A HREF="adminmanual.html#toc11.41">forward/opername (1)</A>
-</H2>
-
-<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE></P>
-
-<P>This command sends out any information held in the user file which can
-be broadcast in PC41 protocol packets. This information is Name, QTH, Location
-and Homenode. PC41s are only sent for the information that is available.</P>
-
-<H2><A NAME="ss11.42">11.42</A> <A HREF="adminmanual.html#toc11.42">help (0)</A>
-</H2>
-
-<P><CODE><B>help <cmd></B> Get help on a command</CODE></P>
-
-<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
-to SH/DX, ANNOUNCE can be shortened to AN and so on.</P>
-<P>Look at the APROPOS <string> command which will search the help database
-for the <string> you specify and give you a list of likely commands
-to look at with HELP.</P>
-
-<H2><A NAME="ss11.43">11.43</A> <A HREF="adminmanual.html#toc11.43">init (5)</A>
-</H2>
-
-<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE></P>
-
-<P>This command attempts to re-initialise a link to a (usually) AK1A node
-that has got confused, usually by a protocol loop of some kind. It may
-work - but you usually will be better off simply disconnecting it (or
-better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
-node>).</P>
-<P>Best of luck - you will need it.</P>
-
-<H2><A NAME="ss11.44">11.44</A> <A HREF="adminmanual.html#toc11.44">kill (0)</A>
-</H2>
-
-<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE></P>
-
-<P>Delete a message from the local system. You will only be able to
-delete messages that you have originated or been sent (unless you are
-the sysop).</P>
-
-<H2><A NAME="ss11.45">11.45</A> <A HREF="adminmanual.html#toc11.45">kill (5)</A>
-</H2>
-
-<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
-<B>kill from <call></B> Remove all messages from a callsign<BR>
-<B>kill to <call></B> Remove all messages to a callsign<BR></CODE></P>
-
-<P>You can get rid of any message to or originating from your callsign using
-this command. You can remove more than one message at a time.</P>
-<P>As a sysop you can kill any message on the system.</P>
-
-<H2><A NAME="ss11.46">11.46</A> <A HREF="adminmanual.html#toc11.46">kill full (5)</A>
-</H2>
-
-<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE></P>
-
-<P>Delete a message (usually a 'bulletin') from the whole cluster system. </P>
-<P>This uses the subject field, so any messages that have exactly the same subject
-will be deleted. Beware!</P>
-
-<H2><A NAME="ss11.47">11.47</A> <A HREF="adminmanual.html#toc11.47">kill/expunge (6)</A>
-</H2>
-
-<P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE></P>
-
-<P>Deleting a message using the normal KILL commands only marks that message
-for deletion. The actual deletion only happens later (usually two days later).</P>
-<P>The KILL EXPUNGE command causes the message to be truly deleted more or less
-immediately.</P>
-<P>It otherwise is used in the same way as the KILL command.</P>
-
-
-<H2><A NAME="ss11.48">11.48</A> <A HREF="adminmanual.html#toc11.48">links (0)</A>
-</H2>
-
-<P><CODE><B>links</B> Show which nodes are physically connected</CODE></P>
-
-<P>This is a quick listing that shows which links are connected and
-some information about them. See WHO for a list of all connections.</P>
-
-
-<H2><A NAME="ss11.49">11.49</A> <A HREF="adminmanual.html#toc11.49">load/aliases (9)</A>
-</H2>
-
-<P><CODE><B>load/aliases</B> Reload the command alias table</CODE></P>
-
-<P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
-do this if you change this file whilst the cluster is running in order for the
-changes to take effect.</P>
-
-<H2><A NAME="ss11.50">11.50</A> <A HREF="adminmanual.html#toc11.50">load/badmsg (9)</A>
-</H2>
-
-<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE></P>
-
-<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
-the cluster is running. This table contains a number of perl regular
-expressions which are searched for in the fields targetted of each message.
-If any of them match then that message is immediately deleted on receipt. </P>
-
-<H2><A NAME="ss11.51">11.51</A> <A HREF="adminmanual.html#toc11.51">load/badwords (9)</A>
-</H2>
-
-<P><CODE><B>load/badwords</B> Reload the bad words table</CODE></P>
-
-<P>Reload the /spider/data/badwords file if you have changed it manually whilst
-the cluster is running. This file contains a list of words which, if found
-on certain text portions of PC protocol, will cause those protocol frames
-to be rejected. It will all put out a message if any of these words are
-used on the announce, dx and talk commands. The words can be one or
-more on a line, lines starting with '#' are ignored.</P>
-
-<H2><A NAME="ss11.52">11.52</A> <A HREF="adminmanual.html#toc11.52">load/bands (9)</A>
-</H2>
-
-<P><CODE><B>load/bands</B> Reload the band limits table</CODE></P>
-
-<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
-the cluster is running. </P>
-
-<H2><A NAME="ss11.53">11.53</A> <A HREF="adminmanual.html#toc11.53">load/cmd_cache (9)</A>
-</H2>
-
-<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE></P>
-
-<P>Normally, if you change a command file in the cmd or local_cmd tree it will
-automatially be picked up by the cluster program. Sometimes it can get confused
-if you are doing a lot of moving commands about or delete a command in the
-local_cmd tree and want to use the normal one again. Execute this command to
-reset everything back to the state it was just after a cluster restart.</P>
-
-<H2><A NAME="ss11.54">11.54</A> <A HREF="adminmanual.html#toc11.54">load/forward (9)</A>
-</H2>
-
-<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE></P>
-<P>Reload the /spider/msg/forward.pl file if you have changed it
-manually whilst the cluster is running.</P>
-
-<H2><A NAME="ss11.55">11.55</A> <A HREF="adminmanual.html#toc11.55">load/messages (9)</A>
-</H2>
-
-<P><CODE><B>load/messages</B> Reload the system messages file</CODE></P>
-
-<P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
-commands) you can have them take effect during a cluster session by executing this
-command. You need to do this if get something like :-</P>
-<P>unknown message 'xxxx' in lang 'en'</P>
-
-<H2><A NAME="ss11.56">11.56</A> <A HREF="adminmanual.html#toc11.56">load/prefixes (9)</A>
-</H2>
-
-<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE></P>
-
-<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
-whilst the cluster is running. </P>
-
-<H2><A NAME="ss11.57">11.57</A> <A HREF="adminmanual.html#toc11.57">merge (5)</A>
-</H2>
-
-<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE></P>
-
-<P>MERGE allows you to bring your spot and wwv database up to date. By default
-it will request the last 10 spots and 5 WWVs from the node you select. The
-node must be connected locally.</P>
-<P>You can request any number of spots or wwv and although they will be appended
-to your databases they will not duplicate any that have recently been added
-(the last 2 days for spots and last month for WWV data).</P>
-
-<H2><A NAME="ss11.58">11.58</A> <A HREF="adminmanual.html#toc11.58">msg (9)</A>
-</H2>
-
-<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE></P>
-
-<P>Alter message parameters like To, From, Subject, whether private or bulletin
-or return receipt (RR) is required or whether to keep this message from timing
-out.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can look at the status of a message by using:-</P>
-<P>STAT/MSG <msgno> </P>
-<P>This will display more information on the message than DIR does.</P>
-
-<H2><A NAME="ss11.59">11.59</A> <A HREF="adminmanual.html#toc11.59">pc (8)</A>
-</H2>
-
-<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE></P>
-
-<P>Send some arbitrary text to a locally connected callsign. No processing is done on
-the text. This command allows you to send PC Protocol to unstick things if problems
-arise (messages get stuck etc). eg:-</P>
-<P>pc gb7djk PC33^GB7TLH^GB7DJK^400^</P>
-<P>You can also use in the same way as a talk command to a connected user but
-without any processing, added of "from <blah> to <blah>" or whatever.</P>
-<P>pc G1TLH Try doing that properly!!!</P>
-
-<H2><A NAME="ss11.60">11.60</A> <A HREF="adminmanual.html#toc11.60">ping (1)</A>
-</H2>
-
-<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE></P>
-
-<P>his command allows you to send a frame to another cluster node on
-the network and get a return frame. The time it takes to do this
-is a good indication of the quality of the link. The actual time
-it takes is output to the console in seconds.
-Any visible cluster node can be PINGed.</P>
-
-
-<H2><A NAME="ss11.61">11.61</A> <A HREF="adminmanual.html#toc11.61">rcmd (1)</A>
-</H2>
-
-<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE></P>
-
-<P>This command allows you to send nearly any command to another DX Cluster
-node that is connected to the system. </P>
-<P>Whether you get any output is dependant on a) whether the other system knows
-that the node callsign of this cluster is in fact a node b) whether the
-other system is allowing RCMDs from this node and c) whether you have
-permission to send this command at all.</P>
-
-<H2><A NAME="ss11.62">11.62</A> <A HREF="adminmanual.html#toc11.62">read (0)</A>
-</H2>
-
-<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
-<B>read <msgno></B> Read the specified message<BR></CODE></P>
-
-<P>You can read any messages that are sent as 'non-personal' and also any
-message either sent by or sent to your callsign.</P>
-
-
-<H2><A NAME="ss11.63">11.63</A> <A HREF="adminmanual.html#toc11.63">read (extended for sysops) (5) </A>
-</H2>
-
-<P><CODE><B>read <msgno></B> Read a message on the system</CODE></P>
-
-<P>As a sysop you may read any message on the system</P>
-
-<H2><A NAME="ss11.64">11.64</A> <A HREF="adminmanual.html#toc11.64">reject/announce</A>
-</H2>
-
-<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
-for announce</CODE></P>
-
-<P>Create an 'reject this announce' line for a filter. </P>
-<P>An reject filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/ann by_zone 14,15,16 and not by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can use the tag 'all' to reject everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/ann all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss11.65">11.65</A> <A HREF="adminmanual.html#toc11.65">reject/announce (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/ann by G,M,2
- reject/ann input node_default by G,M,2
- reject/ann user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.66">11.66</A> <A HREF="adminmanual.html#toc11.66">reject/route (8)</A>
-</H2>
-
-<P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE></P>
-
-<P>Create an 'reject this routing PC Protocol' line for a filter. </P>
-
-<P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is NOT passed thru that interface. See HELP FILTERING for more info. Please
-read this to understand how filters work - it will save a lot of grief later on.
-You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You can use the tag 'all' to reject everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/route all (equiv to [very] restricted mode)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.67">11.67</A> <A HREF="adminmanual.html#toc11.67">reject/spots (0)</A>
-</H2>
-
-<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE></P>
-
-<P>Create a 'reject this spot' line for a filter. </P>
-<P>A reject filter line means that if the spot matches this filter it is
-dumped (not passed on). See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: on HF (but don't get
-too hung up about that)</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/spot 1 on hf
- rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can use the tag 'all' to reject everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/spot 3 all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss11.68">11.68</A> <A HREF="adminmanual.html#toc11.68">reject/spots (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
-Reject spot filter sysop version </CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.69">11.69</A> <A HREF="adminmanual.html#toc11.69">reject/wcy (0)</A>
-</H2>
-
-<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).</P>
-<P>This command is really provided for future use.</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss11.70">11.70</A> <A HREF="adminmanual.html#toc11.70">reject/wcy (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
-WCY reject filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>reject/wcy gb7djk all</P>
-
-<H2><A NAME="ss11.71">11.71</A> <A HREF="adminmanual.html#toc11.71">reject/wwv (0)</A>
-</H2>
-
-<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>for example </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/wwv by_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>is probably the only useful thing to do (which will only show WWV broadcasts
-by stations in the US).</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss11.72">11.72</A> <A HREF="adminmanual.html#toc11.72">reject/wwv (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
-WWV reject filter sysop version</CODE></P>
-
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/wwv db0sue-7 1 by_zone 4
- reject/wwv node_default all
-
- reject/wwv user_default by W
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.73">11.73</A> <A HREF="adminmanual.html#toc11.73">reply (0)</A>
-</H2>
-
-<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
-<B>reply <msgno></B> Reply (privately) to the specified message<BR>
-<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
-<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
-message<BR>
-<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE></P>
-
-<P>You can reply to a message and the subject will automatically have
-"Re:" inserted in front of it, if it isn't already present.</P>
-<P>You can also use all the extra qualifiers such as RR, PRIVATE,
-NOPRIVATE, B that you can use with the SEND command (see SEND
-for further details)</P>
-
-<H2><A NAME="ss11.74">11.74</A> <A HREF="adminmanual.html#toc11.74">send (0)</A>
-</H2>
-
-<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
-<B>send RR <call></B> Send a message and ask for a read receipt<BR>
-<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
-<B>send PRIVATE <call></B> Send a personal message<BR>
-<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE></P>
-
-<P>All the SEND commands will create a message which will be sent either to
-an individual callsign or to one of the 'bulletin' addresses. </P>
-<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
-it will mark the message as personal and send it to the cluster node that
-that callsign is connected to.</P>
-<P>You can have more than one callsign in all of the SEND commands.</P>
-<P>You can have multiple qualifiers so that you can have for example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SEND RR COPY 123 PRIVATE G1TLH G0RDI
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
-receive a read receipt when they have read the message.</P>
-<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
-SP is an alias for SEND PRIVATE</P>
-
-<H2><A NAME="ss11.75">11.75</A> <A HREF="adminmanual.html#toc11.75">set/address (0)</A>
-</H2>
-
-<P><CODE><B>set/address <your_address></B> Record your postal address</CODE></P>
-
-<P>Literally, record your address details on the cluster.</P>
-
-<H2><A NAME="ss11.76">11.76</A> <A HREF="adminmanual.html#toc11.76">set/announce (0)</A>
-</H2>
-
-<P><CODE><B>set/announce</B> Allow announce messages</CODE></P>
-
-<P>Allow announce messages to arrive at your terminal.</P>
-
-<H2><A NAME="ss11.77">11.77</A> <A HREF="adminmanual.html#toc11.77">set/arcluster (5)</A>
-</H2>
-
-<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
-the node_call an AR-Cluster type node</CODE></P>
-
-<P>Set the node_call as an AR-Cluster type node</P>
-
-<H2><A NAME="ss11.78">11.78</A> <A HREF="adminmanual.html#toc11.78">set/baddx (8)</A>
-</H2>
-
-<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
-of a dx spot being propagated</CODE></P>
-
-<P>Setting a word as 'baddx' will prevent spots with that word in the callsign
-field of a DX spot from going any further. They will not be displayed and they
-will not be sent onto other nodes.</P>
-<P>The word must be wriiten in full, no wild cards are allowed eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/baddx FORSALE VIDEO FR0G
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To allow a word again, use the following command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- unset/baddx VIDEO
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.79">11.79</A> <A HREF="adminmanual.html#toc11.79">set/badnode (6)</A>
-</H2>
-
-<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
-being propagated</CODE></P>
-
-<P>Setting a callsign as a 'badnode' will prevent spots from that node
-going any further. They will not be displayed and they will not be
-sent onto other nodes.</P>
-<P>The call can be a full or partial call (or a prefix), eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/badnode K1TTT
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will stop anything from K1TTT (including any SSID's)</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- unset/badnode K1TTT
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will allow spots from him again.</P>
-<P>Use with extreme care. This command may well be superceded by FILTERing.</P>
-
-<H2><A NAME="ss11.80">11.80</A> <A HREF="adminmanual.html#toc11.80">set/badspotter (8)</A>
-</H2>
-
-<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE></P>
-
-<P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
-going any further. They will not be displayed and they will not be
-sent onto other nodes.</P>
-<P>The call must be written in full, no wild cards are allowed eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/badspotter VE2STN
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will stop anything from VE2STN. If you want SSIDs as well then you must
-enter them specifically.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- unset/badspotter VE2STN
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will allow spots from him again.</P>
-<P>Use with extreme care. This command may well be superceded by FILTERing.</P>
-
-<H2><A NAME="ss11.81">11.81</A> <A HREF="adminmanual.html#toc11.81">set/badword (8)</A>
-</H2>
-
-<P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE></P>
-
-<P>Setting a word as a 'badword' will prevent things like spots,
-announces or talks with this word in the the text part from going any
-further. They will not be displayed and they will not be sent onto
-other nodes.</P>
-<P>The word must be written in full, no wild cards are allowed eg:-</P>
-<P>set/badword annihilate annihilated annihilation </P>
-<P>will stop anything with these words in the text.</P>
-<P>unset/badword annihilated</P>
-<P>will allow text with this word again.</P>
-
-
-<H2><A NAME="ss11.82">11.82</A> <A HREF="adminmanual.html#toc11.82">set/beep (0)</A>
-</H2>
-
-<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE></P>
-
-<P>Add a beep to DX and other terminal messages.</P>
-
-<H2><A NAME="ss11.83">11.83</A> <A HREF="adminmanual.html#toc11.83">set/bbs (5)</A>
-</H2>
-
-<P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE></P>
-
-<H2><A NAME="ss11.84">11.84</A> <A HREF="adminmanual.html#toc11.84">set/clx (5)</A>
-</H2>
-
-<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
-the node_call a CLX type node</CODE></P>
-
-<P>Set the node_call as a CLX type node</P>
-
-<H2><A NAME="ss11.85">11.85</A> <A HREF="adminmanual.html#toc11.85">set/debug (9)</A>
-</H2>
-
-<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE></P>
-
-<P>You can choose to log several different levels. The levels are</P>
-<P>chan
-state
-msg
-cron
-connect</P>
-<P>You can show what levels you are logging with the <EM>show/debug</EM>
-command.</P>
-<P>You can remove a debug level with unset/debug <name></P>
-
-<H2><A NAME="ss11.86">11.86</A> <A HREF="adminmanual.html#toc11.86">set/dx (0)</A>
-</H2>
-
-<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE></P>
-
-<P>You can stop DX messages with the <EM>unset/dx</EM> command</P>
-
-<H2><A NAME="ss11.87">11.87</A> <A HREF="adminmanual.html#toc11.87">set/dxgrid (0)</A>
-</H2>
-
-<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE></P>
-
-<P>Some logging programs do not like the additional information at
-the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
-command to remove the grid squares.</P>
-
-<H2><A NAME="ss11.88">11.88</A> <A HREF="adminmanual.html#toc11.88">set/dxnet (5)</A>
-</H2>
-
-<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
-the node_call a DXNet type node</CODE></P>
-
-<P>Set the node_call as a DXNet type node</P>
-
-<H2><A NAME="ss11.89">11.89</A> <A HREF="adminmanual.html#toc11.89">set/echo (0)</A>
-</H2>
-
-<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
-
-<P>If you are connected via a telnet session, different implimentations
-of telnet handle echo differently depending on whether you are
-connected via port 23 or some other port. You can use this command
-to change the setting appropriately. </P>
-<P>You can remove the echo with the <EM>unset/echo</EM> command</P>
-<P>The setting is stored in your user profile.</P>
-<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
-
-<H2><A NAME="ss11.90">11.90</A> <A HREF="adminmanual.html#toc11.90">set/email (0)</A>
-</H2>
-
-<P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE></P>
-
-<P>If any personal messages come in for your callsign then you can use
-these commands to control whether they are forwarded onto your email
-address. To enable the forwarding do something like:-</P>
-<P>SET/EMAIL mike.tubby@somewhere.com</P>
-<P>You can have more than one email address (each one separated by a space).
-Emails are forwarded to all the email addresses you specify.</P>
-<P>You can disable forwarding by:-</P>
-<P>UNSET/EMAIL</P>
-
-<H2><A NAME="ss11.91">11.91</A> <A HREF="adminmanual.html#toc11.91">set/here (0)</A>
-</H2>
-
-<P><CODE><B>set/here</B> Set the here flag</CODE></P>
-
-<P>Let others on the cluster know you are here by only displaying your
-callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
-command to let people know you are away. This simply puts brackets
-around your callsign to indicate you are not available.</P>
-
-<H2><A NAME="ss11.92">11.92</A> <A HREF="adminmanual.html#toc11.92">set/homenode (0)</A>
-</H2>
-
-<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE></P>
-
-<P>Tell the cluster system where you normally connect to. Any Messages sent
-to you will normally find their way there should you not be connected.
-eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/HOMENODE gb7djk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.93">11.93</A> <A HREF="adminmanual.html#toc11.93">set/hops (8)</A>
-</H2>
-
-<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
-Set hop count</CODE></P>
-
-<P>Set the hop count for a particular type of broadcast for a node.</P>
-<P>This command allows you to set up special hop counts for a node
-for currently: announce, spots, wwv and wcy broadcasts.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-eg:
- set/hops gb7djk ann 10
- set/hops gb7mbc spots 20
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Set SHOW/HOPS for information on what is already set. This command
-creates a filter and works in conjunction with the filter system. </P>
-
-<H2><A NAME="ss11.94">11.94</A> <A HREF="adminmanual.html#toc11.94">set/isolate (9)</A>
-</H2>
-
-<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE></P>
-
-<P>Connect a node to your system in such a way that you are a full protocol
-member of its network and can see all spots on it, but nothing either leaks
-out from it nor goes back into from the rest of the nodes connected to you.</P>
-<P>You can potentially connect several nodes in this way.</P>
-<P>You can see which nodes are isolated with the show/isolate (1) command.</P>
-<P>You can remove the isolation with the command unset/isolate.</P>
-
-<H2><A NAME="ss11.95">11.95</A> <A HREF="adminmanual.html#toc11.95">set/language (0)</A>
-</H2>
-
-<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE></P>
-
-<P>You can select the language that you want the cluster to use. Currently
-the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).</P>
-
-<H2><A NAME="ss11.96">11.96</A> <A HREF="adminmanual.html#toc11.96">set/location (0)</A>
-</H2>
-
-<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE></P>
-
-<P>You can set your latitude and longitude manually or alternatively use the
-<EM>set/qra</EM> command which will do the conversion for you.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/location 54 04 N 2 02 E
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="ss11.97">11.97</A> <A HREF="adminmanual.html#toc11.97">set/sys_location (9)</A>
-</H2>
-
-<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE></P>
-
-<P>In order to get accurate headings and such like you must tell the system
-what your latitude and longitude is. If you have not yet done a SET/QRA
-then this command will set your QRA locator for you. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/LOCATION 52 22 N 0 57 E
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.98">11.98</A> <A HREF="adminmanual.html#toc11.98">set/logininfo (0)</A>
-</H2>
-
-<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE></P>
-
-<P>Show users and nodes when they log in and out of the local cluster. You
-can stop these messages by using the <EM>unset/logininfo</EM> command.</P>
-
-
-<H2><A NAME="ss11.99">11.99</A> <A HREF="adminmanual.html#toc11.99">set/lockout (9)</A>
-</H2>
-
-<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE></P>
-
-<P>You can show who is locked out with the <EM>show/lockout</EM> command.
-To allow the user to connect again, use the <EM>unset/lockout</EM> command.</P>
-
-<H2><A NAME="ss11.100">11.100</A> <A HREF="adminmanual.html#toc11.100">set/name (0)</A>
-</H2>
-
-<P><CODE><B>set/name <your_name></B> Set your name</CODE></P>
-
-<P>Tell the cluster what your name is, eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/name Dirk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.101">11.101</A> <A HREF="adminmanual.html#toc11.101">set/node (9)</A>
-</H2>
-
-<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE></P>
-
-<P>Tell the system that the call(s) are to be treated as AK1A cluster and
-fed PC Protocol rather normal user commands.</P>
-<P>From version 1.41 you can also set the following types of cluster</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/spider
- set/dxnet
- set/clx
- set/arcluster
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.</P>
-
-<H2><A NAME="ss11.102">11.102</A> <A HREF="adminmanual.html#toc11.102">set/obscount (9)</A>
-</H2>
-
-<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE></P>
-
-<P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
-SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
-counter which is decremented on every outgoing ping and then reset to
-the 'obscount' value on every incoming ping. The default value of this
-parameter is 2. </P>
-<P>What this means is that a neighbouring node will be pinged twice at
-(default) 300 second intervals and if no reply has been heard just before
-what would be the third attempt, that node is disconnected.</P>
-<P>If a ping is heard then the obscount is reset to the full value. Using
-default values, if a node has not responded to a ping within 15 minutes,
-it is disconnected.</P>
-
-<H2><A NAME="ss11.103">11.103</A> <A HREF="adminmanual.html#toc11.103">set/page (0)</A>
-</H2>
-
-<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE></P>
-
-<P>Tell the system how many lines you wish on a page when the number of lines
-of output from a command is more than this. The default is 20. Setting it
-explicitly to 0 will disable paging. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/PAGE 30
- SET/PAGE 0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The setting is stored in your user profile.</P>
-
-<H2><A NAME="ss11.104">11.104</A> <A HREF="adminmanual.html#toc11.104">set/password (0)</A>
-</H2>
-
-<P><CODE><B>set/password</B> Set your own password</CODE></P>
-
-<P>This command only works for a 'telnet' user (currently). It will
-only work if you have a password already set. This initial password
-can only be set by the sysop.</P>
-<P>When you execute this command it will ask you for your old password,
-then ask you to type in your new password twice (to make sure you
-get it right). You may or may not see the data echoed on the screen
-as you type, depending on the type of telnet client you have.</P>
-
-<H2><A NAME="ss11.105">11.105</A> <A HREF="adminmanual.html#toc11.105">set/password (9)</A>
-</H2>
-
-<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE></P>
-
-<P>The password for a user can only be set by a full sysop. The string
-can contain any characters. </P>
-<P>The way this field is used depends on context. If it is being used in
-the SYSOP command context then you are offered 5 random numbers and you
-have to supply the corresponding letters. This is now mainly for ax25
-connections.</P>
-<P>If it is being used on incoming telnet connections then, if a password
-is set or the:</P>
-<P>set/var $main::passwdreq = 1</P>
-<P>command is executed in the startup script, then a password prompt is
-given after the normal 'login: ' prompt. </P>
-<P>The command "unset/password" is provided to allow a sysop to remove a
-users password completely in case a user forgets or loses their password.</P>
-
-<H2><A NAME="ss11.106">11.106</A> <A HREF="adminmanual.html#toc11.106">set/pinginterval (9)</A>
-</H2>
-
-<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE></P>
-
-<P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
-in order to determine the rolling quality of the link and, in future, to
-affect routing decisions. The default interval is 300 secs or 5 minutes.</P>
-<P>You can use this command to set a different interval. Please don't. </P>
-<P>But if you do the value you enter is treated as minutes up 60 and seconds
-for numbers greater than that.</P>
-<P>This is used also to help determine when a link is down at the far end
-(as certain cluster software doesn't always notice), see SET/OBSCOUNT
-for more information.</P>
-
-<H2><A NAME="ss11.107">11.107</A> <A HREF="adminmanual.html#toc11.107">set/privilege (9)</A>
-</H2>
-
-<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE></P>
-
-<P>Set the privilege level on a callsign. The privilege levels that pertain
-to commands are as default:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- 0 - normal user
- 1 - allow remote nodes normal user RCMDs
- 5 - various privileged commands (including shutdown, but not disc-
- connect), the normal level for another node.
- 8 - more privileged commands (including disconnect)
- 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
- LEVEL.
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you are a sysop and you come in as a normal user on a remote connection
-your privilege will automatically be set to 0.</P>
-
-<H2><A NAME="ss11.108">11.108</A> <A HREF="adminmanual.html#toc11.108">set/spider (5)</A>
-</H2>
-
-<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
-the node_call a DXSpider type node</CODE></P>
-
-<P>Set the node_call as a DXSpider type node</P>
-
-<H2><A NAME="ss11.109">11.109</A> <A HREF="adminmanual.html#toc11.109">set/sys_qra (9)</A>
-</H2>
-
-<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE></P>
-
-<H2><A NAME="ss11.110">11.110</A> <A HREF="adminmanual.html#toc11.110">set/qra (0)</A>
-</H2>
-
-<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE></P>
-
-<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
-done a SET/LOCATION then your latitude and longitude will be set roughly
-correctly (assuming your locator is correct ;-). For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/QRA JO02LQ
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.111">11.111</A> <A HREF="adminmanual.html#toc11.111">set/qth (0)</A>
-</H2>
-
-<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE></P>
-
-<P>Tell the system where your are. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/qth East Dereham, Norfolk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.112">11.112</A> <A HREF="adminmanual.html#toc11.112">set/register (9)</A>
-</H2>
-
-<P><CODE><B>set/register <call></B> Mark a user as registered</CODE></P>
-
-<P>Registration is a concept that you can switch on by executing the</P>
-<P>set/var $main::regreq = 1 </P>
-<P>command (usually in your startup file)</P>
-<P>If a user is NOT registered then, firstly, instead of the normal
-motd file (/spider/data/motd) being sent to the user at startup, the
-user is sent the motd_nor file instead. Secondly, the non registered
-user only has READ-ONLY access to the node. The non-registered user
-cannot use DX, ANN etc. </P>
-<P>The only exception to this is that a non-registered user can TALK or
-SEND messages to the sysop.</P>
-<P>To unset a user use the 'unset/register' command</P>
-
-<H2><A NAME="ss11.113">11.113</A> <A HREF="adminmanual.html#toc11.113">set/talk (0)</A>
-</H2>
-
-<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE></P>
-
-<P>Allow talk messages to arrive at your console. You can switch off
-talks with the <EM>unset/talk</EM> command.</P>
-
-<H2><A NAME="ss11.114">11.114</A> <A HREF="adminmanual.html#toc11.114">set/wcy (0)</A>
-</H2>
-
-<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE></P>
-
-<P>Allow WCY information to be seen at your console. You can switch off
-WCY messages with the <EM>unset/wcy</EM> command.</P>
-
-<H2><A NAME="ss11.115">11.115</A> <A HREF="adminmanual.html#toc11.115">set/wwv (0)</A>
-</H2>
-
-<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE></P>
-
-<P>Allow WWV information to be seen at your console. You can switch off
-WWV messages with the <EM>unset/wwv</EM> command.</P>
-
-<H2><A NAME="ss11.116">11.116</A> <A HREF="adminmanual.html#toc11.116">set/wx (0)</A>
-</H2>
-
-<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE></P>
-
-<P>Allow WX information to be seen at your console. You can switch off
-WX messages with the <EM>unset/wx</EM> command.</P>
-
-<H2><A NAME="ss11.117">11.117</A> <A HREF="adminmanual.html#toc11.117">show/baddx (1)</A>
-</H2>
-
-<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE></P>
-
-<P>Display all the bad dx callsigns in the system, see SET/BADDX
-for more information.</P>
-
-<H2><A NAME="ss11.118">11.118</A> <A HREF="adminmanual.html#toc11.118">show/badnode (6)</A>
-</H2>
-
-<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE></P>
-
-<P>Display all the bad node callsigns in the system, see SET/BADNODE
-for more information.</P>
-
-<H2><A NAME="ss11.119">11.119</A> <A HREF="adminmanual.html#toc11.119">show/badspotter (1)</A>
-</H2>
-
-<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE></P>
-
-<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
-for more information.</P>
-
-<H2><A NAME="ss11.120">11.120</A> <A HREF="adminmanual.html#toc11.120">show/badword (1)</A>
-</H2>
-
-<P><CODE><B>show/badword</B> Show all the bad words in the system</CODE></P>
-
-<P>Display all the bad words in the system, see SET/BADWORD
-for more information.</P>
-
-<H2><A NAME="ss11.121">11.121</A> <A HREF="adminmanual.html#toc11.121">show/configuration (0)</A>
-</H2>
-
-<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE></P>
-
-<P>This command allows you to see all the users that can be seen
-and the nodes to which they are connected. With the optional <EM>node</EM>,
-you can specify a particular node to look at.</P>
-<P>This command is normally abbreviated to: sh/c</P>
-<P>BE WARNED: the list that is returned can be VERY long</P>
-
-<H2><A NAME="ss11.122">11.122</A> <A HREF="adminmanual.html#toc11.122">show/configuration/node (0)</A>
-</H2>
-
-<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE></P>
-
-<P>Show all the nodes connected locally and the nodes they have connected.</P>
-
-<H2><A NAME="ss11.123">11.123</A> <A HREF="adminmanual.html#toc11.123">show/connect (1)</A>
-</H2>
-
-<P><CODE><B>show/connect</B> Show all the active connections</CODE></P>
-
-<P>This command shows information on all the active connections known to
-the node. This command gives slightly more information than WHO.</P>
-
-<H2><A NAME="ss11.124">11.124</A> <A HREF="adminmanual.html#toc11.124">show/date (0)</A>
-</H2>
-
-<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
-the local time</CODE></P>
-
-<P>This is very nearly the same as SHOW/TIME, the only difference the format
-of the date string if no arguments are given.</P>
-<P>If no prefixes or callsigns are given then this command returns the local
-time and UTC as the computer has it right now. If you give some prefixes
-then it will show UTC and UTC + the local offset (not including DST) at
-the prefixes or callsigns that you specify.</P>
-
-<H2><A NAME="ss11.125">11.125</A> <A HREF="adminmanual.html#toc11.125">show/debug (9)</A>
-</H2>
-
-<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE></P>
-
-<P>The levels can be set with <EM>set/debug</EM></P>
-
-<H2><A NAME="ss11.126">11.126</A> <A HREF="adminmanual.html#toc11.126">show/dx (0)</A>
-</H2>
-
-<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE></P>
-
-<P>If you just type SHOW/DX you will get the last so many spots
-(sysop configurable, but usually 10).</P>
-<P>In addition you can add any number of these options in very nearly
-any order to the basic SHOW/DX command, they are:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-on <band> - eg 160m 20m 2m 23cm 6mm
-on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
-<number> - the number of spots you want
-<from>-<to> - <from> spot no <to> spot no in
- the selected list
-
-<prefix> - for a spotted callsign beginning with <prefix>
-*<suffix> - for a spotted callsign ending in <suffix>
-*<string>* - for a spotted callsign containing <string>
-
-day <number> - starting <number> days ago
-day <from>-<to> - <from> days <to> days ago
-
-info <text> - any spots containing <text> in the info or remarks
-
-by <call> - any spots spotted by <call> (spotter <call>
- is the same).
-
-qsl - this automatically looks for any qsl info on the call
- held in the spot database.
-
-iota [<iota>] - If the iota island number is missing it will
- look for the string iota and anything which looks like
- an iota island number. If you specify then it will look
- for that island.
-
-qra [<locator>] - this will look for the specific locator if
- you specify one or else anything that looks like a locator.
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>e.g. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.127">11.127</A> <A HREF="adminmanual.html#toc11.127">show/dxcc (0)</A>
-</H2>
-
-<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
-
-<P>This command takes the <prefix> (which can be a full or partial
-callsign if desired), looks up which internal country number it is
-and then displays all the spots as per SH/DX for that country.</P>
-<P>The options for SHOW/DX also apply to this command.
-e.g. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
- SH/DXCC G
- SH/DXCC W on 20m info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.128">11.128</A> <A HREF="adminmanual.html#toc11.128">sh/dxstats (0)</A>
-</H2>
-
-<P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE></P>
-
-<P>Show the total DX spots for the last 31 days</P>
-
-
-<H2><A NAME="ss11.129">11.129</A> <A HREF="adminmanual.html#toc11.129">show/files (0)</A>
-</H2>
-
-<P><CODE><B>show/files [<filearea> [<string>]]</B> List
-the contents of a filearea</CODE></P>
-
-<P>SHOW/FILES on its own will show you a list of the various fileareas
-available on the system. To see the contents of a particular file
-area type:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/FILES <filearea>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>where <filearea> is the name of the filearea you want to see the
-contents of.</P>
-<P>You can also use shell globbing characters like '*' and '?' in a
-string to see a selection of files in a filearea eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/FILES bulletins arld*
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>See also TYPE - to see the contents of a file.</P>
-
-<H2><A NAME="ss11.130">11.130</A> <A HREF="adminmanual.html#toc11.130">show/filter (0)</A>
-</H2>
-
-<P><CODE><B>show/filter</B> Show the filters you have set</CODE></P>
-
-<P>Show the contents of all the filters that are set by you. This command
-displays all the filters set - for all the various categories.</P>
-
-<H2><A NAME="ss11.131">11.131</A> <A HREF="adminmanual.html#toc11.131">show/filter (extended for sysops) (5)</A>
-</H2>
-
-<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE></P>
-
-<P>A sysop can look at any filters that have been set.</P>
-
-<H2><A NAME="ss11.132">11.132</A> <A HREF="adminmanual.html#toc11.132">show/hfstats (0)</A>
-</H2>
-
-<P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE></P>
-
-<P>Show the HF DX spots breakdown by band for the last 31 days</P>
-
-<H2><A NAME="ss11.133">11.133</A> <A HREF="adminmanual.html#toc11.133">show/hftable (0)</A>
-</H2>
-
-<P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE></P>
-
-<P>Show the HF DX Spotter table for your country for the last 31 days</P>
-
-<H2><A NAME="ss11.134">11.134</A> <A HREF="adminmanual.html#toc11.134">show/hops (8)</A>
-</H2>
-
-<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE></P>
-
-<P>This command shows the hop counts set up for a node. You can specify
-which category you want to see. If you leave the category out then
-all the categories will be listed.</P>
-
-<H2><A NAME="ss11.135">11.135</A> <A HREF="adminmanual.html#toc11.135">show/isolate (1)</A>
-</H2>
-
-<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE></P>
-
-<P>Show which nodes are currently set to be isolated.</P>
-
-<H2><A NAME="ss11.136">11.136</A> <A HREF="adminmanual.html#toc11.136">show/lockout (9)</A>
-</H2>
-
-<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE></P>
-
-<P>Show a list of callsigns that have been excluded (locked out) of the
-cluster locally with the <EM>set/lockout</EM> command</P>
-
-<H2><A NAME="ss11.137">11.137</A> <A HREF="adminmanual.html#toc11.137">show/log (8)</A>
-</H2>
-
-<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE></P>
-
-<P>This command outputs a short section of the system log. On its own
-it will output a general logfile. With the optional callsign it will
-show output from the log associated with that callsign.</P>
-
-<H2><A NAME="ss11.138">11.138</A> <A HREF="adminmanual.html#toc11.138">show/moon (0)</A>
-</H2>
-
-<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
-rise and set times</CODE></P>
-
-<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
-together with the azimuth and elevation of the sun currently at those
-locations.</P>
-<P>If you don't specify any prefixes or callsigns, it will show the times for
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
-together with the current azimuth and elevation.</P>
-<P>In addition, it will show the gain or loss dB relative to the nominal
-distance of 385,000Km due to the ellipsoidal nature of the orbit.</P>
-<P>If all else fails it will show the Moonrise and set times for the node
-that you are connected to. </P>
-<P>For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MOON
- SH/MOON G1TLH W5UN
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.139">11.139</A> <A HREF="adminmanual.html#toc11.139">show/muf (0)</A>
-</H2>
-
-<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
-the likely propagation to <prefix></CODE></P>
-
-<P>This command allow you to estimate the likelihood of you contacting
-a station with the prefix you have specified. The output assumes a modest
-power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)</P>
-<P>The result predicts the most likely operating frequencies and signal
-levels for high frequency (shortwave) radio propagation paths on
-specified days of the year and hours of the day. It is most useful for
-paths between 250 km and 6000 km, but can be used with reduced accuracy
-for paths shorter or longer than this.</P>
-<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
-used to predict the MUF given the predicted flux, day of the year,
-hour of the day and geographic coordinates of the transmitter and
-receiver. This routine is reasonably accurate for the purposes here,
-with a claimed RMS error of 3.8 MHz, but much smaller and less complex
-than the programs used by major shortwave broadcasting organizations,
-such as the Voice of America.</P>
-<P>The command will display some header information detailing its
-assumptions, together with the locations, latitude and longitudes and
-bearings. It will then show UTC (UT), local time at the other end
-(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
-(Zen) and the likely signal strengths. Then for each frequency for which
-the system thinks there is a likelihood of a circuit it prints a value.</P>
-<P>The value is currently a likely S meter reading based on the conventional
-6dB / S point scale. If the value has a '+' appended it means that it is
-1/2 an S point stronger. If the value is preceeded by an 'm' it means that
-there is likely to be much fading and by an 's' that the signal is likely
-to be noisy. </P>
-<P>By default SHOW/MUF will show the next two hours worth of data. You
-can specify anything up to 24 hours worth of data by appending the no of
-hours required after the prefix. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>produces:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
- Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
- Location Lat / Long Azim
- East Dereham, Norfolk 52 41 N 0 57 E 47
- United-States-W 43 0 N 87 54 W 299
- UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
- 18 23 11.5 -35 mS0+ mS2 S3
- 19 0 11.2 -41 mS0+ mS2 S3
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>indicating that you will have weak, fading circuits on top band and
-80m but usable signals on 40m (about S3).</P>
-<P>inputting:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W 24
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will get you the above display, but with the next 24 hours worth of
-propagation data.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W L 24
- SH/MUF W 24 Long
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Gives you an estimate of the long path propagation characterics. It
-should be noted that the figures will probably not be very useful, nor
-terrible accurate, but it is included for completeness.</P>
-
-<H2><A NAME="ss11.140">11.140</A> <A HREF="adminmanual.html#toc11.140">show/newconfiguration (0)</A>
-</H2>
-
-<P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE></P>
-
-<P>This command allows you to see all the users that can be seen
-and the nodes to which they are connected. </P>
-<P>This command produces essentially the same information as
-SHOW/CONFIGURATION except that it shows all the duplication of
-any routes that might be present It also uses a different format
-which may not take up quite as much space if you don't have any
-loops.</P>
-<P>BE WARNED: the list that is returned can be VERY long</P>
-
-<H2><A NAME="ss11.141">11.141</A> <A HREF="adminmanual.html#toc11.141">show/newconfiguration/node (0)</A>
-</H2>
-
-<P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE></P>
-
-<P>Show all the nodes connected to this node in the new format.</P>
-
-<H2><A NAME="ss11.142">11.142</A> <A HREF="adminmanual.html#toc11.142">show/node (1)</A>
-</H2>
-
-<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
-number of nodes</CODE></P>
-
-<P>Show the type and version (if connected) of the nodes specified on the
-command line. If no callsigns are specified then a sorted list of all
-the non-user callsigns known to the system will be displayed.</P>
-
-<H2><A NAME="ss11.143">11.143</A> <A HREF="adminmanual.html#toc11.143">show/prefix (0)</A>
-</H2>
-
-<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE></P>
-
-<P>This command takes the <callsign> (which can be a full or partial
-callsign or a prefix), looks up which internal country number
-it is and then displays all the relevant prefixes for that country
-together with the internal country no, the CQ and ITU regions. </P>
-<P>See also SHOW/DXCC</P>
-
-
-<H2><A NAME="ss11.144">11.144</A> <A HREF="adminmanual.html#toc11.144">show/program (5)</A>
-</H2>
-
-<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE></P>
-
-<P>Show the name and location where every program module was load from. This
-is useful for checking where you think you have loaded a .pm file from.</P>
-
-<H2><A NAME="ss11.145">11.145</A> <A HREF="adminmanual.html#toc11.145">show/qra (0)</A>
-</H2>
-
-<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
-between locators<BR>
-<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE></P>
-
-<P>This is a multipurpose command that allows you either to calculate the
-distance and bearing between two locators or (if only one locator is
-given on the command line) the distance and beraing from your station
-to the locator. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/QRA IO92QL
-SH/QRA JN06 IN73
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The first example will show the distance and bearing to the locator from
-yourself, the second example will calculate the distance and bearing from
-the first locator to the second. You can use 4 or 6 character locators.</P>
-<P>It is also possible to convert a latitude and longitude to a locator by
-using this command with a latitude and longitude as an argument, for
-example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/QRA 52 41 N 0 58 E
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.146">11.146</A> <A HREF="adminmanual.html#toc11.146">show/qrz (0)</A>
-</H2>
-
-<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
-
-<P>This command queries the QRZ callbook server on the internet
-and returns any information available for that callsign. This service
-is provided for users of this software by http://www.qrz.com </P>
-
-<H2><A NAME="ss11.147">11.147</A> <A HREF="adminmanual.html#toc11.147">show/registered (9)</A>
-</H2>
-
-<P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE></P>
-
-<H2><A NAME="ss11.148">11.148</A> <A HREF="adminmanual.html#toc11.148">show/route (0)</A>
-</H2>
-
-<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE></P>
-
-<P>This command allows you to see to which node the callsigns specified are
-connected. It is a sort of inverse sh/config.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- sh/route n2tly
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.149">11.149</A> <A HREF="adminmanual.html#toc11.149">show/satellite (0)</A>
-</H2>
-
-<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
-Show satellite tracking data</CODE></P>
-
-<P>Show the tracking data from your location to the satellite of your choice
-from now on for the next few hours.</P>
-<P>If you use this command without a satellite name it will display a list
-of all the satellites known currently to the system. </P>
-<P>If you give a name then you can obtain tracking data of all the passes
-that start and finish 5 degrees below the horizon. As default it will
-give information for the next three hours for every five minute period.</P>
-<P>You can alter the number of hours and the step size, within certain
-limits. </P>
-<P>Each pass in a period is separated with a row of '-----' characters</P>
-<P>So for example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/SAT AO-10
-SH/SAT FENGYUN1 12 2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.150">11.150</A> <A HREF="adminmanual.html#toc11.150">show/sun (0)</A>
-</H2>
-
-<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
-sun rise and set times</CODE></P>
-
-<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
-together with the azimuth and elevation of the sun currently at those
-locations.</P>
-<P>If you don't specify any prefixes or callsigns, it will show the times for
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
-together with the current azimuth and elevation.</P>
-<P>If all else fails it will show the sunrise and set times for the node
-that you are connected to. </P>
-<P>For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/SUN
- SH/SUN G1TLH K9CW ZS
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.151">11.151</A> <A HREF="adminmanual.html#toc11.151">show/time (0)</A>
-</H2>
-
-<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
-the local time</CODE></P>
-
-<P>If no prefixes or callsigns are given then this command returns the local
-time and UTC as the computer has it right now. If you give some prefixes
-then it will show UTC and UTC + the local offset (not including DST) at
-the prefixes or callsigns that you specify.</P>
-
-<H2><A NAME="ss11.152">11.152</A> <A HREF="adminmanual.html#toc11.152">show/vhfstats (0)</A>
-</H2>
-
-<P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE></P>
-
-<P>Show the VHF DX spots breakdown by band for the last 31 days</P>
-
-<H2><A NAME="ss11.153">11.153</A> <A HREF="adminmanual.html#toc11.153">show/vhftable (0)</A>
-</H2>
-
-<P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE></P>
-
-<P>Show the VHF DX Spotter table for your country for the last 31 days</P>
-
-<H2><A NAME="ss11.154">11.154</A> <A HREF="adminmanual.html#toc11.154">show/wcy (0)</A>
-</H2>
-
-<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
-<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE></P>
-
-<P>Display the most recent WCY information that has been received by the system</P>
-
-<H2><A NAME="ss11.155">11.155</A> <A HREF="adminmanual.html#toc11.155">show/wwv (0)</A>
-</H2>
-
-<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
-<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE></P>
-
-<P>Display the most recent WWV information that has been received by the system</P>
-
-
-<H2><A NAME="ss11.156">11.156</A> <A HREF="adminmanual.html#toc11.156">shutdown (5)</A>
-</H2>
-
-<P><CODE><B>shutdown</B> Shutdown the cluster</CODE></P>
-
-<P>Shutdown the cluster and disconnect all the users. If you have Spider
-set to respawn in /etc/inittab it will of course restart.</P>
-
-<H2><A NAME="ss11.157">11.157</A> <A HREF="adminmanual.html#toc11.157">spoof (9)</A>
-</H2>
-
-<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE></P>
-
-<P>This is a very simple yet powerful command for the sysop. It allows you to
-issue commands as if you were a different user. This is very useful for the
-kind of things that users seem to always get wrong.. like home_node for
-example.</P>
-
-<H2><A NAME="ss11.158">11.158</A> <A HREF="adminmanual.html#toc11.158">stat/db (5)</A>
-</H2>
-
-<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE></P>
-
-<P>Show the internal status of a database descriptor.</P>
-<P>Depending on your privilege level you will see more or less information.
-This command is unlikely to be of much use to anyone other than a sysop.</P>
-
-<H2><A NAME="ss11.159">11.159</A> <A HREF="adminmanual.html#toc11.159">stat/channel (5)</A>
-</H2>
-
-<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE></P>
-
-<P>Show the internal status of the channel object either for the channel that
-you are on or else for the callsign that you asked for.</P>
-<P>Only the fields that are defined (in perl term) will be displayed.</P>
-
-<H2><A NAME="ss11.160">11.160</A> <A HREF="adminmanual.html#toc11.160">stat/msg (5)</A>
-</H2>
-
-<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE></P>
-
-<P>This command shows the internal status of a message and includes information
-such as to whom it has been forwarded, its size, origin etc etc.</P>
-
-<P>If no message number is given then the status of the message system is
-displayed.</P>
-
-<H2><A NAME="ss11.161">11.161</A> <A HREF="adminmanual.html#toc11.161">stat/route_node (5)</A>
-</H2>
-
-<P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE></P>
-
-<H2><A NAME="ss11.162">11.162</A> <A HREF="adminmanual.html#toc11.162">stat/route_user (5)</A>
-</H2>
-
-<P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE></P>
-
-<H2><A NAME="ss11.163">11.163</A> <A HREF="adminmanual.html#toc11.163">stat/user (5)</A>
-</H2>
-
-<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE></P>
-
-<P>Shows the full contents of a user record including all the secret flags
-and stuff.</P>
-<P>Only the fields that are defined (in perl term) will be displayed.</P>
-
-<H2><A NAME="ss11.164">11.164</A> <A HREF="adminmanual.html#toc11.164">sysop (0)</A>
-</H2>
-
-<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
-
-<P>The system automatically reduces your privilege level to that of a
-normal user if you login in remotely. This command allows you to
-regain your normal privilege level. It uses the normal system: five
-numbers are returned that are indexes into the character array that is
-your assigned password (see SET/PASSWORD). The indexes start from
-zero.</P>
-<P>You are expected to return a string which contains the characters
-required in the correct order. You may intersperse those characters
-with others to obscure your reply for any watchers. For example (and
-these values are for explanation :-):</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>you type:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>They will all match. If there is no password you will still be offered
-numbers but nothing will happen when you input a string. Any match is
-case sensitive.</P>
-
-<H2><A NAME="ss11.165">11.165</A> <A HREF="adminmanual.html#toc11.165">talk (0)</A>
-</H2>
-
-<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
-<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
-<B>talk <callsign> > <node_call> [<text>]</B>
-Send a text message to <callsign> via <node_call></CODE></P>
-
-<P>Send a short message to any other station that is visible on the cluster
-system. You can send it to anyone you can see with a SHOW/CONFIGURATION
-command, they don't have to be connected locally.</P>
-<P>The second form of TALK is used when other cluster nodes are connected
-with restricted information. This usually means that they don't send
-the user information usually associated with logging on and off the cluster.</P>
-<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
-see GB7TLH in the SH/C list but with no users, then you would use the
-second form of the talk message.</P>
-<P>If you want to have a ragchew with someone you can leave the text message
-out and the system will go into 'Talk' mode. What this means is that a
-short message is sent to the recipient telling them that you are in a 'Talking'
-frame of mind and then you just type - everything you send will go to the
-station that you asked for. </P>
-<P>All the usual announcements, spots and so on will still come out on your
-terminal.</P>
-<P>If you want to do something (such as send a spot) you precede the normal
-command with a '/' character, eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
- /HELP talk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To leave talk mode type:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- /EX
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss11.166">11.166</A> <A HREF="adminmanual.html#toc11.166">type (0)</A>
-</H2>
-
-<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE></P>
-
-<P>Type out the contents of a file in a filearea. So, for example, in
-filearea 'bulletins' you want to look at file 'arld051' you would
-enter:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- TYPE bulletins/arld051
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>See also SHOW/FILES to see what fileareas are available and a
-list of content.</P>
-
-<H2><A NAME="ss11.167">11.167</A> <A HREF="adminmanual.html#toc11.167">who (0)</A>
-</H2>
-
-<P><CODE><B>who</B> Show who is physically connected locally</CODE></P>
-
-<P>This is a quick listing that shows which callsigns are connected and
-what sort of connection they have</P>
-
-<H2><A NAME="ss11.168">11.168</A> <A HREF="adminmanual.html#toc11.168">wx (0)</A>
-</H2>
-
-<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
-<B>wx full <text> </B> Send a weather message to all cluster users</CODE></P>
-
-<P>Weather messages can sometimes be useful if you are experiencing an extreme
-that may indicate enhanced conditions</P>
-
-<H2><A NAME="ss11.169">11.169</A> <A HREF="adminmanual.html#toc11.169">wx (enhanced for sysops) (5)</A>
-</H2>
-
-<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE></P>
-
-<P>Send a weather message only to other cluster nodes and not to general users.</P>
-
-
-
-<HR>
-Next
-<A HREF="adminmanual-10.html">Previous</A>
-<A HREF="adminmanual.html#toc11">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Other filters</TITLE>
- <LINK HREF="adminmanual-3.html" REL=next>
- <LINK HREF="adminmanual-1.html" REL=previous>
- <LINK HREF="adminmanual.html#toc2" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-3.html">Next</A>
-<A HREF="adminmanual-1.html">Previous</A>
-<A HREF="adminmanual.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2.</A> <A HREF="adminmanual.html#toc2">Other filters</A></H2>
-
-<H2><A NAME="ss2.1">2.1</A> <A HREF="adminmanual.html#toc2.1">Filtering Mail</A>
-</H2>
-
-<P>In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
-this to badmsg.pl and edit the file. The original looks something like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-# the list of regexes for messages that we won't store having
-# received them (bear in mind that we must receive them fully before
-# we can bin them)
-
-
-# The format of each line is as follows
-
-# type source pattern
-# P/B/F T/F/O/S regex
-
-# type: P - private, B - bulletin (msg), F - file (ak1a bull)
-# source: T - to field, F - from field, O - origin, S - subject
-# pattern: a perl regex on the field requested
-
-# Currently only type B and P msgs are affected by this code.
-#
-# The list is read from the top down, the first pattern that matches
-# causes the action to be taken.
-
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-
-
-
-package DXMsg;
-
-@badmsg = (
-'B', 'T', 'SALE',
-'B', 'T', 'WANTED',
-'B', 'S', 'WANTED',
-'B', 'S', 'SALE',
-'B', 'S', 'WTB',
-'B', 'S', 'WTS',
-'B', 'T', 'FS',
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>I think this is fairly self explanatory. It is simply a list of subject
-headers that we do not want to pass on to either the users of the cluster or
-the other cluster nodes that we are linked to. This is usually because of
-rules and regulations pertaining to items for sale etc in a particular country.</P>
-
-
-<H2><A NAME="ss2.2">2.2</A> <A HREF="adminmanual.html#toc2.2">Filtering words from text fields in Announce, Talk and DX spots</A>
-</H2>
-
-<P>From version 1.48 onwards the interface to this has changed. You can now
-use the commands <EM>set/badword</EM> to add words that you are not prepared
-to see on the cluster, <EM>unset/badword</EM> to allow that word again and
-<EM>show/badword</EM> to list the words that you have set.</P>
-
-<P>If you have a previous <EM>/spider/data/badwords</EM>, the first time you start
-the node, it will read and convert this file to the new commands. The old style
-file will then be removed.</P>
-
-<H2><A NAME="ss2.3">2.3</A> <A HREF="adminmanual.html#toc2.3">Stopping (possibly bad) DX Spots from Nodes or Spotters</A>
-</H2>
-
-<P>
-There are a number of commands that control whether a spot progresses
-any further by regarding it as "bad" in some way.</P>
-
-<P>A DX Spot has a number of fields which can be checked to see whether they
-contain "bad" values, they are: the DX callsign itself, the Spotter and
-the Originating Node.</P>
-
-<P>There are a set of commands which allow the sysop to control whether a
-spot continues:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/baddx
-set/badspotter
-set/badnode
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>These work in the same as the <EM>set/badword</EM> command, you can add
-any words or callsigns or whatever to the appropriate database. For
-example, to stop a spot from a particular node you do:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/badnode gb7djk gb7dxc
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>a bad spotter:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/badspotter b0mb p1rat nocall
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and some bad dx:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/baddx video wsjt
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can remove a word using the appropriate unset command
-(<EM>unset/baddx, unset/badspotter, unset/badnode</EM>) or list them
-using one of <EM>show/baddx, show/badspotter</EM> and
-<EM>show/badnode</EM>.</P>
-
-<HR>
-<A HREF="adminmanual-3.html">Next</A>
-<A HREF="adminmanual-1.html">Previous</A>
-<A HREF="adminmanual.html#toc2">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Mail</TITLE>
- <LINK HREF="adminmanual-4.html" REL=next>
- <LINK HREF="adminmanual-2.html" REL=previous>
- <LINK HREF="adminmanual.html#toc3" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-4.html">Next</A>
-<A HREF="adminmanual-2.html">Previous</A>
-<A HREF="adminmanual.html#toc3">Contents</A>
-<HR>
-<H2><A NAME="s3">3.</A> <A HREF="adminmanual.html#toc3">Mail</A></H2>
-
-<P>DXSpider deals seamlessly with standard AK1A type mail. It supports both
-personal and bulletin mail and the sysop has additional commands to ensure
-that mail gets to where it is meant. DXSpider will send mail almost
-immediately, assuming that the target is on line. However, only one
-mail message is dealt with at any one time. If a mail message is already
-being sent or recieved, then the new message will be queued until it has
-finished.</P>
-<P>The cluster mail is automatically deleted after 30 days unless the sysop
-sets the "keep" flag using the <EM>msg</EM> command.</P>
-
-<H2><A NAME="ss3.1">3.1</A> <A HREF="adminmanual.html#toc3.1">Personal mail</A>
-</H2>
-
-<P>Personal mail is sent using the <EM>sp</EM> command. This is actually the
-default method of sending mail and so a simple <EM>s</EM> for send will do.
-A full list of the send commands and options is in the <EM>command set</EM>
-section, so I will not duplicate them here.</P>
-
-<H2><A NAME="ss3.2">3.2</A> <A HREF="adminmanual.html#toc3.2">Bulletin mail</A>
-</H2>
-
-<P>Bulletin mail is sent by using the <EM>sb</EM> command. This is one of the
-most common mistakes users make when sending mail. They send a bulletin
-mail with <EM>s</EM> or <EM>sp</EM> instead of <EM>sb</EM> and of course
-the message never leaves the cluster. This can be rectified by the sysop
-by using the <EM>msg</EM> command.</P>
-
-<P>Bulletin addresses can be set using the Forward.pl file.</P>
-
-<H2><A NAME="ss3.3">3.3</A> <A HREF="adminmanual.html#toc3.3">Forward.pl</A>
-</H2>
-
-<P>DXSpider receives all and any mail sent to it without any alterations needed
-in files. Because personal and bulletin mail are treated differently, there
-is no need for a list of accepted bulletin addresses. It is necessary, however,
-to tell the program which links accept which bulletins. For example, it is
-pointless sending bulletins addresses to "UK" to any links other than UK
-ones. The file that does this is called forward.pl and lives in /spider/msg.
-At default, like other spider files it is named forward.pl.issue. Rename it
-to forward.pl and edit the file to match your requirements.
-The format is below ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# this is an example message forwarding file for the system
-#
-# The format of each line is as follows
-#
-# type to/from/at pattern action destinations
-# P/B/F T/F/A regex I/F [ call [, call ...] ]
-#
-# type: P - private, B - bulletin (msg), F - file (ak1a bull)
-# to/from/at: T - to field, F - from field, A - home bbs, O - origin
-# pattern: a perl regex on the field requested
-# action: I - ignore, F - forward
-# destinations: a reference to an array containing node callsigns
-#
-# if it is non-private and isn't in here then it won't get forwarded
-#
-# Currently only type B msgs are affected by this code.
-#
-# The list is read from the top down, the first pattern that matches
-# causes the action to be taken.
-#
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-#
-# If the BBS list is undef or 0 and the action is 'F' (and it matches the
-# pattern) then it will always be forwarded to every node that doesn't have
-# it (I strongly recommend you don't use this unless you REALLY mean it, if
-# you allow a new link with this on EVERY bull will be forwarded immediately
-# on first connection)
-#
-
-package DXMsg;
-
-@forward = (
-'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
-'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Simply insert a bulletin address and state in the brackets where you wish
-that mail to go. For example, you can see here that mail sent to "UK" will
-only be sent to the UK links and not to PA4AB-14.</P>
-
-<P>To force the cluster to reread the file use load/forward</P>
-
-<P>NB: If a user tries to send mail to a bulletin address that does not exist
-in this file, they will get an error.</P>
-
-<H2><A NAME="ss3.4">3.4</A> <A HREF="adminmanual.html#toc3.4">The msg command</A>
-</H2>
-
-<P>The <EM>msg</EM> command is a very powerful and flexible tool for the
-sysop. It allows the sysop to alter to and from fields and make other
-changes to manage the cluster mail.</P>
-<P>Here is a full list of the various options ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waiting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>These commands are simply typed from within the cluster as the sysop user.</P>
-
-<H2><A NAME="ss3.5">3.5</A> <A HREF="adminmanual.html#toc3.5">Message status</A>
-</H2>
-
-<P>You can check on a message from within the cluster by using the command
-<EM>stat/msg</EM>. This will give you additional information on the
-message number including which nodes have received it, which node it
-was received from and when etc. Here is an example of the output of
-the command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-G0VGS de GB7MBC 28-Jan-2001 1308Z >
-stat/msg 6869
- From: GB7DJK
- Msg Time: 26-Jan-2001 1302Z
- Msgno: 6869
- Origin: GB7DJK
- Size: 8012
- Subject: AMSAT 2line KEPS 01025.AMSAT
- To: UK
-Got it Nodes: GB7BAA, GB7ADX
- Private: 0
-Read Confirm: 0
- Times read: 0
-G0VGS de GB7MBC 28-Jan-2001 1308Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss3.6">3.6</A> <A HREF="adminmanual.html#toc3.6">Filtering mail</A>
-</H2>
-
-<P>This is described in the section on <EM>Other filters</EM> so I will not
-duplicate it here.</P>
-
-<H2><A NAME="ss3.7">3.7</A> <A HREF="adminmanual.html#toc3.7">Distribution lists</A>
-</H2>
-
-<P>Distribution lists are simply a list of users to send certain types of
-mail to. An example of this is mail you only wish to send to other
-sysops. In /spider/msg there is a directory called <EM>distro</EM>. You
-put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Any mail sent to "sysop" would only be sent to the callsigns in this list.</P>
-
-<H2><A NAME="ss3.8">3.8</A> <A HREF="adminmanual.html#toc3.8">BBS interface</A>
-</H2>
-
-<P>Spider provides a simple BBS interface. No input is required from the sysop
-of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
-any required mail to the cluster. No mail can flow from Spider to the BBS,
-the interface is one-way.</P>
-
-<P>Please be careful not to flood the cluster network with unnecessary mail.
-Make sure you only send mail to the clusters that want it by using the
-Forward.pl file very carefully.</P>
-
-<HR>
-<A HREF="adminmanual-4.html">Next</A>
-<A HREF="adminmanual-2.html">Previous</A>
-<A HREF="adminmanual.html#toc3">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Scripts</TITLE>
- <LINK HREF="adminmanual-5.html" REL=next>
- <LINK HREF="adminmanual-3.html" REL=previous>
- <LINK HREF="adminmanual.html#toc4" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-5.html">Next</A>
-<A HREF="adminmanual-3.html">Previous</A>
-<A HREF="adminmanual.html#toc4">Contents</A>
-<HR>
-<H2><A NAME="s4">4.</A> <A HREF="adminmanual.html#toc4">Scripts</A></H2>
-
-<P>From 1.48 onwards it will become increasingly possible to control DXSpider's
-operation with scripts of various kinds.</P>
-
-<P>The directory /spider/scripts is where it all happens and is used for several
-things. Firstly it contains a file called startup that can be used to call
-in any changes to the cluster from the default settings on startup. This
-script is executed immediately after all initialisation of the node is done
-but before any connections are possible. Examples of this include how many
-spots it is possible to get with the sh/dx command, whether you want
-registration/passwords to be permanently on etc. An example file is shown
-below and is included in the distribution as startup.issue.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# startup script example
-#
-# set maximum no of spots allowed to 100
-# set/var $Spot::maxspots = 100
-#
-# Set registration on
-# set/var $main::reqreg = 1
-#
-# Set passwords on
-# set/var $main::passwdreq = 1
-#
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>As usual, any text behind a # is treated as a comment and not read. To use
-this file, simply rename it from startup.issue to startup. In our example
-above there are three options. The first option is the amount of spots that
-a user can request with the <EM>sh/dx</EM> command. Normally the default is
-to give 10 spots unless the user specifies more. Without this line enabled,
-the maximum a user can request is 100 spots. Depending on your link quality
-you may wish to enable more or less by specifying the number.</P>
-
-<P>The other 2 options are dealt with more fully in the security section.</P>
-
-<P>Secondly, it is used to store the login scripts for users and nodes. Currently
-this can only be done by the sysop but it is envisaged that eventually users will
-be able to set their own. An example is included in the distibution but here is
-a further example.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# G0FYD
-#
-blank +
-sh/wwv 3
-blank +
-sh/dx
-blank +
-t g0jhc You abt?
-blank +
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The lines in between commands can simply insert a blank line or a character
-such as a + sign to make the output easier to read. Simply create this script
-with your favourite editor and save it with the callsign of the user as the
-filename. Filenames should always be in lower case.</P>
-
-<P>Commands can be inserted in the same way for nodes. A node may wish a series
-of commands to be issued on login, such as a merge command for example.</P>
-
-<P>Thirdly, there are 2 default scripts for users and nodes who do not have a
-specifically defined script. These are <EM>user_default</EM> and
-<EM>node_default</EM></P>
-
-<HR>
-<A HREF="adminmanual-5.html">Next</A>
-<A HREF="adminmanual-3.html">Previous</A>
-<A HREF="adminmanual.html#toc4">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Databases</TITLE>
- <LINK HREF="adminmanual-6.html" REL=next>
- <LINK HREF="adminmanual-4.html" REL=previous>
- <LINK HREF="adminmanual.html#toc5" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-6.html">Next</A>
-<A HREF="adminmanual-4.html">Previous</A>
-<A HREF="adminmanual.html#toc5">Contents</A>
-<HR>
-<H2><A NAME="s5">5.</A> <A HREF="adminmanual.html#toc5">Databases</A></H2>
-
-<P>Spider allows the creation of local or remote databases. It supports
-chained databases, allowing several different databases to be scanned
-with one simple command. Importing of databases is limited at present
-to the standard AK1A databases such as OBLAST and the DB0SDX QSL
-database but will expand with time.</P>
-
-<H2><A NAME="ss5.1">5.1</A> <A HREF="adminmanual.html#toc5.1">Creating databases</A>
-</H2>
-
-<P>Creating a database could not be more simple. All the commands are
-sent from the cluster prompt as the <EM>sysop</EM> user.</P>
-<P>To create a database you use the command <EM>dbcreate</EM>. It can
-be used in 3 different ways like so ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To simply create a database locally, you just tell the command the
-name of the database. This does not create the actual database, it
-simply defines it to say that it exists.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name> chain <name> [<name>...]
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This creates a chained database entry. The first database will be
-scanned, then the second, the third etc...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name> remote <name>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This creates a remote entry. the first name field is the database
-name at the remote node, then the remote switch, then the actual
-node_call of the remote node, for example...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate buckmaster remote gb7dxc
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Remote databases cannot be chained, however, the last database in a
-chain can be a remote database.</P>
-
-<H2><A NAME="ss5.2">5.2</A> <A HREF="adminmanual.html#toc5.2">Importing databases</A>
-</H2>
-
-<P>The only databases that Spider can currently import are the standard
-AK1A databases such as OBLAST or the DB0SDX qsl and address database.
-This will be added to with time.</P>
-<P>To import such a database, first put the file somewhere useful like /tmp
-and then issue the following command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbimport oblast /tmp/OBLAST.FUL
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This will update the existing local oblast database or create it if
-it does not exist.</P>
-
-<H2><A NAME="ss5.3">5.3</A> <A HREF="adminmanual.html#toc5.3">Checking available databases</A>
-</H2>
-
-<P>Once a database is created, you will want to check that it has been
-added. To do this use the <EM>dbavail</EM> command. This will
-output the available databases. For example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbavail
-DB Name Location Chain
-qsl Local
-buck GB7ADX
-hftest GB7DXM
-G0VGS de GB7MBC 3-Feb-2001 1925Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss5.4">5.4</A> <A HREF="adminmanual.html#toc5.4">Looking up databases</A>
-</H2>
-
-<P>To look for information in a defined database, simply use the <EM>dbshow</EM>
-command, for example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbshow buckmaster G0YLM
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will show the information for the callsign G0YLM from the buckmaster
-database if it exists. To make things more standard for the users
-you can add an entry in the Aliases file so that it looks like a standard
-<EM>show</EM> command like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Now you can simply use show/buckmaster or an abreviation.</P>
-
-<H2><A NAME="ss5.5">5.5</A> <A HREF="adminmanual.html#toc5.5">Removing databases</A>
-</H2>
-
-<P>To delete an existing database you use the <EM>dbremove</EM> command.
-For example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbremove oblast
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>would remove the oblast database and its associated datafile from the
-system. There are no warnings or recovery possible from this command.
-If you remove a database it ceases to exist and would have to be created
-from scratch if you still required it.</P>
-
-<HR>
-<A HREF="adminmanual-6.html">Next</A>
-<A HREF="adminmanual-4.html">Previous</A>
-<A HREF="adminmanual.html#toc5">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Information, files and useful programs</TITLE>
- <LINK HREF="adminmanual-7.html" REL=next>
- <LINK HREF="adminmanual-5.html" REL=previous>
- <LINK HREF="adminmanual.html#toc6" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-7.html">Next</A>
-<A HREF="adminmanual-5.html">Previous</A>
-<A HREF="adminmanual.html#toc6">Contents</A>
-<HR>
-<H2><A NAME="s6">6.</A> <A HREF="adminmanual.html#toc6">Information, files and useful programs</A></H2>
-
-<H2><A NAME="ss6.1">6.1</A> <A HREF="adminmanual.html#toc6.1">MOTD</A>
-</H2>
-
-<P>One of the more important things a cluster sysop needs to do is to get
-information to his users. The simplest way to do this is to have a banner
-that is sent to the user on login. This is know as a "message of the day"
-or "motd". To set this up, simply create a file in /spider/data called motd
-and edit it to say whatever you want. It is purely a text file and will be
-sent automatically to anyone logging in to the cluster.</P>
-
-<H2><A NAME="ss6.2">6.2</A> <A HREF="adminmanual.html#toc6.2">MOTD_NOR</A>
-</H2>
-
-<P>This message of the day file lives in the same directory as the standard
-motd file but is only sent to non-registered users. Once registered they
-will receive the same message as any other user.</P>
-
-<H2><A NAME="ss6.3">6.3</A> <A HREF="adminmanual.html#toc6.3">Downtime message</A>
-</H2>
-
-<P>If for any reason the cluster is down, maybe for upgrade or maintenance but
-the machine is still running, a message can be sent to the user advising them
-of the fact. This message lives in the /spider/data directory and is called
-"offline". Simply create the file and edit it to say whatever you wish.
-This file will be sent to a user attempting to log into the cluster when
-DXSpider is not actually running.</P>
-
-<H2><A NAME="ss6.4">6.4</A> <A HREF="adminmanual.html#toc6.4">Other text messages</A>
-</H2>
-
-<P>You can set other text messages to be read by the user if they input the file
-name. This could be for news items or maybe information for new users.
-To set this up, make a directory under /spider called <EM>packclus</EM>.
-Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
-for example. In fact you can create files with any names you like. These can
-be listed by the user with the command ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/files
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>They can be read by the user by typing the command ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-type news
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If the file they want to read is called <EM>news</EM>. You could also set
-an alias for this in the Alias file to allow them just to type <EM>news</EM></P>
-
-<P>You can also store other information in this directory, either directly or
-nested under directories. One use for this would be to store DX bulletins
-such as the OPDX bulletins. These can be listed and read by the user.
-To keep things tidy, make a directory under /spider/packclus called
-<EM>bulletin</EM>. Now copy any OPDX or similar bulletins into it. These
-can be listed by the user in the same way as above using the <EM>show/files</EM>
-command with an extension for the bulletin directory you have just created,
-like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/files bulletin
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>An example would look like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/files
-bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can see that in the files area (basically the packclus directory) there is a
-file called <EM>news</EM> and a directory called <EM>bulletin</EM>. You can
-also see that dates they were created. In the case of the file <EM>news</EM>,
-you can also see the time it was last modified, a good clue as to whether the
-file has been updated since you last read it. To read the file called
-<EM>news</EM> you would simply issue the command ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-type news
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To look what is in the bulletin directory you issue the command ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/files bulletin
-opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
-opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
-opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
-opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
-opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
-opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
-opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
-opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
-opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
-opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
-opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
-opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
-opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
-Press Enter to continue, A to abort (16 lines) >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can now read any file in this directory using the type command, like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-type bulletin/opdx391
-Ohio/Penn DX Bulletin No. 391
-The Ohio/Penn Dx PacketCluster
-DX Bulletin No. 391
-BID: $OPDX.391
-January 11, 1999
-Editor Tedd Mirgliotta, KB8NW
-Provided by BARF-80 BBS Cleveland, Ohio
-Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
-Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
-Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
-& The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
-Press Enter to continue, A to abort (508 lines) >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The page length will of course depend on what you have it set to!</P>
-
-<H2><A NAME="ss6.5">6.5</A> <A HREF="adminmanual.html#toc6.5">The Aliases file</A>
-</H2>
-
-<P>You will find a file in /spider/cmd/ called Aliases. This is the file that
-controls what a user gets when issuing a command. It is also possible to
-create your own aliases for databases and files you create locally.</P>
-
-<P>You should not alter the original file in /spider/cmd/ but create a new file
-with the same name in /spider/local_cmd. This means that any new Aliases files
-that is downloaded will not overwrite your self created Aliases and also that
-you do not override any new Aliases with your copy in /spider/local_cmd/. You
-must remember that any files you store in /spider/local/ or /spider/local_cmd
-override the originals if the same lines are used in both files.</P>
-
-<P>The best way of dealing with all this then is to only put your own locally
-created Aliases in the copy in /spider/local_cmd. The example below is
-currently in use at GB7MBC.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-#
-# Local Aliases File
-#
-
-package CmdAlias;
-
-%alias = (
- 'n' => [
- '^news$', 'type news', 'type',
- ],
- 's' => [
- '^sh\w*/buck$', 'show/qrz', 'show',
- '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
- '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
- '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
- '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
- ],
-)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Each alphabetical section should be preceded by the initial letter and the section
-should be wrapped in square brackets as you can see. The syntax is straightforward.
-The first section on each line is the new command that will be allowed once the
-alias is included. The second section is the command it is replacing and the last
-section is the actual command that is being used.</P>
-
-<P>The eagle-eyed amongst you will have noticed that in the first section, the new
-alias command has a '^' at the start and a '$' at the end. Basically these force
-a perfect match on the alias. The '^' says match the beginning exactly and the
-'$' says match the end exactly. This prevents unwanted and unintentional matches
-with similar commands.</P>
-
-<P>I have 3 different types of alias in this file. At the top is an alias for 'news'.
-This is a file I have created in the /spider/packclus/ directory where I can inform
-users of new developments or points of interest. In it's initial form a user would
-have to use the command <EM>type news</EM>. The alias allows them to simply type
-<EM>news</EM> to get the info. Second is an alias for the <EM>show/qrz</EM>
-command so that those users used to the original <EM>show/buck</EM> command in
-AK1A will not get an error, and the rest of the lines are for locally created
-databases so that a user can type <EM>show/hftest</EM> instead of having to use
-the command <EM>dbshow hftest</EM> which is not as intuitive.</P>
-
-<P>This file is just an example and you should edit it to your own requirements.
-Once created, simply issue the command <EM>load/alias</EM> at the cluster
-prompt as the sysop user and the aliases should be available.</P>
-
-
-<H2><A NAME="ss6.6">6.6</A> <A HREF="adminmanual.html#toc6.6">Console.pl</A>
-</H2>
-
-<P>In later versions of Spider a simple console program is provided for the sysop.
-This has a type ahead buffer with line editing facilities and colour for spots,
-announces etc. To use this program, simply use console.pl instead of client.</P>
-
-<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.</P>
-
-<H2><A NAME="ss6.7">6.7</A> <A HREF="adminmanual.html#toc6.7">Updating kepler data</A>
-</H2>
-
-<P>Spider has a powerful and flexible show/satellite command. In order for
-this to be accurate, the kepler data has to be updated regularly. In
-general, this data is available as an email or via cluster mail.
-Updating it is simple. First you need to export the mail message as a
-file. You do this with the <EM>export</EM> command from the cluster prompt
-as the sysop. For example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-export 5467 /spider/perl/keps.in
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>would export message number 5467 as a file called keps.in in the
-/spider/perl directory.</P>
-
-<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
-the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
-convert the file like so ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./convkeps.pl keps.in
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Now go back to the cluster and issue the command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-load/keps
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>That is it! the kepler data has been updated.</P>
-
-<H2><A NAME="ss6.8">6.8</A> <A HREF="adminmanual.html#toc6.8">The QRZ callbook</A>
-</H2>
-
-<P>The command <EM>sh/qrz</EM> will only work once you have followed a few
-simple steps. First you need to get a user ID and password from qrz.com.
-Simply go to the site and create one. Secondly you need to copy the file
-/spider/perl/Internet.pm to /spider/local and alter it to match your user
-ID and password. You also at this point need to set $allow=1 to complete
-the setup. Many thanks to Fred Lloyd, the proprieter of
-<A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.</P>
-
-<H2><A NAME="ss6.9">6.9</A> <A HREF="adminmanual.html#toc6.9">Connecting logging programs</A>
-</H2>
-
-<P>There appear to be very few logging programs out there that support telnet
-especially the popular ones like LogEQF, Turbolog etc. This can make it
-difficult to connect to your own cluster!
-The way to do it is to make the logging program think it has a TNC attached
-to a com port on the logging PC and 'push' a linux login out to it.
-This is achieved very simply by the use of <EM>agetty</EM>.</P>
-
-<P>All that is required is to add a line in /etc/inittab to have the client
-ready for a connection on the com port of your choice. Remember that in
-Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Add this after the standard runlevel lines in /etc/inittab. The above
-line works on ttyS1 (com2). Now as root, issue the command <EM>telinit q</EM>
-and it should be ready for connection. All that is required is a 3 wire
-serial lead (tx, rx and signal ground). Tell you logging program to use
-8n1 at 9600 baud and you should see a Linux login prompt. Login as normal
-and then telnet from there to the cluster.</P>
-
-<HR>
-<A HREF="adminmanual-7.html">Next</A>
-<A HREF="adminmanual-5.html">Previous</A>
-<A HREF="adminmanual.html#toc6">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Java Web applet</TITLE>
- <LINK HREF="adminmanual-8.html" REL=next>
- <LINK HREF="adminmanual-6.html" REL=previous>
- <LINK HREF="adminmanual.html#toc7" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-8.html">Next</A>
-<A HREF="adminmanual-6.html">Previous</A>
-<A HREF="adminmanual.html#toc7">Contents</A>
-<HR>
-<H2><A NAME="s7">7.</A> <A HREF="adminmanual.html#toc7">Java Web applet</A></H2>
-
-<P>In the spider tree will be a directory <EM>spider-web</EM>. This is a
-neat little java web applet that can be run from a website. The applet
-must run on the same machine as the cluster. The included README file is
-shown below.</P>
-
-<P>I should comment here that the applet is precompiled, that is, ready to go.
-It was compiled using JDK1.3.1. If your version is earlier than this then it
-may not work. Should that be the case you need to recompile or update your
-JDK. To recompile do the following ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd /spider/spider-web
-rm *.class
-/usr/bin/javac spiderclient.java
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>I have used /usr/bin/javac as an example, your path to javac may be different.</P>
-<P>
-<PRE>
-Spider-WEB v0.6b
-
-Completely based on a clx web client written in Java by dl6dbh
-(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
-
-The webserver has to run on the same machine as your DxSpider software!
-
-It is assumed that you have Java installed. You need JDK1.3.1 at least.
-
-Installation instructions (Performed as root):
-
-Put all the files in the spider-web directory into a newly created directory
-under the DocumentRoot of your websever for instance 'client'. In my case
-this is: /home/httpd/html/client/ although ymmv. For Suse the correct
-path should be /usr/local/httpd/htdocs/client/ for example.
-
-Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
-/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
-/usr/local/httpd/cgi-bin/ for example.
-
-Change the permissions of the files to ensure they are correct, obviously you
-will need to use the correct path the the files according to your system:
-
-chmod 755 /home/httpd/html/cgi-bin/spider.cgi
-chmod -R 755 /home/httpd/html/client/
-
-By default the spider.cgi script should pick up your hostname (As long as this
-is set correctly). If it does not or your hostname differs from the name that
-you attach to the public address that you are using, then edit spider.cgi :
-
-# Uncomment and set the hostname manually here if the above fails.
-# $HOSTNAME = "gb7mbc.spoo.org" ;
-$PORT = "8000" ;
-
-'HOSTNAME' is the hostname of your cluster.
-
-'PORT' is the portnumber that you use to connect to your DxSpider via
-telnet (see Listeners.pm)
-
-NOTE: If you can start the console but cannot connect to the cluster from it,
-then it is possible that the machine you are on cannot resolve the hostname of
-your cluster machine. If this is the case, you need to set your hostname
-manually as above.
-
-You also need to set the $NODECALL variable. This prints the name of your
-choosing (probably your cluster callsign) on the html page.
-
-You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
-</PRE>
-</P>
-
-<HR>
-<A HREF="adminmanual-8.html">Next</A>
-<A HREF="adminmanual-6.html">Previous</A>
-<A HREF="adminmanual.html#toc7">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Web based statistics</TITLE>
- <LINK HREF="adminmanual-9.html" REL=next>
- <LINK HREF="adminmanual-7.html" REL=previous>
- <LINK HREF="adminmanual.html#toc8" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-9.html">Next</A>
-<A HREF="adminmanual-7.html">Previous</A>
-<A HREF="adminmanual.html#toc8">Contents</A>
-<HR>
-<H2><A NAME="s8">8.</A> <A HREF="adminmanual.html#toc8">Web based statistics</A></H2>
-
-<P>From version 1.50, you can use the freeware software MRTG to produce
-really nice graphical statistics on your web site. For an example
-try
-<A HREF="http://www.gb7mbc.net/mrtg/stats.html">http://www.gb7mbc.net/mrtg/stats.html</A>.</P>
-
-<P>The following should help you get it all working.</P>
-
-<P>First you need to download the latest version of MRTG from
-<A HREF="http://people.ee.ethz.ch/~oetiker/webtools/mrtg/">http://people.ee.ethz.ch/~oetiker/webtools/mrtg/</A>.
-You will also need the following files..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-libpng-1.0.14.tar.gz
-zlib-1.1.4.tar.gz
-gd-1.8.3.tar.gz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Login to your machine as the root user, put all the downloaded files
-in /usr/local/src/ (or wherever you prefer) and untar and compile them.
-All the information to compile and install these sources come with them.
-After compilation and installation, you will find MRTG in /usr/local/mrtg-2.</P>
-
-<P>Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
-/spider/html/mrtg/</P>
-
-<P>You now need to make 2 symbolic links like below...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
-ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Now login to the cluster with your sysop callsign and run the command
-"mrtg all".</P>
-
-<P>Now you are nearly there! Login as the sysop user and change to the
-/spider/html/mrtg/ directory. Now run the command <EM>indexmaker</EM> as
-shown below...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Changing the callsign for your own cluster callsign of course!</P>
-
-<P>And finally you need to login as the root user and create one last
-symbolic link. Where this points will depend on where your html
-documents are kept. For RedHat systems you use...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and for SuSE systems...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you now point your browser to your website as below it should all
-be happening!</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-http://www.xxx.xxx/mrtg/stats.html
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Of course, to get the stats to update, you need to add some information
-in the spider crontab file as below...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# Update stats for mrtg on website
-00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This will update the site every 5 minutes.</P>
-
-<HR>
-<A HREF="adminmanual-9.html">Next</A>
-<A HREF="adminmanual-7.html">Previous</A>
-<A HREF="adminmanual.html#toc8">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50: Security</TITLE>
- <LINK HREF="adminmanual-10.html" REL=next>
- <LINK HREF="adminmanual-8.html" REL=previous>
- <LINK HREF="adminmanual.html#toc9" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-10.html">Next</A>
-<A HREF="adminmanual-8.html">Previous</A>
-<A HREF="adminmanual.html#toc9">Contents</A>
-<HR>
-<H2><A NAME="s9">9.</A> <A HREF="adminmanual.html#toc9">Security</A></H2>
-
-<P>From version 1.49 DXSpider has some additional security features. These
-are not by any means meant to be exhaustive, however they do afford some
-security against piracy. These two new features can be used independently
-of each other or in concert to tighten the security.</P>
-
-<H2><A NAME="ss9.1">9.1</A> <A HREF="adminmanual.html#toc9.1">Registration</A>
-</H2>
-
-<P>The basic principle of registration is simple. If a user is not registered
-by the sysop, then they have read-only access to the cluster. The only
-thing they can actually send is a talk or a message to the sysop. In
-order for them to be able to spot, send announces or talks etc the sysop
-must register them with the <EM>set/register</EM> command, like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/register g0vgs
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The user g0vgs can now fully use the cluster. In order to enable
-registration, you can issue the command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/var $main::reqreg = 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Any users that are not registered will now see the motd_nor file rather
-than the motd file as discussed in the Information, files and useful
-programs section.</P>
-
-<P>Entering this line at the prompt will only last for the time the cluster
-is running of course and would not be present on a restart. To make the
-change permanent, add the above line to /spider/scripts/startup. To
-read more on the startup file, see the section on Information, files
-and useful programs.</P>
-
-<P>To unregister a user use <EM>unset/register</EM> and to show the list
-of registered users, use the command <EM>show/register</EM>.</P>
-
-<H2><A NAME="ss9.2">9.2</A> <A HREF="adminmanual.html#toc9.2">Passwords</A>
-</H2>
-
-<P>At the moment, passwords only affect users who login to a DXSpider
-cluster node via telnet. If a user requires a password, they can
-either set it themselves or have the sysop enter it for them by using
-the <EM>set/password</EM> command. Any users who already have passwords,
-such as remote sysops, will be asked for their passwords automatically
-by the cluster. Using passwords in this way means that the user has a
-choice on whether to have a password or not. To force the use of
-passwords at login, issue the command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/var $main::passwdreq = 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>at the cluster prompt. This can also be added to the /spider/scripts/startup
-file as above to make the change permanent.</P>
-
-<P>Of course, if you do this you will have to assign a password for each of
-your users. If you were asking them to register, it is anticipated that
-you would ask them to send you a message both to ask to be registered and
-to give you the password they wish to use.</P>
-
-<P>Should a user forget their password, it can be reset by the sysop by
-first removing the existing password and then setting a new one like so ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-unset/password g0vgs
-set/password g0vgs new_password
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<HR>
-<A HREF="adminmanual-10.html">Next</A>
-<A HREF="adminmanual-8.html">Previous</A>
-<A HREF="adminmanual.html#toc9">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Administration Manual v1.50</TITLE>
- <LINK HREF="adminmanual-1.html" REL=next>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>The DXSpider Administration Manual v1.50</H1>
-
-<H2>Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and
-Charlie Carroll, K1XX, (k1xx@ptcnh.net)</H2>February 2003 revision 0.3
-<HR>
-<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
-<HR>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="adminmanual-1.html">Routing and Filtering</A></H2>
-
-<UL>
-<LI><A NAME="toc1.1">1.1</A> <A HREF="adminmanual-1.html#ss1.1">Introduction</A>
-<LI><A NAME="toc1.2">1.2</A> <A HREF="adminmanual-1.html#ss1.2">Route Filters</A>
-<LI><A NAME="toc1.3">1.3</A> <A HREF="adminmanual-1.html#ss1.3">The node_default filter</A>
-<LI><A NAME="toc1.4">1.4</A> <A HREF="adminmanual-1.html#ss1.4">General route filtering</A>
-<LI><A NAME="toc1.5">1.5</A> <A HREF="adminmanual-1.html#ss1.5">General filter rules</A>
-<LI><A NAME="toc1.6">1.6</A> <A HREF="adminmanual-1.html#ss1.6">Types of filter</A>
-<LI><A NAME="toc1.7">1.7</A> <A HREF="adminmanual-1.html#ss1.7">Filter options</A>
-<LI><A NAME="toc1.8">1.8</A> <A HREF="adminmanual-1.html#ss1.8">Default filters</A>
-<LI><A NAME="toc1.9">1.9</A> <A HREF="adminmanual-1.html#ss1.9">Advanced filtering</A>
-<LI><A NAME="toc1.10">1.10</A> <A HREF="adminmanual-1.html#ss1.10">Basic hop control</A>
-<LI><A NAME="toc1.11">1.11</A> <A HREF="adminmanual-1.html#ss1.11">Hop Control on Specific Nodes</A>
-<LI><A NAME="toc1.12">1.12</A> <A HREF="adminmanual-1.html#ss1.12">Isolating networks</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">Other filters</A></H2>
-
-<UL>
-<LI><A NAME="toc2.1">2.1</A> <A HREF="adminmanual-2.html#ss2.1">Filtering Mail</A>
-<LI><A NAME="toc2.2">2.2</A> <A HREF="adminmanual-2.html#ss2.2">Filtering words from text fields in Announce, Talk and DX spots</A>
-<LI><A NAME="toc2.3">2.3</A> <A HREF="adminmanual-2.html#ss2.3">Stopping (possibly bad) DX Spots from Nodes or Spotters</A>
-</UL>
-<P>
-<H2><A NAME="toc3">3.</A> <A HREF="adminmanual-3.html">Mail</A></H2>
-
-<UL>
-<LI><A NAME="toc3.1">3.1</A> <A HREF="adminmanual-3.html#ss3.1">Personal mail</A>
-<LI><A NAME="toc3.2">3.2</A> <A HREF="adminmanual-3.html#ss3.2">Bulletin mail</A>
-<LI><A NAME="toc3.3">3.3</A> <A HREF="adminmanual-3.html#ss3.3">Forward.pl</A>
-<LI><A NAME="toc3.4">3.4</A> <A HREF="adminmanual-3.html#ss3.4">The msg command</A>
-<LI><A NAME="toc3.5">3.5</A> <A HREF="adminmanual-3.html#ss3.5">Message status</A>
-<LI><A NAME="toc3.6">3.6</A> <A HREF="adminmanual-3.html#ss3.6">Filtering mail</A>
-<LI><A NAME="toc3.7">3.7</A> <A HREF="adminmanual-3.html#ss3.7">Distribution lists</A>
-<LI><A NAME="toc3.8">3.8</A> <A HREF="adminmanual-3.html#ss3.8">BBS interface</A>
-</UL>
-<P>
-<H2><A NAME="toc4">4.</A> <A HREF="adminmanual-4.html">Scripts</A></H2>
-
-<P>
-<H2><A NAME="toc5">5.</A> <A HREF="adminmanual-5.html">Databases</A></H2>
-
-<UL>
-<LI><A NAME="toc5.1">5.1</A> <A HREF="adminmanual-5.html#ss5.1">Creating databases</A>
-<LI><A NAME="toc5.2">5.2</A> <A HREF="adminmanual-5.html#ss5.2">Importing databases</A>
-<LI><A NAME="toc5.3">5.3</A> <A HREF="adminmanual-5.html#ss5.3">Checking available databases</A>
-<LI><A NAME="toc5.4">5.4</A> <A HREF="adminmanual-5.html#ss5.4">Looking up databases</A>
-<LI><A NAME="toc5.5">5.5</A> <A HREF="adminmanual-5.html#ss5.5">Removing databases</A>
-</UL>
-<P>
-<H2><A NAME="toc6">6.</A> <A HREF="adminmanual-6.html">Information, files and useful programs</A></H2>
-
-<UL>
-<LI><A NAME="toc6.1">6.1</A> <A HREF="adminmanual-6.html#ss6.1">MOTD</A>
-<LI><A NAME="toc6.2">6.2</A> <A HREF="adminmanual-6.html#ss6.2">MOTD_NOR</A>
-<LI><A NAME="toc6.3">6.3</A> <A HREF="adminmanual-6.html#ss6.3">Downtime message</A>
-<LI><A NAME="toc6.4">6.4</A> <A HREF="adminmanual-6.html#ss6.4">Other text messages</A>
-<LI><A NAME="toc6.5">6.5</A> <A HREF="adminmanual-6.html#ss6.5">The Aliases file</A>
-<LI><A NAME="toc6.6">6.6</A> <A HREF="adminmanual-6.html#ss6.6">Console.pl</A>
-<LI><A NAME="toc6.7">6.7</A> <A HREF="adminmanual-6.html#ss6.7">Updating kepler data</A>
-<LI><A NAME="toc6.8">6.8</A> <A HREF="adminmanual-6.html#ss6.8">The QRZ callbook</A>
-<LI><A NAME="toc6.9">6.9</A> <A HREF="adminmanual-6.html#ss6.9">Connecting logging programs</A>
-</UL>
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">Java Web applet</A></H2>
-
-<P>
-<H2><A NAME="toc8">8.</A> <A HREF="adminmanual-8.html">Web based statistics</A></H2>
-
-<P>
-<H2><A NAME="toc9">9.</A> <A HREF="adminmanual-9.html">Security</A></H2>
-
-<UL>
-<LI><A NAME="toc9.1">9.1</A> <A HREF="adminmanual-9.html#ss9.1">Registration</A>
-<LI><A NAME="toc9.2">9.2</A> <A HREF="adminmanual-9.html#ss9.2">Passwords</A>
-</UL>
-<P>
-<H2><A NAME="toc10">10.</A> <A HREF="adminmanual-10.html">CVS</A></H2>
-
-<UL>
-<LI><A NAME="toc10.1">10.1</A> <A HREF="adminmanual-10.html#ss10.1">CVS from a Linux platform</A>
-<LI><A NAME="toc10.2">10.2</A> <A HREF="adminmanual-10.html#ss10.2">CVS from a Windows platform</A>
-</UL>
-<P>
-<H2><A NAME="toc11">11.</A> <A HREF="adminmanual-11.html">The DXSpider command set</A></H2>
-
-<UL>
-<LI><A NAME="toc11.1">11.1</A> <A HREF="adminmanual-11.html#ss11.1">accept/announce (0)</A>
-<LI><A NAME="toc11.2">11.2</A> <A HREF="adminmanual-11.html#ss11.2">accept/announce (extended for sysops) (8)</A>
-<LI><A NAME="toc11.3">11.3</A> <A HREF="adminmanual-11.html#ss11.3">accept/route (8)</A>
-<LI><A NAME="toc11.4">11.4</A> <A HREF="adminmanual-11.html#ss11.4">accept/spots (0)</A>
-<LI><A NAME="toc11.5">11.5</A> <A HREF="adminmanual-11.html#ss11.5">accept/spots (extended for sysops) (8)</A>
-<LI><A NAME="toc11.6">11.6</A> <A HREF="adminmanual-11.html#ss11.6">accept/wcy (0)</A>
-<LI><A NAME="toc11.7">11.7</A> <A HREF="adminmanual-11.html#ss11.7">accept/wcy (extended for sysops) (8)</A>
-<LI><A NAME="toc11.8">11.8</A> <A HREF="adminmanual-11.html#ss11.8">accept/wwv (0)</A>
-<LI><A NAME="toc11.9">11.9</A> <A HREF="adminmanual-11.html#ss11.9">accept/wwv (extended for sysops) (8)</A>
-<LI><A NAME="toc11.10">11.10</A> <A HREF="adminmanual-11.html#ss11.10">announce (0)</A>
-<LI><A NAME="toc11.11">11.11</A> <A HREF="adminmanual-11.html#ss11.11">announce full (0)</A>
-<LI><A NAME="toc11.12">11.12</A> <A HREF="adminmanual-11.html#ss11.12">announce sysop (5)</A>
-<LI><A NAME="toc11.13">11.13</A> <A HREF="adminmanual-11.html#ss11.13">apropos (0)</A>
-<LI><A NAME="toc11.14">11.14</A> <A HREF="adminmanual-11.html#ss11.14">bye (0)</A>
-<LI><A NAME="toc11.15">11.15</A> <A HREF="adminmanual-11.html#ss11.15">catchup (5)</A>
-<LI><A NAME="toc11.16">11.16</A> <A HREF="adminmanual-11.html#ss11.16">clear/announce (8)</A>
-<LI><A NAME="toc11.17">11.17</A> <A HREF="adminmanual-11.html#ss11.17">clear/route (8)</A>
-<LI><A NAME="toc11.18">11.18</A> <A HREF="adminmanual-11.html#ss11.18">clear/spots (0)</A>
-<LI><A NAME="toc11.19">11.19</A> <A HREF="adminmanual-11.html#ss11.19">clear/spots (extended for sysops) (8)</A>
-<LI><A NAME="toc11.20">11.20</A> <A HREF="adminmanual-11.html#ss11.20">clear/wcy (0)</A>
-<LI><A NAME="toc11.21">11.21</A> <A HREF="adminmanual-11.html#ss11.21">clear/wcy (extended for sysops) (8)</A>
-<LI><A NAME="toc11.22">11.22</A> <A HREF="adminmanual-11.html#ss11.22">clear/wwv (0)</A>
-<LI><A NAME="toc11.23">11.23</A> <A HREF="adminmanual-11.html#ss11.23">clear/wwv (extended for sysops) (8)</A>
-<LI><A NAME="toc11.24">11.24</A> <A HREF="adminmanual-11.html#ss11.24">connect (5) </A>
-<LI><A NAME="toc11.25">11.25</A> <A HREF="adminmanual-11.html#ss11.25">dbavail (0)</A>
-<LI><A NAME="toc11.26">11.26</A> <A HREF="adminmanual-11.html#ss11.26">dbcreate (9)</A>
-<LI><A NAME="toc11.27">11.27</A> <A HREF="adminmanual-11.html#ss11.27">dbimport (9)</A>
-<LI><A NAME="toc11.28">11.28</A> <A HREF="adminmanual-11.html#ss11.28">dbremove (9)</A>
-<LI><A NAME="toc11.29">11.29</A> <A HREF="adminmanual-11.html#ss11.29">dbshow (0)</A>
-<LI><A NAME="toc11.30">11.30</A> <A HREF="adminmanual-11.html#ss11.30">debug (9)</A>
-<LI><A NAME="toc11.31">11.31</A> <A HREF="adminmanual-11.html#ss11.31">delete/user (9)</A>
-<LI><A NAME="toc11.32">11.32</A> <A HREF="adminmanual-11.html#ss11.32">demonstrate (9)</A>
-<LI><A NAME="toc11.33">11.33</A> <A HREF="adminmanual-11.html#ss11.33">directory (0)</A>
-<LI><A NAME="toc11.34">11.34</A> <A HREF="adminmanual-11.html#ss11.34">directory (extended for sysops) (5)</A>
-<LI><A NAME="toc11.35">11.35</A> <A HREF="adminmanual-11.html#ss11.35">disconnect (8)</A>
-<LI><A NAME="toc11.36">11.36</A> <A HREF="adminmanual-11.html#ss11.36">dx (0)</A>
-<LI><A NAME="toc11.37">11.37</A> <A HREF="adminmanual-11.html#ss11.37">export (9)</A>
-<LI><A NAME="toc11.38">11.38</A> <A HREF="adminmanual-11.html#ss11.38">export_users (9)</A>
-<LI><A NAME="toc11.39">11.39</A> <A HREF="adminmanual-11.html#ss11.39">filtering (0)</A>
-<LI><A NAME="toc11.40">11.40</A> <A HREF="adminmanual-11.html#ss11.40">forward/latlong (8)</A>
-<LI><A NAME="toc11.41">11.41</A> <A HREF="adminmanual-11.html#ss11.41">forward/opername (1)</A>
-<LI><A NAME="toc11.42">11.42</A> <A HREF="adminmanual-11.html#ss11.42">help (0)</A>
-<LI><A NAME="toc11.43">11.43</A> <A HREF="adminmanual-11.html#ss11.43">init (5)</A>
-<LI><A NAME="toc11.44">11.44</A> <A HREF="adminmanual-11.html#ss11.44">kill (0)</A>
-<LI><A NAME="toc11.45">11.45</A> <A HREF="adminmanual-11.html#ss11.45">kill (5)</A>
-<LI><A NAME="toc11.46">11.46</A> <A HREF="adminmanual-11.html#ss11.46">kill full (5)</A>
-<LI><A NAME="toc11.47">11.47</A> <A HREF="adminmanual-11.html#ss11.47">kill/expunge (6)</A>
-<LI><A NAME="toc11.48">11.48</A> <A HREF="adminmanual-11.html#ss11.48">links (0)</A>
-<LI><A NAME="toc11.49">11.49</A> <A HREF="adminmanual-11.html#ss11.49">load/aliases (9)</A>
-<LI><A NAME="toc11.50">11.50</A> <A HREF="adminmanual-11.html#ss11.50">load/badmsg (9)</A>
-<LI><A NAME="toc11.51">11.51</A> <A HREF="adminmanual-11.html#ss11.51">load/badwords (9)</A>
-<LI><A NAME="toc11.52">11.52</A> <A HREF="adminmanual-11.html#ss11.52">load/bands (9)</A>
-<LI><A NAME="toc11.53">11.53</A> <A HREF="adminmanual-11.html#ss11.53">load/cmd_cache (9)</A>
-<LI><A NAME="toc11.54">11.54</A> <A HREF="adminmanual-11.html#ss11.54">load/forward (9)</A>
-<LI><A NAME="toc11.55">11.55</A> <A HREF="adminmanual-11.html#ss11.55">load/messages (9)</A>
-<LI><A NAME="toc11.56">11.56</A> <A HREF="adminmanual-11.html#ss11.56">load/prefixes (9)</A>
-<LI><A NAME="toc11.57">11.57</A> <A HREF="adminmanual-11.html#ss11.57">merge (5)</A>
-<LI><A NAME="toc11.58">11.58</A> <A HREF="adminmanual-11.html#ss11.58">msg (9)</A>
-<LI><A NAME="toc11.59">11.59</A> <A HREF="adminmanual-11.html#ss11.59">pc (8)</A>
-<LI><A NAME="toc11.60">11.60</A> <A HREF="adminmanual-11.html#ss11.60">ping (1)</A>
-<LI><A NAME="toc11.61">11.61</A> <A HREF="adminmanual-11.html#ss11.61">rcmd (1)</A>
-<LI><A NAME="toc11.62">11.62</A> <A HREF="adminmanual-11.html#ss11.62">read (0)</A>
-<LI><A NAME="toc11.63">11.63</A> <A HREF="adminmanual-11.html#ss11.63">read (extended for sysops) (5) </A>
-<LI><A NAME="toc11.64">11.64</A> <A HREF="adminmanual-11.html#ss11.64">reject/announce</A>
-<LI><A NAME="toc11.65">11.65</A> <A HREF="adminmanual-11.html#ss11.65">reject/announce (extended for sysops) (8)</A>
-<LI><A NAME="toc11.66">11.66</A> <A HREF="adminmanual-11.html#ss11.66">reject/route (8)</A>
-<LI><A NAME="toc11.67">11.67</A> <A HREF="adminmanual-11.html#ss11.67">reject/spots (0)</A>
-<LI><A NAME="toc11.68">11.68</A> <A HREF="adminmanual-11.html#ss11.68">reject/spots (extended for sysops) (8)</A>
-<LI><A NAME="toc11.69">11.69</A> <A HREF="adminmanual-11.html#ss11.69">reject/wcy (0)</A>
-<LI><A NAME="toc11.70">11.70</A> <A HREF="adminmanual-11.html#ss11.70">reject/wcy (extended for sysops) (8)</A>
-<LI><A NAME="toc11.71">11.71</A> <A HREF="adminmanual-11.html#ss11.71">reject/wwv (0)</A>
-<LI><A NAME="toc11.72">11.72</A> <A HREF="adminmanual-11.html#ss11.72">reject/wwv (extended for sysops) (8)</A>
-<LI><A NAME="toc11.73">11.73</A> <A HREF="adminmanual-11.html#ss11.73">reply (0)</A>
-<LI><A NAME="toc11.74">11.74</A> <A HREF="adminmanual-11.html#ss11.74">send (0)</A>
-<LI><A NAME="toc11.75">11.75</A> <A HREF="adminmanual-11.html#ss11.75">set/address (0)</A>
-<LI><A NAME="toc11.76">11.76</A> <A HREF="adminmanual-11.html#ss11.76">set/announce (0)</A>
-<LI><A NAME="toc11.77">11.77</A> <A HREF="adminmanual-11.html#ss11.77">set/arcluster (5)</A>
-<LI><A NAME="toc11.78">11.78</A> <A HREF="adminmanual-11.html#ss11.78">set/baddx (8)</A>
-<LI><A NAME="toc11.79">11.79</A> <A HREF="adminmanual-11.html#ss11.79">set/badnode (6)</A>
-<LI><A NAME="toc11.80">11.80</A> <A HREF="adminmanual-11.html#ss11.80">set/badspotter (8)</A>
-<LI><A NAME="toc11.81">11.81</A> <A HREF="adminmanual-11.html#ss11.81">set/badword (8)</A>
-<LI><A NAME="toc11.82">11.82</A> <A HREF="adminmanual-11.html#ss11.82">set/beep (0)</A>
-<LI><A NAME="toc11.83">11.83</A> <A HREF="adminmanual-11.html#ss11.83">set/bbs (5)</A>
-<LI><A NAME="toc11.84">11.84</A> <A HREF="adminmanual-11.html#ss11.84">set/clx (5)</A>
-<LI><A NAME="toc11.85">11.85</A> <A HREF="adminmanual-11.html#ss11.85">set/debug (9)</A>
-<LI><A NAME="toc11.86">11.86</A> <A HREF="adminmanual-11.html#ss11.86">set/dx (0)</A>
-<LI><A NAME="toc11.87">11.87</A> <A HREF="adminmanual-11.html#ss11.87">set/dxgrid (0)</A>
-<LI><A NAME="toc11.88">11.88</A> <A HREF="adminmanual-11.html#ss11.88">set/dxnet (5)</A>
-<LI><A NAME="toc11.89">11.89</A> <A HREF="adminmanual-11.html#ss11.89">set/echo (0)</A>
-<LI><A NAME="toc11.90">11.90</A> <A HREF="adminmanual-11.html#ss11.90">set/email (0)</A>
-<LI><A NAME="toc11.91">11.91</A> <A HREF="adminmanual-11.html#ss11.91">set/here (0)</A>
-<LI><A NAME="toc11.92">11.92</A> <A HREF="adminmanual-11.html#ss11.92">set/homenode (0)</A>
-<LI><A NAME="toc11.93">11.93</A> <A HREF="adminmanual-11.html#ss11.93">set/hops (8)</A>
-<LI><A NAME="toc11.94">11.94</A> <A HREF="adminmanual-11.html#ss11.94">set/isolate (9)</A>
-<LI><A NAME="toc11.95">11.95</A> <A HREF="adminmanual-11.html#ss11.95">set/language (0)</A>
-<LI><A NAME="toc11.96">11.96</A> <A HREF="adminmanual-11.html#ss11.96">set/location (0)</A>
-<LI><A NAME="toc11.97">11.97</A> <A HREF="adminmanual-11.html#ss11.97">set/sys_location (9)</A>
-<LI><A NAME="toc11.98">11.98</A> <A HREF="adminmanual-11.html#ss11.98">set/logininfo (0)</A>
-<LI><A NAME="toc11.99">11.99</A> <A HREF="adminmanual-11.html#ss11.99">set/lockout (9)</A>
-<LI><A NAME="toc11.100">11.100</A> <A HREF="adminmanual-11.html#ss11.100">set/name (0)</A>
-<LI><A NAME="toc11.101">11.101</A> <A HREF="adminmanual-11.html#ss11.101">set/node (9)</A>
-<LI><A NAME="toc11.102">11.102</A> <A HREF="adminmanual-11.html#ss11.102">set/obscount (9)</A>
-<LI><A NAME="toc11.103">11.103</A> <A HREF="adminmanual-11.html#ss11.103">set/page (0)</A>
-<LI><A NAME="toc11.104">11.104</A> <A HREF="adminmanual-11.html#ss11.104">set/password (0)</A>
-<LI><A NAME="toc11.105">11.105</A> <A HREF="adminmanual-11.html#ss11.105">set/password (9)</A>
-<LI><A NAME="toc11.106">11.106</A> <A HREF="adminmanual-11.html#ss11.106">set/pinginterval (9)</A>
-<LI><A NAME="toc11.107">11.107</A> <A HREF="adminmanual-11.html#ss11.107">set/privilege (9)</A>
-<LI><A NAME="toc11.108">11.108</A> <A HREF="adminmanual-11.html#ss11.108">set/spider (5)</A>
-<LI><A NAME="toc11.109">11.109</A> <A HREF="adminmanual-11.html#ss11.109">set/sys_qra (9)</A>
-<LI><A NAME="toc11.110">11.110</A> <A HREF="adminmanual-11.html#ss11.110">set/qra (0)</A>
-<LI><A NAME="toc11.111">11.111</A> <A HREF="adminmanual-11.html#ss11.111">set/qth (0)</A>
-<LI><A NAME="toc11.112">11.112</A> <A HREF="adminmanual-11.html#ss11.112">set/register (9)</A>
-<LI><A NAME="toc11.113">11.113</A> <A HREF="adminmanual-11.html#ss11.113">set/talk (0)</A>
-<LI><A NAME="toc11.114">11.114</A> <A HREF="adminmanual-11.html#ss11.114">set/wcy (0)</A>
-<LI><A NAME="toc11.115">11.115</A> <A HREF="adminmanual-11.html#ss11.115">set/wwv (0)</A>
-<LI><A NAME="toc11.116">11.116</A> <A HREF="adminmanual-11.html#ss11.116">set/wx (0)</A>
-<LI><A NAME="toc11.117">11.117</A> <A HREF="adminmanual-11.html#ss11.117">show/baddx (1)</A>
-<LI><A NAME="toc11.118">11.118</A> <A HREF="adminmanual-11.html#ss11.118">show/badnode (6)</A>
-<LI><A NAME="toc11.119">11.119</A> <A HREF="adminmanual-11.html#ss11.119">show/badspotter (1)</A>
-<LI><A NAME="toc11.120">11.120</A> <A HREF="adminmanual-11.html#ss11.120">show/badword (1)</A>
-<LI><A NAME="toc11.121">11.121</A> <A HREF="adminmanual-11.html#ss11.121">show/configuration (0)</A>
-<LI><A NAME="toc11.122">11.122</A> <A HREF="adminmanual-11.html#ss11.122">show/configuration/node (0)</A>
-<LI><A NAME="toc11.123">11.123</A> <A HREF="adminmanual-11.html#ss11.123">show/connect (1)</A>
-<LI><A NAME="toc11.124">11.124</A> <A HREF="adminmanual-11.html#ss11.124">show/date (0)</A>
-<LI><A NAME="toc11.125">11.125</A> <A HREF="adminmanual-11.html#ss11.125">show/debug (9)</A>
-<LI><A NAME="toc11.126">11.126</A> <A HREF="adminmanual-11.html#ss11.126">show/dx (0)</A>
-<LI><A NAME="toc11.127">11.127</A> <A HREF="adminmanual-11.html#ss11.127">show/dxcc (0)</A>
-<LI><A NAME="toc11.128">11.128</A> <A HREF="adminmanual-11.html#ss11.128">sh/dxstats (0)</A>
-<LI><A NAME="toc11.129">11.129</A> <A HREF="adminmanual-11.html#ss11.129">show/files (0)</A>
-<LI><A NAME="toc11.130">11.130</A> <A HREF="adminmanual-11.html#ss11.130">show/filter (0)</A>
-<LI><A NAME="toc11.131">11.131</A> <A HREF="adminmanual-11.html#ss11.131">show/filter (extended for sysops) (5)</A>
-<LI><A NAME="toc11.132">11.132</A> <A HREF="adminmanual-11.html#ss11.132">show/hfstats (0)</A>
-<LI><A NAME="toc11.133">11.133</A> <A HREF="adminmanual-11.html#ss11.133">show/hftable (0)</A>
-<LI><A NAME="toc11.134">11.134</A> <A HREF="adminmanual-11.html#ss11.134">show/hops (8)</A>
-<LI><A NAME="toc11.135">11.135</A> <A HREF="adminmanual-11.html#ss11.135">show/isolate (1)</A>
-<LI><A NAME="toc11.136">11.136</A> <A HREF="adminmanual-11.html#ss11.136">show/lockout (9)</A>
-<LI><A NAME="toc11.137">11.137</A> <A HREF="adminmanual-11.html#ss11.137">show/log (8)</A>
-<LI><A NAME="toc11.138">11.138</A> <A HREF="adminmanual-11.html#ss11.138">show/moon (0)</A>
-<LI><A NAME="toc11.139">11.139</A> <A HREF="adminmanual-11.html#ss11.139">show/muf (0)</A>
-<LI><A NAME="toc11.140">11.140</A> <A HREF="adminmanual-11.html#ss11.140">show/newconfiguration (0)</A>
-<LI><A NAME="toc11.141">11.141</A> <A HREF="adminmanual-11.html#ss11.141">show/newconfiguration/node (0)</A>
-<LI><A NAME="toc11.142">11.142</A> <A HREF="adminmanual-11.html#ss11.142">show/node (1)</A>
-<LI><A NAME="toc11.143">11.143</A> <A HREF="adminmanual-11.html#ss11.143">show/prefix (0)</A>
-<LI><A NAME="toc11.144">11.144</A> <A HREF="adminmanual-11.html#ss11.144">show/program (5)</A>
-<LI><A NAME="toc11.145">11.145</A> <A HREF="adminmanual-11.html#ss11.145">show/qra (0)</A>
-<LI><A NAME="toc11.146">11.146</A> <A HREF="adminmanual-11.html#ss11.146">show/qrz (0)</A>
-<LI><A NAME="toc11.147">11.147</A> <A HREF="adminmanual-11.html#ss11.147">show/registered (9)</A>
-<LI><A NAME="toc11.148">11.148</A> <A HREF="adminmanual-11.html#ss11.148">show/route (0)</A>
-<LI><A NAME="toc11.149">11.149</A> <A HREF="adminmanual-11.html#ss11.149">show/satellite (0)</A>
-<LI><A NAME="toc11.150">11.150</A> <A HREF="adminmanual-11.html#ss11.150">show/sun (0)</A>
-<LI><A NAME="toc11.151">11.151</A> <A HREF="adminmanual-11.html#ss11.151">show/time (0)</A>
-<LI><A NAME="toc11.152">11.152</A> <A HREF="adminmanual-11.html#ss11.152">show/vhfstats (0)</A>
-<LI><A NAME="toc11.153">11.153</A> <A HREF="adminmanual-11.html#ss11.153">show/vhftable (0)</A>
-<LI><A NAME="toc11.154">11.154</A> <A HREF="adminmanual-11.html#ss11.154">show/wcy (0)</A>
-<LI><A NAME="toc11.155">11.155</A> <A HREF="adminmanual-11.html#ss11.155">show/wwv (0)</A>
-<LI><A NAME="toc11.156">11.156</A> <A HREF="adminmanual-11.html#ss11.156">shutdown (5)</A>
-<LI><A NAME="toc11.157">11.157</A> <A HREF="adminmanual-11.html#ss11.157">spoof (9)</A>
-<LI><A NAME="toc11.158">11.158</A> <A HREF="adminmanual-11.html#ss11.158">stat/db (5)</A>
-<LI><A NAME="toc11.159">11.159</A> <A HREF="adminmanual-11.html#ss11.159">stat/channel (5)</A>
-<LI><A NAME="toc11.160">11.160</A> <A HREF="adminmanual-11.html#ss11.160">stat/msg (5)</A>
-<LI><A NAME="toc11.161">11.161</A> <A HREF="adminmanual-11.html#ss11.161">stat/route_node (5)</A>
-<LI><A NAME="toc11.162">11.162</A> <A HREF="adminmanual-11.html#ss11.162">stat/route_user (5)</A>
-<LI><A NAME="toc11.163">11.163</A> <A HREF="adminmanual-11.html#ss11.163">stat/user (5)</A>
-<LI><A NAME="toc11.164">11.164</A> <A HREF="adminmanual-11.html#ss11.164">sysop (0)</A>
-<LI><A NAME="toc11.165">11.165</A> <A HREF="adminmanual-11.html#ss11.165">talk (0)</A>
-<LI><A NAME="toc11.166">11.166</A> <A HREF="adminmanual-11.html#ss11.166">type (0)</A>
-<LI><A NAME="toc11.167">11.167</A> <A HREF="adminmanual-11.html#ss11.167">who (0)</A>
-<LI><A NAME="toc11.168">11.168</A> <A HREF="adminmanual-11.html#ss11.168">wx (0)</A>
-<LI><A NAME="toc11.169">11.169</A> <A HREF="adminmanual-11.html#ss11.169">wx (enhanced for sysops) (5)</A>
-</UL>
-<HR>
-<A HREF="adminmanual-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: Linux Installation </TITLE>
- <LINK HREF="installation-2.html" REL=next>
-
- <LINK HREF="installation.html#toc1" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-2.html">Next</A>
-Previous
-<A HREF="installation.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="s1">1.</A> <A HREF="installation.html#toc1">Linux Installation </A></H2>
-
-<H2><A NAME="ss1.1">1.1</A> <A HREF="installation.html#toc1.1">Introduction</A>
-</H2>
-
-<P>This section describes the installation of DX Spider v1.50 on a
-<A HREF="http://www.redhat.com">RedHat</A> Linux Distribution.
-Wherever possible I will try to include differences for other distributions. </P>
-
-<P>I am assuming a general knowledge of Linux and its commands. You should
-know how to use <EM>tar</EM> and how to edit files using your favourite editor.</P>
-
-<P>The crucial ingredient for all of this is
-<A HREF="http://www.perl.org">Perl</A>. Earlier versions of
-Spider required perl 5.004, however it is now <I>STRONGLY</I> recommended
-that you use at least version 5.005_03 as this is the version being used
-in the development of Spider.</P>
-
-<P>In addition to the standard Red Hat distribution you will require the
-following modules from
-<A HREF="http://www.cpan.org/modules/by-module/">http://www.cpan.org/modules/by-module/</A> , please note however that with later versions of perl, some of these
-modules may be included with the distribution. Get the modules anyway and try
-to install as below. If they complain, they are probably already a part of your
-perl distribution.</P>
-
-<P>
-<UL>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Data/Data-Dumper-2.10.tar.gz">Data-Dumper-2.101.tar.gz</A></LI>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Date/TimeDate-1.10.tar.gz">TimeDate-1.10.tar.gz</A></LI>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/IO/IO-1.20.tar.gz">IO-1.20.tar.gz (for perl 5.00403 and lower)</A></LI>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Net/Net-Telnet-3.02.tar.gz">Net-Telnet-3.03.tar.gz</A></LI>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz">Curses-1.06.tar.gz</A></LI>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A></LI>
-<LI>
-<A HREF="http://www.cpan.org/modules/by-module/Digest/Digest-SHA1-2.01.tar.gz">Digest-SHA1-2.01.tar.gz</A></LI>
-</UL>
-</P>
-
-<P>Copy the CPAN modules listed above to a convenient place on your computer. One good
-place would be /usr/local/packages, and the instructions which follow will assume that
-that's where you have put them.</P>
-
-<P>Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -</P>
-<P>
-<PRE>
-# tar xvfz /usr/local/packages/Data-Dumper-2.101.tar.gz
-# cd Data-Dumper-2.101
-# perl Makefile.PL
-# make test
-# make install
-# cd ..
-#
-# tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
-# cd TimeDate-1.10
-# perl Makefile.PL
-# make test
-# make install
-# cd ..
-#
-# tar xvfz /usr/local/packages/IO-1.20.tar.gz
-# cd IO-1.20
-# perl Makefile.PL
-# make test
-# make install UNINST=1
-# cd ..
-#
-# tar xvfz /usr/local/packages/Net-Telnet-3.03.tar.gz
-# cd Net-Telnet-3.02
-# perl Makefile.PL
-# make test
-# make install
-# cd ..
-#
-# tar xvfz /usr/local/packages/Curses-1.06.tar.gz
-# cd Curses-1.06
-# perl Makefile.PL
-# make test
-# make install
-# cd ..
-#
-# tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz
-# cd Time-HiRes-01.20
-# perl Makefile.PL
-# make test
-# make install
-# cd ..
-#
-# tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz
-# cd Digest-SHA1-2.01
-# perl Makefile.PL
-# make test
-# make install
-# cd ..
-</PRE>
-</P>
-
-<P>Do not fall into the trap of thinking they're all the same, just because they
-nearly are! Pay particular attention to the instructions of <EM>IO</EM>, above.</P>
-
-
-<H2><A NAME="ss1.2">1.2</A> <A HREF="installation.html#toc1.2">Preparation</A>
-</H2>
-
-<P>I will assume that you have already downloaded the latest tarball of
-the DXSpider software and are ready to install it. I am assuming version
-1.50 for this section but of course you would use the latest version.</P>
-
-<P>Login as root and create a user to run the cluster under. <B><I>UNDER
-NO CIRCUMSTANCES USE ROOT AS THIS USER!</I></B>. I am going to use
-the name <EM>sysop</EM>. You can call it anything you wish. Depending
-on your security requirements you may wish to use an existing user,
-however this is your own choice.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# adduser -m sysop
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For SuSE distributions, the command would be ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# useradd -m sysop
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Now set a password for the user ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# passwd sysop
-# New UNIX password:
-# Retype new UNIX password:
-passwd: all authentication tokens updated successfully
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss1.3">1.3</A> <A HREF="installation.html#toc1.3">Installing the software</A>
-</H2>
-
-<P>Now to unpack the DX Spider distribution, set symbolic links and group
-permissions. Copy the tarball to /home/sysop and do the following.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# cd ~sysop
-# tar xvfz spider-1.50.tar.gz
-# ln -s ~sysop/spider /spider
-# groupadd -g 251 spider (or another number)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>If you do not have the command <EM>groupadd</EM> available to you simply
-add a line in /etc/group by hand.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# vi /etc/group (or your favorite editor)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You also need to add some others to the group, including your own callsign
-(this will be used as an alias) and root. The finished line in /etc/group
-should look something like this</P>
-<P><CODE>spider:x:251:sysop,g0vgs,root</CODE></P>
-
-<P>The next step is to set the permissions on the Spider directory tree and files ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# chown -R sysop.spider spider
-# find . -type d -exec chmod 2775 {} \;
-# find . -type f -exec chmod 775 {} \;
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This last step allows various users of the group <EM>spider</EM> to have
-write access to all the directories. This is not really needed just yet
-but will be useful when web interfaces start to appear.</P>
-
-<P>Finally, you need to fix the permissions on the ax25_call and netrom_call
-programs. Check where they are with the <EM>locate</EM> command and alter
-the permissions with the <EM>chmod</EM> command like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# chown root ax25_call netrom_call
-# chmod 4775 ax25_call netrom_call
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss1.4">1.4</A> <A HREF="installation.html#toc1.4">Setting callsigns etc</A>
-</H2>
-
-<P>Now login to your machine as the user you created earlier. In my case that
-user is called <EM>sysop</EM>. Once logged in, issue the following commands ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ cd /spider
-$ mkdir local
-$ mkdir local_cmd
-$ cp perl/DXVars.pm.issue local/DXVars.pm
-$ cd local
-$ vi DXVars.pm (or your favourite editor)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Using the distributed DXVars.pm as a a template, set your cluster callsign,
-sysop callsign and other user info to suit your own environment. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$mycall = "GB7DJK";
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This is the call sign of your cluster. If you use an SSID then include it here
-also.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$myalias = "G1TLH";
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This is the sysop user callsign, normally your own.</P>
-
-<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B></P>
-
-<P>Note that this a perl file which will be parsed and executed as part of the
-cluster. If you get it wrong then perl will complain when you start the cluster
-process. It is important only to alter the text of any section. Some of the
-lines look a little odd. Take this line for example ....</P>
-<P><CODE>$myemail = "ianmaude\@btinternet.com";</CODE></P>
-
-<P>There appears to be an extra slash in there. However this has to be there
-for the file to work so leave it in.</P>
-
-<P>DON'T alter any file in /spider/perl, they are overwritten with every
-release. Any files or commands you place in /spider/local or /spider/local_cmd
-will automagically be used in preference to the ones in /spider/perl EVEN
-while the cluster is running!</P>
-
-<P>Save the new file and change directory to ../perl ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ cd ../perl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Now type the following command which creates the basic user file with you as
-the sysop.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ ./create_sysop.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss1.5">1.5</A> <A HREF="installation.html#toc1.5">The client program</A>
-</H2>
-
-<P>In earlier versions of Spider, all the processes were Perl scripts. This
-was fine but with a lot of users your computer memory would soon be used up.
-To combat this a new client was written in "C". This client only works for
-<EM>incoming</EM> connects at the moment. Before you can use it though it
-has to be "made". CD to /spider/src and type <EM>make</EM>. You
-should see the output on your screen and hopefully now have a small C program
-called <EM>client</EM>. Leave it in this directory.</P>
-
-
-<H2><A NAME="ss1.6">1.6</A> <A HREF="installation.html#toc1.6">Starting up for the first time</A>
-</H2>
-
-<P>We can now bring spider up for the first time and see if all is well or not!
-It should look something like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ ./cluster.pl
-DXSpider DX Cluster Version 1.50
-Copyright (c) 1998 Dirk Koopman G1TLH
-loading prefixes ...
-loading band data ...
-loading user file system ...
-starting listener ...
-reading existing message headers
-reading cron jobs
-orft we jolly well go ...
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>If all is well then login on another term or console as <EM>sysop</EM> and
-cd to /spider/src. Now issue the following command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ ./client
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This should log you into the cluster as the sysop under the alias callsign we
-set earlier. In this case the callsign is G0VGS. The cluster callsign is set
-in the DXVars.pm file in /spider/local. In this case we will assume that this
-was set as GB7MBC. You should therefore see this when you login ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-G0VGS de GB7MBC 19-Nov-1999 2150Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>If you do, congratulations! If not, look over the instructions again, you
-have probably missed something out. You can shut spider down again with the
-command ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-shutdown
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>and both the cluster and the client should return to Linux prompts.</P>
-
-
-<HR>
-<A HREF="installation-2.html">Next</A>
-Previous
-<A HREF="installation.html#toc1">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: Linux quick installation guide</TITLE>
- <LINK HREF="installation-3.html" REL=next>
- <LINK HREF="installation-1.html" REL=previous>
- <LINK HREF="installation.html#toc2" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-3.html">Next</A>
-<A HREF="installation-1.html">Previous</A>
-<A HREF="installation.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2.</A> <A HREF="installation.html#toc2">Linux quick installation guide</A></H2>
-
-<P>This section is designed for experienced Spider sysops who want to install
-Spider from scratch. It is simply a check list of things that need to be
-done without any explanations. The name in brackets at the end of each line
-is the user that should be doing that process.</P>
-<P>
-<UL>
-<LI>Login as root</LI>
-<LI>Get the additional CPAN modules and install them (root)</LI>
-<LI>Create the "sysop" user and set a password (root)</LI>
-<LI>Put the Spider tarball in sysop and untar it (root)</LI>
-<LI>ln -s sysop/spider /spider (root)</LI>
-<LI>groupadd -g 251 spider (root)</LI>
-<LI>Add any more users you need to the group entry in /etc/group (root)</LI>
-<LI>Set the permissions on the spider tree (root)</LI>
-<LI>Fix permissions on ax25_call and netrom_call (root)</LI>
-<LI>Login as the sysop user</LI>
-<LI>cd to /spider (sysop)</LI>
-<LI>mkdir local (sysop)</LI>
-<LI>mkdir local_cmd (sysop)</LI>
-<LI>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)</LI>
-<LI>cd to /spider/local and edit DXVars to set your details (sysop)</LI>
-<LI>cd ../perl (sysop)</LI>
-<LI>./create_sysop.pl (sysop)</LI>
-<LI>./cluster.pl (sysop)</LI>
-</UL>
-</P>
-
-<P>Spider should now be running and you should be able to login using the
-client program.</P>
-<P>
-<UL>
-<LI>Login as root</LI>
-<LI>Enter the correct line in ax25d.conf (root)</LI>
-<LI>Enter the correct line in /etc/services (root)</LI>
-<LI>Enter the correct line in /etc/inetd.conf (root)</LI>
-<LI>killall -HUP inetd (root)</LI>
-</UL>
-</P>
-
-<P>Spider should now be able to accept logins via telnet, netrom and ax25.</P>
-<P>
-<UL>
-<LI>Login as sysop</LI>
-<LI>Start the cluster (sysop)</LI>
-<LI>set/node and type for links (sysop)</LI>
-<LI>Write any connect scripts (sysop)</LI>
-<LI>Edit /spider/crontab as required (sysop)</LI>
-<LI>Edit any other files as necessary (sysop)</LI>
-<LI>Set filters, hops and forwarding files (sysop)</LI>
-<LI>Login as root</LI>
-<LI>Enter the correct line in /etc/inittab (root)</LI>
-</UL>
-</P>
-
-<HR>
-<A HREF="installation-3.html">Next</A>
-<A HREF="installation-1.html">Previous</A>
-<A HREF="installation.html#toc2">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: Setting up the AX25 Utilities</TITLE>
- <LINK HREF="installation-4.html" REL=next>
- <LINK HREF="installation-2.html" REL=previous>
- <LINK HREF="installation.html#toc3" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-4.html">Next</A>
-<A HREF="installation-2.html">Previous</A>
-<A HREF="installation.html#toc3">Contents</A>
-<HR>
-<H2><A NAME="s3">3.</A> <A HREF="installation.html#toc3">Setting up the AX25 Utilities</A></H2>
-
-<P>The aim of this section is not to fully cover the installation
-and configuration of all the possible ax25 modules. I will
-attempt to cover a simple installation and configure 2 serial
-ports as if they had TNC's on them. I will also show what
-additional configuration the DXSpider program requires.</P>
-
-<P>Please bear in mind that I am basing this section on a RedHat
-7.1 distribution, if you are using SuSe or any other distibution
-then your mileage may vary. I will be happy to make any changes
-and additions if you email me any errors or distribution specific
-requirements.</P>
-
-<P>You would probably benefit from reading the
-<A HREF="http://www.fokus.gmd.de/linux/HOWTO/html_single/AX25-HOWTO.html#AEN151">AX25-HOWTO</A> which is much more
-comprehensive and an interesting configuration program is also available
-called
-<A HREF="http://1409.org/projects/index.html">ax25-config</A> which
-may help you to configure things.</P>
-
-<P>The following files are extracts from the working files at GB7MBC and
-are in daily use. However, there are many ways that you can configure the
-ax25 utils, this is just the one I use, it does not mean it is necessarily
-the best or for that matter, the right way!</P>
-
-<H2><A NAME="ss3.1">3.1</A> <A HREF="installation.html#toc3.1">Getting Started</A>
-</H2>
-
-<P>There are 2 things you need to do initially. You need to get the
-3 files required for the ax25 installation and you need to make
-some changes to the kernel configuration.</P>
-
-<P>The first thing is to get the versions of the ax25 utils that match
-your kernel. You may also wish to get a node package of some kind.
-There are 2 main node packages in use of which I shall keep to the
-original by Tomi Manninen, OH2BNS as this is included in the ax25
-rpms as standard. The other is
-<A HREF="ftp://ftp.funet.fi/pub/ham/packet/linux/awznode/">AWZNode</A> by IZ5AWZ.</P>
-
-<P>NB: The AX25 stuff in 2.4 kernels appears to have been broken until 2.4.18. I
-strongly suggest you get at least this kernel.</P>
-
-<P>For 2.4 kernels you need these files...</P>
-
-<P>
-<UL>
-<LI>
-<A HREF="ftp://ftp.rpmfind.net/linux/redhat/7.1/en/powertools/i386/RedHat/RPMS/libax25-0.0.7-7.i386.rpm">libax25-0.0.7-7.i386.rpm</A></LI>
-<LI>
-<A HREF="ftp://ftp.rpmfind.net/linux/redhat/7.1/en/powertools/i386/RedHat/RPMS/ax25-tools-0.0.6-13.i386.rpm">ax25-tools-0.0.6-13.i386.rpm</A></LI>
-<LI>
-<A HREF="ftp://ftp.rpmfind.net/linux/redhat/7.1/en/powertools/i386/RedHat/RPMS/ax25-apps-0.0.4-9.i386.rpm">ax25-apps-0.0.4-9.i386.rpm</A></LI>
-</UL>
-</P>
-
-<H2><A NAME="ss3.2">3.2</A> <A HREF="installation.html#toc3.2">The kernel</A>
-</H2>
-
-<P>First you need to add Amateur Radio Support to your kernel. This is
-a main menu item and should be easily found. Within this header you
-will find lots of options. For our purposes you need to enable
-Amateur Radio AX.25 Level 2 Protocol, NET/ROM and the Serial Port
-KISS Driver. For the purposes of this document I will work under the
-assumption that you include them in the kernel fully, ie not as modules.
-If you need to look at compiling your kernel for ax25 more fully, I would
-refer to the excellent
-<A HREF="http://www.fokus.gmd.de/linux/HOWTO/html_single/AX25-HOWTO.html#AEN151">AX25-HOWTO</A></P>
-
-<P>I should say at this stage that NET/ROM is not mandatory. If you do not use it
-simply ignore any instruction concerning it.</P>
-
-<P>Now recompile your kernel in the normal way and reboot your system.</P>
-
-<H2><A NAME="ss3.3">3.3</A> <A HREF="installation.html#toc3.3">Installing the RPM's</A>
-</H2>
-
-<P>Now install the RPM's you downloaded, libax25 first, then ax25-tools,
-then ax25-apps.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rpm -ivh libax25-0.0.7-7.i386.rpm
-rpm -ivh ax25-tool-0.0.6-13.i386.rpm
-rpm -ivh ax25-apps-0.0.4-9.i386.rpm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss3.4">3.4</A> <A HREF="installation.html#toc3.4">Configuration</A>
-</H2>
-
-<P>You will find the configuration files in /etc/ax25. These consist of
-several files ...</P>
-<P>
-<UL>
-<LI>axports</LI>
-<LI>nrports</LI>
-<LI>nrbroadcast</LI>
-<LI>ax25d.conf</LI>
-<LI>node.conf</LI>
-</UL>
-</P>
-
-<P>These are the main files. You will find other files but they do not
-have any use unless you are wanting to use that particular protocol,
-Rose or axip for example.</P>
-
-<P>NOTE:- before we start it is important to realise that every interface
-requires a different SSID. You should be able to follow this in the
-following examples.</P>
-
-<H2><A NAME="ss3.5">3.5</A> <A HREF="installation.html#toc3.5">axports</A>
-</H2>
-
-<P>This file sets up the ax25 ports you want to use. An example is below
-for a standard TNC2 ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#portname callsign baudrate paclen window description
- 2m gb7mbc-2 19200 256 2 2m port on 144.900MHz
- 4m gb7mbc-4 19200 256 2 4m port on 70.325MHz
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Note that the portnames have to be unique.</P>
-
-<P>The file headings are as follows ...</P>
-<P>
-<PRE>
-portname - The name you will refer to the port by
-callsign - The ax25 callsign you want to assign to the port
-baudrate - The speed you communicate between TNC and computer
-paclen - The maximum packet length for ax25 connections
-window - The ax25 window parameter. This is like 'maxframe'
-description - A textual description of the port
-</PRE>
-</P>
-
-<H2><A NAME="ss3.6">3.6</A> <A HREF="installation.html#toc3.6">nrports</A>
-</H2>
-
-<P>This file sets up the netrom ports you want to use. An example is below
-and includes a port for both cluster and node. You will see why we need
-2 ports later ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#portname callsign alias paclen description
- netrom gb7mbc-8 BARE 236 Node Netrom Port
- netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Note that the portnames have to be unique.</P>
-
-<P>The file headings are as follows ...</P>
-<P>
-<PRE>
-portname - The name you will refer to the port by
-callsign - This is the callsign that NET/ROM traffic from this
- port will use
-alias - The NET/ROM alias this port will be assigned
-paclen - The maximum size of NET/ROM frames transmitted
-description - A textual description of the port
-</PRE>
-</P>
-
-<H2><A NAME="ss3.7">3.7</A> <A HREF="installation.html#toc3.7">nrbroadcast</A>
-</H2>
-
-<P>This file sets up the netrom broadcast qualities. An example is below ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#axport min_obs def_qual worst_qual verbose
- 4m 5 10 100 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The file headings are as follows ...</P>
-<P>
-<PRE>
-axport - The port name in axports that you wish to broadcast
- NET/ROM on.
-min_obs - The minimum obsolescence value for the port
-def_qual - The default quality for the port
-worst_qual - The worst quality for the port. Any routes under
- this quality will be ignored
-verbose - This flag determines whether you will only broadcast
- your own node (0) or all known nodes (1)
-</PRE>
-</P>
-
-<H2><A NAME="ss3.8">3.8</A> <A HREF="installation.html#toc3.8">ax25d.conf</A>
-</H2>
-
-<P>This file controls any incoming ax25 and NET/ROM connections and steers
-them to the relevant program. There are lots of configuration options
-you can set here, however they are well covered in the AX25-HOWTO. For
-our purposes I will show a typical set of parameters. An example is
-below ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-[gb7mbc-0 via 2m]
-parameters 2 1 6 900 * 15 0
-NOCALL * * * * * * L
-default * * * * * * - sysop /spider/src/client client %u ax25
-
-[gb7mbc-1 via 2m]
-parameters 2 1 6 900 * 15 0
-NOCALL * * * * * * L
-default * * * * * * 0 root /usr/sbin/node node
-
-[gb7mbc-0 via 4m]
-parameters 2 1 6 900 * 15 0
-NOCALL * * * * * * L
-default * * * * * * - sysop /spider/src/client client %u ax25
-
-[gb7mbc-1 via 4m]
-parameters 2 1 6 900 * 15 0
-NOCALL * * * * * * L
-default * * * * * * 0 root /usr/sbin/node node
-
-<netrom2>
-parameters 1 10 * * * 3 *
-NOCALL * * * * * * L
-default * * * * * * - sysop /spider/src/client client %u ax25
-
-<netrom>
-parameters 1 10 * * * 3 *
-NOCALL * * * * * * L
-default * * * * * * 0 root /usr/sbin/node node
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>There are a few things to take note of here. Firstly, all ax25
-sections are wrapped in [ ] and all NET/ROM sections are wrapped in
-< >. Secondly you should be able to see that anyone who forgets to
-set their callsign in a TNC and tries to connect with the standard
-NOCALL set into their TNC will not connect, the 'L' means 'lockout'.
-Lastly and importantly, notice the order of the sections. They are
-all done in interface order.</P>
-
-<P>You should be able to see that the normal line for access to the
-cluster is like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-default * * * * * * - sysop /spider/src/client client %u ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>however, if you wish your users to be able to use SSID's on their callsigns ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-default * * * * * * - sysop /spider/src/client client %s ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For most purposes this is not desirable. The only time you probably will
-need this is when you need to allow other cluster nodes that are using SSID's
-in. In this case it would probably be better to use the first example and
-then add a specific line for that node like this:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
-default * * * * * * - sysop /spider/src/client client %u ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss3.9">3.9</A> <A HREF="installation.html#toc3.9">node.conf</A>
-</H2>
-
-<P>For those of you that wish to run the node, you need to set up the
-node.conf file. There are a couple of additional files, node.perms is
-very similar to the way ftp permissions are set up in NOS systems and
-node.motd is the message anyone logging into the node will get.
-The node.conf file sets all the parameters of the node as you would
-expect. An example is below ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# /etc/ax25/node.conf - LinuxNode configuration file
-#
-# see node.conf(5)
-
-# Idle timeout (seconds).
-#
-IdleTimeout 1800
-
-# Timeout when gatewaying (seconds).
-#
-ConnTimeout 40000
-
-# Visible hostname. Will be shown at telnet login.
-#
-HostName gb7mbc.ampr.org
-
-# ReConnect flag.
-#
-ReConnect off
-
-# "Local" network.
-#
-#LocalNet 44.139.8.48/32
-
-# Command aliases. See node.conf(5) for the meaning of the uppercase
-# letters in the name of the alias.
-#
-##Alias CAllbook 'telnet %{2:44.17.0.53} 1235 %1 s'
-#Alias CONVers 'telnet %{2:oh2ti} 3600 "/n %u %{1:139}\n/w *"'
-#Alias CLuster 'c hkiclh'
-Alias CONV "telnet lurpac 3600"
-Alias BBS "c 70cm gb7crv"
-Alias DXC "telnet localhost 9000"
-Alias MUD "telnet homer 4000"
-##Alias TEMP "finger temp@mary.g6phf"
-##Alias TNOS "c ip1 gb7mbc-5"
-##Alias TUtor "telnet gb7mbc 3599"
-
-# Hidden ports.
-#
-#HiddenPorts 2
-
-# External commands. See node.conf(5) for the meaning of the uppercase
-# letters in the name of the extcmd.
-#
-# Flags: 1 Run command through pipe
-# 2 Reconnected flag
-#
-#ExtCmd TPM 3 nobody /usr/bin/finger finger tpm
-#ExtCmd ECho 1 nobody /bin/echo echo \%U \%u \%S \%s \%P \%p \%R \%r \%T \%t \%\% \%0 \%{1:foobar} \%{2} \%3 \%4 \%5
-
-# Node ID.
-#
-NodeId "\nBARE:GB7MBC-1"
-#NodeId \033[01;31m***\033[0m
-
-# Netrom port name. This port is used for outgoing netrom connects.
-#
-NrPort netrom
-
-# Logging level
-#
-LogLevel 3
-
-# The escape character (CTRL-T)
-#
-EscapeChar ^T
-
-# Resolve ip numbers to addresses?
-#
-ResolveAddrs off
-
-# Node prompt.
-#
-#NodePrompt "\n"
-#NodePrompt "%s@%h \%i> "
-NodePrompt "\nBARE:GB7MBC-1 \%i > "
-#NodePrompt "\a\033[36m%U\033[0m de \033[01;32m#LNODE\033[0m:\033[01;33mOH2BNS-10\033[0m> "
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This should be fairly obvious I hope.</P>
-
-<H2><A NAME="ss3.10">3.10</A> <A HREF="installation.html#toc3.10">Getting it all running</A>
-</H2>
-
-<P>Ok, now we have all the relevant files configured, the next step is to get
-it all running.</P>
-
-<P>The first thing to do is attach the TNC's. Your TNC's should be in KISS mode
-and connected to the serial ports involved.</P>
-
-<P>You now use the 'kissattach' command to connect the TNC's to the system like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-kissattach /dev/ttyS0 2m 44.131.96.199
-kissattach /dev/ttyS1 4m 44.131.96.199
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Assuming that 44.131.96.199 is your IP address. The devices ttyS0 and ttyS1 are com1 and
-com2 respectively. Now we can set some parameters ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-kissparms -p 2m -t 150 -l 150 -s 50 -r 50
-kissparms -p 4m -t 150 -l 150 -s 50 -r 50
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The command 'man kissparms' will give you the explanation of the switches.</P>
-
-<P>Now we need to attach the NET/ROM ports in the same way ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-nrattach netrom
-nrattach netrom2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>All of the above can be put in a file and called from /etc/rc.d/rc.local. Put all
-the above commands in a file called rc.ax25 and put a line in rc.local to call it.</P>
-
-<P>Now you can start the daemons that set everything in motion ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ax25d
-netromd -i
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>All should now be running. All that remains is to get the node working for telnet
-connections. If nothing else, this will allow you to connect to the node yourself
-to check on connection status etc. There are 2 files that need to be edited.</P>
-
-<P>First edit /etc/services and add</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-node 3000/tcp #OH2BNS's Node Software
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Assuming you want it to run on port 3000</P>
-
-<P>Now cd /etc/xinetd.d and edit a new file called node. It should look like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# default: on
-# unencrypted username/password pairs for authentication.
-service node
-{
- socket_type = stream
- wait = no
- user = root
- server = /usr/sbin/node
- log_on_failure += USERID
- disable = no
-}
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You now need to restart the xinetd daemon. First find out what the PID is
-like so ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ps auxw |grep xinetd
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You will get a reply something like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-root 592 0.0 0.1 2256 620 ? S Feb07 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The PID or Process ID is 592 in this case so now we can issue the command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-kill -HUP 592
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>All should now be operational and you should be able to log into the node by
-using a telnet session to the relevant port, like so ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-telnet localhost 3000
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>If that works, you are just about there. you should (assuming you have radios connected
-to the TNC's) be able to connect out to other stations and receive incoming ax25 and
-netrom connections.</P>
-
-<HR>
-<A HREF="installation-4.html">Next</A>
-<A HREF="installation-2.html">Previous</A>
-<A HREF="installation.html#toc3">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: Configuration</TITLE>
- <LINK HREF="installation-5.html" REL=next>
- <LINK HREF="installation-3.html" REL=previous>
- <LINK HREF="installation.html#toc4" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-5.html">Next</A>
-<A HREF="installation-3.html">Previous</A>
-<A HREF="installation.html#toc4">Contents</A>
-<HR>
-<H2><A NAME="s4">4.</A> <A HREF="installation.html#toc4">Configuration</A></H2>
-
-<H2><A NAME="ss4.1">4.1</A> <A HREF="installation.html#toc4.1">Allowing ax25 connects from users</A>
-</H2>
-
-<P>This is dealt with in the previous section</P>
-
-<H2><A NAME="ss4.2">4.2</A> <A HREF="installation.html#toc4.2">Allowing telnet connects from users </A>
-</H2>
-
-<P>
->From version 1.47 there is a new (more efficient) way of doing this
-(see next section) but, if you prefer, the method of doing it described
-here will continue to work just fine.</P>
-
-<P>Allowing telnet connections is quite simple. Firstly you need to add a line
-in /etc/services to allow connections to a port number, like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-spdlogin 8000/tcp # spider anonymous login port
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Then add a line in /etc/inetd.conf like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Once this is done, you need to restart inetd like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-killall -HUP inetd
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Now login as <EM>sysop</EM> and cd spider/src. You can test that spider
-is accepting telnet logins by issuing the following command ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./client login telnet
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You should get a login prompt and on issuing a callsign, you will be given
-access to the cluster. Note, you will not get a password login. There seems
-no good reason for a password prompt to be given so it is not asked for.</P>
-
-<P>Assuming all is well, then try a telnet from your linux console ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-telnet localhost 8000
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You should now get the login prompt and be able to login as before.</P>
-
-<H2><A NAME="ss4.3">4.3</A> <A HREF="installation.html#toc4.3">Setting up telnet connects (from 1.47 onwards)</A>
-</H2>
-
-<P>>From version 1.47 you can choose to allow the perl cluster.pl program to
-allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
-interface program). If you are using Windows then this is the only method
-available of allowing incoming telnet connections.</P>
-
-<P>To do this you need first to remove any line that you may previously have set
-up in /etc/inetd.conf. Remember to:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-killall -HUP inetd
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>to make the change happen...</P>
-
-<P>Having done that, you need to copy the file
-<EM>/spider/perl/Listeners.pm</EM> to <EM>/spider/local</EM> and
-then edit it. You will need to uncomment the line containing "0.0.0.0"
-and select the correct port to listen on. So that it looks like this:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-@listen = (
- ["0.0.0.0", 8000],
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>As standard, the listener will listen on all interfaces simultaneously.
-If you require more control than this, you can specify each interface
-individually:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-@listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This will only be successful if the IP addresses on each interface are static.
-If you are using some kind of dynamic IP addressing then the 'default' method
-is the only one that will work.</P>
-
-<P>Restart the cluster.pl program to enable the listener.</P>
-
-<P>One important difference with the internal listener is that no echoing
-is done by the cluster program. Users will need to set 'local-echo' on in
-their telnet clients if it isn't set automatically (as per the standards).
-Needless to say this will probably only apply to Windows users. </P>
-
-<H2><A NAME="ss4.4">4.4</A> <A HREF="installation.html#toc4.4">Setting up for AGW Engine (1.47 onwards)</A>
-</H2>
-
-<P>AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine
-from Linux as well as Windows based machines.</P>
-
-<P>In order to enable access to an AGW Engine you need to copy
-<EM>/spider/perl/AGWConnect.pm</EM> to <EM>/spider/local</EM> and edit it.
-Specifically you must:-</P>
-<P>
-<UL>
-<LI> set <CODE>$enable</CODE> to 1.</LI>
-<LI> set <CODE>$login</CODE> and <CODE>$passwd</CODE> to the values set up in your AGW installation.
-If you haven't set any there, then you should not touch these values.</LI>
-<LI> You can connect to a remote AGW engine (ie on some other machine) by changing <CODE>$addr</CODE>
-and <CODE>$port</CODE> appropriately.</LI>
-<LI> Restart the cluster.pl program</LI>
-</UL>
- </P>
-
-
-<H2><A NAME="ss4.5">4.5</A> <A HREF="installation.html#toc4.5">Setting up node connects</A>
-</H2>
-
-<P>In order to allow cluster node connections, spider needs to know that the
-connecting callsign is a cluster node. This is the case whether the connect
-is incoming or outgoing. In spider this is a simple task and can be done in
-runtime.</P>
-
-<P>Later versions of Spider can distinguish different software and treat them
-differently. For example, the WCY beacon cannot be handles by AK1A type
-nodes as AK1A does not know what to do with PC73. There are 4 different
-types of node at present and although they may not have any major
-differences at the moment, it allows for compatibility. The 4 types are ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/node (AK1A type)
-set/spider
-set/dxnet
-set/clx
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For now, we will assume that the cluster we are going to connect to is an
-AK1A type node.</P>
-
-<P>Start up the cluster as you did before and login as the sysop with client.
-The cluster node I am wanting to make a connection to is GB7BAA but you would
-obviously use whatever callsign you required. At the prompt type ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/node gb7baa
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The case does not matter as long as you have a version of DXSpider later than
-1.33. Earlier versions required the callsign to be in upper case.</P>
-
-<P>That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop, cd to spider/src and issue the command ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./client gb7baa (using the callsign you set as a node)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>You should get an initialisation string from DXSpider like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./client gb7baa
-PC38^GB7MBC^~
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If the callsign you just set up as a cluster node is for an incoming connect,
-this is all that needs to be done. If the connection is to be outgoing then
-a connection script needs to be written.</P>
-
-<P>Sometimes you make a mistake... Honest, it does happen. If you want to make a node
-back to being a normal user, regardless
-of what type it is, do:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-unset/node gb7baa
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss4.6">4.6</A> <A HREF="installation.html#toc4.6">Connection scripts</A>
-</H2>
-
-<P>Because DXSpider operates under Linux, connections can be made using just about
-any protocol; AX25, NETRom, tcp/ip, ROSE etc are all possible examples.
-Connect scripts live in the /spider/connect directory and are simple ascii files.
-Writing a script for connections is therefore relatively simple. </P>
-
-<P>The connect scripts consist of lines which start with the following keywords
-or symbols:-</P>
-<P>
-<DL>
-
-<DT><B>#</B><DD><P>All lines starting with a <CODE>#</CODE> are ignored, as are completely
-blank lines.</P>
-
-<DT><B>timeout</B><DD><P><CODE>timeout</CODE> followed by a number is the number of seconds to wait for a
-command to complete. If there is no timeout specified in the script
-then the default is 60 seconds.</P>
-
-<DT><B>abort</B><DD><P><CODE>abort</CODE> is a regular expression containing one or more strings to look
-for to abort a connection. This is a perl regular expression and is
-executed ignoring case.</P>
-
-<DT><B>connect</B><DD><P><CODE>connect</CODE> followed by ax25, agw (for Windows users) or telnet and some type dependent
-information. In the case of a telnet connection, there can be up to
-two parameters.
-The first is the ip address or hostname of the computer you wish to
-connect to and the second is the port number you want to use (this
-can be left out if it is a normal telnet session).
-In the case of an ax25 session then this would normally be a call to
-ax25_call or netrom_call as in the example above. It is your
-responsibility to get your node and other ax25 parameters to work
-before going down this route!</P>
-
-<DT><B>'</B><DD><P><CODE>'</CODE> is the delimiting character for a word or phrase of an expect/send
-line in a chat type script. The words/phrases normally come in pairs,
-either can be empty. Each line reads input from the connection until
-it sees the string (or perl regular expression) contained in the
-left hand string. If the left hand string is empty then it doesn't
-read or wait for anything. The comparison is done ignoring case.
-When the left hand string has found what it is looking for (if it is)
-then the right hand string is sent to the connection.
-This process is repeated for every line of chat script. </P>
-
-<DT><B>client</B><DD><P><CODE>client</CODE> starts the connection, put the arguments you would want here
-if you were starting the client program manually. You only need this
-if the script has a different name to the callsign you are trying to
-connect to (i.e. you have a script called other which actually
-connects to GB7DJK-1 [instead of a script called gb7djk-1]).</P>
-</DL>
-</P>
-
-<P>There are many possible ways to configure the script but here are three examples,
-one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 60
-abort (Busy|Sorry|Fail)
-# don't forget to chmod 4775 netrom_call!
-connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
-'Connect' ''
-'Connect' 'c np7'
-'Connect' 'c gb7dxm'
-# you can leave this out if you call the script 'gb7dxm'
-client gb7dxm ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 60
-abort (Busy|Sorry|Fail)
-# this does exactly the same as the previous example
-# the '1' is the AGW port number to connect thru for g1tlh
-connect agw 1 g1tlh
-'Connect' ''
-'Connect' 'c np7'
-'Connect' 'c gb7dxm'
-# you can leave this out if you call the script 'gb7dxm'
-client gb7dxm ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 15
-connect telnet dirkl.tobit.co.uk
-'login' 'gb7djk'
-'word' 'gb7djk'
-# tell GB7DJK-1 that it is connected to GB7DJK
-# you can leave this out if you call this script 'gb7djk'
-client gb7djk telnet
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>Both these examples assume that everything is set up properly at the other end.
-You will find other examples in the /spider/examples directory.</P>
-
-<H2><A NAME="ss4.7">4.7</A> <A HREF="installation.html#toc4.7">Starting the connection</A>
-</H2>
-
-<P>You start the connection, from within a sysop enabled cluster login, by typing
-in the word <EM>connect</EM> followed by a script name like this ....</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
-connection to GB7DJK-1 started
-G0VGS de GB7MBC 13-Dec-1998 2043Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This will start a connection using the script called <EM>gb7djk-1</EM>. You can
-follow the connection by watching the term or console from where you started
-<EM>cluster.pl</EM>. From version 1.47 onwards, you will need to <CODE>set/debug connect</CODE> first.
-You should see something like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-<- D G1TLH connect gb7djk-1
--> D G1TLH connection to GB7DJK-1 started
--> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
-timeout set to 15
-CONNECT sort: telnet command: dirkl.tobit.co.uk
-CHAT "login" -> "gb7djk"
-received "
-Red Hat Linux release 5.1 (Manhattan)
-Kernel 2.0.35 on an i586
-"
-received "login: "
-sent "gb7djk"
-CHAT "word" -> "gb7djk"
-received "gb7djk"
-received "Password: "
-sent "gb7djk"
-Connected to GB7DJK-1, starting normal protocol
-<- O GB7DJK-1 telnet
--> B GB7DJK-1 0
-GB7DJK-1 channel func state 0 -> init
-<- D GB7DJK-1
-<- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
-<- D GB7DJK-1 PC38^GB7DJK-1^~
-<- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
-0 00:00^5447^~
- etc
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>With later versions of Spider there is a set/login command for users. This
-tells them when a user or node logs in or out. If you do not add a line to
-your scripts after the final line (or before the client line which should always
-be last if needed) then the login/logout information will be sent to users
-<I>before</I> the login actually completes. This means if a node is
-unreachable, it will continue sending logins and logouts to users even though it
-is not actually connecting. To avoid this use the following line ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-'connect' ''
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>In a script, this might look like ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 35
-abort (Busy|Sorry|Fail)
-connect telnet mary 3000
-'ogin:' 'gb7mbc'
-'>' 'telnet 44.131.93.96 7305'
-'connect' ''
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss4.8">4.8</A> <A HREF="installation.html#toc4.8">Telnet echo</A>
-</H2>
-
-<P>Cluster links in particular suffer greatly from the presence of telnet echo.
-This is caused by the telnet negotiation itself and can create at worst severe
-loops. At best it creates unnecessary bandwidth and large logfiles! There are
-things that can be done to limit this problem but will not always work dependent
-on the route taken to connect.</P>
-
-<P>Telnet echo itself should only be a problem if the connection is being made to
-the telnet port (23). This port uses special rules that include echo negotiation.
-If the connection is to a different port, such as 7300, this negotiation does
-not happen and therefore no echo should be present.</P>
-
-<P>Sometimes it is not possible to make a direct connection to another node and this
-can cause problems. There is a way of trying to suppress the telnet echo but
-this will not always work, unfortunately it is difficult to be more specific.
-Here is an example of what I mean ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 35
-abort (Busy|Sorry|Fail)
-connect telnet mary.lancs.ac.uk
-'ogin:' 'gb7mbc'
-'word:' 'mypasswd'
-'\$' 'stty -echo raw'
-'\$' 'telnet 44.131.93.96'
-'connect' ''
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>So, the first connection is made by Spider. This is fine as Spider uses the
-Net_Telnet script from within perl. This actually uses TCP rather than TELNET
-so no negotiation will be done on the first connection. Once connected to
-mary.lancs.ac.uk, the command is sent to suppress echo. Now a telnet is made
-to a cluster node that is accepting connections on port 23. The problem with
-this link is that the negotiation is made by the remote machine, therefore you
-have no control over it. The chances are that this link will create echo and
-there will be no way you can stop it.</P>
-
-
-<H2><A NAME="ss4.9">4.9</A> <A HREF="installation.html#toc4.9">Autostarting the cluster</A>
-</H2>
-
-<P>Ok, you should now have DXSpider running nicely and allowing connects by cluster
-nodes or users. However, it has to be shutdown and restarted manually. It
-would be much easier to have it start automatically. </P>
-
-<P>This is not only a way to start the cluster automatically, it also works as a
-watchdog, checking the sanity of DXSpider and respawning it should it crash for
-any reason. Before doing the following, shutdown the cluster as you did earlier.</P>
-
-<P>Login as root and bring up the /etc/inittab file in your favourite editor. Add
-the following lines to the file near the end ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-##Start DXSpider on bootup and respawn it should it crash
-DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This line works fine for RedHat distributions. It is also fine for SuSE up to
-7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The line required for Slackware distributions is slightly different. My thanks to
-Aurelio, PA3EZL for this information.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
-it should it crash for any reason.</P>
-
-<P>NB: It should be noted that /dev/tty7 is only an example. Some SuSE systems will
-only accept upto tty6. It really does not matter which tty you run it on.</P>
-
-<P>As root type the command <EM>telinit q</EM>. DXSpider should start up
-immediately. You will see the output on tty7 and if you login as <EM>sysop</EM>
-you should find everything running nicely.</P>
-
-<HR>
-<A HREF="installation-5.html">Next</A>
-<A HREF="installation-3.html">Previous</A>
-<A HREF="installation.html#toc4">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: Microsoft Windows Installation</TITLE>
- <LINK HREF="installation-6.html" REL=next>
- <LINK HREF="installation-4.html" REL=previous>
- <LINK HREF="installation.html#toc5" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-6.html">Next</A>
-<A HREF="installation-4.html">Previous</A>
-<A HREF="installation.html#toc5">Contents</A>
-<HR>
-<H2><A NAME="s5">5.</A> <A HREF="installation.html#toc5">Microsoft Windows Installation</A></H2>
-
-<H2><A NAME="ss5.1">5.1</A> <A HREF="installation.html#toc5.1">Introduction</A>
-</H2>
-
-<P><B>IMPORTANT:</B> </P>
-<P>What you'll be left with once you've followed these instructions
-is (hopefully) a working DX Spider v1.50 system that is capable
-of accepting or originating "internet" connections, plus inbound
-and outbound AX.25 and TCP/IP radio connections.</P>
-<P>On the other hand, you may have an enquiring mind, or better yet,
-may be looking for a useful way of connecting your current
-(perhaps) AK1A cluster "to the internet" via some networking
-mechanism (BPQEther, etc) or other. I won't be producing
-instructions for the latter case, because I don't have an AK1A to
-play with. But someone might ...</P>
-<P>Whatever, this document is intended to get you started with DX
-Spider in a Microsoft Windows ™ environment. It's not
-intended to teach you anything other than how to perform a
-minimum configuration of a DX Spider installation and have it
-able to connect across "the internet" to other DX Clusters, while
-accepting inbound TELNET and radio connections.</P>
-
-<H2><A NAME="ss5.2">5.2</A> <A HREF="installation.html#toc5.2">The requirements</A>
-</H2>
-
-<P>The very first things you're going to need are (in order of
-importance):-</P>
-<P>
-<UL>
-<LI>A cup of good, strong tea</LI>
-<LI>A supported Windows platform with an internet connection so you can
-download the necessary software bits and bobs directly to it. There are other ways, but this is preferable.</LI>
-<LI>Another cup of good, strong tea</LI>
-<LI>If all goes according to plan, about an hour to spare</LI>
-<LI>Plenty of good, strong tea</LI>
-</UL>
-</P>
-
-<H2><A NAME="ss5.3">5.3</A> <A HREF="installation.html#toc5.3">The system</A>
-</H2>
-
-<P>The platform I used to generate these instructions was a
-"vanilla" Microsoft Windows Me 4.90.3000 system, with a 700MHz
-AMD Athlon processor and 96 Mb memory. I've also personally
-verified that it runs on my laptop (Pentium 266MHz, 32 Mb memory,
-Windows 98 SE v4.10.2222 A) and a computer that I assembled from
-a random pile of junk (AMD K6-2 333MHz, 64 Mb memory, Windows 98
-v4.10.1998). As a result, I have reason to believe that what I'm
-about to describe will perform equally on any 32-bit MS Windows
-environment with 32 Mb of memory.</P>
-<P>Because of the changes that have recently been made to the core
-"cluster.pl" module and the introduction of a very lightweight
-"winclient.pl", I have a sneaking suspicion that this will now
-run on any platform that has reasonably complete support for
-Perl. Is there someone out there with both an enquiring mind and
-(say) a Macintosh, for instance?</P>
-<P>Please bear in mind, though, that my instructions relate solely
-to how to get this going under a Microsoft Windows environment,
-and I have zero intention of trying to make them say otherwise.</P>
-
-<H2><A NAME="ss5.4">5.4</A> <A HREF="installation.html#toc5.4">Perl</A>
-</H2>
-
-<P>Install your chosen Perl environment. Unless you have a very good
-reason for not doing so, I strongly suggest that you use
-ActivePerl v5.6. For my testing & development, I used build 623.
-(A recent installation used the newer ActivePerl v5.6.1, build
-633 without any noticable difficulty.) You can get this from:
-<A HREF="http://www.activestate.com/Products/ActivePerl/Download.html">http://www.activestate.com/Products/ActivePerl/Download.html</A></P>
-<P>The link takes you to an initial page of System Requirements and
-Software Prerequisites. If you do not have it already installed,
-you can download and install the Windows Installer 2.0 for a Win98
-installation. Be forewarned, you will have to reboot your PC at the
-completion of the installer's installation. </P>
-<P>If you already have the installer on your PC, simply click on the
-Next arrow at the bottom of the page. Two clicks will finally get
-you to the actual download page. The MSI version of Build 633 is
-now 8.6MB in size, so make that a big cup of tea or coffee if you're
-on a slow dial-up connection.</P>
-<P>During installation, please ensure that you do choose the options
-to "Add Perl to the PATH environment variable" and "Create Perl
-file extension association"; it will make your life so much
-easier. Once the installation is finished, be sure to reboot your
-PC. You probably won't be told anywhere else that this needs to
-be done now, but it does. Really.</P>
-<P>Once you've rebooted, open a "DOS box" (Start > Run > command
-might do it, if you can't find it elsewhere) and from wherever it
-lands, type PERL -v <ENTER> (it's better if that's a lower-case
-'v', because an upper-case 'V' means something else. You should
-be rewarded with some interesting information about your Perl
-installation. If you're not, you must go back to the beginning
-and discover what went wrong and fix it. It's pointless to
-proceed unless this simple check is passed. Assuming it did work,
-you may now move on.</P>
-
-<H2><A NAME="ss5.5">5.5</A> <A HREF="installation.html#toc5.5">Additional packages</A>
-</H2>
-
-<P>Some extensions ("packages") need to be added to the base Perl
-distribution, and we'll do this next. If you're using the Perl I
-recommended, and don't know any better for yourself, then just
-blindly following these instructions will work just fine. If that
-didn't describe you, then you're on your own.</P>
-<P>Visit the following URL:</P>
-<P>
-<A HREF="http://www.activestate.com/PPMPackages/zips/6xx-builds-only/">http://www.activestate.com/PPMPackages/zips/6xx-builds-only/</A></P>
-<P>and download the following files:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Data-Dumper.zip
-Net-Telnet.zip
-TimeDate.zip
-Time-HiRes.zip
-DB_File.zip
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If this is a new installation, now would also be a good time to
-install a copy of WinZip on your PC. Make yourself a convenient
-directory to unpack all of these zip files into (I put mine in
-"D:\ppm>" but "C:\ppm" works just as well.) and do the following
-(the bits you type in are blue ). You can upzip all of the files into
-the same directory. When prompted, simply overwrite the Readme file
-from each zip package. Note that where these files land will be
-directly related to where you chose to install your ActivePerl
-(mine, as you can probably guess from what follows, went into "D:\Perl"):-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-D:\ppm>ppm install Data-Dumper.ppd
-Installing package 'Data-Dumper.ppd'
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
-Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
-Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
-Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
-D:\ppm>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>I'm not going to bother you with exhaustive details of the rest
-of them, but suffice it to say you need to:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ppm install DB_File.ppd
-ppm install Net-Telnet.ppd
-ppm install TimeDate.ppd
-ppm install Time-HiRes.ppd
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If all that seemed to work OK, time to move along. Before anyone
-who is familiar with PPM tells me that we didn't need to download
-and keep those files locally, I knew that. I also knew that PPM
-is sometimes awkward to configure via firewalls, and that
-sometimes the repositories don't always work the way we'd hope. I
-do it that way because it suits me.</P>
-
-<H2><A NAME="ss5.6">5.6</A> <A HREF="installation.html#toc5.6">Getting Spider</A>
-</H2>
-
-<P>Get the current version of the DX Spider distribution. This needs
-to be v1.50 or later. You've got two ways (currently) of getting
-this; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get the latest "official"
-release from:</P>
-<P>
-<A HREF="http://www.dxcluster.org/download/index.html">http://www.dxcluster.org/download/index.html</A></P>
-<P>or if you want the lastest snapshot of CVS version (which is produced
-every night):-</P>
-<P>
-<A HREF="http://www.dxcluster.org/download/CVSlatest.tgz">http://www.dxcluster.org/download/CVSlatest.tgz</A></P>
-<P>This is generally the best one to go for as it is completely up to
-date. However, there is always the very slight chance that it might
-unstable. Generally, there will be a note on the website if this is
-the case. </P>
-
-<P>The only difference between "CVSlatest.tgz" and the latest
-"official" release version is that it is more up to date. <B>Do not confuse
-the "CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" - they
-are two quite different things.</B> "Downloading from Sourceforge with CVS" is
-explained in a section within the Admin manual.</P>
-
-<P>If you go down the CVS route (ie installing WinCVS as explained in the Admin
-manual and downloaded from sourceforge), then everything will be nicely
-installed on your local disk. If you got the CVSlatest.tgz file, unzip
-(
-<A HREF="http://www.winzip.com">winzip</A>) it to "C:\".
-This is an important point since paths are included within the .tgz
-file. Make sure you unzip to the root directory of whichever drive you use...
-"C:\" or "D:\" or .., not "C:\spider." If you double click on CVSlatest.tgz,
-WinZip should open with a dialogue box that says the Archive contains a single
-file (CVSlatest.tar) and asks whether WinZip should decompress it to a
-temporary fold and then open it. Say "Yes" and then you will get the typical
-Classical WinZip listing of files ready for extraction. Remember, extract
-them to your desired root directory ("C:\" or "D:\" or ...). The following
-examples assume that you put it on drive "C:\", for convenience.</P>
-
-<HR>
-<A HREF="installation-6.html">Next</A>
-<A HREF="installation-4.html">Previous</A>
-<A HREF="installation.html#toc5">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: Installing the software</TITLE>
- <LINK HREF="installation-7.html" REL=next>
- <LINK HREF="installation-5.html" REL=previous>
- <LINK HREF="installation.html#toc6" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-7.html">Next</A>
-<A HREF="installation-5.html">Previous</A>
-<A HREF="installation.html#toc6">Contents</A>
-<HR>
-<H2><A NAME="s6">6.</A> <A HREF="installation.html#toc6">Installing the software</A></H2>
-
-<P>At this point you will need to create 2 additional directories under
-"C:\Spider." Make directories "C:\spider\local" and "C:\spider\local_cmd".
-If "C:\spider" is missing, go back and figure out why, because it shouldn't be.</P>
-<P>Now create your own local copy of the DXVars.pm file by:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy c:\spider\perl\DXVars.pm.issue
-c:\spider\local\DXVars.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Now you'll need to edit this file using a text editor like Notepad. If nothing
-else, you can simply</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd \spider\local
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and then</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-notepad DXVars.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>to bring up an editor window containing the file. As an absolute
-minimum you must adjust the following items in DXVars.pm:-</P>
-<P>
-<UL>
-<LI> $mycall - Should hold the callsign of your DX Cluster</LI>
-<LI> $myname - The SysOp's first name</LI>
-<LI> $myalias - the SysOp's callsign. Cannot be the same as $mycall!</LI>
-<LI> $myqth - The station's geographical location (QTH).</LI>
-<LI> $mylatitude - The station latitude in degrees and decimal fractions</LI>
-<LI> $mylongitude - The station longitude in degrees and decimal fractions</LI>
-<LI> $mylocator - The Maidenhead (or QRA) locator of the station </LI>
-</UL>
-</P>
-<P>You really also ought to update the $myqth and $myemail variables. And
-unless you are absolutely certain you know what you're doing, you
-should change nothing else in this file. Note that if you use an "@" or
-a "$" character in one of the above strings (typically in $myemail) you must
-write them as "\@" or "\$". </P>
-
-<H2><A NAME="ss6.1">6.1</A> <A HREF="installation.html#toc6.1">Incoming telnets</A>
-</H2>
-
-<P>If you want to enable inbound "TELNET" connections (or you are running
-Windows 98, NT, 2000 or XP), you've got a little more work to do. From a
-handy "DOS box" that's not doing anything else, do the following:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy \spider\perl\Listeners.pm \spider\local
-cd \spider\local
-notepad listeners.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The following line need attention:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# ["0.0.0.0", 7300],
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>On my machine, I've simply uncommented the "0.0.0.0" entry by
-removing the '#' from the front of the line. </P>
-<P><B>You MUST carry out this step if you are
-running on a Windows 98, NT, 2000 or XP based system</B></P>
-<P>If you don't have a static hostname for your machine, and you
-intend to allow folk to connect to your machine across the
-internet, then I'd suggest you pay a visit to www.dyndns.org and
-create one for yourself. While it's free, it will take a modest
-amount of effort on your part to read, understand and
-implement what needs to be done to set this up.</P>
-
-<P>If your machine is connected to the internet <B>and</B> you don't
-want to allow your machine to be visible to the outside world you
-should change the "0.0.0.0" to "127.0.0.1" [which is
-"localhost"]. This will then only allow connections from inside your
-machine. As was said earlier: if you aren't running Win9x (or you want
-to use DXTelnet or somesuch), then you need to have the machine
-listening at least to "127.0.0.1" ("0.0.0.0" means <B>all</B> IP
-addresses).</P>
-
-<H2><A NAME="ss6.2">6.2</A> <A HREF="installation.html#toc6.2">The AGW packet engine</A>
-</H2>
-
-<P>On the assumption that you'll be using the SV2AGW Packet Engine
-to interface your radios to the cluster, it would be a good idea to
-download the Packet Engine software! You can get this software from:</P>
-<P>
-<A HREF="http://www.raag.org/sv2agw/agwpe.zip">http://www.raag.org/sv2agw/agwpe.zip</A></P>
-<P>Depending upon your TNCs, you may also need to get:</P>
-<P>
-<A HREF="http://www.raag.org/sv2agw/drivers.zip">http://www.raag.org/sv2agw/drivers.zip</A></P>
-<P>A couple of the tools:</P>
-<P>
-<A HREF="http://www.raag.org/sv2agw/agwterm.zip">http://www.raag.org/sv2agw/agwterm.zip</A></P>
-<P>
-<A HREF="http://www.raag.org/sv2agw/agwmonitor.zip">http://www.raag.org/sv2agw/agwmonitor.zip</A></P>
-<P>will also help with troubleshooting of the RF links themselves.</P>
-<P>Install and configure AGWPE. You should now create your own local copy of
-AGWConnect.pm by:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy c:\spider\perl\AGWConnect.pm
-c:\spider\local\AGWConnect.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and then</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-notepad AGWConnect.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>to bring up an editor window containing the file. You must
-consider adjusting the following items in AGWConnect.pm:-</P>
-<P>
-<UL>
-<LI>$enable - set to '1' to enable AGWPE interface </LI>
-<LI>$login - the login ID you chose when you set up the SV2AGW security :-)</LI>
-<LI>$passwd - password that matches $login</LI>
-</UL>
-</P>
-<P>The login ID and passwd only need to be set if you are accessing AGW separately
-via its web interface. This interface is normally not needed for use with DXSpider.</P>
-
-<H2><A NAME="ss6.3">6.3</A> <A HREF="installation.html#toc6.3">Setting up the initial user files</A>
-</H2>
-
-<P>Next you need to create the initial user files, etc. A tool is
-supplied which will do this for you. To run the tool:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd \spider\perl
-perl create_sysop.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If all goes according to plan, you will see no output from this
-program, and after a brief wait, your DOS prompt will be
-returned.</P>
-<P>Depending on how brave you are, you might now care to try the
-following:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-perl cluster.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you did everything you were told, your DOS window will now
-hold a display which looks something like:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DXSpider DX Cluster Version 1.50
-Copyright (c) 1998-2002 Dirk Koopman G1TLH
-loading prefixes ...
-loading band data ...
-loading user file system ...
-starting listeners ...
-Internal port: localhost 27754
-load badwords: Ok
-reading in duplicate spot and WWV info ...
-reading existing message headers ...
-load badmsg: Ok
-load forward: Ok
-load swop: Ok
-@msg = 0 before delete
-@msg = 0 after delete
-reading cron jobs ...v cron: reading /spider/cmd/crontab
-cron: adding 1 0 * * 0
-DXUser::export("$main::data/user_asc")
-reading database descriptors ...
-doing local initialisation ...
-orft we jolly well go ...
-queue msg (0)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Now, if that's what you've got, you are very nearly home and dry
-(in as far as these particular experiments are concerned, anyhow)</P>
-<P>If you are running Windows 9x you can access your new cluster (from
-the local machine) by finding yourself another "DOS box" and doing the
-following:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd \spider\perl
-perl winclient.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you are running Windows NT, 2000 or XP then winclient.pl does not
-work. We don't know why other than this seems to be some kind of
-incomaptibility in perl. You can achieve the same thing by telnetting
-to the port you defined in Listeners.pm (7300 as default), thus:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Menu->Start->Run
-telnet localhost 7300
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>On getting the <B>login:</B> prompt, enter your sysop callsign (the one you
-put in DXVars.pm as $myalias).</P>
-
-<P>I would recommend <B>strongly</B> that you obtain a better telnet
-client than that which comes with windows (I use
-<A HREF="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html">PuTTY</A>). </P>
-
-<P>Anyway, if you are rewarded with a display which looks something like:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.50
-Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
-M0ADI de GB7SJP 4-Mar-2001 1511Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You've arrived. Try some commands, and see how they feel. (In
-case you were wondering, "Iain", "M0ADI" and "GB7SJP" all came
-from the version of DXVars.pm that was on the machine when I
-started the winclient.pl)</P>
-
-<P>The interface is very basic. It is a simple command line. There are
-better looking interfaces. Most of the "standard" logging and DX
-Cluster access programs that are capable of connecting via a TCP or
-telnet connection will work as a "Sysop Console" client. You connect
-to "localhost" on the port that you defined in Listeners.pm (usually
-7300). I recommend packages like
-<A HREF="http://www.qsl.net/wd4ngb/telnet.htm">DXTelnet</A>.</P>
-
-<H2><A NAME="ss6.4">6.4</A> <A HREF="installation.html#toc6.4">Connecting to other clusters</A>
-</H2>
-
-<P>If you want to connect this to another cluster, then you'll want to
-negotiate a link with someone. For experimental purposes, I'm happy to
-allow folk to connect to GB7DXA (spud.ath.cx), on the understanding
-that the system may or may not be there and may or may not be
-connected to anything particularly useful at any given moment. Contact
-me by
-<A HREF="mailto:g0rdi@blacksheep.org">Email</A> if you
-want me to set up a connection for you.</P>
-
-<HR>
-<A HREF="installation-7.html">Next</A>
-<A HREF="installation-5.html">Previous</A>
-<A HREF="installation.html#toc6">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50: General Information</TITLE>
- <LINK HREF="installation-6.html" REL=previous>
- <LINK HREF="installation.html#toc7" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-<A HREF="installation-6.html">Previous</A>
-<A HREF="installation.html#toc7">Contents</A>
-<HR>
-<H2><A NAME="s7">7.</A> <A HREF="installation.html#toc7">General Information</A></H2>
-
-<P>The following relates to all versions of DXSpider and is not platform related.</P>
-
-<H2><A NAME="ss7.1">7.1</A> <A HREF="installation.html#toc7.1">The crontab file</A>
-</H2>
-
-<P>Login as <EM>sysop</EM> and create a file in /spider/local_cmd called crontab.
-Edit it with your favourite editor and add a line like this (I have included
-a comment)</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# check every 10 minutes to see if gb7xxx is connected and if not
-# start a connect job going
-
-0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>The callsign involved will be the callsign of the cluster node you are
-going to connect to. This will now check every 10 minutes to see if
-gb7xxx is connected, if it is then nothing will be done. If it is not,
-then a connect attempt will be started.</P>
-
-<P>There are probably lots of other things you could use this crontab file for.
-If you want to know more about it, look at the
-<A HREF="http://www.dxcluster.org/cron.html">DXSpider</A> website
-at the cron page where it is explained more fully.</P>
-
-<HR>
-Next
-<A HREF="installation-6.html">Previous</A>
-<A HREF="installation.html#toc7">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider Installation Manual v1.50</TITLE>
- <LINK HREF="installation-1.html" REL=next>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="installation-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>The DXSpider Installation Manual v1.50</H1>
-
-<H2>Iain Philipps, G0RDI (g0rdi@77hz.com),
-Ian Maude, G0VGS, (g0vgs@gb7mbc.net) and Charlie
-Carroll, K1XX, (k1xx@ptcnh.net)</H2>February 2003 revision 0.5
-<HR>
-<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
-<HR>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="installation-1.html">Linux Installation </A></H2>
-
-<UL>
-<LI><A NAME="toc1.1">1.1</A> <A HREF="installation-1.html#ss1.1">Introduction</A>
-<LI><A NAME="toc1.2">1.2</A> <A HREF="installation-1.html#ss1.2">Preparation</A>
-<LI><A NAME="toc1.3">1.3</A> <A HREF="installation-1.html#ss1.3">Installing the software</A>
-<LI><A NAME="toc1.4">1.4</A> <A HREF="installation-1.html#ss1.4">Setting callsigns etc</A>
-<LI><A NAME="toc1.5">1.5</A> <A HREF="installation-1.html#ss1.5">The client program</A>
-<LI><A NAME="toc1.6">1.6</A> <A HREF="installation-1.html#ss1.6">Starting up for the first time</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="installation-2.html">Linux quick installation guide</A></H2>
-
-<P>
-<H2><A NAME="toc3">3.</A> <A HREF="installation-3.html">Setting up the AX25 Utilities</A></H2>
-
-<UL>
-<LI><A NAME="toc3.1">3.1</A> <A HREF="installation-3.html#ss3.1">Getting Started</A>
-<LI><A NAME="toc3.2">3.2</A> <A HREF="installation-3.html#ss3.2">The kernel</A>
-<LI><A NAME="toc3.3">3.3</A> <A HREF="installation-3.html#ss3.3">Installing the RPM's</A>
-<LI><A NAME="toc3.4">3.4</A> <A HREF="installation-3.html#ss3.4">Configuration</A>
-<LI><A NAME="toc3.5">3.5</A> <A HREF="installation-3.html#ss3.5">axports</A>
-<LI><A NAME="toc3.6">3.6</A> <A HREF="installation-3.html#ss3.6">nrports</A>
-<LI><A NAME="toc3.7">3.7</A> <A HREF="installation-3.html#ss3.7">nrbroadcast</A>
-<LI><A NAME="toc3.8">3.8</A> <A HREF="installation-3.html#ss3.8">ax25d.conf</A>
-<LI><A NAME="toc3.9">3.9</A> <A HREF="installation-3.html#ss3.9">node.conf</A>
-<LI><A NAME="toc3.10">3.10</A> <A HREF="installation-3.html#ss3.10">Getting it all running</A>
-</UL>
-<P>
-<H2><A NAME="toc4">4.</A> <A HREF="installation-4.html">Configuration</A></H2>
-
-<UL>
-<LI><A NAME="toc4.1">4.1</A> <A HREF="installation-4.html#ss4.1">Allowing ax25 connects from users</A>
-<LI><A NAME="toc4.2">4.2</A> <A HREF="installation-4.html#ss4.2">Allowing telnet connects from users </A>
-<LI><A NAME="toc4.3">4.3</A> <A HREF="installation-4.html#ss4.3">Setting up telnet connects (from 1.47 onwards)</A>
-<LI><A NAME="toc4.4">4.4</A> <A HREF="installation-4.html#ss4.4">Setting up for AGW Engine (1.47 onwards)</A>
-<LI><A NAME="toc4.5">4.5</A> <A HREF="installation-4.html#ss4.5">Setting up node connects</A>
-<LI><A NAME="toc4.6">4.6</A> <A HREF="installation-4.html#ss4.6">Connection scripts</A>
-<LI><A NAME="toc4.7">4.7</A> <A HREF="installation-4.html#ss4.7">Starting the connection</A>
-<LI><A NAME="toc4.8">4.8</A> <A HREF="installation-4.html#ss4.8">Telnet echo</A>
-<LI><A NAME="toc4.9">4.9</A> <A HREF="installation-4.html#ss4.9">Autostarting the cluster</A>
-</UL>
-<P>
-<H2><A NAME="toc5">5.</A> <A HREF="installation-5.html">Microsoft Windows Installation</A></H2>
-
-<UL>
-<LI><A NAME="toc5.1">5.1</A> <A HREF="installation-5.html#ss5.1">Introduction</A>
-<LI><A NAME="toc5.2">5.2</A> <A HREF="installation-5.html#ss5.2">The requirements</A>
-<LI><A NAME="toc5.3">5.3</A> <A HREF="installation-5.html#ss5.3">The system</A>
-<LI><A NAME="toc5.4">5.4</A> <A HREF="installation-5.html#ss5.4">Perl</A>
-<LI><A NAME="toc5.5">5.5</A> <A HREF="installation-5.html#ss5.5">Additional packages</A>
-<LI><A NAME="toc5.6">5.6</A> <A HREF="installation-5.html#ss5.6">Getting Spider</A>
-</UL>
-<P>
-<H2><A NAME="toc6">6.</A> <A HREF="installation-6.html">Installing the software</A></H2>
-
-<UL>
-<LI><A NAME="toc6.1">6.1</A> <A HREF="installation-6.html#ss6.1">Incoming telnets</A>
-<LI><A NAME="toc6.2">6.2</A> <A HREF="installation-6.html#ss6.2">The AGW packet engine</A>
-<LI><A NAME="toc6.3">6.3</A> <A HREF="installation-6.html#ss6.3">Setting up the initial user files</A>
-<LI><A NAME="toc6.4">6.4</A> <A HREF="installation-6.html#ss6.4">Connecting to other clusters</A>
-</UL>
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="installation-7.html">General Information</A></H2>
-
-<UL>
-<LI><A NAME="toc7.1">7.1</A> <A HREF="installation-7.html#ss7.1">The crontab file</A>
-</UL>
-<HR>
-<A HREF="installation-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider CVS Changes Addendum v1.50</TITLE>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-Previous
-Contents
-<HR>
-<H1>The DXSpider CVS Changes Addendum v1.50</H1>
-
-<H2>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>February 2003 revision 0.1
-<HR>
-<EM>A reference for CVS users of the DXSpider DXCluster program.</EM>
-<HR>
-<P>If you have any problems with a new CVS version please mail the support
-list.</P>
-
-<P>The latest CVS is version 1.50 build 57.191. There are major changes going on currently as the code is being prepared for New Protocol.</P>
-
-<P>To run the latest CVS you need to additional perl modules. The links are below...</P>
-
-<P>
-<UL>
-<LI>
-<A HREF="ftp://ftp.plig.org/pub/CPAN/authors/id/A/AM/AMS/Storable-2.06.tar.gz">Storable-2.06.tar.gz</A></LI>
-<LI>
-<A HREF="ftp://ftp.plig.org/pub/CPAN/authors/id/M/MR/MROGASKI/Log-Agent-0.303.tar.gz">Log-Agent-0.303.tar.gz</A></LI>
-</UL>
-</P>
-
-<HR>
-Next
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider FAQ: Installation </TITLE>
- <LINK HREF="spiderFAQ-2.html" REL=next>
-
- <LINK HREF="spiderFAQ.html#toc1" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="spiderFAQ-2.html">Next</A>
-Previous
-<A HREF="spiderFAQ.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="s1">1.</A> <A HREF="spiderFAQ.html#toc1">Installation </A></H2>
-
-<H2><A NAME="ss1.1">1.1</A> <A HREF="spiderFAQ.html#toc1.1">Where do I get DXSpider?</A>
-</H2>
-
-<P>All things Spider can be found at
-<A HREF="http://www.dxcluster.org">www.dxcluster.org</A> and the actual program and patches can be found in the
-<A HREF="http://www.dxcluster.org/download/index.html">download</A> area.</P>
-
-<H2><A NAME="ss1.2">1.2</A> <A HREF="spiderFAQ.html#toc1.2">How do I use the patches?</A>
-</H2>
-
-<P>Patching is done in the standard linux way ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-zcat /tmp/patch-1.40 | patch -p0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>assuming the patch version you are using is 1.40 and resides in /tmp!</P>
-
-<P>Be aware that each patch assumes the previous patch has been applied. That
-is to say if you are patching from version 1.38 to 1.40 you would first need
-to apply patch-1.39 and then patch-1.40.</P>
-
-<H2><A NAME="ss1.3">1.3</A> <A HREF="spiderFAQ.html#toc1.3">If I use a tarball to overwrite my installation, what happens to my configuration?</A>
-</H2>
-
-<P>The tarballs are designed to not overwrite your existing configuration
-and can be used at any time to update your Spider software. All the key
-files have the suffix .issue (eg. DXVars.pm.issue) at default.</P>
-
-<H2><A NAME="ss1.4">1.4</A> <A HREF="spiderFAQ.html#toc1.4">I am running RedHat 5.2 and I am getting strange errors, what is wrong?</A>
-</H2>
-
-<P>The version of Perl that comes with 5.2 seems to be some kind of pre-release
-and is broken. You can get a new version of perl from
-<A HREF="http://www.dxcluster.org/download/index.html">www.dxcluster.org</A>
-or
-<A HREF="ftp://updates.redhat.com">ftp://updates.redhat.com</A>.
-Don't forget to patch it with the CPAN modules.</P>
-
-<HR>
-<A HREF="spiderFAQ-2.html">Next</A>
-Previous
-<A HREF="spiderFAQ.html#toc1">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider FAQ: Administration</TITLE>
- <LINK HREF="spiderFAQ-1.html" REL=previous>
- <LINK HREF="spiderFAQ.html#toc2" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-<A HREF="spiderFAQ-1.html">Previous</A>
-<A HREF="spiderFAQ.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2.</A> <A HREF="spiderFAQ.html#toc2">Administration</A></H2>
-
-<H2><A NAME="ss2.1">2.1</A> <A HREF="spiderFAQ.html#toc2.1">How can I get Spider to restart automatically if it crashes?</A>
-</H2>
-
-<P>Put this line into /etc/inittab ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Run <EM>telinit q</EM> as root. Spider will restart so be aware. However, any
-time you reboot, cluster.pl will start in tty7 and if it crashes, it should restart ok.</P>
-
-<H2><A NAME="ss2.2">2.2</A> <A HREF="spiderFAQ.html#toc2.2">How can I monitor traffic to and from a node or user?</A>
-</H2>
-
-<P>There are 2 ways to achieve this. You can use the <EM>tail</EM> command like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-tail -f /spider/data/debug/167.dat |grep G0VGS
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>or in later versions of Spider, there is a command called <EM>watchdbg</EM> in which
-case you simply type ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-watchdbg G0VGS
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss2.3">2.3</A> <A HREF="spiderFAQ.html#toc2.3">My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.</A>
-</H2>
-
-<P>Assuming that the permissions are set correctly (perm level 5 required), it could be
-that the home_node is set incorrectly. You can reset the home_node using the <EM>spoof</EM>
-command like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-spoof gb7adx set/home gb7adx
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Assuming that the node_call you are changing is gb7adx.</P>
-
-<H2><A NAME="ss2.4">2.4</A> <A HREF="spiderFAQ.html#toc2.4">I do not seem to be sending any bulletin mail to my link partners, what is wrong?</A>
-</H2>
-
-<P>There is a file in /spider/msg called forward.pl.issue. Rename this to
-forward.pl and edit it to meet your requirements. You will need to issue
-the command <EM>load/forward</EM> or restart Spider for the changes to
-take effect.</P>
-
-<H2><A NAME="ss2.5">2.5</A> <A HREF="spiderFAQ.html#toc2.5">How can I automatically limit the amount of debug logfiles that are stored?</A>
-</H2>
-
-<P>Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-/usr/sbin/tmpwatch -f 240 /spider/data/debug
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Remember to make it executable!</P>
-<P>This will limit your debug data down to the last 10 days</P>
-
-<H2><A NAME="ss2.6">2.6</A> <A HREF="spiderFAQ.html#toc2.6">I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?</A>
-</H2>
-
-<P>Almost certainly this is a change in the db format of perl. Follow these
-few steps to correct the problem.</P>
-<P>
-<UL>
-<LI>stop the cluster (disable any autostart in inittab)</LI>
-<LI>cd /spider/data</LI>
-<LI>issue the command perl user_asc</LI>
-<LI>restart the cluster</LI>
-</UL>
-</P>
-<P>That should solve the problem.</P>
-
-<H2><A NAME="ss2.7">2.7</A> <A HREF="spiderFAQ.html#toc2.7">Since I last updated I seem to be getting duplicate spots appearing.</A>
-</H2>
-
-<P>What has probably happened is that the dupefile has got corrupted in
-some way. Simply delete the /spider/data/dupefile and restart the
-cluster. It may take a little time to become fully functional but
-should solve your problem.</P>
-
-<H2><A NAME="ss2.8">2.8</A> <A HREF="spiderFAQ.html#toc2.8">I have deleted a message but it is still there, why?</A>
-</H2>
-
-<P>This is now the way messages are handled for deletion in Spider. If you
-look closely you will see a 'D' following the message number. This
-message is marked for deletion and will be deleted in 2 days if nothing
-further is done. Optionally you can use the command <EM>delete/expunge</EM>
-to delete it immediately.</P>
-
-<HR>
-Next
-<A HREF="spiderFAQ-1.html">Previous</A>
-<A HREF="spiderFAQ.html#toc2">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider FAQ</TITLE>
- <LINK HREF="spiderFAQ-1.html" REL=next>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="spiderFAQ-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>The DXSpider FAQ</H1>
-
-<H2>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>December 2001 Revision: 1.8
-<HR>
-<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
-<HR>
-<P>Please mail any FAQs to the maintainer at the address above.</P>
-
-
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="spiderFAQ-1.html">Installation </A></H2>
-
-<UL>
-<LI><A NAME="toc1.1">1.1</A> <A HREF="spiderFAQ-1.html#ss1.1">Where do I get DXSpider?</A>
-<LI><A NAME="toc1.2">1.2</A> <A HREF="spiderFAQ-1.html#ss1.2">How do I use the patches?</A>
-<LI><A NAME="toc1.3">1.3</A> <A HREF="spiderFAQ-1.html#ss1.3">If I use a tarball to overwrite my installation, what happens to my configuration?</A>
-<LI><A NAME="toc1.4">1.4</A> <A HREF="spiderFAQ-1.html#ss1.4">I am running RedHat 5.2 and I am getting strange errors, what is wrong?</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="spiderFAQ-2.html">Administration</A></H2>
-
-<UL>
-<LI><A NAME="toc2.1">2.1</A> <A HREF="spiderFAQ-2.html#ss2.1">How can I get Spider to restart automatically if it crashes?</A>
-<LI><A NAME="toc2.2">2.2</A> <A HREF="spiderFAQ-2.html#ss2.2">How can I monitor traffic to and from a node or user?</A>
-<LI><A NAME="toc2.3">2.3</A> <A HREF="spiderFAQ-2.html#ss2.3">My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.</A>
-<LI><A NAME="toc2.4">2.4</A> <A HREF="spiderFAQ-2.html#ss2.4">I do not seem to be sending any bulletin mail to my link partners, what is wrong?</A>
-<LI><A NAME="toc2.5">2.5</A> <A HREF="spiderFAQ-2.html#ss2.5">How can I automatically limit the amount of debug logfiles that are stored?</A>
-<LI><A NAME="toc2.6">2.6</A> <A HREF="spiderFAQ-2.html#ss2.6">I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?</A>
-<LI><A NAME="toc2.7">2.7</A> <A HREF="spiderFAQ-2.html#ss2.7">Since I last updated I seem to be getting duplicate spots appearing.</A>
-<LI><A NAME="toc2.8">2.8</A> <A HREF="spiderFAQ-2.html#ss2.8">I have deleted a message but it is still there, why?</A>
-</UL>
-<HR>
-<A HREF="spiderFAQ-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
-<html>
- <head>
- <title>User Command Reference</title>
- <meta name="Keywords" content="DX Cluster, DXSpider, Spider, Packet Cluster, DXCluster, Pavillion Software, AK1A, AX25, AX.25, WWV, Packet Radio, Amateur Radio, Propagation, DX, DXing, G1TLH, GB7TLH, Dirk Koopman, Mailing list, Linux, RedHat, PERL">
- <meta name="Description" content="Software and systems for realtime digital communications between amateur radio stations for the provision of information on propagation conditions and stations operating">
- <meta name="Author" content="Dirk Koopman G1TLH">
- </head>
- <body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
- <FONT COLOR="#606060">
- <hr>
- <h2>User Command Reference</h2>
- <hr>
- </font>
-
-
- <address><a href="mailto:djk@tobit.co.uk">Dirk Koopman G1TLH</a></address>
- <p>
- <!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
- <!-- hhmts start -->
-Last modified: Wed Nov 17 16:27:21 GMT 1999
-<!-- hhmts end -->
- <h4>Introduction</h4>
-
- <p>This is the list of user commands currently available within the DX Spider DX Cluster system.</p>
- <p>It is automatically generated from the system help files.</p>
-
- <h4>The Commands</h4>
-
- <data>
-
-<!-- Standard Footer!! -->
- <p> </p>
- <p>
- <FONT COLOR="#606060"><hr></font>
- <font color="#FF0000" size=-2>
- Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved<br>
- </font>
- <font color="#000000" size=-2>$Id$</font>
- </body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
-<html>
- <head>
- <title>Local extensions</title>
- <meta name="Keywords" content="DX Cluster, DXSpider, Spider, Packet Cluster, DXCluster, Pavillion Software, AK1A, AX25, AX.25, WWV, Packet Radio, Amateur Radio, Propagation, DX, DXing, G1TLH, GB7TLH, Dirk Koopman, Mailing list, Linux, RedHat, PERL">
- <meta name="Description" content="Software and systems for realtime digital communications between amateur radio stations for the provision of information on propagation conditions and stations operating">
- <meta name="Author" content="Dirk Koopman G1TLH">
- </head>
- <body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
- <FONT COLOR="#606060">
- <hr>
- <h2>Local extensions</h2>
- <hr>
- </font>
-
-
- <address><a href="mailto:djk@tobit.co.uk">Dirk Koopman G1TLH</a></address>
- <p>
- <!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
- <!-- hhmts start -->
-Last modified: Mon Dec 28 22:43:23 GMT 1998
-<!-- hhmts end -->
- <h4>Introduction</h4>
-
- The DXSpider system is designed to be extensible, to facilitate experimentation and
- self-training in both Amateur Radio and Programming.
-
- <p>Having said all of that it is also designed so that it should be relatively easy to solve
- some real world problems that we have in the DX Cluster network as well as allow the implementation
- and testing of new protocols relatively safely.
-
- <h4>What is it?</h4>
-
- The mechanism I have chosen to allow people to do their own thing, is a perl <tt>.pm</tt> file called
- <b>Local.pm</b>. It is simply a perl package with its own address space, which has a number of defined
- subroutines called from certain places in the daemon code. I have provided a "blank" version for you
- to modify.
-
- <h4>Where is it?</h4>
-
- The template is <b>/spider/perl/Local.pm</b>. This file should be
- copied into <b>/spider/local</b> and then modified to your taste.
-
- <p>At the moment, the template's format and standard functions are
- not really finalised, but I won't take away the functions that are
- currently there and I won't rename them. I reserve the right to
- add to them!
-
- <p>As and when I get a clearer idea of what people might wish to do with
- it and how, I will add to the documentation on this page. So for now:
- this is it!
-
-<!-- Standard Footer!! -->
- <p> </p>
- <p>
- <FONT COLOR="#606060"><hr></font>
- <font color="#FF0000" size=-2>
- Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved<br>
- </font>
- <font color="#000000" size=-2>$Id$</font>
- </body>
-</html>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Introduction</TITLE>
- <LINK HREF="usermanual-2.html" REL=next>
-
- <LINK HREF="usermanual.html#toc1" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-2.html">Next</A>
-Previous
-<A HREF="usermanual.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="s1">1.</A> <A HREF="usermanual.html#toc1">Introduction</A></H2>
-
-<H2><A NAME="ss1.1">1.1</A> <A HREF="usermanual.html#toc1.1">What is a DX Cluster?</A>
-</H2>
-
-<P>A DX Cluster is a packet node where DX chasers on any band or mode can
-post rare or interesting stations that they have worked or heard. Of
-course other people are doing the same thing too, so you can find new
-DX as well as telling others about the stations you have worked.
-Clusters tend to be linked to each other so that the amount of people
-using them is increased, thereby increasing the amount of posted DX.
-Other information can be found on clusters such as on-line call books,
-mail etc. You can talk to other stations connected to the cluster
-network too, in real time, whether at the node you are logged into or
-on another node connected to the network. You can also use converse
-mode, where several stations can talk to each other in the same way.
-Of course, the DX is still posted to you all the while!</P>
-
-<H2><A NAME="ss1.2">1.2</A> <A HREF="usermanual.html#toc1.2">So what is DXSpider?</A>
-</H2>
-
-<P>PacketCluster nodes have been around since roughly 1985. The original
-PacketCluster idea came from Dick Newell, AK1A, and ran under DOS.
-In about 1992 Dick stopped the development of the PacketCluster
-software for amateur radio. Many systems are still using this
-relatively old DOS software today.</P>
-<P>There are several new compatible cluster programs around now,
-including DXSpider. DXSpider is a clone of PacketCluster software that runs
-under several operating systems including Linux and Windows. Linux is fast
-becoming the choice for amateur radio stations because of it's flexibility,
-reliability and the lack of the memory limitations of DOS. Linux supports
-multitasking and is also multiuser. It has support for AX25, ROSE,
-NetROM and TCPIP built in, making it the ideal choice for amateur
-radio. It is also totally free!</P>
-<P>DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
-exercise in perl programming. It has developed rapidly and today is a
-very powerful cluster program. It was designed to be totally compatible
-with the AK1A program, although several commands have been extended to
-improve functionality.</P>
-<P>This manual is designed to help you become familiar with the commands
-that DXSpider supports and to help you get the best from the program so
-you can enjoy working that rare DX! As DXSpider is being improved all the
-time, commands will be added as time goes by, so make sure you have
-the most upto date version of this manual. The latest version will
-always be included with the cluster program so if you are unsure, simply
-ask your sysop. The manual will also be available on the wesite.</P>
-
-
-<HR>
-<A HREF="usermanual-2.html">Next</A>
-Previous
-<A HREF="usermanual.html#toc1">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Filtering (From version 1.45)</TITLE>
- <LINK HREF="usermanual-11.html" REL=next>
- <LINK HREF="usermanual-9.html" REL=previous>
- <LINK HREF="usermanual.html#toc10" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-11.html">Next</A>
-<A HREF="usermanual-9.html">Previous</A>
-<A HREF="usermanual.html#toc10">Contents</A>
-<HR>
-<H2><A NAME="s10">10.</A> <A HREF="usermanual.html#toc10">Filtering (From version 1.45)</A></H2>
-
-<H2><A NAME="ss10.1">10.1</A> <A HREF="usermanual.html#toc10.1">General filter rules</A>
-</H2>
-
-<P>Upto v1.44 it was not possible for the user to set their own filters. From
-v1.45 though that has all changed. It is now possible to set filters for just
-about anything you wish. If you have just updated from an older version of
-DXSpider you will need to update your new filters. You do not need to do
-anything with your old filters, they will be renamed as you update.</P>
-
-<P>There are 3 basic commands involved in setting and manipulating filters. These
-are <EM>accept</EM>, <EM>reject</EM> and <EM>clear</EM>. First we will look
-generally at filtering. There are a number of things you can filter in the
-DXSpider system. They all use the same general mechanism.</P>
-
-<P>In general terms you can create a 'reject' or an 'accept' filter which can have
-up to 10 lines in it. You do this using, for example ... </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-accept/spots .....
-reject/spots .....
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>where ..... are the specific commands for that type of filter. There are
-filters for spots, wwv, announce, wcy and (for sysops) connects. See each
-different accept or reject command reference for more details.</P>
-<P>There is also a command to clear out one or more lines in a filter. They are ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>There is clear/xxxx command for each type of filter.</P>
-
-<P>and you can check that your filters have worked by the command ... </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-show/filter
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For now we are going to use spots for the examples, but you can apply the same
-principles to all types of filter.</P>
-
-<H2><A NAME="ss10.2">10.2</A> <A HREF="usermanual.html#toc10.2">Types of filter</A>
-</H2>
-
-<P>There are two main types of filter, <EM>accept</EM> or <EM>reject</EM>. You
-can use either to achieve the result you want dependent on your own preference
-and which is more simple to do. It is pointless writing 8 lines of reject
-filters when 1 accept filter would do the same thing! Each filter has 10
-lines (of any length) which are tried in order. If a line matches then the
-action you have specified is taken (ie reject means ignore it and accept
-means take it)</P>
-
-<P>If you specify reject filters, then any lines that arrive that match the filter
-will be dumped but all else will be accepted. If you use an accept filter,
-then ONLY the lines in the filter will be accepted and all else will be dumped.
-For example if you have a single line <EM>accept</EM> filter ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>then you will <EM>ONLY</EM> get VHF spots <EM>from</EM> or <EM>to</EM> CQ zones
-14, 15 and 16.</P>
-
-<P>If you set a reject filter like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Then you will get everything <EM>EXCEPT</EM> HF CW spots. You could make this
-single filter even more flexible. For example, if you are interested in IOTA
-and will work it even on CW even though normally you are not interested in
-CW, then you could say ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw and not info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>But in that case you might only be interested in iota and say:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots not on hf/cw or info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>which achieves exactly the same thing. You should choose one or the other
-until you are comfortable with the way it works. You can mix them if you
-wish (actually you can have an accept AND a reject on the same line) but
-don't attempt this until you are sure you know what you are doing!</P>
-
-<P>You can arrange your filter lines into logical units, either for your own
-understanding or simply convenience. Here is an example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots 1 on hf/cw
-reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>What this does is to ignore all HF CW spots and also rejects any spots on VHF
-which don't either originate or spot someone in Europe. </P>
-
-<P>This is an example where you would use a line number (1 and 2 in this case), if
-you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
-This make it easier to see just what filters you have set. It also makes it
-more simple to remove individual filters, during a contest for example.</P>
-
-<P>You will notice in the above example that the second line has brackets. Look
-at the line logically. You can see there are 2 separate sections to it. We
-are saying reject spots that are VHF or above <EM>APART</EM> from those in
-zones 14, 15 and 16 (either spotted there or originated there). If you did
-not have the brackets to separate the 2 sections, then Spider would read it
-logically from the front and see a different expression entirely ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The simple way to remember this is, if you use OR - use brackets. Whilst we are
-here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.</P>
-<P>As mentioned earlier, setting several filters can be more flexible than
-simply setting one complex one. Doing it in this way means that if you want
-to alter your filter you can just redefine or remove one or more lines of it or
-one line. For example ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots 1 on hf/ssb
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>would redefine our earlier example, or </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To remove all the filter lines in the spot filter ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss10.3">10.3</A> <A HREF="usermanual.html#toc10.3">Filter options</A>
-</H2>
-
-<P>You can filter in several different ways. The options are listed in the
-various helpfiles for accept, reject and filter.</P>
-
-<H2><A NAME="ss10.4">10.4</A> <A HREF="usermanual.html#toc10.4">Advanced filtering</A>
-</H2>
-
-<P>Once you are happy with the results you get, you may like to experiment. </P>
-
-<P>The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, for example ... </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-rej/spot on hf/cw
-acc/spot on 0/30000
-acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Note that the first filter has not been specified with a number. This
-will automatically be assumed to be number 1. In this case, we have
-said <EM>reject all HF spots in the CW section of the bands but accept
-all others at HF. Also accept anything in VHF and above spotted in or
-by operators in the zones 14, 15 and 16</EM>. Each filter slot actually
-has a 'reject' slot and an 'accept' slot. The reject slot is executed
-BEFORE the accept slot.</P>
-
-<P>It was mentioned earlier that after a reject test that doesn't match, the
-default for following tests is 'accept', the reverse is true for 'accept'.
-In the example what happens is that the reject is executed first, any non
-hf/cw spot is passed to the accept line, which lets through everything
-else on HF. The next filter line lets through just VHF/UHF spots from EU.</P>
-
-
-<HR>
-<A HREF="usermanual-11.html">Next</A>
-<A HREF="usermanual-9.html">Previous</A>
-<A HREF="usermanual.html#toc10">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Hints, tips and common questions.</TITLE>
- <LINK HREF="usermanual-12.html" REL=next>
- <LINK HREF="usermanual-10.html" REL=previous>
- <LINK HREF="usermanual.html#toc11" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-12.html">Next</A>
-<A HREF="usermanual-10.html">Previous</A>
-<A HREF="usermanual.html#toc11">Contents</A>
-<HR>
-<H2><A NAME="s11">11.</A> <A HREF="usermanual.html#toc11">Hints, tips and common questions.</A></H2>
-
-<P><B>Q.</B>These commands seem very long! Can I shorten them?</P>
-<P><B>A.</B>Of course you can and the usual abbreviations work. If you
-are unsure, try it. </P>
-<P><B>Q.</B>I am not sure if this command is correct. Can I cause any
-harm if I try it?</P>
-<P><B>A.</B>Do not be afraid to try a command to see if it will work,
-at the worst you will get an error message. If you require any
-help on a command, just type help followed by the command you
-want help on. Look at the "DXSpider Command Reference" section to see
-what help can be found.</P>
-<P><B>Q.</B>How should I use the announce command?</P>
-<P><B>A.</B>With respect. Use the command by all means, but please
-only use the "full" extension if absolutely necessary. It can
-create a LOT of messages passing between clusters.</P>
-<P><B>Q.</B>I like to be working in the shack while logged into the
-cluster but I can't be looking at the screen all the time. How
-can I be alerted when anything happens?</P>
-<P><B>A.</B>Use the <B>SET/BEEP</B> command. You can find information
-on this in the "DXSpider Command Reference" section.</P>
-<P><B>Q.</B>I got disconnected from the cluster and now I can't log
-back in again. What is wrong?</P>
-<P><B>A.</B>Probably the cluster thinks you are still logged on and
-will not let you reconnect using the same call to prevent loops.
-Try logging on again adding an ssid to your callsign as DXSpider
-treats G0YLM and G0YLM-1 as different users.</P>
-<P><B>Q.</B>How do I know if I have got the latest version of this
-user manual?</P>
-<P><B>A.</B>The latest and greatest will always be on the Website. It will
-also be included with every release of DXSpider. As always, if unsure,
-ask your sysop what version number is the latest. </P>
-
-<HR>
-<A HREF="usermanual-12.html">Next</A>
-<A HREF="usermanual-10.html">Previous</A>
-<A HREF="usermanual.html#toc11">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: The DXSpider command reference</TITLE>
- <LINK HREF="usermanual-11.html" REL=previous>
- <LINK HREF="usermanual.html#toc12" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-<A HREF="usermanual-11.html">Previous</A>
-<A HREF="usermanual.html#toc12">Contents</A>
-<HR>
-<H2><A NAME="s12">12.</A> <A HREF="usermanual.html#toc12">The DXSpider command reference</A></H2>
-
-<P>Below is a complete list of commands available from the cluster prompt.
-These are listed below in alphabetical order. </P>
-
-<H2><A NAME="ss12.1">12.1</A> <A HREF="usermanual.html#toc12.1">accept/announce</A>
-</H2>
-
-<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
-line for announce</CODE></P>
-
-<P>Create an 'accept this announce' line for a filter. </P>
-<P>An accept filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann dest 6MUK
- acc/ann 2 by_zone 14,15,16
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>or</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This filter would only allow announces that were posted buy UK stations.
-You can use the tag 'all' to accept everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss12.2">12.2</A> <A HREF="usermanual.html#toc12.2">accept/spots </A>
-</H2>
-
-<P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE></P>
-
-<P>Create an 'accept this spot' line for a filter.</P>
-
-<P>An accept filter line means that if the spot matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: freq HF (but don't get
-too hung up about that)</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can use the tag 'all' to accept everything, eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 3 all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss12.3">12.3</A> <A HREF="usermanual.html#toc12.3">accept/wcy </A>
-</H2>
-
-<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<P>There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).</P>
-<P>This command is really provided for future use.</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss12.4">12.4</A> <A HREF="usermanual.html#toc12.4">accept/wwv </A>
-</H2>
-
-<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>for example </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wwv by_zone 4
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>is probably the only useful thing to do (which will only show WWV broadcasts
-by stations in the US).</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss12.5">12.5</A> <A HREF="usermanual.html#toc12.5">announce </A>
-</H2>
-
-<P><CODE><B>announce <text></B> Send an announcement to local users</CODE></P>
-
-<P>Send an announcement to LOCAL users only, where <text> is the text
-of the announcement you wish to broadcast</P>
-
-<H2><A NAME="ss12.6">12.6</A> <A HREF="usermanual.html#toc12.6">announce full </A>
-</H2>
-
-<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
-
-<P>This command will send your announcement across the whole cluster
-network.</P>
-
-<H2><A NAME="ss12.7">12.7</A> <A HREF="usermanual.html#toc12.7">apropos </A>
-</H2>
-
-<P><CODE><B>apropos <string></B> Search the help database</CODE></P>
-
-<P>Search the help database for <string> (it isn't case sensitive),
-and print the names of all the commands that may be relevant.</P>
-
-<H2><A NAME="ss12.8">12.8</A> <A HREF="usermanual.html#toc12.8">bye </A>
-</H2>
-
-<P><CODE><B>bye</B> Exit from the cluster</CODE></P>
-
-<P>This will disconnect you from the cluster</P>
-
-<H2><A NAME="ss12.9">12.9</A> <A HREF="usermanual.html#toc12.9">clear/spots </A>
-</H2>
-
-<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE></P>
-
-<P>This command allows you to clear (remove) a line in a spot filter or to
-remove the whole filter.</P>
-<P>If you have a filter:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and you say:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- clear/spot 1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>you will be left with:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If you do:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- clear/spot all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>the filter will be completely removed.</P>
-
-<H2><A NAME="ss12.10">12.10</A> <A HREF="usermanual.html#toc12.10">dbavail </A>
-</H2>
-
-<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE></P>
-
-<P>The title says it all really, this command lists all the databases defined
-in the system. It is also aliased to SHOW/COMMAND.</P>
-
-<H2><A NAME="ss12.11">12.11</A> <A HREF="usermanual.html#toc12.11">dbshow </A>
-</H2>
-
-<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
-
-<P>This is the generic user interface to the database to the database system.
-It is expected that the sysop will add an entry to the local Aliases file
-so that users can use the more familiar AK1A style of enquiry such as:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/BUCK G1TLH
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but if he hasn't and the database really does exist (use DBAVAIL or
-SHOW/COMMAND to find out) you can do the same thing with:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DBSHOW buck G1TLH
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.12">12.12</A> <A HREF="usermanual.html#toc12.12">directory </A>
-</H2>
-
-<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
-<B>directory own</B> List your own messages<BR>
-<B>directory new</B> List all new messages<BR>
-<B>directory to <call></B> List all messages to <call><BR>
-<B>directory from <call></B> List all messages from <call><BR>
-<B>directory subject <string></B> List all messages with <string> in subject<BR>
-<B>directory <nn></B> List last <nn> messages<BR>
-<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE></P>
-
-<P>List the messages in the messages directory.</P>
-<P>If there is a 'p' one space after the message number then it is a
-personal message. If there is a '-' between the message number and the
-'p' then this indicates that the message has been read.</P>
-<P>You can use shell escape characters such as '*' and '?' in the <call>
-fields.</P>
-<P>You can combine some of the various directory commands together eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DIR TO G1TLH 5
-or
- DIR SUBJECT IOTA 200-250
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can abbreviate all the commands to one letter and use ak1a syntax:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DIR/T G1* 10
- DIR/S QSL 10-100 5
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.13">12.13</A> <A HREF="usermanual.html#toc12.13">dx </A>
-</H2>
-
-<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
-
-<P>This is how you send a DX Spot to other users. You can, in fact, now
-enter the <freq> and the <call> either way round. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will all give the same result. You can add some remarks to the end
-of the command and they will be added to the spot.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX FR0G 144600 this is a test
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can credit someone else by saying:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX by G1TLH FR0G 144.600 he isn't on the cluster
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The <freq> is compared against the available bands set up in the
-cluster. See SHOW/BANDS for more information.</P>
-
-<H2><A NAME="ss12.14">12.14</A> <A HREF="usermanual.html#toc12.14">help </A>
-</H2>
-
-<P><CODE><B>help <cmd></B> Get help on a command</CODE></P>
-
-<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
-to SH/DX, ANNOUNCE can be shortened to AN and so on.</P>
-<P>Look at the APROPOS <string> command which will search the help database
-for the <string> you specify and give you a list of likely commands
-to look at with HELP.</P>
-
-<H2><A NAME="ss12.15">12.15</A> <A HREF="usermanual.html#toc12.15">kill </A>
-</H2>
-
-<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE></P>
-
-<P>Delete a message from the local system. You will only be able to
-delete messages that you have originated or been sent (unless you are
-the sysop).</P>
-
-<H2><A NAME="ss12.16">12.16</A> <A HREF="usermanual.html#toc12.16">links </A>
-</H2>
-
-<P><CODE><B>links</B> Show which nodes are physically connected</CODE></P>
-
-<P>This is a quick listing that shows which links are connected and
-some information about them. See WHO for a list of all connections.</P>
-
-<H2><A NAME="ss12.17">12.17</A> <A HREF="usermanual.html#toc12.17">read </A>
-</H2>
-
-<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
-<B>read <msgno></B> Read the specified message<BR></CODE></P>
-
-<P>You can read any messages that are sent as 'non-personal' and also any
-message either sent by or sent to your callsign.</P>
-
-<H2><A NAME="ss12.18">12.18</A> <A HREF="usermanual.html#toc12.18">reject/announce</A>
-</H2>
-
-<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
-for announce</CODE></P>
-
-<P>Create an 'reject this announce' line for a filter. </P>
-<P>An reject filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/ann by_zone 14,15,16 and not by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can use the tag 'all' to reject everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/ann all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss12.19">12.19</A> <A HREF="usermanual.html#toc12.19">reject/spots </A>
-</H2>
-
-<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE></P>
-
-<P>Create a 'reject this spot' line for a filter. </P>
-<P>A reject filter line means that if the spot matches this filter it is
-dumped (not passed on). See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.</P>
-<P>You can use any of the following things in this line:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: on HF (but don't get
-too hung up about that)</P>
-<P>some examples:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/spot 1 on hf
- rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can use the tag 'all' to reject everything eg:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/spot 3 all
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>but this probably for advanced users...</P>
-
-<H2><A NAME="ss12.20">12.20</A> <A HREF="usermanual.html#toc12.20">reject/wcy </A>
-</H2>
-
-<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).</P>
-<P>This command is really provided for future use.</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss12.21">12.21</A> <A HREF="usermanual.html#toc12.21">reject/wwv </A>
-</H2>
-
-<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE></P>
-
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>for example </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/wwv by_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>is probably the only useful thing to do (which will only show WWV broadcasts
-by stations in the US).</P>
-<P>See HELP FILTER for information.</P>
-
-<H2><A NAME="ss12.22">12.22</A> <A HREF="usermanual.html#toc12.22">reply </A>
-</H2>
-
-<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
-<B>reply <msgno></B> Reply (privately) to the specified message<BR>
-<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
-<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
-message<BR>
-<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE></P>
-
-<P>You can reply to a message and the subject will automatically have
-"Re:" inserted in front of it, if it isn't already present.</P>
-<P>You can also use all the extra qualifiers such as RR, PRIVATE,
-NOPRIVATE, B that you can use with the SEND command (see SEND
-for further details)</P>
-
-<H2><A NAME="ss12.23">12.23</A> <A HREF="usermanual.html#toc12.23">send </A>
-</H2>
-
-<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
-<B>send RR <call></B> Send a message and ask for a read receipt<BR>
-<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
-<B>send PRIVATE <call></B> Send a personal message<BR>
-<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE></P>
-
-<P>All the SEND commands will create a message which will be sent either to
-an individual callsign or to one of the 'bulletin' addresses. </P>
-<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
-it will mark the message as personal and send it to the cluster node that
-that callsign is connected to.</P>
-<P>You can have more than one callsign in all of the SEND commands.</P>
-<P>You can have multiple qualifiers so that you can have for example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SEND RR COPY 123 PRIVATE G1TLH G0RDI
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
-receive a read receipt when they have read the message.</P>
-<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
-SP is an alias for SEND PRIVATE</P>
-
-<H2><A NAME="ss12.24">12.24</A> <A HREF="usermanual.html#toc12.24">set/address </A>
-</H2>
-
-<P><CODE><B>set/address <your_address></B> Record your postal address</CODE></P>
-
-<P>Literally, record your address details on the cluster.</P>
-
-<H2><A NAME="ss12.25">12.25</A> <A HREF="usermanual.html#toc12.25">set/announce </A>
-</H2>
-
-<P><CODE><B>set/announce</B> Allow announce messages</CODE></P>
-
-<P>Allow announce messages to arrive at your terminal.</P>
-
-<H2><A NAME="ss12.26">12.26</A> <A HREF="usermanual.html#toc12.26">set/beep </A>
-</H2>
-
-<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE></P>
-
-<P>Add a beep to DX and other terminal messages.</P>
-
-<H2><A NAME="ss12.27">12.27</A> <A HREF="usermanual.html#toc12.27">set/dx </A>
-</H2>
-
-<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE></P>
-
-<P>You can stop DX messages with the <EM>unset/dx</EM> command</P>
-
-<H2><A NAME="ss12.28">12.28</A> <A HREF="usermanual.html#toc12.28">set/dxgrid</A>
-</H2>
-
-<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE></P>
-
-<P>Some logging programs do not like the additional information at
-the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
-command to remove the grid squares.</P>
-
-<H2><A NAME="ss12.29">12.29</A> <A HREF="usermanual.html#toc12.29">set/echo </A>
-</H2>
-
-<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
-
-<P>If you are connected via a telnet session, different implimentations
-of telnet handle echo differently depending on whether you are
-connected via port 23 or some other port. You can use this command
-to change the setting appropriately. </P>
-<P>You can remove the echo with the <EM>unset/echo</EM> command</P>
-<P>The setting is stored in your user profile.</P>
-<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
-
-<H2><A NAME="ss12.30">12.30</A> <A HREF="usermanual.html#toc12.30">set/here</A>
-</H2>
-
-<P><CODE><B>set/here</B> Set the here flag</CODE></P>
-
-<P>Let others on the cluster know you are here by only displaying your
-callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
-command to let people know you are away. This simply puts brackets
-around your callsign to indicate you are not available.</P>
-
-<H2><A NAME="ss12.31">12.31</A> <A HREF="usermanual.html#toc12.31">set/homenode </A>
-</H2>
-
-<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE></P>
-
-<P>Tell the cluster system where you normally connect to. Any Messages sent
-to you will normally find their way there should you not be connected.
-eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/HOMENODE gb7djk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.32">12.32</A> <A HREF="usermanual.html#toc12.32">set/language </A>
-</H2>
-
-<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE></P>
-
-<P>You can select the language that you want the cluster to use. Currently
-the languages available are <EM>en</EM> (English) <EM>sp</EM> (Spanish)
-and <EM>nl</EM> (Dutch).</P>
-
-<H2><A NAME="ss12.33">12.33</A> <A HREF="usermanual.html#toc12.33">set/location </A>
-</H2>
-
-<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE></P>
-
-<P>You can set your latitude and longitude manually or alternatively use the
-<EM>set/qra</EM> command which will do the conversion for you.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/location 54 04 N 2 02 E
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.34">12.34</A> <A HREF="usermanual.html#toc12.34">set/logininfo </A>
-</H2>
-
-<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE></P>
-
-<P>Show users and nodes when they log in and out of the local cluster. You
-can stop these messages by using the <EM>unset/logininfo</EM> command.</P>
-
-<H2><A NAME="ss12.35">12.35</A> <A HREF="usermanual.html#toc12.35">set/name </A>
-</H2>
-
-<P><CODE><B>set/name <your_name></B> Set your name</CODE></P>
-
-<P>Tell the cluster what your name is, eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/name Dirk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.36">12.36</A> <A HREF="usermanual.html#toc12.36">set/page </A>
-</H2>
-
-<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE></P>
-
-<P>Tell the system how many lines you wish on a page when the number of lines
-of output from a command is more than this. The default is 20. Setting it
-explicitly to 0 will disable paging. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/PAGE 30
- SET/PAGE 0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The setting is stored in your user profile.</P>
-
-<H2><A NAME="ss12.37">12.37</A> <A HREF="usermanual.html#toc12.37">set/qra </A>
-</H2>
-
-<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE></P>
-
-<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
-done a SET/LOCATION then your latitude and longitude will be set roughly
-correctly (assuming your locator is correct ;-). For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/QRA JO02LQ
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.38">12.38</A> <A HREF="usermanual.html#toc12.38">set/qth</A>
-</H2>
-
-<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE></P>
-
-<P>Tell the system where your are. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/qth East Dereham, Norfolk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.39">12.39</A> <A HREF="usermanual.html#toc12.39">set/talk</A>
-</H2>
-
-<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE></P>
-
-<P>Allow talk messages to arrive at your console. You can switch off
-talks with the <EM>unset/talk</EM> command.</P>
-
-<H2><A NAME="ss12.40">12.40</A> <A HREF="usermanual.html#toc12.40">set/wcy</A>
-</H2>
-
-<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE></P>
-
-<P>Allow WCY information to be seen at your console. You can switch off
-WCY messages with the <EM>unset/wcy</EM> command.</P>
-
-<H2><A NAME="ss12.41">12.41</A> <A HREF="usermanual.html#toc12.41">set/wwv</A>
-</H2>
-
-<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE></P>
-
-<P>Allow WWV information to be seen at your console. You can switch off
-WWV messages with the <EM>unset/wwv</EM> command.</P>
-
-<H2><A NAME="ss12.42">12.42</A> <A HREF="usermanual.html#toc12.42">set/wx </A>
-</H2>
-
-<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE></P>
-
-<P>Allow WX information to be seen at your console. You can switch off
-WX messages with the <EM>unset/wx</EM> command.</P>
-
-<H2><A NAME="ss12.43">12.43</A> <A HREF="usermanual.html#toc12.43">show/configuration</A>
-</H2>
-
-<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE></P>
-
-<P>This command allows you to see all the users that can be seen
-and the nodes to which they are connected. With the optional <EM>node</EM>,
-you can specify a particular node to look at.</P>
-<P>This command is normally abbreviated to: sh/c</P>
-<P>BE WARNED: the list that is returned can be VERY long</P>
-
-<H2><A NAME="ss12.44">12.44</A> <A HREF="usermanual.html#toc12.44">show/configuration/node</A>
-</H2>
-
-<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE></P>
-
-<P>Show all the nodes connected locally and the nodes they have connected.</P>
-
-
-<H2><A NAME="ss12.45">12.45</A> <A HREF="usermanual.html#toc12.45">show/date </A>
-</H2>
-
-<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
-the local time</CODE></P>
-
-<P>This is very nearly the same as SHOW/TIME, the only difference the format
-of the date string if no arguments are given.</P>
-<P>If no prefixes or callsigns are given then this command returns the local
-time and UTC as the computer has it right now. If you give some prefixes
-then it will show UTC and UTC + the local offset (not including DST) at
-the prefixes or callsigns that you specify.</P>
-
-<H2><A NAME="ss12.46">12.46</A> <A HREF="usermanual.html#toc12.46">show/dx </A>
-</H2>
-
-<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE></P>
-
-<P>If you just type SHOW/DX you will get the last so many spots
-(sysop configurable, but usually 10).</P>
-<P>In addition you can add any number of these options in very nearly
-any order to the basic SHOW/DX command, they are:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-on <band> - eg 160m 20m 2m 23cm 6mm
-on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
-<number> - the number of spots you want
-<from>-<to> - <from> spot no <to> spot no in
- the selected list
-
-<prefix> - for a spotted callsign beginning with <prefix>
-*<suffix> - for a spotted callsign ending in <suffix>
-*<string>* - for a spotted callsign containing <string>
-
-day <number> - starting <number> days ago
-day <from>-<to> - <from> days <to> days ago
-
-info <text> - any spots containing <text> in the info or remarks
-
-by <call> - any spots spotted by <call> (spotter <call>
- is the same).
-
-qsl - this automatically looks for any qsl info on the call
- held in the spot database.
-
-iota [<iota>] - If the iota island number is missing it will
- look for the string iota and anything which looks like
- an iota island number. If you specify then it will look
- for that island.
-
-qra [<locator>] - this will look for the specific locator if
- you specify one or else anything that looks like a locator.
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>e.g. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.47">12.47</A> <A HREF="usermanual.html#toc12.47">show/dxcc </A>
-</H2>
-
-<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
-
-<P>This command takes the <prefix> (which can be a full or partial
-callsign if desired), looks up which internal country number it is
-and then displays all the spots as per SH/DX for that country.</P>
-<P>The options for SHOW/DX also apply to this command.
-e.g. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
- SH/DXCC G
- SH/DXCC W on 20m info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.48">12.48</A> <A HREF="usermanual.html#toc12.48">show/files </A>
-</H2>
-
-<P><CODE><B>show/files [<filearea> [<string>]]</B> List
-the contents of a filearea</CODE></P>
-
-<P>SHOW/FILES on its own will show you a list of the various fileareas
-available on the system. To see the contents of a particular file
-area type:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/FILES <filearea>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>where <filearea> is the name of the filearea you want to see the
-contents of.</P>
-<P>You can also use shell globbing characters like '*' and '?' in a
-string to see a selection of files in a filearea eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/FILES bulletins arld*
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>See also TYPE - to see the contents of a file.</P>
-
-<H2><A NAME="ss12.49">12.49</A> <A HREF="usermanual.html#toc12.49">show/filter </A>
-</H2>
-
-<P><CODE><B>show/filter</B> Show the filters you have set</CODE></P>
-
-<P>Show the contents of all the filters that are set by you. This command
-displays all the filters set - for all the various categories.</P>
-
-<H2><A NAME="ss12.50">12.50</A> <A HREF="usermanual.html#toc12.50">show/moon </A>
-</H2>
-
-<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
-rise and set times</CODE></P>
-
-<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
-together with the azimuth and elevation of the sun currently at those
-locations.</P>
-<P>If you don't specify any prefixes or callsigns, it will show the times for
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
-together with the current azimuth and elevation.</P>
-<P>In addition, it will show the gain or loss dB relative to the nominal
-distance of 385,000Km due to the ellipsoidal nature of the orbit.</P>
-<P>If all else fails it will show the Moonrise and set times for the node
-that you are connected to. </P>
-<P>For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MOON
- SH/MOON G1TLH W5UN
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.51">12.51</A> <A HREF="usermanual.html#toc12.51">show/muf </A>
-</H2>
-
-<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
-the likely propagation to <prefix></CODE></P>
-
-<P>This command allow you to estimate the likelihood of you contacting
-a station with the prefix you have specified. The output assumes a modest
-power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)</P>
-<P>The result predicts the most likely operating frequencies and signal
-levels for high frequency (shortwave) radio propagation paths on
-specified days of the year and hours of the day. It is most useful for
-paths between 250 km and 6000 km, but can be used with reduced accuracy
-for paths shorter or longer than this.</P>
-<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
-used to predict the MUF given the predicted flux, day of the year,
-hour of the day and geographic coordinates of the transmitter and
-receiver. This routine is reasonably accurate for the purposes here,
-with a claimed RMS error of 3.8 MHz, but much smaller and less complex
-than the programs used by major shortwave broadcasting organizations,
-such as the Voice of America.</P>
-<P>The command will display some header information detailing its
-assumptions, together with the locations, latitude and longitudes and
-bearings. It will then show UTC (UT), local time at the other end
-(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
-(Zen) and the likely signal strengths. Then for each frequency for which
-the system thinks there is a likelihood of a circuit it prints a value.</P>
-<P>The value is currently a likely S meter reading based on the conventional
-6dB / S point scale. If the value has a '+' appended it means that it is
-1/2 an S point stronger. If the value is preceeded by an 'm' it means that
-there is likely to be much fading and by an 's' that the signal is likely
-to be noisy. </P>
-<P>By default SHOW/MUF will show the next two hours worth of data. You
-can specify anything up to 24 hours worth of data by appending the no of
-hours required after the prefix. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>produces:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
- Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
- Location Lat / Long Azim
- East Dereham, Norfolk 52 41 N 0 57 E 47
- United-States-W 43 0 N 87 54 W 299
- UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
- 18 23 11.5 -35 mS0+ mS2 S3
- 19 0 11.2 -41 mS0+ mS2 S3
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>indicating that you will have weak, fading circuits on top band and
-80m but usable signals on 40m (about S3).</P>
-<P>inputing:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W 24
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will get you the above display, but with the next 24 hours worth of
-propagation data.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W L 24
- SH/MUF W 24 Long
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Gives you an estimate of the long path propagation characterics. It
-should be noted that the figures will probably not be very useful, nor
-terrible accurate, but it is included for completeness.</P>
-
-<H2><A NAME="ss12.52">12.52</A> <A HREF="usermanual.html#toc12.52">show/prefix </A>
-</H2>
-
-<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE></P>
-
-<P>This command takes the <callsign> (which can be a full or partial
-callsign or a prefix), looks up which internal country number
-it is and then displays all the relevant prefixes for that country
-together with the internal country no, the CQ and ITU regions. </P>
-<P>See also SHOW/DXCC</P>
-
-<H2><A NAME="ss12.53">12.53</A> <A HREF="usermanual.html#toc12.53">show/qra </A>
-</H2>
-
-<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
-between locators<BR>
-<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE></P>
-
-<P>This is a multipurpose command that allows you either to calculate the
-distance and bearing between two locators or (if only one locator is
-given on the command line) the distance and beraing from your station
-to the locator. For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/QRA IO92QL
-SH/QRA JN06 IN73
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The first example will show the distance and bearing to the locator from
-yourself, the second example will calculate the distance and bearing from
-the first locator to the second. You can use 4 or 6 character locators.</P>
-<P>It is also possible to convert a latitude and longitude to a locator by
-using this command with a latitude and longitude as an argument, for
-example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/QRA 52 41 N 0 58 E
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.54">12.54</A> <A HREF="usermanual.html#toc12.54">show/qrz</A>
-</H2>
-
-<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
-
-<P>This command queries the QRZ callbook server on the internet
-and returns any information available for that callsign. This service
-is provided for users of this software by http://www.qrz.com </P>
-
-<H2><A NAME="ss12.55">12.55</A> <A HREF="usermanual.html#toc12.55">show/route </A>
-</H2>
-
-<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE></P>
-
-<P>This command allows you to see to which node the callsigns specified are
-connected. It is a sort of inverse sh/config.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- sh/route n2tly
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.56">12.56</A> <A HREF="usermanual.html#toc12.56">show/satellite </A>
-</H2>
-
-<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
-Show satellite tracking data</CODE></P>
-
-<P>Show the tracking data from your location to the satellite of your choice
-from now on for the next few hours.</P>
-<P>If you use this command without a satellite name it will display a list
-of all the satellites known currently to the system. </P>
-<P>If you give a name then you can obtain tracking data of all the passes
-that start and finish 5 degrees below the horizon. As default it will
-give information for the next three hours for every five minute period.</P>
-<P>You can alter the number of hours and the step size, within certain
-limits. </P>
-<P>Each pass in a period is separated with a row of '-----' characters</P>
-<P>So for example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/SAT AO-10
-SH/SAT FENGYUN1 12 2
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.57">12.57</A> <A HREF="usermanual.html#toc12.57">show/sun </A>
-</H2>
-
-<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
-sun rise and set times</CODE></P>
-
-<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
-together with the azimuth and elevation of the sun currently at those
-locations.</P>
-<P>If you don't specify any prefixes or callsigns, it will show the times for
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
-together with the current azimuth and elevation.</P>
-<P>If all else fails it will show the sunrise and set times for the node
-that you are connected to. </P>
-<P>For example:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/SUN
- SH/SUN G1TLH K9CW ZS
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.58">12.58</A> <A HREF="usermanual.html#toc12.58">show/time </A>
-</H2>
-
-<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
-the local time</CODE></P>
-
-<P>If no prefixes or callsigns are given then this command returns the local
-time and UTC as the computer has it right now. If you give some prefixes
-then it will show UTC and UTC + the local offset (not including DST) at
-the prefixes or callsigns that you specify.</P>
-
-<H2><A NAME="ss12.59">12.59</A> <A HREF="usermanual.html#toc12.59">show/wcy </A>
-</H2>
-
-<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
-<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE></P>
-
-<P>Display the most recent WCY information that has been received by the system</P>
-
-<H2><A NAME="ss12.60">12.60</A> <A HREF="usermanual.html#toc12.60">show/wwv</A>
-</H2>
-
-<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
-<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE></P>
-
-<P>Display the most recent WWV information that has been received by the system</P>
-
-<H2><A NAME="ss12.61">12.61</A> <A HREF="usermanual.html#toc12.61">sysop </A>
-</H2>
-
-<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
-
-<P>The system automatically reduces your privilege level to that of a
-normal user if you login in remotely. This command allows you to
-regain your normal privilege level. It uses the normal system: five
-numbers are returned that are indexes into the character array that is
-your assigned password (see SET/PASSWORD). The indexes start from
-zero.</P>
-<P>You are expected to return a string which contains the characters
-required in the correct order. You may intersperse those characters
-with others to obscure your reply for any watchers. For example (and
-these values are for explanation :-):</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>you type:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>They will all match. If there is no password you will still be offered
-numbers but nothing will happen when you input a string. Any match is
-case sensitive.</P>
-
-<H2><A NAME="ss12.62">12.62</A> <A HREF="usermanual.html#toc12.62">talk </A>
-</H2>
-
-<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
-<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
-<B>talk <callsign> > <node_call> [<text>]</B>
-Send a text message to <callsign> via <node_call></CODE></P>
-
-<P>Send a short message to any other station that is visible on the cluster
-system. You can send it to anyone you can see with a SHOW/CONFIGURATION
-command, they don't have to be connected locally.</P>
-<P>The second form of TALK is used when other cluster nodes are connected
-with restricted information. This usually means that they don't send
-the user information usually associated with logging on and off the cluster.</P>
-<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
-see GB7TLH in the SH/C list but with no users, then you would use the
-second form of the talk message.</P>
-<P>If you want to have a ragchew with someone you can leave the text message
-out and the system will go into 'Talk' mode. What this means is that a
-short message is sent to the recipient telling them that you are in a 'Talking'
-frame of mind and then you just type - everything you send will go to the
-station that you asked for. </P>
-<P>All the usual announcements, spots and so on will still come out on your
-terminal.</P>
-<P>If you want to do something (such as send a spot) you precede the normal
-command with a '/' character, eg:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
- /HELP talk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To leave talk mode type:</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- /EX
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss12.63">12.63</A> <A HREF="usermanual.html#toc12.63">type </A>
-</H2>
-
-<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE></P>
-
-<P>Type out the contents of a file in a filearea. So, for example, in
-filearea 'bulletins' you want to look at file 'arld051' you would
-enter:-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- TYPE bulletins/arld051
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>See also SHOW/FILES to see what fileareas are available and a
-list of content.</P>
-
-<H2><A NAME="ss12.64">12.64</A> <A HREF="usermanual.html#toc12.64">who </A>
-</H2>
-
-<P><CODE><B>who</B> Show who is physically connected locally</CODE></P>
-
-<P>This is a quick listing that shows which callsigns are connected and
-what sort of connection they have</P>
-
-<H2><A NAME="ss12.65">12.65</A> <A HREF="usermanual.html#toc12.65">wx </A>
-</H2>
-
-<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
-<B>wx full <text> </B> Send a weather message to all cluster users</CODE></P>
-
-<P>Weather messages can sometimes be useful if you are experiencing an extreme
-that may indicate enhanced conditions</P>
-
-<HR>
-Next
-<A HREF="usermanual-11.html">Previous</A>
-<A HREF="usermanual.html#toc12">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Logins and logouts.</TITLE>
- <LINK HREF="usermanual-3.html" REL=next>
- <LINK HREF="usermanual-1.html" REL=previous>
- <LINK HREF="usermanual.html#toc2" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-3.html">Next</A>
-<A HREF="usermanual-1.html">Previous</A>
-<A HREF="usermanual.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2.</A> <A HREF="usermanual.html#toc2">Logins and logouts.</A></H2>
-
-<P>You might not think that there is a lot of point of including a
-section on how to log in and out of DXSpider. However, you would be
-suprised at the difficulties some people have in simply getting in
-and out of the cluster!</P>
-<P>There are several ways a login might be achieved, dependant on how
-the sysop has DXSpider configured. It is impossible for me to cover all
-variations but here are the basic ones.</P>
-
-<H2><A NAME="ss2.1">2.1</A> <A HREF="usermanual.html#toc2.1">AX25 logins.</A>
-</H2>
-
-<P>Simplicity itself. The usual <B>CONNECT</B> command will log you straight
-into the cluster and you will not have to do anything else.
-Obviously, you will have to connect to the correct callsign. Some
-nodes use an SSID with their call so you would have to add that.</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-connect GB7MBC
-connect GB7MBC-1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss2.2">2.2</A> <A HREF="usermanual.html#toc2.2">Netrom logins.</A>
-</H2>
-
-<P>There are several possibilities here, dependant on how the sysop has
-configured his system. If you are connecting via netrom then you are
-most probably connecting from another station. Listing the nodes in
-that station with the <B>NODES</B> command will tell you what callsign
-or netrom alias to connect to. Then just issue the connect command
-from there. It is possible that the netrom alias may connect you to
-a node with an alias for the cluster, such as DXC. Just type this
-and you will be connected.</P>
-<P><B>Example:</B>
-<BLOCKQUOTE><CODE>
-<PRE>
-connect MBCDX
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss2.3">2.3</A> <A HREF="usermanual.html#toc2.3">Telnet logins.</A>
-</H2>
-
-<P>With telnet connections, the source callsign is not seen by DXSpider, so
-you will be asked to login with your callsign.
-To telnet to DXSpider, you would connect to a specific port. There is no
-standard at the moment for a cluster telnet port but ask the sysop if
-you are unsure.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-telnet gb7mbc 8000
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>All the above are possible ways of connecting to a DXSpider cluster. You
-may have some or all of these available to you. There may be one or
-two additional ways to connect dependant on the network local to you.
-However I am sure you get the idea.</P>
-
-<H2><A NAME="ss2.4">2.4</A> <A HREF="usermanual.html#toc2.4">Logouts.</A>
-</H2>
-
-<P>Logging out can be done by simply issuing the standard <B>BYE</B>
-command.</P>
-<P>You could also send a disconnect if you are using AX25, or a <B>CLOSE</B>
-command if you are connected via telnet.
-If you do not log out gracefully using one of the above commands,
-you may find you are unable to get a full connect next time. This
-may also happen if a netrom connection drops. You may get connected,
-but nothing else will happen because the program thinks you are still
-connected and will not let you connect twice under the same call.
-However you could reconnect by adding a number to the end of your call,
-for example G0YLM-2.
-This can be done by either altering your MYCALL setting in the TNC or
-by altering your program configuration. </P>
-
-
-<HR>
-<A HREF="usermanual-3.html">Next</A>
-<A HREF="usermanual-1.html">Previous</A>
-<A HREF="usermanual.html#toc2">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Setting your personal details.</TITLE>
- <LINK HREF="usermanual-4.html" REL=next>
- <LINK HREF="usermanual-2.html" REL=previous>
- <LINK HREF="usermanual.html#toc3" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-4.html">Next</A>
-<A HREF="usermanual-2.html">Previous</A>
-<A HREF="usermanual.html#toc3">Contents</A>
-<HR>
-<H2><A NAME="s3">3.</A> <A HREF="usermanual.html#toc3">Setting your personal details.</A></H2>
-
-<P>Once logged in to the cluster, you should set your details so that
-anybody who wishes to contact you can find out who and where you are.
-There are four items to set, your name, qth, location and home node.
-Setting these details also allows the use of the SHOW/HEADING and
-SHOW/SUN commands from within the cluster. Unless you set your QTH
-and location, these commands cannot function.
-Once you have set your name, DXSpider will greet you with it next time
-you login. Your QTH setting is where you live and it is a good idea
-to add your locator to this as the location setting is converted to
-latitude and longitude once inputted. You can actually set your location
-in latitude/longitude or as a locator. Setting your home node will
-tell the program where you wish mail to be sent to you.</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/name Ian
-set/qth Morecambe, Lancashire IO84NB
-set/location 48 34 n 12 12 e
-set/qra IO84NB
-set/home gb7mbc
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<HR>
-<A HREF="usermanual-4.html">Next</A>
-<A HREF="usermanual-2.html">Previous</A>
-<A HREF="usermanual.html#toc3">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Getting and posting DX.</TITLE>
- <LINK HREF="usermanual-5.html" REL=next>
- <LINK HREF="usermanual-3.html" REL=previous>
- <LINK HREF="usermanual.html#toc4" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-5.html">Next</A>
-<A HREF="usermanual-3.html">Previous</A>
-<A HREF="usermanual.html#toc4">Contents</A>
-<HR>
-<H2><A NAME="s4">4.</A> <A HREF="usermanual.html#toc4">Getting and posting DX.</A></H2>
-
-<P>When all is said and done, this is the main function of a DX cluster.
-In its simplest form you can just connect to the node and you will
-start to receive DX spots almost immediately! You can check on
-recent postings in either a general manner or on a particular band or
-mode. You can even check DX by callsign or a fragment of a callsign.
-Of course, once you get the hang of things, it is expected that you
-start posting some yourself! After all, there would be no clusters
-if people did not post DX and you get the added thrill of the hunt!</P>
-
-<H2><A NAME="ss4.1">4.1</A> <A HREF="usermanual.html#toc4.1">Receiving DX.</A>
-</H2>
-
-<P>As we have already said, it is possible just to connect to the
-cluster and you will receive spots automatically. However, you may
-wish to check on spots just posted. Maybe you wish to see if a
-particular band is open or if a certain callsign is active, perhaps a
-DXpedition. The command to do this is <B>SHOW/DX</B>. Without any
-other arguments, this command will output the last 10 spots
-posted. It is possible to look at more than this, for example the
-last 20 or 50 spots, by adding the number to the command. You can
-make it even more specific by adding a band in either wavelength or
-frequency, and/or any additional information such as QSL details.</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/dx
-show/dx 5
-show/dx 20
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will show the last 10, 5 and 20 spots received by the cluster
-respectively.</P>
-<P><B>Examples</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/dx on 20m
-show/dx 10 on 20m
-show/dx 20 on 20m
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will show the last 5, 10 or 20 spots on 20 metres only.</P>
-<P>It is also possible to check for certain callsigns, or fragments of
-callsigns in the same way.</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/dx g0vgs
-show/dx 10 g0vgs
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>would show the last 5 or 10 dx spots containing the callsign g0vgs.</P>
-
-<P>You can check for DX by offset and also by specifying a comment to
-search for.</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/dx 30-40
-show/dx 14000-14033
-show/dx iota
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>would show the spots that arrived between 30 and 40 spots ago and any
-spots with the word <EM>iota</EM> in the comment field. The case of
-the comment is not important.</P>
-<P>Checking DX posted on a certain day is possible too. All you have
-to do here is to specify how many days ago it was like this ...</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/dx day 30
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>It is of course possible to specify multiple arguments.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/dx 20 prefix 9a on vhf day 30
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This would show the last 20 spots posted by or about calls with the prefix
-9a on vhf 30 days ago.</P>
-<P>As you can see the <B>SHOW/DX</B> command is very flexible, so if you are
-not sure whether something will work or not, try it and see! More
-information can be found in the Command Set section.</P>
-
-<H2><A NAME="ss4.2">4.2</A> <A HREF="usermanual.html#toc4.2">Posting DX.</A>
-</H2>
-
-<P>To post DX you use the <B>DX</B> command. The syntax is shown below. </P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dx (frequency) (callsign) (remarks)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Where frequency is in kilohertz and the callsign is the callsign of
-the station you have worked or heard, (ie not your own callsign!).
-The remarks section allows you to add information like the operators
-name or perhaps a location. Actually DXSpider will allow the frequency
-and callsign fields to be entered in any order.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dx 14004 pa3ezl OP Aurelio 599
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>In fact, all the following will give the same result...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dx 14004 pa3ezl OP Aurelio 599
-dx pa3ezl 14004 OP Aurelio 599
-dx pa3ezl 14.004 OP Aurelio 599
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This posting, or callout as it is known, will be forwarded to all
-other connected stations both at the cluster you are connected to and
-other active clusters in the network. The callout will also be sent
-to you as proof of receipt. </P>
-
-<HR>
-<A HREF="usermanual-5.html">Next</A>
-<A HREF="usermanual-3.html">Previous</A>
-<A HREF="usermanual.html#toc4">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Headings and propagation</TITLE>
- <LINK HREF="usermanual-6.html" REL=next>
- <LINK HREF="usermanual-4.html" REL=previous>
- <LINK HREF="usermanual.html#toc5" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-6.html">Next</A>
-<A HREF="usermanual-4.html">Previous</A>
-<A HREF="usermanual.html#toc5">Contents</A>
-<HR>
-<H2><A NAME="s5">5.</A> <A HREF="usermanual.html#toc5">Headings and propagation</A></H2>
-
-<P>There are three commands in DXSpider to help you get the best DX possible.
-These are <B>SHOW/SUN</B>, <B>SHOW/MOON</B> and
-<B>SHOW/HEADING</B>. These commands will only work for you if you
-have entered your personal details. They use your entered location as
-a reference, so if you have not entered it or have entered it incorrectly
-they will not return the correct information.</P>
-
-<H2><A NAME="ss5.1">5.1</A> <A HREF="usermanual.html#toc5.1">Sun</A>
-</H2>
-
-<P>The <B>SHOW/SUN</B> command can be used in three different ways. It
-can be used to show sunrise and sunset times for your own station, a
-particular callsign or a prefix. </P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/sun
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The output from this would look something like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/sun
-Location Rise Set Azim Elev
-G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/sun 5b4
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>would look like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/sun 5b4
-Location Rise Set Azim Elev
-5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can also specify multiple arguments like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/sun gw4veq 5b4ab zs
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>and then the output would look like this ...</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/sun gw4veq 5b4ab zs
-Location Rise Set Azim Elev
-GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
-5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
-ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
-ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
-ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss5.2">5.2</A> <A HREF="usermanual.html#toc5.2">Moon</A>
-</H2>
-
-<P>The <B>SHOW/MOON</B> command works in the same way as the
-<B>SHOW/SUN</B> command. This program however, calculates the
-rise and set times of the moon for a prefix or callsign, together
-with the current azimuth and elevation of the sun at these
-locations.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/moon ea
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The output from this command would look like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/moon ea
-Location Rise Set Azim Elev RGain dB
-EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You can see that the output is similar to the <B>SHOW/SUN</B>
-command, with slightly different fields.</P>
-
-<H2><A NAME="ss5.3">5.3</A> <A HREF="usermanual.html#toc5.3">Heading</A>
-</H2>
-
-<P>The <B>SHOW/HEADING</B> command works in the same way as the
-<B>SHOW/SUN</B> and <B>SHOW/MOON</B> commands but outputs beam
-headings for a specified callsign or prefix. Reciprocal beam headings
-are also calculated.</P>
-<P><B>Example</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/heading zl
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The output from this command would look like this ..</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/heading zl
-ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
-ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
-ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
-ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<HR>
-<A HREF="usermanual-6.html">Next</A>
-<A HREF="usermanual-4.html">Previous</A>
-<A HREF="usermanual.html#toc5">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Announcements.</TITLE>
- <LINK HREF="usermanual-7.html" REL=next>
- <LINK HREF="usermanual-5.html" REL=previous>
- <LINK HREF="usermanual.html#toc6" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-7.html">Next</A>
-<A HREF="usermanual-5.html">Previous</A>
-<A HREF="usermanual.html#toc6">Contents</A>
-<HR>
-<H2><A NAME="s6">6.</A> <A HREF="usermanual.html#toc6">Announcements.</A></H2>
-
-<H2><A NAME="ss6.1">6.1</A> <A HREF="usermanual.html#toc6.1">Making announcements.</A>
-</H2>
-
-<P>Occasionally, you may wish to post something that does not fall into
-the normal parameters for a DX callout. You may wish to tell
-everybody connected that 10 FM is open for example, or ask if anyone
-knows the QSL manager for a certain callsign etc. You can do this
-using the <B>ANNOUNCE</B> command.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-announce 10 FM is open in IO84NB to europe.
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>That would let everyone know locally that this was the case, however
-it would not be forwarded to other nodes connected. To send
-announcements to other connected nodes as well, you would use the
-<B>FULL</B> extension.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-announce full Anyone seen EA7WA today?
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Be cautious in your use of announce full. There are many other tools
-available to get the information you require and the judicious use of
-this command is frowned upon as it creates a great deal of traffic
-across the network.</P>
-
-<H2><A NAME="ss6.2">6.2</A> <A HREF="usermanual.html#toc6.2">Listing announcements.</A>
-</H2>
-
-<P>You can list previous announcements in the standard format with the
-<B>SHOW</B> command. As before you can list just the last 5 or as
-many as you wish.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/announcements
-show/announcements 10
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<HR>
-<A HREF="usermanual-7.html">Next</A>
-<A HREF="usermanual-5.html">Previous</A>
-<A HREF="usermanual.html#toc6">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Nodes and users.</TITLE>
- <LINK HREF="usermanual-8.html" REL=next>
- <LINK HREF="usermanual-6.html" REL=previous>
- <LINK HREF="usermanual.html#toc7" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-8.html">Next</A>
-<A HREF="usermanual-6.html">Previous</A>
-<A HREF="usermanual.html#toc7">Contents</A>
-<HR>
-<H2><A NAME="s7">7.</A> <A HREF="usermanual.html#toc7">Nodes and users.</A></H2>
-
-<P>You can check which nodes are connected in the network, who is
-logged on locally, who is logged on at all the nodes or even
-just one node in particular. This is handy if you wish to see whether
-a friend is connected at the node they use. To see who is connected
-to the nodes, the <B>SHOW/CONFIGURATION</B> command is used.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/configuration
-show/configuration/nodes
-show/configuration (node_call)
-show/configuration (prefix)
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The first of our three examples would output something like this,</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/c
-Node Callsigns
-EI5TCR (7 users)
-GB7ADX
-GB7BAA G4FPV G8TIC
-GB7BIG (GD0TEP) GD3UMW
-GB7BPQ (G0INA) G0RCI G3AKU G3OCA
-(GB7CDX) G3JNB G4ALR
-GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
- G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
- ON7WP
-GB7DXA G0RDI G8SJP
-GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
- G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
-GB7DXE G1NNB
-(GB7DXG) GU6EFB GU7DHI
-GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
- G4XQY G7GAN
-GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
- M0BCT M1EMF
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>You will notice that EI5TCR is showing only that it has 7 users and not
-giving the actual callsigns. This means that this node is on a limited
-protocol of some kind, probably because of a contest situation where
-slow radio links can block up and fail if too much information is sent
-between nodes.</P>
-<P>The second example would just show the nodes connected in the
-network, like this,</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/c/n
-Node Callsigns
-GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
- GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
- GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
- GB7YDX KL7G N2TLY (ON0DXK)
-GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
-GB7MBC
-PA4AB-14 PA4AB-14
-PI4TUE-8 PI4TUE-8
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>If we insert the node_call pi4tue-8 into the third example, then
-this would be the output,</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Node Callsigns
-PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
- F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
- ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
- PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
- YT1XX
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>As you can see, only the users of the requested node are shown.</P>
-<P>You can also use a prefix to show only a group of nodes. For example
-you may only wish to see who is connected to the nodes in the UK. To
-do this simply use a prefix like this ...</P>
-<P>
-<PRE>
-show/configuration gb7
-</PRE>
-</P>
-<P>To show the locally connected users, the <B>SHOW/USERS</B> command is
-used</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/users
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The output of this command would look like this,</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Callsigns connected to GB7MBC
-G0JHC G0NEI G0VGS G0VGS-2 G0YLM
-G3JAG G3OWO G3UEU
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<HR>
-<A HREF="usermanual-8.html">Next</A>
-<A HREF="usermanual-6.html">Previous</A>
-<A HREF="usermanual.html#toc7">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Talk mode.</TITLE>
- <LINK HREF="usermanual-9.html" REL=next>
- <LINK HREF="usermanual-7.html" REL=previous>
- <LINK HREF="usermanual.html#toc8" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-9.html">Next</A>
-<A HREF="usermanual-7.html">Previous</A>
-<A HREF="usermanual.html#toc8">Contents</A>
-<HR>
-<H2><A NAME="s8">8.</A> <A HREF="usermanual.html#toc8">Talk mode.</A></H2>
-
-<P>You can send a single comment or start a dedicated talk session to
-another user by using the <B>TALK</B> command. </P>
-
-<P>Talk mode is used to send a one line comment or greeting to a
-specific user connected either at your node or another in the
-network. You can also enter into a dedicated talk session with
-another user. Talks will be automatically forwarded to other nodes
-if the station you are talking to is not connected locally.
-You can find out who is connected by using the
-<B>SHOW/CONFIGURATION</B> command, (described earlier).</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-talk g0rdi Having a good day Iain?
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>This example would send the line "Having a good day Iain?" to the
-user g0rdi but would leave you in normal mode. </P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-talk g0rdi
-Entering Talkmode, /EX to end, /<cmd> to run a command
-Talk (G0RDI)>
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>As you can see, you can still run commands whilst in talk mode.
-Simply prefix the command with a / like /sh/dx and you will get
-the expected output.
-If the user is connected to another node, you may have to use a
-slightly extended version of the <B>TALK</B> command.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-talk g0rdi > gb7djk
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>To exit talk mode, you issue the command <B>/ex</B>. </P>
-<P>Whilst in talk mode you will still receive DX spots. This means that
-you can chat to a friend whilst working DX. </P>
-
-<HR>
-<A HREF="usermanual-9.html">Next</A>
-<A HREF="usermanual-7.html">Previous</A>
-<A HREF="usermanual.html#toc8">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50: Mail.</TITLE>
- <LINK HREF="usermanual-10.html" REL=next>
- <LINK HREF="usermanual-8.html" REL=previous>
- <LINK HREF="usermanual.html#toc9" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-10.html">Next</A>
-<A HREF="usermanual-8.html">Previous</A>
-<A HREF="usermanual.html#toc9">Contents</A>
-<HR>
-<H2><A NAME="s9">9.</A> <A HREF="usermanual.html#toc9">Mail.</A></H2>
-
-<P>You can send and receive both personal mail and bulletins with DXSpider
-quite easily.</P>
-
-<H2><A NAME="ss9.1">9.1</A> <A HREF="usermanual.html#toc9.1">The "directory" command.</A>
-</H2>
-
-<P>To list mail you would use the <B>DIRECTORY</B> command. On its
-own, this command will output the last ten messages received by the
-node, either to or from yourself or bulletins such as "DX" and "ALL".
-As with other commands you can display more by specifying a number
-with the command. You should be aware that Spider will accept
-these commands by separating with either a slash or a space, so
-<EM>dir new</EM> and <EM>dir/new</EM> work in the same way.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-directory
-directory/20
-directory 20
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>Of course most of the time you will only want to list new mail sent
-to you personally since your last login. However you might also like
-to check for general mail received by the node. In fact if there is
-new mail for you, the cluster will tell you when you login. You will
-also be informed if new mail arrives for you during the time you are
-logged in.
-Mail is not only sent to callsigns though. Mail can also be sent to
-subjects like "all" or "local" or "dx" etc. You can treat these
-bulletins in the same way as personal mail with the directory
-command.</P>
-<P><B>Examples:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-directory/new
-directory/own
-directory/own/10
-directory/all
-directory/from <call>
-</PRE>
-</CODE></BLOCKQUOTE>
- </P>
-<P>The last option will only show mail from a callsign if it was sent to
-you personally or was sent as a bulletin. There are some additional
-commands and these can be found in the DXSpider Command Reference section.</P>
-
-<H2><A NAME="ss9.2">9.2</A> <A HREF="usermanual.html#toc9.2">Reading mail.</A>
-</H2>
-
-<P>The output of the <B>DIRECTORY</B> command could be something like
-this.</P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dir
- 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
- 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
- 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
- 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
- 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
- 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
- 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
- 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
- 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
- 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
- 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>The first column is the actual message number. If the message is a
-personal one to you, you will see a letter 'p' after this number. If
-the message has been read, there will be a '-' between the message
-number and the 'p'. This only works for personal messages. The next
-column shows the file size of the message. The third column shows the
-address the message was sent to and the next column shows who sent it.
-The rest is fairly self-explanatory.</P>
-<P>Reading a message is as simple as typing read, followed by the
-message number that you wish to read.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-read 25
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>will read message number 25. However the mail will be displayed in it's
-entirety unless you specify a page length. You can set your page length
-to any number you like and when the message reaches that number of lines
-you will get a prompt giving you options.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/page 20
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-
-<H2><A NAME="ss9.3">9.3</A> <A HREF="usermanual.html#toc9.3">Sending mail.</A>
-</H2>
-
-<P>Sending mail is done in the time honoured way. First you specify
-a recipient for the message, then you will be prompted for a subject.
-Once you have done this you will be asked to type your message.
-Please remember that there is no automatic word wrap, so unless you
-are using a client that wraps lines automatically, remember to hit
-return at the end of each line.</P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-send m0azm
-Enter Subject (30 characters):
-See you Thursday
-Enter Message /EX to send or /ABORT to exit
-Hi Ian,
-Just a quick note to say that I can make Thursday after all. The
-appointment I had has cancelled so we are go!
-Cheers
-Ian
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-<P>At this point you can either hit return and enter /ex to send the
-message or use /abort at any time to abort it. You can now display
-the message in the normal way. There are several send options and
-these are listed in the Command Set section. These include sending
-mail to several recipients and asking for a return receipt.</P>
-
-
-<H2><A NAME="ss9.4">9.4</A> <A HREF="usermanual.html#toc9.4">Replying to mail.</A>
-</H2>
-
-<P>If mail is addressed to you or to a bulletin address, you can use the
-<B>REPLY</B> command to reply to it. Using this command, the
-subject will be automatically set for you as "Re: subject", whatever
-the subject was. </P>
-<P><B>Example:</B></P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reply 2500
-</PRE>
-</CODE></BLOCKQUOTE>
-</P>
-
-<H2><A NAME="ss9.5">9.5</A> <A HREF="usermanual.html#toc9.5">Deleting mail</A>
-</H2>
-
-<P>To delete a message, you use the <EM>delete</EM> command.
-You can only delete messages sent to or received by yourself.
-Bulletins are dealt with automatically or by the sysop.</P>
-
-<HR>
-<A HREF="usermanual-10.html">Next</A>
-<A HREF="usermanual-8.html">Previous</A>
-<A HREF="usermanual.html#toc9">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
- <TITLE>The DXSpider User Manual v1.50</TITLE>
- <LINK HREF="usermanual-1.html" REL=next>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="usermanual-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>The DXSpider User Manual v1.50</H1>
-
-<H2>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>September 2002 revision 0.1
-<HR>
-<EM>A complete reference for users of the DXSpider DXCluster program.</EM>
-<HR>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="usermanual-1.html">Introduction</A></H2>
-
-<UL>
-<LI><A NAME="toc1.1">1.1</A> <A HREF="usermanual-1.html#ss1.1">What is a DX Cluster?</A>
-<LI><A NAME="toc1.2">1.2</A> <A HREF="usermanual-1.html#ss1.2">So what is DXSpider?</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="usermanual-2.html">Logins and logouts.</A></H2>
-
-<UL>
-<LI><A NAME="toc2.1">2.1</A> <A HREF="usermanual-2.html#ss2.1">AX25 logins.</A>
-<LI><A NAME="toc2.2">2.2</A> <A HREF="usermanual-2.html#ss2.2">Netrom logins.</A>
-<LI><A NAME="toc2.3">2.3</A> <A HREF="usermanual-2.html#ss2.3">Telnet logins.</A>
-<LI><A NAME="toc2.4">2.4</A> <A HREF="usermanual-2.html#ss2.4">Logouts.</A>
-</UL>
-<P>
-<H2><A NAME="toc3">3.</A> <A HREF="usermanual-3.html">Setting your personal details.</A></H2>
-
-<P>
-<H2><A NAME="toc4">4.</A> <A HREF="usermanual-4.html">Getting and posting DX.</A></H2>
-
-<UL>
-<LI><A NAME="toc4.1">4.1</A> <A HREF="usermanual-4.html#ss4.1">Receiving DX.</A>
-<LI><A NAME="toc4.2">4.2</A> <A HREF="usermanual-4.html#ss4.2">Posting DX.</A>
-</UL>
-<P>
-<H2><A NAME="toc5">5.</A> <A HREF="usermanual-5.html">Headings and propagation</A></H2>
-
-<UL>
-<LI><A NAME="toc5.1">5.1</A> <A HREF="usermanual-5.html#ss5.1">Sun</A>
-<LI><A NAME="toc5.2">5.2</A> <A HREF="usermanual-5.html#ss5.2">Moon</A>
-<LI><A NAME="toc5.3">5.3</A> <A HREF="usermanual-5.html#ss5.3">Heading</A>
-</UL>
-<P>
-<H2><A NAME="toc6">6.</A> <A HREF="usermanual-6.html">Announcements.</A></H2>
-
-<UL>
-<LI><A NAME="toc6.1">6.1</A> <A HREF="usermanual-6.html#ss6.1">Making announcements.</A>
-<LI><A NAME="toc6.2">6.2</A> <A HREF="usermanual-6.html#ss6.2">Listing announcements.</A>
-</UL>
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="usermanual-7.html">Nodes and users.</A></H2>
-
-<P>
-<H2><A NAME="toc8">8.</A> <A HREF="usermanual-8.html">Talk mode.</A></H2>
-
-<P>
-<H2><A NAME="toc9">9.</A> <A HREF="usermanual-9.html">Mail.</A></H2>
-
-<UL>
-<LI><A NAME="toc9.1">9.1</A> <A HREF="usermanual-9.html#ss9.1">The "directory" command.</A>
-<LI><A NAME="toc9.2">9.2</A> <A HREF="usermanual-9.html#ss9.2">Reading mail.</A>
-<LI><A NAME="toc9.3">9.3</A> <A HREF="usermanual-9.html#ss9.3">Sending mail.</A>
-<LI><A NAME="toc9.4">9.4</A> <A HREF="usermanual-9.html#ss9.4">Replying to mail.</A>
-<LI><A NAME="toc9.5">9.5</A> <A HREF="usermanual-9.html#ss9.5">Deleting mail</A>
-</UL>
-<P>
-<H2><A NAME="toc10">10.</A> <A HREF="usermanual-10.html">Filtering (From version 1.45)</A></H2>
-
-<UL>
-<LI><A NAME="toc10.1">10.1</A> <A HREF="usermanual-10.html#ss10.1">General filter rules</A>
-<LI><A NAME="toc10.2">10.2</A> <A HREF="usermanual-10.html#ss10.2">Types of filter</A>
-<LI><A NAME="toc10.3">10.3</A> <A HREF="usermanual-10.html#ss10.3">Filter options</A>
-<LI><A NAME="toc10.4">10.4</A> <A HREF="usermanual-10.html#ss10.4">Advanced filtering</A>
-</UL>
-<P>
-<H2><A NAME="toc11">11.</A> <A HREF="usermanual-11.html">Hints, tips and common questions.</A></H2>
-
-<P>
-<H2><A NAME="toc12">12.</A> <A HREF="usermanual-12.html">The DXSpider command reference</A></H2>
-
-<UL>
-<LI><A NAME="toc12.1">12.1</A> <A HREF="usermanual-12.html#ss12.1">accept/announce</A>
-<LI><A NAME="toc12.2">12.2</A> <A HREF="usermanual-12.html#ss12.2">accept/spots </A>
-<LI><A NAME="toc12.3">12.3</A> <A HREF="usermanual-12.html#ss12.3">accept/wcy </A>
-<LI><A NAME="toc12.4">12.4</A> <A HREF="usermanual-12.html#ss12.4">accept/wwv </A>
-<LI><A NAME="toc12.5">12.5</A> <A HREF="usermanual-12.html#ss12.5">announce </A>
-<LI><A NAME="toc12.6">12.6</A> <A HREF="usermanual-12.html#ss12.6">announce full </A>
-<LI><A NAME="toc12.7">12.7</A> <A HREF="usermanual-12.html#ss12.7">apropos </A>
-<LI><A NAME="toc12.8">12.8</A> <A HREF="usermanual-12.html#ss12.8">bye </A>
-<LI><A NAME="toc12.9">12.9</A> <A HREF="usermanual-12.html#ss12.9">clear/spots </A>
-<LI><A NAME="toc12.10">12.10</A> <A HREF="usermanual-12.html#ss12.10">dbavail </A>
-<LI><A NAME="toc12.11">12.11</A> <A HREF="usermanual-12.html#ss12.11">dbshow </A>
-<LI><A NAME="toc12.12">12.12</A> <A HREF="usermanual-12.html#ss12.12">directory </A>
-<LI><A NAME="toc12.13">12.13</A> <A HREF="usermanual-12.html#ss12.13">dx </A>
-<LI><A NAME="toc12.14">12.14</A> <A HREF="usermanual-12.html#ss12.14">help </A>
-<LI><A NAME="toc12.15">12.15</A> <A HREF="usermanual-12.html#ss12.15">kill </A>
-<LI><A NAME="toc12.16">12.16</A> <A HREF="usermanual-12.html#ss12.16">links </A>
-<LI><A NAME="toc12.17">12.17</A> <A HREF="usermanual-12.html#ss12.17">read </A>
-<LI><A NAME="toc12.18">12.18</A> <A HREF="usermanual-12.html#ss12.18">reject/announce</A>
-<LI><A NAME="toc12.19">12.19</A> <A HREF="usermanual-12.html#ss12.19">reject/spots </A>
-<LI><A NAME="toc12.20">12.20</A> <A HREF="usermanual-12.html#ss12.20">reject/wcy </A>
-<LI><A NAME="toc12.21">12.21</A> <A HREF="usermanual-12.html#ss12.21">reject/wwv </A>
-<LI><A NAME="toc12.22">12.22</A> <A HREF="usermanual-12.html#ss12.22">reply </A>
-<LI><A NAME="toc12.23">12.23</A> <A HREF="usermanual-12.html#ss12.23">send </A>
-<LI><A NAME="toc12.24">12.24</A> <A HREF="usermanual-12.html#ss12.24">set/address </A>
-<LI><A NAME="toc12.25">12.25</A> <A HREF="usermanual-12.html#ss12.25">set/announce </A>
-<LI><A NAME="toc12.26">12.26</A> <A HREF="usermanual-12.html#ss12.26">set/beep </A>
-<LI><A NAME="toc12.27">12.27</A> <A HREF="usermanual-12.html#ss12.27">set/dx </A>
-<LI><A NAME="toc12.28">12.28</A> <A HREF="usermanual-12.html#ss12.28">set/dxgrid</A>
-<LI><A NAME="toc12.29">12.29</A> <A HREF="usermanual-12.html#ss12.29">set/echo </A>
-<LI><A NAME="toc12.30">12.30</A> <A HREF="usermanual-12.html#ss12.30">set/here</A>
-<LI><A NAME="toc12.31">12.31</A> <A HREF="usermanual-12.html#ss12.31">set/homenode </A>
-<LI><A NAME="toc12.32">12.32</A> <A HREF="usermanual-12.html#ss12.32">set/language </A>
-<LI><A NAME="toc12.33">12.33</A> <A HREF="usermanual-12.html#ss12.33">set/location </A>
-<LI><A NAME="toc12.34">12.34</A> <A HREF="usermanual-12.html#ss12.34">set/logininfo </A>
-<LI><A NAME="toc12.35">12.35</A> <A HREF="usermanual-12.html#ss12.35">set/name </A>
-<LI><A NAME="toc12.36">12.36</A> <A HREF="usermanual-12.html#ss12.36">set/page </A>
-<LI><A NAME="toc12.37">12.37</A> <A HREF="usermanual-12.html#ss12.37">set/qra </A>
-<LI><A NAME="toc12.38">12.38</A> <A HREF="usermanual-12.html#ss12.38">set/qth</A>
-<LI><A NAME="toc12.39">12.39</A> <A HREF="usermanual-12.html#ss12.39">set/talk</A>
-<LI><A NAME="toc12.40">12.40</A> <A HREF="usermanual-12.html#ss12.40">set/wcy</A>
-<LI><A NAME="toc12.41">12.41</A> <A HREF="usermanual-12.html#ss12.41">set/wwv</A>
-<LI><A NAME="toc12.42">12.42</A> <A HREF="usermanual-12.html#ss12.42">set/wx </A>
-<LI><A NAME="toc12.43">12.43</A> <A HREF="usermanual-12.html#ss12.43">show/configuration</A>
-<LI><A NAME="toc12.44">12.44</A> <A HREF="usermanual-12.html#ss12.44">show/configuration/node</A>
-<LI><A NAME="toc12.45">12.45</A> <A HREF="usermanual-12.html#ss12.45">show/date </A>
-<LI><A NAME="toc12.46">12.46</A> <A HREF="usermanual-12.html#ss12.46">show/dx </A>
-<LI><A NAME="toc12.47">12.47</A> <A HREF="usermanual-12.html#ss12.47">show/dxcc </A>
-<LI><A NAME="toc12.48">12.48</A> <A HREF="usermanual-12.html#ss12.48">show/files </A>
-<LI><A NAME="toc12.49">12.49</A> <A HREF="usermanual-12.html#ss12.49">show/filter </A>
-<LI><A NAME="toc12.50">12.50</A> <A HREF="usermanual-12.html#ss12.50">show/moon </A>
-<LI><A NAME="toc12.51">12.51</A> <A HREF="usermanual-12.html#ss12.51">show/muf </A>
-<LI><A NAME="toc12.52">12.52</A> <A HREF="usermanual-12.html#ss12.52">show/prefix </A>
-<LI><A NAME="toc12.53">12.53</A> <A HREF="usermanual-12.html#ss12.53">show/qra </A>
-<LI><A NAME="toc12.54">12.54</A> <A HREF="usermanual-12.html#ss12.54">show/qrz</A>
-<LI><A NAME="toc12.55">12.55</A> <A HREF="usermanual-12.html#ss12.55">show/route </A>
-<LI><A NAME="toc12.56">12.56</A> <A HREF="usermanual-12.html#ss12.56">show/satellite </A>
-<LI><A NAME="toc12.57">12.57</A> <A HREF="usermanual-12.html#ss12.57">show/sun </A>
-<LI><A NAME="toc12.58">12.58</A> <A HREF="usermanual-12.html#ss12.58">show/time </A>
-<LI><A NAME="toc12.59">12.59</A> <A HREF="usermanual-12.html#ss12.59">show/wcy </A>
-<LI><A NAME="toc12.60">12.60</A> <A HREF="usermanual-12.html#ss12.60">show/wwv</A>
-<LI><A NAME="toc12.61">12.61</A> <A HREF="usermanual-12.html#ss12.61">sysop </A>
-<LI><A NAME="toc12.62">12.62</A> <A HREF="usermanual-12.html#ss12.62">talk </A>
-<LI><A NAME="toc12.63">12.63</A> <A HREF="usermanual-12.html#ss12.63">type </A>
-<LI><A NAME="toc12.64">12.64</A> <A HREF="usermanual-12.html#ss12.64">who </A>
-<LI><A NAME="toc12.65">12.65</A> <A HREF="usermanual-12.html#ss12.65">wx </A>
-</UL>
-<HR>
-<A HREF="usermanual-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
- The DXSpider Administration Manual v1.50
- Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
- K1XX, (k1xx@ptcnh.net)
- February 2003 revision 0.3
-
- A reference for SysOps of the DXSpider DXCluster program.
- ______________________________________________________________________
-
- Table of Contents
-
-
-
- 1. Routing and Filtering
- 1.1 Introduction
- 1.2 Route Filters
- 1.3 The node_default filter
- 1.4 General route filtering
- 1.5 General filter rules
- 1.6 Types of filter
- 1.7 Filter options
- 1.8 Default filters
- 1.9 Advanced filtering
- 1.10 Basic hop control
- 1.11 Hop Control on Specific Nodes
- 1.12 Isolating networks
-
- 2. Other filters
- 2.1 Filtering Mail
- 2.2 Filtering words from text fields in Announce, Talk and DX spots
- 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
-
- 3. Mail
- 3.1 Personal mail
- 3.2 Bulletin mail
- 3.3 Forward.pl
- 3.4 The msg command
- 3.5 Message status
- 3.6 Filtering mail
- 3.7 Distribution lists
- 3.8 BBS interface
-
- 4. Scripts
- 5. Databases
- 5.1 Creating databases
- 5.2 Importing databases
- 5.3 Checking available databases
- 5.4 Looking up databases
- 5.5 Removing databases
-
- 6. Information, files and useful programs
- 6.1 MOTD
- 6.2 MOTD_NOR
- 6.3 Downtime message
- 6.4 Other text messages
- 6.5 The Aliases file
- 6.6 Console.pl
- 6.7 Updating kepler data
- 6.8 The QRZ callbook
- 6.9 Connecting logging programs
-
- 7. Java Web applet
- 8. Web based statistics
- 9. Security
- 9.1 Registration
- 9.2 Passwords
-
- 10. CVS
- 10.1 CVS from a Linux platform
- 10.2 CVS from a Windows platform
-
- 11. The DXSpider command set
- 11.1 accept/announce (0)
- 11.2 accept/announce (extended for sysops) (8)
- 11.3 accept/route (8)
- 11.4 accept/spots (0)
- 11.5 accept/spots (extended for sysops) (8)
- 11.6 accept/wcy (0)
- 11.7 accept/wcy (extended for sysops) (8)
- 11.8 accept/wwv (0)
- 11.9 accept/wwv (extended for sysops) (8)
- 11.10 announce (0)
- 11.11 announce full (0)
- 11.12 announce sysop (5)
- 11.13 apropos (0)
- 11.14 bye (0)
- 11.15 catchup (5)
- 11.16 clear/announce (8)
- 11.17 clear/route (8)
- 11.18 clear/spots (0)
- 11.19 clear/spots (extended for sysops) (8)
- 11.20 clear/wcy (0)
- 11.21 clear/wcy (extended for sysops) (8)
- 11.22 clear/wwv (0)
- 11.23 clear/wwv (extended for sysops) (8)
- 11.24 connect (5)
- 11.25 dbavail (0)
- 11.26 dbcreate (9)
- 11.27 dbimport (9)
- 11.28 dbremove (9)
- 11.29 dbshow (0)
- 11.30 debug (9)
- 11.31 delete/user (9)
- 11.32 demonstrate (9)
- 11.33 directory (0)
- 11.34 directory (extended for sysops) (5)
- 11.35 disconnect (8)
- 11.36 dx (0)
- 11.37 export (9)
- 11.38 export_users (9)
- 11.39 filtering (0)
- 11.40 forward/latlong (8)
- 11.41 forward/opername (1)
- 11.42 help (0)
- 11.43 init (5)
- 11.44 kill (0)
- 11.45 kill (5)
- 11.46 kill full (5)
- 11.47 kill/expunge (6)
- 11.48 links (0)
- 11.49 load/aliases (9)
- 11.50 load/badmsg (9)
- 11.51 load/badwords (9)
- 11.52 load/bands (9)
- 11.53 load/cmd_cache (9)
- 11.54 load/forward (9)
- 11.55 load/messages (9)
- 11.56 load/prefixes (9)
- 11.57 merge (5)
- 11.58 msg (9)
- 11.59 pc (8)
- 11.60 ping (1)
- 11.61 rcmd (1)
- 11.62 read (0)
- 11.63 read (extended for sysops) (5)
- 11.64 reject/announce
- 11.65 reject/announce (extended for sysops) (8)
- 11.66 reject/route (8)
- 11.67 reject/spots (0)
- 11.68 reject/spots (extended for sysops) (8)
- 11.69 reject/wcy (0)
- 11.70 reject/wcy (extended for sysops) (8)
- 11.71 reject/wwv (0)
- 11.72 reject/wwv (extended for sysops) (8)
- 11.73 reply (0)
- 11.74 send (0)
- 11.75 set/address (0)
- 11.76 set/announce (0)
- 11.77 set/arcluster (5)
- 11.78 set/baddx (8)
- 11.79 set/badnode (6)
- 11.80 set/badspotter (8)
- 11.81 set/badword (8)
- 11.82 set/beep (0)
- 11.83 set/bbs (5)
- 11.84 set/clx (5)
- 11.85 set/debug (9)
- 11.86 set/dx (0)
- 11.87 set/dxgrid (0)
- 11.88 set/dxnet (5)
- 11.89 set/echo (0)
- 11.90 set/email (0)
- 11.91 set/here (0)
- 11.92 set/homenode (0)
- 11.93 set/hops (8)
- 11.94 set/isolate (9)
- 11.95 set/language (0)
- 11.96 set/location (0)
- 11.97 set/sys_location (9)
- 11.98 set/logininfo (0)
- 11.99 set/lockout (9)
- 11.100 set/name (0)
- 11.101 set/node (9)
- 11.102 set/obscount (9)
- 11.103 set/page (0)
- 11.104 set/password (0)
- 11.105 set/password (9)
- 11.106 set/pinginterval (9)
- 11.107 set/privilege (9)
- 11.108 set/spider (5)
- 11.109 set/sys_qra (9)
- 11.110 set/qra (0)
- 11.111 set/qth (0)
- 11.112 set/register (9)
- 11.113 set/talk (0)
- 11.114 set/wcy (0)
- 11.115 set/wwv (0)
- 11.116 set/wx (0)
- 11.117 show/baddx (1)
- 11.118 show/badnode (6)
- 11.119 show/badspotter (1)
- 11.120 show/badword (1)
- 11.121 show/configuration (0)
- 11.122 show/configuration/node (0)
- 11.123 show/connect (1)
- 11.124 show/date (0)
- 11.125 show/debug (9)
- 11.126 show/dx (0)
- 11.127 show/dxcc (0)
- 11.128 sh/dxstats (0)
- 11.129 show/files (0)
- 11.130 show/filter (0)
- 11.131 show/filter (extended for sysops) (5)
- 11.132 show/hfstats (0)
- 11.133 show/hftable (0)
- 11.134 show/hops (8)
- 11.135 show/isolate (1)
- 11.136 show/lockout (9)
- 11.137 show/log (8)
- 11.138 show/moon (0)
- 11.139 show/muf (0)
- 11.140 show/newconfiguration (0)
- 11.141 show/newconfiguration/node (0)
- 11.142 show/node (1)
- 11.143 show/prefix (0)
- 11.144 show/program (5)
- 11.145 show/qra (0)
- 11.146 show/qrz (0)
- 11.147 show/registered (9)
- 11.148 show/route (0)
- 11.149 show/satellite (0)
- 11.150 show/sun (0)
- 11.151 show/time (0)
- 11.152 show/vhfstats (0)
- 11.153 show/vhftable (0)
- 11.154 show/wcy (0)
- 11.155 show/wwv (0)
- 11.156 shutdown (5)
- 11.157 spoof (9)
- 11.158 stat/db (5)
- 11.159 stat/channel (5)
- 11.160 stat/msg (5)
- 11.161 stat/route_node (5)
- 11.162 stat/route_user (5)
- 11.163 stat/user (5)
- 11.164 sysop (0)
- 11.165 talk (0)
- 11.166 type (0)
- 11.167 who (0)
- 11.168 wx (0)
- 11.169 wx (enhanced for sysops) (5)
-
-
- ______________________________________________________________________
-
- 1. Routing and Filtering
-
- 1.1. Introduction
-
- From DXSpider version 1.48, major changes were introduced to the way
- node connections are treated. This is part of an ongoing process to
- remove problems with loops and to enable talk and other functions to
- propagate across the whole of the worldwide cluster network. In fact,
- in a Spider network, it would be useful, perhaps even necessary to
- have loops. This would give real resilience to the network, meaning
- that if a link dropped, the information flow would simply come in and
- go out via a different route. Of course, we do not have a complete
- network of Spider nodes, there are other programs out there. Some of
- these do not have any protection from loops. Certainly AK1A does not
- handle loops well at all. It is therefore necessary to have some form
- of protection for these nodes.
-
-
- In fact DXSpider has had a simple system for some time which is called
- isolation. This is similar to what in other systems such as clx, is
- called passive mode. A more detailed explanation of isolation is given
- further below. This system is still available and, for simple
- networks, is probably all that you need.
-
-
- The new functionality introduced in version 1.48 allows filtering the
- node and user protocol frames on a "per interface" basis. We call this
- route filtering. This is used instead of isolation.
-
-
- What this really means is that you can control more or less completely
- which user and node management PC protocol frames pass to each of your
- partner nodes. You can also limit what comes into your node from your
- partners. It is even possible to control the settings that your
- partner node has for the routing information that it sends to you
- (using the rcmd command).
-
-
- 1.2. Route Filters
-
- Initially when route filters were being tested we generated a
- "default" filter. Unfortunately it quickly became apparent that this
- might suit the UK cluster network but didn't really fit anybody else.
- However using a default filter is an appropriate thing to do. How, is
- explained further on.
-
-
- The first thing that you must do is determine whether you need to use
- route filtering at all. If you are a "normal" node with two or three
- partners and you arranged in an "official" non-looping tree type
- network, then you do not need to do route filtering and you will feel
- a lot better for not getting involved. If you are successfully using
- isolation then you also probably don't need to use route filtering.
-
-
- To put it simply, you should not mix Isolation and Route Filtering.
- It will work, of sorts, but you will not get the expected results. If
- you are using Isolation sucessfully at the moment, do not get involved
- in Route Filtering unless you have a good supply of aspirin! Once you
- have started down the road of Route Filtering, do not use Isolation
- either. Use one or the other, not both.
-
-
- You will only require this functionality if you are "well-connected".
- What that means is that you are connected to several different parts
- of (say) the EU cluster and, at the same time, also connected to two
- or three places in the US which, in turn are connected back to the EU.
- This is called a "loop" and if you are seriously looped then you need
- filtering.
-
-
- I should at this stage give a little bit of background on filters.
- All the filters in Spider work in basically the same way. You can
- either accept or reject various options in order to create the filter
- rules you wish to achieve. Some filters are user settable, others can
- only be altered by the sysop. Route filtering can only be done by the
- sysop.
-
-
-
- Anyway, without further discouragement, let me start the process of
- explanation.
-
-
- 1.3. The node_default filter
-
- All normal systems should have a default routing filter and it should
- usually be set to send only the normal, unlooped, view of your
- "national" network. Here in the UK that means nodes from the UK and
- Eire, in EU it is more complex as the networks there grew up in a more
- intertwined way.
-
-
-
- The generic commands are:-
-
-
-
- reject/route node_default <filter_option>
-
- or
-
- accept/route node_default <filter_option>
-
-
-
- where filter_option is one of the following ...
-
-
-
- call <prefixes>
- call_dxcc <numbers>
- call_itu <numbers>
- call_zone <numbers>
- channel <prefixes>
- channel_dxcc <numbers>
- channel_itu <numbers>
- channel_zone <numbers>
-
-
-
- Please be careful if you alter this setting, it will affect ALL your
- links! Remember, this is a default filter for node connections, not a
- per link default.
-
-
- For the default routing filter then you have two real choices: either
- a "national" view or the "safe" option of only your own callsign.
- Examples of each (for my node: GB7DJK) are:-
-
-
-
- acc/route node_default call_dxcc 61,38
- acc/route node_default call gb7djk
-
-
-
- GB7DJK uses the first of these. The DXCC countries can be obtained
- from the show/prefix command.
-
-
- The example filters shown control output TO all your partner nodes
- unless they have a specific filter applied to them (see next section).
-
-
- It is also possible to control the incoming routing information that
- you are prepared to accept FROM your partner nodes. The reason this is
- necessary is to make sure that stuff like mail, pings and similar
- commands a) go down the correct links and b) don't loop around
- excessively. Again using GB7DJK as an example a typical default input
- filter would be something like:
-
-
-
- rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
-
-
-
- What this does is accept node and user information for our national
- network from nodes that are in our national network, but rejects such
- information from anyone else. Although it doesn't explicitly say so,
- by implication, any other node information (not from the UK and Eire)
- is accepted.
-
-
- As I imagine it will take a little while to get one's head around all
- of this you can study the effect of any rules that you try by watching
- the debug output after having done:-
-
-
-
- set/debug filter
-
-
-
- After you have got tired of that, to put it back the way it was:-
-
-
-
- unset/debug filter
-
-
-
- 1.4. General route filtering
-
- Exactly the same rules apply for general route filtering. You would
- use either an accept filter or a reject filter like this ...
-
-
-
- reject/route <node_call> <filter_option>
-
- or
-
- accept/route <node_call> <filter_option>
-
-
-
- Here are some examples of route filters ...
-
-
-
- rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
- rej/route all (equiv to [very] restricted mode)
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-
-
-
- In practice you will either be opening the default filter out for a
- partner by defining a specific filter for that callsign:-
-
-
-
- acc/route gb7baa all
- acc/route gb7baa input all
-
-
-
- or restricting it quite a lot, in fact making it very nearly like an
- isolated node, like this:-
-
-
-
- acc/route pi4ehv-8 call gb7djk
- rej/route pi4ehv-8 input call_dxcc 61,38
-
-
-
- This last example takes everything except UK and Eire from PI4EHV-8
- but only sends him my local configuration (just a PC19 for GB7DJK and
- PC16s for my local users).
-
-
- It is possible to write much more complex rules, there are up to 10
- accept/reject pairs per callsign per filter. For more information see
- the next section.
-
-
-
- 1.5. General filter rules
-
- Upto v1.44 it was not possible for the user to set their own filters.
- From v1.45 though that has all changed. It is now possible to set
- filters for just about anything you wish. If you have just updated
- from an older version of DXSpider you will need to update your new
- filters. You do not need to do anything with your old filters, they
- will be renamed as you update.
-
-
- There are 3 basic commands involved in setting and manipulating
- filters. These are accept, reject and clear. First we will look
- generally at filtering. There are a number of things you can filter in
- the DXSpider system. They all use the same general mechanism.
-
-
- In general terms you can create a "reject" or an "accept" filter which
- can have up to 10 lines in it. You do this using, for example ...
-
-
-
- accept/spots .....
- reject/spots .....
-
-
-
- where ..... are the specific commands for that type of filter. There
- are filters for spots, wwv, announce, wcy and (for sysops) connects.
- See each different accept or reject command reference for more
- details.
-
- There is also a command to clear out one or more lines in a filter.
- They are ...
-
-
-
- clear/spots 1
- clear/spots all
-
-
-
- There is clear/xxxx command for each type of filter.
-
-
- and you can check that your filters have worked by the command ...
-
-
-
- show/filter
-
-
-
- For now we are going to use spots for the examples, but you can apply
- the same principles to all types of filter.
-
-
- 1.6. Types of filter
-
- There are two main types of filter, accept or reject. You can use
- either to achieve the result you want dependent on your own preference
- and which is more simple to do. It is pointless writing 8 lines of
- reject filters when 1 accept filter would do the same thing! Each
- filter has 10 lines (of any length) which are tried in order. If a
- line matches then the action you have specified is taken (ie reject
- means ignore it and accept means take it)
-
-
- If you specify reject filters, then any lines that arrive that match
- the filter will be dumped but all else will be accepted. If you use
- an accept filter, then ONLY the lines in the filter will be accepted
- and all else will be dumped. For example if you have a single line
- accept filter ...
-
-
-
- accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
-
-
- If you set a reject filter like this ...
-
-
-
- reject/spots on hf/cw
-
-
-
- Then you will get everything EXCEPT HF CW spots. You could make this
- single filter even more flexible. For example, if you are interested
- in IOTA and will work it even on CW even though normally you are not
- interested in CW, then you could say ...
-
-
-
- reject/spots on hf/cw and not info iota
-
-
-
- But in that case you might only be interested in iota and say:-
-
-
-
- accept/spots not on hf/cw or info iota
-
-
-
- which achieves exactly the same thing. You should choose one or the
- other until you are comfortable with the way it works. You can mix
- them if you wish (actually you can have an accept AND a reject on the
- same line) but don't attempt this until you are sure you know what you
- are doing!
-
-
- You can arrange your filter lines into logical units, either for your
- own understanding or simply convenience. Here is an example ...
-
-
-
- reject/spots 1 on hf/cw
- reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- What this does is to ignore all HF CW spots and also rejects any spots
- on VHF which don't either originate or spot someone in Europe.
-
-
- This is an example where you would use a line number (1 and 2 in this
- case), if you leave the digit out, the system assumes '1'. Digits
- '0'-'9' are available. This make it easier to see just what filters
- you have set. It also makes it more simple to remove individual
- filters, during a contest for example.
-
-
- You will notice in the above example that the second line has
- brackets. Look at the line logically. You can see there are 2
- separate sections to it. We are saying reject spots that are VHF or
- above APART from those in zones 14, 15 and 16 (either spotted there or
- originated there). If you did not have the brackets to separate the 2
- sections, then Spider would read it logically from the front and see a
- different expression entirely ...
-
-
-
- (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-
-
-
- The simple way to remember this is, if you use OR - use brackets.
- Whilst we are here CASE is not important. 'And BY_Zone' is just the
- same as 'and by_zone'.
-
- As mentioned earlier, setting several filters can be more flexible
- than simply setting one complex one. Doing it in this way means that
- if you want to alter your filter you can just redefine or remove one
- or more lines of it or one line. For example ...
-
-
-
- reject/spots 1 on hf/ssb
-
- would redefine our earlier example, or
-
-
-
- clear/spots 1
-
-
-
- To remove all the filter lines in the spot filter ...
-
-
-
- clear/spots all
-
-
-
- 1.7. Filter options
-
- You can filter in several different ways. The options are listed in
- the various helpfiles for accept, reject and filter.
-
-
- 1.8. Default filters
-
- Sometimes all that is needed is a general rule for node connects.
- This can be done with a node_default filter. This rule will always be
- followed, even if the link is isolated, unless another filter is set
- specifically. Default rules can be set for nodes and users. They can
- be set for spots, announces, WWV and WCY. They can also be used for
- hops. An example might look like this ...
-
-
-
- accept/spot node_default by_zone 14,15,16,20,33
- set/hops node_default spot 50
-
-
-
- This filter is for spots only, you could set others for announce, WWV
- and WCY. This filter would work for ALL nodes unless a specific
- filter is written to override it for a particular node. You can also
- set a user_default should you require. It is important to note that
- default filters should be considered to be "connected". By this I
- mean that should you override the default filter for spots, you need
- to add a rule for the hops for spots also.
-
-
- 1.9. Advanced filtering
-
- Once you are happy with the results you get, you may like to
- experiment.
-
-
- The previous example that filters hf/cw spots and accepts vhf/uhf
- spots from EU can be written with a mixed filter, for example ...
-
-
-
- rej/spot on hf/cw
- acc/spot on 0/30000
- acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-
- Note that the first filter has not been specified with a number. This
- will automatically be assumed to be number 1. In this case, we have
- said reject all HF spots in the CW section of the bands but accept all
- others at HF. Also accept anything in VHF and above spotted in or by
- operators in the zones 14, 15 and 16. Each filter slot actually has a
- 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
- the accept slot.
-
-
- It was mentioned earlier that after a reject test that doesn't match,
- the default for following tests is 'accept', the reverse is true for
- 'accept'. In the example what happens is that the reject is executed
- first, any non hf/cw spot is passed to the accept line, which lets
- through everything else on HF. The next filter line lets through just
- VHF/UHF spots from EU.
-
-
- 1.10. Basic hop control
-
- In /spider/data you will find a file called hop_table.pl. This is the
- file that controls your hop count settings. It has a set of default
- hops on the various PC frames and also a set for each node you want to
- alter the hops for. You may be happy with the default settings of
- course, but this powerful tool can help to protect and improve the
- network. The file will look something like this ...
-
-
-
- #
- # hop table construction
- #
-
- package DXProt;
-
- # default hopcount to use
- $def_hopcount = 5;
-
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
-
-
- # the per node hop control thingy
-
-
- %nodehops =
- (
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- );
-
-
-
- Each set of hops is contained within a pair of curly braces and
- contains a series of PC frame types. PC11 for example is a DX spot.
- The figures here are not exhaustive but should give you a good idea of
- how the file works.
-
-
- SHould any of the nodecalls include an ssid, it is important to wrap
- the whole call in single quotes, like this ...
-
-
-
- 'DB0FHF-15' => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-
-
-
- If you do not do this, you will get errors and the file will not work
- as expected.
-
-
- You can alter this file at any time, including whilst the cluster is
- running. If you alter the file during runtime, the command load/hops
- will bring your changes into effect.
-
-
- 1.11. Hop Control on Specific Nodes
-
- You can set a callsign specific hop count for any of the standard
- filter options so:-
-
-
-
- set/hops gb7djk spot 4
- set/hops node_default route 10
- set/hops gb7baa wcy 5
-
-
-
- all work on their specific area of the protocol.
-
-
- The set/hops command overrides any hops that you have set otherwise.
-
-
- You can show what hops have been set using the show/hops command.
-
-
- 1.12. Isolating networks
-
- It is possible to isolate networks from each other on a "gateway" node
- using the set/isolate <node_call> command.
-
-
- The effect of this is to partition an isolated network completely from
- another node connected to your node. Your node will appear on and
- otherwise behave normally on every network to which you are connected,
- but data from an isolated network will not cross onto any other
- network or vice versa. However all the spot, announce and WWV traffic
- and personal messages will still be handled locally (because you are a
- real node on all connected networks), that is locally connected users
- will appear on all networks and will be able to access and receive
- information from all networks transparently. All routed messages will
- be sent as normal, so if a user on one network knows that you are a
- gateway for another network, he can still still send a talk/announce
- etc message via your node and it will be routed across.
-
-
- If you use isolate on a node connection you will continue to receive
- all information from the isolated partner, however you will not pass
- any information back to the isolated node. There are times when you
- would like to forward only spots across a link (maybe during a contest
- for example). To do this, isolate the node in the normal way and use
- an acc/spot >call< all filter to override the isolate.
-
-
- 2. Other filters
-
- 2.1. Filtering Mail
-
- In the /spider/msg directory you will find a file called
- badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
- original looks something like this ....
-
-
-
- # the list of regexes for messages that we won't store having
- # received them (bear in mind that we must receive them fully before
- # we can bin them)
-
-
- # The format of each line is as follows
-
- # type source pattern
- # P/B/F T/F/O/S regex
-
- # type: P - private, B - bulletin (msg), F - file (ak1a bull)
- # source: T - to field, F - from field, O - origin, S - subject
- # pattern: a perl regex on the field requested
-
- # Currently only type B and P msgs are affected by this code.
- #
- # The list is read from the top down, the first pattern that matches
- # causes the action to be taken.
-
- # The pattern can be undef or 0 in which case it will always be selected
- # for the action specified
-
-
-
- package DXMsg;
-
- @badmsg = (
- );
-
-
-
- I think this is fairly self explanatory. It is simply a list of
- subject headers that we do not want to pass on to either the users of
- the cluster or the other cluster nodes that we are linked to. This is
- usually because of rules and regulations pertaining to items for sale
- etc in a particular country.
-
-
-
- 2.2. Filtering words from text fields in Announce, Talk and DX spots
-
- From version 1.48 onwards the interface to this has changed. You can
- now use the commands set/badword to add words that you are not
- prepared to see on the cluster, unset/badword to allow that word again
- and show/badword to list the words that you have set.
-
-
- If you have a previous /spider/data/badwords, the first time you start
- the node, it will read and convert this file to the new commands. The
- old style file will then be removed.
-
-
- 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
-
-
- There are a number of commands that control whether a spot progresses
- any further by regarding it as "bad" in some way.
-
-
- A DX Spot has a number of fields which can be checked to see whether
- they contain "bad" values, they are: the DX callsign itself, the
- Spotter and the Originating Node.
-
-
- There are a set of commands which allow the sysop to control whether a
- spot continues:-
-
-
-
- set/baddx
- set/badspotter
- set/badnode
-
-
-
- These work in the same as the set/badword command, you can add any
- words or callsigns or whatever to the appropriate database. For
- example, to stop a spot from a particular node you do:
-
-
-
- set/badnode gb7djk gb7dxc
-
-
-
- a bad spotter:
-
-
-
- set/badspotter b0mb p1rat nocall
-
-
-
- and some bad dx:
-
-
-
- set/baddx video wsjt
-
-
-
- You can remove a word using the appropriate unset command
- (unset/baddx, unset/badspotter, unset/badnode) or list them using one
- of show/baddx, show/badspotter and show/badnode.
-
-
-
- 3. Mail
-
- DXSpider deals seamlessly with standard AK1A type mail. It supports
- both personal and bulletin mail and the sysop has additional commands
- to ensure that mail gets to where it is meant. DXSpider will send
- mail almost immediately, assuming that the target is on line.
- However, only one mail message is dealt with at any one time. If a
- mail message is already being sent or recieved, then the new message
- will be queued until it has finished.
-
- The cluster mail is automatically deleted after 30 days unless the
- sysop sets the "keep" flag using the msg command.
-
-
- 3.1. Personal mail
-
- Personal mail is sent using the sp command. This is actually the
- default method of sending mail and so a simple s for send will do. A
- full list of the send commands and options is in the command set
- section, so I will not duplicate them here.
-
-
- 3.2. Bulletin mail
-
- Bulletin mail is sent by using the sb command. This is one of the
- most common mistakes users make when sending mail. They send a
- bulletin mail with s or sp instead of sb and of course the message
- never leaves the cluster. This can be rectified by the sysop by using
- the msg command.
-
-
- Bulletin addresses can be set using the Forward.pl file.
-
-
- 3.3. Forward.pl
-
- DXSpider receives all and any mail sent to it without any alterations
- needed in files. Because personal and bulletin mail are treated
- differently, there is no need for a list of accepted bulletin
- addresses. It is necessary, however, to tell the program which links
- accept which bulletins. For example, it is pointless sending
- bulletins addresses to "UK" to any links other than UK ones. The file
- that does this is called forward.pl and lives in /spider/msg. At
- default, like other spider files it is named forward.pl.issue. Rename
- it to forward.pl and edit the file to match your requirements. The
- format is below ...
-
-
-
- #
- # this is an example message forwarding file for the system
- #
- # The format of each line is as follows
- #
- # type to/from/at pattern action destinations
- # P/B/F T/F/A regex I/F [ call [, call ...] ]
- #
- # type: P - private, B - bulletin (msg), F - file (ak1a bull)
- # to/from/at: T - to field, F - from field, A - home bbs, O - origin
- # pattern: a perl regex on the field requested
- # action: I - ignore, F - forward
- # destinations: a reference to an array containing node callsigns
- #
- # if it is non-private and isn't in here then it won't get forwarded
- #
- # Currently only type B msgs are affected by this code.
- #
- # The list is read from the top down, the first pattern that matches
- # causes the action to be taken.
- #
- # The pattern can be undef or 0 in which case it will always be selected
- # for the action specified
- #
- # If the BBS list is undef or 0 and the action is 'F' (and it matches the
- # pattern) then it will always be forwarded to every node that doesn't have
- # it (I strongly recommend you don't use this unless you REALLY mean it, if
- # you allow a new link with this on EVERY bull will be forwarded immediately
- # on first connection)
- #
-
- package DXMsg;
-
- @forward = (
- );
-
-
-
- Simply insert a bulletin address and state in the brackets where you
- wish that mail to go. For example, you can see here that mail sent to
- "UK" will only be sent to the UK links and not to PA4AB-14.
-
-
- To force the cluster to reread the file use load/forward
-
-
- NB: If a user tries to send mail to a bulletin address that does not
- exist in this file, they will get an error.
-
-
- 3.4. The msg command
-
- The msg command is a very powerful and flexible tool for the sysop.
- It allows the sysop to alter to and from fields and make other changes
- to manage the cluster mail.
-
- Here is a full list of the various options ...
-
-
-
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waiting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
-
-
-
- These commands are simply typed from within the cluster as the sysop
- user.
-
-
- 3.5. Message status
-
- You can check on a message from within the cluster by using the
- command stat/msg. This will give you additional information on the
- message number including which nodes have received it, which node it
- was received from and when etc. Here is an example of the output of
- the command ...
-
-
-
- G0VGS de GB7MBC 28-Jan-2001 1308Z >
- stat/msg 6869
- From: GB7DJK
- Msg Time: 26-Jan-2001 1302Z
- Msgno: 6869
- Origin: GB7DJK
- Size: 8012
- Subject: AMSAT 2line KEPS 01025.AMSAT
- To: UK
- Got it Nodes: GB7BAA, GB7ADX
- Private: 0
- Read Confirm: 0
- Times read: 0
- G0VGS de GB7MBC 28-Jan-2001 1308Z >
-
-
-
- 3.6. Filtering mail
-
- This is described in the section on Other filters so I will not
- duplicate it here.
-
-
- 3.7. Distribution lists
-
- Distribution lists are simply a list of users to send certain types of
- mail to. An example of this is mail you only wish to send to other
- sysops. In /spider/msg there is a directory called distro. You put
- any distibution lists in here. For example, here is a file called
- SYSOP.pl that caters for the UK sysops.
-
-
- qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
-
-
-
- Any mail sent to "sysop" would only be sent to the callsigns in this
- list.
-
-
- 3.8. BBS interface
-
- Spider provides a simple BBS interface. No input is required from the
- sysop of the cluster at all. The BBS simply sets the cluster as a BBS
- and pushes any required mail to the cluster. No mail can flow from
- Spider to the BBS, the interface is one-way.
-
-
- Please be careful not to flood the cluster network with unnecessary
- mail. Make sure you only send mail to the clusters that want it by
- using the Forward.pl file very carefully.
-
-
- 4. Scripts
-
- From 1.48 onwards it will become increasingly possible to control
- DXSpider's operation with scripts of various kinds.
-
-
- The directory /spider/scripts is where it all happens and is used for
- several things. Firstly it contains a file called startup that can be
- used to call in any changes to the cluster from the default settings
- on startup. This script is executed immediately after all
- initialisation of the node is done but before any connections are
- possible. Examples of this include how many spots it is possible to
- get with the sh/dx command, whether you want registration/passwords to
- be permanently on etc. An example file is shown below and is included
- in the distribution as startup.issue.
-
-
-
- #
- # startup script example
- #
- # set maximum no of spots allowed to 100
- # set/var $Spot::maxspots = 100
- #
- # Set registration on
- # set/var $main::reqreg = 1
- #
- # Set passwords on
- # set/var $main::passwdreq = 1
- #
-
-
-
- As usual, any text behind a # is treated as a comment and not read.
- To use this file, simply rename it from startup.issue to startup. In
- our example above there are three options. The first option is the
- amount of spots that a user can request with the sh/dx command.
- Normally the default is to give 10 spots unless the user specifies
- more. Without this line enabled, the maximum a user can request is
- 100 spots. Depending on your link quality you may wish to enable more
- or less by specifying the number.
-
-
- The other 2 options are dealt with more fully in the security section.
-
-
- Secondly, it is used to store the login scripts for users and nodes.
- Currently this can only be done by the sysop but it is envisaged that
- eventually users will be able to set their own. An example is
- included in the distibution but here is a further example.
-
-
-
- #
- # G0FYD
- #
- blank +
- sh/wwv 3
- blank +
- sh/dx
- blank +
- t g0jhc You abt?
- blank +
-
-
-
- The lines in between commands can simply insert a blank line or a
- character such as a + sign to make the output easier to read. Simply
- create this script with your favourite editor and save it with the
- callsign of the user as the filename. Filenames should always be in
- lower case.
-
-
- Commands can be inserted in the same way for nodes. A node may wish a
- series of commands to be issued on login, such as a merge command for
- example.
-
-
- Thirdly, there are 2 default scripts for users and nodes who do not
- have a specifically defined script. These are user_default and
- node_default
-
-
- 5. Databases
-
- Spider allows the creation of local or remote databases. It supports
- chained databases, allowing several different databases to be scanned
- with one simple command. Importing of databases is limited at present
- to the standard AK1A databases such as OBLAST and the DB0SDX QSL
- database but will expand with time.
-
-
- 5.1. Creating databases
-
- Creating a database could not be more simple. All the commands are
- sent from the cluster prompt as the sysop user.
-
- To create a database you use the command dbcreate. It can be used in
- 3 different ways like so ..
-
-
-
- dbcreate <name>
-
-
- To simply create a database locally, you just tell the command the
- name of the database. This does not create the actual database, it
- simply defines it to say that it exists.
-
-
-
- dbcreate <name> chain <name> [<name>...]
-
-
-
- This creates a chained database entry. The first database will be
- scanned, then the second, the third etc...
-
-
-
- dbcreate <name> remote <name>
-
-
-
- This creates a remote entry. the first name field is the database
- name at the remote node, then the remote switch, then the actual
- node_call of the remote node, for example...
-
-
-
- dbcreate buckmaster remote gb7dxc
-
-
-
- Remote databases cannot be chained, however, the last database in a
- chain can be a remote database.
-
-
- 5.2. Importing databases
-
- The only databases that Spider can currently import are the standard
- AK1A databases such as OBLAST or the DB0SDX qsl and address database.
- This will be added to with time.
-
- To import such a database, first put the file somewhere useful like
- /tmp and then issue the following command ...
-
-
-
- dbimport oblast /tmp/OBLAST.FUL
-
-
-
- This will update the existing local oblast database or create it if it
- does not exist.
-
-
- 5.3. Checking available databases
-
- Once a database is created, you will want to check that it has been
- added. To do this use the dbavail command. This will output the
- available databases. For example ...
-
-
-
- dbavail
- DB Name Location Chain
- qsl Local
- buck GB7ADX
- hftest GB7DXM
- G0VGS de GB7MBC 3-Feb-2001 1925Z >
-
-
-
- 5.4. Looking up databases
-
- To look for information in a defined database, simply use the dbshow
- command, for example ...
-
-
-
- dbshow buckmaster G0YLM
-
-
-
- will show the information for the callsign G0YLM from the buckmaster
- database if it exists. To make things more standard for the users you
- can add an entry in the Aliases file so that it looks like a standard
- show command like this ...
-
-
-
- Now you can simply use show/buckmaster or an abreviation.
-
-
- 5.5. Removing databases
-
- To delete an existing database you use the dbremove command. For
- example ...
-
-
-
- dbremove oblast
-
-
-
- would remove the oblast database and its associated datafile from the
- system. There are no warnings or recovery possible from this command.
- If you remove a database it ceases to exist and would have to be
- created from scratch if you still required it.
-
-
- 6. Information, files and useful programs
-
- 6.1. MOTD
-
- One of the more important things a cluster sysop needs to do is to get
- information to his users. The simplest way to do this is to have a
- banner that is sent to the user on login. This is know as a "message
- of the day" or "motd". To set this up, simply create a file in
- /spider/data called motd and edit it to say whatever you want. It is
- purely a text file and will be sent automatically to anyone logging in
- to the cluster.
- 6.2. MOTD_NOR
-
- This message of the day file lives in the same directory as the
- standard motd file but is only sent to non-registered users. Once
- registered they will receive the same message as any other user.
-
-
- 6.3. Downtime message
-
- If for any reason the cluster is down, maybe for upgrade or
- maintenance but the machine is still running, a message can be sent to
- the user advising them of the fact. This message lives in the
- /spider/data directory and is called "offline". Simply create the
- file and edit it to say whatever you wish. This file will be sent to
- a user attempting to log into the cluster when DXSpider is not
- actually running.
-
-
- 6.4. Other text messages
-
- You can set other text messages to be read by the user if they input
- the file name. This could be for news items or maybe information for
- new users. To set this up, make a directory under /spider called
- packclus. Under this directory you can create files called news or
- newuser for example. In fact you can create files with any names you
- like. These can be listed by the user with the command ....
-
-
-
- show/files
-
-
-
- They can be read by the user by typing the command ....
-
-
-
- type news
-
-
-
- If the file they want to read is called news. You could also set an
- alias for this in the Alias file to allow them just to type news
-
-
- You can also store other information in this directory, either
- directly or nested under directories. One use for this would be to
- store DX bulletins such as the OPDX bulletins. These can be listed
- and read by the user. To keep things tidy, make a directory under
- /spider/packclus called bulletin. Now copy any OPDX or similar
- bulletins into it. These can be listed by the user in the same way as
- above using the show/files command with an extension for the bulletin
- directory you have just created, like this ....
-
-
-
- show/files bulletin
-
-
-
- An example would look like this ....
-
- sh/files
- bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
-
-
-
- You can see that in the files area (basically the packclus directory)
- there is a file called news and a directory called bulletin. You can
- also see that dates they were created. In the case of the file news,
- you can also see the time it was last modified, a good clue as to
- whether the file has been updated since you last read it. To read the
- file called news you would simply issue the command ....
-
-
-
- type news
-
-
-
- To look what is in the bulletin directory you issue the command ....
-
-
-
- show/files bulletin
- opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
- opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
- opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
- opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
- opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
- opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
- opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
- opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
- opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
- opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
- opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
- opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
- opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
- Press Enter to continue, A to abort (16 lines) >
-
-
-
- You can now read any file in this directory using the type command,
- like this ....
-
-
-
- type bulletin/opdx391
- Ohio/Penn DX Bulletin No. 391
- The Ohio/Penn Dx PacketCluster
- DX Bulletin No. 391
- BID: $OPDX.391
- January 11, 1999
- Editor Tedd Mirgliotta, KB8NW
- Provided by BARF-80 BBS Cleveland, Ohio
- Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
- Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
- Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
- & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
- Press Enter to continue, A to abort (508 lines) >
-
-
-
- The page length will of course depend on what you have it set to!
-
-
- 6.5. The Aliases file
-
- You will find a file in /spider/cmd/ called Aliases. This is the file
- that controls what a user gets when issuing a command. It is also
- possible to create your own aliases for databases and files you create
- locally.
-
-
- You should not alter the original file in /spider/cmd/ but create a
- new file with the same name in /spider/local_cmd. This means that any
- new Aliases files that is downloaded will not overwrite your self
- created Aliases and also that you do not override any new Aliases with
- your copy in /spider/local_cmd/. You must remember that any files you
- store in /spider/local/ or /spider/local_cmd override the originals if
- the same lines are used in both files.
-
-
- The best way of dealing with all this then is to only put your own
- locally created Aliases in the copy in /spider/local_cmd. The example
- below is currently in use at GB7MBC.
-
-
-
- #
- # Local Aliases File
- #
-
- package CmdAlias;
-
- %alias = (
- 'n' => [
- '^news$', 'type news', 'type',
- ],
- 's' => [
- '^sh\w*/buck$', 'show/qrz', 'show',
- '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
- '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
- '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
- '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
- ],
- )
-
-
-
- Each alphabetical section should be preceded by the initial letter and
- the section should be wrapped in square brackets as you can see. The
- syntax is straightforward. The first section on each line is the new
- command that will be allowed once the alias is included. The second
- section is the command it is replacing and the last section is the
- actual command that is being used.
-
-
- The eagle-eyed amongst you will have noticed that in the first
- section, the new alias command has a '^' at the start and a '$' at the
- end. Basically these force a perfect match on the alias. The '^'
- says match the beginning exactly and the with similar commands.
-
-
- I have 3 different types of alias in this file. At the top is an
- alias for 'news'. This is a file I have created in the
- /spider/packclus/ directory where I can inform users of new
- developments or points of interest. In it's initial form a user would
- have to use the command type news. The alias allows them to simply
- type news to get the info. Second is an alias for the show/qrz
- command so that those users used to the original show/buck command in
- AK1A will not get an error, and the rest of the lines are for locally
- created databases so that a user can type show/hftest instead of
- having to use the command dbshow hftest which is not as intuitive.
-
-
- This file is just an example and you should edit it to your own
- requirements. Once created, simply issue the command load/alias at
- the cluster prompt as the sysop user and the aliases should be
- available.
-
-
-
- 6.6. Console.pl
-
- In later versions of Spider a simple console program is provided for
- the sysop. This has a type ahead buffer with line editing facilities
- and colour for spots, announces etc. To use this program, simply use
- console.pl instead of client.
-
-
- To edit the colours, copy /spider/perl/Console.pl to /spider/local and
- edit the file with your favourite editor.
-
-
- 6.7. Updating kepler data
-
- Spider has a powerful and flexible show/satellite command. In order
- for this to be accurate, the kepler data has to be updated regularly.
- In general, this data is available as an email or via cluster mail.
- Updating it is simple. First you need to export the mail message as a
- file. You do this with the export command from the cluster prompt as
- the sysop. For example ...
-
-
-
- export 5467 /spider/perl/keps.in
-
-
-
- would export message number 5467 as a file called keps.in in the
- /spider/perl directory.
-
-
- Now login to a VT as sysop and cd /spider/perl. There is a command in
- the perl directory called convkeps.pl. All we need to do now is
- convert the file like so ...
-
-
-
- ./convkeps.pl keps.in
-
-
-
- Now go back to the cluster and issue the command ...
-
-
-
- load/keps
-
-
-
- That is it! the kepler data has been updated.
-
-
- 6.8. The QRZ callbook
-
- The command sh/qrz will only work once you have followed a few simple
- steps. First you need to get a user ID and password from qrz.com.
- Simply go to the site and create one. Secondly you need to copy the
- file /spider/perl/Internet.pm to /spider/local and alter it to match
- your user ID and password. You also at this point need to set
- $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
- proprieter of qrz.com for allowing this access.
-
-
- 6.9. Connecting logging programs
-
- There appear to be very few logging programs out there that support
- telnet especially the popular ones like LogEQF, Turbolog etc. This
- can make it difficult to connect to your own cluster! The way to do
- it is to make the logging program think it has a TNC attached to a com
- port on the logging PC and 'push' a linux login out to it. This is
- achieved very simply by the use of agetty.
-
-
- All that is required is to add a line in /etc/inittab to have the
- client ready for a connection on the com port of your choice.
- Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
- for com2 etc.
-
-
-
- c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
-
-
-
- Add this after the standard runlevel lines in /etc/inittab. The above
- line works on ttyS1 (com2). Now as root, issue the command telinit q
- and it should be ready for connection. All that is required is a 3
- wire serial lead (tx, rx and signal ground). Tell you logging program
- to use 8n1 at 9600 baud and you should see a Linux login prompt.
- Login as normal and then telnet from there to the cluster.
-
-
- 7. Java Web applet
-
- In the spider tree will be a directory spider-web. This is a neat
- little java web applet that can be run from a website. The applet
- must run on the same machine as the cluster. The included README file
- is shown below.
-
-
- I should comment here that the applet is precompiled, that is, ready
- to go. It was compiled using JDK1.3.1. If your version is earlier
- than this then it may not work. Should that be the case you need to
- recompile or update your JDK. To recompile do the following ...
-
-
-
- cd /spider/spider-web
- rm *.class
- /usr/bin/javac spiderclient.java
-
-
-
- I have used /usr/bin/javac as an example, your path to javac may be
- different.
-
-
- Spider-WEB v0.6b
-
- Completely based on a clx web client written in Java by dl6dbh
- (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
-
- The webserver has to run on the same machine as your DxSpider software!
-
- It is assumed that you have Java installed. You need JDK1.3.1 at least.
-
- Installation instructions (Performed as root):
-
- Put all the files in the spider-web directory into a newly created directory
- under the DocumentRoot of your websever for instance 'client'. In my case
- this is: /home/httpd/html/client/ although ymmv. For Suse the correct
- path should be /usr/local/httpd/htdocs/client/ for example.
-
- Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
- /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
- /usr/local/httpd/cgi-bin/ for example.
-
- Change the permissions of the files to ensure they are correct, obviously you
- will need to use the correct path the the files according to your system:
-
- chmod 755 /home/httpd/html/cgi-bin/spider.cgi
- chmod -R 755 /home/httpd/html/client/
-
- By default the spider.cgi script should pick up your hostname (As long as this
- is set correctly). If it does not or your hostname differs from the name that
- you attach to the public address that you are using, then edit spider.cgi :
-
- # Uncomment and set the hostname manually here if the above fails.
- # $HOSTNAME = "gb7mbc.spoo.org" ;
- $PORT = "8000" ;
-
-
- telnet (see Listeners.pm)
-
- NOTE: If you can start the console but cannot connect to the cluster from it,
- then it is possible that the machine you are on cannot resolve the hostname of
- your cluster machine. If this is the case, you need to set your hostname
- manually as above.
-
- You also need to set the $NODECALL variable. This prints the name of your
- choosing (probably your cluster callsign) on the html page.
-
- You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
-
-
-
- 8. Web based statistics
-
- From version 1.50, you can use the freeware software MRTG to produce
- really nice graphical statistics on your web site. For an example try
- http://www.gb7mbc.net/mrtg/stats.html.
-
-
- The following should help you get it all working.
-
-
- First you need to download the latest version of MRTG from
- http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
- the following files..
-
-
-
- libpng-1.0.14.tar.gz
- zlib-1.1.4.tar.gz
- gd-1.8.3.tar.gz
-
-
-
- Login to your machine as the root user, put all the downloaded files
- in /usr/local/src/ (or wherever you prefer) and untar and compile
- them. All the information to compile and install these sources come
- with them. After compilation and installation, you will find MRTG in
- /usr/local/mrtg-2.
-
-
- Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
- /spider/html/mrtg/
-
-
- You now need to make 2 symbolic links like below...
-
-
-
- ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
- ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
-
-
-
- Now login to the cluster with your sysop callsign and run the command
- "mrtg all".
-
-
- Now you are nearly there! Login as the sysop user and change to the
- /spider/html/mrtg/ directory. Now run the command indexmaker as shown
- below...
-
-
-
- indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
-
-
-
- Changing the callsign for your own cluster callsign of course!
-
-
- And finally you need to login as the root user and create one last
- symbolic link. Where this points will depend on where your html
- documents are kept. For RedHat systems you use...
-
-
-
- ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
-
-
-
- and for SuSE systems...
-
-
-
- ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
-
-
-
- If you now point your browser to your website as below it should all
- be happening!
-
-
-
- http://www.xxx.xxx/mrtg/stats.html
-
-
-
- Of course, to get the stats to update, you need to add some
- information in the spider crontab file as below...
-
-
-
- # Update stats for mrtg on website
- 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
-
-
-
- This will update the site every 5 minutes.
-
-
- 9. Security
-
- From version 1.49 DXSpider has some additional security features.
- These are not by any means meant to be exhaustive, however they do
- afford some security against piracy. These two new features can be
- used independently of each other or in concert to tighten the
- security.
-
-
- 9.1. Registration
-
- The basic principle of registration is simple. If a user is not
- registered by the sysop, then they have read-only access to the
- cluster. The only thing they can actually send is a talk or a message
- to the sysop. In order for them to be able to spot, send announces or
- talks etc the sysop must register them with the set/register command,
- like this ...
-
-
-
- set/register g0vgs
-
-
-
- The user g0vgs can now fully use the cluster. In order to enable
- registration, you can issue the command ...
-
- set/var $main::reqreg = 1
-
-
-
- Any users that are not registered will now see the motd_nor file
- rather than the motd file as discussed in the Information, files and
- useful programs section.
-
-
- Entering this line at the prompt will only last for the time the
- cluster is running of course and would not be present on a restart.
- To make the change permanent, add the above line to
- /spider/scripts/startup. To read more on the startup file, see the
- section on Information, files and useful programs.
-
-
- To unregister a user use unset/register and to show the list of
- registered users, use the command show/register.
-
-
- 9.2. Passwords
-
- At the moment, passwords only affect users who login to a DXSpider
- cluster node via telnet. If a user requires a password, they can
- either set it themselves or have the sysop enter it for them by using
- the set/password command. Any users who already have passwords, such
- as remote sysops, will be asked for their passwords automatically by
- the cluster. Using passwords in this way means that the user has a
- choice on whether to have a password or not. To force the use of
- passwords at login, issue the command ...
-
-
-
- set/var $main::passwdreq = 1
-
-
-
- at the cluster prompt. This can also be added to the
- /spider/scripts/startup file as above to make the change permanent.
-
-
- Of course, if you do this you will have to assign a password for each
- of your users. If you were asking them to register, it is anticipated
- that you would ask them to send you a message both to ask to be
- registered and to give you the password they wish to use.
-
-
- Should a user forget their password, it can be reset by the sysop by
- first removing the existing password and then setting a new one like
- so ...
-
-
-
- unset/password g0vgs
- set/password g0vgs new_password
-
-
-
- 10. CVS
-
-
-
- 10.1. CVS from a Linux platform
-
- CVS stands for "Concurrent Versions System" and the CVS for DXSpider
- is held at Sourceforge. This means that it is possible to update your
- DXSpider installation to the latest sources by using a few simple
- commands. A graphical interface to CVS for Windows is explained in
- the next section.
-
-
- Please be aware that if you update your system using CVS, it is
- possible that you could be running code that is very beta and not
- fully tested. There is a possibility that it could be unstable.
-
-
- I am of course assuming that you have a machine with both DXSpider and
- Internet access running.
-
-
- BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
- ENTIRE SPIDER TREE!!
-
-
- Assuming you are connected to the Internet, you need to login to the
- CVS repository and then update your Spider source. There are several
- steps which are listed below ...
-
-
- First login as the user sysop. Next you need to connect to the CVS
- repository. You do this with the command below ...
-
-
- cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-
-
-
- You will get a password prompt. Simply hit return here and your
- machine should return to a normal linux prompt.
-
-
- What happens next depends on whether you have an existing installation
- that you want to update with the latest and greatest or whether you
- just want to see what is there and/or run it on a new machine for
- testing.
-
- If you are installing Spider from CVS then change directory to
- /home/sysop
-
- If you are wanting to update Spider then cd to /tmp
-
-
- The next step will create a brand new 'spider' directory in your
- current directory.
-
-
- cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
-
-
-
- This command is all on one line.
-
-
- Hopefully your screen should show you downloading files. The -z3
- simply compresses the download to improve speed. When this has
- finished, you will have exactly the same as if you had untarred a full
- tarball PLUS some extra directories and files that CVS needs to do the
- magic that it does.
- Now if you are doing a new installation, that's it. Carry on as if
- you have just downloaded and untarred the lastest tarball.
-
-
- If you want to upgrade your current installation then do this ...
-
-
-
- tar cvfz /tmp/s.tgz spider
- cd /
- tar xvfzp /tmp/s.tgz
-
-
-
- This is assuming you downloaded to the /tmp directory of course.
-
-
- NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
- permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
- YOU?????
-
- Remember to recompile the C client (cd /spider/src; make)
-
-
- At this point the files have been upgraded. You can (usually) restart
- the cluster in your own time. However, if you attempt to use any new
- commands or features expect it to be fatal! At least your cluster
- will have been restarted then so it will be too late to worry about
- it!
-
-
- Now the magic part! From now on when you want to update, simply
- connect to the Internet and then, as the user sysop ...
-
-
-
- cd /spider
- cvs -z3 update -d
-
-
-
- and your files will be updated. As above, remember to recompile the
- "C" client if it has been updated (CVS will tell you) and restart if
- any of the perl scripts have been altered or added, again, CVS will
- tell you.
-
-
- You will find any changes documented in the /spider/Changes file.
-
-
- 10.2. CVS from a Windows platform
-
- After the initial setup, an update to your DXSpider software is no
- more than a couple of clicks away. This section is intended to
- explain and illustrate the use of the WinCVS application to update
- your DXSpider software. The current stable version of WinCVS is Ver.
- 1.2. You can get this software at:
-
- http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
-
- Pick your download mirror and then install WinCVS after the download
- is complete.
-
-
- In this next section I have included a series of links to .jpg files
- to take advantage of the picture and 1000 words equivalency. The .jpg
- files are in the C:\spider\html directory. If someone using a Linux
- system is reading this section from boredom, the files are in
- /home/sysop/spider/html. One aside, a Linux user can also get a copy
- of gcvs and do your updates graphically as opposed to from the command
- line. The following descriptions are almost identical between WinCvs
- and gcvs. The following screen shots have duplicate links, depending
- upon whether you are viewing this information under the Windows or
- Linux operating system.
-
- When WinCVS is installed, running, and you are connected to the
- internet, the initial screen looks like:
-
- initial.jpg
-
- If you want, you can also look at these .jpg files with another viewer
- that might provide some better clarity to the image. On the left is
- the directory tree for your hard disk. Notice that the spider
- directory has a gray highlight.
-
- To start configuring WinCVS, click on Admin at the top of the screen
- and then Preferences. This should get you:
-
- pref-gen.jpg
-
- In the top line for CVSROOT, enter:
-
-
- anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-
-
-
- and select
-
-
- "passwd" file on the cvs server
-
-
-
- for Authentication on the General tab.
-
- Next, move to the right to the Ports tab.
-
- pref-ports.jpg
-
- In here, check the box on the second line down for the "pserver" port.
- Enter a port number of 2401.
-
- Finally, go to the WinCvs tab all the way to the right.
-
- pref-wincvs.jpg
-
- Enter Notepad as the viewer to open files. For the HOME folder, put
- "C:\spider" and click OK because the configuration is now complete.
-
- You are now ready to upgrade your copy of DXSpider. Click on the
- greyed Spider folder shown in the directory tree on the left of the
- WinCVS display. Two things should happen. The Spider folder will be
- selected and the greyed-out arrow located just below the word Query in
- the top line will turn to solid green.
-
- For anyone using gcvs under Linux, the green arrow is located on the
- extreme left of the display, under the word File. A gcvs screen looks
- like:
-
- gcvs.jpg
-
- Click on the now green arrow to start the download process. An Update
- Settings box will be displayed to which you can simply say OK.
-
- update-OK.jpg
-
- For future reference, the Update Settings box is the place where you
- can enter information to revert to a prior version of DXSpider.
- Information on reverting to a Before Date is contained in the WinCVS
- manual.
-
- After a short period of time, a series of file names will scroll by in
- the lower pane of the WinCVS window. Eventually you should see
-
-
- *****CVS exited normally with code 0*****
-
-
-
- appear in the lower pane. You're done. The updated files are in
- place ready for you to stop and then restart your DXSpider. After the
- restart, you're running with the latest version of DXSpider.
-
- completed.jpg
-
- To paraphrase from the CVS section... Now the magic part! From now on
- when you want to update, simply connect to the Internet and start
- WinCVS.
-
-
- Click on the greyed-out Spider directory in the left screen
- Click on the green down arrow
- Click OK on the Update Settings dialog box
- Restart your Spider software
-
-
-
- 11. The DXSpider command set
-
- Below is a complete list of commands available from the cluster
- prompt. Most maintenance tasks are automatic but there are some
- commands that are useful for a sysop. These are listed below in
- alphabetical order. The number in brackets following the command name
- is the permissions level needed to use the command
-
-
- 11.1. accept/announce (0)
-
- accept/announce [0-9] <pattern> Set an accept filter line for announce
-
-
- Create an 'accept this announce' line for a filter.
-
- An accept filter line means that if the announce matches this filter
- it is passed onto the user. See HELP FILTERS for more info. Please
- read this to understand how filters work - it will save a lot of grief
- later on.
-
- You can use any of the following things in this line:-
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-
-
-
- some examples:-
-
-
-
- acc/ann dest 6MUK
- acc/ann 2 by_zone 14,15,16
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-
-
-
- or
-
-
-
- acc/ann by G,M,2
-
-
-
- This filter would only allow announces that were posted buy UK
- stations. You can use the tag 'all' to accept everything eg:
-
-
-
- acc/ann all
-
-
-
- but this probably for advanced users...
-
-
- 11.2. accept/announce (extended for sysops) (8)
-
- accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
- version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- accept/ann by G,M,2
- accept/ann input node_default by G,M,2
- accept/ann user_default by G,M,2
-
-
-
- 11.3. accept/route (8)
-
- accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
- routing
-
-
- Create an 'accept this routing PC Protocol' line for a filter.
-
-
- An accept filter line means that if a PC16/17/19/21/24/41/50 matches
- this filter it is passed thru that interface. See HELP FILTERING for
- more info. Please read this to understand how filters work - it will
- save a lot of grief later on.
-
-
- You can use any of the following things in this line:-
-
-
-
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-
-
-
- some examples:-
-
-
-
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-
-
-
- You can use the tag 'all' to accept everything eg:
-
-
-
- acc/route all
-
-
-
- 11.4. accept/spots (0)
-
- accept/spots [0-9] <pattern> Set an accept filter line for spots
-
-
- Create an 'accept this spot' line for a filter.
-
-
- An accept filter line means that if the spot matches this filter it is
- passed onto the user. See HELP FILTERS for more info. Please read this
- to understand how filters work - it will save a lot of grief later on.
-
-
- Please read the following section carefully. Though it looks similar,
- reformatting, corrections, and hopefully clarifications have been
- added.
-
- You can use any of the following things in this line:-
-
-
-
- Filters for the station being spotted:
- call <letters of the prefix, but NOT country inclusive>
- call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted
- call K --> K1XX, K1XXX will be spotted
- W1XX, W1XXX will NOT be spotted
- call PA --> PA3EZL will be spotted
- PB2FG will NOT be spotted
-
- call_dxcc <numbers or prefixes>
- call_dxcc G --> G1AAA will be spotted
- GU1AAA will NOT be spotted (different country)
- call_dxcc K --> K1XX, W1XX will be spotted (same country)
- call_dxcc 139 --> PA3EZL and PB2FG will be spotted
-
- call_itu <numbers>
- call_zone <numbers>
-
- Filters for the callsign of the station doing the spotting:
- by <letters of the prefix, but NOT country inclusive>
- by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted
- by K --> spots from K1XX, K1XXX will be spotted
- spots from W1XX, W1XXX will NOT be spotted
-
- by_dxcc <numbers or prefixes>
- by_dxcc G --> spots from G1AAA will be spotted
- spots from GU1AAA will NOT be spotted (different
- country)
- by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)
- by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted
-
- by_itu <numbers>
- by_zone <numbers>
-
- Filters for the callsign of the "node" doing the spotting:
- origin <letters of the prefix, but NOT country inclusive>
- origin K --> spots from a node starting with K will be spotted
- spots from a node starting with KK will NOT be spotted
- spots from a node starting with W will NOT be spotted
-
- Filters for the callsign of the connected node or user (channel) doing the spotting:
- channel <prefixes>
- channel W1HR --> spots from the connected node W1HR will be spotted
- channel K1QX --> spots from the connected user K1QX will be spotted
-
- info <string> eg: iota or qsl
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
-
-
-
- For frequencies, you can use any of the band names defined in
- SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
- thus: hf/ssb. You can also just have a simple range like: 0/30000 -
- this is more efficient than saying simply: freq HF (but don't get too
- hung up about that)
-
- some examples:-
-
-
-
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- You can use the tag 'all' to accept everything, eg:
-
-
-
- acc/spot 3 all
-
-
-
- but this probably for advanced users...
-
-
- 11.5. accept/spots (extended for sysops) (8)
-
- accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- accept/spot db0sue-7 1 by_zone 14,15,16
- accept/spot node_default all
- set/hops node_default 10
-
- accept/spot user_default by G,M,2
-
-
-
- 11.6. accept/wcy (0)
-
- accept/wcy [0-9] <pattern> set an accept WCY filter
-
-
- It is unlikely that you will want to do this, but if you do then you
- can filter on the following fields:-
-
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-
-
- There are no examples because WCY Broadcasts only come from one place
- and you either want them or not (see UNSET/WCY if you don't want
- them).
-
- This command is really provided for future use.
-
- See HELP FILTER for information.
-
-
- 11.7. accept/wcy (extended for sysops) (8)
-
- accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- accept/wcy node_default all
- set/hops node_default 10
-
-
-
- 11.8. accept/wwv (0)
-
- accept/wwv [0-9] <pattern> Set an accept WWV filter
-
-
- It is unlikely that you will want to do this, but if you do then you
- can filter on the following fields:-
-
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-
-
- for example
-
-
-
- accept/wwv by_zone 4
-
-
-
- is probably the only useful thing to do (which will only show WWV
- broadcasts by stations in the US).
-
- See HELP FILTER for information.
-
-
-
- 11.9. accept/wwv (extended for sysops) (8)
-
- accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- accept/wwv db0sue-7 1 by_zone 4
- accept/wwv node_default all
- set/hops node_default 10
-
- accept/wwv user_default by W,K
-
-
-
- 11.10. announce (0)
-
- announce <text> Send an announcement to local users
-
-
- Send an announcement to LOCAL users only, where <text> is the text of
- the announcement you wish to broadcast. If you do not wish to receive
- announces, use the set/noannounce command. Any announces made by a
- sysop will override set/noannounce.
-
-
- 11.11. announce full (0)
-
- announce full <text> Send an announcement cluster wide
-
-
- This command will send your announcement across the whole cluster
- network.
-
-
-
- 11.12. announce sysop (5)
-
- announce sysop <text>
-
-
- Send an announcement to Sysops only
-
-
- 11.13. apropos (0)
-
- apropos <string> Search the help database
-
-
- Search the help database for <string> (it isn't case sensitive), and
- print the names of all the commands that may be relevant.
-
-
- 11.14. bye (0)
-
- bye Exit from the cluster
-
-
- This will disconnect you from the cluster
-
-
- 11.15. catchup (5)
-
- catchup <node_call> All|[<msgno> ...] Mark a message as sent
-
-
- When you send messages the fact that you have forwarded it to another
- node is remembered so that it isn't sent again. When you have a new
- partner node and you add their callsign to your /spider/msg/forward.pl
- file, all outstanding non-private messages will be forwarded to them.
- This may well be ALL the non-private messages. You can prevent this by
- using these commmands:-
-
-
-
- catchup GB7DJK all
- catchup GB7DJK 300 301 302 303 500-510
-
-
-
- and to undo what you have just done:-
-
-
-
- uncatchup GB7DJK all
- uncatchup GB7DJK 300 301 302 303 500-510
-
-
-
- which will arrange for them to be forward candidates again.
-
- Order is not important.
-
-
- 11.16. clear/announce (8)
-
- clear/announce <callsign> [input] [0-9|all] Clear an announce filter
- line
-
-
- A sysop can clear an input or normal output filter for a user or the
- node_default or user_default.
-
-
- 11.17. clear/route (8)
-
- clear/route <callsign> [input] [0-9|all] Clear a route filter line
-
-
- This command allows you to clear (remove) a line in a route filter or
- to remove the whole filter.
-
- see CLEAR/SPOTS for a more detailed explanation.
-
- A sysop can clear an input or normal output filter for a user or the
- node_default or user_default.
-
-
- 11.18. clear/spots (0)
-
- clear/spots [1|all] Clear a spot filter line
-
-
- This command allows you to clear (remove) a line in a spot filter or
- to remove the whole filter.
- If you have a filter:-
-
-
-
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- and you say:-
-
-
-
- clear/spot 1
-
-
-
- you will be left with:-
-
-
-
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- If you do:
-
-
-
- clear/spot all
-
-
-
- the filter will be completely removed.
-
-
- 11.19. clear/spots (extended for sysops) (8)
-
- clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
-
-
- A sysop can clear an input or normal output filter for a user or the
- node_default or user_default.
-
-
- 11.20. clear/wcy (0)
-
- clear/wcy [1|all] Clear a WCY filter line
-
-
- This command allows you to clear (remove) a line in a WCY filter or to
- remove the whole filter.
-
- see CLEAR/SPOTS for a more detailed explanation.
-
-
- 11.21. clear/wcy (extended for sysops) (8)
-
- clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
-
-
-
- A sysop can clear an input or normal output filter for a user or the
- node_default or user_default.
-
-
- 11.22. clear/wwv (0)
-
- clear/wwv [1|all] Clear a WWV filter line
-
-
- This command allows you to clear (remove) a line in a WWV filter or to
- remove the whole filter.
-
- see CLEAR/SPOTS for a more detailed explanation.
-
-
- 11.23. clear/wwv (extended for sysops) (8)
-
- clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
-
-
- A sysop can clear an input or normal output filter for a user or the
- node_default or user_default.
-
-
- 11.24. connect (5)
-
- connect <callsign> Start a connection to another DX Cluster
-
-
- Start a connection process that will culminate in a new connection to
- the DX cluster <callsign>. This process creates a new 'client' process
- which will use the script in /spider/connect/<callsign> to effect the
- 'chat' exchange necessary to traverse the network(s) to logon to the
- cluster <callsign>.
-
-
- 11.25. dbavail (0)
-
- dbavail Show a list of all the databases in the system
-
-
- The title says it all really, this command lists all the databases
- defined in the system. It is also aliased to SHOW/COMMAND.
-
-
- 11.26. dbcreate (9)
-
- dbcreate <name> Create a database entry
- dbcreate <name> chain <name> [<name>..] Create a chained database
- entry
- dbcreate <name> remote <node> Create a remote database entry
-
-
- DBCREATE allows you to define a database in the system. It doesn't
- actually create anything, just defines it.
-
- The databases that are created are simple DB_File hash databases, they
- are therefore already 'indexed'.
-
- You can define a local database with the first form of the command eg:
-
- DBCREATE oblast
-
- You can also chain databases with the addition of the 'chain' keyword.
- This will search each database one after the other. A typical example
- is:
- DBCREATE sdx_qsl chain sql_ad
-
- No checking is done to see if the any of the chained databases exist,
- in fact it is usually better to do the above statement first then do
- each of the chained databases.
-
- Databases can exist offsite. To define a database that lives on
- another node do:
-
- DBCREATE buckmaster remote gb7dxc
-
- Remote databases cannot be chained; however, the last database in a a
- chain can be a remote database eg:
-
- DBCREATE qsl chain gb7dxc
-
- To see what databases have been defined do:
-
- DBAVAIL (or it will have been aliased to SHOW/COMMAND)
-
- It would be normal for you to add an entry into your local Aliases
- file to allow people to use the 'SHOW/<dbname>' style syntax. So you
- would need to add a line like:-
-
-
-
- 's' => [
- ..
- ..
- '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
- ..
- ..
- ],
-
-
-
- to allow
-
- SH/BUCK g1tlh
-
- to work as they may be used to.
-
- See DBIMPORT for the importing of existing AK1A format data to
- databases. See DBSHOW for generic database enquiry
-
-
- 11.27. dbimport (9)
-
- dbimport <dbname> Import AK1A data into a database
-
-
- If you want to import or update data in bulk to a database you can use
- this command. It will either create or update entries into an existing
- database. For example:-
-
- DBIMPORT oblast /tmp/OBLAST.FUL
-
- will import the standard OBLAST database that comes with AK1A into the
- oblast database held locally.
-
-
- 11.28. dbremove (9)
-
- dbremove <dbname> Delete a database
-
- DBREMOVE will completely remove a database entry and also delete any
- data file that is associated with it.
-
- There is no warning, no comeback, no safety net.
-
- For example:
-
- DBREMOVE oblast
-
- will remove the oblast database from the system and it will also
- remove the associated datafile.
-
- I repeat:
-
- There is no warning, no comeback, no safety net.
-
- You have been warned.
-
-
- 11.29. dbshow (0)
-
- dbshow <dbname> <key> Display an entry, if it exists, in a database
-
-
- This is the generic user interface to the database to the database
- system. It is expected that the sysop will add an entry to the local
- Aliases file so that users can use the more familiar AK1A style of
- enquiry such as:
-
-
-
- SH/BUCK G1TLH
-
-
-
- but if he hasn't and the database really does exist (use DBAVAIL or
- SHOW/COMMAND to find out) you can do the same thing with:
-
-
-
- DBSHOW buck G1TLH
-
-
-
- 11.30. debug (9)
-
- debug Set the cluster program into debug mode
-
-
- Executing this command will only have an effect if you are running the
- cluster in debug mode i.e.
-
-
-
- perl -d cluster.pl
-
-
-
- It will interrupt the cluster just after the debug command has
- finished.
-
- 11.31. delete/user (9)
-
- delete/user <callsign> Delete a user from the User Database
-
-
- This command will completely remove a one or more users from the
- database.
-
- There is NO SECOND CHANCE.
-
- It goes without saying that you should use this command CAREFULLY!
-
-
- 11.32. demonstrate (9)
-
- demonstrate <call> <command> Demonstrate a command to another user
-
-
- This command is provided so that sysops can demonstrate commands to
- other users. It runs a command as though that user had typed it in and
- then sends the output to that user, together with the command that
- caused it.
-
-
-
- DEMO g7brn sh/dx iota oc209
- DEMO g1tlh set/here
-
-
-
- Note that this command is similar to SPOOF and will have the same side
- effects. Commands are run at the privilege of the user which is being
- demonstrated to.
-
-
- 11.33. directory (0)
-
- directory List messages
- directory own List your own messages
- directory new List all new messages
- directory to <call> List all messages to <call>
- directory from <call> List all messages from <call>
- directory subject <string> List all messages with <string> in subject
- directory <nn> List last <nn> messages
- directory <from>-<to> List messages <from> message <to> message
-
-
- List the messages in the messages directory.
-
- If there is a 'p' one space after the message number then it is a
- personal message. If there is a '-' between the message number and the
-
- You can use shell escape characters such as '*' and '?' in the <call>
- fields.
-
- You can combine some of the various directory commands together eg:-
-
-
-
- DIR TO G1TLH 5
- or
- DIR SUBJECT IOTA 200-250
-
-
-
- You can abbreviate all the commands to one letter and use ak1a
- syntax:-
-
-
-
- DIR/T G1* 10
- DIR/S QSL 10-100 5
-
-
-
- 11.34. directory (extended for sysops) (5)
-
- Works just like the user command except that sysops can see ALL
- messages.
-
-
- 11.35. disconnect (8)
-
- disconnect <call> [<call> ...] Disconnect a user or node
-
-
- Disconnect any <call> connected locally
-
-
- 11.36. dx (0)
-
- dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
-
- This is how you send a DX Spot to other users. You can, in fact, now
- enter the <freq> and the <call> either way round.
-
-
-
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
-
-
-
- will all give the same result. You can add some remarks to the end of
- the command and they will be added to the spot.
-
-
-
- DX FR0G 144600 this is a test
-
-
-
- You can credit someone else by saying:-
-
-
-
- DX by G1TLH FR0G 144.600 he isn't on the cluster
-
-
-
- The <freq> is compared against the available bands set up in the
- cluster. See SHOW/BANDS for more information.
-
- 11.37. export (9)
-
- export <msgno> <filename> Export a message to a file
-
-
- Export a message to a file. This command can only be executed on a
- local console with a fully privileged user. The file produced will be
- in a form ready to be imported back into the cluster by placing it in
- the import directory (/spider/msg/import).
-
- This command cannot overwrite an existing file. This is to provide
- some measure of security. Any files written will owned by the same
- user as the main cluster, otherwise you can put the new files anywhere
- the cluster can access. For example:-
-
- EXPORT 2345 /tmp/a
-
-
- 11.38. export_users (9)
-
- export_users [<filename>] Export the users database to ascii
-
-
- Export the users database to a file in ascii format. If no filename is
- given then it will export the file to /spider/data/user_asc.
-
- If the file already exists it will be renamed to <filename>.o. In fact
- up to 5 generations of the file can be kept each one with an extra 'o'
- on the suffix.
-
- BE WARNED: this will write to any file you have write access to. No
- check is made on the filename (if any) that you specify.
-
-
- 11.39. filtering (0)
-
- filtering Filtering things in DXSpider
-
-
- There are a number of things you can filter in the DXSpider system.
- They all use the same general mechanism.
-
- In general terms you can create a 'reject' or an 'accept' filter which
- can have up to 10 lines in it. You do this using, for example:-
-
- accept/spots ..... reject/spots .....
-
- where ..... are the specific commands for that type of filter. There
- are filters for spots, wwv, announce, wcy and (for sysops) connects.
- See each different accept or reject command reference for more
- details.
-
- There is also a command to clear out one or more lines in a filter and
- one to show you what you have set. They are:-
-
- clear/spots 1 clear/spots all
-
- and
-
- show/filter
-
- There is clear/xxxx command for each type of filter.
-
- For now we are going to use spots for the examples, but you can apply
- the principles to all types of filter.
-
- There are two main types of filter 'accept' or 'reject'; which you use
- depends entirely on how you look at the world and what is least
- writing to achieve what you want. Each filter has 10 lines (of any
- length) which are tried in order. If a line matches then the action
- you have specified is taken (ie reject means ignore it and accept
- means gimme it).
-
- The important thing to remember is that if you specify a 'reject'
- filter (all the lines in it say 'reject/spots' (for instance) then if
- a spot comes in that doesn't match any of the lines then you will get
- it BUT if you specify an 'accept' filter then any spots that don't
- match are dumped. For example if I have a one line accept filter:-
-
- accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
- then automatically you will ONLY get VHF spots from or to CQ zones 14
- 15 and 16. If you set a reject filter like:
-
- reject/spots on hf/cw
-
- Then you will get everything EXCEPT HF CW spots, If you am interested
- in IOTA and will work it even on CW then you could say:-
-
- reject/spots on hf/cw and not info iota
-
- But in that case you might only be interested in iota and say:-
-
- accept/spots not on hf/cw or info iota
-
- which is exactly the same. You should choose one or the other until
- you are confortable with the way it works. Yes, you can mix them
- (actually you can have an accept AND a reject on the same line) but
- don't try this at home until you can analyse the results that you get
- without ringing up the sysop for help.
-
- You can arrange your filter lines into logical units, either for your
- own understanding or simply convenience. I have one set frequently:-
-
- reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone
- 14,15,16 or call_zone 14,15,16)
-
- What this does is to ignore all HF CW spots (being a class B I can't
- read any CW and couldn't possibly be interested in HF :-) and also
- rejects any spots on VHF which don't either originate or spot someone
- in Europe.
-
- This is an exmaple where you would use the line number (1 and 2 in
- this case), if you leave the digit out, the system assumes '1'. Digits
-
- You can leave the word 'and' out if you want, it is implied. You can
- use any number of brackets to make the 'expression' as you want it.
- There are things called precedence rules working here which mean that
- you will NEED brackets in a situation like line 2 because, without it,
- will assume:-
-
- (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-
- annoying, but that is the way it is. If you use OR - use brackets.
- Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
- by_zone'.
-
- If you want to alter your filter you can just redefine one or more
- lines of it or clear out one line. For example:-
-
- reject/spots 1 on hf/ssb
-
- or
-
- clear/spots 1
-
- To remove the filter in its entirty:-
-
- clear/spots all
-
- There are similar CLEAR commands for the other filters:-
-
- clear/announce clear/wcy clear/wwv
-
- ADVANCED USERS:-
-
- Once you are happy with the results you get, you may like to
- experiment.
-
- my example that filters hf/cw spots and accepts vhf/uhf spots from EU
- can be written with a mixed filter, eg:
-
- rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and
- (by_zone 14,15,16 or call_zone 14,15,16)
-
- each filter slot actually has a 'reject' slot and an 'accept' slot.
- The reject slot is executed BEFORE the accept slot.
-
- It was mentioned earlier that after a reject test that doesn't match,
- the default for following tests is 'accept', the reverse is true for
- first, any non hf/cw spot is passed to the accept line, which lets
- thru everything else on HF.
-
- The next filter line lets through just VHF/UHF spots from EU.
-
-
- 11.40. forward/latlong (8)
-
- forward/latlong <node_call> Send latitude and longitude information to
- another cluster
-
-
- This command sends all the latitude and longitude information that
- your cluster is holding against callsigns. One advantage of recieving
- this information is that more locator information is held by you.
- This means that more locators are given on the DX line assuming you
- have set/dxgrid enabled. This could be a LOT of information though,
- so it is not recommended on slow links.
-
-
- 11.41. forward/opername (1)
-
- forward/opername <call> Send out information on this <call> to all
- clusters
-
-
- This command sends out any information held in the user file which can
- be broadcast in PC41 protocol packets. This information is Name, QTH,
- Location and Homenode. PC41s are only sent for the information that is
- available.
-
-
- 11.42. help (0)
-
- help <cmd> Get help on a command
-
-
-
- All commands can be abbreviated, so SHOW/DX can be abbreviated to
- SH/DX, ANNOUNCE can be shortened to AN and so on.
-
- Look at the APROPOS <string> command which will search the help
- database for the <string> you specify and give you a list of likely
- commands to look at with HELP.
-
-
- 11.43. init (5)
-
- init <node call> Re-initialise a link to an AK1A compatible node
-
-
- This command attempts to re-initialise a link to a (usually) AK1A node
- that has got confused, usually by a protocol loop of some kind. It may
- work - but you usually will be better off simply disconnecting it (or
- better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
- node>).
-
- Best of luck - you will need it.
-
-
- 11.44. kill (0)
-
- kill <msgno> [<msgno> ..] Delete a message from the local system
-
-
- Delete a message from the local system. You will only be able to
- delete messages that you have originated or been sent (unless you are
- the sysop).
-
-
- 11.45. kill (5)
-
- kill <msgno> [<msgno> ...] Remove or erase a message from the system
- kill from <call> Remove all messages from a callsign
- kill to <call> Remove all messages to a callsign
-
-
- You can get rid of any message to or originating from your callsign
- using this command. You can remove more than one message at a time.
-
- As a sysop you can kill any message on the system.
-
-
- 11.46. kill full (5)
-
- kill full <msgno> [<msgno>] Delete a message from the whole cluster
-
-
- Delete a message (usually a 'bulletin') from the whole cluster system.
-
- This uses the subject field, so any messages that have exactly the
- same subject will be deleted. Beware!
-
-
- 11.47. kill/expunge (6)
-
- kill/expunge <msgno> [<msgno>..]Expunge a message
-
-
- Deleting a message using the normal KILL commands only marks that
- message for deletion. The actual deletion only happens later (usually
- two days later).
-
-
- The KILL EXPUNGE command causes the message to be truly deleted more
- or less immediately.
-
- It otherwise is used in the same way as the KILL command.
-
-
-
- 11.48. links (0)
-
- links Show which nodes are physically connected
-
-
- This is a quick listing that shows which links are connected and some
- information about them. See WHO for a list of all connections.
-
-
-
- 11.49. load/aliases (9)
-
- load/aliases Reload the command alias table
-
-
- Reload the /spider/cmd/Aliases file after you have editted it. You
- will need to do this if you change this file whilst the cluster is
- running in order for the changes to take effect.
-
-
- 11.50. load/badmsg (9)
-
- load/badmsg Reload the bad message table
-
-
- Reload the /spider/msg/badmsg.pl file if you have changed it manually
- whilst the cluster is running. This table contains a number of perl
- regular expressions which are searched for in the fields targetted of
- each message. If any of them match then that message is immediately
- deleted on receipt.
-
-
- 11.51. load/badwords (9)
-
- load/badwords Reload the bad words table
-
-
- Reload the /spider/data/badwords file if you have changed it manually
- whilst the cluster is running. This file contains a list of words
- which, if found on certain text portions of PC protocol, will cause
- those protocol frames to be rejected. It will all put out a message if
- any of these words are used on the announce, dx and talk commands. The
- words can be one or more on a line, lines starting with '#' are
- ignored.
-
-
- 11.52. load/bands (9)
-
- load/bands Reload the band limits table
-
-
- Reload the /spider/data/bands.pl file if you have changed it manually
- whilst the cluster is running.
-
-
- 11.53. load/cmd_cache (9)
-
- load/cmd_cache Reload the automatic command cache
-
- Normally, if you change a command file in the cmd or local_cmd tree it
- will automatially be picked up by the cluster program. Sometimes it
- can get confused if you are doing a lot of moving commands about or
- delete a command in the local_cmd tree and want to use the normal one
- again. Execute this command to reset everything back to the state it
- was just after a cluster restart.
-
-
- 11.54. load/forward (9)
-
- load/forward Reload the msg forwarding routing table
-
- Reload the /spider/msg/forward.pl file if you have changed it manually
- whilst the cluster is running.
-
-
- 11.55. load/messages (9)
-
- load/messages Reload the system messages file
-
-
- If you change the /spider/perl/Messages file (usually whilst
- fiddling/writing ne commands) you can have them take effect during a
- cluster session by executing this command. You need to do this if get
- something like :-
-
- unknown message 'xxxx' in lang 'en'
-
-
- 11.56. load/prefixes (9)
-
- load/prefixes Reload the prefix table
-
-
- Reload the /spider/data/prefix_data.pl file if you have changed it
- manually whilst the cluster is running.
-
-
- 11.57. merge (5)
-
- merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
-
-
- MERGE allows you to bring your spot and wwv database up to date. By
- default it will request the last 10 spots and 5 WWVs from the node you
- select. The node must be connected locally.
-
- You can request any number of spots or wwv and although they will be
- appended to your databases they will not duplicate any that have
- recently been added (the last 2 days for spots and last month for WWV
- data).
-
-
- 11.58. msg (9)
-
- msg <cmd> <msgno> [data ...] Alter various message parameters
-
-
- Alter message parameters like To, From, Subject, whether private or
- bulletin or return receipt (RR) is required or whether to keep this
- message from timing out.
-
-
-
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
-
-
-
- You can look at the status of a message by using:-
-
- STAT/MSG <msgno>
-
- This will display more information on the message than DIR does.
-
-
- 11.59. pc (8)
-
- pc <call> <text> Send text (eg PC Protocol) to <call>
-
-
- Send some arbitrary text to a locally connected callsign. No
- processing is done on the text. This command allows you to send PC
- Protocol to unstick things if problems arise (messages get stuck etc).
- eg:-
-
- pc gb7djk PC33^GB7TLH^GB7DJK^400^
-
- You can also use in the same way as a talk command to a connected user
- but without any processing, added of "from <blah> to <blah>" or
- whatever.
-
- pc G1TLH Try doing that properly!!!
-
-
- 11.60. ping (1)
-
- ping <node> Check the link quality between nodes
-
-
- his command allows you to send a frame to another cluster node on the
- network and get a return frame. The time it takes to do this is a
- good indication of the quality of the link. The actual time it takes
- is output to the console in seconds. Any visible cluster node can be
- PINGed.
-
-
-
- 11.61. rcmd (1)
-
- rcmd <node call> <cmd> Send a command to another DX cluster
-
-
- This command allows you to send nearly any command to another DX
- Cluster node that is connected to the system.
-
-
- Whether you get any output is dependant on a) whether the other system
- knows that the node callsign of this cluster is in fact a node b)
- whether the other system is allowing RCMDs from this node and c)
- whether you have permission to send this command at all.
-
-
- 11.62. read (0)
-
- read Read the next unread personal message addressed to you
- read <msgno> Read the specified message
-
-
- You can read any messages that are sent as 'non-personal' and also any
- message either sent by or sent to your callsign.
-
-
-
- 11.63. read (extended for sysops) (5)
-
- read <msgno> Read a message on the system
-
-
- As a sysop you may read any message on the system
-
-
- 11.64. reject/announce
-
- reject/announce [0-9] <pattern> Set a reject filter for announce
-
-
- Create an 'reject this announce' line for a filter.
-
- An reject filter line means that if the announce matches this filter
- it is passed onto the user. See HELP FILTERS for more info. Please
- read this to understand how filters work - it will save a lot of grief
- later on.
-
- You can use any of the following things in this line:-
-
-
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-
-
-
- some examples:-
-
-
-
- rej/ann by_zone 14,15,16 and not by G,M,2
-
-
-
- You can use the tag 'all' to reject everything eg:
-
-
-
- rej/ann all
-
-
-
- but this probably for advanced users...
-
-
- 11.65. reject/announce (extended for sysops) (8)
-
- reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
- version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- reject/ann by G,M,2
- reject/ann input node_default by G,M,2
- reject/ann user_default by G,M,2
-
-
-
- 11.66. reject/route (8)
-
- reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
- routing
-
-
- Create an 'reject this routing PC Protocol' line for a filter.
-
-
- An reject filter line means that if a PC16/17/19/21/24/41/50 matches
- this filter it is NOT passed thru that interface. See HELP FILTERING
- for more info. Please read this to understand how filters work - it
- will save a lot of grief later on. You can use any of the following
- things in this line:-
-
-
-
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-
-
-
- some examples:-
-
-
-
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
-
-
-
- You can use the tag 'all' to reject everything eg:
-
-
-
- rej/route all (equiv to [very] restricted mode)
-
-
-
- 11.67. reject/spots (0)
-
- reject/spots [0-9] <pattern> Set a reject filter line for spots
-
-
- Create a 'reject this spot' line for a filter.
-
- A reject filter line means that if the spot matches this filter it is
- dumped (not passed on). See HELP FILTERS for more info. Please read
- this to understand how filters work - it will save a lot of grief
- later on.
-
- You can use any of the following things in this line:-
-
-
-
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-
-
-
- For frequencies, you can use any of the band names defined in
- SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
- thus: hf/ssb. You can also just have a simple range like: 0/30000 -
- this is more efficient than saying simply: on HF (but don't get too
- hung up about that)
-
- some examples:-
-
-
-
- rej/spot 1 on hf
- rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- You can use the tag 'all' to reject everything eg:
-
-
-
- rej/spot 3 all
-
-
-
- but this probably for advanced users...
-
-
- 11.68. reject/spots (extended for sysops) (8)
-
- reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
- version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
-
-
-
- 11.69. reject/wcy (0)
-
- reject/wcy [0-9] <pattern> Set a reject WCY filter
-
-
- It is unlikely that you will want to do this, but if you do then you
- can filter on the following fields:-
-
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-
-
- There are no examples because WCY Broadcasts only come from one place
- and you either want them or not (see UNSET/WCY if you don't want
- them).
-
- This command is really provided for future use.
-
- See HELP FILTER for information.
-
-
-
- 11.70. reject/wcy (extended for sysops) (8)
-
- reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
- version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
- reject/wcy gb7djk all
-
-
- 11.71. reject/wwv (0)
-
- reject/wwv [0-9] <pattern> Set a reject WWV filter
-
-
- It is unlikely that you will want to do this, but if you do then you
- can filter on the following fields:-
-
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-
-
- for example
-
-
-
- reject/wwv by_zone 14,15,16
-
-
-
- is probably the only useful thing to do (which will only show WWV
- broadcasts by stations in the US).
-
- See HELP FILTER for information.
-
-
- 11.72. reject/wwv (extended for sysops) (8)
-
- reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
- version
-
-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
-
-
-
- reject/wwv db0sue-7 1 by_zone 4
- reject/wwv node_default all
-
- reject/wwv user_default by W
-
- 11.73. reply (0)
-
- reply Reply (privately) to the last message that you have read
- reply <msgno> Reply (privately) to the specified message
- reply B <msgno> Reply as a Bulletin to the specified message
- reply NOPrivate <msgno> Reply as a Bulletin to the specified message
- reply RR <msgno> Reply to the specified message with read receipt
-
-
- You can reply to a message and the subject will automatically have
- "Re:" inserted in front of it, if it isn't already present.
-
- You can also use all the extra qualifiers such as RR, PRIVATE,
- NOPRIVATE, B that you can use with the SEND command (see SEND for
- further details)
-
-
- 11.74. send (0)
-
- send <call> [<call> ...] Send a message to one or more callsigns
- send RR <call> Send a message and ask for a read receipt
- send COPY <msgno> <call> Send a copy of a message to someone
- send PRIVATE <call> Send a personal message
- send NOPRIVATE <call> Send a message to all stations
-
-
- All the SEND commands will create a message which will be sent either
- to an individual callsign or to one of the 'bulletin' addresses.
-
- SEND <call> on its own acts as though you had typed SEND PRIVATE, that
- is it will mark the message as personal and send it to the cluster
- node that that callsign is connected to.
-
- You can have more than one callsign in all of the SEND commands.
-
- You can have multiple qualifiers so that you can have for example:-
-
-
-
- SEND RR COPY 123 PRIVATE G1TLH G0RDI
-
-
-
- which should send a copy of message 123 to G1TLH and G0RDI and you
- will receive a read receipt when they have read the message.
-
- SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
- is an alias for SEND PRIVATE
-
-
- 11.75. set/address (0)
-
- set/address <your_address> Record your postal address
-
-
- Literally, record your address details on the cluster.
-
-
- 11.76. set/announce (0)
-
- set/announce Allow announce messages
-
-
- Allow announce messages to arrive at your terminal.
-
- 11.77. set/arcluster (5)
-
- set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
- Cluster type node
-
-
- Set the node_call as an AR-Cluster type node
-
-
- 11.78. set/baddx (8)
-
- set/baddx <call> Stop words we do not wish to see in the callsign
- field of a dx spot being propagated
-
-
- Setting a word as 'baddx' will prevent spots with that word in the
- callsign field of a DX spot from going any further. They will not be
- displayed and they will not be sent onto other nodes.
-
- The word must be wriiten in full, no wild cards are allowed eg:-
-
-
-
- set/baddx FORSALE VIDEO FR0G
-
-
-
- To allow a word again, use the following command ...
-
-
-
- unset/baddx VIDEO
-
-
-
- 11.79. set/badnode (6)
-
- set/badnode <node_call> Stop spots from this node_call being
- propagated
-
-
- Setting a callsign as a 'badnode' will prevent spots from that node
- going any further. They will not be displayed and they will not be
- sent onto other nodes.
-
- The call can be a full or partial call (or a prefix), eg:-
-
-
-
- set/badnode K1TTT
-
-
-
- will stop anything from K1TTT (including any SSID's)
-
-
-
- unset/badnode K1TTT
-
-
-
- will allow spots from him again.
-
- Use with extreme care. This command may well be superceded by
- FILTERing.
-
-
- 11.80. set/badspotter (8)
-
- set/badspotter <call> Stop spots from this callsign being propagated
-
-
- Setting a callsign as a 'badspotter' will prevent spots from this
- callsign going any further. They will not be displayed and they will
- not be sent onto other nodes.
-
- The call must be written in full, no wild cards are allowed eg:-
-
-
-
- set/badspotter VE2STN
-
-
-
- will stop anything from VE2STN. If you want SSIDs as well then you
- must enter them specifically.
-
-
-
- unset/badspotter VE2STN
-
-
-
- will allow spots from him again.
-
- Use with extreme care. This command may well be superceded by
- FILTERing.
-
-
- 11.81. set/badword (8)
-
- set/badword <word> Stop things with this word being propogated
-
-
- Setting a word as a 'badword' will prevent things like spots,
- announces or talks with this word in the the text part from going any
- further. They will not be displayed and they will not be sent onto
- other nodes.
-
- The word must be written in full, no wild cards are allowed eg:-
-
- set/badword annihilate annihilated annihilation
-
- will stop anything with these words in the text.
-
- unset/badword annihilated
-
- will allow text with this word again.
-
-
-
- 11.82. set/beep (0)
-
- set/beep Add beeps to terminal messages
-
- Add a beep to DX and other terminal messages.
-
-
- 11.83. set/bbs (5)
-
- set/bbs <call> [<call>..]Make <call> a BBS
-
-
- 11.84. set/clx (5)
-
- set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
- node
-
-
- Set the node_call as a CLX type node
-
-
- 11.85. set/debug (9)
-
- set/debug <name> Add a debug level to the debug set
-
-
- You can choose to log several different levels. The levels are
-
- chan state msg cron connect
-
- You can show what levels you are logging with the show/debug command.
-
- You can remove a debug level with unset/debug <name>
-
-
- 11.86. set/dx (0)
-
- set/dxAllow DX messages to arrive at your terminal
-
-
- You can stop DX messages with the unset/dx command
-
-
- 11.87. set/dxgrid (0)
-
- set/dxgridAllow grid squares on the end of DX messages
-
-
- Some logging programs do not like the additional information at the
- end of a DX spot. If this is the case, use the unset/dxgrid command
- to remove the grid squares.
-
-
- 11.88. set/dxnet (5)
-
- set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
- type node
-
-
- Set the node_call as a DXNet type node
-
-
- 11.89. set/echo (0)
-
- set/echo Make the cluster echo your input
-
-
- If you are connected via a telnet session, different implimentations
- of telnet handle echo differently depending on whether you are
- connected via port 23 or some other port. You can use this command to
- change the setting appropriately.
-
- You can remove the echo with the unset/echo command
-
- The setting is stored in your user profile.
-
- YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
-
-
- 11.90. set/email (0)
-
- set/email <email_address> Set email address(es) and forward your
- personals
-
-
- If any personal messages come in for your callsign then you can use
- these commands to control whether they are forwarded onto your email
- address. To enable the forwarding do something like:-
-
- SET/EMAIL mike.tubby@somewhere.com
-
- You can have more than one email address (each one separated by a
- space). Emails are forwarded to all the email addresses you specify.
-
- You can disable forwarding by:-
-
- UNSET/EMAIL
-
-
- 11.91. set/here (0)
-
- set/here Set the here flag
-
-
- Let others on the cluster know you are here by only displaying your
- callsign. If you are away from your terminal you can use the
- unset/here command to let people know you are away. This simply puts
- brackets around your callsign to indicate you are not available.
-
-
- 11.92. set/homenode (0)
-
- set/homenode <node_call> Set your home cluster
-
-
- Tell the cluster system where you normally connect to. Any Messages
- sent to you will normally find their way there should you not be
- connected. eg:-
-
-
-
- SET/HOMENODE gb7djk
-
-
-
- 11.93. set/hops (8)
-
- set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
-
-
- Set the hop count for a particular type of broadcast for a node.
-
- This command allows you to set up special hop counts for a node for
- currently: announce, spots, wwv and wcy broadcasts.
- eg:
- set/hops gb7djk ann 10
- set/hops gb7mbc spots 20
-
-
-
- Set SHOW/HOPS for information on what is already set. This command
- creates a filter and works in conjunction with the filter system.
-
-
- 11.94. set/isolate (9)
-
- set/isolate <node call> Isolate a node from the rest of the network
-
-
- Connect a node to your system in such a way that you are a full
- protocol member of its network and can see all spots on it, but
- nothing either leaks out from it nor goes back into from the rest of
- the nodes connected to you.
-
- You can potentially connect several nodes in this way.
-
- You can see which nodes are isolated with the show/isolate (1)
- command.
-
- You can remove the isolation with the command unset/isolate.
-
-
- 11.95. set/language (0)
-
- set/language <language> Set the language you wish to use
-
-
- You can select the language that you want the cluster to use.
- Currently the languages available are en (English) and nl (Dutch).
-
-
- 11.96. set/location (0)
-
- set/location <lat and long> Set your latitude and longitude
-
-
- You can set your latitude and longitude manually or alternatively use
- the set/qra command which will do the conversion for you.
-
-
-
- set/location 54 04 N 2 02 E
-
-
-
- 11.97. set/sys_location (9)
-
- set/sys_location <lat & long> Set your cluster latitude and longitude
-
-
- In order to get accurate headings and such like you must tell the
- system what your latitude and longitude is. If you have not yet done a
- SET/QRA then this command will set your QRA locator for you. For
- example:-
-
-
- SET/LOCATION 52 22 N 0 57 E
-
-
-
- 11.98. set/logininfo (0)
-
- set/logininfo Show logins and logouts of nodes and users
-
-
- Show users and nodes when they log in and out of the local cluster.
- You can stop these messages by using the unset/logininfo command.
-
-
-
- 11.99. set/lockout (9)
-
- set/lockout <call> Stop a callsign connecting to the cluster
-
-
- You can show who is locked out with the show/lockout command. To
- allow the user to connect again, use the unset/lockout command.
-
-
- 11.100. set/name (0)
-
- set/name <your_name> Set your name
-
-
- Tell the cluster what your name is, eg:-
-
-
-
- set/name Dirk
-
-
-
- 11.101. set/node (9)
-
- set/node <call> [<call> ...] Make the callsign an AK1A cluster
-
-
- Tell the system that the call(s) are to be treated as AK1A cluster and
- fed PC Protocol rather normal user commands.
-
- From version 1.41 you can also set the following types of cluster
-
-
-
- set/spider
- set/dxnet
- set/clx
- set/arcluster
-
-
-
- To see what your nodes are set to, use the show/nodes command.
-
-
-
- 11.102. set/obscount (9)
-
- set/obscount <count> <node call> Set the 'pump-up' obsolescence
- counter
-
-
- From version 1.35 onwards neighbouring nodes are pinged at regular
- intervals (see SET/PINGINTERVAL), usually 300 seconds or 5 minutes.
- There is a 'pump-up' counter which is decremented on every outgoing
- ping and then reset to the 'obscount' value on every incoming ping.
- The default value of this parameter is 2.
-
- What this means is that a neighbouring node will be pinged twice at
- (default) 300 second intervals and if no reply has been heard just
- before what would be the third attempt, that node is disconnected.
-
- If a ping is heard then the obscount is reset to the full value. Using
- default values, if a node has not responded to a ping within 15
- minutes, it is disconnected.
-
-
- 11.103. set/page (0)
-
- set/page <n> Set the number of lines per page
-
-
- Tell the system how many lines you wish on a page when the number of
- lines of output from a command is more than this. The default is 20.
- Setting it explicitly to 0 will disable paging.
-
-
-
- SET/PAGE 30
- SET/PAGE 0
-
-
-
- The setting is stored in your user profile.
-
-
- 11.104. set/password (0)
-
- set/password Set your own password
-
-
- This command only works for a 'telnet' user (currently). It will only
- work if you have a password already set. This initial password can
- only be set by the sysop.
-
- When you execute this command it will ask you for your old password,
- then ask you to type in your new password twice (to make sure you get
- it right). You may or may not see the data echoed on the screen as you
- type, depending on the type of telnet client you have.
-
-
- 11.105. set/password (9)
-
- set/password <callsign> <string> Set a users password
-
-
- The password for a user can only be set by a full sysop. The string
- can contain any characters.
-
- The way this field is used depends on context. If it is being used in
- the SYSOP command context then you are offered 5 random numbers and
- you have to supply the corresponding letters. This is now mainly for
- ax25 connections.
-
- If it is being used on incoming telnet connections then, if a password
- is set or the:
-
- set/var $main::passwdreq = 1
-
- command is executed in the startup script, then a password prompt is
- given after the normal 'login: ' prompt.
-
- The command "unset/password" is provided to allow a sysop to remove a
- users password completely in case a user forgets or loses their
- password.
-
-
- 11.106. set/pinginterval (9)
-
- set/pinginterval <time> <node call> Set the ping time to neighbouring
- nodes
-
-
- As from version 1.35 all neighbouring nodes are pinged at regular
- intervals in order to determine the rolling quality of the link and,
- in future, to affect routing decisions. The default interval is 300
- secs or 5 minutes.
-
- You can use this command to set a different interval. Please don't.
-
- But if you do the value you enter is treated as minutes up 60 and
- seconds for numbers greater than that.
-
- This is used also to help determine when a link is down at the far end
- (as certain cluster software doesn't always notice), see SET/OBSCOUNT
- for more information.
-
-
- 11.107. set/privilege (9)
-
- set/privilege <n> <call> [<call> ...] Set the privilege level on a
- call
-
-
- Set the privilege level on a callsign. The privilege levels that
- pertain to commands are as default:-
-
-
-
- 0 - normal user
- 1 - allow remote nodes normal user RCMDs
- 5 - various privileged commands (including shutdown, but not disc-
- connect), the normal level for another node.
- 8 - more privileged commands (including disconnect)
- 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
- LEVEL.
-
-
-
- If you are a sysop and you come in as a normal user on a remote
- connection your privilege will automatically be set to 0.
-
-
-
- 11.108. set/spider (5)
-
- set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
- type node
-
-
- Set the node_call as a DXSpider type node
-
-
- 11.109. set/sys_qra (9)
-
- set/sys_qra <locator> Set your cluster QRA locator
-
-
- 11.110. set/qra (0)
-
- set/qra <locator> Set your QRA locator
-
-
- Tell the system what your QRA (or Maidenhead) locator is. If you have
- not done a SET/LOCATION then your latitude and longitude will be set
- roughly correctly (assuming your locator is correct ;-). For example:-
-
-
-
- SET/QRA JO02LQ
-
-
-
- 11.111. set/qth (0)
-
- set/qth <your QTH> Set your QTH
-
-
- Tell the system where your are. For example:-
-
-
-
- set/qth East Dereham, Norfolk
-
-
-
- 11.112. set/register (9)
-
- set/register <call> Mark a user as registered
-
-
- Registration is a concept that you can switch on by executing the
-
- set/var $main::regreq = 1
-
- command (usually in your startup file)
-
- If a user is NOT registered then, firstly, instead of the normal motd
- file (/spider/data/motd) being sent to the user at startup, the user
- is sent the motd_nor file instead. Secondly, the non registered user
- only has READ-ONLY access to the node. The non-registered user cannot
- use DX, ANN etc.
-
- The only exception to this is that a non-registered user can TALK or
- SEND messages to the sysop.
-
- To unset a user use the 'unset/register' command
-
-
- 11.113. set/talk (0)
-
- set/talk Allow talk messages to be seen at your console
-
-
- Allow talk messages to arrive at your console. You can switch off
- talks with the unset/talk command.
-
-
- 11.114. set/wcy (0)
-
- set/wcy Allow WCY messages to be seen at your console
-
-
- Allow WCY information to be seen at your console. You can switch off
- WCY messages with the unset/wcy command.
-
-
- 11.115. set/wwv (0)
-
- set/wwv Allow WWV messages to be seen at your console
-
-
- Allow WWV information to be seen at your console. You can switch off
- WWV messages with the unset/wwv command.
-
-
- 11.116. set/wx (0)
-
- set/wx Allow WX messages to be seen at your console
-
-
- Allow WX information to be seen at your console. You can switch off
- WX messages with the unset/wx command.
-
-
- 11.117. show/baddx (1)
-
- show/baddxShow all the bad dx calls in the system
-
-
- Display all the bad dx callsigns in the system, see SET/BADDX for more
- information.
-
-
- 11.118. show/badnode (6)
-
- show/badnode Show all the bad nodes in the system
-
-
- Display all the bad node callsigns in the system, see SET/BADNODE for
- more information.
-
-
- 11.119. show/badspotter (1)
-
- show/badspotter Show all the bad spotters in the system
-
-
- Display all the bad spotter's callsigns in the system, see
- SET/BADSPOTTER for more information.
-
-
- 11.120. show/badword (1)
-
- show/badword Show all the bad words in the system
-
-
- Display all the bad words in the system, see SET/BADWORD for more
- information.
-
-
- 11.121. show/configuration (0)
-
- show/configuration [<node>] Show all visible nodes and their users
-
-
- This command allows you to see all the users that can be seen and the
- nodes to which they are connected. With the optional node, you can
- specify a particular node to look at.
-
- This command is normally abbreviated to: sh/c
-
- BE WARNED: the list that is returned can be VERY long
-
-
- 11.122. show/configuration/node (0)
-
- show/configuration/node Show all the nodes connected
-
-
- Show all the nodes connected locally and the nodes they have
- connected.
-
-
- 11.123. show/connect (1)
-
- show/connect Show all the active connections
-
-
- This command shows information on all the active connections known to
- the node. This command gives slightly more information than WHO.
-
-
- 11.124. show/date (0)
-
- show/date [<prefix>|<callsign>] Show the local time
-
-
- This is very nearly the same as SHOW/TIME, the only difference the
- format of the date string if no arguments are given.
-
- If no prefixes or callsigns are given then this command returns the
- local time and UTC as the computer has it right now. If you give some
- prefixes then it will show UTC and UTC + the local offset (not
- including DST) at the prefixes or callsigns that you specify.
-
-
- 11.125. show/debug (9)
-
- show/debug Show what levels of debug you are logging
-
-
- The levels can be set with set/debug
-
-
-
- 11.126. show/dx (0)
-
- show/dx [options] interrogate the spot database
-
-
- If you just type SHOW/DX you will get the last so many spots (sysop
- configurable, but usually 10).
-
- In addition you can add any number of these options in very nearly any
- order to the basic SHOW/DX command, they are:-
-
-
-
- on <band> - eg 160m 20m 2m 23cm 6mm
- on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
- <number> - the number of spots you want
- <from>-<to> - <from> spot no <to> spot no in
- the selected list
-
- <prefix> - for a spotted callsign beginning with <prefix>
- *<suffix> - for a spotted callsign ending in <suffix>
- *<string>* - for a spotted callsign containing <string>
-
- day <number> - starting <number> days ago
- day <from>-<to> - <from> days <to> days ago
-
- info <text> - any spots containing <text> in the info or remarks
-
- by <call> - any spots spotted by <call> (spotter <call>
- is the same).
-
- qsl - this automatically looks for any qsl info on the call
- held in the spot database.
-
- iota [<iota>] - If the iota island number is missing it will
- look for the string iota and anything which looks like
- an iota island number. If you specify then it will look
- for that island.
-
- qra [<locator>] - this will look for the specific locator if
- you specify one or else anything that looks like a locator.
-
-
-
- e.g.
-
-
-
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
-
-
-
- 11.127. show/dxcc (0)
-
- show/dxcc <prefix> Interrogate the spot database by country
-
-
- This command takes the <prefix> (which can be a full or partial
- callsign if desired), looks up which internal country number it is and
- then displays all the spots as per SH/DX for that country.
-
- The options for SHOW/DX also apply to this command. e.g.
-
-
-
- SH/DXCC G
- SH/DXCC W on 20m info iota
-
-
-
- 11.128. sh/dxstats (0)
-
- sh/dxstats Show the DX Statistics for last 31 days
-
-
- Show the total DX spots for the last 31 days
-
-
-
- 11.129. show/files (0)
-
- show/files [<filearea> [<string>]] List the contents of a filearea
-
-
- SHOW/FILES on its own will show you a list of the various fileareas
- available on the system. To see the contents of a particular file area
- type:-
-
-
-
- SH/FILES <filearea>
-
-
-
- where <filearea> is the name of the filearea you want to see the
- contents of.
-
- You can also use shell globbing characters like '*' and '?' in a
- string to see a selection of files in a filearea eg:-
-
-
-
- SH/FILES bulletins arld*
-
-
-
- See also TYPE - to see the contents of a file.
-
-
- 11.130. show/filter (0)
-
- show/filter Show the filters you have set
-
- Show the contents of all the filters that are set by you. This command
- displays all the filters set - for all the various categories.
-
-
- 11.131. show/filter (extended for sysops) (5)
-
- show/filter <callsign> Show the filters set by <callsign>
-
-
- A sysop can look at any filters that have been set.
-
-
- 11.132. show/hfstats (0)
-
- show/hfstats Show the HF DX Statistics for last 31 days
-
-
- Show the HF DX spots breakdown by band for the last 31 days
-
-
- 11.133. show/hftable (0)
-
- show/hftable Show the HF DX Spotter Table for your country
-
-
- Show the HF DX Spotter table for your country for the last 31 days
-
-
- 11.134. show/hops (8)
-
- show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
- node
-
-
- This command shows the hop counts set up for a node. You can specify
- which category you want to see. If you leave the category out then all
- the categories will be listed.
-
-
- 11.135. show/isolate (1)
-
- show/isolate Show a list of isolated nodes
-
-
- Show which nodes are currently set to be isolated.
-
-
- 11.136. show/lockout (9)
-
- show/lockout Show a list of excluded callsigns
-
-
- Show a list of callsigns that have been excluded (locked out) of the
- cluster locally with the set/lockout command
-
-
- 11.137. show/log (8)
-
- show/log [<callsign>] Show excerpts from the system log
-
-
- This command outputs a short section of the system log. On its own it
- will output a general logfile. With the optional callsign it will
- show output from the log associated with that callsign.
-
-
- 11.138. show/moon (0)
-
- show/moon [<prefix>|<callsign>] Show moon rise and set times
-
-
- Show the Moon rise and set times for a (list of) prefixes or
- callsigns, together with the azimuth and elevation of the sun
- currently at those locations.
-
- If you don't specify any prefixes or callsigns, it will show the times
- for your QTH (assuming you have set it with either SET/LOCATION or
- SET/QRA), together with the current azimuth and elevation.
-
- In addition, it will show the gain or loss dB relative to the nominal
- distance of 385,000Km due to the ellipsoidal nature of the orbit.
-
- If all else fails it will show the Moonrise and set times for the node
- that you are connected to.
-
- For example:-
-
-
-
- SH/MOON
- SH/MOON G1TLH W5UN
-
-
-
- 11.139. show/muf (0)
-
- show/muf <prefix> [<hours>][long] Show the likely propagation to
- <prefix>
-
-
- This command allow you to estimate the likelihood of you contacting a
- station with the prefix you have specified. The output assumes a
- modest power of 20dBW and receiver sensitivity of -123dBm (about
- 0.15muV/10dB SINAD)
-
- The result predicts the most likely operating frequencies and signal
- levels for high frequency (shortwave) radio propagation paths on
- specified days of the year and hours of the day. It is most useful for
- paths between 250 km and 6000 km, but can be used with reduced
- accuracy for paths shorter or longer than this.
-
- The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
- used to predict the MUF given the predicted flux, day of the year,
- hour of the day and geographic coordinates of the transmitter and
- receiver. This routine is reasonably accurate for the purposes here,
- with a claimed RMS error of 3.8 MHz, but much smaller and less complex
- than the programs used by major shortwave broadcasting organizations,
- such as the Voice of America.
-
- The command will display some header information detailing its
- assumptions, together with the locations, latitude and longitudes and
- bearings. It will then show UTC (UT), local time at the other end
- (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
- (Zen) and the likely signal strengths. Then for each frequency for
- which the system thinks there is a likelihood of a circuit it prints a
- value.
-
- The value is currently a likely S meter reading based on the
- conventional 6dB / S point scale. If the value has a '+' appended it
- means that it is 1/2 an S point stronger. If the value is preceeded by
- an 'm' it means that there is likely to be much fading and by an 's'
- that the signal is likely to be noisy.
-
- By default SHOW/MUF will show the next two hours worth of data. You
- can specify anything up to 24 hours worth of data by appending the no
- of hours required after the prefix. For example:-
-
-
-
- SH/MUF W
-
-
-
- produces:
-
-
-
- RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
- Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
- Location Lat / Long Azim
- East Dereham, Norfolk 52 41 N 0 57 E 47
- United-States-W 43 0 N 87 54 W 299
- UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
- 18 23 11.5 -35 mS0+ mS2 S3
- 19 0 11.2 -41 mS0+ mS2 S3
-
-
-
- indicating that you will have weak, fading circuits on top band and
- 80m but usable signals on 40m (about S3).
-
- inputting:-
-
-
-
- SH/MUF W 24
-
-
-
- will get you the above display, but with the next 24 hours worth of
- propagation data.
-
-
-
- SH/MUF W L 24
- SH/MUF W 24 Long
-
-
-
- Gives you an estimate of the long path propagation characterics. It
- should be noted that the figures will probably not be very useful, nor
- terrible accurate, but it is included for completeness.
-
-
- 11.140. show/newconfiguration (0)
-
- show/newconfiguration [<node>] Show all the nodes and users visible
-
-
- This command allows you to see all the users that can be seen and the
- nodes to which they are connected.
-
- This command produces essentially the same information as
- SHOW/CONFIGURATION except that it shows all the duplication of any
- routes that might be present It also uses a different format which may
- not take up quite as much space if you don't have any loops.
-
- BE WARNED: the list that is returned can be VERY long
-
-
- 11.141. show/newconfiguration/node (0)
-
- show/newconfiguration/node Show all the nodes connected locally
-
-
- Show all the nodes connected to this node in the new format.
-
-
- 11.142. show/node (1)
-
- show/node [<node_call> ...] Show the type and version number of nodes
-
-
- Show the type and version (if connected) of the nodes specified on the
- command line. If no callsigns are specified then a sorted list of all
- the non-user callsigns known to the system will be displayed.
-
-
- 11.143. show/prefix (0)
-
- show/prefix <callsign> Interrogate the prefix database
-
-
- This command takes the <callsign> (which can be a full or partial
- callsign or a prefix), looks up which internal country number it is
- and then displays all the relevant prefixes for that country together
- with the internal country no, the CQ and ITU regions.
-
- See also SHOW/DXCC
-
-
-
- 11.144. show/program (5)
-
- show/program Show the locations of all the included program modules
-
-
- Show the name and location where every program module was load from.
- This is useful for checking where you think you have loaded a .pm file
- from.
-
-
- 11.145. show/qra (0)
-
- show/qra <locator> [<locator>] Show the distance between locators
- show/qra <lat> <long> Convert latitude and longitude to a locator
-
-
- This is a multipurpose command that allows you either to calculate the
- distance and bearing between two locators or (if only one locator is
- given on the command line) the distance and beraing from your station
- to the locator. For example:-
-
-
-
- SH/QRA IO92QL
- SH/QRA JN06 IN73
-
- The first example will show the distance and bearing to the locator
- from yourself, the second example will calculate the distance and
- bearing from the first locator to the second. You can use 4 or 6
- character locators.
-
- It is also possible to convert a latitude and longitude to a locator
- by using this command with a latitude and longitude as an argument,
- for example:-
-
-
-
- SH/QRA 52 41 N 0 58 E
-
-
-
- 11.146. show/qrz (0)
-
- show/qrz <callsign> Show any callbook details on a callsign
-
-
- This command queries the QRZ callbook server on the internet and
- returns any information available for that callsign. This service is
- provided for users of this software by http://www.qrz.com
-
-
- 11.147. show/registered (9)
-
- show/registered [<prefix>[ Show the registered users
-
-
- 11.148. show/route (0)
-
- show/route <callsign> Show the route to <callsign>
-
-
- This command allows you to see to which node the callsigns specified
- are connected. It is a sort of inverse sh/config.
-
-
-
- sh/route n2tly
-
-
-
- 11.149. show/satellite (0)
-
- show/satellite <name> [<hours> <interval>] Show satellite tracking
- data
-
-
- Show the tracking data from your location to the satellite of your
- choice from now on for the next few hours.
-
- If you use this command without a satellite name it will display a
- list of all the satellites known currently to the system.
-
- If you give a name then you can obtain tracking data of all the passes
- that start and finish 5 degrees below the horizon. As default it will
- give information for the next three hours for every five minute
- period.
-
-
- You can alter the number of hours and the step size, within certain
- limits.
-
- Each pass in a period is separated with a row of '-----' characters
-
- So for example:-
-
-
-
- SH/SAT AO-10
- SH/SAT FENGYUN1 12 2
-
-
-
- 11.150. show/sun (0)
-
- show/sun [<prefix>|<callsign>] Show sun rise and set times
-
-
- Show the sun rise and set times for a (list of) prefixes or callsigns,
- together with the azimuth and elevation of the sun currently at those
- locations.
-
- If you don't specify any prefixes or callsigns, it will show the times
- for your QTH (assuming you have set it with either SET/LOCATION or
- SET/QRA), together with the current azimuth and elevation.
-
- If all else fails it will show the sunrise and set times for the node
- that you are connected to.
-
- For example:-
-
-
-
- SH/SUN
- SH/SUN G1TLH K9CW ZS
-
-
-
- 11.151. show/time (0)
-
- show/time [<prefix>|<callsign>] Show the local time
-
-
- If no prefixes or callsigns are given then this command returns the
- local time and UTC as the computer has it right now. If you give some
- prefixes then it will show UTC and UTC + the local offset (not
- including DST) at the prefixes or callsigns that you specify.
-
-
- 11.152. show/vhfstats (0)
-
- show/vhfstats Show the VHF DX Statistics for last 31 days
-
-
- Show the VHF DX spots breakdown by band for the last 31 days
-
-
- 11.153. show/vhftable (0)
-
- show/vhftable Show the VHF DX Spotter Table for your country
-
- Show the VHF DX Spotter table for your country for the last 31 days
-
-
- 11.154. show/wcy (0)
-
- show/wcy Show the last 10 WCY broadcasts
- show/wcy <n> Show the last <n> WCY broadcasts
-
-
- Display the most recent WCY information that has been received by the
- system
-
-
- 11.155. show/wwv (0)
-
- show/wwv Show the last 10 WWV broadcasts
- show/wwv <n> Show the last <n> WWV broadcasts
-
-
- Display the most recent WWV information that has been received by the
- system
-
-
-
- 11.156. shutdown (5)
-
- shutdown Shutdown the cluster
-
-
- Shutdown the cluster and disconnect all the users. If you have Spider
- set to respawn in /etc/inittab it will of course restart.
-
-
- 11.157. spoof (9)
-
- spoof <callsign> <command> Run commands as another user
-
-
- This is a very simple yet powerful command for the sysop. It allows
- you to issue commands as if you were a different user. This is very
- useful for the kind of things that users seem to always get wrong..
- like home_node for example.
-
-
- 11.158. stat/db (5)
-
- stat/db <dbname> Show the status of a database
-
-
- Show the internal status of a database descriptor.
-
- Depending on your privilege level you will see more or less
- information. This command is unlikely to be of much use to anyone
- other than a sysop.
-
-
- 11.159. stat/channel (5)
-
- stat/channel <callsign> Show the status of a channel on the cluster
-
-
- Show the internal status of the channel object either for the channel
- that you are on or else for the callsign that you asked for.
-
- Only the fields that are defined (in perl term) will be displayed.
-
- 11.160. stat/msg (5)
-
- stat/msg <msgno> Show the status of a message
-
-
- This command shows the internal status of a message and includes
- information such as to whom it has been forwarded, its size, origin
- etc etc.
-
-
- If no message number is given then the status of the message system is
- displayed.
-
-
- 11.161. stat/route_node (5)
-
- stat/route_node <callsign> Show the data in a Route::Node object
-
-
- 11.162. stat/route_user (5)
-
- stat/route_user <callsign> Show the data in a Route::User object
-
-
- 11.163. stat/user (5)
-
- stat/user <callsign> Show the full status of a user
-
-
- Shows the full contents of a user record including all the secret
- flags and stuff.
-
- Only the fields that are defined (in perl term) will be displayed.
-
-
- 11.164. sysop (0)
-
- sysop Regain your privileges if you login remotely
-
-
- The system automatically reduces your privilege level to that of a
- normal user if you login in remotely. This command allows you to
- regain your normal privilege level. It uses the normal system: five
- numbers are returned that are indexes into the character array that is
- your assigned password (see SET/PASSWORD). The indexes start from
- zero.
-
- You are expected to return a string which contains the characters
- required in the correct order. You may intersperse those characters
- with others to obscure your reply for any watchers. For example (and
- these values are for explanation :-):
-
-
-
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
-
-
-
- you type:-
-
-
-
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-
-
-
- They will all match. If there is no password you will still be offered
- numbers but nothing will happen when you input a string. Any match is
- case sensitive.
-
-
- 11.165. talk (0)
-
- talk <callsign> Enter talk mode with <callsign>
- talk <callsign> <text> Send a text message to <callsign>
- talk <callsign> > <node_call> [<text>] Send a text message to
- <callsign> via <node_call>
-
-
- Send a short message to any other station that is visible on the
- cluster system. You can send it to anyone you can see with a
- SHOW/CONFIGURATION command, they don't have to be connected locally.
-
- The second form of TALK is used when other cluster nodes are connected
- with restricted information. This usually means that they don't send
- the user information usually associated with logging on and off the
- cluster.
-
- If you know that G3JNB is likely to be present on GB7TLH, but you can
- only see GB7TLH in the SH/C list but with no users, then you would use
- the second form of the talk message.
-
- If you want to have a ragchew with someone you can leave the text
- message out and the system will go into 'Talk' mode. What this means
- is that a short message is sent to the recipient telling them that you
- are in a 'Talking' frame of mind and then you just type - everything
- you send will go to the station that you asked for.
-
- All the usual announcements, spots and so on will still come out on
- your terminal.
-
- If you want to do something (such as send a spot) you precede the
- normal command with a '/' character, eg:-
-
-
-
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
- /HELP talk
-
-
-
- To leave talk mode type:
-
-
-
- /EX
-
-
-
- 11.166. type (0)
-
- type <filearea>/<name> Look at a file in one of the fileareas
-
-
- Type out the contents of a file in a filearea. So, for example, in
- filearea 'bulletins' you want to look at file 'arld051' you would
- enter:-
-
-
-
- TYPE bulletins/arld051
-
-
-
- See also SHOW/FILES to see what fileareas are available and a list of
- content.
-
-
- 11.167. who (0)
-
- who Show who is physically connected locally
-
-
- This is a quick listing that shows which callsigns are connected and
- what sort of connection they have
-
-
- 11.168. wx (0)
-
- wx <text> Send a weather message to local users
- wx full <text> Send a weather message to all cluster users
-
-
- Weather messages can sometimes be useful if you are experiencing an
- extreme that may indicate enhanced conditions
-
-
- 11.169. wx (enhanced for sysops) (5)
-
- wx sysop <text> Send a weather message to other clusters only
-
-
- Send a weather message only to other cluster nodes and not to general
- users.
-
-
-
+++ /dev/null
- The DXSpider Installation Manual v1.50
- Iain Philipps, G0RDI (g0rdi@77hz.com), Ian Maude, G0VGS,
- (g0vgs@gb7mbc.net) and Charlie Carroll, K1XX,
- (k1xx@ptcnh.net)
- February 2003 revision 0.5
-
- A reference for SysOps of the DXSpider DXCluster program.
- ______________________________________________________________________
-
- Table of Contents
-
-
- 1. Linux Installation
- 1.1 Introduction
- 1.2 Preparation
- 1.3 Installing the software
- 1.4 Setting callsigns etc
- 1.5 The client program
- 1.6 Starting up for the first time
-
- 2. Linux quick installation guide
- 3. Setting up the AX25 Utilities
- 3.1 Getting Started
- 3.2 The kernel
- 3.3 Installing the RPM's
- 3.4 Configuration
- 3.5 axports
- 3.6 nrports
- 3.7 nrbroadcast
- 3.8 ax25d.conf
- 3.9 node.conf
- 3.10 Getting it all running
-
- 4. Configuration
- 4.1 Allowing ax25 connects from users
- 4.2 Allowing telnet connects from users
- 4.3 Setting up telnet connects (from 1.47 onwards)
- 4.4 Setting up for AGW Engine (1.47 onwards)
- 4.5 Setting up node connects
- 4.6 Connection scripts
- 4.7 Starting the connection
- 4.8 Telnet echo
- 4.9 Autostarting the cluster
-
- 5. Microsoft Windows Installation
- 5.1 Introduction
- 5.2 The requirements
- 5.3 The system
- 5.4 Perl
- 5.5 Additional packages
- 5.6 Getting Spider
-
- 6. Installing the software
- 6.1 Incoming telnets
- 6.2 The AGW packet engine
- 6.3 Setting up the initial user files
- 6.4 Connecting to other clusters
-
- 7. General Information
- 7.1 The crontab file
-
-
- ______________________________________________________________________
-
-
-
- 1. Linux Installation
-
- 1.1. Introduction
-
- This section describes the installation of DX Spider v1.50 on a RedHat
- Linux Distribution. Wherever possible I will try to include
- differences for other distributions.
-
-
- I am assuming a general knowledge of Linux and its commands. You
- should know how to use tar and how to edit files using your favourite
- editor.
-
-
- The crucial ingredient for all of this is Perl. Earlier versions of
- Spider required perl 5.004, however it is now STRONGLY recommended
- that you use at least version 5.005_03 as this is the version being
- used in the development of Spider.
-
-
- In addition to the standard Red Hat distribution you will require the
- following modules from http://www.cpan.org/modules/by-module/ , please
- note however that with later versions of perl, some of these modules
- may be included with the distribution. Get the modules anyway and try
- to install as below. If they complain, they are probably already a
- part of your perl distribution.
-
-
-
- o Data-Dumper-2.101.tar.gz
-
- o TimeDate-1.10.tar.gz
-
- o IO-1.20.tar.gz (for perl 5.00403 and lower)
-
- o Net-Telnet-3.03.tar.gz
-
- o Curses-1.06.tar.gz
-
- o Time-HiRes-01.20.tar.gz
-
- o Digest-SHA1-2.01.tar.gz
-
-
- Copy the CPAN modules listed above to a convenient place on your
- computer. One good place would be /usr/local/packages, and the
- instructions which follow will assume that that's where you have put
- them.
-
-
- Log in as 'root', and make sure you're at '/root' before you continue.
- Here are exactly the commands you must issue next: -
-
-
-
- # tar xvfz /usr/local/packages/Data-Dumper-2.101.tar.gz
- # cd Data-Dumper-2.101
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
- #
- # tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
- # cd TimeDate-1.10
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
- #
- # tar xvfz /usr/local/packages/IO-1.20.tar.gz
- # cd IO-1.20
- # perl Makefile.PL
- # make test
- # make install UNINST=1
- # cd ..
- #
- # tar xvfz /usr/local/packages/Net-Telnet-3.03.tar.gz
- # cd Net-Telnet-3.02
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
- #
- # tar xvfz /usr/local/packages/Curses-1.06.tar.gz
- # cd Curses-1.06
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
- #
- # tar xvfz /usr/local/packages/Time-HiRes-01.20.tar.gz
- # cd Time-HiRes-01.20
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
- #
- # tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz
- # cd Digest-SHA1-2.01
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
-
-
-
- Do not fall into the trap of thinking they're all the same, just
- because they nearly are! Pay particular attention to the instructions
- of IO, above.
-
-
-
- 1.2. Preparation
-
- I will assume that you have already downloaded the latest tarball of
- the DXSpider software and are ready to install it. I am assuming
- version 1.50 for this section but of course you would use the latest
- version.
-
-
- Login as root and create a user to run the cluster under. UNDER NO
- CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use the name
- sysop. You can call it anything you wish. Depending on your security
- requirements you may wish to use an existing user, however this is
- your own choice.
-
-
-
- # adduser -m sysop
-
-
-
- For SuSE distributions, the command would be ..
-
-
-
- # useradd -m sysop
-
-
-
- Now set a password for the user ...
-
-
-
- # passwd sysop
- # New UNIX password:
- # Retype new UNIX password:
- passwd: all authentication tokens updated successfully
-
-
-
- 1.3. Installing the software
-
- Now to unpack the DX Spider distribution, set symbolic links and group
- permissions. Copy the tarball to /home/sysop and do the following.
-
-
-
- # cd ~sysop
- # tar xvfz spider-1.50.tar.gz
- # ln -s ~sysop/spider /spider
- # groupadd -g 251 spider (or another number)
-
-
-
- If you do not have the command groupadd available to you simply add a
- line in /etc/group by hand.
-
-
-
- # vi /etc/group (or your favorite editor)
-
-
-
- You also need to add some others to the group, including your own
- callsign (this will be used as an alias) and root. The finished line
- in /etc/group should look something like this
-
- spider:x:251:sysop,g0vgs,root
-
-
- The next step is to set the permissions on the Spider directory tree
- and files ....
-
-
-
- # chown -R sysop.spider spider
- # find . -type d -exec chmod 2775 {} \;
- # find . -type f -exec chmod 775 {} \;
-
-
-
- This last step allows various users of the group spider to have write
- access to all the directories. This is not really needed just yet but
- will be useful when web interfaces start to appear.
-
-
- Finally, you need to fix the permissions on the ax25_call and
- netrom_call programs. Check where they are with the locate command
- and alter the permissions with the chmod command like this ..
-
-
-
- # chown root ax25_call netrom_call
- # chmod 4775 ax25_call netrom_call
-
-
-
- 1.4. Setting callsigns etc
-
- Now login to your machine as the user you created earlier. In my case
- that user is called sysop. Once logged in, issue the following
- commands ....
-
-
-
- $ cd /spider
- $ mkdir local
- $ mkdir local_cmd
- $ cp perl/DXVars.pm.issue local/DXVars.pm
- $ cd local
- $ vi DXVars.pm (or your favourite editor)
-
-
-
- Using the distributed DXVars.pm as a a template, set your cluster
- callsign, sysop callsign and other user info to suit your own
- environment.
-
-
-
- $mycall = "GB7DJK";
-
-
-
- This is the call sign of your cluster. If you use an SSID then
- include it here also.
-
-
-
- $myalias = "G1TLH";
-
-
-
- This is the sysop user callsign, normally your own.
-
-
- PLEASE USE CAPITAL LETTERS FOR CALLSIGNS
-
-
- Note that this a perl file which will be parsed and executed as part
- of the cluster. If you get it wrong then perl will complain when you
- start the cluster process. It is important only to alter the text of
- any section. Some of the lines look a little odd. Take this line for
- example ....
-
- $myemail = "ianmaude\@btinternet.com";
-
-
- There appears to be an extra slash in there. However this has to be
- there for the file to work so leave it in.
-
-
- DON'T alter any file in /spider/perl, they are overwritten with every
- release. Any files or commands you place in /spider/local or
- /spider/local_cmd will automagically be used in preference to the ones
- in /spider/perl EVEN while the cluster is running!
-
-
- Save the new file and change directory to ../perl ....
-
-
-
- $ cd ../perl
-
-
-
- Now type the following command which creates the basic user file with
- you as the sysop.
-
-
-
- $ ./create_sysop.pl
-
-
-
- 1.5. The client program
-
- In earlier versions of Spider, all the processes were Perl scripts.
- This was fine but with a lot of users your computer memory would soon
- be used up. To combat this a new client was written in "C". This
- client only works for incoming connects at the moment. Before you can
- use it though it has to be "made". CD to /spider/src and type make.
- You should see the output on your screen and hopefully now have a
- small C program called client. Leave it in this directory.
- 1.6. Starting up for the first time
-
- We can now bring spider up for the first time and see if all is well
- or not! It should look something like this ...
-
-
-
- $ ./cluster.pl
- DXSpider DX Cluster Version 1.50
- Copyright (c) 1998 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listener ...
- reading existing message headers
- reading cron jobs
- orft we jolly well go ...
-
-
-
- If all is well then login on another term or console as sysop and cd
- to /spider/src. Now issue the following command ...
-
-
-
- $ ./client
-
-
-
- This should log you into the cluster as the sysop under the alias
- callsign we set earlier. In this case the callsign is G0VGS. The
- cluster callsign is set in the DXVars.pm file in /spider/local. In
- this case we will assume that this was set as GB7MBC. You should
- therefore see this when you login ....
-
-
-
- G0VGS de GB7MBC 19-Nov-1999 2150Z >
-
-
-
- If you do, congratulations! If not, look over the instructions again,
- you have probably missed something out. You can shut spider down
- again with the command ....
-
-
-
- shutdown
-
-
-
- and both the cluster and the client should return to Linux prompts.
-
-
-
- 2. Linux quick installation guide
-
- This section is designed for experienced Spider sysops who want to
- install Spider from scratch. It is simply a check list of things that
- need to be done without any explanations. The name in brackets at the
- end of each line is the user that should be doing that process.
-
-
- o Login as root
-
- o Get the additional CPAN modules and install them (root)
-
- o Create the "sysop" user and set a password (root)
-
- o Put the Spider tarball in sysop and untar it (root)
-
- o ln -s sysop/spider /spider (root)
-
- o groupadd -g 251 spider (root)
-
- o Add any more users you need to the group entry in /etc/group (root)
-
- o Set the permissions on the spider tree (root)
-
- o Fix permissions on ax25_call and netrom_call (root)
-
- o Login as the sysop user
-
- o cd to /spider (sysop)
-
- o mkdir local (sysop)
-
- o mkdir local_cmd (sysop)
-
- o cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
-
- o cd to /spider/local and edit DXVars to set your details (sysop)
-
- o cd ../perl (sysop)
-
- o ./create_sysop.pl (sysop)
-
- o ./cluster.pl (sysop)
-
-
- Spider should now be running and you should be able to login using the
- client program.
-
-
- o Login as root
-
- o Enter the correct line in ax25d.conf (root)
-
- o Enter the correct line in /etc/services (root)
-
- o Enter the correct line in /etc/inetd.conf (root)
-
- o killall -HUP inetd (root)
-
-
- Spider should now be able to accept logins via telnet, netrom and
- ax25.
-
-
- o Login as sysop
-
- o Start the cluster (sysop)
-
- o set/node and type for links (sysop)
-
- o Write any connect scripts (sysop)
-
- o Edit /spider/crontab as required (sysop)
-
- o Edit any other files as necessary (sysop)
-
- o Set filters, hops and forwarding files (sysop)
-
- o Login as root
-
- o Enter the correct line in /etc/inittab (root)
-
-
- 3. Setting up the AX25 Utilities
-
- The aim of this section is not to fully cover the installation and
- configuration of all the possible ax25 modules. I will attempt to
- cover a simple installation and configure 2 serial ports as if they
- had TNC's on them. I will also show what additional configuration the
- DXSpider program requires.
-
-
- Please bear in mind that I am basing this section on a RedHat 7.1
- distribution, if you are using SuSe or any other distibution then your
- mileage may vary. I will be happy to make any changes and additions
- if you email me any errors or distribution specific requirements.
-
-
- You would probably benefit from reading the AX25-HOWTO which is much
- more comprehensive and an interesting configuration program is also
- available called ax25-config which may help you to configure things.
-
-
- The following files are extracts from the working files at GB7MBC and
- are in daily use. However, there are many ways that you can configure
- the ax25 utils, this is just the one I use, it does not mean it is
- necessarily the best or for that matter, the right way!
-
-
- 3.1. Getting Started
-
- There are 2 things you need to do initially. You need to get the 3
- files required for the ax25 installation and you need to make some
- changes to the kernel configuration.
-
-
- The first thing is to get the versions of the ax25 utils that match
- your kernel. You may also wish to get a node package of some kind.
- There are 2 main node packages in use of which I shall keep to the
- original by Tomi Manninen, OH2BNS as this is included in the ax25 rpms
- as standard. The other is AWZNode by IZ5AWZ.
-
-
- NB: The AX25 stuff in 2.4 kernels appears to have been broken until
- 2.4.18. I strongly suggest you get at least this kernel.
-
-
- For 2.4 kernels you need these files...
-
-
-
- o libax25-0.0.7-7.i386.rpm
-
- o ax25-tools-0.0.6-13.i386.rpm
-
- o ax25-apps-0.0.4-9.i386.rpm
-
-
- 3.2. The kernel
-
- First you need to add Amateur Radio Support to your kernel. This is a
- main menu item and should be easily found. Within this header you
- will find lots of options. For our purposes you need to enable
- Amateur Radio AX.25 Level 2 Protocol, NET/ROM and the Serial Port KISS
- Driver. For the purposes of this document I will work under the
- assumption that you include them in the kernel fully, ie not as
- modules. If you need to look at compiling your kernel for ax25 more
- fully, I would refer to the excellent AX25-HOWTO
-
-
- I should say at this stage that NET/ROM is not mandatory. If you do
- not use it simply ignore any instruction concerning it.
-
-
- Now recompile your kernel in the normal way and reboot your system.
-
-
- 3.3. Installing the RPM's
-
- Now install the RPM's you downloaded, libax25 first, then ax25-tools,
- then ax25-apps.
-
-
-
- rpm -ivh libax25-0.0.7-7.i386.rpm
- rpm -ivh ax25-tool-0.0.6-13.i386.rpm
- rpm -ivh ax25-apps-0.0.4-9.i386.rpm
-
-
-
- 3.4. Configuration
-
- You will find the configuration files in /etc/ax25. These consist of
- several files ...
-
-
- o axports
-
- o nrports
-
- o nrbroadcast
-
- o ax25d.conf
-
- o node.conf
-
-
- These are the main files. You will find other files but they do not
- have any use unless you are wanting to use that particular protocol,
- Rose or axip for example.
-
-
- NOTE:- before we start it is important to realise that every interface
- requires a different SSID. You should be able to follow this in the
- following examples.
- 3.5. axports
-
- This file sets up the ax25 ports you want to use. An example is below
- for a standard TNC2 ...
-
-
-
- #portname callsign baudrate paclen window description
- 2m gb7mbc-2 19200 256 2 2m port on 144.900MHz
- 4m gb7mbc-4 19200 256 2 4m port on 70.325MHz
-
-
-
- Note that the portnames have to be unique.
-
-
- The file headings are as follows ...
-
-
- portname - The name you will refer to the port by
- callsign - The ax25 callsign you want to assign to the port
- baudrate - The speed you communicate between TNC and computer
- paclen - The maximum packet length for ax25 connections
- window - The ax25 window parameter. This is like 'maxframe'
- description - A textual description of the port
-
-
-
- 3.6. nrports
-
- This file sets up the netrom ports you want to use. An example is
- below and includes a port for both cluster and node. You will see why
- we need 2 ports later ...
-
-
-
- #portname callsign alias paclen description
- netrom gb7mbc-8 BARE 236 Node Netrom Port
- netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
-
-
-
- Note that the portnames have to be unique.
-
-
- The file headings are as follows ...
-
-
- portname - The name you will refer to the port by
- callsign - This is the callsign that NET/ROM traffic from this
- port will use
- alias - The NET/ROM alias this port will be assigned
- paclen - The maximum size of NET/ROM frames transmitted
- description - A textual description of the port
-
-
-
- 3.7. nrbroadcast
-
- This file sets up the netrom broadcast qualities. An example is below
- ...
-
-
-
- #axport min_obs def_qual worst_qual verbose
- 4m 5 10 100 1
-
-
-
- The file headings are as follows ...
-
-
- axport - The port name in axports that you wish to broadcast
- NET/ROM on.
- min_obs - The minimum obsolescence value for the port
- def_qual - The default quality for the port
- worst_qual - The worst quality for the port. Any routes under
- this quality will be ignored
- verbose - This flag determines whether you will only broadcast
- your own node (0) or all known nodes (1)
-
-
-
- 3.8. ax25d.conf
-
- This file controls any incoming ax25 and NET/ROM connections and
- steers them to the relevant program. There are lots of configuration
- options you can set here, however they are well covered in the
- AX25-HOWTO. For our purposes I will show a typical set of parameters.
- An example is below ...
-
-
-
- [gb7mbc-0 via 2m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
-
- [gb7mbc-1 via 2m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
-
- [gb7mbc-0 via 4m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
-
- [gb7mbc-1 via 4m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
-
- <netrom2>
- parameters 1 10 * * * 3 *
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
-
- <netrom>
- parameters 1 10 * * * 3 *
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
-
-
-
- There are a few things to take note of here. Firstly, all ax25
- sections are wrapped in [ ] and all NET/ROM sections are wrapped in <
- >. Secondly you should be able to see that anyone who forgets to set
- their callsign in a TNC and tries to connect with the standard NOCALL
- set into their TNC will not connect, the 'L' means 'lockout'. Lastly
- and importantly, notice the order of the sections. They are all done
- in interface order.
-
-
- You should be able to see that the normal line for access to the
- cluster is like this ..
-
-
-
- default * * * * * * - sysop /spider/src/client client %u ax25
-
-
-
- however, if you wish your users to be able to use SSID's on their
- callsigns ..
-
-
-
- default * * * * * * - sysop /spider/src/client client %s ax25
-
-
-
- For most purposes this is not desirable. The only time you probably
- will need this is when you need to allow other cluster nodes that are
- using SSID's in. In this case it would probably be better to use the
- first example and then add a specific line for that node like this:
-
-
-
- GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
- default * * * * * * - sysop /spider/src/client client %u ax25
-
-
-
- 3.9. node.conf
-
- For those of you that wish to run the node, you need to set up the
- node.conf file. There are a couple of additional files, node.perms is
- very similar to the way ftp permissions are set up in NOS systems and
- node.motd is the message anyone logging into the node will get. The
- node.conf file sets all the parameters of the node as you would
- expect. An example is below ...
-
-
-
- # /etc/ax25/node.conf - LinuxNode configuration file
- #
- # see node.conf(5)
-
- # Idle timeout (seconds).
- #
- IdleTimeout 1800
-
- # Timeout when gatewaying (seconds).
- #
- ConnTimeout 40000
-
- # Visible hostname. Will be shown at telnet login.
- #
- HostName gb7mbc.ampr.org
-
- # ReConnect flag.
- #
- ReConnect off
-
- # "Local" network.
- #
- #LocalNet 44.139.8.48/32
-
- # Command aliases. See node.conf(5) for the meaning of the uppercase
- # letters in the name of the alias.
- #
- ##Alias CAllbook 'telnet %{2:44.17.0.53} 1235 %1 s'
- #Alias CONVers 'telnet %{2:oh2ti} 3600 "/n %u %{1:139}\n/w *"'
- #Alias CLuster 'c hkiclh'
- Alias CONV "telnet lurpac 3600"
- Alias BBS "c 70cm gb7crv"
- Alias DXC "telnet localhost 9000"
- Alias MUD "telnet homer 4000"
- ##Alias TEMP "finger temp@mary.g6phf"
- ##Alias TNOS "c ip1 gb7mbc-5"
- ##Alias TUtor "telnet gb7mbc 3599"
-
- # Hidden ports.
- #
- #HiddenPorts 2
-
- # External commands. See node.conf(5) for the meaning of the uppercase
- # letters in the name of the extcmd.
- #
- # Flags: 1 Run command through pipe
- # 2 Reconnected flag
- #
- #ExtCmd TPM 3 nobody /usr/bin/finger finger tpm
- #ExtCmd ECho 1 nobody /bin/echo echo \%U \%u \%S \%s \%P \%p \%R \%r \%T \%t \%\% \%0 \%{1:foobar} \%{2} \%3 \%4 \%5
-
- # Node ID.
- #
- NodeId "\nBARE:GB7MBC-1"
- #NodeId \033[01;31m***\033[0m
-
- # Netrom port name. This port is used for outgoing netrom connects.
- #
- NrPort netrom
-
- # Logging level
- #
- LogLevel 3
-
- # The escape character (CTRL-T)
- #
- EscapeChar ^T
-
- # Resolve ip numbers to addresses?
- #
- ResolveAddrs off
-
- # Node prompt.
- #
- #NodePrompt "\n"
- #NodePrompt "%s@%h \%i> "
- NodePrompt "\nBARE:GB7MBC-1 \%i > "
- #NodePrompt "\a\033[36m%U\033[0m de \033[01;32m#LNODE\033[0m:\033[01;33mOH2BNS-10\033[0m> "
-
-
-
- This should be fairly obvious I hope.
-
-
- 3.10. Getting it all running
-
- Ok, now we have all the relevant files configured, the next step is to
- get it all running.
-
-
- The first thing to do is attach the TNC's. Your TNC's should be in
- KISS mode and connected to the serial ports involved.
-
-
- You now use the 'kissattach' command to connect the TNC's to the
- system like this ...
-
-
-
- kissattach /dev/ttyS0 2m 44.131.96.199
- kissattach /dev/ttyS1 4m 44.131.96.199
-
-
-
- Assuming that 44.131.96.199 is your IP address. The devices ttyS0 and
- ttyS1 are com1 and com2 respectively. Now we can set some parameters
- ...
-
-
-
- kissparms -p 2m -t 150 -l 150 -s 50 -r 50
- kissparms -p 4m -t 150 -l 150 -s 50 -r 50
-
-
-
- The command 'man kissparms' will give you the explanation of the
- switches.
-
-
- Now we need to attach the NET/ROM ports in the same way ...
-
-
-
- nrattach netrom
- nrattach netrom2
-
- All of the above can be put in a file and called from
- /etc/rc.d/rc.local. Put all the above commands in a file called
- rc.ax25 and put a line in rc.local to call it.
-
-
- Now you can start the daemons that set everything in motion ...
-
-
-
- ax25d
- netromd -i
-
-
-
- All should now be running. All that remains is to get the node
- working for telnet connections. If nothing else, this will allow you
- to connect to the node yourself to check on connection status etc.
- There are 2 files that need to be edited.
-
-
- First edit /etc/services and add
-
-
-
- node 3000/tcp #OH2BNS's Node Software
-
-
-
- Assuming you want it to run on port 3000
-
-
- Now cd /etc/xinetd.d and edit a new file called node. It should look
- like this ...
-
-
-
- # default: on
- # unencrypted username/password pairs for authentication.
- service node
- {
- socket_type = stream
- wait = no
- user = root
- server = /usr/sbin/node
- log_on_failure += USERID
- disable = no
- }
-
-
-
- You now need to restart the xinetd daemon. First find out what the
- PID is like so ..
-
-
-
- ps auxw |grep xinetd
-
-
-
- You will get a reply something like this ...
-
-
-
- root 592 0.0 0.1 2256 620 ? S Feb07 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid
-
-
-
- The PID or Process ID is 592 in this case so now we can issue the
- command ...
-
-
-
- kill -HUP 592
-
-
-
- All should now be operational and you should be able to log into the
- node by using a telnet session to the relevant port, like so ...
-
-
-
- telnet localhost 3000
-
-
-
- If that works, you are just about there. you should (assuming you
- have radios connected to the TNC's) be able to connect out to other
- stations and receive incoming ax25 and netrom connections.
-
-
- 4. Configuration
-
- 4.1. Allowing ax25 connects from users
-
- This is dealt with in the previous section
-
-
- 4.2. Allowing telnet connects from users
-
-
- >From version 1.47 there is a new (more efficient) way of doing this
- (see next section) but, if you prefer, the method of doing it
- described here will continue to work just fine.
-
-
- Allowing telnet connections is quite simple. Firstly you need to add
- a line in /etc/services to allow connections to a port number, like
- this ....
-
-
-
- spdlogin 8000/tcp # spider anonymous login port
-
-
-
- Then add a line in /etc/inetd.conf like this ....
-
- spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
-
-
-
- Once this is done, you need to restart inetd like this ....
-
-
-
- killall -HUP inetd
-
-
-
- Now login as sysop and cd spider/src. You can test that spider is
- accepting telnet logins by issuing the following command ....
-
-
-
- ./client login telnet
-
-
-
- You should get a login prompt and on issuing a callsign, you will be
- given access to the cluster. Note, you will not get a password login.
- There seems no good reason for a password prompt to be given so it is
- not asked for.
-
-
- Assuming all is well, then try a telnet from your linux console ....
-
-
-
- telnet localhost 8000
-
-
-
- You should now get the login prompt and be able to login as before.
-
-
- 4.3. Setting up telnet connects (from 1.47 onwards)
-
- >From version 1.47 you can choose to allow the perl cluster.pl program
- to allow connections directly (i.e. not via the /spider/src/client
- interface program). If you are using Windows then this is the only
- method available of allowing incoming telnet connections.
-
-
- To do this you need first to remove any line that you may previously
- have set up in /etc/inetd.conf. Remember to:-
-
-
-
- killall -HUP inetd
-
-
-
- to make the change happen...
-
-
- Having done that, you need to copy the file /spider/perl/Listeners.pm
- to /spider/local and then edit it. You will need to uncomment the line
- containing "0.0.0.0" and select the correct port to listen on. So that
- it looks like this:-
-
-
-
- @listen = (
- ["0.0.0.0", 8000],
- );
-
-
-
- As standard, the listener will listen on all interfaces
- simultaneously. If you require more control than this, you can
- specify each interface individually:-
-
-
-
- @listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
- );
-
-
-
- This will only be successful if the IP addresses on each interface are
- static. If you are using some kind of dynamic IP addressing then the
- 'default' method is the only one that will work.
-
-
- Restart the cluster.pl program to enable the listener.
-
-
- One important difference with the internal listener is that no echoing
- is done by the cluster program. Users will need to set 'local-echo' on
- in their telnet clients if it isn't set automatically (as per the
- standards). Needless to say this will probably only apply to Windows
- users.
-
-
- 4.4. Setting up for AGW Engine (1.47 onwards)
-
- AGW Engine is a Windows based ax25 stack. You can connect to an AGW
- engine from Linux as well as Windows based machines.
-
-
- In order to enable access to an AGW Engine you need to copy
- /spider/perl/AGWConnect.pm to /spider/local and edit it. Specifically
- you must:-
-
-
- o set $enable to 1.
-
- o set $login and $passwd to the values set up in your AGW
- installation. If you haven't set any there, then you should not
- touch these values.
-
-
- o You can connect to a remote AGW engine (ie on some other machine)
- by changing $addr and $port appropriately.
-
- o Restart the cluster.pl program
-
-
-
- 4.5. Setting up node connects
-
- In order to allow cluster node connections, spider needs to know that
- the connecting callsign is a cluster node. This is the case whether
- the connect is incoming or outgoing. In spider this is a simple task
- and can be done in runtime.
-
-
- Later versions of Spider can distinguish different software and treat
- them differently. For example, the WCY beacon cannot be handles by
- AK1A type nodes as AK1A does not know what to do with PC73. There are
- 4 different types of node at present and although they may not have
- any major differences at the moment, it allows for compatibility. The
- 4 types are ...
-
-
-
- set/node (AK1A type)
- set/spider
- set/dxnet
- set/clx
-
-
-
- For now, we will assume that the cluster we are going to connect to is
- an AK1A type node.
-
-
- Start up the cluster as you did before and login as the sysop with
- client. The cluster node I am wanting to make a connection to is
- GB7BAA but you would obviously use whatever callsign you required. At
- the prompt type ...
-
-
-
- set/node gb7baa
-
-
-
- The case does not matter as long as you have a version of DXSpider
- later than 1.33. Earlier versions required the callsign to be in
- upper case.
-
-
- That is now set, it is as simple as that. To prove it, login on yet
- another console as sysop, cd to spider/src and issue the command ...
-
-
-
- ./client gb7baa (using the callsign you set as a node)
-
-
-
- You should get an initialisation string from DXSpider like this ...
-
-
-
- ./client gb7baa
- PC38^GB7MBC^~
-
-
-
- If the callsign you just set up as a cluster node is for an incoming
- connect, this is all that needs to be done. If the connection is to
- be outgoing then a connection script needs to be written.
-
-
- Sometimes you make a mistake... Honest, it does happen. If you want
- to make a node back to being a normal user, regardless of what type it
- is, do:
-
-
-
- unset/node gb7baa
-
-
-
- 4.6. Connection scripts
-
- Because DXSpider operates under Linux, connections can be made using
- just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
- possible examples. Connect scripts live in the /spider/connect
- directory and are simple ascii files. Writing a script for
- connections is therefore relatively simple.
-
-
- The connect scripts consist of lines which start with the following
- keywords or symbols:-
-
-
-
- # All lines starting with a # are ignored, as are completely blank
- lines.
-
-
- timeout
- timeout followed by a number is the number of seconds to wait
- for a command to complete. If there is no timeout specified in
- the script then the default is 60 seconds.
-
-
- abort
- abort is a regular expression containing one or more strings to
- look for to abort a connection. This is a perl regular
- expression and is executed ignoring case.
-
-
- connect
- connect followed by ax25, agw (for Windows users) or telnet and
- some type dependent information. In the case of a telnet
- connection, there can be up to two parameters. The first is the
- ip address or hostname of the computer you wish to connect to
- and the second is the port number you want to use (this can be
- left out if it is a normal telnet session). In the case of an
- ax25 session then this would normally be a call to ax25_call or
- netrom_call as in the example above. It is your responsibility
- to get your node and other ax25 parameters to work before going
- down this route!
-
-
- ' line in a chat type script. The words/phrases normally come in
- pairs, either can be empty. Each line reads input from the
- connection until it sees the string (or perl regular expression)
- contained in the left hand string. If the left hand string is
- empty then it doesn't read or wait for anything. The comparison
- is done ignoring case. When the left hand string has found what
- it is looking for (if it is) then the right hand string is sent
- to the connection. This process is repeated for every line of
- chat script.
-
-
- client
- client starts the connection, put the arguments you would want
- here if you were starting the client program manually. You only
- need this if the script has a different name to the callsign you
- are trying to connect to (i.e. you have a script called other
- which actually connects to GB7DJK-1 [instead of a script called
- gb7djk-1]).
-
-
- There are many possible ways to configure the script but here are
- three examples, one for a NETRom/AX25 connect, one for AGW engines and
- one for tcp/ip.
-
-
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
-
-
-
- timeout 60
- abort (Busy|Sorry|Fail)
- # this does exactly the same as the previous example
- # the '1' is the AGW port number to connect thru for g1tlh
- connect agw 1 g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
-
-
-
- timeout 15
- connect telnet dirkl.tobit.co.uk
- # tell GB7DJK-1 that it is connected to GB7DJK
- # you can leave this out if you call this script 'gb7djk'
- client gb7djk telnet
-
-
- Both these examples assume that everything is set up properly at the
- other end. You will find other examples in the /spider/examples
- directory.
-
-
- 4.7. Starting the connection
-
- You start the connection, from within a sysop enabled cluster login,
- by typing in the word connect followed by a script name like this ....
-
-
-
- G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
- connection to GB7DJK-1 started
- G0VGS de GB7MBC 13-Dec-1998 2043Z >
-
-
-
- This will start a connection using the script called gb7djk-1. You
- can follow the connection by watching the term or console from where
- you started cluster.pl. From version 1.47 onwards, you will need to
- set/debug connect first. You should see something like this ...
-
-
-
- <- D G1TLH connect gb7djk-1
- -> D G1TLH connection to GB7DJK-1 started
- -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
- timeout set to 15
- CONNECT sort: telnet command: dirkl.tobit.co.uk
- CHAT "login" -> "gb7djk"
- received "
- Red Hat Linux release 5.1 (Manhattan)
- Kernel 2.0.35 on an i586
- "
- received "login: "
- sent "gb7djk"
- CHAT "word" -> "gb7djk"
- received "gb7djk"
- received "Password: "
- sent "gb7djk"
- Connected to GB7DJK-1, starting normal protocol
- <- O GB7DJK-1 telnet
- -> B GB7DJK-1 0
- GB7DJK-1 channel func state 0 -> init
- <- D GB7DJK-1
- <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
- <- D GB7DJK-1 PC38^GB7DJK-1^~
- <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
- 0 00:00^5447^~
- etc
-
-
-
- With later versions of Spider there is a set/login command for users.
- This tells them when a user or node logs in or out. If you do not add
- a line to your scripts after the final line (or before the client line
- which should always be last if needed) then the login/logout
- information will be sent to users before the login actually completes.
- This means if a node is unreachable, it will continue sending logins
- and logouts to users even though it is not actually connecting. To
- avoid this use the following line ...
- In a script, this might look like ...
-
-
-
- timeout 35
- abort (Busy|Sorry|Fail)
- connect telnet mary 3000
-
-
-
- 4.8. Telnet echo
-
- Cluster links in particular suffer greatly from the presence of telnet
- echo. This is caused by the telnet negotiation itself and can create
- at worst severe loops. At best it creates unnecessary bandwidth and
- large logfiles! There are things that can be done to limit this
- problem but will not always work dependent on the route taken to
- connect.
-
-
- Telnet echo itself should only be a problem if the connection is being
- made to the telnet port (23). This port uses special rules that
- include echo negotiation. If the connection is to a different port,
- such as 7300, this negotiation does not happen and therefore no echo
- should be present.
-
-
- Sometimes it is not possible to make a direct connection to another
- node and this can cause problems. There is a way of trying to
- suppress the telnet echo but this will not always work, unfortunately
- it is difficult to be more specific. Here is an example of what I
- mean ...
-
-
-
- timeout 35
- abort (Busy|Sorry|Fail)
- connect telnet mary.lancs.ac.uk
-
-
-
- So, the first connection is made by Spider. This is fine as Spider
- uses the Net_Telnet script from within perl. This actually uses TCP
- rather than TELNET so no negotiation will be done on the first
- connection. Once connected to mary.lancs.ac.uk, the command is sent
- to suppress echo. Now a telnet is made to a cluster node that is
- accepting connections on port 23. The problem with this link is that
- the negotiation is made by the remote machine, therefore you have no
- control over it. The chances are that this link will create echo and
- there will be no way you can stop it.
-
-
-
- 4.9. Autostarting the cluster
-
- Ok, you should now have DXSpider running nicely and allowing connects
- by cluster nodes or users. However, it has to be shutdown and
- restarted manually. It would be much easier to have it start
- automatically.
-
-
-
- This is not only a way to start the cluster automatically, it also
- works as a watchdog, checking the sanity of DXSpider and respawning it
- should it crash for any reason. Before doing the following, shutdown
- the cluster as you did earlier.
-
-
- Login as root and bring up the /etc/inittab file in your favourite
- editor. Add the following lines to the file near the end ...
-
-
-
- ##Start DXSpider on bootup and respawn it should it crash
- DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-
-
-
- This line works fine for RedHat distributions. It is also fine for
- SuSE up to 7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like
- this ...
-
-
-
- DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-
-
-
- The line required for Slackware distributions is slightly different.
- My thanks to Aurelio, PA3EZL for this information.
-
-
-
- DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
-
-
-
- This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
- restart it should it crash for any reason.
-
-
- NB: It should be noted that /dev/tty7 is only an example. Some SuSE
- systems will only accept upto tty6. It really does not matter which
- tty you run it on.
-
-
- As root type the command telinit q. DXSpider should start up
- immediately. You will see the output on tty7 and if you login as
- sysop you should find everything running nicely.
-
-
- 5. Microsoft Windows Installation
-
- 5.1. Introduction
-
- IMPORTANT:
-
- What you'll be left with once you've followed these instructions is
- (hopefully) a working DX Spider v1.50 system that is capable of
- accepting or originating "internet" connections, plus inbound and
- outbound AX.25 and TCP/IP radio connections.
-
- On the other hand, you may have an enquiring mind, or better yet, may
- be looking for a useful way of connecting your current (perhaps) AK1A
- cluster "to the internet" via some networking mechanism (BPQEther,
- etc) or other. I won't be producing instructions for the latter case,
- because I don't have an AK1A to play with. But someone might ...
-
- Whatever, this document is intended to get you started with DX Spider
- in a Microsoft Windows (TM) environment. It's not intended to teach
- you anything other than how to perform a minimum configuration of a DX
- Spider installation and have it able to connect across "the internet"
- to other DX Clusters, while accepting inbound TELNET and radio
- connections.
-
-
- 5.2. The requirements
-
- The very first things you're going to need are (in order of
- importance):-
-
-
- o A cup of good, strong tea
-
- o A supported Windows platform with an internet connection so you can
- download the necessary software bits and bobs directly to it. There
- are other ways, but this is preferable.
-
- o Another cup of good, strong tea
-
- o If all goes according to plan, about an hour to spare
-
- o Plenty of good, strong tea
-
-
- 5.3. The system
-
- The platform I used to generate these instructions was a "vanilla"
- Microsoft Windows Me 4.90.3000 system, with a 700MHz AMD Athlon
- processor and 96 Mb memory. I've also personally verified that it runs
- on my laptop (Pentium 266MHz, 32 Mb memory, Windows 98 SE v4.10.2222
- A) and a computer that I assembled from a random pile of junk (AMD
- K6-2 333MHz, 64 Mb memory, Windows 98 v4.10.1998). As a result, I have
- reason to believe that what I'm about to describe will perform equally
- on any 32-bit MS Windows environment with 32 Mb of memory.
-
- Because of the changes that have recently been made to the core
- "cluster.pl" module and the introduction of a very lightweight
- "winclient.pl", I have a sneaking suspicion that this will now run on
- any platform that has reasonably complete support for Perl. Is there
- someone out there with both an enquiring mind and (say) a Macintosh,
- for instance?
-
- Please bear in mind, though, that my instructions relate solely to how
- to get this going under a Microsoft Windows environment, and I have
- zero intention of trying to make them say otherwise.
-
-
- 5.4. Perl
-
- Install your chosen Perl environment. Unless you have a very good
- reason for not doing so, I strongly suggest that you use ActivePerl
- v5.6. For my testing & development, I used build 623. (A recent
- installation used the newer ActivePerl v5.6.1, build 633 without any
- noticable difficulty.) You can get this from:
- http://www.activestate.com/Products/ActivePerl/Download.html
-
-
- The link takes you to an initial page of System Requirements and
- Software Prerequisites. If you do not have it already installed, you
- can download and install the Windows Installer 2.0 for a Win98
- installation. Be forewarned, you will have to reboot your PC at the
- completion of the installer's installation.
-
- If you already have the installer on your PC, simply click on the Next
- arrow at the bottom of the page. Two clicks will finally get you to
- the actual download page. The MSI version of Build 633 is now 8.6MB
- in size, so make that a big cup of tea or coffee if you're on a slow
- dial-up connection.
-
- During installation, please ensure that you do choose the options to
- "Add Perl to the PATH environment variable" and "Create Perl file
- extension association"; it will make your life so much easier. Once
- the installation is finished, be sure to reboot your PC. You probably
- won't be told anywhere else that this needs to be done now, but it
- does. Really.
-
- Once you've rebooted, open a "DOS box" (Start > Run > command might do
- it, if you can't find it elsewhere) and from wherever it lands, type
- PERL -v <ENTER> (it's better if that's a lower-case be rewarded with
- some interesting information about your Perl installation. If you're
- not, you must go back to the beginning and discover what went wrong
- and fix it. It's pointless to proceed unless this simple check is
- passed. Assuming it did work, you may now move on.
-
-
- 5.5. Additional packages
-
- Some extensions ("packages") need to be added to the base Perl
- distribution, and we'll do this next. If you're using the Perl I
- recommended, and don't know any better for yourself, then just blindly
- following these instructions will work just fine. If that didn't
- describe you, then you're on your own.
-
- Visit the following URL:
-
- http://www.activestate.com/PPMPackages/zips/6xx-builds-only/
-
- and download the following files:-
-
-
-
- Data-Dumper.zip
- Net-Telnet.zip
- TimeDate.zip
- Time-HiRes.zip
- DB_File.zip
-
-
-
- If this is a new installation, now would also be a good time to
- install a copy of WinZip on your PC. Make yourself a convenient
- directory to unpack all of these zip files into (I put mine in
- "D:\ppm>" but "C:\ppm" works just as well.) and do the following (the
- bits you type in are blue ). You can upzip all of the files into the
- same directory. When prompted, simply overwrite the Readme file from
- each zip package. Note that where these files land will be directly
- related to where you chose to install your ActivePerl (mine, as you
- can probably guess from what follows, went into "D:\Perl"):-
-
-
-
- D:\ppm>ppm install Data-Dumper.ppd
- Installing package 'Data-Dumper.ppd'
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
- Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
- Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
- Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
- D:\ppm>
-
-
-
- I'm not going to bother you with exhaustive details of the rest of
- them, but suffice it to say you need to:
-
-
-
- ppm install DB_File.ppd
- ppm install Net-Telnet.ppd
- ppm install TimeDate.ppd
- ppm install Time-HiRes.ppd
-
-
-
- If all that seemed to work OK, time to move along. Before anyone who
- is familiar with PPM tells me that we didn't need to download and keep
- those files locally, I knew that. I also knew that PPM is sometimes
- awkward to configure via firewalls, and that sometimes the
- repositories don't always work the way we'd hope. I do it that way
- because it suits me.
-
-
- 5.6. Getting Spider
-
- Get the current version of the DX Spider distribution. This needs to
- be v1.50 or later. You've got two ways (currently) of getting this;
- either get a CVS update from sourceforge (if you don't know what this
- is, then it isn't for you) or get the latest "official" release from:
-
- http://www.dxcluster.org/download/index.html
-
- or if you want the lastest snapshot of CVS version (which is produced
- every night):-
-
- http://www.dxcluster.org/download/CVSlatest.tgz
-
- This is generally the best one to go for as it is completely up to
- date. However, there is always the very slight chance that it might
- unstable. Generally, there will be a note on the website if this is
- the case.
-
-
- The only difference between "CVSlatest.tgz" and the latest "official"
- release version is that it is more up to date. Do not confuse the
- "CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -
- they are two quite different things. "Downloading from Sourceforge
- with CVS" is explained in a section within the Admin manual.
-
-
- If you go down the CVS route (ie installing WinCVS as explained in the
- Admin manual and downloaded from sourceforge), then everything will be
- nicely installed on your local disk. If you got the CVSlatest.tgz
- file, unzip (winzip) it to "C:\". This is an important point since
- paths are included within the .tgz file. Make sure you unzip to the
- root directory of whichever drive you use... "C:\" or "D:\" or ..,
- not "C:\spider." If you double click on CVSlatest.tgz, WinZip should
- open with a dialogue box that says the Archive contains a single file
- (CVSlatest.tar) and asks whether WinZip should decompress it to a
- temporary fold and then open it. Say "Yes" and then you will get the
- typical Classical WinZip listing of files ready for extraction.
- Remember, extract them to your desired root directory ("C:\" or "D:\"
- or ...). The following examples assume that you put it on drive
- "C:\", for convenience.
-
-
- 6. Installing the software
-
- At this point you will need to create 2 additional directories under
- "C:\Spider." Make directories "C:\spider\local" and
- "C:\spider\local_cmd". If "C:\spider" is missing, go back and figure
- out why, because it shouldn't be.
-
- Now create your own local copy of the DXVars.pm file by:-
-
-
-
- copy c:\spider\perl\DXVars.pm.issue
- c:\spider\local\DXVars.pm
-
-
-
- Now you'll need to edit this file using a text editor like Notepad. If
- nothing else, you can simply
-
-
-
- cd \spider\local
-
-
-
- and then
-
-
-
- notepad DXVars.pm
-
-
-
- to bring up an editor window containing the file. As an absolute
- minimum you must adjust the following items in DXVars.pm:-
-
-
- o $mycall - Should hold the callsign of your DX Cluster
-
- o $myname - The SysOp's first name
-
- o $myalias - the SysOp's callsign. Cannot be the same as $mycall!
-
- o $myqth - The station's geographical location (QTH).
-
- o $mylatitude - The station latitude in degrees and decimal fractions
-
- o $mylongitude - The station longitude in degrees and decimal
- fractions
-
-
- o $mylocator - The Maidenhead (or QRA) locator of the station
-
- You really also ought to update the $myqth and $myemail variables. And
- unless you are absolutely certain you know what you're doing, you
- should change nothing else in this file. Note that if you use an "@"
- or a "$" character in one of the above strings (typically in $myemail)
- you must write them as "\@" or "\$".
-
-
- 6.1. Incoming telnets
-
- If you want to enable inbound "TELNET" connections (or you are running
- Windows 98, NT, 2000 or XP), you've got a little more work to do. From
- a handy "DOS box" that's not doing anything else, do the following:-
-
-
-
- copy \spider\perl\Listeners.pm \spider\local
- cd \spider\local
- notepad listeners.pm
-
-
-
- The following line need attention:-
-
-
-
- # ["0.0.0.0", 7300],
-
-
-
- On my machine, I've simply uncommented the "0.0.0.0" entry by removing
- the '#' from the front of the line.
-
- You MUST carry out this step if you are running on a Windows 98, NT,
- 2000 or XP based system
-
- If you don't have a static hostname for your machine, and you intend
- to allow folk to connect to your machine across the internet, then I'd
- suggest you pay a visit to www.dyndns.org and create one for yourself.
- While it's free, it will take a modest amount of effort on your part
- to read, understand and implement what needs to be done to set this
- up.
-
-
- If your machine is connected to the internet and you don't want to
- allow your machine to be visible to the outside world you should
- change the "0.0.0.0" to "127.0.0.1" [which is "localhost"]. This will
- then only allow connections from inside your machine. As was said
- earlier: if you aren't running Win9x (or you want to use DXTelnet or
- somesuch), then you need to have the machine listening at least to
- "127.0.0.1" ("0.0.0.0" means all IP addresses).
-
-
- 6.2. The AGW packet engine
-
- On the assumption that you'll be using the SV2AGW Packet Engine to
- interface your radios to the cluster, it would be a good idea to
- download the Packet Engine software! You can get this software from:
-
- http://www.raag.org/sv2agw/agwpe.zip
-
- Depending upon your TNCs, you may also need to get:
-
- http://www.raag.org/sv2agw/drivers.zip
-
- A couple of the tools:
-
- http://www.raag.org/sv2agw/agwterm.zip
-
- http://www.raag.org/sv2agw/agwmonitor.zip
-
- will also help with troubleshooting of the RF links themselves.
-
- Install and configure AGWPE. You should now create your own local
- copy of AGWConnect.pm by:-
-
-
-
- copy c:\spider\perl\AGWConnect.pm
- c:\spider\local\AGWConnect.pm
-
-
-
- and then
-
-
-
- notepad AGWConnect.pm
-
-
-
- to bring up an editor window containing the file. You must consider
- adjusting the following items in AGWConnect.pm:-
-
-
- o $enable - set to '1' to enable AGWPE interface
-
- o $login - the login ID you chose when you set up the SV2AGW
- security :-)
-
- o $passwd - password that matches $login
-
- The login ID and passwd only need to be set if you are accessing AGW
- separately via its web interface. This interface is normally not
- needed for use with DXSpider.
-
-
- 6.3. Setting up the initial user files
-
- Next you need to create the initial user files, etc. A tool is
- supplied which will do this for you. To run the tool:-
-
-
-
- cd \spider\perl
- perl create_sysop.pl
-
-
-
- If all goes according to plan, you will see no output from this
- program, and after a brief wait, your DOS prompt will be returned.
-
- Depending on how brave you are, you might now care to try the
- following:-
-
-
- perl cluster.pl
-
-
-
- If you did everything you were told, your DOS window will now hold a
- display which looks something like:-
-
-
-
- DXSpider DX Cluster Version 1.50
- Copyright (c) 1998-2002 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listeners ...
- Internal port: localhost 27754
- load badwords: Ok
- reading in duplicate spot and WWV info ...
- reading existing message headers ...
- load badmsg: Ok
- load forward: Ok
- load swop: Ok
- @msg = 0 before delete
- @msg = 0 after delete
- reading cron jobs ...v cron: reading /spider/cmd/crontab
- cron: adding 1 0 * * 0
- DXUser::export("$main::data/user_asc")
- reading database descriptors ...
- doing local initialisation ...
- orft we jolly well go ...
- queue msg (0)
-
-
-
- Now, if that's what you've got, you are very nearly home and dry (in
- as far as these particular experiments are concerned, anyhow)
-
- If you are running Windows 9x you can access your new cluster (from
- the local machine) by finding yourself another "DOS box" and doing the
- following:-
-
-
-
- cd \spider\perl
- perl winclient.pl
-
-
-
- If you are running Windows NT, 2000 or XP then winclient.pl does not
- work. We don't know why other than this seems to be some kind of
- incomaptibility in perl. You can achieve the same thing by telnetting
- to the port you defined in Listeners.pm (7300 as default), thus:-
-
-
-
- Menu->Start->Run
- telnet localhost 7300
-
-
-
- On getting the login: prompt, enter your sysop callsign (the one you
- put in DXVars.pm as $myalias).
- I would recommend strongly that you obtain a better telnet client than
- that which comes with windows (I use PuTTY).
-
-
- Anyway, if you are rewarded with a display which looks something
- like:-
-
-
-
- Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.50
- Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
- M0ADI de GB7SJP 4-Mar-2001 1511Z >
-
-
-
- You've arrived. Try some commands, and see how they feel. (In case you
- were wondering, "Iain", "M0ADI" and "GB7SJP" all came from the version
- of DXVars.pm that was on the machine when I started the winclient.pl)
-
-
- The interface is very basic. It is a simple command line. There are
- better looking interfaces. Most of the "standard" logging and DX
- Cluster access programs that are capable of connecting via a TCP or
- telnet connection will work as a "Sysop Console" client. You connect
- to "localhost" on the port that you defined in Listeners.pm (usually
- 7300). I recommend packages like DXTelnet.
-
-
- 6.4. Connecting to other clusters
-
- If you want to connect this to another cluster, then you'll want to
- negotiate a link with someone. For experimental purposes, I'm happy to
- allow folk to connect to GB7DXA (spud.ath.cx), on the understanding
- that the system may or may not be there and may or may not be
- connected to anything particularly useful at any given moment. Contact
- me by Email if you want me to set up a connection for you.
-
-
- 7. General Information
-
- The following relates to all versions of DXSpider and is not platform
- related.
-
-
- 7.1. The crontab file
-
- Login as sysop and create a file in /spider/local_cmd called crontab.
- Edit it with your favourite editor and add a line like this (I have
- included a comment)
-
-
-
- # check every 10 minutes to see if gb7xxx is connected and if not
- # start a connect job going
-
- 0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')
-
-
-
- The callsign involved will be the callsign of the cluster node you are
- going to connect to. This will now check every 10 minutes to see if
- gb7xxx is connected, if it is then nothing will be done. If it is
- not, then a connect attempt will be started.
- There are probably lots of other things you could use this crontab
- file for. If you want to know more about it, look at the DXSpider
- website at the cron page where it is explained more fully.
-
-
-
+++ /dev/null
- The DXSpider CVS Changes Addendum v1.50
- Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
- February 2003 revision 0.1
-
- A reference for CVS users of the DXSpider DXCluster program.
-
- If you have any problems with a new CVS version please mail the
- support list.
-
-
- The latest CVS is version 1.50 build 57.191. There are major changes
- going on currently as the code is being prepared for New Protocol.
-
-
- To run the latest CVS you need to additional perl modules. The links
- are below...
-
-
-
- +\bo Storable-2.06.tar.gz
-
- +\bo Log-Agent-0.303.tar.gz
-
-
-
+++ /dev/null
- The DXSpider FAQ
- Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
- December 2001 Revision: 1.8
-
- A reference for SysOps of the DXSpider DXCluster program.
- ______________________________________________________________________
-
- Table of Contents
-
-
- 1. Installation
- 1.1 Where do I get DXSpider?
- 1.2 How do I use the patches?
- 1.3 If I use a tarball to overwrite my installation, what happens to my configuration?
- 1.4 I am running RedHat 5.2 and I am getting strange errors, what is wrong?
-
- 2. Administration
- 2.1 How can I get Spider to restart automatically if it crashes?
- 2.2 How can I monitor traffic to and from a node or user?
- 2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.
- 2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong?
- 2.5 How can I automatically limit the amount of debug logfiles that are stored?
- 2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?
- 2.7 Since I last updated I seem to be getting duplicate spots appearing.
- 2.8 I have deleted a message but it is still there, why?
-
-
- ______________________________________________________________________
-
- Please mail any FAQs to the maintainer at the address above.
-
-
-
- 1\b1.\b. I\bIn\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn
-
- 1\b1.\b.1\b1.\b. W\bWh\bhe\ber\bre\be d\bdo\bo I\bI g\bge\bet\bt D\bDX\bXS\bSp\bpi\bid\bde\ber\br?\b?
-
- All things Spider can be found at www.dxcluster.org and the actual
- program and patches can be found in the download area.
-
-
- 1\b1.\b.2\b2.\b. H\bHo\bow\bw d\bdo\bo I\bI u\bus\bse\be t\bth\bhe\be p\bpa\bat\btc\bch\bhe\bes\bs?\b?
-
- Patching is done in the standard linux way ...
-
-
-
- zcat /tmp/patch-1.40 | patch -p0
-
-
-
- assuming the patch version you are using is 1.40 and resides in /tmp!
-
-
- Be aware that each patch assumes the previous patch has been applied.
- That is to say if you are patching from version 1.38 to 1.40 you would
- first need to apply patch-1.39 and then patch-1.40.
-
-
- 1\b1.\b.3\b3.\b. I\bIf\bf I\bI u\bus\bse\be a\ba t\bta\bar\brb\bba\bal\bll\bl t\bto\bo o\bov\bve\ber\brw\bwr\bri\bit\bte\be m\bmy\by i\bin\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn,\b, w\bwh\bha\bat\bt h\bha\bap\bpp\bpe\ben\bns\bs t\bto\bo
- m\bmy\by c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn?\b?
-
- The tarballs are designed to not overwrite your existing configuration
- and can be used at any time to update your Spider software. All the
- key files have the suffix .issue (eg. DXVars.pm.issue) at default.
-
-
- 1\b1.\b.4\b4.\b. I\bI a\bam\bm r\bru\bun\bnn\bni\bin\bng\bg R\bRe\bed\bdH\bHa\bat\bt 5\b5.\b.2\b2 a\ban\bnd\bd I\bI a\bam\bm g\bge\bet\btt\bti\bin\bng\bg s\bst\btr\bra\ban\bng\bge\be e\ber\brr\bro\bor\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs
- w\bwr\bro\bon\bng\bg?\b?
-
- The version of Perl that comes with 5.2 seems to be some kind of pre-
- release and is broken. You can get a new version of perl from
- www.dxcluster.org or ftp://updates.redhat.com. Don't forget to patch
- it with the CPAN modules.
-
-
- 2\b2.\b. A\bAd\bdm\bmi\bin\bni\bis\bst\btr\bra\bat\bti\bio\bon\bn
-
- 2\b2.\b.1\b1.\b. H\bHo\bow\bw c\bca\ban\bn I\bI g\bge\bet\bt S\bSp\bpi\bid\bde\ber\br t\bto\bo r\bre\bes\bst\bta\bar\brt\bt a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by i\bif\bf i\bit\bt c\bcr\bra\bas\bsh\bhe\bes\bs?\b?
-
- Put this line into /etc/inittab ..
-
-
-
- DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7
-
-
-
- Run _\bt_\be_\bl_\bi_\bn_\bi_\bt _\bq as root. Spider will restart so be aware. However, any
- time you reboot, cluster.pl will start in tty7 and if it crashes, it
- should restart ok.
-
-
- 2\b2.\b.2\b2.\b. H\bHo\bow\bw c\bca\ban\bn I\bI m\bmo\bon\bni\bit\bto\bor\br t\btr\bra\baf\bff\bfi\bic\bc t\bto\bo a\ban\bnd\bd f\bfr\bro\bom\bm a\ba n\bno\bod\bde\be o\bor\br u\bus\bse\ber\br?\b?
-
- There are 2 ways to achieve this. You can use the _\bt_\ba_\bi_\bl command like
- this ..
-
-
-
- tail -f /spider/data/debug/167.dat |grep G0VGS
-
-
-
- or in later versions of Spider, there is a command called _\bw_\ba_\bt_\bc_\bh_\bd_\bb_\bg in
- which case you simply type ..
-
-
-
- watchdbg G0VGS
-
-
-
- 2\b2.\b.3\b3.\b. M\bMy\by n\bne\bei\big\bgh\bhb\bbo\bou\bur\bri\bin\bng\bg n\bno\bod\bde\be c\bca\ban\bnn\bno\bot\bt u\bus\bse\be t\bth\bhe\be R\bRC\bCM\bMD\bD c\bco\bom\bmm\bma\ban\bnd\bd t\bto\bo m\bme\be,\b, h\bhe\be j\bju\bus\bst\bt
- k\bke\bee\bep\bps\bs g\bge\bet\btt\bti\bin\bng\bg t\bth\bhe\be "\b"t\btu\but\bt t\btu\but\bt"\b" m\bme\bes\bss\bsa\bag\bge\be.\b.
-
- Assuming that the permissions are set correctly (perm level 5
- required), it could be that the home_node is set incorrectly. You can
- reset the home_node using the _\bs_\bp_\bo_\bo_\bf command like this ..
-
-
-
- spoof gb7adx set/home gb7adx
-
-
-
- Assuming that the node_call you are changing is gb7adx.
-
-
- 2\b2.\b.4\b4.\b. I\bI d\bdo\bo n\bno\bot\bt s\bse\bee\bem\bm t\bto\bo b\bbe\be s\bse\ben\bnd\bdi\bin\bng\bg a\ban\bny\by b\bbu\bul\bll\ble\bet\bti\bin\bn m\bma\bai\bil\bl t\bto\bo m\bmy\by l\bli\bin\bnk\bk p\bpa\bar\brt\bt-\b-
- n\bne\ber\brs\bs,\b, w\bwh\bha\bat\bt i\bis\bs w\bwr\bro\bon\bng\bg?\b?
-
- There is a file in /spider/msg called forward.pl.issue. Rename this
- to forward.pl and edit it to meet your requirements. You will need to
- issue the command _\bl_\bo_\ba_\bd_\b/_\bf_\bo_\br_\bw_\ba_\br_\bd or restart Spider for the changes to
- take effect.
-
-
- 2\b2.\b.5\b5.\b. H\bHo\bow\bw c\bca\ban\bn I\bI a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by l\bli\bim\bmi\bit\bt t\bth\bhe\be a\bam\bmo\bou\bun\bnt\bt o\bof\bf d\bde\beb\bbu\bug\bg l\blo\bog\bgf\bfi\bil\ble\bes\bs t\bth\bha\bat\bt
- a\bar\bre\be s\bst\bto\bor\bre\bed\bd?\b?
-
- Use the tmpwatch command. Create a file in /etc/cron.daily/
- containing the line ...
-
-
-
- /usr/sbin/tmpwatch -f 240 /spider/data/debug
-
-
-
- Remember to make it executable!
-
- This will limit your debug data down to the last 10 days
-
-
- 2\b2.\b.6\b6.\b. I\bI u\bup\bpd\bda\bat\bte\bed\bd m\bmy\by L\bLi\bin\bnu\bux\bx d\bdi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn a\ban\bnd\bd n\bno\bow\bw S\bSp\bpi\bid\bde\ber\br c\bca\ban\bnn\bno\bot\bt r\bre\bea\bad\bd t\bth\bhe\be
- u\bus\bse\ber\brs\bs f\bfi\bil\ble\be o\bor\br t\bth\bhe\be d\bdu\bup\bpe\bef\bfi\bil\ble\be,\b, w\bwh\bha\bat\bt i\bis\bs t\bth\bhe\be p\bpr\bro\bob\bbl\ble\bem\bm?\b?
-
- Almost certainly this is a change in the db format of perl. Follow
- these few steps to correct the problem.
-
-
- +\bo stop the cluster (disable any autostart in inittab)
-
- +\bo cd /spider/data
-
- +\bo issue the command perl user_asc
-
- +\bo restart the cluster
-
- That should solve the problem.
-
-
- 2\b2.\b.7\b7.\b. S\bSi\bin\bnc\bce\be I\bI l\bla\bas\bst\bt u\bup\bpd\bda\bat\bte\bed\bd I\bI s\bse\bee\bem\bm t\bto\bo b\bbe\be g\bge\bet\btt\bti\bin\bng\bg d\bdu\bup\bpl\bli\bic\bca\bat\bte\be s\bsp\bpo\bot\bts\bs
- a\bap\bpp\bpe\bea\bar\bri\bin\bng\bg.\b.
-
- What has probably happened is that the dupefile has got corrupted in
- some way. Simply delete the /spider/data/dupefile and restart the
- cluster. It may take a little time to become fully functional but
- should solve your problem.
-
-
- 2\b2.\b.8\b8.\b. I\bI h\bha\bav\bve\be d\bde\bel\ble\bet\bte\bed\bd a\ba m\bme\bes\bss\bsa\bag\bge\be b\bbu\but\bt i\bit\bt i\bis\bs s\bst\bti\bil\bll\bl t\bth\bhe\ber\bre\be,\b, w\bwh\bhy\by?\b?
-
- This is now the way messages are handled for deletion in Spider. If
- you look closely you will see a 'D' following the message number.
- This message is marked for deletion and will be deleted in 2 days if
- nothing further is done. Optionally you can use the command
- _\bd_\be_\bl_\be_\bt_\be_\b/_\be_\bx_\bp_\bu_\bn_\bg_\be to delete it immediately.
-
-
-
+++ /dev/null
- The DXSpider User Manual v1.50
- Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
- September 2002 revision 0.1
-
- A complete reference for users of the DXSpider DXCluster program.
- ______________________________________________________________________
-
- Table of Contents
-
-
- 1. Introduction
- 1.1 What is a DX Cluster?
- 1.2 So what is DXSpider?
-
- 2. Logins and logouts.
- 2.1 AX25 logins.
- 2.2 Netrom logins.
- 2.3 Telnet logins.
- 2.4 Logouts.
-
- 3. Setting your personal details.
- 4. Getting and posting DX.
- 4.1 Receiving DX.
- 4.2 Posting DX.
-
- 5. Headings and propagation
- 5.1 Sun
- 5.2 Moon
- 5.3 Heading
-
- 6. Announcements.
- 6.1 Making announcements.
- 6.2 Listing announcements.
-
- 7. Nodes and users.
- 8. Talk mode.
- 9. Mail.
- 9.1 The "directory" command.
- 9.2 Reading mail.
- 9.3 Sending mail.
- 9.4 Replying to mail.
- 9.5 Deleting mail
-
- 10. Filtering (From version 1.45)
- 10.1 General filter rules
- 10.2 Types of filter
- 10.3 Filter options
- 10.4 Advanced filtering
-
- 11. Hints, tips and common questions.
- 12. The DXSpider command reference
-
-
- ______________________________________________________________________
-
- 1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
-
- 1\b1.\b.1\b1.\b. W\bWh\bha\bat\bt i\bis\bs a\ba D\bDX\bX C\bCl\blu\bus\bst\bte\ber\br?\b?
-
- A DX Cluster is a packet node where DX chasers on any band or mode can
- post rare or interesting stations that they have worked or heard. Of
- course other people are doing the same thing too, so you can find new
- DX as well as telling others about the stations you have worked.
- Clusters tend to be linked to each other so that the amount of people
- using them is increased, thereby increasing the amount of posted DX.
- Other information can be found on clusters such as on-line call books,
- mail etc. You can talk to other stations connected to the cluster
- network too, in real time, whether at the node you are logged into or
- on another node connected to the network. You can also use converse
- mode, where several stations can talk to each other in the same way.
- Of course, the DX is still posted to you all the while!
-
-
- 1\b1.\b.2\b2.\b. S\bSo\bo w\bwh\bha\bat\bt i\bis\bs D\bDX\bXS\bSp\bpi\bid\bde\ber\br?\b?
-
- PacketCluster nodes have been around since roughly 1985. The original
- PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
- about 1992 Dick stopped the development of the PacketCluster software
- for amateur radio. Many systems are still using this relatively old
- DOS software today.
-
- There are several new compatible cluster programs around now,
- including DXSpider. DXSpider is a clone of PacketCluster software
- that runs under several operating systems including Linux and Windows.
- Linux is fast becoming the choice for amateur radio stations because
- of it's flexibility, reliability and the lack of the memory
- limitations of DOS. Linux supports multitasking and is also
- multiuser. It has support for AX25, ROSE, NetROM and TCPIP built in,
- making it the ideal choice for amateur radio. It is also totally
- free!
-
- DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
- exercise in perl programming. It has developed rapidly and today is a
- very powerful cluster program. It was designed to be totally
- compatible with the AK1A program, although several commands have been
- extended to improve functionality.
-
- This manual is designed to help you become familiar with the commands
- that DXSpider supports and to help you get the best from the program
- so you can enjoy working that rare DX! As DXSpider is being improved
- all the time, commands will be added as time goes by, so make sure you
- have the most upto date version of this manual. The latest version
- will always be included with the cluster program so if you are unsure,
- simply ask your sysop. The manual will also be available on the
- wesite.
-
-
-
- 2\b2.\b. L\bLo\bog\bgi\bin\bns\bs a\ban\bnd\bd l\blo\bog\bgo\bou\but\bts\bs.\b.
-
- You might not think that there is a lot of point of including a
- section on how to log in and out of DXSpider. However, you would be
- suprised at the difficulties some people have in simply getting in and
- out of the cluster!
-
- There are several ways a login might be achieved, dependant on how the
- sysop has DXSpider configured. It is impossible for me to cover all
- variations but here are the basic ones.
-
-
- 2\b2.\b.1\b1.\b. A\bAX\bX2\b25\b5 l\blo\bog\bgi\bin\bns\bs.\b.
-
- Simplicity itself. The usual C\bCO\bON\bNN\bNE\bEC\bCT\bT command will log you straight
- into the cluster and you will not have to do anything else.
- Obviously, you will have to connect to the correct callsign. Some
- nodes use an SSID with their call so you would have to add that.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- connect GB7MBC
- connect GB7MBC-1
-
-
-
- 2\b2.\b.2\b2.\b. N\bNe\bet\btr\bro\bom\bm l\blo\bog\bgi\bin\bns\bs.\b.
-
- There are several possibilities here, dependant on how the sysop has
- configured his system. If you are connecting via netrom then you are
- most probably connecting from another station. Listing the nodes in
- that station with the N\bNO\bOD\bDE\bES\bS command will tell you what callsign or
- netrom alias to connect to. Then just issue the connect command from
- there. It is possible that the netrom alias may connect you to a node
- with an alias for the cluster, such as DXC. Just type this and you
- will be connected.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
- connect MBCDX
-
-
-
- 2\b2.\b.3\b3.\b. T\bTe\bel\bln\bne\bet\bt l\blo\bog\bgi\bin\bns\bs.\b.
-
- With telnet connections, the source callsign is not seen by DXSpider,
- so you will be asked to login with your callsign. To telnet to
- DXSpider, you would connect to a specific port. There is no standard
- at the moment for a cluster telnet port but ask the sysop if you are
- unsure.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- telnet gb7mbc 8000
-
-
-
- All the above are possible ways of connecting to a DXSpider cluster.
- You may have some or all of these available to you. There may be one
- or two additional ways to connect dependant on the network local to
- you. However I am sure you get the idea.
-
-
- 2\b2.\b.4\b4.\b. L\bLo\bog\bgo\bou\but\bts\bs.\b.
-
- Logging out can be done by simply issuing the standard B\bBY\bYE\bE command.
-
- You could also send a disconnect if you are using AX25, or a C\bCL\bLO\bOS\bSE\bE
- command if you are connected via telnet. If you do not log out
- gracefully using one of the above commands, you may find you are
- unable to get a full connect next time. This may also happen if a
- netrom connection drops. You may get connected, but nothing else will
- happen because the program thinks you are still connected and will not
- let you connect twice under the same call. However you could
- reconnect by adding a number to the end of your call, for example
- G0YLM-2. This can be done by either altering your MYCALL setting in
- the TNC or by altering your program configuration.
-
-
- 3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg y\byo\bou\bur\br p\bpe\ber\brs\bso\bon\bna\bal\bl d\bde\bet\bta\bai\bil\bls\bs.\b.
-
- Once logged in to the cluster, you should set your details so that
- anybody who wishes to contact you can find out who and where you are.
- There are four items to set, your name, qth, location and home node.
- Setting these details also allows the use of the SHOW/HEADING and
- SHOW/SUN commands from within the cluster. Unless you set your QTH
- and location, these commands cannot function. Once you have set your
- name, DXSpider will greet you with it next time you login. Your QTH
- setting is where you live and it is a good idea to add your locator to
- this as the location setting is converted to latitude and longitude
- once inputted. You can actually set your location in
- latitude/longitude or as a locator. Setting your home node will tell
- the program where you wish mail to be sent to you.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- set/name Ian
- set/qth Morecambe, Lancashire IO84NB
- set/location 48 34 n 12 12 e
- set/qra IO84NB
- set/home gb7mbc
-
-
-
- 4\b4.\b. G\bGe\bet\btt\bti\bin\bng\bg a\ban\bnd\bd p\bpo\bos\bst\bti\bin\bng\bg D\bDX\bX.\b.
-
- When all is said and done, this is the main function of a DX cluster.
- In its simplest form you can just connect to the node and you will
- start to receive DX spots almost immediately! You can check on recent
- postings in either a general manner or on a particular band or mode.
- You can even check DX by callsign or a fragment of a callsign. Of
- course, once you get the hang of things, it is expected that you start
- posting some yourself! After all, there would be no clusters if
- people did not post DX and you get the added thrill of the hunt!
-
-
- 4\b4.\b.1\b1.\b. R\bRe\bec\bce\bei\biv\bvi\bin\bng\bg D\bDX\bX.\b.
-
- As we have already said, it is possible just to connect to the cluster
- and you will receive spots automatically. However, you may wish to
- check on spots just posted. Maybe you wish to see if a particular
- band is open or if a certain callsign is active, perhaps a DXpedition.
- The command to do this is S\bSH\bHO\bOW\bW/\b/D\bDX\bX. Without any other arguments, this
- command will output the last 10 spots posted. It is possible to look
- at more than this, for example the last 20 or 50 spots, by adding the
- number to the command. You can make it even more specific by adding a
- band in either wavelength or frequency, and/or any additional
- information such as QSL details.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- show/dx
- show/dx 5
- show/dx 20
-
-
-
- will show the last 10, 5 and 20 spots received by the cluster
- respectively.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs
-
-
-
- show/dx on 20m
- show/dx 10 on 20m
- show/dx 20 on 20m
-
-
-
- will show the last 5, 10 or 20 spots on 20 metres only.
-
- It is also possible to check for certain callsigns, or fragments of
- callsigns in the same way.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- show/dx g0vgs
- show/dx 10 g0vgs
-
-
-
- would show the last 5 or 10 dx spots containing the callsign g0vgs.
-
-
- You can check for DX by offset and also by specifying a comment to
- search for.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- show/dx 30-40
- show/dx 14000-14033
- show/dx iota
-
-
-
- would show the spots that arrived between 30 and 40 spots ago and any
- spots with the word _\bi_\bo_\bt_\ba in the comment field. The case of the
- comment is not important.
-
- Checking DX posted on a certain day is possible too. All you have to
- do here is to specify how many days ago it was like this ...
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- show/dx day 30
-
-
-
- It is of course possible to specify multiple arguments.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
- show/dx 20 prefix 9a on vhf day 30
-
-
-
- This would show the last 20 spots posted by or about calls with the
- prefix 9a on vhf 30 days ago.
-
- As you can see the S\bSH\bHO\bOW\bW/\b/D\bDX\bX command is very flexible, so if you are not
- sure whether something will work or not, try it and see! More
- information can be found in the Command Set section.
-
-
- 4\b4.\b.2\b2.\b. P\bPo\bos\bst\bti\bin\bng\bg D\bDX\bX.\b.
-
- To post DX you use the D\bDX\bX command. The syntax is shown below.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- dx (frequency) (callsign) (remarks)
-
-
-
- Where frequency is in kilohertz and the callsign is the callsign of
- the station you have worked or heard, (ie not your own callsign!).
- The remarks section allows you to add information like the operators
- name or perhaps a location. Actually DXSpider will allow the
- frequency and callsign fields to be entered in any order.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- dx 14004 pa3ezl OP Aurelio 599
-
-
-
- In fact, all the following will give the same result...
-
-
-
- dx 14004 pa3ezl OP Aurelio 599
- dx pa3ezl 14004 OP Aurelio 599
- dx pa3ezl 14.004 OP Aurelio 599
-
-
-
- This posting, or callout as it is known, will be forwarded to all
- other connected stations both at the cluster you are connected to and
- other active clusters in the network. The callout will also be sent
- to you as proof of receipt.
-
-
- 5\b5.\b. H\bHe\bea\bad\bdi\bin\bng\bgs\bs a\ban\bnd\bd p\bpr\bro\bop\bpa\bag\bga\bat\bti\bio\bon\bn
-
- There are three commands in DXSpider to help you get the best DX
- possible. These are S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN, S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN and S\bSH\bHO\bOW\bW/\b/H\bHE\bEA\bAD\bDI\bIN\bNG\bG. These
- commands will only work for you if you have entered your personal
- details. They use your entered location as a reference, so if you
- have not entered it or have entered it incorrectly they will not
- return the correct information.
- 5\b5.\b.1\b1.\b. S\bSu\bun\bn
-
- The S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command can be used in three different ways. It can be
- used to show sunrise and sunset times for your own station, a
- particular callsign or a prefix.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- show/sun
-
-
-
- The output from this would look something like this ..
-
-
-
- sh/sun
- Location Rise Set Azim Elev
- G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
-
-
-
- sh/sun 5b4
-
-
-
- would look like this ...
-
-
-
- sh/sun 5b4
- Location Rise Set Azim Elev
- 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
-
-
-
- You can also specify multiple arguments like this ...
-
-
-
- sh/sun gw4veq 5b4ab zs
-
-
-
- and then the output would look like this ...
-
-
-
- sh/sun gw4veq 5b4ab zs
- Location Rise Set Azim Elev
- GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
- 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
- ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
- ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
- ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
-
-
- 5\b5.\b.2\b2.\b. M\bMo\boo\bon\bn
-
- The S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN command works in the same way as the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command.
- This program however, calculates the rise and set times of the moon
- for a prefix or callsign, together with the current azimuth and
- elevation of the sun at these locations.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- show/moon ea
-
-
-
- The output from this command would look like this ..
-
-
-
- sh/moon ea
- Location Rise Set Azim Elev RGain dB
- EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
-
-
-
- You can see that the output is similar to the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command, with
- slightly different fields.
-
-
- 5\b5.\b.3\b3.\b. H\bHe\bea\bad\bdi\bin\bng\bg
-
- The S\bSH\bHO\bOW\bW/\b/H\bHE\bEA\bAD\bDI\bIN\bNG\bG command works in the same way as the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN and
- S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN commands but outputs beam headings for a specified callsign
- or prefix. Reciprocal beam headings are also calculated.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be
-
-
-
- show/heading zl
-
-
-
- The output from this command would look like this ..
-
-
-
- sh/heading zl
- ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
- ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
- ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
- ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
-
-
-
- 6\b6.\b. A\bAn\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
-
- 6\b6.\b.1\b1.\b. M\bMa\bak\bki\bin\bng\bg a\ban\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
-
- Occasionally, you may wish to post something that does not fall into
- the normal parameters for a DX callout. You may wish to tell
- everybody connected that 10 FM is open for example, or ask if anyone
- knows the QSL manager for a certain callsign etc. You can do this
- using the A\bAN\bNN\bNO\bOU\bUN\bNC\bCE\bE command.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- announce 10 FM is open in IO84NB to europe.
-
-
-
- That would let everyone know locally that this was the case, however
- it would not be forwarded to other nodes connected. To send
- announcements to other connected nodes as well, you would use the F\bFU\bUL\bLL\bL
- extension.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- announce full Anyone seen EA7WA today?
-
-
-
- Be cautious in your use of announce full. There are many other tools
- available to get the information you require and the judicious use of
- this command is frowned upon as it creates a great deal of traffic
- across the network.
-
-
- 6\b6.\b.2\b2.\b. L\bLi\bis\bst\bti\bin\bng\bg a\ban\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
-
- You can list previous announcements in the standard format with the
- S\bSH\bHO\bOW\bW command. As before you can list just the last 5 or as many as
- you wish.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- show/announcements
- show/announcements 10
-
-
-
- 7\b7.\b. N\bNo\bod\bde\bes\bs a\ban\bnd\bd u\bus\bse\ber\brs\bs.\b.
-
- You can check which nodes are connected in the network, who is logged
- on locally, who is logged on at all the nodes or even just one node in
- particular. This is handy if you wish to see whether a friend is
- connected at the node they use. To see who is connected to the nodes,
- the S\bSH\bHO\bOW\bW/\b/C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN command is used.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- show/configuration
- show/configuration/nodes
- show/configuration (node_call)
- show/configuration (prefix)
-
-
-
- The first of our three examples would output something like this,
-
-
-
- sh/c
- Node Callsigns
- EI5TCR (7 users)
- GB7ADX
- GB7BAA G4FPV G8TIC
- GB7BIG (GD0TEP) GD3UMW
- GB7BPQ (G0INA) G0RCI G3AKU G3OCA
- (GB7CDX) G3JNB G4ALR
- GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
- G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
- ON7WP
- GB7DXA G0RDI G8SJP
- GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
- G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
- GB7DXE G1NNB
- (GB7DXG) GU6EFB GU7DHI
- GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
- G4XQY G7GAN
- GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
- M0BCT M1EMF
-
-
-
- You will notice that EI5TCR is showing only that it has 7 users and
- not giving the actual callsigns. This means that this node is on a
- limited protocol of some kind, probably because of a contest situation
- where slow radio links can block up and fail if too much information
- is sent between nodes.
-
- The second example would just show the nodes connected in the network,
- like this,
-
-
-
- sh/c/n
- Node Callsigns
- GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
- GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
- GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
- GB7YDX KL7G N2TLY (ON0DXK)
- GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
- GB7MBC
- PA4AB-14 PA4AB-14
- PI4TUE-8 PI4TUE-8
-
-
-
- If we insert the node_call pi4tue-8 into the third example, then this
- would be the output,
-
-
-
- Node Callsigns
- PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
- F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
- ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
- PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
- YT1XX
-
-
-
- As you can see, only the users of the requested node are shown.
-
- You can also use a prefix to show only a group of nodes. For example
- you may only wish to see who is connected to the nodes in the UK. To
- do this simply use a prefix like this ...
-
-
- show/configuration gb7
-
-
-
- To show the locally connected users, the S\bSH\bHO\bOW\bW/\b/U\bUS\bSE\bER\bRS\bS command is used
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- show/users
-
-
-
- The output of this command would look like this,
-
-
-
- Callsigns connected to GB7MBC
- G0JHC G0NEI G0VGS G0VGS-2 G0YLM
- G3JAG G3OWO G3UEU
-
-
-
- 8\b8.\b. T\bTa\bal\blk\bk m\bmo\bod\bde\be.\b.
-
- You can send a single comment or start a dedicated talk session to
- another user by using the T\bTA\bAL\bLK\bK command.
-
-
- Talk mode is used to send a one line comment or greeting to a specific
- user connected either at your node or another in the network. You can
- also enter into a dedicated talk session with another user. Talks
- will be automatically forwarded to other nodes if the station you are
- talking to is not connected locally. You can find out who is
- connected by using the S\bSH\bHO\bOW\bW/\b/C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN command, (described
- earlier).
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- talk g0rdi Having a good day Iain?
-
-
- This example would send the line "Having a good day Iain?" to the user
- g0rdi but would leave you in normal mode.
-
-
-
- talk g0rdi
- Entering Talkmode, /EX to end, /<cmd> to run a command
- Talk (G0RDI)>
-
-
-
- As you can see, you can still run commands whilst in talk mode.
- Simply prefix the command with a / like /sh/dx and you will get the
- expected output. If the user is connected to another node, you may
- have to use a slightly extended version of the T\bTA\bAL\bLK\bK command.
-
-
-
- talk g0rdi > gb7djk
-
-
-
- To exit talk mode, you issue the command /\b/e\bex\bx.
-
- Whilst in talk mode you will still receive DX spots. This means that
- you can chat to a friend whilst working DX.
-
-
- 9\b9.\b. M\bMa\bai\bil\bl.\b.
-
- You can send and receive both personal mail and bulletins with
- DXSpider quite easily.
-
-
- 9\b9.\b.1\b1.\b. T\bTh\bhe\be "\b"d\bdi\bir\bre\bec\bct\bto\bor\bry\by"\b" c\bco\bom\bmm\bma\ban\bnd\bd.\b.
-
- To list mail you would use the D\bDI\bIR\bRE\bEC\bCT\bTO\bOR\bRY\bY command. On its own, this
- command will output the last ten messages received by the node, either
- to or from yourself or bulletins such as "DX" and "ALL". As with
- other commands you can display more by specifying a number with the
- command. You should be aware that Spider will accept these commands
- by separating with either a slash or a space, so _\bd_\bi_\br _\bn_\be_\bw and _\bd_\bi_\br_\b/_\bn_\be_\bw
- work in the same way.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- directory
- directory/20
- directory 20
-
-
-
- Of course most of the time you will only want to list new mail sent to
- you personally since your last login. However you might also like to
- check for general mail received by the node. In fact if there is new
- mail for you, the cluster will tell you when you login. You will also
- be informed if new mail arrives for you during the time you are logged
- in. Mail is not only sent to callsigns though. Mail can also be sent
- to subjects like "all" or "local" or "dx" etc. You can treat these
- bulletins in the same way as personal mail with the directory command.
-
- E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
-
-
-
- directory/new
- directory/own
- directory/own/10
- directory/all
- directory/from <call>
-
-
-
- The last option will only show mail from a callsign if it was sent to
- you personally or was sent as a bulletin. There are some additional
- commands and these can be found in the DXSpider Command Reference
- section.
-
-
- 9\b9.\b.2\b2.\b. R\bRe\bea\bad\bdi\bin\bng\bg m\bma\bai\bil\bl.\b.
-
- The output of the D\bDI\bIR\bRE\bEC\bCT\bTO\bOR\bRY\bY command could be something like this.
-
-
-
- dir
- 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
- 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
- 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
- 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
- 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
- 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
- 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
- 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
- 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
- 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
- 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
-
-
-
- The first column is the actual message number. If the message is a
- personal one to you, you will see a letter 'p' after this number. If
- the message has been read, there will be a '-' between the message
- number and the 'p'. This only works for personal messages. The next
- column shows the file size of the message. The third column shows the
- address the message was sent to and the next column shows who sent it.
- The rest is fairly self-explanatory.
-
- Reading a message is as simple as typing read, followed by the message
- number that you wish to read.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- read 25
-
-
-
- will read message number 25. However the mail will be displayed in
- it's entirety unless you specify a page length. You can set your page
- length to any number you like and when the message reaches that number
- of lines you will get a prompt giving you options.
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- set/page 20
-
-
-
- 9\b9.\b.3\b3.\b. S\bSe\ben\bnd\bdi\bin\bng\bg m\bma\bai\bil\bl.\b.
-
- Sending mail is done in the time honoured way. First you specify a
- recipient for the message, then you will be prompted for a subject.
- Once you have done this you will be asked to type your message.
- Please remember that there is no automatic word wrap, so unless you
- are using a client that wraps lines automatically, remember to hit
- return at the end of each line.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- send m0azm
- Enter Subject (30 characters):
- See you Thursday
- Enter Message /EX to send or /ABORT to exit
- Hi Ian,
- Just a quick note to say that I can make Thursday after all. The
- appointment I had has cancelled so we are go!
- Cheers
- Ian
-
-
-
- At this point you can either hit return and enter /ex to send the
- message or use /abort at any time to abort it. You can now display
- the message in the normal way. There are several send options and
- these are listed in the Command Set section. These include sending
- mail to several recipients and asking for a return receipt.
-
-
-
- 9\b9.\b.4\b4.\b. R\bRe\bep\bpl\bly\byi\bin\bng\bg t\bto\bo m\bma\bai\bil\bl.\b.
-
- If mail is addressed to you or to a bulletin address, you can use the
- R\bRE\bEP\bPL\bLY\bY command to reply to it. Using this command, the subject will be
- automatically set for you as "Re: subject", whatever the subject was.
-
- E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
-
-
-
- reply 2500
-
-
-
- 9\b9.\b.5\b5.\b. D\bDe\bel\ble\bet\bti\bin\bng\bg m\bma\bai\bil\bl
-
- To delete a message, you use the _\bd_\be_\bl_\be_\bt_\be command. You can only delete
- messages sent to or received by yourself. Bulletins are dealt with
- automatically or by the sysop.
- 1\b10\b0.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(F\bFr\bro\bom\bm v\bve\ber\brs\bsi\bio\bon\bn 1\b1.\b.4\b45\b5)\b)
-
- 1\b10\b0.\b.1\b1.\b. G\bGe\ben\bne\ber\bra\bal\bl f\bfi\bil\blt\bte\ber\br r\bru\bul\ble\bes\bs
-
- Upto v1.44 it was not possible for the user to set their own filters.
- From v1.45 though that has all changed. It is now possible to set
- filters for just about anything you wish. If you have just updated
- from an older version of DXSpider you will need to update your new
- filters. You do not need to do anything with your old filters, they
- will be renamed as you update.
-
-
- There are 3 basic commands involved in setting and manipulating
- filters. These are _\ba_\bc_\bc_\be_\bp_\bt, _\br_\be_\bj_\be_\bc_\bt and _\bc_\bl_\be_\ba_\br. First we will look
- generally at filtering. There are a number of things you can filter in
- the DXSpider system. They all use the same general mechanism.
-
-
- In general terms you can create a 'reject' or an 'accept' filter which
- can have up to 10 lines in it. You do this using, for example ...
-
-
-
- accept/spots .....
- reject/spots .....
-
-
-
- where ..... are the specific commands for that type of filter. There
- are filters for spots, wwv, announce, wcy and (for sysops) connects.
- See each different accept or reject command reference for more
- details.
-
- There is also a command to clear out one or more lines in a filter.
- They are ...
-
-
-
- clear/spots 1
- clear/spots all
-
-
-
- There is clear/xxxx command for each type of filter.
-
-
- and you can check that your filters have worked by the command ...
-
-
-
- show/filter
-
-
-
- For now we are going to use spots for the examples, but you can apply
- the same principles to all types of filter.
-
-
-
- 1\b10\b0.\b.2\b2.\b. T\bTy\byp\bpe\bes\bs o\bof\bf f\bfi\bil\blt\bte\ber\br
-
- There are two main types of filter, _\ba_\bc_\bc_\be_\bp_\bt or _\br_\be_\bj_\be_\bc_\bt. You can use
- either to achieve the result you want dependent on your own preference
- and which is more simple to do. It is pointless writing 8 lines of
- reject filters when 1 accept filter would do the same thing! Each
- filter has 10 lines (of any length) which are tried in order. If a
- line matches then the action you have specified is taken (ie reject
- means ignore it and accept means take it)
-
-
- If you specify reject filters, then any lines that arrive that match
- the filter will be dumped but all else will be accepted. If you use
- an accept filter, then ONLY the lines in the filter will be accepted
- and all else will be dumped. For example if you have a single line
- _\ba_\bc_\bc_\be_\bp_\bt filter ...
-
-
-
- accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- then you will _\bO_\bN_\bL_\bY get VHF spots _\bf_\br_\bo_\bm or _\bt_\bo CQ zones 14, 15 and 16.
-
-
- If you set a reject filter like this ...
-
-
-
- reject/spots on hf/cw
-
-
-
- Then you will get everything _\bE_\bX_\bC_\bE_\bP_\bT HF CW spots. You could make this
- single filter even more flexible. For example, if you are interested
- in IOTA and will work it even on CW even though normally you are not
- interested in CW, then you could say ...
-
-
-
- reject/spots on hf/cw and not info iota
-
-
-
- But in that case you might only be interested in iota and say:-
-
-
-
- accept/spots not on hf/cw or info iota
-
-
-
- which achieves exactly the same thing. You should choose one or the
- other until you are comfortable with the way it works. You can mix
- them if you wish (actually you can have an accept AND a reject on the
- same line) but don't attempt this until you are sure you know what you
- are doing!
-
-
- You can arrange your filter lines into logical units, either for your
- own understanding or simply convenience. Here is an example ...
- reject/spots 1 on hf/cw
- reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- What this does is to ignore all HF CW spots and also rejects any spots
- on VHF which don't either originate or spot someone in Europe.
-
-
- This is an example where you would use a line number (1 and 2 in this
- case), if you leave the digit out, the system assumes '1'. Digits
- '0'-'9' are available. This make it easier to see just what filters
- you have set. It also makes it more simple to remove individual
- filters, during a contest for example.
-
-
- You will notice in the above example that the second line has
- brackets. Look at the line logically. You can see there are 2
- separate sections to it. We are saying reject spots that are VHF or
- above _\bA_\bP_\bA_\bR_\bT from those in zones 14, 15 and 16 (either spotted there or
- originated there). If you did not have the brackets to separate the 2
- sections, then Spider would read it logically from the front and see a
- different expression entirely ...
-
-
-
- (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-
-
-
- The simple way to remember this is, if you use OR - use brackets.
- Whilst we are here CASE is not important. 'And BY_Zone' is just the
- same as 'and by_zone'.
-
- As mentioned earlier, setting several filters can be more flexible
- than simply setting one complex one. Doing it in this way means that
- if you want to alter your filter you can just redefine or remove one
- or more lines of it or one line. For example ...
-
-
-
- reject/spots 1 on hf/ssb
-
-
-
- would redefine our earlier example, or
-
-
-
- clear/spots 1
-
-
-
- To remove all the filter lines in the spot filter ...
-
-
-
- clear/spots all
-
-
-
- 1\b10\b0.\b.3\b3.\b. F\bFi\bil\blt\bte\ber\br o\bop\bpt\bti\bio\bon\bns\bs
-
- You can filter in several different ways. The options are listed in
- the various helpfiles for accept, reject and filter.
-
-
- 1\b10\b0.\b.4\b4.\b. A\bAd\bdv\bva\ban\bnc\bce\bed\bd f\bfi\bil\blt\bte\ber\bri\bin\bng\bg
-
- Once you are happy with the results you get, you may like to
- experiment.
-
-
- The previous example that filters hf/cw spots and accepts vhf/uhf
- spots from EU can be written with a mixed filter, for example ...
-
-
-
- rej/spot on hf/cw
- acc/spot on 0/30000
- acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
- Note that the first filter has not been specified with a number. This
- will automatically be assumed to be number 1. In this case, we have
- said _\br_\be_\bj_\be_\bc_\bt _\ba_\bl_\bl _\bH_\bF _\bs_\bp_\bo_\bt_\bs _\bi_\bn _\bt_\bh_\be _\bC_\bW _\bs_\be_\bc_\bt_\bi_\bo_\bn _\bo_\bf _\bt_\bh_\be _\bb_\ba_\bn_\bd_\bs _\bb_\bu_\bt _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bl_\bl
- _\bo_\bt_\bh_\be_\br_\bs _\ba_\bt _\bH_\bF_\b. _\bA_\bl_\bs_\bo _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bn_\by_\bt_\bh_\bi_\bn_\bg _\bi_\bn _\bV_\bH_\bF _\ba_\bn_\bd _\ba_\bb_\bo_\bv_\be _\bs_\bp_\bo_\bt_\bt_\be_\bd _\bi_\bn _\bo_\br _\bb_\by
- _\bo_\bp_\be_\br_\ba_\bt_\bo_\br_\bs _\bi_\bn _\bt_\bh_\be _\bz_\bo_\bn_\be_\bs _\b1_\b4_\b, _\b1_\b5 _\ba_\bn_\bd _\b1_\b6. Each filter slot actually has a
- 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
- the accept slot.
-
-
- It was mentioned earlier that after a reject test that doesn't match,
- the default for following tests is 'accept', the reverse is true for
- 'accept'. In the example what happens is that the reject is executed
- first, any non hf/cw spot is passed to the accept line, which lets
- through everything else on HF. The next filter line lets through just
- VHF/UHF spots from EU.
-
-
-
- 1\b11\b1.\b. H\bHi\bin\bnt\bts\bs,\b, t\bti\bip\bps\bs a\ban\bnd\bd c\bco\bom\bmm\bmo\bon\bn q\bqu\bue\bes\bst\bti\bio\bon\bns\bs.\b.
-
- Q\bQ.\b.These commands seem very long! Can I shorten them?
-
- A\bA.\b.Of course you can and the usual abbreviations work. If you are
- unsure, try it.
-
- Q\bQ.\b.I am not sure if this command is correct. Can I cause any harm if I
- try it?
-
- A\bA.\b.Do not be afraid to try a command to see if it will work, at the
- worst you will get an error message. If you require any help on a
- command, just type help followed by the command you want help on.
- Look at the "DXSpider Command Reference" section to see what help can
- be found.
-
- Q\bQ.\b.How should I use the announce command?
-
- A\bA.\b.With respect. Use the command by all means, but please only use the
- "full" extension if absolutely necessary. It can create a LOT of
- messages passing between clusters.
-
- Q\bQ.\b.I like to be working in the shack while logged into the cluster but
- I can't be looking at the screen all the time. How can I be alerted
- when anything happens?
-
- A\bA.\b.Use the S\bSE\bET\bT/\b/B\bBE\bEE\bEP\bP command. You can find information on this in the
- "DXSpider Command Reference" section.
-
- Q\bQ.\b.I got disconnected from the cluster and now I can't log back in
- again. What is wrong?
-
- A\bA.\b.Probably the cluster thinks you are still logged on and will not let
- you reconnect using the same call to prevent loops. Try logging on
- again adding an ssid to your callsign as DXSpider treats G0YLM and
- G0YLM-1 as different users.
-
- Q\bQ.\b.How do I know if I have got the latest version of this user manual?
-
- A\bA.\b.The latest and greatest will always be on the Website. It will also
- be included with every release of DXSpider. As always, if unsure, ask
- your sysop what version number is the latest.
-
-
- 1\b12\b2.\b. T\bTh\bhe\be D\bDX\bXS\bSp\bpi\bid\bde\ber\br c\bco\bom\bmm\bma\ban\bnd\bd r\bre\bef\bfe\ber\bre\ben\bnc\bce\be
-
-
-
projects / spider.git / commitdiff