From: g0vgs Date: Wed, 8 Jan 2003 19:41:48 +0000 (+0000) Subject: Add install procedure for MRTG to Admin manual (g0vgs) X-Git-Tag: PRE-1-52~94 X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=b34f092aea53555f7dcea38612def9692f8dba1d;p=spider.git Add install procedure for MRTG to Admin manual (g0vgs) --- diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html index 11d83731..e7f0992d 100644 --- a/html/adminmanual-1.html +++ b/html/adminmanual-1.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Routing and Filtering @@ -13,9 +13,9 @@ Previous Contents

1. Routing and Filtering

1.1 Introduction +

1.1 Introduction

From DXSpider version 1.48, major changes were introduced to the way @@ -29,76 +29,76 @@ 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. -

+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. -

+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. -

+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 +(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. -

+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. -

+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. -

+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. -

+"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. -

+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 +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. -

+intertwined way.

-The generic commands are:- +The generic commands are:-


 @@ -109,7 +109,8 @@ or
 accept/route node_default <filter_option>

where filter_option is one of the following ... +

where filter_option is one of the following ...


 @@ -123,13 +124,14 @@ 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. -

+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:- +callsign. Examples of each (for my node: GB7DJK) are:-


 @@ -137,53 +139,57 @@ 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. -

+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). -

+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: +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. -

+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:- +debug output after having done:-


  set/debug filter

After you have got tired of that, to put it back the way it was:- +

After you have got tired of that, to put it back the way it was:-


  unset/debug filter

1.4 General route filtering +
+ +

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 ... +use either an accept filter or a reject filter like this ...


 @@ -194,8 +200,9 @@ or
 accept/route <node_call> <filter_option>

Here are some examples of route filters ... +

+ +

Here are some examples of route filters ...


 @@ -205,8 +212,9 @@ 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:- +partner by defining a specific filter for that callsign:-


 @@ -214,8 +222,9 @@ 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:- +isolated node, like this:-


 @@ -223,31 +232,32 @@ 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). -

+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 +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. -

+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. -

+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 ... +up to 10 lines in it. You do this using, for example ...


 @@ -256,10 +266,11 @@ 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 ... +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 ...


 @@ -267,9 +278,10 @@ 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 ... +

There is clear/xxxx command for each type of filter.

+ +

and you can check that your filters have worked by the command ...


 @@ -277,11 +289,12 @@ clear/spots all
 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 +principles to all types of filter.
+ +

1.6 Types of filter

There are two main types of filter, accept or reject. You @@ -290,52 +303,56 @@ 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) -

+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 ... +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 ... +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 ... +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:- +

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! -

+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 ... +understanding or simply convenience. Here is an example ...


 @@ -343,60 +360,65 @@ 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. -

+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. -

+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 ... +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'. +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 ... +one line. For example ...


  reject/spots 1 on hf/ssb

would redefine our earlier example, or +

would redefine our earlier example, or


  clear/spots 1

To remove all the filter lines in the spot filter ... +

To remove all the filter lines in the spot filter ...


  clear/spots all

1.7 Filter options +
+ +

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 +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 @@ -404,7 +426,7 @@ 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 ... +this ...


 @@ -412,20 +434,21 @@ 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 +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. -

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 ... +can be written with a mixed filter, for example ...


 @@ -434,20 +457,21 @@ 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. -

+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 +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 @@ -455,7 +479,7 @@ 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 ... +like this ...


 @@ -510,13 +534,14 @@ $def_hopcount = 5;
 };

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. -

+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 ... +whole call in single quotes, like this ...


 @@ -530,18 +555,19 @@ whole call in single quotes, like this ...
                    },

If you do not do this, you will get errors and the file will not work as -expected. -

+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 +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:- +options so:-


 @@ -550,18 +576,19 @@ 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 +
+
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. -

+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 @@ -572,15 +599,15 @@ 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. -

+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. -

+an acc/spot >call< all filter to override the isolate.

Next Previous diff --git a/html/adminmanual-10.html b/html/adminmanual-10.html index 6aff45b9..fd0deaa8 100644 --- a/html/adminmanual-10.html +++ b/html/adminmanual-10.html @@ -1,2722 +1,207 @@ - - The DXSpider Administration Manual v1.50: The DXSpider command set + + The DXSpider Administration Manual v1.50: CVS + -Next +Next Previous Contents

10. The DXSpider command set

10. CVS

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 -

10.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... -

10.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
-
-

10.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
-
-

10.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... -

10.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
-
-

10.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. -

10.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
-
-

10.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. -

10.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
-
-

10.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. -

10.11 announce full (0) -

- -

announce full <text> Send an announcement cluster wide -

This command will send your announcement across the whole cluster -network. -

10.12 announce sysop (5) -

- -

announce sysop <text> -

Send an announcement to Sysops only -

10.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. -

10.14 bye (0) -

- -

bye Exit from the cluster -

This will disconnect you from the cluster -

10.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. -

10.16 clear/announce (8) -

- -

clear/announce [input] <callsign> [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. -

10.17 clear/route (8) -

- -

clear/route [input] ^lt;callsign> [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. -

10.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. -

10.19 clear/spots (extended for sysops) (8) -

- -

clear/spots [input] <callsign> [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. -

10.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. -

10.21 clear/wcy (extended for sysops) (8) -

- -

clear/wcy [input] <callsign> [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. -

10.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. -

10.23 clear/wwv (extended for sysops) (8) -

- -

clear/wwv [input] <callsign> [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. -

10.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>. -

10.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. -

10.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 -

10.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. -

10.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. -

10.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
-
-

10.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. -

10.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! -

10.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. -

10.33 directory (0) -

- -

directory List messages directory all List all 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 -'p' then this indicates that the message has been read. -

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
-
-

10.34 directory (extended for sysops) (5) -

- -

Works just like the user command except that sysops can see ALL messages. -

10.35 disconnect (8) -

- -

disconnect <call> [<call> ...] Disconnect a user or node -

Disconnect any <call> connected locally -

10.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. -

10.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 -

10.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. -

10.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 -'0'-'9' are available. -

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 -'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. -

The next filter line lets through just VHF/UHF spots from EU. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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). -

10.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. -

10.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! -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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' -

10.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. -

10.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). -

10.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. -

10.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!!! -

10.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. -

10.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. -

10.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. -

10.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 -

10.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... -

10.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
-
-

10.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)
-
-

10.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>
-
-

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... -

10.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
-
-

10.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. -

10.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 -

10.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. -

10.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
-
-

10.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) -

10.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 -

10.75 set/address (0) -

- -

set/address <your_address> Record your postal address -

Literally, record your address details on the cluster. -

10.76 set/announce (0) -

- -

set/announce Allow announce messages -

Allow announce messages to arrive at your terminal. -

10.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 -

10.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
-
-

10.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. -

10.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. -

10.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. -

10.82 set/beep (0) -

- -

set/beep Add beeps to terminal messages -

Add a beep to DX and other terminal messages. -

10.83 set/bbs (5) -

- -

set/bbs <call> [<call>..]Make <call> a BBS -

10.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 -

10.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> -

10.86 set/dx (0) -

- -

set/dxAllow DX messages to arrive at your terminal -

You can stop DX messages with the unset/dx command -

10.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. -

10.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 -

10.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. -

10.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 -

10.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. -

10.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
-
-

10.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. -

10.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. -

10.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). -

10.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
-
-

10.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
-
-

10.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. -

10.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. -

10.100 set/name (0) -

- -

set/name <your_name> Set your name -

Tell the cluster what your name is, eg:- -


--  set/name Dirk
-
-

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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 -

10.109 set/sys_qra (9) -

- -

set/sys_qra <locator> Set your cluster QRA locator -

10.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
-
-

10.111 set/qth (0) -

- -

set/qth <your QTH> Set your QTH -

Tell the system where your are. For example:- -


--  set/qth East Dereham, Norfolk
-
-

10.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 -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.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 -

10.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. -

10.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. -

10.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. -

10.125 show/debug (9) -

- -

show/debug Show what levels of debug you are logging -

The levels can be set with set/debug -

10.126 show/dx (0) +

10.1 CVS from a Linux platform

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.
+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.
 
-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.
+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.
 
-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
-
-

10.127 show/dxcc (0) -

I am of course assuming that you have a machine with both DXSpider and +Internet access running.

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
-
-

10.128 sh/dxstats (0) -

BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR +ENTIRE SPIDER TREE!!

sh/dxstats Show the DX Statistics for last 31 days -

Show the total DX spots for the last 31 days -

10.129 show/files (0) -

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 ...

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:- +

First login as the user sysop. Next you need to connect to the CVS +repository. You do this with the command below ...


 -   SH/FILES bulletins arld*
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
 
-

See also TYPE - to see the contents of a file. -

10.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. -

10.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. -

10.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 -

10.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 -

10.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. -

10.135 show/isolate (1) -

- -

show/isolate Show a list of isolated nodes -

Show which nodes are currently set to be isolated. -

10.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 -

10.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. -

10.138 show/moon (0) -

You will get a password prompt. Simply hit return here and your machine should +return to a normal linux prompt.

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
-
-

10.139 show/muf (0) -

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

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:- +

The next step will create a brand new 'spider' directory in your current +directory.


--  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
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
 
-

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. -

10.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 -

10.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. -

10.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. -

10.143 show/prefix (0) -

This command is all on one line.

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. -

10.144 show/program (5) -

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.

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. -

10.145 show/qra (0) -

Now if you are doing a new installation, that's it. Carry on as if you have +just downloaded and untarred the lastest tarball.

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:- +

If you want to upgrade your current installation then do this ...


 -SH/QRA 52 41 N 0 58 E
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz

10.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 -

10.147 show/registered (9) -

- -

show/registered [<prefix>[ Show the registered users -

10.148 show/route (0) -

This is assuming you downloaded to the /tmp directory of course.

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
-
-

10.149 show/satellite (0) -

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)

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
-
-

10.150 show/sun (0) -

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!

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 all else fails it will show the sunrise and set times for the node -that you are connected to. -

For example:- +

Now the magic part! From now on when you want to update, simply connect to the +Internet and then, as the user sysop ...


 -  SH/SUN
-  SH/SUN G1TLH K9CW ZS
+cd /spider
+cvs -z3 update -d

10.151 show/time (0) -

- -

show/time [<prefix>|<callsign>] Show -the local time -

10.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 -

10.153 show/vhftable (0) -

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.

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 -

10.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 -

10.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 -

10.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. -

10.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. -

10.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. -

10.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. -

10.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. -

10.161 stat/route_node (5) -

- -

stat/route_node <callsign> Show the data in a Route::Node object -

10.162 stat/route_user (5) -

You will find any changes documented in the /spider/Changes file.

stat/route_user <callsign> Show the data in a Route::User object -

10.163 stat/user (5) +

10.2 CVS from a Windows platform

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. +

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:

10.164 sysop (0) -

- -

sysop Regain your privileges if you login remotely +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:

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 :-): +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:


 -  password = 012345678901234567890123456789
-  > sysop
-  22 10 15 17 3
+anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login

you type:- -

and select


 - aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
+"passwd" file on the cvs server

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. +

for Authentication on the General tab.

Next, move to the right to the Ports tab.

10.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> +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.

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:- +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:


--   /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
-   /HELP talk
-
-

To leave talk mode type: +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


 -   /EX
+*****CVS exited normally with code 0*****

10.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:- +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.


 -   TYPE bulletins/arld051
+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

See also SHOW/FILES to see what fileareas are available and a -list of content. -

10.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 -

10.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 -

10.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. -

-Next +Next Previous Contents diff --git a/html/adminmanual-11.html b/html/adminmanual-11.html new file mode 100644 index 00000000..e0519f4a --- /dev/null +++ b/html/adminmanual-11.html @@ -0,0 +1,2809 @@ + + + + + The DXSpider Administration Manual v1.50: The DXSpider command set + + + + + +Next +Previous +Contents +

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)
+
+


++  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 [input] <callsign> [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 [input] ^lt;callsign> [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 [input] <callsign> [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 [input] <callsign> [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 [input] <callsign> [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 all List all 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 +'p' then this indicates that the message has been read.

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 +'0'-'9' are available.

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

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 +'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.

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>
+
+

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.

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

+ +

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.

+ + + +

+Next +Previous +Contents + + diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html index af3f76b3..feb9bdf8 100644 --- a/html/adminmanual-2.html +++ b/html/adminmanual-2.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Other filters @@ -13,13 +13,13 @@ Previous Contents

2. Other filters

2.1 Filtering Mail +

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 .... +this to badmsg.pl and edit the file. The original looks something like this ....


 @@ -61,38 +61,39 @@ package DXMsg;
 );

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 +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. -

+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 +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. -

+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. -

+the Originating Node.

There are a set of commands which allow the sysop to control whether a -spot continues:- +spot continues:-


 @@ -101,34 +102,38 @@ 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: +example, to stop a spot from a particular node you do:


  set/badnode gb7djk gb7dxc

a bad spotter: +

a bad spotter:


  set/badspotter b0mb p1rat nocall

and some bad dx: +

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. -

+show/badnode.

Next Previous diff --git a/html/adminmanual-3.html b/html/adminmanual-3.html index aa163d9f..f8ee47f2 100644 --- a/html/adminmanual-3.html +++ b/html/adminmanual-3.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Mail @@ -13,7 +13,7 @@ Previous Contents

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 @@ -21,30 +21,30 @@ 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. +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 +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 +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 +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 @@ -55,7 +55,7 @@ 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 ... +The format is below ...


 @@ -107,22 +107,23 @@ package DXMsg;
 );

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 -

+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 +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 ... +changes to manage the cluster mail.

Here is a full list of the various options ...


 @@ -142,16 +143,17 @@ changes to manage the cluster mail.
   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 +
+
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 ... +the command ...


 @@ -171,21 +173,22 @@ Read Confirm: 0
 G0VGS de GB7MBC 28-Jan-2001 1308Z >

3.6 Filtering mail +
+ +

3.6 Filtering mail

This is described in the section on Other filters so I will not -duplicate it here. -

3.7 Distribution lists +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. +SYSOP.pl that caters for the UK sysops.


 @@ -194,20 +197,21 @@ qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
    GB7DXK GB7DXI GB7DXS)

Any mail sent to "sysop" would only be sent to the callsigns in this list. -

3.8 BBS interface +
+
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. -

+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. -

+Forward.pl file very carefully.

Next Previous diff --git a/html/adminmanual-4.html b/html/adminmanual-4.html index d0f9178c..f74b9e43 100644 --- a/html/adminmanual-4.html +++ b/html/adminmanual-4.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Scripts @@ -13,11 +13,11 @@ Previous Contents

4. Scripts

From 1.48 onwards it will become increasingly possible to control DXSpider's -operation with scripts of various kinds. -

+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 @@ -25,7 +25,7 @@ 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. +below and is included in the distribution as startup.issue.


 @@ -43,21 +43,22 @@ below and is included in the distribution as startup.issue.
 #

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. -

+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. +a further example.


 @@ -73,18 +74,19 @@ 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. -

+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. -

+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 -

+node_default

Next Previous diff --git a/html/adminmanual-5.html b/html/adminmanual-5.html index ae1126b6..57b15b24 100644 --- a/html/adminmanual-5.html +++ b/html/adminmanual-5.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Databases @@ -13,79 +13,84 @@ Previous Contents

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 +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. +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 .. +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. +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... +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... +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 +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. +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 ... +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 +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 ... +output the available databases. For example ...


 @@ -97,46 +102,50 @@ hftest           GB7DXM
 G0VGS de GB7MBC  3-Feb-2001 1925Z >

5.4 Looking up databases +
+ +

5.4 Looking up databases

To look for information in a defined database, simply use the dbshow -command, for example ... +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 ... +show command like this ...


  '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',

Now you can simply use show/buckmaster or an abreviation. -

5.5 Removing databases +
+
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 ... +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. -

+from scratch if you still required it.

Next Previous diff --git a/html/adminmanual-6.html b/html/adminmanual-6.html index 54ffbbc2..de224c60 100644 --- a/html/adminmanual-6.html +++ b/html/adminmanual-6.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Information, files and useful programs @@ -13,9 +13,9 @@ Previous Contents

6. Information, files and useful programs

6.1 MOTD +

6.1 MOTD

One of the more important things a cluster sysop needs to do is to get @@ -23,16 +23,16 @@ 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 +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 +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 @@ -40,9 +40,9 @@ 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 +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 @@ -50,23 +50,25 @@ 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 .... +be listed by the user with the command ....


  show/files

They can be read by the user by typing the command .... +

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 -

+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. @@ -74,15 +76,16 @@ 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 .... +like this ....


  show/files bulletin

An example would look like this .... +

+ +

An example would look like this ....


 @@ -90,19 +93,21 @@ 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 .... +news you would simply issue the command ....


  type news

To look what is in the bulletin directory you issue the command .... +

To look what is in the bulletin directory you issue the command ....


 @@ -123,7 +128,8 @@ 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 .... +

You can now read any file in this directory using the type command, like this ....


 @@ -142,25 +148,26 @@ Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
 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 +
+
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. -

+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. -

+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. +currently in use at GB7MBC.


 @@ -185,19 +192,20 @@ package CmdAlias;
 )

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. -

+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 '$' says match the end exactly. This prevents unwanted and unintentional matches -with similar commands. -

+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 @@ -206,24 +214,24 @@ have to use the command type news. The alias allows them to simply typ 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. -

+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 +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. -

+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 +file with your favourite editor.
+ +

6.7 Updating kepler data

Spider has a powerful and flexible show/satellite command. In order for @@ -231,38 +239,41 @@ 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 ... +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. -

+/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 ... +convert the file like so ...


  ./convkeps.pl keps.in

Now go back to the cluster and issue the command ... +

+ +

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 +
+ +
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 @@ -271,9 +282,9 @@ 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 +qrz.com for allowing this access.
+ +

6.9 Connecting logging programs

There appear to be very few logging programs out there that support telnet @@ -281,25 +292,26 @@ 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. -

+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. +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. -

+and then telnet from there to the cluster.

Next Previous diff --git a/html/adminmanual-7.html b/html/adminmanual-7.html index 1483a653..619745f4 100644 --- a/html/adminmanual-7.html +++ b/html/adminmanual-7.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50: Java Web applet @@ -13,17 +13,17 @@ Previous Contents

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. -

+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 ... +JDK. To recompile do the following ...


 @@ -32,8 +32,9 @@ rm *.class
 /usr/bin/javac spiderclient.java

I have used /usr/bin/javac as an example, your path to javac may be different. +

+ +

I have used /usr/bin/javac as an example, your path to javac may be different.

 Spider-WEB v0.6b
@@ -85,7 +86,8 @@ choosing (probably your cluster callsign) on the html page.
 
 You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi

Next Previous diff --git a/html/adminmanual-8.html b/html/adminmanual-8.html index 89d93378..2968375a 100644 --- a/html/adminmanual-8.html +++ b/html/adminmanual-8.html @@ -1,8 +1,8 @@ - - The DXSpider Administration Manual v1.50: Security + + The DXSpider Administration Manual v1.50: Web based statistics @@ -13,83 +13,99 @@ Previous Contents

8. Security

8. Web based statistics

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. -

8.1 Registration -

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.

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 ... +

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..


 -set/register g0vgs
+libpng-1.0.14.tar.gz
+zlib-1.1.4.tar.gz
+gd-1.8.3.tar.gz

The user g0vgs can now fully use the cluster. In order to enable -registration, you can issue the command ... +

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...


 -set/var $main::reqreg = 1
+ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
+ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2

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. -

8.2 Passwords -

+ +

Now login to the cluster as your sysop user and run the command +"mrtg all".

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 ... +

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...


 -set/var $main::passwdreq = 1
+indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg

at the cluster prompt. This can also be added to the /spider/scripts/startup -file as above to make the change permanent. +

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...

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. +


++ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
+
+

and for SuSE systems...

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 ... +


++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!


 -unset/password g0vgs
-set/password g0vgs new_password
+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.

Next Previous diff --git a/html/adminmanual-9.html b/html/adminmanual-9.html index 33140fee..85d49507 100644 --- a/html/adminmanual-9.html +++ b/html/adminmanual-9.html @@ -1,8 +1,8 @@ - - The DXSpider Administration Manual v1.50: CVS + + The DXSpider Administration Manual v1.50: Security @@ -13,178 +13,87 @@ Previous Contents

9. CVS

9. Security

9.1 CVS from a Linux platform +
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

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 ... +

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 ...


 -tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
+set/register g0vgs

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 ... +

The user g0vgs can now fully use the cluster. In order to enable +registration, you can issue the command ...


 -cd /spider
-cvs -z3 update -d
+set/var $main::reqreg = 1

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. -

9.2 CVS from a Windows platform +
+
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

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: +

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 ...

-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*****
+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.

-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. +

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 ...

-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
+unset/password g0vgs
+set/password g0vgs new_password

Next Previous diff --git a/html/adminmanual.html b/html/adminmanual.html index a0c306ec..37de4cf0 100644 --- a/html/adminmanual.html +++ b/html/adminmanual.html @@ -1,7 +1,7 @@ - + The DXSpider Administration Manual v1.50 @@ -16,47 +16,47 @@ Contents

The DXSpider Administration Manual v1.50

Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and -Charlie Carroll, K1XX, (k1xx@ptcnh.net)

July 2002 revision 0.1 -

+Charlie Carroll, K1XX, (k1xx@ptcnh.net)January 2003 revision 0.2 +

A reference for SysOps of the DXSpider DXCluster program.

1. Routing and Filtering

2. Other filters

3. Mail

4. Scripts

@@ -65,216 +65,219 @@ Charlie Carroll, K1XX, (k1xx@ptcnh.net)July 2002 revision 0.1

5. Databases

6. Information, files and useful programs

7. Java Web applet

8. Security

8. Web based statistics

+ +

9. Security

9. CVS

10. CVS

10. The DXSpider command set

11. The DXSpider command set

Next diff --git a/html/installation-1.html b/html/installation-1.html index 2b4af659..fb989dd6 100644 --- a/html/installation-1.html +++ b/html/installation-1.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Linux Installation @@ -13,31 +13,31 @@ Previous Contents

1. Linux Installation

1.1 Introduction +

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. -

+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. -

+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 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. -

+perl distribution.

@@ -55,12 +55,13 @@ perl distribution.
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: - +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.10.tar.gz
@@ -112,39 +113,42 @@ that's where you have put them.
 # 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 +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. -

+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. +however this is your own choice.


  # adduser -m sysop

For SuSE distributions, the command would be .. +

+ +

For SuSE distributions, the command would be ..


  # useradd -m sysop

Now set a password for the user ... +

+ +

Now set a password for the user ...


 @@ -154,12 +158,13 @@ however this is your own choice.
 passwd: all authentication tokens updated successfully

1.3 Installing the software +
+ +

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. +permissions. Copy the tarball to /home/sysop and do the following.


 @@ -169,22 +174,24 @@ permissions.  Copy the tarball to /home/sysop and do the following.
 # 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. +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 .... +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 ....


 @@ -193,14 +200,15 @@ should look something like this
 # 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. -

+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 .. +the permissions with the chmod command like this ..


 @@ -208,12 +216,13 @@ the permissions with the chmod command like this ..
 # chmod 4775 ax25_call netrom_call

1.4 Setting callsigns etc +
+ +

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 .... +user is called sysop. Once logged in, issue the following commands ....


 @@ -225,61 +234,66 @@ $ 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. +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. +also.


  $myalias = "G1TLH";

This is the sysop user callsign, normally your own. -

PLEASE USE CAPITAL LETTERS FOR CALLSIGNS -

+ +

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"; -

+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. -

+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 .... +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. +the sysop.


  $ ./create_sysop.pl

1.5 The client program +
+ +

1.5 The client program

In earlier versions of Spider, all the processes were Perl scripts. This @@ -288,14 +302,14 @@ 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 +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 ... +It should look something like this ...


 @@ -311,40 +325,44 @@ 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 ... +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 .... +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 .... +command ....


  shutdown

and both the cluster and the client should return to Linux prompts. -

+ +

and both the cluster and the client should return to Linux prompts.

+ +

Next Previous diff --git a/html/installation-2.html b/html/installation-2.html index 2dd17eab..cdff561e 100644 --- a/html/installation-2.html +++ b/html/installation-2.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Linux quick installation guide @@ -13,12 +13,12 @@ Previous Contents

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. +is the user that should be doing that process.

Login as root
./create_sysop.pl (sysop)
./cluster.pl (sysop)

Spider should now be running and you should be able to login using the -client program. +client program.

Login as root
Enter the correct line in /etc/inetd.conf (root)
killall -HUP inetd (root)

Spider should now be able to accept logins via telnet, netrom and ax25. +

+ +

Spider should now be able to accept logins via telnet, netrom and ax25.

Login as sysop
Login as root
Enter the correct line in /etc/inittab (root)

Next Previous diff --git a/html/installation-3.html b/html/installation-3.html index 8cc7a575..996ebabb 100644 --- a/html/installation-3.html +++ b/html/installation-3.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Setting up the AX25 Utilities @@ -13,51 +13,51 @@ Previous Contents

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. -

+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. -

+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. -

+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 +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. -

+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. -

+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... -

+strongly suggest you get at least this kernel.

+ +

For 2.4 kernels you need these files...

@@ -67,8 +67,9 @@ strongly suggest you get at least this kernel.
ax25-apps-0.0.4-9.i386.rpm

3.2 The kernel +
+ +

3.2 The kernel

First you need to add Amateur Radio Support to your kernel. This is @@ -79,17 +80,18 @@ 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

+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 +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. +then ax25-apps.


 @@ -98,12 +100,13 @@ rpm -ivh ax25-tool-0.0.6-13.i386.rpm
 rpm -ivh ax25-apps-0.0.4-9.i386.rpm

3.4 Configuration +
+ +

3.4 Configuration

You will find the configuration files in /etc/ax25. These consist of -several files ... +several files ...

axports
ax25d.conf
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. -

+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 +following examples.
+ +

3.5 axports

This file sets up the ax25 ports you want to use. An example is below -for a standard TNC2 ... +for a standard TNC2 ...


 @@ -134,10 +138,11 @@ for a standard TNC2 ...
  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 ... +

+ +

Note that the portnames have to be unique.

+ +

The file headings are as follows ...

 portname        -       The name you will refer to the port by
@@ -147,13 +152,14 @@ 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 +
+ +

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 ... +2 ports later ...


 @@ -162,10 +168,11 @@ and includes a port for both cluster and node.  You will see why we need
  netrom2    gb7mbc-9   MBCDX   236      Cluster Netrom Port

Note that the portnames have to be unique. -

The file headings are as follows ... +

+ +

Note that the portnames have to be unique.

+ +

The file headings are as follows ...

 portname        -       The name you will refer to the port by
@@ -175,11 +182,12 @@ 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 +
+ +

3.7 nrbroadcast

This file sets up the netrom broadcast qualities. An example is below ... +

This file sets up the netrom broadcast qualities. An example is below ...


 @@ -187,8 +195,9 @@ description     -       A textual description of the port
  4m       5         10         100          1

The file headings are as follows ... +

+ +

The file headings are as follows ...

 axport          -       The port name in axports that you wish to broadcast
@@ -200,15 +209,16 @@ worst_qual      -       The worst quality for the port.  Any routes under
 verbose         -       This flag determines whether you will only broadcast
                         your own node (0) or all known nodes (1)

3.8 ax25d.conf +
+ +

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 ... +below ...


 @@ -243,36 +253,39 @@ 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. -

+all done in interface order.

You should be able to see that the normal line for access to the -cluster is like this .. +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 .. +

+ +

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: +then add a specific line for that node like this:


 @@ -280,8 +293,9 @@ GB7DJK-2  * * * * * *  - sysop /spider/src/client client gb7djk-2 ax25
 default  * * * * * *  - sysop /spider/src/client client %u ax25

3.9 node.conf +
+ +

3.9 node.conf

For those of you that wish to run the node, you need to set up the @@ -289,7 +303,7 @@ 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 ... +expect. An example is below ...


 @@ -373,19 +387,20 @@ 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 +
+ +
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. -

+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 ... +and connected to the serial ports involved.

+ +

You now use the 'kissattach' command to connect the TNC's to the system like this ...


 @@ -393,9 +408,10 @@ 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 ... +com2 respectively. Now we can set some parameters ...


 @@ -403,10 +419,11 @@ 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 ... +

+ +

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 ...


 @@ -414,11 +431,12 @@ 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 ... +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 ...


 @@ -426,22 +444,24 @@ 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 +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 ... +

+ +

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 ...


 @@ -458,45 +478,50 @@ service node
 }

You now need to restart the xinetd daemon. First find out what the PID is -like so .. +like so ..


  ps auxw |grep xinetd

You will get a reply something like this ... +

+ +

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 ... +

+ +

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 ... +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. -

+netrom connections.

Next Previous diff --git a/html/installation-4.html b/html/installation-4.html index 7438b7aa..87d6c591 100644 --- a/html/installation-4.html +++ b/html/installation-4.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Configuration @@ -13,92 +13,98 @@ Previous Contents

4. Configuration

4.1 Allowing ax25 connects from users +

4.1 Allowing ax25 connects from users

This is dealt with in the previous section -

4.2 Allowing telnet 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. -

+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 .... +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 .... +

+ +

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 .... +

+ +

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 .... +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 .... +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) +
+ +
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. -

+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:- +up in /etc/inetd.conf. Remember to:-


  killall -HUP inetd

to make the change happen... -

+ +

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:- +and select the correct port to listen on. So that it looks like this:-


 @@ -107,10 +113,11 @@ and select the correct port to listen on. So that it looks like this:-
 );

As standard, the listener will listen on all interfaces simultaneously. If you require more control than this, you can specify each interface -individually:- +individually:-


 @@ -120,27 +127,28 @@ individually:-
 );

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. -

+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) +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. -

+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:- +Specifically you must:-

set $enable to 1.

$port

Restart the cluster.pl program

- -

4.5 Setting up node connects +
+ + +

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. -

+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 ... +differences at the moment, it allows for compatibility. The 4 types are ...


 @@ -175,33 +183,36 @@ set/dxnet
 set/clx

For now, we will assume that the cluster we are going to connect to is an -AK1A type node. -

+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 ... +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. -

+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 ... +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 ... +

+ +

You should get an initialisation string from DXSpider like this ...


 @@ -209,44 +220,46 @@ console as sysop, cd to spider/src and issue the command ...
 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. -

+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: +of what type it is, do:


  unset/node gb7baa

4.6 Connection scripts +
+ +

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. -

+Writing a script for connections is therefore relatively simple.

The connect scripts consist of lines which start with the following keywords -or symbols:- +or symbols:-

#

All lines starting with a # are ignored, as are completely -blank lines. -

+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. -

+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. -

+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. @@ -256,8 +269,8 @@ 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! -

+before going down this route!

'

' 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 @@ -266,17 +279,18 @@ 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. -

+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]). +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. +one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip.


 @@ -291,8 +305,9 @@ connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
 client gb7dxm ax25

+ +


 @@ -308,8 +323,9 @@ connect agw 1 g1tlh
 client gb7dxm ax25

+ +


 @@ -322,15 +338,16 @@ connect telnet dirkl.tobit.co.uk
 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 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 .... +in the word connect followed by a script name like this ....


 @@ -339,11 +356,12 @@ 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 ... +You should see something like this ...


 @@ -375,22 +393,24 @@ GB7DJK-1 channel func  state 0 -> init
     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 ... +is not actually connecting. To avoid this use the following line ...


  'connect' ''

In a script, this might look like ... +

+ +

In a script, this might look like ...


 @@ -402,25 +422,26 @@ connect telnet mary 3000
 'connect' ''

4.8 Telnet echo +
+ +

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. -

+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. -

+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 ... +Here is an example of what I mean ...


 @@ -434,7 +455,8 @@ connect telnet mary.lancs.ac.uk
 'connect' ''

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 @@ -442,22 +464,22 @@ 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 +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. -

+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. -

+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 ... +the following lines to the file near the end ...


 @@ -465,35 +487,38 @@ the following lines to the file near the end ...
 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 ... +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. +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. -

+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. -

+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. -

+you should find everything running nicely.

Next Previous diff --git a/html/installation-5.html b/html/installation-5.html index 62959bd0..ecf22fa0 100644 --- a/html/installation-5.html +++ b/html/installation-5.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Microsoft Windows Installation @@ -13,34 +13,34 @@ Previous Contents

5. Microsoft Windows Installation

5.1 Introduction +

5.1 Introduction

IMPORTANT: +

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. +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 ... +play with. But someone might ...

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. -

5.2 The requirements +accepting inbound TELNET and radio connections.
+ +

5.2 The requirements

The very first things you're going to need are (in order of -importance):- +importance):-

A cup of good, strong tea
If all goes according to plan, about an hour to spare
Plenty of good, strong tea

5.3 The system +
+ +

5.3 The system

The platform I used to generate these instructions was a @@ -62,18 +63,18 @@ 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. +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? +(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 +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 @@ -81,22 +82,23 @@ 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 +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. +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. +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. +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 @@ -105,19 +107,20 @@ 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 +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: +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:- +http://www.activestate.com/PPMPackages/zips/6xx-builds-only/

and download the following files:-


 @@ -128,6 +131,7 @@ 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 @@ -136,7 +140,7 @@ directory to unpack all of these zip files into (I put mine in 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"):- +(mine, as you can probably guess from what follows, went into "D:\Perl"):-


 @@ -152,8 +156,9 @@ 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: +of them, but suffice it to say you need to:


 @@ -163,36 +168,39 @@ 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 +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: +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/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 +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 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. -

+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 @@ -206,8 +214,8 @@ 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. -

+examples assume that you put it on drive "C:\", for convenience.

Next Previous diff --git a/html/installation-6.html b/html/installation-6.html index 26b17421..87f4d54c 100644 --- a/html/installation-6.html +++ b/html/installation-6.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: Installing the software @@ -13,12 +13,12 @@ Previous Contents

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:- +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:-


 @@ -26,23 +26,26 @@ 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 +else, you can simply


  cd \spider\local

and then +

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:- +minimum you must adjust the following items in DXVars.pm:-

$mycall - Should hold the callsign of your DX Cluster
$mylongitude - The station longitude in degrees and decimal fractions
$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 +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:- +handy "DOS box" that's not doing anything else, do the following:-


 @@ -73,24 +77,26 @@ cd \spider\local
 notepad listeners.pm

The following line need attention:- +

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. +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 +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. -

+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 @@ -98,23 +104,27 @@ should change the "0.0.0.0" to "127.0.0.1" [which is 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 +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: +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/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/drivers.zip

A couple of the tools: +http://www.raag.org/sv2agw/agwterm.zip

-http://www.raag.org/sv2agw/agwterm.zip

-http://www.raag.org/sv2agw/agwmonitor.zip

will also help with troubleshooting of the RF links themselves. +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:- +AGWConnect.pm by:-


 @@ -122,29 +132,32 @@ copy c:\spider\perl\AGWConnect.pm
 c:\spider\local\AGWConnect.pm

and then +

and then


  notepad AGWConnect.pm

to bring up an editor window containing the file. You must -consider adjusting the following items in AGWConnect.pm:- +consider adjusting the following items in AGWConnect.pm:-

$enable - set to '1' to enable AGWPE interface
$login - the login ID you chose when you set up the SV2AGW security :-)
$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 +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:- +supplied which will do this for you. To run the tool:-


 @@ -152,19 +165,21 @@ 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. +returned.

Depending on how brave you are, you might now care to try the -following:- +following:-


  perl cluster.pl

If you did everything you were told, your DOS window will now -hold a display which looks something like:- +hold a display which looks something like:-


 @@ -192,11 +207,12 @@ 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) +(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:- +following:-


 @@ -204,10 +220,11 @@ 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:- +to the port you defined in Listeners.pm (7300 as default), thus:-


 @@ -215,14 +232,15 @@ Menu->Start->Run
 telnet localhost 7300

On getting the login: prompt, enter your sysop callsign (the one you -put in DXVars.pm as $myalias). -

+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:- +PuTTY).

+ +

Anyway, if you are rewarded with a display which looks something like:-


 @@ -231,20 +249,21 @@ 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) -

+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 +DXTelnet.
+ +

6.4 Connecting to other clusters

If you want to connect this to another cluster, then you'll want to @@ -254,8 +273,8 @@ 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. -

+want me to set up a connection for you.

Next Previous diff --git a/html/installation-7.html b/html/installation-7.html index eeb2162e..e7956dfe 100644 --- a/html/installation-7.html +++ b/html/installation-7.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50: General Information @@ -12,16 +12,16 @@ Next Previous Contents

7. General Information

The following relates to all versions of DXSpider and is not platform related. -

7.1 The crontab file +
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) +a comment)


 @@ -31,17 +31,18 @@ a comment)
 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. -

+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. -

+at the cron page where it is explained more fully.

Next Previous diff --git a/html/installation.html b/html/installation.html index 85c2aa50..946ce785 100644 --- a/html/installation.html +++ b/html/installation.html @@ -1,7 +1,7 @@ - + The DXSpider Installation Manual v1.50 @@ -18,19 +18,19 @@ Contents

Iain Philipps, G0RDI (g0rdi@77hz.com), Ian Maude, G0VGS, (g0vgs@gb7mbc.net) and Charlie Carroll, K1XX, (k1xx@ptcnh.net)

September 2002 revision 0.4 -

A reference for SysOps of the DXSpider DXCluster program.

1. Linux Installation

2. Linux quick installation guide

@@ -39,56 +39,56 @@ Carroll, K1XX, (k1xx@ptcnh.net)September 2002 revision 0.4

3. Setting up the AX25 Utilities

4. Configuration

5. Microsoft Windows Installation

6. Installing the software

7. General Information

Next diff --git a/html/spiderCVS.html b/html/spiderCVS.html index c36b1c10..66324575 100644 --- a/html/spiderCVS.html +++ b/html/spiderCVS.html @@ -1,7 +1,7 @@ - + The DXSpider CVS Changes addendum @@ -15,18 +15,18 @@ Contents

The DXSpider CVS Changes addendum

Ian Maude, G0VGS, (ianmaude@btinternet.com)

Version 1.50 July 2002 -

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. -

+list.

The latest CVS is version 1.50 build 57.002. There are major changes going on currently -as the code is being prepared for New Protocol. -

+as the code is being prepared for New Protocol.

There are currently no addenda, please look to the /spider/Changes file for any -small alterations. -

+small alterations.

Next Previous diff --git a/html/spiderFAQ-1.html b/html/spiderFAQ-1.html index 9b0ebc04..1fca230d 100644 --- a/html/spiderFAQ-1.html +++ b/html/spiderFAQ-1.html @@ -1,7 +1,7 @@ - + The DXSpider FAQ: Installation @@ -13,40 +13,41 @@ Previous Contents

1. Installation

1.1 Where do I get DXSpider? +

1.1 Where do I get DXSpider?

All things Spider can be found at www.dxcluster.org and the actual program and patches can be found in the -download area. -

1.2 How do I use the patches? +download area.
+ +

1.2 How do I use the patches?

Patching is done in the standard linux way ... +

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! -

+ +

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.3 If I use a tarball to overwrite my installation, what happens to my configuration? +to apply patch-1.39 and then patch-1.40.
+ +

1.3 If I use a tarball to overwrite my installation, what happens to my configuration?

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.4 I am running RedHat 5.2 and I am getting strange errors, what is wrong? +files have the suffix .issue (eg. DXVars.pm.issue) at default.
+ +

1.4 I am running RedHat 5.2 and I am getting strange errors, what is wrong?

The version of Perl that comes with 5.2 seems to be some kind of pre-release @@ -54,8 +55,8 @@ 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. -

+Don't forget to patch it with the CPAN modules.

Next Previous diff --git a/html/spiderFAQ-2.html b/html/spiderFAQ-2.html index 300b2774..4f15b247 100644 --- a/html/spiderFAQ-2.html +++ b/html/spiderFAQ-2.html @@ -1,7 +1,7 @@ - + The DXSpider FAQ: Administration @@ -12,80 +12,85 @@ Next Previous Contents

2. Administration

2.1 How can I get Spider to restart automatically if it crashes? +

2.1 How can I get Spider to restart automatically if it crashes?

Put this line into /etc/inittab .. +

Put this line into /etc/inittab ..


  DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop > /dev/tty7

Run telinit q 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.2 How can I monitor traffic to and from a node or user? +time you reboot, cluster.pl will start in tty7 and if it crashes, it should restart ok.
+ +

2.2 How can I monitor traffic to and from a node or user?

There are 2 ways to achieve this. You can use the tail command like this .. +

There are 2 ways to achieve this. You can use the tail command like this ..


  tail -f /spider/data/debug/167.dat |grep G0VGS

or in later versions of Spider, there is a command called watchdbg in which -case you simply type .. +case you simply type ..


  watchdbg G0VGS

2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message. +
+ +

2.3 My neighbouring node cannot use the RCMD command to me, he just keeps getting the "tut tut" message.

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 spoof -command like this .. +command like this ..


  spoof gb7adx set/home gb7adx

Assuming that the node_call you are changing is gb7adx. -

2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong? +
+
Assuming that the node_call you are changing is gb7adx.
+ +

2.4 I do not seem to be sending any bulletin mail to my link partners, what is wrong?

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 load/forward or restart Spider for the changes to -take effect. -

2.5 How can I automatically limit the amount of debug logfiles that are stored? +take effect.
+ +

2.5 How can I automatically limit the amount of debug logfiles that are stored?

Use the tmpwatch command. Create a file in /etc/cron.daily/ containing the line ... +

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.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem? +
+
Remember to make it executable!
+
This will limit your debug data down to the last 10 days
+ +

2.6 I updated my Linux distribution and now Spider cannot read the users file or the dupefile, what is the problem?

Almost certainly this is a change in the db format of perl. Follow these -few steps to correct the problem. +few steps to correct the problem.

stop the cluster (disable any autostart in inittab)
issue the command perl user_asc
restart the cluster

That should solve the problem. -

2.7 Since I last updated I seem to be getting duplicate spots appearing. +
+
That should solve the problem.
+ +

2.7 Since I last updated I seem to be getting duplicate spots appearing.

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.8 I have deleted a message but it is still there, why? +should solve your problem.
+ +

2.8 I have deleted a message but it is still there, why?

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 delete/expunge -to delete it immediately. -

+to delete it immediately.

Next Previous diff --git a/html/spiderFAQ.html b/html/spiderFAQ.html index a0fbbbd5..f9ec536e 100644 --- a/html/spiderFAQ.html +++ b/html/spiderFAQ.html @@ -1,7 +1,7 @@ - + The DXSpider FAQ @@ -16,33 +16,33 @@ Contents

The DXSpider FAQ

Ian Maude, G0VGS, (g0vgs@gb7mbc.net)

December 2001 Revision: 1.8 -

A reference for SysOps of the DXSpider DXCluster program.

Please mail any FAQs to the maintainer at the address above. -

Please mail any FAQs to the maintainer at the address above.

+ +

1. Installation

2. Administration

Next diff --git a/html/usermanual-1.html b/html/usermanual-1.html index 1758c79e..bfe7761b 100644 --- a/html/usermanual-1.html +++ b/html/usermanual-1.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Introduction @@ -13,9 +13,9 @@ Previous Contents

1. Introduction

1.1 What is a DX Cluster? +

1.1 What is a DX Cluster?

A DX Cluster is a packet node where DX chasers on any band or mode can @@ -29,16 +29,16 @@ 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.2 So what is DXSpider? +Of course, the DX is still posted to you all the while!
+ +

1.2 So what is DXSpider?

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. +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 @@ -46,21 +46,21 @@ 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! +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. +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. -

+ask your sysop. The manual will also be available on the wesite.

+ +

Next Previous diff --git a/html/usermanual-10.html b/html/usermanual-10.html index 88fab61c..77bb31b0 100644 --- a/html/usermanual-10.html +++ b/html/usermanual-10.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Filtering (From version 1.45) @@ -13,24 +13,24 @@ Previous Contents

10. Filtering (From version 1.45)

10.1 General filter rules +

10.1 General filter rules

+anything with your old filters, they will be renamed as you update.

+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 ... +up to 10 lines in it. You do this using, for example ...


 @@ -39,10 +39,11 @@ 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 ... +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 ...


 @@ -50,9 +51,10 @@ 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 ... +

There is clear/xxxx command for each type of filter.

+ +

and you can check that your filters have worked by the command ...


 @@ -60,11 +62,12 @@ clear/spots all
 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. -

10.2 Types of filter +principles to all types of filter.
+ +

10.2 Types of filter

There are two main types of filter, accept or reject. You @@ -73,52 +76,56 @@ 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) -

+means take it)


  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 ... +14, 15 and 16.

+ +

If you set a reject filter like this ...


  reject/spots on hf/cw


  reject/spots on hf/cw and not info iota

But in that case you might only be interested in iota and say:- +

But in that case you might only be interested in iota and say:-


  accept/spots not on hf/cw or info iota

+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 ... +understanding or simply convenience. Here is an example ...


 @@ -126,66 +133,71 @@ 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. -

+which don't either originate or spot someone in Europe.

+more simple to remove individual filters, during a contest for example.


  (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16


  reject/spots 1 on hf/ssb

would redefine our earlier example, or +

would redefine our earlier example, or


  clear/spots 1

To remove all the filter lines in the spot filter ... +

To remove all the filter lines in the spot filter ...


  clear/spots all

10.3 Filter options +
+ +

10.3 Filter options

You can filter in several different ways. The options are listed in the -various helpfiles for accept, reject and filter. -

10.4 Advanced filtering +various helpfiles for accept, reject and filter.
+ +

10.4 Advanced filtering

Once you are happy with the results you get, you may like to experiment. -

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 ... +can be written with a mixed filter, for example ...


 @@ -194,21 +206,22 @@ 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. -

+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. -

+else on HF. The next filter line lets through just VHF/UHF spots from EU.

+ +

Next Previous diff --git a/html/usermanual-11.html b/html/usermanual-11.html index dd9cc112..03951d36 100644 --- a/html/usermanual-11.html +++ b/html/usermanual-11.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Hints, tips and common questions. @@ -13,39 +13,39 @@ Previous Contents

11. Hints, tips and common questions.

Q.These commands seem very long! Can I shorten them? +

Q.These commands seem very long! Can I shorten them?

A.Of course you can and the usual abbreviations work. If you -are unsure, try it. +are unsure, try it.

Q.I am not sure if this command is correct. Can I cause any -harm if I try it? +harm if I try it?

A.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.How should I use the announce command? +what help can be found.

Q.How should I use the announce command?

A.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. +create a LOT of messages passing between clusters.

Q.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? +can I be alerted when anything happens?

A.Use the SET/BEEP command. You can find information -on this in the "DXSpider Command Reference" section. +on this in the "DXSpider Command Reference" section.

Q.I got disconnected from the cluster and now I can't log -back in again. What is wrong? +back in again. What is wrong?

A.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. +treats G0YLM and G0YLM-1 as different users.

Q.How do I know if I have got the latest version of this -user manual? +user manual?

A.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. -

+ask your sysop what version number is the latest.

Next Previous diff --git a/html/usermanual-12.html b/html/usermanual-12.html index 742c940a..182378f6 100644 --- a/html/usermanual-12.html +++ b/html/usermanual-12.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: The DXSpider command reference @@ -12,22 +12,22 @@ Next Previous Contents

12. The DXSpider command reference

Below is a complete list of commands available from the cluster prompt. -These are listed below in alphabetical order. -

12.1 accept/announce +These are listed below in alphabetical order.
+ +

12.1 accept/announce

accept/announce [0-9] <pattern> Set an accept filter -line for announce -

Create an 'accept this announce' line for a 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:- +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:-


 @@ -45,7 +45,8 @@ to understand how filters work - it will save a lot of grief later on.
   dest <prefixes>          eg: 6MUK,WDX      (distros)

some examples:- +

some examples:-


 @@ -54,34 +55,37 @@ to understand how filters work - it will save a lot of grief later on.
   (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: +You can use the tag 'all' to accept everything eg:


    acc/ann all

but this probably for advanced users... -

12.2 accept/spots +
+
but this probably for advanced users...
+ +

12.2 accept/spots

accept/spots [0-9] <pattern> Set an accept filter line for spots -

Create an 'accept this spot' line for a filter. -

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. -

You can use any of the following things in this line:- +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:-


 @@ -100,13 +104,14 @@ to understand how filters work - it will save a lot of grief later on.
   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: freq HF (but don't get -too hung up about that) -

some examples:- +too hung up about that)

some examples:-


 @@ -114,22 +119,24 @@ too hung up about that)
   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: +

You can use the tag 'all' to accept everything, eg:


    acc/spot 3 all

but this probably for advanced users... -

12.3 accept/wcy +
+
but this probably for advanced users...
+ +

12.3 accept/wcy

accept/wcy [0-9] <pattern> set an accept WCY filter -

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:- +filter on the following fields:-


 @@ -144,19 +151,20 @@ filter on the following fields:-
   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. -

12.4 accept/wwv +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.
+ +

12.4 accept/wwv

accept/wwv [0-9] <pattern> Set an accept WWV filter -

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:- +filter on the following fields:-


 @@ -171,56 +179,58 @@ filter on the following fields:-
   channel <prefixes>

for example +

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. -

12.5 announce +by stations in the US).
+
See HELP FILTER for information.
+ +

12.5 announce

announce <text> Send an announcement to local users -

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 -

12.6 announce full +of the announcement you wish to broadcast
+ +

12.6 announce full

announce full <text> Send an announcement cluster wide -

announce full <text> Send an announcement cluster wide

This command will send your announcement across the whole cluster -network. -

12.7 apropos +network.
+ +

12.7 apropos

apropos <string> Search the help database -

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. -

12.8 bye +and print the names of all the commands that may be relevant.
+ +

12.8 bye

bye Exit from the cluster -

This will disconnect you from the cluster -

12.9 clear/spots +
`bye Exit from the cluster`
+ +
This will disconnect you from the cluster
+ +

12.9 clear/spots

clear/spots [1|all] Clear a spot filter line -

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:- +remove the whole filter.

If you have a filter:-


 @@ -228,61 +238,67 @@ remove the whole filter.
   acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

and you say:- +

and you say:-


    clear/spot 1

you will be left with:- +

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: +

If you do:


    clear/spot all

the filter will be completely removed. -

12.10 dbavail +
+
the filter will be completely removed.
+ +

12.10 dbavail

dbavail Show a list of all the databases in the system -

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. -

12.11 dbshow +in the system. It is also aliased to SHOW/COMMAND.
+ +

12.11 dbshow

dbshow <dbname> <key> Display an entry, if it exists, in a database -

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: +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: +SHOW/COMMAND to find out) you can do the same thing with:


    DBSHOW buck G1TLH

12.12 directory +
+ +

12.12 directory

directory List messages directory all List all messages @@ -292,15 +308,15 @@ SHOW/COMMAND to find out) you can do the same thing with: 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. +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 -'p' then this indicates that the message has been read. +'p' then this indicates that the message has been read.

You can use shell escape characters such as '*' and '?' in the <call> -fields. -

You can combine some of the various directory commands together eg:- +fields.

You can combine some of the various directory commands together eg:-


 @@ -309,7 +325,8 @@ or
    DIR SUBJECT IOTA 200-250

You can abbreviate all the commands to one letter and use ak1a syntax:- +

You can abbreviate all the commands to one letter and use ak1a syntax:-


 @@ -317,14 +334,15 @@ or
    DIR/S QSL 10-100 5

12.13 dx +
+ +

12.13 dx

dx [by <call>] <freq> <call> <remarks> Send a DX spot -

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. +enter the <freq> and the <call> either way round.


 @@ -333,72 +351,75 @@ enter the <freq> and the <call> either way round.
    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. +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:- +

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. -

12.14 help +cluster. See SHOW/BANDS for more information.
+ +

12.14 help

help <cmd> Get help on a command -

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. +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. -

12.15 kill +to look at with HELP.
+ +

12.15 kill

kill <msgno> [<msgno> ..] Delete a message from the local system -

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). -

12.16 links +the sysop).
+ +

12.16 links

links Show which nodes are physically connected -

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. -

12.17 read +some information about them. See WHO for a list of all connections.
+ +

12.17 read

read Read the next unread personal message addressed to you -read <msgno> Read the specified message -

+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. -

12.18 reject/announce +message either sent by or sent to your callsign.
+ +

12.18 reject/announce

reject/announce [0-9] <pattern> Set a reject filter -for announce -

Create an 'reject this announce' line for a 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:- +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:-


 @@ -416,32 +437,35 @@ to understand how filters work - it will save a lot of grief later on.
   dest <prefixes>          eg: 6MUK,WDX      (distros)

some examples:- +

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: +

You can use the tag 'all' to reject everything eg:


    rej/ann all

but this probably for advanced users... -

12.19 reject/spots +
+
but this probably for advanced users...
+ +

12.19 reject/spots

reject/spots [0-9] <pattern> Set a reject filter line for spots -

Create a 'reject this spot' line for a filter. +

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:- +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:-


 @@ -460,12 +484,13 @@ to understand how filters work - it will save a lot of grief later on.
   channel <prefixes>

some examples:- +too hung up about that)

some examples:-


 @@ -473,22 +498,24 @@ too hung up about that)
   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: +

You can use the tag 'all' to reject everything eg:


    rej/spot 3 all

but this probably for advanced users... -

12.20 reject/wcy +
+
but this probably for advanced users...
+ +

12.20 reject/wcy

reject/wcy [0-9] <pattern> Set a reject WCY filter -

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:- +filter on the following fields:-


 @@ -503,18 +530,19 @@ filter on the following fields:-
   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. -

12.21 reject/wwv +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.
+ +

12.21 reject/wwv

reject/wwv [0-9] <pattern> Set a reject WWV filter -

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:- +filter on the following fields:-


 @@ -529,18 +557,20 @@ filter on the following fields:-
   channel <prefixes>

for example +

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. -

12.22 reply +by stations in the US).
+
See HELP FILTER for information.
+ +

12.22 reply

reply Reply (privately) to the last message that you have read @@ -548,168 +578,172 @@ by stations in the US). 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 -

+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. +"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) -

12.23 send +for further details)
+ +

12.23 send

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 -

+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. +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:- +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. +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 -

12.24 set/address +SP is an alias for SEND PRIVATE
+ +

12.24 set/address

set/address <your_address> Record your postal address -

Literally, record your address details on the cluster. -

12.25 set/announce +
`set/address <your_address> Record your postal address`
+ +
Literally, record your address details on the cluster.
+ +

12.25 set/announce

set/announce Allow announce messages -

Allow announce messages to arrive at your terminal. -

12.26 set/beep +
`set/announce Allow announce messages`
+ +
Allow announce messages to arrive at your terminal.
+ +

12.26 set/beep

set/beep Add beeps to terminal messages -

Add a beep to DX and other terminal messages. -

12.27 set/dx +
`set/beep Add beeps to terminal messages`
+ +
Add a beep to DX and other terminal messages.
+ +

12.27 set/dx

set/dxAllow DX messages to arrive at your terminal -

You can stop DX messages with the unset/dx command -

12.28 set/dxgrid +
`set/dxAllow DX messages to arrive at your terminal`
+ +
You can stop DX messages with the unset/dx command
+ +

12.28 set/dxgrid

set/dxgridAllow grid squares on the end of DX messages -

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. -

12.29 set/echo +command to remove the grid squares.
+ +

12.29 set/echo

set/echo Make the cluster echo your input -

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. -

12.30 set/here +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.
+ +

12.30 set/here

set/here Set the here flag -

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. -

12.31 set/homenode +around your callsign to indicate you are not available.
+ +

12.31 set/homenode

set/homenode <node_call> Set your home cluster -

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:- +eg:-


    SET/HOMENODE gb7djk

12.32 set/language +
+ +

12.32 set/language

set/language <language> Set the language you wish to use -

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) sp (Spanish) -and nl (Dutch). -

12.33 set/location +and nl (Dutch).
+ +

12.33 set/location

set/location <lat and long> Set your latitude and longitude -

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/qra command which will do the conversion for you.


    set/location 54 04 N 2 02 E

12.34 set/logininfo +
+ +

12.34 set/logininfo

set/logininfo Show logins and logouts of nodes and users -

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. -

12.35 set/name +can stop these messages by using the unset/logininfo command.
+ +

12.35 set/name

set/name <your_name> Set your name -

Tell the cluster what your name is, eg:- +

set/name <your_name> Set your name

+ +

Tell the cluster what your name is, eg:-


    set/name Dirk

12.36 set/page +
+ +

12.36 set/page

set/page <n> Set the number of lines per page -

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. +explicitly to 0 will disable paging.


 @@ -717,109 +751,112 @@ explicitly to 0 will disable paging.
   SET/PAGE 0

The setting is stored in your user profile. -

12.37 set/qra +
+
The setting is stored in your user profile.
+ +

12.37 set/qra

set/qra <locator> Set your QRA locator -

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:- +correctly (assuming your locator is correct ;-). For example:-


    SET/QRA JO02LQ

12.38 set/qth +
+ +

12.38 set/qth

set/qth <your QTH> Set your QTH -

Tell the system where your are. For example:- +

set/qth <your QTH> Set your QTH

+ +

Tell the system where your are. For example:-


    set/qth East Dereham, Norfolk

12.39 set/talk +
+ +

12.39 set/talk

set/talk Allow talk messages to be seen at your console -

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. -

12.40 set/wcy +talks with the unset/talk command.
+ +

12.40 set/wcy

set/wcy Allow WCY messages to be seen at your console -

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. -

12.41 set/wwv +WCY messages with the unset/wcy command.
+ +

12.41 set/wwv

set/wwv Allow WWV messages to be seen at your console -

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. -

12.42 set/wx +WWV messages with the unset/wwv command.
+ +

12.42 set/wx

set/wx Allow WX messages to be seen at your console -

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. -

12.43 show/configuration +WX messages with the unset/wx command.
+ +

12.43 show/configuration

show/configuration [<node>] Show all visible nodes and their users -

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 -

12.44 show/configuration/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
+ +

12.44 show/configuration/node

show/configuration/node Show all the nodes connected -

Show all the nodes connected locally and the nodes they have connected. -

12.45 show/date +
`show/configuration/node Show all the nodes connected`
+ +
Show all the nodes connected locally and the nodes they have connected.
+ + +

12.45 show/date

show/date [<prefix>|<callsign>] Show -the local time -

+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. +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. -

12.46 show/dx +the prefixes or callsigns that you specify.
+ +

12.46 show/dx

show/dx [options] interrogate the spot database -

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). +(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:- +any order to the basic SHOW/DX command, they are:-


 @@ -855,7 +892,8 @@ qra [<locator>] - this will look for the specific locator if
                   you specify one or else anything that looks like a locator.

e.g. +

e.g.


 @@ -869,17 +907,18 @@ qra [<locator>] - this will look for the specific locator if
    SH/DX qra jn86

12.47 show/dxcc +
+ +

12.47 show/dxcc

show/dxcc <prefix> Interrogate the spot database by country -

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. +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. +e.g.


 @@ -888,59 +927,62 @@ e.g.
    SH/DXCC W on 20m info iota

12.48 show/files +
+ +

12.48 show/files

show/files [<filearea> [<string>]] List -the contents of a filearea -

+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:- +area type:-


     SH/FILES <filearea>

where <filearea> is the name of the filearea you want to see the -contents of. +contents of.

You can also use shell globbing characters like '*' and '?' in a -string to see a selection of files in a filearea eg:- +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. -

12.49 show/filter +
+
See also TYPE - to see the contents of a file.
+ +

12.49 show/filter

show/filter Show the filters you have set -

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. -

12.50 show/moon +displays all the filters set - for all the various categories.
+ +

12.50 show/moon

show/moon [<prefix>|<callsign>] Show moon -rise and set times -

+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. +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. +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. +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:- +that you are connected to.

For example:-


 @@ -948,49 +990,51 @@ that you are connected to.
   SH/MOON G1TLH W5UN

12.51 show/muf +
+ +

12.51 show/muf

show/muf <prefix> [<hours>][long] Show -the likely propagation to <prefix> -

+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) +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. +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. +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 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. +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:- +hours required after the prefix. For example:-


    SH/MUF W

produces: +

produces:


 @@ -1004,17 +1048,19 @@ hours required after the prefix. For example:-
   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). -

inputing:- +80m but usable signals on 40m (about S3).

inputing:-


    SH/MUF W 24

will get you the above display, but with the next 24 hours worth of -propagation data. +propagation data.


 @@ -1022,32 +1068,33 @@ propagation data.
   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. -

12.52 show/prefix +terrible accurate, but it is included for completeness.
+ +

12.52 show/prefix

show/prefix <callsign> Interrogate the prefix database -

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. -

12.53 show/qra +together with the internal country no, the CQ and ITU regions.
+
See also SHOW/DXCC
+ +

12.53 show/qra

show/qra <locator> [<locator>] Show the distance between locators -show/qra <lat> <long> Convert latitude and longitude to a locator -

+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:- +to the locator. For example:-


 @@ -1055,59 +1102,62 @@ 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. +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:- +example:-


  SH/QRA 52 41 N 0 58 E

12.54 show/qrz +
+ +

12.54 show/qrz

show/qrz <callsign> Show any callbook details on a callsign -

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 -

12.55 show/route +is provided for users of this software by http://www.qrz.com
+ +

12.55 show/route

show/route <callsign> Show the route to <callsign> -

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. +connected. It is a sort of inverse sh/config.


    sh/route n2tly

12.56 show/satellite +
+ +

12.56 show/satellite

show/satellite <name> [<hours> <interval>] -Show satellite tracking data -

+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. +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. +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. +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:- +limits.

Each pass in a period is separated with a row of '-----' characters

So for example:-


 @@ -1115,22 +1165,23 @@ SH/SAT AO-10
 SH/SAT FENGYUN1 12 2

12.57 show/sun +
+ +

12.57 show/sun

show/sun [<prefix>|<callsign>] Show -sun rise and set times -

+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. +locations.

If all else fails it will show the sunrise and set times for the node -that you are connected to. -

For example:- +that you are connected to.

For example:-


 @@ -1138,49 +1189,50 @@ that you are connected to.
   SH/SUN G1TLH K9CW ZS

12.58 show/time +
+ +

12.58 show/time

show/time [<prefix>|<callsign>] Show -the local time -

+the local time

12.59 show/wcy +the prefixes or callsigns that you specify.
+ +

12.59 show/wcy

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 -

12.60 show/wwv +show/wcy <n> Show the last <n> WCY broadcasts
+ +
Display the most recent WCY information that has been received by the system
+ +

12.60 show/wwv

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 -

12.61 sysop +show/wwv <n> Show the last <n> WWV broadcasts
+ +
Display the most recent WWV information that has been received by the system
+ +

12.61 sysop

sysop Regain your privileges if you login remotely -

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. +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 :-): +these values are for explanation :-):


 @@ -1189,7 +1241,8 @@ these values are for explanation :-):
   22 10 15 17 3

you type:- +

you type:-


 @@ -1198,36 +1251,37 @@ these values are for explanation :-):
  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. -

12.62 talk +case sensitive.
+ +

12.62 talk

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 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. +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. +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. +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. +station that you asked for.

All the usual announcements, spots and so on will still come out on your -terminal. +terminal.

If you want to do something (such as send a spot) you precede the normal -command with a '/' character, eg:- +command with a '/' character, eg:-


 @@ -1235,48 +1289,51 @@ command with a '/' character, eg:-
    /HELP talk

To leave talk mode type: +

To leave talk mode type:

/EX

12.63 type +
+ +

12.63 type

type <filearea>/<name> Look at a file in one of the fileareas -

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:- +enter:-


     TYPE bulletins/arld051

See also SHOW/FILES to see what fileareas are available and a -list of content. -

12.64 who +list of content.
+ +

12.64 who

who Show who is physically connected locally -

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 -

12.65 wx +what sort of connection they have
+ +

12.65 wx

wx <text> Send a weather message to local users -wx full <text> Send a weather message to all cluster 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 -

+that may indicate enhanced conditions

Next Previous diff --git a/html/usermanual-2.html b/html/usermanual-2.html index 92e21349..ba279317 100644 --- a/html/usermanual-2.html +++ b/html/usermanual-2.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Logins and logouts. @@ -13,24 +13,24 @@ Previous Contents

2. Logins and logouts.

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! +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.1 AX25 logins. +variations but here are the basic ones.
+ +

2.1 AX25 logins.

Simplicity itself. The usual CONNECT 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. -

Examples: +nodes use an SSID with their call so you would have to add that.

Examples:


 @@ -38,8 +38,9 @@ connect GB7MBC
 connect GB7MBC-1

2.2 Netrom logins. +
+ +

2.2 Netrom logins.

There are several possibilities here, dependant on how the sysop has @@ -49,39 +50,41 @@ that station with the NODES 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. +and you will be connected.

Example:


  connect MBCDX

2.3 Telnet logins. +
+ +

2.3 Telnet logins.

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. -

Example: +you are unsure.

Example:


  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.4 Logouts. +However I am sure you get the idea.
+ +

2.4 Logouts.

Logging out can be done by simply issuing the standard BYE -command. +command.

You could also send a disconnect if you are using AX25, or a CLOSE command if you are connected via telnet. If you do not log out gracefully using one of the above commands, @@ -92,9 +95,9 @@ 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. -

+by altering your program configuration.

+ +

Next Previous diff --git a/html/usermanual-3.html b/html/usermanual-3.html index 6e22acbb..65e07dc8 100644 --- a/html/usermanual-3.html +++ b/html/usermanual-3.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Setting your personal details. @@ -13,7 +13,7 @@ Previous Contents

3. Setting your personal details.

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. @@ -26,8 +26,8 @@ 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. -

Examples: +tell the program where you wish mail to be sent to you.

Examples:


 @@ -38,7 +38,8 @@ set/qra IO84NB
 set/home gb7mbc

Next Previous diff --git a/html/usermanual-4.html b/html/usermanual-4.html index 5ce4b801..e4c5c36b 100644 --- a/html/usermanual-4.html +++ b/html/usermanual-4.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Getting and posting DX. @@ -13,7 +13,7 @@ Previous Contents

4. Getting and posting DX.

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 @@ -22,9 +22,9 @@ 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.1 Receiving DX. +if people did not post DX and you get the added thrill of the hunt!
+ +

4.1 Receiving DX.

As we have already said, it is possible just to connect to the @@ -36,8 +36,8 @@ 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. -

Examples: +frequency, and/or any additional information such as QSL details.

Examples:


 @@ -46,9 +46,10 @@ show/dx 5
 show/dx 20

will show the last 10, 5 and 20 spots received by the cluster -respectively. -

Examples +respectively.

Examples


 @@ -57,10 +58,11 @@ show/dx 10 on 20m
 show/dx 20 on 20m

will show the last 5, 10 or 20 spots on 20 metres only. +

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. -

Examples: +callsigns in the same way.

Examples:


 @@ -68,11 +70,12 @@ show/dx g0vgs
 show/dx 10 g0vgs

would show the last 5 or 10 dx spots containing the callsign 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. -

Examples: +search for.

Examples:


 @@ -81,56 +84,61 @@ 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 iota in the comment field. The case of -the comment is not important. +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 ... -

Example: +to do here is to specify how many days ago it was like this ...

Example:


  show/dx day 30

It is of course possible to specify multiple arguments. -

Example: +

It is of course possible to specify multiple arguments.

Example:


  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. +9a on vhf 30 days ago.

As you can see the SHOW/DX 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.2 Posting DX. +information can be found in the Command Set section.
+ +

4.2 Posting DX.

To post DX you use the DX command. The syntax is shown below. -

Example: +

To post DX you use the DX command. The syntax is shown below.

Example:


  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. -

Example: +and callsign fields to be entered in any order.

Example:


  dx 14004 pa3ezl OP Aurelio 599

In fact, all the following will give the same result... +

In fact, all the following will give the same result...


 @@ -139,11 +147,12 @@ 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. -

+to you as proof of receipt.

Next Previous diff --git a/html/usermanual-5.html b/html/usermanual-5.html index eded4b5d..d43a170e 100644 --- a/html/usermanual-5.html +++ b/html/usermanual-5.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Headings and propagation @@ -13,29 +13,30 @@ Previous Contents

5. Headings and propagation

There are three commands in DXSpider to help you get the best DX possible. These are SHOW/SUN, SHOW/MOON and SHOW/HEADING. 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.1 Sun +they will not return the correct information.
+ +

5.1 Sun

The SHOW/SUN 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. -

Example: +particular callsign or a prefix.

Example:


  show/sun

The output from this would look something like this .. +

The output from this would look something like this ..


 @@ -44,13 +45,15 @@ Location                              Rise   Set      Azim   Elev
 G0VGS  Morecambe, Lancashire          07:08Z 17:39Z  205.3   24.1


  sh/sun 5b4

would look like this ... +

would look like this ...


 @@ -59,14 +62,16 @@ Location                              Rise   Set      Azim   Elev
 5B     Cyprus-5B                      04:23Z 15:40Z  244.0   18.8

You can also specify multiple arguments like this ... +

You can also specify multiple arguments like this ...


  sh/sun gw4veq 5b4ab zs

and then the output would look like this ... +

and then the output would look like this ...


 @@ -79,23 +84,25 @@ 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.2 Moon +
+ +

5.2 Moon

The SHOW/MOON command works in the same way as the SHOW/SUN 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. -

Example: +locations.

Example:


  show/moon ea

The output from this command would look like this .. +

The output from this command would look like this ..


 @@ -104,24 +111,26 @@ 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 SHOW/SUN -command, with slightly different fields. -

5.3 Heading +command, with slightly different fields.
+ +

5.3 Heading

The SHOW/HEADING command works in the same way as the SHOW/SUN and SHOW/MOON commands but outputs beam headings for a specified callsign or prefix. Reciprocal beam headings -are also calculated. -

Example +are also calculated.

Example


  show/heading zl

The output from this command would look like this .. +

The output from this command would look like this ..


 @@ -132,7 +141,8 @@ ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 34
 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs

Next Previous diff --git a/html/usermanual-6.html b/html/usermanual-6.html index 5f20a93a..b1f9a78f 100644 --- a/html/usermanual-6.html +++ b/html/usermanual-6.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Announcements. @@ -13,46 +13,48 @@ Previous Contents

6. Announcements.

6.1 Making announcements. +

6.1 Making announcements.

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 ANNOUNCE command. -

Example: +using the ANNOUNCE command.

Example:


  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 -FULL extension. -

Example: +FULL extension.

Example:


  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.2 Listing announcements. +across the network.
+ +

6.2 Listing announcements.

You can list previous announcements in the standard format with the SHOW command. As before you can list just the last 5 or as -many as you wish. -

Example: +many as you wish.

Example:


 @@ -60,7 +62,8 @@ show/announcements
 show/announcements 10

Next Previous diff --git a/html/usermanual-7.html b/html/usermanual-7.html index b1e3369b..9f07b324 100644 --- a/html/usermanual-7.html +++ b/html/usermanual-7.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Nodes and users. @@ -13,14 +13,14 @@ Previous Contents

7. Nodes and users.

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 SHOW/CONFIGURATION command is used. -

Example: +to the nodes, the SHOW/CONFIGURATION command is used.

Example:


 @@ -30,7 +30,8 @@ show/configuration (node_call)
 show/configuration (prefix)

The first of our three examples would output something like this, +

The first of our three examples would output something like this,


 @@ -56,13 +57,14 @@ 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. +between nodes.

The second example would just show the nodes connected in the -network, like this, +network, like this,


 @@ -78,8 +80,9 @@ 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, +this would be the output,


 @@ -91,24 +94,27 @@ PI4TUE-8     9A1CMA-6     DF6PW        DL4FAY       DL4KAK       DL4WF-2
              YT1XX

As you can see, only the users of the requested node are shown. +

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 ... +do this simply use a prefix like this ...

 show/configuration gb7

To show the locally connected users, the SHOW/USERS command is -used -

Example: +used

Example:


  show/users

The output of this command would look like this, +

The output of this command would look like this,


 @@ -117,7 +123,8 @@ G0JHC        G0NEI        G0VGS        G0VGS-2      G0YLM
 G3JAG        G3OWO        G3UEU

Next Previous diff --git a/html/usermanual-8.html b/html/usermanual-8.html index 31149d14..6870a8e7 100644 --- a/html/usermanual-8.html +++ b/html/usermanual-8.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Talk mode. @@ -13,19 +13,19 @@ Previous Contents

8. Talk mode.

You can send a single comment or start a dedicated talk session to -another user by using the TALK command. -

+another user by using the TALK 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 -SHOW/CONFIGURATION command, (described earlier). -

Examples: +SHOW/CONFIGURATION command, (described earlier).

Examples:


 @@ -33,8 +33,9 @@ You can find out who is connected by using the
 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. +user g0rdi but would leave you in normal mode.


 @@ -43,21 +44,23 @@ 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 TALK command. +slightly extended version of the TALK command.


  talk g0rdi > gb7djk

To exit talk mode, you issue the command /ex. +

To exit talk mode, you issue the command /ex.

Whilst in talk mode you will still receive DX spots. This means that -you can chat to a friend whilst working DX. -

+you can chat to a friend whilst working DX.

Next Previous diff --git a/html/usermanual-9.html b/html/usermanual-9.html index 5888ec7d..b11fcabe 100644 --- a/html/usermanual-9.html +++ b/html/usermanual-9.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50: Mail. @@ -13,12 +13,12 @@ Previous Contents

9. Mail.

You can send and receive both personal mail and bulletins with DXSpider -quite easily. -

9.1 The "directory" command. +quite easily.
+ +

9.1 The "directory" command.

To list mail you would use the DIRECTORY command. On its @@ -27,8 +27,8 @@ 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 -dir new and dir/new work in the same way. -

Example: +dir new and dir/new work in the same way.

Example:


 @@ -37,6 +37,7 @@ 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 @@ -46,8 +47,8 @@ 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. -

Examples: +command.

Examples:


 @@ -58,16 +59,16 @@ 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.2 Reading mail. +commands and these can be found in the DXSpider Command Reference section.
+ +

9.2 Reading mail.

The output of the DIRECTORY command could be something like -this. +this.


 @@ -85,36 +86,39 @@ dir
  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. +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. -

Example: +message number that you wish to read.

Example:


  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. -

Example: +you will get a prompt giving you options.

Example:


  set/page 20

9.3 Sending mail. +
+ + +

9.3 Sending mail.

Sending mail is done in the time honoured way. First you specify @@ -122,8 +126,8 @@ 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. -

Example: +return at the end of each line.

Example:


 @@ -138,35 +142,37 @@ 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.4 Replying to mail. +mail to several recipients and asking for a return receipt.
+ + +

9.4 Replying to mail.

If mail is addressed to you or to a bulletin address, you can use the REPLY command to reply to it. Using this command, the subject will be automatically set for you as "Re: subject", whatever -the subject was. -

Example: +the subject was.

Example:


  reply 2500

9.5 Deleting mail +
+ +

9.5 Deleting mail

To delete a message, you use the delete command. You can only delete messages sent to or received by yourself. -Bulletins are dealt with automatically or by the sysop. -

+Bulletins are dealt with automatically or by the sysop.

Next Previous diff --git a/html/usermanual.html b/html/usermanual.html index b603b7ff..6831d80f 100644 --- a/html/usermanual.html +++ b/html/usermanual.html @@ -1,7 +1,7 @@ - + The DXSpider User Manual v1.50 @@ -16,24 +16,24 @@ Contents

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.

1. Introduction

2. Logins and logouts.

3. Setting your personal details.

@@ -42,23 +42,23 @@ Contents

4. Getting and posting DX.

5. Headings and propagation

6. Announcements.

7. Nodes and users.

@@ -70,20 +70,20 @@ Contents

9. Mail.

10. Filtering (From version 1.45)

11. Hints, tips and common questions.

@@ -92,71 +92,71 @@ Contents

12. The DXSpider command reference

Next diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 4a9638f9..3a46f544 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -7,7 +7,7 @@ The DXSpider Administration Manual v1.50 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll, K1XX, (k1xx@ptcnh.net) -July 2002 revision 0.1 +January 2003 revision 0.2 A reference for SysOps of the DXSpider DXCluster program. @@ -1445,6 +1445,89 @@ choosing (probably your cluster callsign) on the html page. You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi +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 . + +

+The following should help you get it all working. + +

+First you need to download the latest version of MRTG from . +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 as your sysop user 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. + Security

diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 3cdb45bd..3de50e2e 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,7 +1,7 @@ The DXSpider Administration Manual v1.50 Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll, K1XX, (k1xx@ptcnh.net) - July 2002 revision 0.1 + January 2003 revision 0.2 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -10,62 +10,7 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Routing and Filtering - 1.1 Introduction 1.2 Route Filters 1.3 The node_default filter @@ -80,13 +25,11 @@ 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 @@ -97,9 +40,7 @@ 3.8 BBS interface 4. Scripts - 5. Databases - 5.1 Creating databases 5.2 Importing databases 5.3 Checking available databases @@ -107,7 +48,6 @@ 5.5 Removing databases 6. Information, files and useful programs - 6.1 MOTD 6.2 MOTD_NOR 6.3 Downtime message @@ -119,188 +59,185 @@ 6.9 Connecting logging programs 7. Java Web applet - - 8. Security - - 8.1 Registration - 8.2 Passwords - - 9. CVS - - 9.1 CVS from a Linux platform - 9.2 CVS from a Windows platform - - 10. The DXSpider command set - - 10.1 accept/announce (0) - 10.2 accept/announce (extended for sysops) (8) - 10.3 accept/route (8) - 10.4 accept/spots (0) - 10.5 accept/spots (extended for sysops) (8) - 10.6 accept/wcy (0) - 10.7 accept/wcy (extended for sysops) (8) - 10.8 accept/wwv (0) - 10.9 accept/wwv (extended for sysops) (8) - 10.10 announce (0) - 10.11 announce full (0) - 10.12 announce sysop (5) - 10.13 apropos (0) - 10.14 bye (0) - 10.15 catchup (5) - 10.16 clear/announce (8) - 10.17 clear/route (8) - 10.18 clear/spots (0) - 10.19 clear/spots (extended for sysops) (8) - 10.20 clear/wcy (0) - 10.21 clear/wcy (extended for sysops) (8) - 10.22 clear/wwv (0) - 10.23 clear/wwv (extended for sysops) (8) - 10.24 connect (5) - 10.25 dbavail (0) - 10.26 dbcreate (9) - 10.27 dbimport (9) - 10.28 dbremove (9) - 10.29 dbshow (0) - 10.30 debug (9) - 10.31 delete/user (9) - 10.32 demonstrate (9) - 10.33 directory (0) - 10.34 directory (extended for sysops) (5) - 10.35 disconnect (8) - 10.36 dx (0) - 10.37 export (9) - 10.38 export_users (9) - 10.39 filtering (0) - 10.40 forward/latlong (8) - 10.41 forward/opername (1) - 10.42 help (0) - 10.43 init (5) - 10.44 kill (0) - 10.45 kill (5) - 10.46 kill full (5) - 10.47 kill/expunge (6) - 10.48 links (0) - 10.49 load/aliases (9) - 10.50 load/badmsg (9) - 10.51 load/badwords (9) - 10.52 load/bands (9) - 10.53 load/cmd_cache (9) - 10.54 load/forward (9) - 10.55 load/messages (9) - 10.56 load/prefixes (9) - 10.57 merge (5) - 10.58 msg (9) - 10.59 pc (8) - 10.60 ping (1) - 10.61 rcmd (1) - 10.62 read (0) - 10.63 read (extended for sysops) (5) - 10.64 reject/announce - 10.65 reject/announce (extended for sysops) (8) - 10.66 reject/route (8) - 10.67 reject/spots (0) - 10.68 reject/spots (extended for sysops) (8) - 10.69 reject/wcy (0) - 10.70 reject/wcy (extended for sysops) (8) - 10.71 reject/wwv (0) - 10.72 reject/wwv (extended for sysops) (8) - 10.73 reply (0) - 10.74 send (0) - 10.75 set/address (0) - 10.76 set/announce (0) - 10.77 set/arcluster (5) - 10.78 set/baddx (8) - 10.79 set/badnode (6) - 10.80 set/badspotter (8) - 10.81 set/badword (8) - 10.82 set/beep (0) - 10.83 set/bbs (5) - 10.84 set/clx (5) - 10.85 set/debug (9) - 10.86 set/dx (0) - 10.87 set/dxgrid (0) - 10.88 set/dxnet (5) - 10.89 set/echo (0) - 10.90 set/email (0) - 10.91 set/here (0) - 10.92 set/homenode (0) - 10.93 set/hops (8) - 10.94 set/isolate (9) - 10.95 set/language (0) - 10.96 set/location (0) - 10.97 set/sys_location (9) - 10.98 set/logininfo (0) - 10.99 set/lockout (9) - 10.100 set/name (0) - 10.101 set/node (9) - 10.102 set/obscount (9) - 10.103 set/page (0) - 10.104 set/password (0) - 10.105 set/password (9) - 10.106 set/pinginterval (9) - 10.107 set/privilege (9) - 10.108 set/spider (5) - 10.109 set/sys_qra (9) - 10.110 set/qra (0) - 10.111 set/qth (0) - 10.112 set/register (9) - 10.113 set/talk (0) - 10.114 set/wcy (0) - 10.115 set/wwv (0) - 10.116 set/wx (0) - 10.117 show/baddx (1) - 10.118 show/badnode (6) - 10.119 show/badspotter (1) - 10.120 show/badword (1) - 10.121 show/configuration (0) - 10.122 show/configuration/node (0) - 10.123 show/connect (1) - 10.124 show/date (0) - 10.125 show/debug (9) - 10.126 show/dx (0) - 10.127 show/dxcc (0) - 10.128 sh/dxstats (0) - 10.129 show/files (0) - 10.130 show/filter (0) - 10.131 show/filter (extended for sysops) (5) - 10.132 show/hfstats (0) - 10.133 show/hftable (0) - 10.134 show/hops (8) - 10.135 show/isolate (1) - 10.136 show/lockout (9) - 10.137 show/log (8) - 10.138 show/moon (0) - 10.139 show/muf (0) - 10.140 show/newconfiguration (0) - 10.141 show/newconfiguration/node (0) - 10.142 show/node (1) - 10.143 show/prefix (0) - 10.144 show/program (5) - 10.145 show/qra (0) - 10.146 show/qrz (0) - 10.147 show/registered (9) - 10.148 show/route (0) - 10.149 show/satellite (0) - 10.150 show/sun (0) - 10.151 show/time (0) - 10.152 show/vhfstats (0) - 10.153 show/vhftable (0) - 10.154 show/wcy (0) - 10.155 show/wwv (0) - 10.156 shutdown (5) - 10.157 spoof (9) - 10.158 stat/db (5) - 10.159 stat/channel (5) - 10.160 stat/msg (5) - 10.161 stat/route_node (5) - 10.162 stat/route_user (5) - 10.163 stat/user (5) - 10.164 sysop (0) - 10.165 talk (0) - 10.166 type (0) - 10.167 who (0) - 10.168 wx (0) - 10.169 wx (enhanced for sysops) (5) + 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) ______________________________________________________________________ @@ -328,6 +265,8 @@ 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. @@ -394,16 +333,18 @@ "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 + The generic commands are:- - or - accept/route node_default + reject/route node_default + + or + + accept/route node_default @@ -422,7 +363,6 @@ - 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. @@ -439,7 +379,6 @@ - GB7DJK uses the first of these. The DXCC countries can be obtained from the show/prefix command. @@ -460,6 +399,7 @@ 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, @@ -477,7 +417,6 @@ - After you have got tired of that, to put it back the way it was:- @@ -486,8 +425,6 @@ - - 1.4. General route filtering Exactly the same rules apply for general route filtering. You would @@ -503,8 +440,6 @@ - - Here are some examples of route filters ... @@ -516,7 +451,6 @@ - In practice you will either be opening the default filter out for a partner by defining a specific filter for that callsign:- @@ -526,6 +460,7 @@ acc/route gb7baa input all + or restricting it quite a lot, in fact making it very nearly like an isolated node, like this:- @@ -536,7 +471,6 @@ - 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). @@ -569,13 +503,11 @@ - 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 @@ -591,7 +523,6 @@ - There is clear/xxxx command for each type of filter. @@ -599,13 +530,10 @@ - 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. @@ -633,7 +561,6 @@ - then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16. @@ -645,7 +572,6 @@ - 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 @@ -657,7 +583,6 @@ - But in that case you might only be interested in iota and say:- @@ -666,7 +591,6 @@ - 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 @@ -684,7 +608,6 @@ - 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. @@ -710,7 +633,6 @@ - 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'. @@ -732,7 +654,6 @@ - To remove all the filter lines in the spot filter ... @@ -741,8 +662,6 @@ - - 1.7. Filter options You can filter in several different ways. The options are listed in @@ -765,7 +684,6 @@ - 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 @@ -818,44 +736,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # # hop table construction # @@ -908,8 +788,6 @@ - - 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 @@ -921,7 +799,6 @@ - 'DB0FHF-15' => { 11 => 5, 12 => 8, @@ -933,7 +810,6 @@ - If you do not do this, you will get errors and the file will not work as expected. @@ -956,7 +832,6 @@ - all work on their specific area of the protocol. @@ -1004,7 +879,6 @@ - # 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) @@ -1036,8 +910,6 @@ - - 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 @@ -1082,7 +954,6 @@ - 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: @@ -1093,7 +964,6 @@ - a bad spotter: @@ -1102,7 +972,6 @@ - and some bad dx: @@ -1111,15 +980,12 @@ - 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 @@ -1169,23 +1035,6 @@ - - - - - - - - - - - - - - - - - # # this is an example message forwarding file for the system # @@ -1224,7 +1073,6 @@ - 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. @@ -1247,11 +1095,6 @@ - - - - - MSG TO - change TO callsign to MSG FRom - change FROM callsign to MSG PRrivate - set private flag @@ -1269,7 +1112,6 @@ - These commands are simply typed from within the cluster as the sysop user. @@ -1301,8 +1143,6 @@ - - 3.6. Filtering mail This is described in the section on Other filters so I will not @@ -1324,7 +1164,6 @@ - Any mail sent to "sysop" would only be sent to the callsigns in this list. @@ -1375,8 +1214,6 @@ - - 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 @@ -1410,7 +1247,6 @@ - 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 @@ -1460,7 +1296,6 @@ - This creates a chained database entry. The first database will be scanned, then the second, the third etc... @@ -1470,7 +1305,6 @@ - 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... @@ -1481,7 +1315,6 @@ - Remote databases cannot be chained, however, the last database in a chain can be a remote database. @@ -1501,7 +1334,6 @@ - This will update the existing local oblast database or create it if it does not exist. @@ -1514,8 +1346,6 @@ - - dbavail DB Name Location Chain qsl Local @@ -1525,8 +1355,6 @@ - - 5.4. Looking up databases To look for information in a defined database, simply use the dbshow @@ -1538,7 +1366,6 @@ - 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 @@ -1546,10 +1373,6 @@ - - - - Now you can simply use show/buckmaster or an abreviation. @@ -1564,7 +1387,6 @@ - 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 @@ -1615,7 +1437,6 @@ - They can be read by the user by typing the command .... @@ -1624,7 +1445,6 @@ - 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 @@ -1644,8 +1464,6 @@ - - An example would look like this .... sh/files @@ -1653,7 +1471,6 @@ - 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, @@ -1667,7 +1484,6 @@ - To look what is in the bulletin directory you issue the command .... @@ -1690,7 +1506,6 @@ - You can now read any file in this directory using the type command, like this .... @@ -1712,8 +1527,6 @@ - - The page length will of course depend on what you have it set to! @@ -1740,7 +1553,6 @@ - # # Local Aliases File # @@ -1762,8 +1574,6 @@ - - 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 @@ -1824,8 +1634,6 @@ - - would export message number 5467 as a file called keps.in in the /spider/perl directory. @@ -1840,8 +1648,6 @@ - - Now go back to the cluster and issue the command ... @@ -1850,8 +1656,6 @@ - - That is it! the kepler data has been updated. @@ -1887,8 +1691,6 @@ - - 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 @@ -1918,8 +1720,6 @@ - - I have used /usr/bin/javac as an example, your path to javac may be different. @@ -1973,8 +1773,106 @@ + 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 as your sysop user 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 + + - 8. Security + 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 @@ -1983,7 +1881,7 @@ security. - 8.1. Registration + 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 @@ -1998,17 +1896,13 @@ - 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. @@ -2025,7 +1919,7 @@ registered users, use the command show/register. - 8.2. Passwords + 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 @@ -2042,8 +1936,6 @@ - - at the cluster prompt. This can also be added to the /spider/scripts/startup file as above to make the change permanent. @@ -2065,11 +1957,11 @@ + 10. CVS - 9. CVS - 9.1. CVS from a Linux platform + 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 @@ -2135,8 +2027,6 @@ 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. @@ -2151,7 +2041,6 @@ - This is assuming you downloaded to the /tmp directory of course. @@ -2174,11 +2063,8 @@ - - - cd /spider - cvs -z3 update -d - + cd /spider + cvs -z3 update -d @@ -2191,7 +2077,7 @@ You will find any changes documented in the /spider/Changes file. - 9.2. CVS from a Windows platform + 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 @@ -2204,6 +2090,7 @@ 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 @@ -2237,13 +2124,10 @@ - and select - - "passwd" file on the cvs server - + "passwd" file on the cvs server @@ -2293,7 +2177,6 @@ - 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. @@ -2305,19 +2188,14 @@ 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 - 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 - - - - - - 10. The DXSpider command set + 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 @@ -2326,7 +2204,7 @@ is the permissions level needed to use the command - 10.1. accept/announce (0) + 11.1. accept/announce (0) accept/announce [0-9] Set an accept filter line for announce @@ -2340,8 +2218,6 @@ You can use any of the following things in this line:- - - info eg: iota or qsl by eg: G,M,2 origin @@ -2357,7 +2233,6 @@ - some examples:- @@ -2368,14 +2243,11 @@ - or - - acc/ann by G,M,2 - + acc/ann by G,M,2 @@ -2388,11 +2260,10 @@ - but this probably for advanced users... - 10.2. accept/announce (extended for sysops) (8) + 11.2. accept/announce (extended for sysops) (8) accept/announce [input] [0-9] Announce filter sysop version @@ -2409,9 +2280,7 @@ - - - 10.3. accept/route (8) + 11.3. accept/route (8) accept/route [0-9] Set an 'accept' filter line for routing @@ -2440,6 +2309,7 @@ origin_zone + some examples:- @@ -2449,8 +2319,6 @@ - - You can use the tag 'all' to accept everything eg: @@ -2459,9 +2327,7 @@ - - - 10.4. accept/spots (0) + 11.4. accept/spots (0) accept/spots [0-9] Set an accept filter line for spots @@ -2473,6 +2339,7 @@ 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. @@ -2481,80 +2348,53 @@ + Filters for the station being spotted: + call + 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 + 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 + call_zone + Filters for the callsign of the station doing the spotting: + by + 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 + 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 + by_zone + Filters for the callsign of the "node" doing the spotting: + origin + 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 + channel W1HR --> spots from the connected node W1HR will be spotted + channel K1QX --> spots from the connected user K1QX will be spotted - - - - - - - - - - - - - - - - - - Filters for the station being spotted: - call - 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 - 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 - call_zone - - Filters for the callsign of the station doing the spotting: - by - 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 - 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 - by_zone - - Filters for the callsign of the "node" doing the spotting: - origin - 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 - channel W1HR --> spots from the connected node W1HR will be spotted - channel K1QX --> spots from the connected user K1QX will be spotted - - info eg: iota or qsl - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - - + info eg: iota or qsl + freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on same as 'freq' @@ -2572,6 +2412,7 @@ 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: @@ -2580,11 +2421,10 @@ - but this probably for advanced users... - 10.5. accept/spots (extended for sysops) (8) + 11.5. accept/spots (extended for sysops) (8) accept/spots [input] [0-9] Spot filter sysop version @@ -2602,9 +2442,7 @@ - - - 10.6. accept/wcy (0) + 11.6. accept/wcy (0) accept/wcy [0-9] set an accept WCY filter @@ -2626,8 +2464,6 @@ - - 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). @@ -2637,8 +2473,7 @@ See HELP FILTER for information. - - 10.7. accept/wcy (extended for sysops) (8) + 11.7. accept/wcy (extended for sysops) (8) accept/wcy [input] [0-9] WCY filter sysop version @@ -2653,9 +2488,7 @@ - - - 10.8. accept/wwv (0) + 11.8. accept/wwv (0) accept/wwv [0-9] Set an accept WWV filter @@ -2677,7 +2510,6 @@ - for example @@ -2686,14 +2518,14 @@ - is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information. - 10.9. accept/wwv (extended for sysops) (8) + + 11.9. accept/wwv (extended for sysops) (8) accept/wwv [input] [0-9] WWV filter sysop version @@ -2703,18 +2535,15 @@ + accept/wwv db0sue-7 1 by_zone 4 + accept/wwv node_default all + set/hops node_default 10 - 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 - - + accept/wwv user_default by W,K - 10.10. announce (0) + 11.10. announce (0) announce Send an announcement to local users @@ -2725,7 +2554,7 @@ sysop will override set/noannounce. - 10.11. announce full (0) + 11.11. announce full (0) announce full Send an announcement cluster wide @@ -2735,7 +2564,7 @@ - 10.12. announce sysop (5) + 11.12. announce sysop (5) announce sysop @@ -2743,7 +2572,7 @@ Send an announcement to Sysops only - 10.13. apropos (0) + 11.13. apropos (0) apropos Search the help database @@ -2752,7 +2581,7 @@ print the names of all the commands that may be relevant. - 10.14. bye (0) + 11.14. bye (0) bye Exit from the cluster @@ -2760,7 +2589,7 @@ This will disconnect you from the cluster - 10.15. catchup (5) + 11.15. catchup (5) catchup All|[ ...] Mark a message as sent @@ -2779,7 +2608,6 @@ - and to undo what you have just done:- @@ -2789,13 +2617,12 @@ - which will arrange for them to be forward candidates again. Order is not important. - 10.16. clear/announce (8) + 11.16. clear/announce (8) clear/announce [input] [0-9|all] Clear an announce filter line @@ -2805,7 +2632,7 @@ node_default or user_default. - 10.17. clear/route (8) + 11.17. clear/route (8) clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line @@ -2819,14 +2646,13 @@ node_default or user_default. - 10.18. clear/spots (0) + 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:- @@ -2844,7 +2670,6 @@ - you will be left with:- @@ -2853,7 +2678,6 @@ - If you do: @@ -2862,11 +2686,10 @@ - the filter will be completely removed. - 10.19. clear/spots (extended for sysops) (8) + 11.19. clear/spots (extended for sysops) (8) clear/spots [input] [0-9|all] Clear a spot filter line @@ -2875,7 +2698,7 @@ node_default or user_default. - 10.20. clear/wcy (0) + 11.20. clear/wcy (0) clear/wcy [1|all] Clear a WCY filter line @@ -2886,26 +2709,28 @@ see CLEAR/SPOTS for a more detailed explanation. - 10.21. clear/wcy (extended for sysops) (8) + 11.21. clear/wcy (extended for sysops) (8) clear/wcy [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. - 10.22. clear/wwv (0) + 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. - 10.23. clear/wwv (extended for sysops) (8) + 11.23. clear/wwv (extended for sysops) (8) clear/wwv [input] [0-9|all] Clear a WWV filter line @@ -2914,7 +2739,7 @@ node_default or user_default. - 10.24. connect (5) + 11.24. connect (5) connect Start a connection to another DX Cluster @@ -2926,7 +2751,7 @@ cluster . - 10.25. dbavail (0) + 11.25. dbavail (0) dbavail Show a list of all the databases in the system @@ -2935,7 +2760,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. - 10.26. dbcreate (9) + 11.26. dbcreate (9) dbcreate Create a database entry dbcreate chain [..] Create a chained database @@ -2956,7 +2781,6 @@ 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, @@ -2993,7 +2817,6 @@ - to allow SH/BUCK g1tlh @@ -3004,7 +2827,7 @@ databases. See DBSHOW for generic database enquiry - 10.27. dbimport (9) + 11.27. dbimport (9) dbimport Import AK1A data into a database @@ -3019,11 +2842,10 @@ oblast database held locally. - 10.28. dbremove (9) + 11.28. dbremove (9) dbremove Delete a database - DBREMOVE will completely remove a database entry and also delete any data file that is associated with it. @@ -3033,7 +2855,6 @@ DBREMOVE oblast - will remove the oblast database from the system and it will also remove the associated datafile. @@ -3044,7 +2865,7 @@ You have been warned. - 10.29. dbshow (0) + 11.29. dbshow (0) dbshow Display an entry, if it exists, in a database @@ -3060,7 +2881,6 @@ - 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: @@ -3070,10 +2890,7 @@ - - - - 10.30. debug (9) + 11.30. debug (9) debug Set the cluster program into debug mode @@ -3087,12 +2904,10 @@ - It will interrupt the cluster just after the debug command has finished. - - 10.31. delete/user (9) + 11.31. delete/user (9) delete/user Delete a user from the User Database @@ -3105,7 +2920,7 @@ It goes without saying that you should use this command CAREFULLY! - 10.32. demonstrate (9) + 11.32. demonstrate (9) demonstrate Demonstrate a command to another user @@ -3122,13 +2937,12 @@ - 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. - 10.33. directory (0) + 11.33. directory (0) directory List messages directory own List your own messages @@ -3158,29 +2972,23 @@ - You can abbreviate all the commands to one letter and use ak1a syntax:- - - - DIR/T G1* 10 - DIR/S QSL 10-100 5 + DIR/T G1* 10 + DIR/S QSL 10-100 5 - - - - 10.34. directory (extended for sysops) (5) + 11.34. directory (extended for sysops) (5) Works just like the user command except that sysops can see ALL messages. - 10.35. disconnect (8) + 11.35. disconnect (8) disconnect [ ...] Disconnect a user or node @@ -3188,7 +2996,7 @@ Disconnect any connected locally - 10.36. dx (0) + 11.36. dx (0) dx [by ] Send a DX spot @@ -3204,7 +3012,6 @@ - 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. @@ -3214,7 +3021,6 @@ - You can credit someone else by saying:- @@ -3223,15 +3029,14 @@ - The is compared against the available bands set up in the cluster. See SHOW/BANDS for more information. - - 10.37. export (9) + 11.37. export (9) export 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 @@ -3245,7 +3050,7 @@ EXPORT 2345 /tmp/a - 10.38. export_users (9) + 11.38. export_users (9) export_users [] Export the users database to ascii @@ -3261,7 +3066,7 @@ check is made on the filename (if any) that you specify. - 10.39. filtering (0) + 11.39. filtering (0) filtering Filtering things in DXSpider @@ -3363,7 +3168,6 @@ clear/spots 1 - To remove the filter in its entirty:- clear/spots all @@ -3394,7 +3198,7 @@ The next filter line lets through just VHF/UHF spots from EU. - 10.40. forward/latlong (8) + 11.40. forward/latlong (8) forward/latlong Send latitude and longitude information to another cluster @@ -3408,7 +3212,7 @@ so it is not recommended on slow links. - 10.41. forward/opername (1) + 11.41. forward/opername (1) forward/opername Send out information on this to all clusters @@ -3420,11 +3224,12 @@ available. - 10.42. help (0) + 11.42. help (0) help 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. @@ -3433,7 +3238,7 @@ commands to look at with HELP. - 10.43. init (5) + 11.43. init (5) init Re-initialise a link to an AK1A compatible node @@ -3447,7 +3252,7 @@ Best of luck - you will need it. - 10.44. kill (0) + 11.44. kill (0) kill [ ..] Delete a message from the local system @@ -3457,7 +3262,7 @@ the sysop). - 10.45. kill (5) + 11.45. kill (5) kill [ ...] Remove or erase a message from the system kill from Remove all messages from a callsign @@ -3470,7 +3275,7 @@ As a sysop you can kill any message on the system. - 10.46. kill full (5) + 11.46. kill full (5) kill full [] Delete a message from the whole cluster @@ -3481,7 +3286,7 @@ same subject will be deleted. Beware! - 10.47. kill/expunge (6) + 11.47. kill/expunge (6) kill/expunge [..]Expunge a message @@ -3490,13 +3295,15 @@ 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. - 10.48. links (0) + + 11.48. links (0) links Show which nodes are physically connected @@ -3506,7 +3313,7 @@ - 10.49. load/aliases (9) + 11.49. load/aliases (9) load/aliases Reload the command alias table @@ -3516,7 +3323,7 @@ running in order for the changes to take effect. - 10.50. load/badmsg (9) + 11.50. load/badmsg (9) load/badmsg Reload the bad message table @@ -3528,7 +3335,7 @@ deleted on receipt. - 10.51. load/badwords (9) + 11.51. load/badwords (9) load/badwords Reload the bad words table @@ -3542,7 +3349,7 @@ ignored. - 10.52. load/bands (9) + 11.52. load/bands (9) load/bands Reload the band limits table @@ -3551,18 +3358,19 @@ whilst the cluster is running. - 10.53. load/cmd_cache (9) + 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. - 10.54. load/forward (9) + + + 11.54. load/forward (9) load/forward Reload the msg forwarding routing table @@ -3570,7 +3378,7 @@ whilst the cluster is running. - 10.55. load/messages (9) + 11.55. load/messages (9) load/messages Reload the system messages file @@ -3583,7 +3391,7 @@ unknown message 'xxxx' in lang 'en' - 10.56. load/prefixes (9) + 11.56. load/prefixes (9) load/prefixes Reload the prefix table @@ -3592,7 +3400,7 @@ manually whilst the cluster is running. - 10.57. merge (5) + 11.57. merge (5) merge [/] Ask for the latest spots and WWV @@ -3607,7 +3415,7 @@ data). - 10.58. msg (9) + 11.58. msg (9) msg [data ...] Alter various message parameters @@ -3618,16 +3426,6 @@ - - - - - - - - - - MSG TO - change TO callsign to MSG FRom - change FROM callsign to MSG PRrivate - set private flag @@ -3645,7 +3443,6 @@ - You can look at the status of a message by using:- STAT/MSG @@ -3653,7 +3450,7 @@ This will display more information on the message than DIR does. - 10.59. pc (8) + 11.59. pc (8) pc Send text (eg PC Protocol) to @@ -3672,7 +3469,7 @@ pc G1TLH Try doing that properly!!! - 10.60. ping (1) + 11.60. ping (1) ping Check the link quality between nodes @@ -3685,7 +3482,7 @@ - 10.61. rcmd (1) + 11.61. rcmd (1) rcmd Send a command to another DX cluster @@ -3700,7 +3497,7 @@ whether you have permission to send this command at all. - 10.62. read (0) + 11.62. read (0) read Read the next unread personal message addressed to you read Read the specified message @@ -3711,7 +3508,7 @@ - 10.63. read (extended for sysops) (5) + 11.63. read (extended for sysops) (5) read Read a message on the system @@ -3719,7 +3516,7 @@ As a sysop you may read any message on the system - 10.64. reject/announce + 11.64. reject/announce reject/announce [0-9] Set a reject filter for announce @@ -3750,7 +3547,6 @@ - some examples:- @@ -3759,7 +3555,6 @@ - You can use the tag 'all' to reject everything eg: @@ -3768,11 +3563,10 @@ - but this probably for advanced users... - 10.65. reject/announce (extended for sysops) (8) + 11.65. reject/announce (extended for sysops) (8) reject/announce [input] [0-9] Announce filter sysop version @@ -3789,9 +3583,7 @@ - - - 10.66. reject/route (8) + 11.66. reject/route (8) reject/route [0-9] Set an 'reject' filter line for routing @@ -3819,19 +3611,14 @@ - - some examples:- - rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) - - You can use the tag 'all' to reject everything eg: @@ -3840,9 +3627,7 @@ - - - 10.67. reject/spots (0) + 11.67. reject/spots (0) reject/spots [0-9] Set a reject filter line for spots @@ -3874,7 +3659,6 @@ - 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 - @@ -3890,8 +3674,6 @@ - - You can use the tag 'all' to reject everything eg: @@ -3900,11 +3682,10 @@ - but this probably for advanced users... - 10.68. reject/spots (extended for sysops) (8) + 11.68. reject/spots (extended for sysops) (8) reject/spots [input] [0-9] Reject spot filter sysop version @@ -3923,9 +3704,7 @@ - - - 10.69. reject/wcy (0) + 11.69. reject/wcy (0) reject/wcy [0-9] Set a reject WCY filter @@ -3947,7 +3726,6 @@ - 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). @@ -3958,7 +3736,7 @@ - 10.70. reject/wcy (extended for sysops) (8) + 11.70. reject/wcy (extended for sysops) (8) reject/wcy [input] [0-9] WCY reject filter sysop version @@ -3970,7 +3748,7 @@ reject/wcy gb7djk all - 10.71. reject/wwv (0) + 11.71. reject/wwv (0) reject/wwv [0-9] Set a reject WWV filter @@ -3992,7 +3770,6 @@ - for example @@ -4001,14 +3778,13 @@ - is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information. - 10.72. reject/wwv (extended for sysops) (8) + 11.72. reject/wwv (extended for sysops) (8) reject/wwv [input] [0-9] WWV reject filter sysop version @@ -4024,7 +3800,7 @@ reject/wwv user_default by W - 10.73. reply (0) + 11.73. reply (0) reply Reply (privately) to the last message that you have read reply Reply (privately) to the specified message @@ -4041,7 +3817,7 @@ further details) - 10.74. send (0) + 11.74. send (0) send [ ...] Send a message to one or more callsigns send RR Send a message and ask for a read receipt @@ -4067,7 +3843,6 @@ - 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. @@ -4075,7 +3850,7 @@ is an alias for SEND PRIVATE - 10.75. set/address (0) + 11.75. set/address (0) set/address Record your postal address @@ -4083,14 +3858,14 @@ Literally, record your address details on the cluster. - 10.76. set/announce (0) + 11.76. set/announce (0) set/announce Allow announce messages Allow announce messages to arrive at your terminal. - 10.77. set/arcluster (5) + 11.77. set/arcluster (5) set/arcluster [ ...] Make the node_call an AR- Cluster type node @@ -4099,7 +3874,7 @@ Set the node_call as an AR-Cluster type node - 10.78. set/baddx (8) + 11.78. set/baddx (8) set/baddx Stop words we do not wish to see in the callsign field of a dx spot being propagated @@ -4117,7 +3892,6 @@ - To allow a word again, use the following command ... @@ -4126,9 +3900,7 @@ - - - 10.79. set/badnode (6) + 11.79. set/badnode (6) set/badnode Stop spots from this node_call being propagated @@ -4146,7 +3918,6 @@ - will stop anything from K1TTT (including any SSID's) @@ -4155,14 +3926,13 @@ - will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. - 10.80. set/badspotter (8) + 11.80. set/badspotter (8) set/badspotter Stop spots from this callsign being propagated @@ -4179,7 +3949,6 @@ - will stop anything from VE2STN. If you want SSIDs as well then you must enter them specifically. @@ -4189,14 +3958,13 @@ - will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. - 10.81. set/badword (8) + 11.81. set/badword (8) set/badword Stop things with this word being propogated @@ -4218,19 +3986,19 @@ - 10.82. set/beep (0) + 11.82. set/beep (0) set/beep Add beeps to terminal messages Add a beep to DX and other terminal messages. - 10.83. set/bbs (5) + 11.83. set/bbs (5) set/bbs [..]Make a BBS - 10.84. set/clx (5) + 11.84. set/clx (5) set/clx [ ...] Make the node_call a CLX type node @@ -4239,7 +4007,7 @@ Set the node_call as a CLX type node - 10.85. set/debug (9) + 11.85. set/debug (9) set/debug Add a debug level to the debug set @@ -4253,7 +4021,7 @@ You can remove a debug level with unset/debug - 10.86. set/dx (0) + 11.86. set/dx (0) set/dxAllow DX messages to arrive at your terminal @@ -4261,7 +4029,7 @@ You can stop DX messages with the unset/dx command - 10.87. set/dxgrid (0) + 11.87. set/dxgrid (0) set/dxgridAllow grid squares on the end of DX messages @@ -4271,7 +4039,7 @@ to remove the grid squares. - 10.88. set/dxnet (5) + 11.88. set/dxnet (5) set/dxnet [ ...] Make the node_call a DXNet type node @@ -4280,7 +4048,7 @@ Set the node_call as a DXNet type node - 10.89. set/echo (0) + 11.89. set/echo (0) set/echo Make the cluster echo your input @@ -4297,7 +4065,7 @@ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 10.90. set/email (0) + 11.90. set/email (0) set/email Set email address(es) and forward your personals @@ -4317,7 +4085,7 @@ UNSET/EMAIL - 10.91. set/here (0) + 11.91. set/here (0) set/here Set the here flag @@ -4328,7 +4096,7 @@ brackets around your callsign to indicate you are not available. - 10.92. set/homenode (0) + 11.92. set/homenode (0) set/homenode Set your home cluster @@ -4343,9 +4111,7 @@ - - - 10.93. set/hops (8) + 11.93. set/hops (8) set/hops ann|spots|wwv|wcy Set hop count @@ -4360,12 +4126,11 @@ - Set SHOW/HOPS for information on what is already set. This command creates a filter and works in conjunction with the filter system. - 10.94. set/isolate (9) + 11.94. set/isolate (9) set/isolate Isolate a node from the rest of the network @@ -4383,7 +4148,7 @@ You can remove the isolation with the command unset/isolate. - 10.95. set/language (0) + 11.95. set/language (0) set/language Set the language you wish to use @@ -4392,7 +4157,7 @@ Currently the languages available are en (English) and nl (Dutch). - 10.96. set/location (0) + 11.96. set/location (0) set/location Set your latitude and longitude @@ -4406,10 +4171,7 @@ - - - - 10.97. set/sys_location (9) + 11.97. set/sys_location (9) set/sys_location Set your cluster latitude and longitude @@ -4424,9 +4186,7 @@ - - - 10.98. set/logininfo (0) + 11.98. set/logininfo (0) set/logininfo Show logins and logouts of nodes and users @@ -4436,7 +4196,7 @@ - 10.99. set/lockout (9) + 11.99. set/lockout (9) set/lockout Stop a callsign connecting to the cluster @@ -4445,7 +4205,7 @@ allow the user to connect again, use the unset/lockout command. - 10.100. set/name (0) + 11.100. set/name (0) set/name Set your name @@ -4458,9 +4218,7 @@ - - - 10.101. set/node (9) + 11.101. set/node (9) set/node [ ...] Make the callsign an AK1A cluster @@ -4479,14 +4237,11 @@ - To see what your nodes are set to, use the show/nodes command. - - - 10.102. set/obscount (9) + 11.102. set/obscount (9) set/obscount Set the 'pump-up' obsolescence counter @@ -4507,7 +4262,7 @@ minutes, it is disconnected. - 10.103. set/page (0) + 11.103. set/page (0) set/page Set the number of lines per page @@ -4523,11 +4278,10 @@ - The setting is stored in your user profile. - 10.104. set/password (0) + 11.104. set/password (0) set/password Set your own password @@ -4542,7 +4296,7 @@ type, depending on the type of telnet client you have. - 10.105. set/password (9) + 11.105. set/password (9) set/password Set a users password @@ -4568,7 +4322,7 @@ password. - 10.106. set/pinginterval (9) + 11.106. set/pinginterval (9) set/pinginterval Set the ping time to neighbouring nodes @@ -4589,7 +4343,7 @@ for more information. - 10.107. set/privilege (9) + 11.107. set/privilege (9) set/privilege [ ...] Set the privilege level on a call @@ -4610,15 +4364,12 @@ - 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. - - - 10.108. set/spider (5) + 11.108. set/spider (5) set/spider [ ...] Make the node_call a DXSpider type node @@ -4627,12 +4378,12 @@ Set the node_call as a DXSpider type node - 10.109. set/sys_qra (9) + 11.109. set/sys_qra (9) set/sys_qra Set your cluster QRA locator - 10.110. set/qra (0) + 11.110. set/qra (0) set/qra Set your QRA locator @@ -4647,9 +4398,7 @@ - - - 10.111. set/qth (0) + 11.111. set/qth (0) set/qth Set your QTH @@ -4662,9 +4411,7 @@ - - - 10.112. set/register (9) + 11.112. set/register (9) set/register Mark a user as registered @@ -4687,7 +4434,7 @@ To unset a user use the 'unset/register' command - 10.113. set/talk (0) + 11.113. set/talk (0) set/talk Allow talk messages to be seen at your console @@ -4696,7 +4443,7 @@ talks with the unset/talk command. - 10.114. set/wcy (0) + 11.114. set/wcy (0) set/wcy Allow WCY messages to be seen at your console @@ -4705,7 +4452,7 @@ WCY messages with the unset/wcy command. - 10.115. set/wwv (0) + 11.115. set/wwv (0) set/wwv Allow WWV messages to be seen at your console @@ -4714,7 +4461,7 @@ WWV messages with the unset/wwv command. - 10.116. set/wx (0) + 11.116. set/wx (0) set/wx Allow WX messages to be seen at your console @@ -4723,7 +4470,7 @@ WX messages with the unset/wx command. - 10.117. show/baddx (1) + 11.117. show/baddx (1) show/baddxShow all the bad dx calls in the system @@ -4732,7 +4479,7 @@ information. - 10.118. show/badnode (6) + 11.118. show/badnode (6) show/badnode Show all the bad nodes in the system @@ -4741,7 +4488,7 @@ more information. - 10.119. show/badspotter (1) + 11.119. show/badspotter (1) show/badspotter Show all the bad spotters in the system @@ -4750,7 +4497,7 @@ SET/BADSPOTTER for more information. - 10.120. show/badword (1) + 11.120. show/badword (1) show/badword Show all the bad words in the system @@ -4759,7 +4506,7 @@ information. - 10.121. show/configuration (0) + 11.121. show/configuration (0) show/configuration [] Show all visible nodes and their users @@ -4773,7 +4520,7 @@ BE WARNED: the list that is returned can be VERY long - 10.122. show/configuration/node (0) + 11.122. show/configuration/node (0) show/configuration/node Show all the nodes connected @@ -4782,7 +4529,7 @@ connected. - 10.123. show/connect (1) + 11.123. show/connect (1) show/connect Show all the active connections @@ -4791,7 +4538,7 @@ the node. This command gives slightly more information than WHO. - 10.124. show/date (0) + 11.124. show/date (0) show/date [|] Show the local time @@ -4805,7 +4552,7 @@ including DST) at the prefixes or callsigns that you specify. - 10.125. show/debug (9) + 11.125. show/debug (9) show/debug Show what levels of debug you are logging @@ -4814,9 +4561,7 @@ - - - 10.126. show/dx (0) + 11.126. show/dx (0) show/dx [options] interrogate the spot database @@ -4829,7 +4574,6 @@ - on - eg 160m 20m 2m 23cm 6mm on - eg hf vhf uhf shf (see SHOW/BANDS) @@ -4862,12 +4606,10 @@ - e.g. - SH/DX 9m0 SH/DX on 20m info iota SH/DX 9a on vhf day 30 @@ -4878,11 +4620,7 @@ - - - - - 10.127. show/dxcc (0) + 11.127. show/dxcc (0) show/dxcc Interrogate the spot database by country @@ -4895,15 +4633,12 @@ - SH/DXCC G SH/DXCC W on 20m info iota - - - 10.128. sh/dxstats (0) + 11.128. sh/dxstats (0) sh/dxstats Show the DX Statistics for last 31 days @@ -4912,7 +4647,7 @@ - 10.129. show/files (0) + 11.129. show/files (0) show/files [ []] List the contents of a filearea @@ -4927,7 +4662,6 @@ - where is the name of the filearea you want to see the contents of. @@ -4940,11 +4674,10 @@ - See also TYPE - to see the contents of a file. - 10.130. show/filter (0) + 11.130. show/filter (0) show/filter Show the filters you have set @@ -4952,7 +4685,7 @@ displays all the filters set - for all the various categories. - 10.131. show/filter (extended for sysops) (5) + 11.131. show/filter (extended for sysops) (5) show/filter Show the filters set by @@ -4960,7 +4693,7 @@ A sysop can look at any filters that have been set. - 10.132. show/hfstats (0) + 11.132. show/hfstats (0) show/hfstats Show the HF DX Statistics for last 31 days @@ -4968,7 +4701,7 @@ Show the HF DX spots breakdown by band for the last 31 days - 10.133. show/hftable (0) + 11.133. show/hftable (0) show/hftable Show the HF DX Spotter Table for your country @@ -4976,7 +4709,7 @@ Show the HF DX Spotter table for your country for the last 31 days - 10.134. show/hops (8) + 11.134. show/hops (8) show/hops [ann|spots|wcy|wwv|] Show the hop counts for a node @@ -4987,7 +4720,7 @@ the categories will be listed. - 10.135. show/isolate (1) + 11.135. show/isolate (1) show/isolate Show a list of isolated nodes @@ -4995,7 +4728,7 @@ Show which nodes are currently set to be isolated. - 10.136. show/lockout (9) + 11.136. show/lockout (9) show/lockout Show a list of excluded callsigns @@ -5004,7 +4737,7 @@ cluster locally with the set/lockout command - 10.137. show/log (8) + 11.137. show/log (8) show/log [] Show excerpts from the system log @@ -5014,7 +4747,7 @@ show output from the log associated with that callsign. - 10.138. show/moon (0) + 11.138. show/moon (0) show/moon [|] Show moon rise and set times @@ -5042,9 +4775,7 @@ - - - 10.139. show/muf (0) + 11.139. show/muf (0) show/muf [][long] Show the likely propagation to @@ -5093,7 +4824,6 @@ - produces: @@ -5109,7 +4839,6 @@ - indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). @@ -5121,7 +4850,6 @@ - will get you the above display, but with the next 24 hours worth of propagation data. @@ -5132,13 +4860,12 @@ - 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. - 10.140. show/newconfiguration (0) + 11.140. show/newconfiguration (0) show/newconfiguration [] Show all the nodes and users visible @@ -5154,7 +4881,7 @@ BE WARNED: the list that is returned can be VERY long - 10.141. show/newconfiguration/node (0) + 11.141. show/newconfiguration/node (0) show/newconfiguration/node Show all the nodes connected locally @@ -5162,7 +4889,7 @@ Show all the nodes connected to this node in the new format. - 10.142. show/node (1) + 11.142. show/node (1) show/node [ ...] Show the type and version number of nodes @@ -5172,7 +4899,7 @@ the non-user callsigns known to the system will be displayed. - 10.143. show/prefix (0) + 11.143. show/prefix (0) show/prefix Interrogate the prefix database @@ -5186,7 +4913,7 @@ - 10.144. show/program (5) + 11.144. show/program (5) show/program Show the locations of all the included program modules @@ -5196,7 +4923,7 @@ from. - 10.145. show/qra (0) + 11.145. show/qra (0) show/qra [] Show the distance between locators show/qra Convert latitude and longitude to a locator @@ -5227,9 +4954,7 @@ - - - 10.146. show/qrz (0) + 11.146. show/qrz (0) show/qrz Show any callbook details on a callsign @@ -5239,12 +4964,12 @@ provided for users of this software by http://www.qrz.com - 10.147. show/registered (9) + 11.147. show/registered (9) show/registered [[ Show the registered users - 10.148. show/route (0) + 11.148. show/route (0) show/route Show the route to @@ -5258,9 +4983,7 @@ - - - 10.149. show/satellite (0) + 11.149. show/satellite (0) show/satellite [ ] Show satellite tracking data @@ -5292,9 +5015,7 @@ - - - 10.150. show/sun (0) + 11.150. show/sun (0) show/sun [|] Show sun rise and set times @@ -5319,9 +5040,7 @@ - - - 10.151. show/time (0) + 11.151. show/time (0) show/time [|] Show the local time @@ -5332,7 +5051,7 @@ including DST) at the prefixes or callsigns that you specify. - 10.152. show/vhfstats (0) + 11.152. show/vhfstats (0) show/vhfstats Show the VHF DX Statistics for last 31 days @@ -5340,14 +5059,14 @@ Show the VHF DX spots breakdown by band for the last 31 days - 10.153. show/vhftable (0) + 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 - 10.154. show/wcy (0) + 11.154. show/wcy (0) show/wcy Show the last 10 WCY broadcasts show/wcy Show the last WCY broadcasts @@ -5357,7 +5076,7 @@ system - 10.155. show/wwv (0) + 11.155. show/wwv (0) show/wwv Show the last 10 WWV broadcasts show/wwv Show the last WWV broadcasts @@ -5368,7 +5087,7 @@ - 10.156. shutdown (5) + 11.156. shutdown (5) shutdown Shutdown the cluster @@ -5377,7 +5096,7 @@ set to respawn in /etc/inittab it will of course restart. - 10.157. spoof (9) + 11.157. spoof (9) spoof Run commands as another user @@ -5388,7 +5107,7 @@ like home_node for example. - 10.158. stat/db (5) + 11.158. stat/db (5) stat/db Show the status of a database @@ -5400,7 +5119,7 @@ other than a sysop. - 10.159. stat/channel (5) + 11.159. stat/channel (5) stat/channel Show the status of a channel on the cluster @@ -5410,7 +5129,7 @@ Only the fields that are defined (in perl term) will be displayed. - 10.160. stat/msg (5) + 11.160. stat/msg (5) stat/msg Show the status of a message @@ -5424,17 +5143,17 @@ displayed. - 10.161. stat/route_node (5) + 11.161. stat/route_node (5) stat/route_node Show the data in a Route::Node object - 10.162. stat/route_user (5) + 11.162. stat/route_user (5) stat/route_user Show the data in a Route::User object - 10.163. stat/user (5) + 11.163. stat/user (5) stat/user Show the full status of a user @@ -5445,7 +5164,7 @@ Only the fields that are defined (in perl term) will be displayed. - 10.164. sysop (0) + 11.164. sysop (0) sysop Regain your privileges if you login remotely @@ -5470,25 +5189,22 @@ - 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. - 10.165. talk (0) + 11.165. talk (0) talk Enter talk mode with talk Send a text message to @@ -5528,7 +5244,6 @@ - To leave talk mode type: @@ -5537,12 +5252,7 @@ - - - - - - 10.166. type (0) + 11.166. type (0) type / Look at a file in one of the fileareas @@ -5557,12 +5267,11 @@ - See also SHOW/FILES to see what fileareas are available and a list of content. - 10.167. who (0) + 11.167. who (0) who Show who is physically connected locally @@ -5571,7 +5280,7 @@ what sort of connection they have - 10.168. wx (0) + 11.168. wx (0) wx Send a weather message to local users wx full Send a weather message to all cluster users @@ -5581,7 +5290,7 @@ extreme that may indicate enhanced conditions - 10.169. wx (enhanced for sysops) (5) + 11.169. wx (enhanced for sysops) (5) wx sysop Send a weather message to other clusters only @@ -5591,20 +5300,3 @@ - - - - - - - - - - - - - - - - - diff --git a/txt/installation.txt b/txt/installation.txt index 4f4f5dfc..7e8b480b 100644 --- a/txt/installation.txt +++ b/txt/installation.txt @@ -10,62 +10,7 @@ Table of Contents - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1. Linux Installation - 1.1 Introduction 1.2 Preparation 1.3 Installing the software @@ -74,9 +19,7 @@ 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 @@ -89,7 +32,6 @@ 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) @@ -101,7 +43,6 @@ 4.9 Autostarting the cluster 5. Microsoft Windows Installation - 5.1 Introduction 5.2 The requirements 5.3 The system @@ -110,19 +51,19 @@ 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 @@ -130,6 +71,8 @@ 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. @@ -175,26 +118,6 @@ Here are exactly the commands you must issue next: - - - - - - - - - - - - - - - - - - - - - # tar xvfz /usr/local/packages/Data-Dumper-2.10.tar.gz # cd Data-Dumper-2.10 @@ -247,7 +170,6 @@ - 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. @@ -274,8 +196,6 @@ - - For SuSE distributions, the command would be .. @@ -284,8 +204,6 @@ - - Now set a password for the user ... @@ -297,8 +215,6 @@ - - 1.3. Installing the software Now to unpack the DX Spider distribution, set symbolic links and group @@ -313,8 +229,6 @@ - - If you do not have the command groupadd available to you simply add a line in /etc/group by hand. @@ -324,8 +238,6 @@ - - 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 @@ -344,8 +256,6 @@ - - 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. @@ -362,8 +272,6 @@ - - 1.4. Setting callsigns etc Now login to your machine as the user you created earlier. In my case @@ -381,8 +289,6 @@ - - Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to suit your own environment. @@ -393,7 +299,6 @@ - This is the call sign of your cluster. If you use an SSID then include it here also. @@ -403,8 +308,6 @@ - - This is the sysop user callsign, normally your own. @@ -438,8 +341,6 @@ - - Now type the following command which creates the basic user file with you as the sysop. @@ -449,8 +350,6 @@ - - 1.5. The client program In earlier versions of Spider, all the processes were Perl scripts. @@ -480,8 +379,6 @@ - - If all is well then login on another term or console as sysop and cd to /spider/src. Now issue the following command ... @@ -491,8 +388,6 @@ - - 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 @@ -505,8 +400,6 @@ - - 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 .... @@ -517,15 +410,10 @@ - - 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 @@ -657,7 +545,6 @@ - o libax25-0.0.7-7.i386.rpm o ax25-tools-0.0.6-13.i386.rpm @@ -697,8 +584,6 @@ - - 3.4. Configuration You will find the configuration files in /etc/ax25. These consist of @@ -737,8 +622,6 @@ - - Note that the portnames have to be unique. @@ -754,7 +637,6 @@ - 3.6. nrports This file sets up the netrom ports you want to use. An example is @@ -769,8 +651,6 @@ - - Note that the portnames have to be unique. @@ -786,10 +666,6 @@ - - - - 3.7. nrbroadcast This file sets up the netrom broadcast qualities. An example is below @@ -802,8 +678,6 @@ - - The file headings are as follows ... @@ -818,7 +692,6 @@ - 3.8. ax25d.conf This file controls any incoming ax25 and NET/ROM connections and @@ -829,33 +702,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - [gb7mbc-0 via 2m] parameters 2 1 6 900 * 15 0 NOCALL * * * * * * L @@ -888,8 +734,6 @@ - - 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 @@ -908,8 +752,6 @@ - - however, if you wish your users to be able to use SSID's on their callsigns .. @@ -919,9 +761,6 @@ - - - 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 @@ -934,8 +773,6 @@ - - 3.9. node.conf For those of you that wish to run the node, you need to set up the @@ -947,47 +784,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # /etc/ax25/node.conf - LinuxNode configuration file # # see node.conf(5) @@ -1069,8 +865,6 @@ - - This should be fairly obvious I hope. @@ -1094,8 +888,6 @@ - - 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 ... @@ -1107,8 +899,6 @@ - - The command 'man kissparms' will give you the explanation of the switches. @@ -1134,8 +924,6 @@ - - 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. @@ -1150,8 +938,6 @@ - - Assuming you want it to run on port 3000 @@ -1174,8 +960,6 @@ - - You now need to restart the xinetd daemon. First find out what the PID is like so .. @@ -1185,7 +969,6 @@ - You will get a reply something like this ... @@ -1194,8 +977,6 @@ - - The PID or Process ID is 592 in this case so now we can issue the command ... @@ -1205,8 +986,6 @@ - - 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 ... @@ -1216,8 +995,6 @@ - - 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. @@ -1248,16 +1025,12 @@ - - 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 .... @@ -1266,8 +1039,6 @@ - - Now login as sysop and cd spider/src. You can test that spider is accepting telnet logins by issuing the following command .... @@ -1277,8 +1048,6 @@ - - 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 @@ -1293,8 +1062,6 @@ - - You should now get the login prompt and be able to login as before. @@ -1315,9 +1082,6 @@ - - - to make the change happen... @@ -1334,8 +1098,6 @@ - - As standard, the listener will listen on all interfaces simultaneously. If you require more control than this, you can specify each interface individually:- @@ -1349,8 +1111,6 @@ - - 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. @@ -1391,7 +1151,6 @@ - 4.5. Setting up node connects In order to allow cluster node connections, spider needs to know that @@ -1416,8 +1175,6 @@ - - For now, we will assume that the cluster we are going to connect to is an AK1A type node. @@ -1433,8 +1190,6 @@ - - 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. @@ -1449,7 +1204,6 @@ - You should get an initialisation string from DXSpider like this ... @@ -1459,7 +1213,6 @@ - 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. @@ -1475,8 +1228,6 @@ - - 4.6. Connection scripts Because DXSpider operates under Linux, connections can be made using @@ -1555,11 +1306,6 @@ - - - - - timeout 60 abort (Busy|Sorry|Fail) # this does exactly the same as the previous example @@ -1570,11 +1316,6 @@ - - - - - timeout 15 connect telnet dirkl.tobit.co.uk # tell GB7DJK-1 that it is connected to GB7DJK @@ -1600,8 +1341,6 @@ - - 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 @@ -1638,8 +1377,6 @@ - - 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 @@ -1658,8 +1395,6 @@ - - 4.8. Telnet echo Cluster links in particular suffer greatly from the presence of telnet @@ -1691,8 +1426,6 @@ - - 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 @@ -1730,8 +1463,6 @@ - - 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 ... @@ -1742,8 +1473,6 @@ - - The line required for Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for this information. @@ -1753,8 +1482,6 @@ - - This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart it should it crash for any reason. @@ -1898,7 +1625,6 @@ - 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 @@ -1911,7 +1637,6 @@ - D:\ppm>ppm install Data-Dumper.ppd Installing package 'Data-Dumper.ppd' Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs @@ -1925,7 +1650,6 @@ - I'm not going to bother you with exhaustive details of the rest of them, but suffice it to say you need to: @@ -1938,7 +1662,6 @@ - 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 @@ -2006,7 +1729,6 @@ - Now you'll need to edit this file using a text editor like Notepad. If nothing else, you can simply @@ -2016,7 +1738,6 @@ - and then @@ -2025,7 +1746,6 @@ - to bring up an editor window containing the file. As an absolute minimum you must adjust the following items in DXVars.pm:- @@ -2067,7 +1787,6 @@ - The following line need attention:- @@ -2076,7 +1795,6 @@ - On my machine, I've simply uncommented the "0.0.0.0" entry by removing the '#' from the front of the line. @@ -2130,7 +1848,6 @@ - and then @@ -2139,7 +1856,6 @@ - to bring up an editor window containing the file. You must consider adjusting the following items in AGWConnect.pm:- @@ -2168,7 +1884,6 @@ - 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. @@ -2180,7 +1895,6 @@ - If you did everything you were told, your DOS window will now hold a display which looks something like:- @@ -2211,7 +1925,6 @@ - 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) @@ -2226,7 +1939,6 @@ - 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 @@ -2239,7 +1951,6 @@ - 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 @@ -2257,7 +1968,6 @@ - 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) @@ -2302,8 +2012,6 @@ - - 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 @@ -2314,63 +2022,3 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/txt/spiderCVS.txt b/txt/spiderCVS.txt index 3532d369..df62beec 100644 --- a/txt/spiderCVS.txt +++ b/txt/spiderCVS.txt @@ -17,50 +17,3 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/txt/spiderFAQ.txt b/txt/spiderFAQ.txt index f32efc22..315f73cb 100644 --- a/txt/spiderFAQ.txt +++ b/txt/spiderFAQ.txt @@ -9,14 +9,12 @@ 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. @@ -51,8 +49,6 @@ - - assuming the patch version you are using is 1.40 and resides in /tmp! @@ -61,9 +57,6 @@ first need to apply patch-1.39 and then patch-1.40. - - - 11..33.. IIff II uussee aa ttaarrbbaallll ttoo oovveerrwwrriittee mmyy iinnssttaallllaattiioonn,, wwhhaatt hhaappppeennss ttoo mmyy ccoonnffiigguurraattiioonn?? @@ -93,7 +86,6 @@ - Run _t_e_l_i_n_i_t _q 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. @@ -110,7 +102,6 @@ - or in later versions of Spider, there is a command called _w_a_t_c_h_d_b_g in which case you simply type .. @@ -120,8 +111,6 @@ - - 22..33.. MMyy nneeiigghhbboouurriinngg nnooddee ccaannnnoott uussee tthhee RRCCMMDD ccoommmmaanndd ttoo mmee,, hhee jjuusstt kkeeeeppss ggeettttiinngg tthhee ""ttuutt ttuutt"" mmeessssaaggee.. @@ -130,8 +119,8 @@ reset the home_node using the _s_p_o_o_f command like this .. - spoof gb7adx set/home gb7adx + spoof gb7adx set/home gb7adx @@ -159,7 +148,6 @@ - Remember to make it executable! This will limit your debug data down to the last 10 days @@ -202,63 +190,3 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/txt/usermanual.txt b/txt/usermanual.txt index a373bc0d..efe38ffd 100644 --- a/txt/usermanual.txt +++ b/txt/usermanual.txt @@ -9,97 +9,33 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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. @@ -107,16 +43,13 @@ 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 - 12.1 accept/announce 12.2 accept/spots 12.3 accept/wcy @@ -262,10 +195,8 @@ - connect GB7MBC - connect GB7MBC-1 - - + connect GB7MBC + connect GB7MBC-1 @@ -287,8 +218,6 @@ - - 22..33.. TTeellnneett llooggiinnss.. With telnet connections, the source callsign is not seen by DXSpider, @@ -305,7 +234,6 @@ - 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 @@ -328,6 +256,7 @@ the TNC or by altering your program configuration. + 33.. SSeettttiinngg yyoouurr ppeerrssoonnaall ddeettaaiillss.. Once logged in to the cluster, you should set your details so that @@ -355,8 +284,6 @@ - - 44.. GGeettttiinngg aanndd ppoossttiinngg DDXX.. When all is said and done, this is the main function of a DX cluster. @@ -392,8 +319,6 @@ - - will show the last 10, 5 and 20 spots received by the cluster respectively. @@ -406,8 +331,6 @@ 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 @@ -422,7 +345,6 @@ - would show the last 5 or 10 dx spots containing the callsign g0vgs. @@ -439,7 +361,6 @@ - would show the spots that arrived between 30 and 40 spots ago and any spots with the word _i_o_t_a in the comment field. The case of the comment is not important. @@ -455,14 +376,14 @@ - It is of course possible to specify multiple arguments. EExxaammppllee:: - show/dx 20 prefix 9a on vhf day 30 + show/dx 20 prefix 9a on vhf day 30 + This would show the last 20 spots posted by or about calls with the @@ -472,7 +393,6 @@ sure whether something will work or not, try it and see! More information can be found in the Command Set section. - 44..22.. PPoossttiinngg DDXX.. To post DX you use the DDXX command. The syntax is shown below. @@ -485,7 +405,6 @@ - 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 @@ -500,7 +419,6 @@ - In fact, all the following will give the same result... @@ -511,7 +429,6 @@ - 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 @@ -526,6 +443,8 @@ 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. + + 55..11.. SSuunn The SSHHOOWW//SSUUNN command can be used in three different ways. It can be @@ -536,8 +455,7 @@ - show/sun - + show/sun @@ -551,14 +469,10 @@ - - - sh/sun 5b4 - would look like this ... @@ -569,7 +483,6 @@ - You can also specify multiple arguments like this ... @@ -578,7 +491,6 @@ - and then the output would look like this ... @@ -592,6 +504,7 @@ ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0 + 55..22.. MMoooonn The SSHHOOWW//MMOOOONN command works in the same way as the SSHHOOWW//SSUUNN command. @@ -607,7 +520,6 @@ - The output from this command would look like this .. @@ -618,7 +530,6 @@ - You can see that the output is similar to the SSHHOOWW//SSUUNN command, with slightly different fields. @@ -637,7 +548,6 @@ - The output from this command would look like this .. @@ -650,8 +560,6 @@ - - 66.. AAnnnnoouunncceemmeennttss.. 66..11.. MMaakkiinngg aannnnoouunncceemmeennttss.. @@ -665,12 +573,10 @@ EExxaammppllee:: - 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 FFUULLLL @@ -684,7 +590,6 @@ - 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 @@ -706,8 +611,6 @@ - - 77.. NNooddeess aanndd uusseerrss.. You can check which nodes are connected in the network, who is logged @@ -720,15 +623,10 @@ - - - - - show/configuration - show/configuration/nodes - show/configuration (node_call) - show/configuration (prefix) - + show/configuration + show/configuration/nodes + show/configuration (node_call) + show/configuration (prefix) @@ -736,27 +634,26 @@ - 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 - + 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 @@ -784,19 +681,17 @@ - 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 - + 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 @@ -821,7 +716,6 @@ - The output of this command would look like this, @@ -832,8 +726,6 @@ - - 88.. TTaallkk mmooddee.. You can send a single comment or start a dedicated talk session to @@ -852,10 +744,10 @@ - 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. @@ -866,8 +758,6 @@ 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 @@ -879,7 +769,6 @@ - To exit talk mode, you issue the command //eexx. Whilst in talk mode you will still receive DX spots. This means that @@ -912,7 +801,6 @@ - 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 @@ -934,8 +822,6 @@ - - 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 @@ -963,7 +849,6 @@ - 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 @@ -983,11 +868,11 @@ - 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. + EExxaammppllee:: @@ -996,9 +881,6 @@ - - - 99..33.. SSeennddiinngg mmaaiill.. Sending mail is done in the time honoured way. First you specify a @@ -1024,7 +906,6 @@ - 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 @@ -1047,13 +928,13 @@ - - 99..55.. DDeelleettiinngg mmaaiill To delete a message, you use the _d_e_l_e_t_e command. You can only delete messages sent to or received by yourself. Bulletins are dealt with automatically or by the sysop. + + 1100.. FFiilltteerriinngg ((FFrroomm vveerrssiioonn 11..4455)) 1100..11.. GGeenneerraall ffiilltteerr rruulleess @@ -1077,13 +958,11 @@ - 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 @@ -1099,7 +978,6 @@ - There is clear/xxxx command for each type of filter. @@ -1107,19 +985,14 @@ - 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. - - 1100..22.. TTyyppeess ooff ffiilltteerr There are two main types of filter, _a_c_c_e_p_t or _r_e_j_e_c_t. You can use @@ -1143,7 +1016,6 @@ - then you will _O_N_L_Y get VHF spots _f_r_o_m or _t_o CQ zones 14, 15 and 16. @@ -1155,7 +1027,6 @@ - Then you will get everything _E_X_C_E_P_T 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 @@ -1167,7 +1038,6 @@ - But in that case you might only be interested in iota and say:- @@ -1176,7 +1046,6 @@ - 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 @@ -1186,16 +1055,16 @@ 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 @@ -1217,7 +1086,6 @@ - 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'. @@ -1233,7 +1101,6 @@ - would redefine our earlier example, or @@ -1242,7 +1109,6 @@ - To remove all the filter lines in the spot filter ... @@ -1251,13 +1117,13 @@ - 1100..33.. FFiilltteerr ooppttiioonnss You can filter in several different ways. The options are listed in the various helpfiles for accept, reject and filter. + 1100..44.. AAddvvaanncceedd ffiilltteerriinngg Once you are happy with the results you get, you may like to @@ -1275,7 +1141,6 @@ - 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 _r_e_j_e_c_t _a_l_l _H_F _s_p_o_t_s _i_n _t_h_e _C_W _s_e_c_t_i_o_n _o_f _t_h_e _b_a_n_d_s _b_u_t _a_c_c_e_p_t _a_l_l @@ -1323,6 +1188,7 @@ AA..Use the SSEETT//BBEEEEPP command. You can find information on this in the "DXSpider Command Reference" section. + QQ..I got disconnected from the cluster and now I can't log back in again. What is wrong? @@ -1375,7 +1241,6 @@ - some examples:- @@ -1384,15 +1249,14 @@ 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 + 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: @@ -1402,7 +1266,6 @@ - but this probably for advanced users... @@ -1438,8 +1301,6 @@ - - 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 - @@ -1450,10 +1311,8 @@ - acc/spot 1 on hf/cw - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - + 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: @@ -1464,7 +1323,6 @@ - but this probably for advanced users... @@ -1490,8 +1348,6 @@ - - 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). @@ -1511,22 +1367,15 @@ - - - - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel for example @@ -1537,7 +1386,6 @@ - is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). @@ -1579,9 +1427,6 @@ This will disconnect you from the cluster - - - 1122..99.. cclleeaarr//ssppoottss cclleeaarr//ssppoottss [[11||aallll]] Clear a spot filter line @@ -1598,8 +1443,6 @@ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - and you say:- @@ -1608,7 +1451,6 @@ - you will be left with:- @@ -1617,7 +1459,6 @@ - If you do: @@ -1626,7 +1467,6 @@ - the filter will be completely removed. @@ -1648,10 +1488,12 @@ 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 + 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: @@ -1662,8 +1504,6 @@ - - 1122..1122.. ddiirreeccttoorryy ddiirreeccttoorryy List messages @@ -1694,7 +1534,6 @@ - You can abbreviate all the commands to one letter and use ak1a syntax:- @@ -1705,8 +1544,6 @@ - - 1122..1133.. ddxx ddxx [[bbyy <>]] <> <> <> Send a DX spot @@ -1714,20 +1551,21 @@ This is how you send a DX Spot to other users. You can, in fact, now enter the and the 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 - + DX FR0G 144600 this is a test @@ -1739,7 +1577,6 @@ - The is compared against the available bands set up in the cluster. See SHOW/BANDS for more information. @@ -1780,6 +1617,8 @@ rreeaadd Read the next unread personal message addressed to you rreeaadd <> 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. @@ -1789,6 +1628,7 @@ rreejjeecctt//aannnnoouunnccee [[00--99]] <> 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 @@ -1815,7 +1655,6 @@ - some examples:- @@ -1824,7 +1663,6 @@ - You can use the tag 'all' to reject everything eg: @@ -1833,7 +1671,6 @@ - but this probably for advanced users... @@ -1853,20 +1690,19 @@ - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - call eg: G,PA,HB9 - info eg: iota or qsl - by - call_dxcc eg: 61,62 (from eg: sh/pre G) - call_itu - call_zone - by_dxcc - by_itu - by_zone - origin - channel - + freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on same as 'freq' + call eg: G,PA,HB9 + info eg: iota or qsl + by + call_dxcc eg: 61,62 (from eg: sh/pre G) + call_itu + call_zone + by_dxcc + by_itu + by_zone + origin + channel @@ -1885,7 +1721,6 @@ - You can use the tag 'all' to reject everything eg: @@ -1894,7 +1729,6 @@ - but this probably for advanced users... @@ -1908,21 +1742,15 @@ - - - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel - - + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel There are no examples because WCY Broadcasts only come from one place @@ -1956,7 +1784,6 @@ - for example @@ -1965,7 +1792,6 @@ - is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). @@ -1989,6 +1815,7 @@ further details) + 1122..2233.. sseenndd sseenndd <> [[<> ......]] Send a message to one or more callsigns @@ -2015,7 +1842,6 @@ - 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. @@ -2108,8 +1934,6 @@ - - 1122..3322.. sseett//llaanngguuaaggee sseett//llaanngguuaaggee <> Set the language you wish to use @@ -2120,6 +1944,7 @@ (Dutch). + 1122..3333.. sseett//llooccaattiioonn sseett//llooccaattiioonn <> Set your latitude and longitude @@ -2134,8 +1959,6 @@ - - 1122..3344.. sseett//llooggiinniinnffoo sseett//llooggiinniinnffoo Show logins and logouts of nodes and users @@ -2158,8 +1981,6 @@ - - 1122..3366.. sseett//ppaaggee sseett//ppaaggee <> Set the number of lines per page @@ -2184,6 +2005,7 @@ sseett//qqrraa <> 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:- @@ -2194,8 +2016,6 @@ - - 1122..3388.. sseett//qqtthh sseett//qqtthh <> Set your QTH @@ -2209,8 +2029,6 @@ - - 1122..3399.. sseett//ttaallkk sseett//ttaallkk Allow talk messages to be seen at your console @@ -2242,10 +2060,12 @@ sseett//wwxx 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 _u_n_s_e_t_/_w_x command. + 1122..4433.. sshhooww//ccoonnffiigguurraattiioonn sshhooww//ccoonnffiigguurraattiioonn [[<>]] Show all visible nodes and their users @@ -2297,17 +2117,6 @@ - - - - - - - - - - - on - eg 160m 20m 2m 23cm 6mm on - eg hf vhf uhf shf (see SHOW/BANDS) @@ -2340,12 +2149,10 @@ - e.g. - SH/DX 9m0 SH/DX on 20m info iota SH/DX 9a on vhf day 30 @@ -2356,8 +2163,6 @@ - - 1122..4477.. sshhooww//ddxxcccc sshhooww//ddxxcccc <> Interrogate the spot database by country @@ -2371,16 +2176,11 @@ - - - SH/DXCC G SH/DXCC W on 20m info iota - - 1122..4488.. sshhooww//ffiilleess sshhooww//ffiilleess [[<> [[<>]]]] List the contents of a filearea @@ -2396,7 +2196,6 @@ - where is the name of the filearea you want to see the contents of. @@ -2409,7 +2208,6 @@ - See also TYPE - to see the contents of a file. @@ -2449,8 +2247,6 @@ - - 1122..5511.. sshhooww//mmuuff sshhooww//mmuuff <> [[<>]][[lloonngg]] Show the likely propagation to @@ -2500,12 +2296,10 @@ - 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 @@ -2517,7 +2311,6 @@ - indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). @@ -2529,7 +2322,6 @@ - will get you the above display, but with the next 24 hours worth of propagation data. @@ -2540,7 +2332,6 @@ - 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. @@ -2577,7 +2368,6 @@ - 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 @@ -2593,8 +2383,6 @@ - - 1122..5544.. sshhooww//qqrrzz sshhooww//qqrrzz <> Show any callbook details on a callsign @@ -2619,8 +2407,6 @@ - - 1122..5566.. sshhooww//ssaatteelllliittee sshhooww//ssaatteelllliittee <> [[<> <>]] Show satellite tracking @@ -2652,8 +2438,6 @@ - - 1122..5577.. sshhooww//ssuunn sshhooww//ssuunn [[<>||<>]] Show sun rise and set times @@ -2679,8 +2463,6 @@ - - 1122..5588.. sshhooww//ttiimmee sshhooww//ttiimmee [[<>||<>]] Show the local time @@ -2703,7 +2485,6 @@ - 1122..6600.. sshhooww//wwwwvv sshhooww//wwwwvv Show the last 10 WWV broadcasts @@ -2739,7 +2520,6 @@ - you type:- @@ -2750,7 +2530,6 @@ - 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. @@ -2796,7 +2575,6 @@ - To leave talk mode type: @@ -2805,8 +2583,6 @@ - - 1122..6633.. ttyyppee ttyyppee <>//<> Look at a file in one of the fileareas @@ -2822,7 +2598,6 @@ - See also SHOW/FILES to see what fileareas are available and a list of content. @@ -2847,58 +2622,3 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1.1 Introduction +

1.2 Route Filters +(using the rcmd command). + +

1.3 The node_default filter +of explanation. + +

1.4 General route filtering + + +

1.5 General filter rules +see the next section. + + +

1.6 Types of filter +principles to all types of filter. + +

1.7 Filter options + + +

1.8 Default filters +various helpfiles for accept, reject and filter. + +

1.9 Advanced filtering +default filter for spots, you need to add a rule for the hops for spots also. + +

1.10 Basic hop control +lets through just VHF/UHF spots from EU. + +

1.11 Hop Control on Specific Nodes +bring your changes into effect. + +

1.12 Isolating networks + +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. + +

10.1 accept/announce (0) -

10.2 accept/announce (extended for sysops) (8) -

10.3 accept/route (8) -

10.4 accept/spots (0) -

10.5 accept/spots (extended for sysops) (8) -

10.6 accept/wcy (0) -

10.7 accept/wcy (extended for sysops) (8) -

10.8 accept/wwv (0) -

10.9 accept/wwv (extended for sysops) (8) -

10.10 announce (0) -

10.11 announce full (0) -

10.12 announce sysop (5) -

10.13 apropos (0) -

10.14 bye (0) -

10.15 catchup (5) -

10.16 clear/announce (8) -

10.17 clear/route (8) -

10.18 clear/spots (0) -

10.19 clear/spots (extended for sysops) (8) -

10.20 clear/wcy (0) -

10.21 clear/wcy (extended for sysops) (8) -

10.22 clear/wwv (0) -

10.23 clear/wwv (extended for sysops) (8) -

10.24 connect (5) -

10.25 dbavail (0) -

10.26 dbcreate (9) -

10.27 dbimport (9) -

10.28 dbremove (9) -

10.29 dbshow (0) -

10.30 debug (9) -

10.31 delete/user (9) -

10.32 demonstrate (9) -

10.33 directory (0) -

10.34 directory (extended for sysops) (5) -

10.35 disconnect (8) -

10.36 dx (0) -

10.37 export (9) -

10.38 export_users (9) -

10.39 filtering (0) -

10.40 forward/latlong (8) -

10.41 forward/opername (1) -

10.42 help (0) -

10.43 init (5) -

10.44 kill (0) -

10.45 kill (5) -

10.46 kill full (5) -

10.47 kill/expunge (6) -

10.48 links (0) -

10.49 load/aliases (9) -

10.50 load/badmsg (9) -

10.51 load/badwords (9) -

10.52 load/bands (9) -

10.53 load/cmd_cache (9) -

10.54 load/forward (9) -

10.55 load/messages (9) -

10.56 load/prefixes (9) -

10.57 merge (5) -

10.58 msg (9) -

10.59 pc (8) -

10.60 ping (1) -

10.61 rcmd (1) -

10.62 read (0) -

10.63 read (extended for sysops) (5) -

10.64 reject/announce -

10.65 reject/announce (extended for sysops) (8) -

10.66 reject/route (8) -

10.67 reject/spots (0) -

10.68 reject/spots (extended for sysops) (8) -

1.2 Route Filters +(using the rcmd command).
+ +

1.3 The node_default filter +of explanation.
+ +

1.4 General route filtering +
+ +

1.5 General filter rules +see the next section.
+ + +

1.6 Types of filter +principles to all types of filter.
+ +

1.7 Filter options +
+ +

1.8 Default filters +various helpfiles for accept, reject and filter.
+ +

1.9 Advanced filtering +default filter for spots, you need to add a rule for the hops for spots also.
+ +

1.10 Basic hop control +lets through just VHF/UHF spots from EU.
+ +

1.11 Hop Control on Specific Nodes +bring your changes into effect.
+ +

1.12 Isolating networks +
+
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.
+ +