From: g0vgs Date: Tue, 17 Apr 2001 20:44:11 +0000 (+0000) Subject: trying again after broken pipe error X-Git-Tag: R_1_47~19 X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=commitdiff_plain;h=b8ff94755eecda16276c449274c6a76c4f14a8d1;p=spider.git trying again after broken pipe error --- diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html new file mode 100644 index 00000000..b9691bbb --- /dev/null +++ b/html/adminmanual-1.html @@ -0,0 +1,140 @@ + + + + + The DXSpider Administration Manual v1.47: Hop control + + + + + + +Next +Previous +Contents +

1. Hop control

+ +

Starting with version 1.13 there is simple hop control available on a per +node basis. Also it is possible to isolate a network completely so that you +get all the benefits of being on that network, but can't pass on information +from it to any other networks you may be connected to (or vice versa). +

1.1 Basic hop control +

+ +

In /spider/data you will find a file called hop_table.pl. This is the file +that controls your hop count settings. It has a set of default hops on the +various PC frames and also a set for each node you want to alter the hops for. +You may be happy with the default settings of course, but this powerful tool +can help to protect and improve the network. The file will look something +like this ... +


++# 
+# hop table construction
+# 
+
+package DXProt;
+
+# default hopcount to use
+$def_hopcount = 5;
+
+# some variable hop counts based on message type
+%hopcount = 
+(
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+);
+
+
+# the per node hop control thingy
+
+
+%nodehops = 
+
+ GB7ADX => {            11 => 8,
+                        12 => 8,
+                        16 => 8,
+                        17 => 8,
+                        19 => 8,
+                        21 => 8,
+                   },
+
+ GB7UDX => {            11 => 8,
+                        12 => 8,
+                        16 => 8,
+                        17 => 8,
+                        19 => 8,
+                        21 => 8,
+                   },
+ GB7BAA => {
+                        11 => 5,
+                        12 => 8,
+                        16 => 8,
+                        17 => 8,
+                        19 => 8,
+                        21 => 8,
+                   },
+};
+
+

Each set of hops is contained within a pair of curly braces and contains a +series of PC frame types. PC11 for example is a DX spot. The figures here +are not exhaustive but should give you a good idea of how the file works. +

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.2 Isolating networks +

+ +

It is possible to isolate networks from each other on a "gateway" node using the +set/isolate <node_call> command. +

The effect of this is to partition an isolated network completely from another +nodes connected to your node. Your node will appear on and otherwise behave +normally on every network to which you are connected, but data from an isolated +network will not cross onto any other network or vice versa. However all the +spot, announce and WWV traffic and personal messages will still be handled +locally (because you are a real node on all connected networks), that is locally +connected users will appear on all networks and will be able to access and +receive information from all networks transparently. All routed messages will +be sent as normal, so if a user on one network knows that you are a gateway for +another network, he can still still send a talk/announce etc message via your +node and it will be routed across. +

The only limitation currently is that non-private messages cannot be passed down +isolated links regardless of whether they are generated locally. This will change +when the bulletin routing facility is added. +

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 put in a filter in the /spider/filter/spots +directory to override the isolate. This filter can be very simple and consists +of just one line .... +


++$in = [
+        [ 1, 0, 'd', 0, 3]      # The last figure (3) is the hop count
+];
+
+

There is a lot more on filtering in the next section. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html new file mode 100644 index 00000000..39b9bde3 --- /dev/null +++ b/html/adminmanual-2.html @@ -0,0 +1,247 @@ + + + + + The DXSpider Administration Manual v1.47: Filtering (Old Style upto v1.44) + + + + + + +Next +Previous +Contents +

2. Filtering (Old Style upto v1.44)

+ +

Filters can be set for spots, announcements and WWV. You will find the +directories for these under /spider/filter. You will find some examples in +the directories with the suffix .issue. There are two types of +filter, one for incoming information and one for outgoing information. +Outgoing filters are in the form CALLSIGN.pl and incoming filters +are in the form in_CALLSIGN.pl. Filters can be set for both nodes +and users. +

All filters work in basically the same way. There are several elements +delimited by commas. There can be many lines in the filter and they are +read from the top by the program. When writing a filter you need to think +carefully about just what you want to achieve. You are either going to write +a filter to accept or to reject. Think of a filter as +having 2 main elements. For a reject filter, you would have a line or multiple +lines rejecting the things you do not wish to receive and then a default line +accepting everything else that is not included in the filter. Likewise, for an +accept filter, you would have a line or multiple lines accepting the things you +wish to receive and a default line rejecting everthing else. +

In the example below, a user requires a filter that would only return SSB spots +posted in Europe on the HF bands. This is achieved by first rejecting the CW +section of each HF band and rejecting all of VHF, UHF etc based on frequency. +Secondly, a filter rule is set based on CQ zones to only accept spots posted in +Europe. Lastly, a default filter rule is set to reject anything outside the filter. +


++$in = [
+        [ 0, 0, 'r', # reject all CW spots
+                [
+                1800.0, 1850.0,
+                3500.0, 3600.0,
+                7000.0, 7040.0,
+                14000.0, 14100.0,
+                18068.0, 18110.0,
+                21000.0, 21150.0,
+                24890.0, 24930.0,
+                28000.0, 28180.0,
+                30000.0, 49000000000.0,
+                ] ,1 ],
+        [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
+        [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
+];
+
+

The actual elements of each filter are described more fully in the following +sections. +

2.1 Spots +

+ +

The elements of the Spot filter are .... +


++[action, field_no, sort, possible_values, hops]
+
+

There are 3 elements here to look at. Firstly, the action element. This is +very simple and only 2 possible states exist, accept (1) or drop (0). +

The second element is the field_no. There are 13 possiblities to choose from +here .... +


++      0 = frequency
+      1 = call
+      2 = date in unix format
+      3 = comment
+      4 = spotter
+      5 = spotted dxcc country
+      6 = spotter's dxcc country
+      7 = origin
+      8 = spotted itu
+      9 = spotted cq
+      10 = spotter's itu
+      11 = spotter's cq
+      12 = callsign of the channel on which the spot has appeared
+
+

The third element tells us what to expect in the fourth element. There are +4 possibilities .... +


++     n - numeric list of numbers e.g. [ 1,2,3 ]
+     r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
+     a - an alphanumeric regex
+     d - the default rule
+
+

The fifth element is simply the hops to set in this filter. This would only +be used if the filter was for a node of course and overrides the hop count in +hop_table.pl. +

So, let's look at an example spot filter. It does not matter in the example +who the filter is to be used for. So, what do we need in the filter? We need +to filter the spots the user/node requires and also set a default rule for +anything else outside the filter. Below is a simple filter that stops spots +arriving from outside Europe. +


++$in = [
+  [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'],  # 0 = drop, 'a' = alphanumeric
+  [ 1, 0, 'd', 0, 1 ],                 # 1 = want, 'd' = everything else
+                     ];
+
+

So the filter is wrapped in between a pair of square brackets. This tells +Spider to look in between these limits. Then each line is contained within +its own square brackets and ends with a comma. Lets look carefully at the first +line. The first element is 0 (drop). Therefore anything we put on this line +will not be accepted. The next element is 4. This means we are filtering by +the spotter. The third element is the letter "a" which tells the program to +expect an alphanumeric expression in the fourth element. The fourth element +is a list of letters separated by the pipe symbol. +

What this line does is tell the program to drop any spots posted by anyone in +the USA, Canada or Japan. +

The second line is the default rule for anything else. The "d" tells us this +and the line simply reads... accept anything else. +

You can add as many lines as you need to complete the filter but if there are +several lines of the same type it is neater to enclose them all as one line. +An example of this is where specific bands are set. We could write this like +this .... +


++[ 0,0,'r',[1800.0, 2000.0], 1],
+[ 0,0,'r',[10100.0, 10150.0], 1],
+[ 0,0,'r',[14000.0, 14350.0], 1],
+[ 0,0,'r',[18000.0, 18200.0], 1],
+
+

But the line below achieves the same thing and is more efficient .... +


++  [ 0, 0, 'r',
+    [  
+      1800.0, 2000.0,         # top band 
+      10100.0, 10150.0,       # WARC  
+      14000.0, 14350.0,       # 20m
+      18000.0, 18200.0,       # WARC
+    [ ,1 ],
+
+

2.2 Announcements +

+ +


++
+# This is an example announce or filter allowing only West EU announces
+# 
+# The element list is:-
+# 0 - callsign of announcer
+# 1 - destination * = all, <callsign> = routed to the node
+# 2 - text
+# 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
+# 4 - origin
+# 5 - 0 - announce, 1 - wx
+# 6 - channel callsign (the interface from which this spot came)
+
+$in = [
+        [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
+        [ 0, 0, 'd', 0 ]
+];
+
+

In this example, only the prefixes listed will be allowed. It is possible to +be quite specific. The Dutch prefix "P" is followed by several secondary +identifiers which are allowed. So, in the example, "PA" or "PE" would be ok +but not "PG". It is even possible to allow information from a single callsign. +In the example this is DK0WCY, to allow the posting of his Aurora Beacon. +

2.3 WWV +

+ +


++
+# This is an example WWV filter
+# 
+# The element list is:-
+# 0 - nominal unix date of spot (ie the day + hour:13)
+# 1 - the hour
+# 2 - SFI
+# 3 - K
+# 4 - I
+# 5 - text
+# 6 - spotter
+# 7 - origin
+# 8 - incoming interface callsign
+
+# this one doesn't filter, it just sets the hop count to 6 and is
+# used mainly just to override any isolation from WWV coming from
+# the internet.
+
+$in = [
+        [ 1, 0, 'd', 0, 6 ]
+];
+
+

It should be noted that the filter will start to be used only once a user/node +has logged out and back in again. +

I am not going to spend any more time on these filters now as they will become +more "comprehensive" in the near future. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-3.html b/html/adminmanual-3.html new file mode 100644 index 00000000..20910151 --- /dev/null +++ b/html/adminmanual-3.html @@ -0,0 +1,239 @@ + + + + + The DXSpider Administration Manual v1.47: Filtering (New Style v1.45 and later) + + + + + + +Next +Previous +Contents +

3. Filtering (New Style v1.45 and later)

+ +

3.1 General filter rules +

+ +

Upto v1.44 it was not possible for the user to set their own filters. From +v1.45 though that has all changed. It is now possible to set filters for just +about anything you wish. If you have just updated from an older version of +DXSpider you will need to update your new filters. You do not need to do +anything with your old filters, they will be renamed as you update. +

There are 3 basic commands involved in setting and manipulating filters. These +are accept, reject and clear. First we will look +generally at filtering. There are a number of things you can filter in the +DXSpider system. They all use the same general mechanism. +

In general terms you can create a 'reject' or an 'accept' filter which can have +up to 10 lines in it. You do this using, for example ... +


++ 
+accept/spots .....
+reject/spots .....
+
+

where ..... are the specific commands for that type of filter. There are filters +for spots, wwv, announce, wcy and (for sysops) connects. See each different +accept or reject command reference for more details. +

There is also a command to clear out one or more lines in a filter. They are ... +


++clear/spots 1
+clear/spots all
+
+

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

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


++  
+show/filter
+
+

For now we are going to use spots for the examples, but you can apply the same +principles to all types of filter. +

3.2 Types of filter +

+ +

There are two main types of filter, accept or reject. You +can use either to achieve the result you want dependent on your own preference +and which is more simple to do. It is pointless writing 8 lines of reject +filters when 1 accept filter would do the same thing! Each filter has 10 +lines (of any length) which are tried in order. If a line matches then the +action you have specified is taken (ie reject means ignore it and accept +means take it) +

If you specify reject filters, then any lines that arrive that match the filter +will be dumped but all else will be accepted. If you use an accept filter, +then ONLY the lines in the filter will be accepted and all else will be dumped. +For example if you have a single line accept filter ... +


++accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+

then you will ONLY get VHF spots from or to CQ zones +14, 15 and 16. +

If you set a reject filter like this ... +


++reject/spots on hf/cw
+
+

Then you will get everything EXCEPT HF CW spots. You could make this +single filter even more flexible. For example, if you are interested in IOTA +and will work it even on CW even though normally you are not interested in +CW, then you could say ... +


++reject/spots on hf/cw and not info iota
+
+

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


++accept/spots not on hf/cw or info iota
+
+

which achieves exactly the same thing. You should choose one or the other +until you are comfortable with the way it works. You can mix them if you +wish (actually you can have an accept AND a reject on the same line) but +don't attempt this until you are sure you know what you are doing! +

You can arrange your filter lines into logical units, either for your own +understanding or simply convenience. Here is an example ... +


++reject/spots 1 on hf/cw
+reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)  
+
+

What this does is to ignore all HF CW spots and also rejects any spots on VHF +which don't either originate or spot someone in Europe. +

This is an example where you would use a line number (1 and 2 in this case), if +you leave the digit out, the system assumes '1'. Digits '0'-'9' are available. +This make it easier to see just what filters you have set. It also makes it +more simple to remove individual filters, during a contest for example. +

You will notice in the above example that the second line has brackets. Look +at the line logically. You can see there are 2 separate sections to it. We +are saying reject spots that are VHF or above APART from those in +zones 14, 15 and 16 (either spotted there or originated there). If you did +not have the brackets to separate the 2 sections, then Spider would read it +logically from the front and see a different expression entirely ... +


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

The simple way to remember this is, if you use OR - use brackets. Whilst we are +here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'. +

As mentioned earlier, setting several filters can be more flexible than +simply setting one complex one. Doing it in this way means that if you want +to alter your filter you can just redefine or remove one or more lines of it or +one line. For example ... +


++reject/spots 1 on hf/ssb
+
+

would redefine our earlier example, or +


++clear/spots 1
+
+

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


++clear/spots all
+
+

3.3 Filter options +

+ +

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

3.4 Default filters +

+ +

Sometimes all that is needed is a general rule for node connects. This can +be done with a node_default filter. This rule will always be followed, even +if the link is isolated, unless another filter is set specifically. Default +rules can be set for nodes and users. They can be set for spots, announces, +WWV and WCY. They can also be used for hops. An example might look like +this ... +


++accept/spot node_default by_zone 14,15,16,20,33
+set/hops node_default spot 50
+
+

This filter is for spots only, you could set others for announce, WWV and WCY. +This filter would work for ALL nodes unless a specific filter is written to +override it for a particular node. You can also set a user_default should +you require. It is important to note that default filters should be +considered to be "connected". By this I mean that should you override the +default filter for spots, you need to add a rule for the hops for spots also. +

3.5 Advanced filtering +

+ +

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

The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, for example ... +


++rej/spot on hf/cw
+acc/spot on 0/30000
+acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
+

Note that the first filter has not been specified with a number. This will +automatically be assumed to be number 1. In this case, we have said reject all +HF spots in the CW section of the bands but accept all others at HF. Also +accept anything in VHF and above spotted in or by operators in the zones +14, 15 and 16. Each filter slot actually has a 'reject' slot and +an 'accept' slot. The reject slot is executed BEFORE the accept slot. +

It was mentioned earlier that after a reject test that doesn't match, the default +for following tests is 'accept', the reverse is true for 'accept'. In the example +what happens is that the reject is executed first, any non hf/cw spot is passed +to the accept line, which lets through everything else on HF. The next filter line +lets through just VHF/UHF spots from EU. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-4.html b/html/adminmanual-4.html new file mode 100644 index 00000000..48e5702a --- /dev/null +++ b/html/adminmanual-4.html @@ -0,0 +1,134 @@ + + + + + The DXSpider Administration Manual v1.47: Other filters + + + + + + +Next +Previous +Contents +

4. Other filters

+ +

4.1 Filtering Mail +

+ +

In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename +this to badmsg.pl and edit the file. The original looks something like this .... +


++
+# the list of regexes for messages that we won't store having
+# received them (bear in mind that we must receive them fully before
+# we can bin them)
+
+
+# The format of each line is as follows
+
+#     type      source             pattern 
+#     P/B/F     T/F/O/S            regex  
+
+# type: P - private, B - bulletin (msg), F - file (ak1a bull)
+# source: T - to field, F - from field,  O - origin, S - subject 
+# pattern: a perl regex on the field requested
+
+# Currently only type B and P msgs are affected by this code.
+# 
+# The list is read from the top down, the first pattern that matches
+# causes the action to be taken.
+
+# The pattern can be undef or 0 in which case it will always be selected
+# for the action specified
+
+
+
+package DXMsg;
+
+@badmsg = (
+'B',    'T',    'SALE', 
+'B',    'T',    'WANTED',
+'B',    'S',    'WANTED',
+'B',    'S',    'SALE', 
+'B',    'S',    'WTB',
+'B',    'S',    'WTS',
+'B',    'T',    'FS',
+);
+
+

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

4.2 Filtering DX callouts (Depricated) +

+ +

From version 1.47, this method is replaced by the command set/baddx +

In the same way as mail, there are some types of spot we do not wish to pass on +to users or linked cluster nodes. In the /spider/data directory you will find +a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The +original looks like this .... +


++
+# the list of dx spot addresses that we don't store and don't pass on
+
+
+package DXProt;
+
+@baddx = qw 
+
+ FROG 
+ SALE
+ FORSALE
+ WANTED
+ P1RATE
+ PIRATE
+ TEST
+ DXTEST
+ NIL
+ NOCALL 
+);
+
+

Again, this is simply a list of names we do not want to see in the spotted +field of a DX callout. +

4.3 Filtering words from text fields in Announce, Talk and DX spots +

+ +

Create a file in /spider/data called badwords. The format is quite +simple. Lines beginning with # are ignored so comments can be added. An +example file is below ... +


++# Below is a list of words we do not wish to see on the cluster
+grunge grunged grunging
+splodge splodger splodging
+grince
+fluffle
+
+

Multiple words can be used on the same line as shown. Obviously these +are just examples :-) +

You can reload the file from the cluster prompt as sysop with load/badwords. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-5.html b/html/adminmanual-5.html new file mode 100644 index 00000000..5fa2d87a --- /dev/null +++ b/html/adminmanual-5.html @@ -0,0 +1,214 @@ + + + + + The DXSpider Administration Manual v1.47: Mail + + + + + + +Next +Previous +Contents +

5. Mail

+ +

DXSpider deals seamlessly with standard AK1A type mail. It supports both +personal and bulletin mail and the sysop has additional commands to ensure +that mail gets to where it is meant. DXSpider will send mail almost +immediately, assuming that the target is on line. However, only one +mail message is dealt with at any one time. If a mail message is already +being sent or recieved, then the new message will be queued until it has +finished. +

The cluster mail is automatically deleted after 30 days unless the sysop +sets the "keep" flag using the msg command. +

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

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

5.3 Forward.pl +

+ +

DXSpider receives all and any mail sent to it without any alterations needed +in files. Because personal and bulletin mail are treated differently, there +is no need for a list of accepted bulletin addresses. It is necessary, however, +to tell the program which links accept which bulletins. For example, it is +pointless sending bulletins addresses to "UK" to any links other than UK +ones. The file that does this is called forward.pl and lives in /spider/msg. +At default, like other spider files it is named forward.pl.issue. Rename it +to forward.pl and edit the file to match your requirements. +The format is below ... +


++#
+# this is an example message forwarding file for the system
+#
+# The format of each line is as follows
+#
+#     type    to/from/at pattern action  destinations
+#     P/B/F     T/F/A     regex   I/F    [ call [, call ...] ]
+#
+# type: P - private, B - bulletin (msg), F - file (ak1a bull)
+# to/from/at: T - to field, F - from field, A - home bbs, O - origin 
+# pattern: a perl regex on the field requested
+# action: I - ignore, F - forward
+# destinations: a reference to an array containing node callsigns
+#
+# if it is non-private and isn't in here then it won't get forwarded 
+#
+# Currently only type B msgs are affected by this code.
+# 
+# The list is read from the top down, the first pattern that matches
+# causes the action to be taken.
+#
+# The pattern can be undef or 0 in which case it will always be selected
+# for the action specified
+#
+# If the BBS list is undef or 0 and the action is 'F' (and it matches the
+# pattern) then it will always be forwarded to every node that doesn't have 
+# it (I strongly recommend you don't use this unless you REALLY mean it, if
+# you allow a new link with this on EVERY bull will be forwarded immediately
+# on first connection)
+#
+
+package DXMsg;
+
+@forward = (
+'B',    'T',    'LOCAL',        'F',    [ qw(GB7MBC) ],
+'B',    'T',    'ALL',          'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'UK',           'F',    [ qw(GB7BAA GB7ADX) ],
+'B',    'T',    'QSL',          'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'QSLINF',       'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'DX',           'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'DXINFO',       'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'DXNEWS',       'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'DXQSL',        'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+'B',    'T',    'SYSOP',        'F',    [ qw(GB7BAA GB7ADX) ],
+'B',    'T',    '50MHZ',        'F',    [ qw(GB7BAA GB7ADX PA4AB-14) ],
+);
+
+

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 +

5.4 The msg command +

+ +

The msg command is a very powerful and flexible tool for the +sysop. It allows the sysop to alter to and from fields and make other +changes to manage the cluster mail. +

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


++  MSG TO <msgno> <call>     - change TO callsign to <call>
+  MSG FRom <msgno> <call>   - change FROM callsign to <call>
+  MSG PRrivate <msgno>      - set private flag
+  MSG NOPRrivate <msgno>    - unset private flag
+  MSG RR <msgno>            - set RR flag
+  MSG NORR <msgno>          - unset RR flag
+  MSG KEep <msgno>          - set the keep flag (message won't be deleted ever)
+  MSG NOKEep <msgno>        - unset the keep flag
+  MSG SUbject <msgno> <new> - change the subject to <new>
+  MSG WAittime <msgno>      - remove any waiting time for this message
+  MSG NOREad <msgno>        - mark message as unread
+  MSG REad <msgno>          - mark message as read
+  MSG QUeue                 - queue any outstanding bulletins
+  MSG QUeue 1               - queue any outstanding private messages
+
+

These commands are simply typed from within the cluster as the sysop user. +

5.5 Message status +

+ +

You can check on a message from within the cluster by using the command +stat/msg. This will give you additional information on the +message number including which nodes have received it, which node it +was received from and when etc. Here is an example of the output of +the command ... +


++G0VGS de GB7MBC 28-Jan-2001 1308Z >
+stat/msg 6869
+        From: GB7DJK
+    Msg Time: 26-Jan-2001 1302Z
+       Msgno: 6869
+      Origin: GB7DJK
+        Size: 8012
+     Subject: AMSAT 2line KEPS 01025.AMSAT
+          To: UK
+Got it Nodes: GB7BAA, GB7ADX
+     Private: 0
+Read Confirm: 0
+  Times read: 0
+G0VGS de GB7MBC 28-Jan-2001 1308Z >
+
+

5.6 Filtering mail +

+ +

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

5.7 Distribution lists +

+ +

Distribution lists are simply a list of users to send certain types of +mail to. An example of this is mail you only wish to send to other +sysops. In /spider/msg there is a directory called distro. You +put any distibution lists in here. For example, here is a file called +SYSOP.pl that caters for the UK sysops. +


++qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+   GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH 
+   GB7DXK GB7DXI GB7DXS)
+
+

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

5.8 BBS interface +

+ +

Spider provides a simple BBS interface. No input is required from the sysop +of the cluster at all. The BBS simply sets the cluster as a BBS and pushes +any required mail to the cluster. No mail can flow from Spider to the BBS, +the interface is one-way. +

Please be careful not to flood the cluster network with unnecessary mail. +Make sure you only send mail to the clusters that want it by using the +Forward.pl file very carefully. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-6.html b/html/adminmanual-6.html new file mode 100644 index 00000000..ee7c7bff --- /dev/null +++ b/html/adminmanual-6.html @@ -0,0 +1,145 @@ + + + + + The DXSpider Administration Manual v1.47: Databases + + + + + + +Next +Previous +Contents +

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

6.1 Creating databases +

+ +

Creating a database could not be more simple. All the commands are +sent from the cluster prompt as the sysop user. +

To create a database you use the command dbcreate. It can +be used in 3 different ways like so .. +


++dbcreate <name>
+
+

To simply create a database locally, you just tell the command the +name of the database. This does not create the actual database, it +simply defines it to say that it exists. +


++dbcreate <name> chain <name> [<name>...]
+
+

This creates a chained database entry. The first database will be +scanned, then the second, the third etc... +


++dbcreate <name> remote <name>
+
+

This creates a remote entry. the first name field is the database +name at the remote node, then the remote switch, then the actual +node_call of the remote node, for example... +


++dbcreate buckmaster remote gb7dxc
+
+

Remote databases cannot be chained, however, the last database in a +chain can be a remote database. +

6.2 Importing databases +

+ +

The only databases that Spider can currently import are the standard +AK1A databases such as OBLAST or the DB0SDX qsl and address database. +This will be added to with time. +

To import such a database, first put the file somewhere useful like /tmp +and then issue the following command ... +


++dbimport oblast /tmp/OBLAST.FUL
+
+

This will update the existing local oblast database or create it if +it does not exist. +

6.3 Checking available databases +

+ +

Once a database is created, you will want to check that it has been +added. To do this use the dbavail command. This will +output the available databases. For example ... +


++dbavail
+DB Name          Location   Chain
+qsl              Local
+buck             GB7ADX
+hftest           GB7DXM
+G0VGS de GB7MBC  3-Feb-2001 1925Z >
+
+

6.4 Looking up databases +

+ +

To look for information in a defined database, simply use the dbshow +command, for example ... +


++dbshow buckmaster G0YLM
+
+

will show the information for the callsign G0YLM from the buckmaster +database if it exists. To make things more standard for the users +you can add an entry in the Aliases file so that it looks like a standard +show command like this ... +


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

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

6.5 Removing databases +

+ +

To delete an existing database you use the dbremove command. +For example ... +


++dbremove oblast
+
+

would remove the oblast database and its associated datafile from the +system. There are no warnings or recovery possible from this command. +If you remove a database it ceases to exist and would have to be created +from scratch if you still required it. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-7.html b/html/adminmanual-7.html new file mode 100644 index 00000000..2519d041 --- /dev/null +++ b/html/adminmanual-7.html @@ -0,0 +1,349 @@ + + + + + The DXSpider Administration Manual v1.47: Information, files and useful programs + + + + + + +Next +Previous +Contents +

7. Information, files and useful programs

+ +

7.1 MOTD +

+ +

One of the more important things a cluster sysop needs to do is to get +information to his users. The simplest way to do this is to have a banner +that is sent to the user on login. This is know as a "message of the day" +or "motd". To set this up, simply create a file in /spider/data called motd +and edit it to say whatever you want. It is purely a text file and will be +sent automatically to anyone logging in to the cluster. +

7.2 Downtime message +

+ +

If for any reason the cluster is down, maybe for upgrade or maintenance but +the machine is still running, a message can be sent to the user advising them +of the fact. This message lives in the /spider/data directory and is called +"offline". Simply create the file and edit it to say whatever you wish. +This file will be sent to a user attempting to log into the cluster when +DXSpider is not actually running. +

7.3 Other text messages +

+ +

You can set other text messages to be read by the user if they input the file +name. This could be for news items or maybe information for new users. +To set this up, make a directory under /spider called packclus. +Under this directory you can create files called news or newuser +for example. In fact you can create files with any names you like. These can +be listed by the user with the command .... +


++show/files
+
+

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


++type news
+
+

If the file they want to read is called news. You could also set +an alias for this in the Alias file to allow them just to type news +

You can also store other information in this directory, either directly or +nested under directories. One use for this would be to store DX bulletins +such as the OPDX bulletins. These can be listed and read by the user. +To keep things tidy, make a directory under /spider/packclus called +bulletin. Now copy any OPDX or similar bulletins into it. These +can be listed by the user in the same way as above using the show/files +command with an extension for the bulletin directory you have just created, +like this .... +


++show/files bulletin
+
+

An example would look like this .... +


++sh/files
+bulletin      DIR 20-Dec-1999 1715Z news          1602 14-Dec-1999 1330Z
+
+

You can see that in the files area (basically the packclus directory) there is a +file called news and a directory called bulletin. You can +also see that dates they were created. In the case of the file news, +you can also see the time it was last modified, a good clue as to whether the +file has been updated since you last read it. To read the file called +news you would simply issue the command .... +


++type news
+
+

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


++show/files bulletin
+opdx390      21381 29-Nov-1999 1621Z opdx390.1     1670 29-Nov-1999 1621Z
+opdx390.2     2193 29-Nov-1999 1621Z opdx391      25045 29-Nov-1999 1621Z  
+opdx392      35969 29-Nov-1999 1621Z opdx393      15023 29-Nov-1999 1621Z  
+opdx394      33429 29-Nov-1999 1621Z opdx394.1     3116 29-Nov-1999 1621Z  
+opdx395      24319 29-Nov-1999 1621Z opdx396      32647 29-Nov-1999 1621Z
+opdx396.1     5537 29-Nov-1999 1621Z opdx396.2     6242 29-Nov-1999 1621Z
+opdx397      18433 29-Nov-1999 1621Z opdx398      19961 29-Nov-1999 1621Z  
+opdx399      17719 29-Nov-1999 1621Z opdx400      19600 29-Nov-1999 1621Z
+opdx401      27738 29-Nov-1999 1621Z opdx402      18698 29-Nov-1999 1621Z
+opdx403      24994 29-Nov-1999 1621Z opdx404      15685 29-Nov-1999 1621Z
+opdx405      13984 29-Nov-1999 1621Z opdx405.1     4166 29-Nov-1999 1621Z
+opdx406      28934 29-Nov-1999 1621Z opdx407      24153 29-Nov-1999 1621Z
+opdx408      15081 29-Nov-1999 1621Z opdx409      23234 29-Nov-1999 1621Z
+Press Enter to continue, A to abort (16 lines) >
+
+

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


++type bulletin/opdx391
+Ohio/Penn DX Bulletin No. 391
+The Ohio/Penn Dx PacketCluster
+DX Bulletin No. 391
+BID: $OPDX.391
+January 11, 1999
+Editor Tedd Mirgliotta, KB8NW
+Provided by BARF-80 BBS Cleveland, Ohio
+Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
+Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
+Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
+& The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
+Press Enter to continue, A to abort (508 lines) >
+
+

The page length will of course depend on what you have it set to! +

7.4 The Aliases file +

+ +

You will find a file in /spider/cmd/ called Aliases. First, copy this file to +/spider/local_cmd/Aliases and edit this file. You will see something like this ... +


++
+#!/usr/bin/perl
+
+# provide some standard aliases for commands for terminally
+# helpless ak1a user (helpless in the sense that they never
+# read nor understand help files)
+
+# This file is automagically reloaded if its modification time is 
+# later than the one stored in CmdAlias.pm
+
+# PLEASE make this file consistant with reality! (the patterns MUST
+# match the filenames!)
+
+# Don't alter this file, copy it into the local_cmd tree and modify it.
+# This file will be replaced everytime I issue a new release.
+
+# You only need to put aliases in here for commands that don't work as
+# you desire naturally, e.g sh/dx on its own just works as you expect
+# so you need not add it as an alias.
+
+
+
+package CmdAlias;
+
+%alias = (
+    '?' => [
+          '^\?', 'apropos', 'apropos',
+        ],
+    'a' => [
+          '^ann.*/full', 'announce full', 'announce', 
+          '^ann.*/sysop', 'announce sysop', 'announce',
+          '^ann.*/(.*)$', 'announce $1', 'announce',
+        ],
+        'b' => [
+        ],
+        'c' => [
+        ],
+        'd' => [
+          '^del', 'kill', 'kill',
+          '^del\w*/fu', 'kill full', 'kill',
+          '^di\w*/a\w*', 'directory all', 'directory',
+          '^di\w*/b\w*', 'directory bulletins', 'directory',
+          '^di\w*/n\w*', 'directory new', 'directory',
+          '^di\w*/o\w*', 'directory own', 'directory',
+          '^di\w*/s\w*', 'directory subject', 'directory',
+          '^di\w*/t\w*', 'directory to', 'directory',
+          '^di\w*/f\w*', 'directory from', 'directory',
+          '^di\w*/(\d+)', 'directory $1', 'directory',
+        ],
+        'e' => [
+        ],
+        'f' => [
+        ],
+        'g' => [
+        ],
+        'h' => [
+        ],
+        'i' => [
+        ],
+        'j' => [
+        ],
+        'k' => [
+        ],
+        'l' => [
+          '^l$', 'directory', 'directory',
+          '^ll$', 'directory', 'directory',
+          '^ll/(\d+)', 'directory $1', 'directory',
+        ],
+        'm' => [
+        ],
+        'n' => [
+          '^news', 'type news', 'type',
+        ],
+        'o' => [
+        ],
+        'p' => [
+        ],
+        'q' => [
+          '^q', 'bye', 'bye',
+        ],
+        'r' => [        
+          '^r$', 'read', 'read',
+          '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
+        ],
+        's' => [
+          '^s/p$', 'send', 'send',
+          '^sb$', 'send noprivate', 'send',
+          '^set/home$', 'set/homenode', 'set/homenode',
+          '^set/nobe', 'unset/beep', 'unset/beep',
+          '^set/nohe', 'unset/here', 'unset/here',
+          '^set/noan', 'unset/announce', 'unset/announce',
+          '^set/nodx', 'unset/dx', 'unset/dx',
+          '^set/nota', 'unset/talk', 'unset/talk',
+          '^set/noww', 'unset/wwv', 'unset/wwv',
+          '^set/nowx', 'unset/wx', 'unset/wx',
+          '^sh$', 'show', 'show',
+          '^sh\w*/buck', 'dbshow buck', 'dbshow',
+          '^sh\w*/bu', 'show/files bulletins', 'show/files',
+          '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
+          '^sh\w*/c$', 'show/configuration', 'show/configuration',
+          '^sh\w*/com', 'dbavail', 'dbavail',
+          '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
+          '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
+          '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
+          '^sh\w*/email', 'dbshow email', 'dbshow',
+          '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
+          '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
+          '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
+          '^sh\w*/tnc', 'who', 'who',
+          '^sh\w*/up', 'show/cluster', 'show/cluster',
+          '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
+          '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
+          '^sp$', 'send', 'send',
+        
+    ],
+        't' => [
+          '^ta$', 'talk', 'talk',
+          '^t$', 'talk', 'talk',
+        ],
+        'u' => [
+        ],
+        'v' => [
+        ],
+        'w' => [
+          '^wx/full', 'wx full', 'wx',
+          '^wx/sysop', 'wx sysop', 'wx',
+        ],
+        'x' => [
+        ],
+        'y' => [
+        ],
+        'z' => [
+        ],
+)
+
+

You can create aliases for commands at will. Beware though, these may not +always turn out as you think. Care is needed and you need to test the +results once you have set an alias. +

7.5 Console.pl +

+ +

In later versions of Spider a simple console program is provided for the sysop. +This has a type ahead buffer with line editing facilities and colour for spots, +announces etc. To use this program, simply use console.pl instead of client. +

To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the +file with your favourite editor. +

7.6 Updating kepler data +

+ +

Spider has a powerful and flexible show/satellite command. In order for +this to be accurate, the kepler data has to be updated regularly. In +general, this data is available as an email or via cluster mail. +Updating it is simple. First you need to export the mail message as a +file. You do this with the export command from the cluster prompt +as the sysop. For example ... +


++export 5467 /spider/perl/keps.in
+
+

would export message number 5467 as a file called keps.in in the +/spider/perl directory. +

Now login to a VT as sysop and cd /spider/perl. There is a command in +the perl directory called convkeps.pl. All we need to do now is +convert the file like so ... +


++./convkeps.pl keps.in
+
+

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


++load/keps
+
+

That is it! the kepler data has been updated. +

7.7 The QRZ callbook +

+ +

The command sh/qrz will only work once you have followed a few +simple steps. First you need to get a user ID and password from qrz.com. +Simply go to the site and create one. Secondly you need to copy the file +/spider/perl/Internet.pm to /spider/local and alter it to match your user +ID and password. You also at this point need to set $allow=1 to complete +the setup. Many thanks to Fred Lloyd, the proprieter of +qrz.com for allowing this access. +

+Next +Previous +Contents + + diff --git a/html/adminmanual-8.html b/html/adminmanual-8.html new file mode 100644 index 00000000..c90ef1fa --- /dev/null +++ b/html/adminmanual-8.html @@ -0,0 +1,114 @@ + + + + + The DXSpider Administration Manual v1.47: CVS + + + + + + +Next +Previous +Contents +

8. CVS

+ +

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

THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST +INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! +THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! +YOU HAVE BEEN WARNED!!! +

DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE +CONSEQUENCES!!! +

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

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

Assuming you are connected to the Internet, you need to login to the +CVS repository and then update your Spider source. There are several +steps which are listed below ... +

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

+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login 
+

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

What happens next depends on whether you have an existing installation that +you want to update with the latest and greatest or whether you just want +to see what is there and/or run it on a new machine for testing. +

If you are installing Spider from CVS then change directory to /home/sysop +

If you are wanting to update Spider then cd to /tmp +

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

+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+

This command is all on one line. +

Hopefully your screen should show you downloading files. The -z3 simply compresses +the download to improve speed. +When this has finished, you will have exactly the same as if you had untarred a full +tarball PLUS some extra directories and files that CVS needs to do the magic that +it does. +

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

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


++tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
+
+

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

NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions +correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU????? +

Remember to recompile the C client (cd /spider/src; make) +

At this point the files have been upgraded. You can (usually) restart the cluster +in your own time. However, if you attempt to use any new commands or features +expect it to be fatal! At least your cluster will have been restarted then so it +will be too late to worry about it! +

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


++cd /spider
+cvs -z3 update -d
+
+

and your files will be updated. As above, remember to recompile the "C" client +if it has been updated (CVS will tell you) and restart if any of the perl scripts +have been altered or added, again, CVS will tell you. +

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

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

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

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

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

9.3 accept/spots (0) +

+ +

accept/announce [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:- +


++  freq <range>           eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+  on <range>             same as 'freq'
+  call <prefixes>        eg: G,PA,HB9
+  info <string>          eg: iota or qsl
+  by <prefixes>            
+  call_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
+  call_itu <numbers>
+  call_zone <numbers>
+  by_dxcc <numbers>
+  by_itu <numbers>
+  by_zone <numbers>
+  origin <prefixes>
+  channel <prefixes>
+
+

For frequencies, you can use any of the band names defined in +SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - +thus: hf/ssb. You can also just have a simple range like: 0/30000 - +this is more efficient than saying simply: 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... +

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

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

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

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

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

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

9.10 announce full (0) +

+ +

announce full <text> Send an announcement cluster wide +

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

9.11 announce sysop (5) +

+ +

announce sysop <text> +

Send an announcement to Sysops only +

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

9.13 bye (0) +

+ +

bye Exit from the cluster +

This will disconnect you from the cluster +

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

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

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

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

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

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

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

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

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

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

9.24 directory (extended for sysops) (5) +

+ +

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

9.25 disconnect (8) +

+ +

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

Disconnect any <call> connected locally +

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

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

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

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

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

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

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

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

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

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

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

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

9.38 load/baddx (9) +

+ +

load/baddx Reload the bad DX table +

Reload the /spider/data/baddx.pl file if you have changed it manually whilst +the cluster is running. This table contains the DX Calls that, if spotted, +will not be passed on. FR0G and TEST are classic examples. +

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

9.40 load/badwords (9) +

+ +

load/badwords Reload the badwords file +

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

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

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

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

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

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

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

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

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

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

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

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

9.52 read (extended for sysops) (5) +

+ +

read <msgno> Read a message on the system +

As a sysop you may read any message on the system +

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

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

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

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

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

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

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

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

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

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

9.63 set/address (0) +

+ +

set/address <your_address> Record your postal address +

Literally, record your address details on the cluster. +

9.64 set/announce (0) +

+ +

set/announce Allow announce messages +

Allow announce messages to arrive at your terminal. +

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

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

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

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

9.69 set/beep (0) +

+ +

set/beep Add beeps to terminal messages +

Add a beep to DX and other terminal messages. +

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

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

9.72 set/dx (0) +

+ +

set/dxAllow DX messages to arrive at your terminal +

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

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

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

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

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

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

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

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

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

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

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

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

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

9.85 set/name (0) +

+ +

set/name <your_name> Set your name +

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


++  set/name Dirk
+
+

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

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

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

9.89 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 but any spaces are removed (you can type in +spaces - but they won't appear in the password). You can see the +result with STAT/USER. The password is the usual 30 character baycom +type password. +

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

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

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

9.93 set/sys_qra (9) +

+ +

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

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

9.95 set/qth (0) +

+ +

set/qth <your QTH> Set your QTH +

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


++  set/qth East Dereham, Norfolk
+
+

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

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

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

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

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

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

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

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

9.104 show/configuration/node (0) +

+ +

show/configuration/node Show all the nodes connected +

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

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

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

9.107 show/debug (9) +

+ +

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

The levels can be set with set/debug +

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

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

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

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

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

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

9.114 show/isolate (1) +

+ +

show/isolate Show a list of isolated nodes +

Show which nodes are currently set to be isolated. +

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

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

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

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

inputing:- +


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

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

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

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

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

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

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

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

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

9.127 show/time (0) +

+ +

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9.141 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.html b/html/adminmanual.html new file mode 100644 index 00000000..69eafc3d --- /dev/null +++ b/html/adminmanual.html @@ -0,0 +1,244 @@ + + + + + The DXSpider Administration Manual v1.47 + + + + + + +Next +Previous +Contents +

The DXSpider Administration Manual v1.47

+ +

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

+A reference for SysOps of the DXSpider DXCluster program. +

1. Hop control

+ +

2. Filtering (Old Style upto v1.44)

+ +

3. Filtering (New Style v1.45 and later)

+ +

4. Other filters

+ +

5. Mail

+ +

6. Databases

+ +

7. Information, files and useful programs

+ +

8. CVS

+ +

9. The DXSpider command set

+ +

+Next +Previous +Contents + + diff --git a/html/index.html b/html/index.html index 0f9e6668..ed74a968 100644 --- a/html/index.html +++ b/html/index.html @@ -63,11 +63,11 @@ Last modified: Sun Apr 1 18:21:18 BST 2001

Download the software and any patches. -
DXSpider Installation and Administration manual. +
DXSpider Installation manual. +
DXSpider Administration manual.
DXSpider User manual.
Peruse the FAQ -
Discover how to install a Windows version. -
If you are on the bleeding edge, see the CVS Erratum. +
If you are on the bleeding edge, see the CVS Addendum.
Explaining the client programs.
Periodic jobs, e.g. starting connection to other clusters.
Programming new commands or altering existing ones. diff --git a/html/installation-1.html b/html/installation-1.html new file mode 100644 index 00000000..343f1b03 --- /dev/null +++ b/html/installation-1.html @@ -0,0 +1,258 @@ + + + + + The DXSpider Installation Manual v1.47: Linux Installation (Original version by Iain Philipps, G0RDI) + + + + + + +Next +Previous +Contents +
+
1. Linux Installation (Original version by Iain Philipps, G0RDI)
+ +
1.1 Introduction +
+ +
This section describes the installation of DX Spider v1.47 on a +RedHat Linux Distribution. +Wherever possible I will try to include differences for other distributions. +I do not intend to try and cover the installation of Linux or the setup +of the AX25 utilities. If you need help on this then read Iains original +installation guide that comes with the Spider distribution. +
+
I am assuming a general knowledge of Linux and its commands. You should +know how to use tar and how to edit files using your favourite editor. +
+
The crucial ingredient for all of this is +Perl. Earlier versions of +Spider required perl 5.004, however it is now STRONGLY recommended +that you use at least version 5.005_03 as this is the version being used +in the development of Spider. +
+
In addition to the standard Red Hat distribution you will require the +following modules from +http://www.cpan.org/CPAN.html ... +
+
+
- Data-Dumper-2.101.tar.gz
- TimeDate-1.10.tar.gz
- IO-1.20.tar.gz (for perl 5.00403 and lower)
- Net-Telnet-3.02.tar.gz
- Curses-1.05.tar.gz
- Time-HiRes-01.20.tar.gz
+
+
Do get the latest versions of these packages and install them +but use the above list as the earliest versions usable. +
+
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.47 for this section but of course you would use the latest version. +
+
Login as root and create a user to run the cluster under. UNDER +NO CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use +the name sysop. You can call it anything you wish. Depending +on your security requirements you may wish to use an existing user, +however this is your own choice. +
+
+
++# adduser -m sysop + +
+
+
Now set a password for the user ... +
+
++# passwd sysop +# New UNIX password: +# Retype new UNIX password: +passwd: all authentication tokens updated successfully + +
+
+
1.3 Installing the software +
+ +
Now to unpack the DX Spider distribution, set symbolic links and group +permissions. Copy the tarball to /home/sysop and do the following. +
+
++# cd ~sysop +# tar xvfz spider-1.47.tar.gz +# ln -s ~sysop/spider /spider +# groupadd -g 251 spider (or another number) + +
+
If you do not have the command groupadd available to you simply +add a line in /etc/group by hand. +
+
++# vi /etc/group (or your favorite editor) + +
+
You also need to add some others to the group, including your own callsign +(this will be used as an alias) and root. The finished line in /etc/group +should look something like this +
spider:x:251:sysop,g0vgs,root +
+
The next step is to set the permissions on the Spider directory tree and files .... +
+
++# chown -R sysop.spider spider +# find . -type d -exec chmod 2775 {} \; +# find . -type f -exec chmod 775 {} \; + +
+
+
This last step allows various users of the group spider to have +write access to all the directories. This is not really needed just yet +but will be useful when web interfaces start to appear. +
+
Finally, you need to fix the permissions on the ax25_call and netrom_call +programs. Check where they are with the locate command and alter +the permissions with the chmod command like this .. +
+
++# chown root ax25_call netrom_call +# chmod 4775 ax25_call netrom_call + +
+
+
1.4 Setting callsigns etc +
+ +
Now login to your machine as the user you created earlier. In my case that +user is called sysop. Once logged in, issue the following commands .... +
+
++$ cd /spider +$ mkdir local +$ mkdir local_cmd +$ cp perl/DXVars.pm.issue local/DXVars.pm +$ cd local +$ vi DXVars.pm (or your favourite editor) + +
+
+
Using the distributed DXVars.pm as a a template, set your cluster callsign, +sysop callsign and other user info to suit your own environment. Note that +this a perl file which will be parsed and executed as part of the cluster. If +you get it wrong then perl will complain when you start the cluster process. +It is important only to alter the text of any section. Some of the lines look +a little odd. Take this line for example .... +
$myemail = "ianmaude\@btinternet.com"; +
+
There appears to be an extra slash in there. However this has to be there +for the file to work so leave it in. +
+
PLEASE USE CAPITAL LETTERS FOR CALLSIGNS +
+
DON'T alter any file in /spider/perl, they are overwritten with every +release. Any files or commands you place in /spider/local or /spider/local_cmd +will automagically be used in preference to the ones in /spider/perl EVEN +while the cluster is running! +
+
Save the new file and change directory to ../perl .... +
+
++$ cd ../perl + +
+
+
Now type the following command which creates the basic user file with you as +the sysop. +
+
++$ ./create_sysop.pl + +
+
+
1.5 Starting up for the first time +
+ +
We can now bring spider up for the first time and see if all is well or not! +It should look something like this ... +
+
++$ ./cluster.pl +DXSpider DX Cluster Version 1.47 +Copyright (c) 1998 Dirk Koopman G1TLH +loading prefixes ... +loading band data ... +loading user file system ... +starting listener ... +reading existing message headers +reading cron jobs +orft we jolly well go ... + +
+
+
If all is well then login on another term or console as sysop and +cd to /spider/src. Now issue the following command ... +
+
++$ ./client + +
+
+
This should log you into the cluster as the sysop under the alias callsign we +set earlier. In this case the callsign is G0VGS. The cluster callsign is set +in the DXVars.pm file in /spider/local. In this case we will assume that this +was set as GB7MBC. You should therefore see this when you login .... +
+
++G0VGS de GB7MBC 19-Nov-1999 2150Z > + +
+
If you do, congratulations! If not, look over the instructions again, you +have probably missed something out. You can shut spider down again with the +command .... +
+
++shutdown + +
+
+
and both the cluster and the client should return to Linux prompts. +
+
1.6 The Client program +
+ +
In earlier versions of Spider, all the processes were Perl scripts. This +was fine but with a lot of users your computer memory would soon be used up. +To combat this a new client was written in "C". This client only works for +incoming connects at the moment. Before you can use it though it +has to be "made". CD to /spider/src and type make. You +should see the output on your screen and hopefully now have a small C program +called client. Leave it in this directory. +
+
+
+Next +Previous +Contents + + diff --git a/html/installation-2.html b/html/installation-2.html new file mode 100644 index 00000000..64446bd2 --- /dev/null +++ b/html/installation-2.html @@ -0,0 +1,72 @@ + + + + + The DXSpider Installation Manual v1.47: Linux quick installation guide + + + + + + +Next +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. +
+
- Login as root
- Get the additional CPAN modules and install them (root)
- Create the "sysop" user and set a password (root)
- Put the Spider tarball in sysop and untar it (root)
- ln -s sysop/spider /spider (root)
- groupadd -g 251 spider (root)
- Add any more users you need to the group entry in /etc/group (root)
- Set the permissions on the spider tree (root)
- Fix permissions on ax25_call and netrom_call (root)
- Login as the sysop user
- cd to /spider (sysop)
- mkdir local (sysop)
- mkdir local_cmd (sysop)
- cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
- cd to /spider/local and edit DXVars to set your details (sysop)
- cd ../perl (sysop)
- ./create_sysop.pl (sysop)
- ./cluster.pl (sysop)
+
Spider should now be running and you should be able to login using the +client program. +
+
- Login as root
- Enter the correct line in ax25d.conf (root)
- Enter the correct line in /etc/services (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. +
+
- Login as sysop
- Start the cluster (sysop)
- set/node and type for links (sysop)
- Write any connect scripts (sysop)
- Edit /spider/crontab as required (sysop)
- Edit any other files as necessary (sysop)
- Set filters, hops and forwarding files (sysop)
- Login as root
- Enter the correct line in /etc/inittab (root)
+
+
+Next +Previous +Contents + + diff --git a/html/installation-3.html b/html/installation-3.html new file mode 100644 index 00000000..7e426123 --- /dev/null +++ b/html/installation-3.html @@ -0,0 +1,523 @@ + + + + + The DXSpider Installation Manual v1.47: Configuration + + + + + + +Next +Previous +Contents +
+
3. Configuration
+ +
3.1 Allowing ax25 connects from users +
+ +
As stated previously, the aim of this document is not to tell you how to +configure Linux or the ax25 utilities. However, you do need to add a line +in your ax25d.conf to allow connections to DXSpider for your users. For +each interface that you wish to allow connections on, use the following format ... +
+
++default * * * * * * - sysop /spider/src/client client %u ax25 + +
+
or, if you wish your users to be able to use SSID's on their callsigns .. +
+
++default * * * * * * - sysop /spider/src/client client %s ax25 + +
+
For most purposes this is not desirable. The only time you probably will +need this is when you need to allow other cluster nodes that are using SSID's +in. In this case it would probably be better to use the first example and +then add a specific line for that node like this: +
+
++GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 +default * * * * * * - sysop /spider/src/client client %u ax25 + +
+
+
3.2 Allowing telnet connects from users +
+ +
+From version 1.47 there is a new (more efficient) way of doing this +(see next section) but, if you prefer, the method of doing it described +here will continue to work just fine. +
+
Allowing telnet connections is quite simple. Firstly you need to add a line +in /etc/services to allow connections to a port number, like this .... +
+
++spdlogin 8000/tcp # spider anonymous login port + +
+
Then add a line in /etc/inetd.conf like this .... +
+
++spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet + +
+
+
Once this is done, you need to restart inetd like this .... +
+
++killall -HUP inetd + +
+
+
+
Now login as sysop and cd spider/src. You can test that spider +is accepting telnet logins by issuing the following command .... +
+
++./client login telnet + +
+
You should get a login prompt and on issuing a callsign, you will be given +access to the cluster. Note, you will not get a password login. There seems +no good reason for a password prompt to be given so it is not asked for. +
+
Assuming all is well, then try a telnet from your linux console .... +
+
++telnet localhost 8000 + +
+
+
You should now get the login prompt and be able to login as before. +
+
3.3 Setting up telnet connects (from 1.47 onwards) +
+ +
From version 1.47 you can choose to allow the perl cluster.pl program to +allow connections directly (i.e. not via the /spider/src/client +interface program). If you are using Windows then this is the only method +available of allowing incoming telnet connections. +
+
To do this you need first to remove any line that you may previously have set +up in /etc/inetd.conf. Remember to:- +
+
++killall -HUP inetd + +
+
+
to make the change happen... +
+
Having done that, you need to copy the file +/spider/perl/Listeners.pm to /spider/local and +then edit it. You will need to uncomment the line containing "0.0.0.0" +and select the correct port to listen on. So that it looks like this:- +
+
++@listen = ( + ["0.0.0.0", 8000], +); + +
+
+
As standard, the listener will listen on all interfaces simultaneously. +If you require more control than this, you can specify each interface +individually:- +
+
++@listen = ( + ["gb7baa.dxcluster.net", 8000], + ["44.131.16.2", 6300], +); + +
+
+
This will only be successful if the IP addresses on each interface are static. +If you are using some kind of dynamic IP addressing then the 'default' method +is the only one that will work. +
+
Restart the cluster.pl program to enable the listener. +
+
One important difference with the internal listener is that no echoing +is done by the cluster program. Users will need to set 'local-echo' on in +their telnet clients if it isn't set automatically (as per the standards). +Needless to say this will probably only apply to Windows users. +
+
3.4 Setting up for AGW Engine (1.47 onwards) +
+ +
AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine +from Linux as well as Windows based machines. +
+
In order to enable access to an AGW Engine you need to copy +/spider/perl/AGWConnect.pm to /spider/local and edit it. +Specifically you must:- +
+
- set $enable to 1.
- set $login and $passwd to the values set up in your AGW installation. +If you haven't set any there, then you should not touch these values.
- You can connect to a remote AGW engine (ie on some other machine) by changing $addr +and $port appropriately.
- Restart the cluster.pl program
+ +
+
+
3.5 Setting up node connects +
+ +
In order to allow cluster node connections, spider needs to know that the +connecting callsign is a cluster node. This is the case whether the connect +is incoming or outgoing. In spider this is a simple task and can be done in +runtime. +
+
Later versions of Spider can distinguish different software and treat them +differently. For example, the WCY beacon cannot be handles by AK1A type +nodes as AK1A does not know what to do with PC73. There are 4 different +types of node at present and although they may not have any major +differences at the moment, it allows for compatibility. The 4 types are ... +
+
++set/node (AK1A type) +set/spider +set/dxnet +set/clx + +
+
+
For now, we will assume that the cluster we are going to connect to is an +AK1A type node. +
+
Start up the cluster as you did before and login as the sysop with client. +The cluster node I am wanting to make a connection to is GB7BAA but you would +obviously use whatever callsign you required. At the prompt type ... +
+
++set/node gb7baa + +
+
+
The case does not matter as long as you have a version of DXSpider later than +1.33. Earlier versions required the callsign to be in upper case. +
+
That is now set, it is as simple as that. To prove it, login on yet another +console as sysop, cd to spider/src and issue the command ... +
+
++./client gb7baa (using the callsign you set as a node) + +
+
+
You should get an initialisation string from DXSpider like this ... +
+
++./client gb7baa +PC38^GB7MBC^~ + +
+
If the callsign you just set up as a cluster node is for an incoming connect, +this is all that needs to be done. If the connection is to be outgoing then +a connection script needs to be written. +
+
Sometimes you make a mistake... Honest, it does happen. If you want to make a node +back to being a normal user, regardless +of what type it is, do: +
+
++unset/node gb7baa + +
+
+
3.6 Connection scripts +
+ +
Because DXSpider operates under Linux, connections can be made using just about +any protocol; AX25, NETRom, tcp/ip, ROSE etc are all possible examples. +Connect scripts live in the /spider/connect directory and are simple ascii files. +Writing a script for connections is therefore relatively simple. +
+
The connect scripts consist of lines which start with the following keywords +or symbols:- +
+
+
+
#
All lines starting with a # are ignored, as are completely +blank lines. +
+
timeout
timeout followed by a number is the number of seconds to wait for a +command to complete. If there is no timeout specified in the script +then the default is 60 seconds. +
+
abort
abort is a regular expression containing one or more strings to look +for to abort a connection. This is a perl regular expression and is +executed ignoring case. +
+
connect
connect followed by ax25, agw (for Windows users) or telnet and some type dependent +information. In the case of a telnet connection, there can be up to +two parameters. +The first is the ip address or hostname of the computer you wish to +connect to and the second is the port number you want to use (this +can be left out if it is a normal telnet session). +In the case of an ax25 session then this would normally be a call to +ax25_call or netrom_call as in the example above. It is your +responsibility to get your node and other ax25 parameters to work +before going down this route! +
+
'
' is the delimiting character for a word or phrase of an expect/send +line in a chat type script. The words/phrases normally come in pairs, +either can be empty. Each line reads input from the connection until +it sees the string (or perl regular expression) contained in the +left hand string. If the left hand string is empty then it doesn't +read or wait for anything. The comparison is done ignoring case. +When the left hand string has found what it is looking for (if it is) +then the right hand string is sent to the connection. +This process is repeated for every line of chat script. +
+
client
client starts the connection, put the arguments you would want here +if you were starting the client program manually. You only need this +if the script has a different name to the callsign you are trying to +connect to (i.e. you have a script called other which actually +connects to GB7DJK-1 [instead of a script called gb7djk-1]). +
+
+
There are many possible ways to configure the script but here are three examples, +one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip. +
+
++timeout 60 +abort (Busy|Sorry|Fail) +# don't forget to chmod 4775 netrom_call! +connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh +'Connect' '' +'Connect' 'c np7' +'Connect' 'c gb7dxm' +# you can leave this out if you call the script 'gb7dxm' +client gb7dxm ax25 + +
+
+
+
+
++timeout 60 +abort (Busy|Sorry|Fail) +# this does exactly the same as the previous example +# the '1' is the AGW port number to connect thru for g1tlh +connect agw 1 g1tlh +'Connect' '' +'Connect' 'c np7' +'Connect' 'c gb7dxm' +# you can leave this out if you call the script 'gb7dxm' +client gb7dxm ax25 + +
+
+
+
+
++timeout 15 +connect telnet dirkl.tobit.co.uk +'login' 'gb7djk' +'word' 'gb7djk' +# tell GB7DJK-1 that it is connected to GB7DJK +# you can leave this out if you call this script 'gb7djk' +client gb7djk telnet + +
+
+
Both these examples assume that everything is set up properly at the other end. +You will find other examples in the /spider/examples directory. +
+
3.7 Starting the connection +
+ +
You start the connection, from within a sysop enabled cluster login, by typing +in the word connect followed by a script name like this .... +
+
++G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1 +connection to GB7DJK-1 started +G0VGS de GB7MBC 13-Dec-1998 2043Z > + +
+
This will start a connection using the script called gb7djk-1. You can +follow the connection by watching the term or console from where you started +cluster.pl. From version 1.47 onwards, you will need to set/debug connect first. +You should see something like this ... +
+
++<- D G1TLH connect gb7djk-1 +-> D G1TLH connection to GB7DJK-1 started +-> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > +timeout set to 15 +CONNECT sort: telnet command: dirkl.tobit.co.uk +CHAT "login" -> "gb7djk" +received " +Red Hat Linux release 5.1 (Manhattan) +Kernel 2.0.35 on an i586 +" +received "login: " +sent "gb7djk" +CHAT "word" -> "gb7djk" +received "gb7djk" +received "Password: " +sent "gb7djk" +Connected to GB7DJK-1, starting normal protocol +<- O GB7DJK-1 telnet +-> B GB7DJK-1 0 +GB7DJK-1 channel func state 0 -> init +<- D GB7DJK-1 +<- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 +<- D GB7DJK-1 PC38^GB7DJK-1^~ +<- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime +0 00:00^5447^~ + etc + +
+
+
With later versions of Spider there is a set/login command for users. This +tells them when a user or node logs in or out. If you do not add a line to +your scripts after the final line (or before the client line which should always +be last if needed) then the login/logout information will be sent to users +before the login actually completes. This means if a node is +unreachable, it will continue sending logins and logouts to users even though it +is not actually connecting. To avoid this use the following line ... +
+
++'connect' '' + +
+
+
In a script, this might look like ... +
+
++timeout 35 +abort (Busy|Sorry|Fail) +connect telnet mary 3000 +'ogin:' 'gb7mbc' +'>' 'telnet 44.131.93.96 7305' +'connect' '' + +
+
+
3.8 Telnet echo +
+ +
Cluster links in particular suffer greatly from the presence of telnet echo. +This is caused by the telnet negotiation itself and can create at worst severe +loops. At best it creates unnecessary bandwidth and large logfiles! There are +things that can be done to limit this problem but will not always work dependent +on the route taken to connect. +
+
Telnet echo itself should only be a problem if the connection is being made to +the telnet port (23). This port uses special rules that include echo negotiation. +If the connection is to a different port, such as 7300, this negotiation does +not happen and therefore no echo should be present. +
+
Sometimes it is not possible to make a direct connection to another node and this +can cause problems. There is a way of trying to suppress the telnet echo but +this will not always work, unfortunately it is difficult to be more specific. +Here is an example of what I mean ... +
+
++timeout 35 +abort (Busy|Sorry|Fail) +connect telnet mary.lancs.ac.uk +'ogin:' 'gb7mbc' +'word:' 'mypasswd' +'\$' 'stty -echo raw' +'\$' 'telnet 44.131.93.96' +'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 +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. +
+
+
3.9 Autostarting the cluster +
+ +
Ok, you should now have DXSpider running nicely and allowing connects by cluster +nodes or users. However, it has to be shutdown and restarted manually. It +would be much easier to have it start automatically. +
+
This is not only a way to start the cluster automatically, it also works as a +watchdog, checking the sanity of DXSpider and respawning it should it crash for +any reason. Before doing the following, shutdown the cluster as you did earlier. +
+
Login as root and bring up the /etc/inittab file in your favourite editor. Add +the following lines to the file near the end ... +
+
++##Start DXSpider on bootup and respawn it should it crash +DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + +
+
+
This line works fine for RedHat distributions. It is also fine for SuSE up to +7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ... +
+
++DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + +
+
+
The line required for Slackware distributions is slightly different. My thanks to +Aurelio, PA3EZL for this information. +
+
++DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7 + +
+
+
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart +it should it crash for any reason. +
+
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. +
+
+Next +Previous +Contents + + diff --git a/html/installation-4.html b/html/installation-4.html new file mode 100644 index 00000000..875c5056 --- /dev/null +++ b/html/installation-4.html @@ -0,0 +1,192 @@ + + + + + The DXSpider Installation Manual v1.47: Microsoft Windows Installation + + + + + + +Next +Previous +Contents +
+
4. Microsoft Windows Installation
+ +
4.1 Introduction +
+ +
IMPORTANT: +
What you'll be left with once you've followed these instructions +is (hopefully) a working DX Spider v1.47 system that is capable +of accepting or originating "internet" connections, plus inbound +AX.25 and TCP/IP radio connections. If the absence of outbound +radio connections is a serious limitation for you, it would be +better for you to wait a couple more weeks until this support has +been added. +
On the other hand, you may have an enquiring mind, or better yet, +may be looking for a useful way of connecting your current +(perhaps) AK1A cluster "to the internet" via some networking +mechanism (BPQEther, etc) or other. I won't be producing +instructions for the latter case, because I don't have an AK1A to +play with. But someone might ... +
Whatever, this document is intended to get you started with DX +Spider in a Microsoft Windows ™ 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. +
+
4.2 The requirements +
+ +
The very first things you're going to need are (in order of +importance):- +
+
- A cup of good, strong tea
- A supported Windows platform with an internet connection so you can +download the necessary software bits and bobs directly to it. There are other ways, but this is preferable.
- Another cup of good, strong tea
- If all goes according to plan, about an hour to spare
- Plenty of good, strong tea
+
+
4.3 The system +
+ +
The platform I used to generate these instructions was a +"vanilla" Microsoft Windows Me 4.90.3000 system, with a 700MHz +AMD Athlon processor and 96 Mb memory. I've also personally +verified that it runs on my laptop (Pentium 266MHz, 32 Mb memory, +Windows 98 SE v4.10.2222 A) and a computer that I assembled from +a random pile of junk (AMD K6-2 333MHz, 64 Mb memory, Windows 98 +v4.10.1998). As a result, I have reason to believe that what I'm +about to describe will perform equally on any 32-bit MS Windows +environment with 32 Mb of memory. +
Because of the changes that have recently been made to the core +"cluster.pl" module and the introduction of a very lightweight +"winclient.pl", I have a sneaking suspicion that this will now +run on any platform that has reasonably complete support for +Perl. Is there someone out there with both an enquiring mind and +(say) a Macintosh, for instance? +
Please bear in mind, though, that my instructions relate solely +to how to get this going under a Microsoft Windows environment, +and I have zero intention of trying to make them say otherwise. +
+
4.4 Perl +
+ +
Install your chosen Perl environment. Unless you have a very good +reason for not doing so, I strongly suggest that you use +ActivePerl v5.6. For my testing & development, I used build 623. +You can get this from:- +http://www.activestate.com/Products/ActivePerl/Download.html
You will need to choose either the MSI or the AS package. My +recommendation is that you choose the MSI package and deal with +the consequences if your system isn't equipped with support for +the latest MS Installer; you'll be better off in the long run. +The build 623 download is 7,460 KB, so now is a really good time +to have some tea if you're on a slow dial-up connection. +
During installation, please ensure that you do choose the options +to "Add Perl to the PATH environment variable" and "Create Perl +file extension association"; it will make your life so much +easier. Once the installation is finished, be sure to reboot your +PC. You probably won't be told anywhere else that this needs to +be done now, but it does. Really. +
Once you've rebooted, open a "DOS box" (Start > Run > command +might do it, if you can't find it elsewhere) and from wherever it +lands, type PERL -v <ENTER> (it's better if that's a lower-case +'v', because an upper-case 'V' means something else. You should +be rewarded with some interesting information about your Perl +installation. If you're not, you must go back to the beginning +and discover what went wrong and fix it. It's pointless to +proceed unless this simple check is passed. Assuming it did work, +you may now move on. +
+
4.5 Additional packages +
+ +
Some extensions ("packages") need to be added to the base Perl +distribution, and we'll do this next. If you're using the Perl I +recommended, and don't know any better for yourself, then just +blindly following these instructions will work just fine. If that +didn't describe you, then you're on your own. +
Visit the following URL: +
+http://www.activestate.com/PPMPackages/zips/6xx-builds-only/
and download the following files:- +
+
++Data-Dumper.zip +Net-Telnet.zip +TimeDate.zip +Time-HiRes.zip +DB_File.zip + +
+
Make yourself a convenient directory to unpack all of these zip +files into (I put mine in "D:\ppm>") and do the following (the +bits you type in are blue ). Note that where these files land +will be directly related to where you chose to install your +ActivePerl (mine, as you can probably guess from what follows, +went into "D:\Perl"):- +
+
++D:\ppm>ppm install Data-Dumper.ppd +Installing package 'Data-Dumper.ppd' +Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs +Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll +Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp +Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib +Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html +Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm +Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist +D:\ppm> + +
+
I'm not going to bother you with exhaustive details of the rest +of them, but suffice it to say you need to: +
+
++ppm install DB_File.ppd +ppm install Net-Telnet.ppd +ppm install TimeDate.ppd +ppm install Time-HiRes.ppd + +
+
If all that seemed to work OK, time to move along. Before anyone +who is familiar with PPM tells me that we didn't need to download +and keep those files locally, I knew that. I also knew that PPM +is sometimes awkward to configure via firewalls, and that +sometimes the repositories don't always work the way we'd hope. I +do it that way because it suits me. +
+
4.6 Getting Spider +
+ +
Get the current version of the DX Spider distribution. This needs +to be v1.47 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 my package from:- +
+http://www.dcc.rsgb.org/WinSpider.zip
or if you want the lastest CVS version (which is produced every night) +
+http://www.dxcluster.org/download/CVSlatest.tgz
If you went down the CVS route, then everything will be nicely +set out on your local disk. If you got the ZIP file, unpack it to +somewhere convenient. The following examples assume that you put +it on drive "C:\", for convenience. +
NOTE: This distribution method will go away as soon as the first +v1.47 tarball is released. You can use WinZip to unpack that, and +my life will be made easier by not needing to keep this .ZIP file +updated. +
+
+Next +Previous +Contents + + diff --git a/html/installation-5.html b/html/installation-5.html new file mode 100644 index 00000000..fde7e8fb --- /dev/null +++ b/html/installation-5.html @@ -0,0 +1,210 @@ + + + + + The DXSpider Installation Manual v1.47: Installing the software + + + + + + +Next +Previous +Contents +
+
5. Installing the software
+ +
Ensure that your CVS session or your unZIPped file have left you +with a directory "C:\spider\local"; if not, go to "C:\spider\" +and create one. If "C:\spider" is missing, go back and figure out +why, because it shouldn't be. +
Now create your own local copy of the DXVars.pm file by:- +
+
++copy c:\spider\perl\DXVars.pm.issue +c:\spider\local\DXVars.pm + +
+
Now you'll need to edit this file using a text editor. If nothing +else, you can simply +
+
++cd \spider\local + +
+
and then +
+
++notepad DXVars.pm + +
+
to bring up an editor window containing the file. As an absolute +minimum you must adjust the following items in DXVars.pm:- +
+
- $mycall - Should hold the callsign of your DX Cluster
- $myname - The SysOp's first name
- $myalias - the SysOp's callsign. Cannot be the same as $mycall!
+
You really also ought to update the $mylatitude, $mylongitude, +$myqth and $myemail variables. And unless you are absolutely +certain you know what you're doing, you should change nothing +else in this file. +
+
5.1 The AGW packet engine +
+ +
On the assumption that you'll be using the SV2AGW Packet Engine +to interface your radios to the cluster, you should now create +your own local copy of AGWConnect.pm by:- +
+
++copy c:\spider\perl\AGWConnect.pm +c:\spider\local\AGWConnect.pm + +
+
and then +
+
++notepad AGWConnect.pm + +
+
to bring up an editor window containing the file. You must +consider adjusting the following items in AGWConnect.pm:- +
+
- $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
+
+
5.2 Setting up the initial user files +
+ +
Next you need to create the initial user files, etc. A tool is +supplied which will do this for you. To run the tool:- +
+
++cd \spider\perl +perl create_sysop.pl + +
+
If all goes according to plan, you will see no output from this +program, and after a brief wait, your DOS prompt will be +returned. +
Depending on how brave you are, you might now care to try the +following:- +
+
++perl cluster.pl + +
+
If you did everything you were told, your DOS window will now +hold a display which looks something like:- +
+
++DXSpider DX Cluster Version 1.47 +Copyright (c) 1998-2001 Dirk Koopman G1TLH +loading prefixes ... +loading band data ... +loading user file system ... +starting listeners ... +Internal port: localhost 27754 +load badwords: Ok +reading in duplicate spot and WWV info ... +reading existing message headers ... +load badmsg: Ok +load forward: Ok +load swop: Ok +@msg = 0 before delete +@msg = 0 after delete +reading cron jobs ...v cron: reading /spider/cmd/crontab +cron: adding 1 0 * * 0 +DXUser::export("$main::data/user_asc") +reading database descriptors ... +doing local initialisation ... +orft we jolly well go ... +queue msg (0) + +
+
Now, if that's what you've got, you are very nearly home and dry +(in as far as these particular experiments are concerned, anyhow) +
To access your new cluster (from the local machine) find yourself another +"DOS box" and do the following:- +
+
++cd \spider\perl +perl winclient.pl + +
+
If you are rewarded with a display which looks something like:- +
+
++Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47 +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) +
+
5.3 Incoming telnets +
+ +
If you want to enable inbound "TELNET" connections, you've got a +little more work to do. From a handy "DOS box" that's not doing +anything else, do the following:- +
+
++copy \spider\perl\listeners.pm \spider\local +cd \spider\local +notepad listeners.pm + +
+
The following lines 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. +
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 +an amount of effort on your part to read, understand and +implement what needs to be done to set this up. +
+
5.4 Connecting to other clusters +
+ +
If you want to connect this to another cluster, then you'll want +to negotiate a link with someone. For experimental purposes, I'm +happy to allow folk to connect to GB7DXA (spud.ath.cx), on the +understanding that the system may or may not be there and may or +may not be connected to anything particularly useful at any given +moment. Contact me by Email if you want me to set up a connection +for you. +
+
+Next +Previous +Contents + + diff --git a/html/installation-6.html b/html/installation-6.html new file mode 100644 index 00000000..d1378c81 --- /dev/null +++ b/html/installation-6.html @@ -0,0 +1,50 @@ + + + + + The DXSpider Installation Manual v1.47: General Information + + + + + +Next +Previous +Contents +
+
6. General Information
+ +
The following relates to all versions of DXSpider and is not platform related. +
+
6.1 The crontab file +
+ +
Login as sysop and create a file in /spider/local_cmd called crontab. +Edit it with your favourite editor and add a line like this (I have included +a comment) +
+
++# check every 10 minutes to see if gb7xxx is connected and if not +# start a connect job going + +0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') + +
+
+
The callsign involved will be the callsign of the cluster node you are +going to connect to. This will now check every 10 minutes to see if +gb7xxx is connected, if it is then nothing will be done. If it is not, +then a connect attempt will be started. +
+
There are probably lots of other things you could use this crontab file for. +If you want to know more about it, look at the +DXSpider website +at the cron page where it is explained more fully. +
+
+Next +Previous +Contents + + diff --git a/html/installation.html b/html/installation.html new file mode 100644 index 00000000..2cb62dff --- /dev/null +++ b/html/installation.html @@ -0,0 +1,82 @@ + + + + + The DXSpider Installation Manual v1.47 + + + + + + +Next +Previous +Contents +
+
The DXSpider Installation Manual v1.47
+ +
Iain Philipps, G0RDI (g0rdi@77hz.com) and +Ian Maude, G0VGS, (ianmaude@btinternet.com)
+
+A reference for SysOps of the DXSpider DXCluster program. +
+
+
1. Linux Installation (Original version by Iain Philipps, G0RDI)
+ +
+
+
2. Linux quick installation guide
+ +
+
3. Configuration
+ +
+
+
4. Microsoft Windows Installation
+ +
- 4.1 Introduction +
- 4.2 The requirements +
- 4.3 The system +
- 4.4 Perl +
- 4.5 Additional packages +
- 4.6 Getting Spider +
+
+
5. Installing the software
+ +
+
+
6. General Information
+ +
- 6.1 The crontab file +
+
+Next +Previous +Contents + + diff --git a/sgml/Makefile b/sgml/Makefile index 0bc764bf..7bb8a2f4 100644 --- a/sgml/Makefile +++ b/sgml/Makefile @@ -2,14 +2,20 @@ # Makefile for Ian, 2.1.2001 # -all: ../html/adminmanual.html ../txt/adminmanual.txt ../html/spiderFAQ.html ../txt/spiderFAQ.txt ../html/usermanual.html ../txt/usermanual.txt ../html/wininstallation.html ../txt/wininstallation.txt ../html/spiderCVS.html ../txt/spiderCVS.txt +all: ../html/adminmanual.html ../txt/adminmanual.txt ../html/installation.html ../txt/installation.txt ../html/spiderFAQ.html ../txt/spiderFAQ.txt ../html/usermanual.html ../txt/usermanual.txt ../html/spiderCVS.html ../txt/spiderCVS.txt # ../txt/adminmanual.txt: adminmanual.sgml - sgml2txt adminmanual.sgml + sgml2txt -f adminmanual.sgml # ../html/adminmanual.html: adminmanual.sgml sgml2html adminmanual.sgml +# ../txt/installation.txt: installation.sgml + sgml2txt -f installation.sgml + +# ../html/installation.html: installation.html + sgml2html installation.sgml + # ../html/spiderFAQ.html: spiderFAQ.sgml sgml2txt spiderFAQ.sgml @@ -22,12 +28,6 @@ all: ../html/adminmanual.html ../txt/adminmanual.txt ../html/spiderFAQ.html ../t # ../txt/usermanual.txt: usermanual.sgml sgml2txt usermanual.sgml -# ../html/wininstallation.html: wininstallation.sgml - sgml2html wininstallation.sgml - -# ../txt/winistallation.txt: wininstallation.sgml - sgml2txt -f wininstallation.sgml - # ../html/spiderCVS.html: spiderCVS.sgml sgml2html spiderCVS.sgml diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 39ec6431..2f04bf2b 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -4,9 +4,9 @@ -The DXSpider Installation and Administration Manual +The DXSpider Administration Manual v1.47 Ian Maude, G0VGS, (ianmaude@btinternet.com) -Version 1.47 (Revision 1.30), April 2001 + A reference for SysOps of the DXSpider DXCluster program. @@ -17,817 +17,6 @@ A reference for SysOps of the DXSpider DXCluster program. -Installation (Original version by Iain Philipps, G0RDI) - -Introduction - -
-This section describes the installation of DX Spider v1.46 on a - Linux Distribution. -Wherever possible I will try to include differences for other distributions. -I do not intend to try and cover the installation of Linux or the setup -of the AX25 utilities. If you need help on this then read Iains original -installation guide that comes with the Spider distribution. - -
-I am assuming a general knowledge of Linux and its commands. You should -know how to use tar and how to edit files using your favourite editor. - -
-The crucial ingredient for all of this is -. Earlier versions of -Spider required perl 5.004, however it is now STRONGLY recommended -that you use at least version 5.005_03 as this is the version being used -in the development of Spider. - -
In addition to the standard Red Hat distribution you will require the -following modules from ... - -
- - - Data-Dumper-2.101.tar.gz - TimeDate-1.10.tar.gz - IO-1.20.tar.gz (for perl 5.00403 and lower) - Net-Telnet-3.02.tar.gz - Curses-1.05.tar.gz - Time-HiRes-01.20.tar.gz - - - -
- -Do get the latest versions of these packages and install them -but use the above list as the earliest versions usable. - -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.46 for this section but of course you would use the latest version. - -
-Login as root and create a user to run the cluster under. UNDER -NO CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use -the name sysop. You can call it anything you wish. Depending -on your security requirements you may wish to use an existing user, -however this is your own choice. - -
- -# adduser -m sysop - - -
-Now set a password for the user ... - - -# passwd sysop -# New UNIX password: -# Retype new UNIX password: -passwd: all authentication tokens updated successfully - - -Installing the software - -
-Now to unpack the DX Spider distribution, set symbolic links and group -permissions. Copy the tarball to /home/sysop and do the following. - - -# cd ~sysop -# tar xvfz spider-1.46.tar.gz -# ln -s ~sysop/spider /spider -# groupadd -g 251 spider (or another number) - - -If you do not have the command groupadd available to you simply -add a line in /etc/group by hand. - - -# vi /etc/group (or your favorite editor) - - -You also need to add some others to the group, including your own callsign -(this will be used as an alias) and root. The finished line in /etc/group -should look something like this - --spider:x:251:sysop,g0vgs,root - - -
-The next step is to set the permissions on the Spider directory tree and files .... - - -# chown -R sysop.spider spider -# find . -type d -exec chmod 2775 {} \; -# find . -type f -exec chmod 775 {} \; - - -
-This last step allows various users of the group spider to have -write access to all the directories. This is not really needed just yet -but will be useful when web interfaces start to appear. - -
-Finally, you need to fix the permissions on the ax25_call and netrom_call -programs. Check where they are with the locate command and alter -the permissions with the chmod command like this .. - - -# chown root ax25_call netrom_call -# chmod 4775 ax25_call netrom_call - - -Setting callsigns etc - -
-Now login to your machine as the user you created earlier. In my case that -user is called sysop. Once logged in, issue the following commands .... - - -$ cd /spider -$ mkdir local -$ mkdir local_cmd -$ cp perl/DXVars.pm.issue local/DXVars.pm -$ cd local -$ vi DXVars.pm (or your favourite editor) - - -
-Using the distributed DXVars.pm as a a template, set your cluster callsign, -sysop callsign and other user info to suit your own environment. Note that -this a perl file which will be parsed and executed as part of the cluster. If -you get it wrong then perl will complain when you start the cluster process. -It is important only to alter the text of any section. Some of the lines look -a little odd. Take this line for example .... - --$myemail = "ianmaude\@btinternet.com"; - - -
-There appears to be an extra slash in there. However this has to be there -for the file to work so leave it in. - -
PLEASE USE CAPITAL LETTERS FOR CALLSIGNS - -
-DON'T alter any file in /spider/perl, they are overwritten with every -release. Any files or commands you place in /spider/local or /spider/local_cmd -will automagically be used in preference to the ones in /spider/perl EVEN -while the cluster is running! - -
-Save the new file and change directory to ../perl .... - - -$ cd ../perl - - -
-Now type the following command which creates the basic user file with you as -the sysop. - - -$ ./create_sysop.pl - - -Starting up for the first time - -
-We can now bring spider up for the first time and see if all is well or not! -It should look something like this ... - - -$ ./cluster.pl -DXSpider DX Cluster Version 1.46 -Copyright (c) 1998 Dirk Koopman G1TLH -loading prefixes ... -loading band data ... -loading user file system ... -starting listener ... -reading existing message headers -reading cron jobs -orft we jolly well go ... - - -
-If all is well then login on another term or console as sysop and -cd to /spider/src. Now issue the following command ... - - -$ ./client - - -
-This should log you into the cluster as the sysop under the alias callsign we -set earlier. In this case the callsign is G0VGS. The cluster callsign is set -in the DXVars.pm file in /spider/local. In this case we will assume that this -was set as GB7MBC. You should therefore see this when you login .... - - -G0VGS de GB7MBC 19-Nov-1999 2150Z > - - -If you do, congratulations! If not, look over the instructions again, you -have probably missed something out. You can shut spider down again with the -command .... - - -shutdown - - -
-and both the cluster and the client should return to Linux prompts. - -The Client program - -
-In earlier versions of Spider, all the processes were Perl scripts. This -was fine but with a lot of users your computer memory would soon be used up. -To combat this a new client was written in "C". This client only works for -incoming connects at the moment. Before you can use it though it -has to be "made". CD to /spider/src and type make. You -should see the output on your screen and hopefully now have a small C program -called client. Leave it in this directory. - - -Quick installation guide (Linux version) - -
-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. - - -Login as root -Get the additional CPAN modules and install them (root) -Create the "sysop" user and set a password (root) -Put the Spider tarball in ~sysop and untar it (root) -ln -s ~sysop/spider /spider (root) -groupadd -g 251 spider (root) -Add any more users you need to the group entry in /etc/group (root) -Set the permissions on the spider tree (root) -Fix permissions on ax25_call and netrom_call (root) -Login as the sysop user -cd to /spider (sysop) -mkdir local (sysop) -mkdir local_cmd (sysop) -cp perl/DXVars.pm.issue local/DXVars.pm (sysop) -cd to /spider/local and edit DXVars to set your details (sysop) -cd ../perl (sysop) -./create_sysop.pl (sysop) -./cluster.pl (sysop) - - -Spider should now be running and you should be able to login using the -client program. - - -Login as root -Enter the correct line in ax25d.conf (root) -Enter the correct line in /etc/services (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. - - -Login as sysop -Start the cluster (sysop) -set/node and type for links (sysop) -Write any connect scripts (sysop) -Edit /spider/crontab as required (sysop) -Edit any other files as necessary (sysop) -Set filters, hops and forwarding files (sysop) -Login as root -Enter the correct line in /etc/inittab (root) - - -Configuration - -Allowing ax25 connects from users - -
-As stated previously, the aim of this document is not to tell you how to -configure Linux or the ax25 utilities. However, you do need to add a line -in your ax25d.conf to allow connections to DXSpider for your users. For -each interface that you wish to allow connections on, use the following format ... - - -default * * * * * * - sysop /spider/src/client client %u ax25 - - -or, if you wish your users to be able to use SSID's on their callsigns .. - - -default * * * * * * - sysop /spider/src/client client %s ax25 - - -For most purposes this is not desirable. The only time you probably will -need this is when you need to allow other cluster nodes that are using SSID's -in. In this case it would probably be better to use the first example and -then add a specific line for that node like this: - - -GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 -default * * * * * * - sysop /spider/src/client client %u ax25 - - -Allowing telnet connects from users - -
-From version 1.47 there is a new (more efficient) way of doing this -(see next section) but, if you prefer, the method of doing it described -here will continue to work just fine. - -
-Allowing telnet connections is quite simple. Firstly you need to add a line -in /etc/services to allow connections to a port number, like this .... - - -spdlogin 8000/tcp # spider anonymous login port - - -Then add a line in /etc/inetd.conf like this .... - - -spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet - - -
-Once this is done, you need to restart inetd like this .... - - -killall -HUP inetd - - - -
Now login as sysop and cd spider/src. You can test that spider -is accepting telnet logins by issuing the following command .... - - -./client login telnet - - -You should get a login prompt and on issuing a callsign, you will be given -access to the cluster. Note, you will not get a password login. There seems -no good reason for a password prompt to be given so it is not asked for. - -
-Assuming all is well, then try a telnet from your linux console .... - - -telnet localhost 8000 - - -
-You should now get the login prompt and be able to login as before. - -Setting up telnet connects (from 1.47 onwards) - -
-From version 1.47 you can choose to allow the perl cluster.pl program to -allow connections directly (i.e. not via the /spider/src/client -interface program). If you are using Windows then this is the only method -available of allowing incoming telnet connections. - -
-To do this you need first to remove any line that you may previously have set -up in /etc/inetd.conf. Remember to:- - - -killall -HUP inetd - - -
-to make the change happen... - -
-Having done that, you need to copy the file -/spider/perl/Listeners.pm to /spider/local and -then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot; -and select the correct port to listen on. So that it looks like this:- - - -@listen = ( - ["0.0.0.0", 8000], -); - - -
-As standard, the listener will listen on all interfaces simultaneously. -If you require more control than this, you can specify each interface -individually:- - - -@listen = ( - ["gb7baa.dxcluster.net", 8000], - ["44.131.16.2", 6300], -); - - -
-This will only be successful if the IP addresses on each interface are static. -If you are using some kind of dynamic IP addressing then the 'default' method -is the only one that will work. - -
-Restart the cluster.pl program to enable the listener. - -
-One important difference with the internal listener is that no echoing -is done by the cluster program. Users will need to set 'local-echo' on in -their telnet clients if it isn't set automatically (as per the standards). -Needless to say this will probably only apply to Windows users. - -Setting up for AGW Engine (1.47 onwards) - -
-AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine -from Linux as well as Windows based machines. - -
-In order to enable access to an AGW Engine you need to copy -/spider/perl/AGWConnect.pm to /spider/local and edit it. -Specifically you must:- - - - set $enable to 1. - set $login and $passwd to the values set up in your AGW installation. -If you haven't set any there, then you should not touch these values. - You can connect to a remote AGW engine (ie on some other machine) by changing $addr -and $port appropriately. - Restart the cluster.pl program - - - -Setting up node connects - -
-In order to allow cluster node connections, spider needs to know that the -connecting callsign is a cluster node. This is the case whether the connect -is incoming or outgoing. In spider this is a simple task and can be done in -runtime. - -
-Later versions of Spider can distinguish different software and treat them -differently. For example, the WCY beacon cannot be handles by AK1A type -nodes as AK1A does not know what to do with PC73. There are 4 different -types of node at present and although they may not have any major -differences at the moment, it allows for compatibility. The 4 types are ... - - -set/node (AK1A type) -set/spider -set/dxnet -set/clx - - -
-For now, we will assume that the cluster we are going to connect to is an -AK1A type node. - -
-Start up the cluster as you did before and login as the sysop with client. -The cluster node I am wanting to make a connection to is GB7BAA but you would -obviously use whatever callsign you required. At the prompt type ... - - -set/node gb7baa - - -
-The case does not matter as long as you have a version of DXSpider later than -1.33. Earlier versions required the callsign to be in upper case. - -
-That is now set, it is as simple as that. To prove it, login on yet another -console as sysop, cd to spider/src and issue the command ... - - -./client gb7baa (using the callsign you set as a node) - - -
-You should get an initialisation string from DXSpider like this ... - - -./client gb7baa -PC38^GB7MBC^~ - - -If the callsign you just set up as a cluster node is for an incoming connect, -this is all that needs to be done. If the connection is to be outgoing then -a connection script needs to be written. - -
-Sometimes you make a mistake... Honest, it does happen. If you want to make a node -back to being a normal user, regardless -of what type it is, do: - - -unset/node gb7baa - - -Connection scripts - -
-Because DXSpider operates under Linux, connections can be made using just about -any protocol; AX25, NETRom, tcp/ip, ROSE etc are all possible examples. -Connect scripts live in the /spider/connect directory and are simple ascii files. -Writing a script for connections is therefore relatively simple. - -
-The connect scripts consist of lines which start with the following keywords -or symbols:- - - - -# are ignored, as are completely - blank lines. - -timeout followed by a number is the number of seconds to wait for a - command to complete. If there is no timeout specified in the script - then the default is 60 seconds. - -abort is a regular expression containing one or more strings to look - for to abort a connection. This is a perl regular expression and is - executed ignoring case. - -connect followed by ax25, agw (for Windows users) or telnet and some type dependent - information. In the case of a telnet connection, there can be up to - two parameters. - The first is the ip address or hostname of the computer you wish to - connect to and the second is the port number you want to use (this - can be left out if it is a normal telnet session). - In the case of an ax25 session then this would normally be a call to - ax25_call or netrom_call as in the example above. It is your - responsibility to get your node and other ax25 parameters to work - before going down this route! - -' is the delimiting character for a word or phrase of an expect/send - line in a chat type script. The words/phrases normally come in pairs, - either can be empty. Each line reads input from the connection until - it sees the string (or perl regular expression) contained in the - left hand string. If the left hand string is empty then it doesn't - read or wait for anything. The comparison is done ignoring case. - When the left hand string has found what it is looking for (if it is) - then the right hand string is sent to the connection. - This process is repeated for every line of chat script. - -client starts the connection, put the arguments you would want here - if you were starting the client program manually. You only need this - if the script has a different name to the callsign you are trying to - connect to (i.e. you have a script called other which actually - connects to GB7DJK-1 [instead of a script called gb7djk-1]). - - - -There are many possible ways to configure the script but here are three examples, -one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip. - - -timeout 60 -abort (Busy|Sorry|Fail) -# don't forget to chmod 4775 netrom_call! -connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh -'Connect' '' -'Connect' 'c np7' -'Connect' 'c gb7dxm' -# you can leave this out if you call the script 'gb7dxm' -client gb7dxm ax25 - - -
- - -timeout 60 -abort (Busy|Sorry|Fail) -# this does exactly the same as the previous example -# the '1' is the AGW port number to connect thru for g1tlh -connect agw 1 g1tlh -'Connect' '' -'Connect' 'c np7' -'Connect' 'c gb7dxm' -# you can leave this out if you call the script 'gb7dxm' -client gb7dxm ax25 - - -
- - -timeout 15 -connect telnet dirkl.tobit.co.uk -'login' 'gb7djk' -'word' 'gb7djk' -# tell GB7DJK-1 that it is connected to GB7DJK -# you can leave this out if you call this script 'gb7djk' -client gb7djk telnet - - -
-Both these examples assume that everything is set up properly at the other end. -You will find other examples in the /spider/examples directory. - -Starting the connection - -
-You start the connection, from within a sysop enabled cluster login, by typing -in the word connect followed by a script name like this .... - - -G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1 -connection to GB7DJK-1 started -G0VGS de GB7MBC 13-Dec-1998 2043Z > - - -This will start a connection using the script called gb7djk-1. You can -follow the connection by watching the term or console from where you started -cluster.pl. From version 1.47 onwards, you will need to set/debug connect first. -You should see something like this ... - - -<- D G1TLH connect gb7djk-1 --> D G1TLH connection to GB7DJK-1 started --> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > -timeout set to 15 -CONNECT sort: telnet command: dirkl.tobit.co.uk -CHAT "login" -> "gb7djk" -received " -Red Hat Linux release 5.1 (Manhattan) -Kernel 2.0.35 on an i586 -" -received "login: " -sent "gb7djk" -CHAT "word" -> "gb7djk" -received "gb7djk" -received "Password: " -sent "gb7djk" -Connected to GB7DJK-1, starting normal protocol -<- O GB7DJK-1 telnet --> B GB7DJK-1 0 -GB7DJK-1 channel func state 0 -> init -<- D GB7DJK-1 -<- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 -<- D GB7DJK-1 PC38^GB7DJK-1^~ -<- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime -0 00:00^5447^~ - etc - - - -
-With later versions of Spider there is a set/login command for users. This -tells them when a user or node logs in or out. If you do not add a line to -your scripts after the final line (or before the client line which should always -be last if needed) then the login/logout information will be sent to users -before the login actually completes. This means if a node is -unreachable, it will continue sending logins and logouts to users even though it -is not actually connecting. To avoid this use the following line ... - - -'connect' '' - - -
-In a script, this might look like ... - - -timeout 35 -abort (Busy|Sorry|Fail) -connect telnet mary 3000 -'ogin:' 'gb7mbc' -'>' 'telnet 44.131.93.96 7305' -'connect' '' - - -Telnet echo - -
-Cluster links in particular suffer greatly from the presence of telnet echo. -This is caused by the telnet negotiation itself and can create at worst severe -loops. At best it creates unnecessary bandwidth and large logfiles! There are -things that can be done to limit this problem but will not always work dependent -on the route taken to connect. - -
-Telnet echo itself should only be a problem if the connection is being made to -the telnet port (23). This port uses special rules that include echo negotiation. -If the connection is to a different port, such as 7300, this negotiation does -not happen and therefore no echo should be present. - -
-Sometimes it is not possible to make a direct connection to another node and this -can cause problems. There is a way of trying to suppress the telnet echo but -this will not always work, unfortunately it is difficult to be more specific. -Here is an example of what I mean ... - - -timeout 35 -abort (Busy|Sorry|Fail) -connect telnet mary.lancs.ac.uk -'ogin:' 'gb7mbc' -'word:' 'mypasswd' -'\$' 'stty -echo raw' -'\$' 'telnet 44.131.93.96' -'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 -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. - - -Automating things - -
-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 and if -connection scripts fail they have to be started again manually too, not much use -if you are not at the console! So, in this section we will automate both. -Firstly starting the cluster. - -Autostarting the cluster - -
-This is not only a way to start the cluster automatically, it also works as a -watchdog, checking the sanity of DXSpider and respawning it should it crash for -any reason. Before doing the following, shutdown the cluster as you did earlier. - -
-Login as root and bring up the /etc/inittab file in your favourite editor. Add -the following lines to the file near the end ... - - -##Start DXSpider on bootup and respawn it should it crash -DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 - - -
-This line works fine for RedHat distributions. It is also fine for SuSE up to -7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ... - - -DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 - - - -The line required for Slackware distributions is slightly different. My thanks to -Aurelio, PA3EZL for this information. - - -DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7 - - -
-This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart -it should it crash for any reason. - -
-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. - -
-So far so good, now to automate script connections... - -The crontab file - -
-Login as sysop and create a file in /spider/local_cmd called crontab. -Edit it with your favourite editor and add a line like this (I have included -a comment) - - -# check every 10 minutes to see if gb7xxx is connected and if not -# start a connect job going - -0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') - - -
-The callsign involved will be the callsign of the cluster node you are -going to connect to. This will now check every 10 minutes to see if -gb7xxx is connected, if it is then nothing will be done. If it is not, -then a connect attempt will be started. - -
-There are probably lots of other things you could use this crontab file for. -If you want to know more about it, look at the - website -at the cron page where it is explained more fully. - Hop control
diff --git a/sgml/spiderCVS.sgml b/sgml/spiderCVS.sgml index 52bdfd95..83042b04 100644 --- a/sgml/spiderCVS.sgml +++ b/sgml/spiderCVS.sgml @@ -4,7 +4,7 @@ -The DXSpider CVS Changes erratum +<title>The DXSpider CVS Changes addendum <author>Ian Maude, G0VGS, (ianmaude@btinternet.com) <date>Version 0.1 March 2001 <abstract> diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index 16c3e0de..ead5fdd4 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,6 @@ - The DXSpider Installation and Administration Manual + The DXSpider Administration Manual v1.47 Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 1.47 (Revision 1.30), April 2001 + A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -64,1231 +64,241 @@ - 1. Installation (Original version by Iain Philipps, G0RDI) - - 1.1 Introduction - 1.2 Preparation - 1.3 Installing the software - 1.4 Setting callsigns etc - 1.5 Starting up for the first time - 1.6 The Client program - - 2. Quick installation guide (Linux version) - - 3. Configuration + 1. Hop control - 3.1 Allowing ax25 connects from users - 3.2 Allowing telnet connects from users - 3.3 Setting up telnet connects (from 1.47 onwards) - 3.4 Setting up for AGW Engine (1.47 onwards) - 3.5 Setting up node connects - 3.6 Connection scripts - 3.7 Starting the connection - 3.8 Telnet echo + 1.1 Basic hop control + 1.2 Isolating networks - 4. Automating things + 2. Filtering (Old Style upto v1.44) - 4.1 Autostarting the cluster - 4.2 The crontab file + 2.1 Spots + 2.2 Announcements + 2.3 WWV - 5. Hop control + 3. Filtering (New Style v1.45 and later) - 5.1 Basic hop control - 5.2 Isolating networks + 3.1 General filter rules + 3.2 Types of filter + 3.3 Filter options + 3.4 Default filters + 3.5 Advanced filtering - 6. Filtering (Old Style upto v1.44) + 4. Other filters - 6.1 Spots - 6.2 Announcements - 6.3 WWV + 4.1 Filtering Mail + 4.2 Filtering DX callouts (Depricated) + 4.3 Filtering words from text fields in Announce, Talk and DX spots - 7. Filtering (New Style v1.45 and later) + 5. Mail - 7.1 General filter rules - 7.2 Types of filter - 7.3 Filter options - 7.4 Default filters - 7.5 Advanced filtering + 5.1 Personal mail + 5.2 Bulletin mail + 5.3 Forward.pl + 5.4 The msg command + 5.5 Message status + 5.6 Filtering mail + 5.7 Distribution lists + 5.8 BBS interface - 8. Other filters + 6. Databases - 8.1 Filtering Mail - 8.2 Filtering DX callouts (Depricated) - 8.3 Filtering words from text fields in Announce, Talk and DX spots + 6.1 Creating databases + 6.2 Importing databases + 6.3 Checking available databases + 6.4 Looking up databases + 6.5 Removing databases - 9. Mail + 7. Information, files and useful programs - 9.1 Personal mail - 9.2 Bulletin mail - 9.3 Forward.pl - 9.4 The msg command - 9.5 Message status - 9.6 Filtering mail - 9.7 Distribution lists - 9.8 BBS interface + 7.1 MOTD + 7.2 Downtime message + 7.3 Other text messages + 7.4 The Aliases file + 7.5 Console.pl + 7.6 Updating kepler data + 7.7 The QRZ callbook - 10. Databases + 8. CVS - 10.1 Creating databases - 10.2 Importing databases - 10.3 Checking available databases - 10.4 Looking up databases - 10.5 Removing databases + 9. The DXSpider command set - 11. Information, files and useful programs - - 11.1 MOTD - 11.2 Downtime message - 11.3 Other text messages - 11.4 The Aliases file - 11.5 Console.pl - 11.6 Updating kepler data - 11.7 The QRZ callbook - - 12. CVS - - 13. The DXSpider command set - - 13.1 accept/announce (0) - 13.2 accept/announce (extended for sysops) (8) - 13.3 accept/spots (0) - 13.4 accept/spots (extended for sysops) (8) - 13.5 accept/wcy (0) - 13.6 accept/wcy (extended for sysops) (8) - 13.7 accept/wwv (0) - 13.8 accept/wwv (extended for sysops) (8) - 13.9 announce (0) - 13.10 announce full (0) - 13.11 announce sysop (5) - 13.12 apropos (0) - 13.13 bye (0) - 13.14 catchup (5) - 13.15 clear/spots (0) - 13.16 connect (5) - 13.17 dbavail (0) - 13.18 dbcreate (9) - 13.19 dbimport (9) - 13.20 dbremove (9) - 13.21 dbshow (0) - 13.22 debug (9) - 13.23 directory (0) - 13.24 directory (extended for sysops) (5) - 13.25 disconnect (8) - 13.26 dx (0) - 13.27 export (9) - 13.28 export_users (9) - 13.29 forward/latlong (8) - 13.30 forward/opername (1) - 13.31 help (0) - 13.32 init (5) - 13.33 kill (0) - 13.34 kill (5) - 13.35 kill full (5) - 13.36 links (0) - 13.37 load/aliases (9) - 13.38 load/baddx (9) - 13.39 load/badmsg (9) - 13.40 load/badwords (9) - 13.41 load/bands (9) - 13.42 load/cmd_cache (9) - 13.43 load/forward (9) - 13.44 load/messages (9) - 13.45 load/prefixes (9) - 13.46 merge (5) - 13.47 msg (9) - 13.48 pc (8) - 13.49 ping (1) - 13.50 rcmd (1) - 13.51 read (0) - 13.52 read (extended for sysops) (5) - 13.53 reject/announce - 13.54 reject/announce (extended for sysops) (8) - 13.55 reject/spots (0) - 13.56 reject/spots (extended for sysops) (8) - 13.57 reject/wcy (0) - 13.58 reject/wcy (extended for sysops) (8) - 13.59 reject/wwv (0) - 13.60 reject/wwv (extended for sysops) (8) - 13.61 reply (0) - 13.62 send (0) - 13.63 set/address (0) - 13.64 set/announce (0) - 13.65 set/arcluster (5) - 13.66 set/baddx (8) - 13.67 set/badnode (6) - 13.68 set/badspotter (8) - 13.69 set/beep (0) - 13.70 set/clx (5) - 13.71 set/debug (9) - 13.72 set/dx (0) - 13.73 set/dxgrid (0) - 13.74 set/dxnet (5) - 13.75 set/echo (0) - 13.76 set/here (0) - 13.77 set/homenode (0) - 13.78 set/hops (8) - 13.79 set/isolate (9) - 13.80 set/language (0) - 13.81 set/location (0) - 13.82 set/sys_location (9) - 13.83 set/logininfo (0) - 13.84 set/lockout (9) - 13.85 set/name (0) - 13.86 set/node (9) - 13.87 set/obscount (9) - 13.88 set/page (0) - 13.89 set/password (9) - 13.90 set/pinginterval (9) - 13.91 set/privilege (9) - 13.92 set/spider (5) - 13.93 set/sys_qra (9) - 13.94 set/qra (0) - 13.95 set/qth (0) - 13.96 set/talk (0) - 13.97 set/wcy (0) - 13.98 set/wwv (0) - 13.99 set/wx (0) - 13.100 show/baddx (1) - 13.101 show/badnode (6) - 13.102 show/badspotter (1) - 13.103 show/configuration (0) - 13.104 show/configuration/node (0) - 13.105 show/connect (1) - 13.106 show/date (0) - 13.107 show/debug (9) - 13.108 show/dx (0) - 13.109 show/dxcc (0) - 13.110 show/files (0) - 13.111 show/filter (0) - 13.112 show/filter (extended for sysops) (5) - 13.113 show/hops (8) - 13.114 show/isolate (1) - 13.115 show/lockout (9) - 13.116 show/log (8) - 13.117 show/moon (0) - 13.118 show/muf (0) - 13.119 show/node (1) - 13.120 show/prefix (0) - 13.121 show/program (5) - 13.122 show/qra (0) - 13.123 show/qrz (0) - 13.124 show/route (0) - 13.125 show/satellite (0) - 13.126 show/sun (0) - 13.127 show/time (0) - 13.128 show/wcy (0) - 13.129 show/wwv (0) - 13.130 shutdown (5) - 13.131 spoof (9) - 13.132 stat/db (5) - 13.133 stat/channel (5) - 13.134 stat/msg (5) - 13.135 stat/user (5) - 13.136 sysop (0) - 13.137 talk (0) - 13.138 type (0) - 13.139 who (0) - 13.140 wx (0) - 13.141 wx (enhanced for sysops) (5) + 9.1 accept/announce (0) + 9.2 accept/announce (extended for sysops) (8) + 9.3 accept/spots (0) + 9.4 accept/spots (extended for sysops) (8) + 9.5 accept/wcy (0) + 9.6 accept/wcy (extended for sysops) (8) + 9.7 accept/wwv (0) + 9.8 accept/wwv (extended for sysops) (8) + 9.9 announce (0) + 9.10 announce full (0) + 9.11 announce sysop (5) + 9.12 apropos (0) + 9.13 bye (0) + 9.14 catchup (5) + 9.15 clear/spots (0) + 9.16 connect (5) + 9.17 dbavail (0) + 9.18 dbcreate (9) + 9.19 dbimport (9) + 9.20 dbremove (9) + 9.21 dbshow (0) + 9.22 debug (9) + 9.23 directory (0) + 9.24 directory (extended for sysops) (5) + 9.25 disconnect (8) + 9.26 dx (0) + 9.27 export (9) + 9.28 export_users (9) + 9.29 forward/latlong (8) + 9.30 forward/opername (1) + 9.31 help (0) + 9.32 init (5) + 9.33 kill (0) + 9.34 kill (5) + 9.35 kill full (5) + 9.36 links (0) + 9.37 load/aliases (9) + 9.38 load/baddx (9) + 9.39 load/badmsg (9) + 9.40 load/badwords (9) + 9.41 load/bands (9) + 9.42 load/cmd_cache (9) + 9.43 load/forward (9) + 9.44 load/messages (9) + 9.45 load/prefixes (9) + 9.46 merge (5) + 9.47 msg (9) + 9.48 pc (8) + 9.49 ping (1) + 9.50 rcmd (1) + 9.51 read (0) + 9.52 read (extended for sysops) (5) + 9.53 reject/announce + 9.54 reject/announce (extended for sysops) (8) + 9.55 reject/spots (0) + 9.56 reject/spots (extended for sysops) (8) + 9.57 reject/wcy (0) + 9.58 reject/wcy (extended for sysops) (8) + 9.59 reject/wwv (0) + 9.60 reject/wwv (extended for sysops) (8) + 9.61 reply (0) + 9.62 send (0) + 9.63 set/address (0) + 9.64 set/announce (0) + 9.65 set/arcluster (5) + 9.66 set/baddx (8) + 9.67 set/badnode (6) + 9.68 set/badspotter (8) + 9.69 set/beep (0) + 9.70 set/clx (5) + 9.71 set/debug (9) + 9.72 set/dx (0) + 9.73 set/dxgrid (0) + 9.74 set/dxnet (5) + 9.75 set/echo (0) + 9.76 set/here (0) + 9.77 set/homenode (0) + 9.78 set/hops (8) + 9.79 set/isolate (9) + 9.80 set/language (0) + 9.81 set/location (0) + 9.82 set/sys_location (9) + 9.83 set/logininfo (0) + 9.84 set/lockout (9) + 9.85 set/name (0) + 9.86 set/node (9) + 9.87 set/obscount (9) + 9.88 set/page (0) + 9.89 set/password (9) + 9.90 set/pinginterval (9) + 9.91 set/privilege (9) + 9.92 set/spider (5) + 9.93 set/sys_qra (9) + 9.94 set/qra (0) + 9.95 set/qth (0) + 9.96 set/talk (0) + 9.97 set/wcy (0) + 9.98 set/wwv (0) + 9.99 set/wx (0) + 9.100 show/baddx (1) + 9.101 show/badnode (6) + 9.102 show/badspotter (1) + 9.103 show/configuration (0) + 9.104 show/configuration/node (0) + 9.105 show/connect (1) + 9.106 show/date (0) + 9.107 show/debug (9) + 9.108 show/dx (0) + 9.109 show/dxcc (0) + 9.110 show/files (0) + 9.111 show/filter (0) + 9.112 show/filter (extended for sysops) (5) + 9.113 show/hops (8) + 9.114 show/isolate (1) + 9.115 show/lockout (9) + 9.116 show/log (8) + 9.117 show/moon (0) + 9.118 show/muf (0) + 9.119 show/node (1) + 9.120 show/prefix (0) + 9.121 show/program (5) + 9.122 show/qra (0) + 9.123 show/qrz (0) + 9.124 show/route (0) + 9.125 show/satellite (0) + 9.126 show/sun (0) + 9.127 show/time (0) + 9.128 show/wcy (0) + 9.129 show/wwv (0) + 9.130 shutdown (5) + 9.131 spoof (9) + 9.132 stat/db (5) + 9.133 stat/channel (5) + 9.134 stat/msg (5) + 9.135 stat/user (5) + 9.136 sysop (0) + 9.137 talk (0) + 9.138 type (0) + 9.139 who (0) + 9.140 wx (0) + 9.141 wx (enhanced for sysops) (5) ______________________________________________________________________ - 11.. IInnssttaallllaattiioonn ((OOrriiggiinnaall vveerrssiioonn bbyy IIaaiinn PPhhiilliippppss,, GG00RRDDII)) - - 11..11.. IInnttrroodduuccttiioonn - - This section describes the installation of DX Spider v1.46 on a RedHat - Linux Distribution. Wherever possible I will try to include - differences for other distributions. I do not intend to try and cover - the installation of Linux or the setup of the AX25 utilities. If you - need help on this then read Iains original installation guide that - comes with the Spider distribution. - - - I am assuming a general knowledge of Linux and its commands. You - should know how to use _t_a_r 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 _S_T_R_O_N_G_L_Y recommended - that you use at least version 5.005_03 as this is the version being - used in the development of Spider. - - - In addition to the standard Red Hat distribution you will require the - following modules from http://www.cpan.org/CPAN.html ... - - - - +o Data-Dumper-2.101.tar.gz - - +o TimeDate-1.10.tar.gz - - +o IO-1.20.tar.gz (for perl 5.00403 and lower) - - +o Net-Telnet-3.02.tar.gz - - +o Curses-1.05.tar.gz - - +o Time-HiRes-01.20.tar.gz - - - - _D_o get the latest versions of these packages and install them but use - the above list as the earliest versions usable. - - - 11..22.. PPrreeppaarraattiioonn - - 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.46 for this section but of course you would use the latest - version. - - - Login as root and create a user to run the cluster under. _U_N_D_E_R _N_O - _C_I_R_C_U_M_S_T_A_N_C_E_S _U_S_E _R_O_O_T _A_S _T_H_I_S _U_S_E_R_!. I am going to use the name - _s_y_s_o_p. You can call it anything you wish. Depending on your security - requirements you may wish to use an existing user, however this is - your own choice. - - - - - # adduser -m sysop - - - - - - Now set a password for the user ... - - - - # passwd sysop - # New UNIX password: - # Retype new UNIX password: - passwd: all authentication tokens updated successfully - - - - - - 11..33.. IInnssttaalllliinngg tthhee ssooffttwwaarree - - Now to unpack the DX Spider distribution, set symbolic links and group - permissions. Copy the tarball to /home/sysop and do the following. - - - - # cd ~sysop - # tar xvfz spider-1.46.tar.gz - # ln -s ~sysop/spider /spider - # groupadd -g 251 spider (or another number) - - - - - If you do not have the command _g_r_o_u_p_a_d_d available to you simply add a - line in /etc/group by hand. - - # vi /etc/group (or your favorite editor) - - - - - You also need to add some others to the group, including your own - callsign (this will be used as an alias) and root. The finished line - in /etc/group should look something like this - - spider:x:251:sysop,g0vgs,root - - - The next step is to set the permissions on the Spider directory tree - and files .... - - - - # chown -R sysop.spider spider - # find . -type d -exec chmod 2775 {} \; - # find . -type f -exec chmod 775 {} \; - - - - - - This last step allows various users of the group _s_p_i_d_e_r to have write - access to all the directories. This is not really needed just yet but - will be useful when web interfaces start to appear. - - - Finally, you need to fix the permissions on the ax25_call and - netrom_call programs. Check where they are with the _l_o_c_a_t_e command - and alter the permissions with the _c_h_m_o_d command like this .. - - - - # chown root ax25_call netrom_call - # chmod 4775 ax25_call netrom_call - - - - - - 11..44.. SSeettttiinngg ccaallllssiiggnnss eettcc - - Now login to your machine as the user you created earlier. In my case - that user is called _s_y_s_o_p. Once logged in, issue the following - commands .... - - - - $ cd /spider - $ mkdir local - $ mkdir local_cmd - $ cp perl/DXVars.pm.issue local/DXVars.pm - $ cd local - $ vi DXVars.pm (or your favourite editor) - - - - - - Using the distributed DXVars.pm as a a template, set your cluster - callsign, sysop callsign and other user info to suit your own - environment. Note that this a perl file which will be parsed and - executed as part of the cluster. If you get it wrong then perl will - complain when you start the cluster process. It is important only to - alter the text of any section. Some of the lines look a little odd. - Take this line for example .... - - $myemail = "ianmaude\@btinternet.com"; - - - There appears to be an extra slash in there. However this has to be - there for the file to work so leave it in. - - - PPLLEEAASSEE UUSSEE CCAAPPIITTAALL LLEETTTTEERRSS FFOORR CCAALLLLSSIIGGNNSS - - - DON'T alter any file in /spider/perl, they are overwritten with every - release. Any files or commands you place in /spider/local or - /spider/local_cmd will automagically be used in preference to the ones - in /spider/perl EVEN while the cluster is running! - - - Save the new file and change directory to ../perl .... - - - - $ cd ../perl - - - - - - Now type the following command which creates the basic user file with - you as the sysop. - - - - $ ./create_sysop.pl - - - - - - 11..55.. SSttaarrttiinngg uupp ffoorr tthhee ffiirrsstt ttiimmee - - We can now bring spider up for the first time and see if all is well - or not! It should look something like this ... - - - - $ ./cluster.pl - DXSpider DX Cluster Version 1.46 - Copyright (c) 1998 Dirk Koopman G1TLH - loading prefixes ... - loading band data ... - loading user file system ... - starting listener ... - reading existing message headers - reading cron jobs - orft we jolly well go ... - - - - - - If all is well then login on another term or console as _s_y_s_o_p and cd - to /spider/src. Now issue the following command ... - - $ ./client - - - - - - This should log you into the cluster as the sysop under the alias - callsign we set earlier. In this case the callsign is G0VGS. The - cluster callsign is set in the DXVars.pm file in /spider/local. In - this case we will assume that this was set as GB7MBC. You should - therefore see this when you login .... - - - - G0VGS de GB7MBC 19-Nov-1999 2150Z > - - - - - If you do, congratulations! If not, look over the instructions again, - you have probably missed something out. You can shut spider down - again with the command .... - - - - shutdown - - - - - - and both the cluster and the client should return to Linux prompts. - - - 11..66.. TThhee CClliieenntt pprrooggrraamm - - In earlier versions of Spider, all the processes were Perl scripts. - This was fine but with a lot of users your computer memory would soon - be used up. To combat this a new client was written in "C". This - client only works for _i_n_c_o_m_i_n_g connects at the moment. Before you can - use it though it has to be "made". CD to /spider/src and type _m_a_k_e. - You should see the output on your screen and hopefully now have a - small C program called _c_l_i_e_n_t. Leave it in this directory. - - - - 22.. QQuuiicckk iinnssttaallllaattiioonn gguuiiddee ((LLiinnuuxx vveerrssiioonn)) - - This section is designed for experienced Spider sysops who want to - install Spider from scratch. It is simply a check list of things that - need to be done without any explanations. The name in brackets at the - end of each line is the user that should be doing that process. - - - +o Login as root - - +o Get the additional CPAN modules and install them (root) - - +o Create the "sysop" user and set a password (root) - - +o Put the Spider tarball in sysop and untar it (root) - - +o ln -s sysop/spider /spider (root) - - +o groupadd -g 251 spider (root) - - +o Add any more users you need to the group entry in /etc/group (root) - - +o Set the permissions on the spider tree (root) - - +o Fix permissions on ax25_call and netrom_call (root) - - +o Login as the sysop user - - +o cd to /spider (sysop) - - +o mkdir local (sysop) - - +o mkdir local_cmd (sysop) - - +o cp perl/DXVars.pm.issue local/DXVars.pm (sysop) - - +o cd to /spider/local and edit DXVars to set your details (sysop) - - +o cd ../perl (sysop) - - +o ./create_sysop.pl (sysop) - - +o ./cluster.pl (sysop) - - Spider should now be running and you should be able to login using the - client program. - - - +o Login as root - - +o Enter the correct line in ax25d.conf (root) - - +o Enter the correct line in /etc/services (root) - - +o Enter the correct line in /etc/inetd.conf (root) - - +o killall -HUP inetd (root) - - Spider should now be able to accept logins via telnet, netrom and - ax25. - - - +o Login as sysop - - +o Start the cluster (sysop) - - +o set/node and type for links (sysop) - - +o Write any connect scripts (sysop) - - +o Edit /spider/crontab as required (sysop) - - +o Edit any other files as necessary (sysop) - - +o Set filters, hops and forwarding files (sysop) - - +o Login as root - - +o Enter the correct line in /etc/inittab (root) - - - 33.. CCoonnffiigguurraattiioonn - - - - - 33..11.. AAlllloowwiinngg aaxx2255 ccoonnnneeccttss ffrroomm uusseerrss - - As stated previously, the aim of this document is not to tell you how - to configure Linux or the ax25 utilities. However, you do need to add - a line in your ax25d.conf to allow connections to DXSpider for your - users. For each interface that you wish to allow connections on, use - the following format ... - - - - default * * * * * * - sysop /spider/src/client client %u ax25 - - - - - or, if you wish your users to be able to use SSID's on their callsigns - .. - - - - default * * * * * * - sysop /spider/src/client client %s ax25 - - - - - For most purposes this is not desirable. The only time you probably - will need this is when you need to allow other cluster nodes that are - using SSID's in. In this case it would probably be better to use the - first example and then add a specific line for that node like this: - - - - GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 - default * * * * * * - sysop /spider/src/client client %u ax25 - - - - - - 33..22.. AAlllloowwiinngg tteellnneett ccoonnnneeccttss ffrroomm uusseerrss - - - From version 1.47 there is a new (more efficient) way of doing this - (see next section) but, if you prefer, the method of doing it - described here will continue to work just fine. - - - Allowing telnet connections is quite simple. Firstly you need to add - a line in /etc/services to allow connections to a port number, like - this .... - - - - spdlogin 8000/tcp # spider anonymous login port - - - - - Then add a line in /etc/inetd.conf like this .... - - - - spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet - - - - Once this is done, you need to restart inetd like this .... - - - - killall -HUP inetd - - - - - - - Now login as _s_y_s_o_p and cd spider/src. You can test that spider is - accepting telnet logins by issuing the following command .... - - - - ./client login telnet - - - - - You should get a login prompt and on issuing a callsign, you will be - given access to the cluster. Note, you will not get a password login. - There seems no good reason for a password prompt to be given so it is - not asked for. - - - Assuming all is well, then try a telnet from your linux console .... - - - - telnet localhost 8000 - - - - - - You should now get the login prompt and be able to login as before. - - - 33..33.. SSeettttiinngg uupp tteellnneett ccoonnnneeccttss ((ffrroomm 11..4477 oonnwwaarrddss)) - - From version 1.47 you can choose to allow the perl cluster.pl program - to allow connections directly (i.e. not via the /spider/src/client - interface program). If you are using Windows then this is the only - method available of allowing incoming telnet connections. - - - To do this you need first to remove any line that you may previously - have set up in /etc/inetd.conf. Remember to:- - - - - killall -HUP inetd - - - - - - to make the change happen... - - - Having done that, you need to copy the file _/_s_p_i_d_e_r_/_p_e_r_l_/_L_i_s_t_e_n_e_r_s_._p_m - to _/_s_p_i_d_e_r_/_l_o_c_a_l and then edit it. You will need to uncomment the line - containing "0.0.0.0" and select the correct port to listen on. So that - it looks like this:- - @listen = ( - ["0.0.0.0", 8000], - ); - - - - - - As standard, the listener will listen on all interfaces - simultaneously. If you require more control than this, you can - specify each interface individually:- - - - - @listen = ( - ["gb7baa.dxcluster.net", 8000], - ["44.131.16.2", 6300], - ); - - - - - - This will only be successful if the IP addresses on each interface are - static. If you are using some kind of dynamic IP addressing then the - 'default' method is the only one that will work. - - - Restart the cluster.pl program to enable the listener. - - - One important difference with the internal listener is that no echoing - is done by the cluster program. Users will need to set 'local-echo' on - in their telnet clients if it isn't set automatically (as per the - standards). Needless to say this will probably only apply to Windows - users. - - - 33..44.. SSeettttiinngg uupp ffoorr AAGGWW EEnnggiinnee ((11..4477 oonnwwaarrddss)) - - AGW Engine is a Windows based ax25 stack. You can connect to an AGW - engine from Linux as well as Windows based machines. - - - In order to enable access to an AGW Engine you need to copy - _/_s_p_i_d_e_r_/_p_e_r_l_/_A_G_W_C_o_n_n_e_c_t_._p_m to _/_s_p_i_d_e_r_/_l_o_c_a_l and edit it. Specifically - you must:- - - - +o set $enable to 1. - - +o set $login and $passwd to the values set up in your AGW - installation. If you haven't set any there, then you should not - touch these values. - - +o You can connect to a remote AGW engine (ie on some other machine) - by changing $addr and $port appropriately. - - +o Restart the cluster.pl program - - - - - - - - 33..55.. SSeettttiinngg uupp nnooddee ccoonnnneeccttss - - In order to allow cluster node connections, spider needs to know that - the connecting callsign is a cluster node. This is the case whether - the connect is incoming or outgoing. In spider this is a simple task - and can be done in runtime. - - - Later versions of Spider can distinguish different software and treat - them differently. For example, the WCY beacon cannot be handles by - AK1A type nodes as AK1A does not know what to do with PC73. There are - 4 different types of node at present and although they may not have - any major differences at the moment, it allows for compatibility. The - 4 types are ... - - - - set/node (AK1A type) - set/spider - set/dxnet - set/clx - - - - - - For now, we will assume that the cluster we are going to connect to is - an AK1A type node. - - - Start up the cluster as you did before and login as the sysop with - client. The cluster node I am wanting to make a connection to is - GB7BAA but you would obviously use whatever callsign you required. At - the prompt type ... - - - - set/node gb7baa - - - - - - The case does not matter as long as you have a version of DXSpider - later than 1.33. Earlier versions required the callsign to be in - upper case. - - - That is now set, it is as simple as that. To prove it, login on yet - another console as sysop, cd to spider/src and issue the command ... - - - - ./client gb7baa (using the callsign you set as a node) - - - - - - You should get an initialisation string from DXSpider like this ... - - - - ./client gb7baa - PC38^GB7MBC^~ - - If the callsign you just set up as a cluster node is for an incoming - connect, this is all that needs to be done. If the connection is to - be outgoing then a connection script needs to be written. - - - Sometimes you make a mistake... Honest, it does happen. If you want - to make a node back to being a normal user, regardless of what type it - is, do: - - - - unset/node gb7baa - - - - - - 33..66.. CCoonnnneeccttiioonn ssccrriippttss - - Because DXSpider operates under Linux, connections can be made using - just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all - possible examples. Connect scripts live in the /spider/connect - directory and are simple ascii files. Writing a script for - connections is therefore relatively simple. - - - The connect scripts consist of lines which start with the following - keywords or symbols:- - - - - ## All lines starting with a # are ignored, as are completely blank - lines. - - - ttiimmeeoouutt - 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. - - - aabboorrtt - 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. - - - ccoonnnneecctt - connect followed by ax25, agw (for Windows users) or telnet and - some type dependent information. In the case of a telnet - connection, there can be up to two parameters. The first is the - ip address or hostname of the computer you wish to connect to - and the second is the port number you want to use (this can be - left out if it is a normal telnet session). In the case of an - ax25 session then this would normally be a call to ax25_call or - netrom_call as in the example above. It is your responsibility - to get your node and other ax25 parameters to work before going - down this route! - - - '' line in a chat type script. The words/phrases normally come in - pairs, either can be empty. Each line reads input from the - connection until it sees the string (or perl regular expression) - contained in the left hand string. If the left hand string is - empty then it doesn't read or wait for anything. The comparison - is done ignoring case. When the left hand string has found what - it is looking for (if it is) then the right hand string is sent - to the connection. This process is repeated for every line of - chat script. - - - cclliieenntt - client starts the connection, put the arguments you would want - here if you were starting the client program manually. You only - need this if the script has a different name to the callsign you - are trying to connect to (i.e. you have a script called other - which actually connects to GB7DJK-1 [instead of a script called - gb7djk-1]). - - - There are many possible ways to configure the script but here are - three examples, one for a NETRom/AX25 connect, one for AGW engines and - one for tcp/ip. - - - - timeout 60 - abort (Busy|Sorry|Fail) - # don't forget to chmod 4775 netrom_call! - connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh - # you can leave this out if you call the script 'gb7dxm' - client gb7dxm ax25 - - - - - - - - - timeout 60 - abort (Busy|Sorry|Fail) - # this does exactly the same as the previous example - # the '1' is the AGW port number to connect thru for g1tlh - connect agw 1 g1tlh - # you can leave this out if you call the script 'gb7dxm' - client gb7dxm ax25 - - - - - - - - - timeout 15 - connect telnet dirkl.tobit.co.uk - # tell GB7DJK-1 that it is connected to GB7DJK - # you can leave this out if you call this script 'gb7djk' - client gb7djk telnet - - - - - - Both these examples assume that everything is set up properly at the - other end. You will find other examples in the /spider/examples - directory. - - - - - 33..77.. SSttaarrttiinngg tthhee ccoonnnneeccttiioonn - - You start the connection, from within a sysop enabled cluster login, - by typing in the word _c_o_n_n_e_c_t followed by a script name like this .... - - - - G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1 - connection to GB7DJK-1 started - G0VGS de GB7MBC 13-Dec-1998 2043Z > - - - - - This will start a connection using the script called _g_b_7_d_j_k_-_1. You - can follow the connection by watching the term or console from where - you started _c_l_u_s_t_e_r_._p_l. From version 1.47 onwards, you will need to - set/debug connect first. You should see something like this ... - - - - <- D G1TLH connect gb7djk-1 - -> D G1TLH connection to GB7DJK-1 started - -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > - timeout set to 15 - CONNECT sort: telnet command: dirkl.tobit.co.uk - CHAT "login" -> "gb7djk" - received " - Red Hat Linux release 5.1 (Manhattan) - Kernel 2.0.35 on an i586 - " - received "login: " - sent "gb7djk" - CHAT "word" -> "gb7djk" - received "gb7djk" - received "Password: " - sent "gb7djk" - Connected to GB7DJK-1, starting normal protocol - <- O GB7DJK-1 telnet - -> B GB7DJK-1 0 - GB7DJK-1 channel func state 0 -> init - <- D GB7DJK-1 - <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 - <- D GB7DJK-1 PC38^GB7DJK-1^~ - <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime - 0 00:00^5447^~ - etc - - - - - - With later versions of Spider there is a set/login command for users. - This tells them when a user or node logs in or out. If you do not add - a line to your scripts after the final line (or before the client line - which should always be last if needed) then the login/logout - information will be sent to users _b_e_f_o_r_e the login actually completes. - This means if a node is unreachable, it will continue sending logins - and logouts to users even though it is not actually connecting. To - avoid this use the following line ... - - - - - - - In a script, this might look like ... - - - - timeout 35 - abort (Busy|Sorry|Fail) - connect telnet mary 3000 - - - - - - 33..88.. TTeellnneett eecchhoo - - Cluster links in particular suffer greatly from the presence of telnet - echo. This is caused by the telnet negotiation itself and can create - at worst severe loops. At best it creates unnecessary bandwidth and - large logfiles! There are things that can be done to limit this - problem but will not always work dependent on the route taken to - connect. - - - Telnet echo itself should only be a problem if the connection is being - made to the telnet port (23). This port uses special rules that - include echo negotiation. If the connection is to a different port, - such as 7300, this negotiation does not happen and therefore no echo - should be present. - - - Sometimes it is not possible to make a direct connection to another - node and this can cause problems. There is a way of trying to - suppress the telnet echo but this will not always work, unfortunately - it is difficult to be more specific. Here is an example of what I - mean ... - - - - timeout 35 - abort (Busy|Sorry|Fail) - connect telnet mary.lancs.ac.uk - - - - - So, the first connection is made by Spider. This is fine as Spider - uses the Net_Telnet script from within perl. This actually uses TCP - rather than TELNET so no negotiation will be done on the first - connection. Once connected to mary.lancs.ac.uk, the command is sent - to suppress echo. Now a telnet is made to a cluster node that is - accepting connections on port 23. The problem with this link is that - the negotiation is made by the remote machine, therefore you have no - control over it. The chances are that this link will create echo and - there will be no way you can stop it. - - - - 44.. AAuuttoommaattiinngg tthhiinnggss - - 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 and if connection scripts fail they have to be - started again manually too, not much use if you are not at the - console! So, in this section we will automate both. Firstly starting - the cluster. - - - 44..11.. AAuuttoossttaarrttiinngg tthhee cclluusstteerr - - This is not only a way to start the cluster automatically, it also - works as a watchdog, checking the sanity of DXSpider and respawning it - should it crash for any reason. Before doing the following, shutdown - the cluster as you did earlier. - - - Login as root and bring up the /etc/inittab file in your favourite - editor. Add the following lines to the file near the end ... - - - - ##Start DXSpider on bootup and respawn it should it crash - DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 - - - - - - This line works fine for RedHat distributions. It is also fine for - SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like - this ... - - - - DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 - - - - - - The line required for Slackware distributions is slightly different. - My thanks to Aurelio, PA3EZL for this information. - - - - DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7 - - - - - - This will automatically start DXSpider on tty7 (ALT-F7) on bootup and - restart it should it crash for any reason. - - - As root type the command _t_e_l_i_n_i_t _q. DXSpider should start up - immediately. You will see the output on tty7 and if you login as - _s_y_s_o_p you should find everything running nicely. - - - So far so good, now to automate script connections... - - - 44..22.. TThhee ccrroonnttaabb ffiillee - - Login as _s_y_s_o_p 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) - + 1. Hop control + Starting with version 1.13 there is simple hop control available on a + per node basis. Also it is possible to isolate a network completely so + that you get all the benefits of being on that network, but can't pass + on information from it to any other networks you may be connected to + (or vice versa). + 1.1. Basic hop control + In /spider/data you will find a file called hop_table.pl. This is the + file that controls your hop count settings. It has a set of default + hops on the various PC frames and also a set for each node you want to + alter the hops for. You may be happy with the default settings of + course, but this powerful tool can help to protect and improve the + network. The file will look something like this ... - # check every 10 minutes to see if gb7xxx is connected and if not - # start a connect job going - 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') - The callsign involved will be the callsign of the cluster node you are - going to connect to. This will now check every 10 minutes to see if - gb7xxx is connected, if it is then nothing will be done. If it is - not, then a connect attempt will be started. - There are probably lots of other things you could use this crontab - file for. If you want to know more about it, look at the DXSpider - website at the cron page where it is explained more fully. - 55.. HHoopp ccoonnttrrooll - Starting with version 1.13 there is simple hop control available on a - per node basis. Also it is possible to isolate a network completely so - that you get all the benefits of being on that network, but can't pass - on information from it to any other networks you may be connected to - (or vice versa). - 55..11.. BBaassiicc hhoopp ccoonnttrrooll - In /spider/data you will find a file called hop_table.pl. This is the - file that controls your hop count settings. It has a set of default - hops on the various PC frames and also a set for each node you want to - alter the hops for. You may be happy with the default settings of - course, but this powerful tool can help to protect and improve the - network. The file will look something like this ... @@ -1379,15 +389,15 @@ You can alter this file at any time, including whilst the cluster is - running. If you alter the file during runtime, the command _l_o_a_d_/_h_o_p_s + running. If you alter the file during runtime, the command load/hops will bring your changes into effect. - 55..22.. IIssoollaattiinngg nneettwwoorrkkss + 1.2. Isolating networks It is possible to isolate networks from each other on a "gateway" node - using the _s_e_t_/_i_s_o_l_a_t_e _<_n_o_d_e___c_a_l_l_> command. + using the set/isolate <node_call> command. The effect of this is to partition an isolated network completely from @@ -1431,14 +441,14 @@ There is a lot more on filtering in the next section. - 66.. FFiilltteerriinngg ((OOlldd SSttyyllee uuppttoo vv11..4444)) + 2. Filtering (Old Style upto v1.44) Filters can be set for spots, announcements and WWV. You will find the directories for these under /spider/filter. You will find some - examples in the directories with the suffix _._i_s_s_u_e. There are two + examples in the directories with the suffix .issue. There are two types of filter, one for incoming information and one for outgoing - information. Outgoing filters are in the form _C_A_L_L_S_I_G_N_._p_l and - incoming filters are in the form _i_n___C_A_L_L_S_I_G_N_._p_l. Filters can be set + information. Outgoing filters are in the form CALLSIGN.pl and + incoming filters are in the form in_CALLSIGN.pl. Filters can be set for both nodes and users. @@ -1446,7 +456,7 @@ elements delimited by commas. There can be many lines in the filter and they are read from the top by the program. When writing a filter you need to think carefully about just what you want to achieve. You - are either going to write a filter to _a_c_c_e_p_t or to _r_e_j_e_c_t. Think of a + are either going to write a filter to accept or to reject. Think of a filter as having 2 main elements. For a reject filter, you would have a line or multiple lines rejecting the things you do not wish to receive and then a default line accepting everything else that is not @@ -1489,7 +499,7 @@ following sections. - 66..11.. SSppoottss + 2.1. Spots The elements of the Spot filter are .... @@ -1623,7 +633,7 @@ - 66..22.. AAnnnnoouunncceemmeennttss + 2.2. Announcements @@ -1656,7 +666,7 @@ allow the posting of his Aurora Beacon. - 66..33.. WWWWVV + 2.3. WWV @@ -1693,9 +703,9 @@ will become more "comprehensive" in the near future. - 77.. FFiilltteerriinngg ((NNeeww SSttyyllee vv11..4455 aanndd llaatteerr)) + 3. Filtering (New Style v1.45 and later) - 77..11.. GGeenneerraall ffiilltteerr rruulleess + 3.1. 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 @@ -1706,7 +716,7 @@ There are 3 basic commands involved in setting and manipulating - filters. These are _a_c_c_e_p_t, _r_e_j_e_c_t and _c_l_e_a_r. First we will look + 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. @@ -1754,9 +764,9 @@ the same principles to all types of filter. - 77..22.. TTyyppeess ooff ffiilltteerr + 3.2. Types of filter - There are two main types of filter, _a_c_c_e_p_t or _r_e_j_e_c_t. You can use + There are two main types of filter, accept or reject. You can use either to achieve the result you want dependent on your own preference and which is more simple to do. It is pointless writing 8 lines of reject filters when 1 accept filter would do the same thing! Each @@ -1769,7 +779,7 @@ 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 - _a_c_c_e_p_t filter ... + accept filter ... @@ -1778,7 +788,7 @@ - then you will _O_N_L_Y get VHF spots _f_r_o_m or _t_o CQ zones 14, 15 and 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 ... @@ -1789,7 +799,7 @@ - Then you will get everything _E_X_C_E_P_T HF CW spots. You could make this + 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 ... @@ -1842,7 +852,7 @@ 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 _A_P_A_R_T from those in zones 14, 15 and 16 (either spotted there 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 ... @@ -1886,13 +896,13 @@ - 77..33.. FFiilltteerr ooppttiioonnss + 3.3. Filter options You can filter in several different ways. The options are listed in the various helpfiles for accept, reject and filter. - 77..44.. DDeeffaauulltt ffiilltteerrss + 3.4. Default filters Sometimes all that is needed is a general rule for node connects. This can be done with a node_default filter. This rule will always be @@ -1918,7 +928,7 @@ to add a rule for the hops for spots also. - 77..55.. AAddvvaanncceedd ffiilltteerriinngg + 3.5. Advanced filtering Once you are happy with the results you get, you may like to experiment. @@ -1938,9 +948,9 @@ 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 - _o_t_h_e_r_s _a_t _H_F_. _A_l_s_o _a_c_c_e_p_t _a_n_y_t_h_i_n_g _i_n _V_H_F _a_n_d _a_b_o_v_e _s_p_o_t_t_e_d _i_n _o_r _b_y - _o_p_e_r_a_t_o_r_s _i_n _t_h_e _z_o_n_e_s _1_4_, _1_5 _a_n_d _1_6. Each filter slot actually has a + 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. @@ -1954,9 +964,9 @@ - 88.. OOtthheerr ffiilltteerrss + 4. Other filters - 88..11.. FFiilltteerriinngg MMaaiill + 4.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 @@ -2018,9 +1028,9 @@ etc in a particular country. - 88..22.. FFiilltteerriinngg DDXX ccaalllloouuttss ((DDeepprriiccaatteedd)) + 4.2. Filtering DX callouts (Depricated) - _F_r_o_m _v_e_r_s_i_o_n _1_._4_7_, _t_h_i_s _m_e_t_h_o_d _i_s _r_e_p_l_a_c_e_d _b_y _t_h_e _c_o_m_m_a_n_d _s_e_t_/_b_a_d_d_x + From version 1.47, this method is replaced by the command set/baddx In the same way as mail, there are some types of spot we do not wish @@ -2072,9 +1082,9 @@ - 88..33.. FFiilltteerriinngg wwoorrddss ffrroomm tteexxtt ffiieellddss iinn AAnnnnoouunnccee,, TTaallkk aanndd DDXX ssppoottss + 4.3. Filtering words from text fields in Announce, Talk and DX spots - Create a file in /spider/data called _b_a_d_w_o_r_d_s. The format is quite + Create a file in /spider/data called badwords. The format is quite simple. Lines beginning with # are ignored so comments can be added. An example file is below ... @@ -2097,7 +1107,7 @@ load/badwords. - 99.. MMaaiill + 5. Mail DXSpider deals seamlessly with standard AK1A type mail. It supports both personal and bulletin mail and the sysop has additional commands @@ -2108,29 +1118,29 @@ will be queued until it has finished. The cluster mail is automatically deleted after 30 days unless the - sysop sets the "keep" flag using the _m_s_g command. + sysop sets the "keep" flag using the msg command. - 99..11.. PPeerrssoonnaall mmaaiill + 5.1. Personal mail - Personal mail is sent using the _s_p 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 _c_o_m_m_a_n_d _s_e_t + 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. - 99..22.. BBuulllleettiinn mmaaiill + 5.2. Bulletin mail - Bulletin mail is sent by using the _s_b command. This is one of the + 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 _s_p instead of _s_b and of course the message + 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 _m_s_g command. + the msg command. Bulletin addresses can be set using the Forward.pl file. - 99..33.. FFoorrwwaarrdd..ppll + 5.3. Forward.pl DXSpider receives all and any mail sent to it without any alterations needed in files. Because personal and bulletin mail are treated @@ -2224,9 +1234,9 @@ - 99..44.. TThhee mmssgg ccoommmmaanndd + 5.4. The msg command - The _m_s_g command is a very powerful and flexible tool for the sysop. + 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. @@ -2264,10 +1274,10 @@ user. - 99..55.. MMeessssaaggee ssttaattuuss + 5.5. Message status You can check on a message from within the cluster by using the - command _s_t_a_t_/_m_s_g. This will give you additional information on 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 ... @@ -2293,17 +1303,17 @@ - 99..66.. FFiilltteerriinngg mmaaiill + 5.6. Filtering mail - This is described in the section on _O_t_h_e_r _f_i_l_t_e_r_s so I will not + This is described in the section on Other filters so I will not duplicate it here. - 99..77.. DDiissttrriibbuuttiioonn lliissttss + 5.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 _d_i_s_t_r_o. You put + 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. @@ -2319,7 +1329,7 @@ list. - 99..88.. BBBBSS iinntteerrffaaccee + 5.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 @@ -2332,7 +1342,7 @@ using the Forward.pl file very carefully. - 1100.. DDaattaabbaasseess + 6. Databases Spider allows the creation of local or remote databases. It supports chained databases, allowing several different databases to be scanned @@ -2341,12 +1351,12 @@ database but will expand with time. - 1100..11.. CCrreeaattiinngg ddaattaabbaasseess + 6.1. Creating databases Creating a database could not be more simple. All the commands are - sent from the cluster prompt as the _s_y_s_o_p user. + sent from the cluster prompt as the sysop user. - To create a database you use the command _d_b_c_r_e_a_t_e. It can be used in + To create a database you use the command dbcreate. It can be used in 3 different ways like so .. @@ -2389,7 +1399,7 @@ chain can be a remote database. - 1100..22.. IImmppoorrttiinngg ddaattaabbaasseess + 6.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. @@ -2409,10 +1419,10 @@ does not exist. - 1100..33.. CChheecckkiinngg aavvaaiillaabbllee ddaattaabbaasseess + 6.3. Checking available databases Once a database is created, you will want to check that it has been - added. To do this use the _d_b_a_v_a_i_l command. This will output the + added. To do this use the dbavail command. This will output the available databases. For example ... @@ -2428,9 +1438,9 @@ - 1100..44.. LLooookkiinngg uupp ddaattaabbaasseess + 6.4. Looking up databases - To look for information in a defined database, simply use the _d_b_s_h_o_w + To look for information in a defined database, simply use the dbshow command, for example ... @@ -2443,7 +1453,7 @@ 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 - _s_h_o_w command like this ... + show command like this ... @@ -2454,9 +1464,9 @@ Now you can simply use show/buckmaster or an abreviation. - 1100..55.. RReemmoovviinngg ddaattaabbaasseess + 6.5. Removing databases - To delete an existing database you use the _d_b_r_e_m_o_v_e command. For + To delete an existing database you use the dbremove command. For example ... @@ -2472,9 +1482,9 @@ created from scratch if you still required it. - 1111.. IInnffoorrmmaattiioonn,, ffiilleess aanndd uusseeffuull pprrooggrraammss + 7. Information, files and useful programs - 1111..11.. MMOOTTDD + 7.1. MOTD One of the more important things a cluster sysop needs to do is to get information to his users. The simplest way to do this is to have a @@ -2485,7 +1495,7 @@ to the cluster. - 1111..22.. DDoowwnnttiimmee mmeessssaaggee + 7.2. Downtime message If for any reason the cluster is down, maybe for upgrade or maintenance but the machine is still running, a message can be sent to @@ -2496,13 +1506,13 @@ actually running. - 1111..33.. OOtthheerr tteexxtt mmeessssaaggeess + 7.3. Other text messages You can set other text messages to be read by the user if they input the file name. This could be for news items or maybe information for new users. To set this up, make a directory under /spider called - _p_a_c_k_c_l_u_s. Under this directory you can create files called _n_e_w_s or - _n_e_w_u_s_e_r for example. In fact you can create files with any names you + 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 .... @@ -2520,17 +1530,17 @@ - If the file they want to read is called _n_e_w_s. You could also set an - alias for this in the Alias file to allow them just to type _n_e_w_s + If the file they want to read is called news. You could also set an + alias for this in the Alias file to allow them just to type news You can also store other information in this directory, either directly or nested under directories. One use for this would be to store DX bulletins such as the OPDX bulletins. These can be listed and read by the user. To keep things tidy, make a directory under - /spider/packclus called _b_u_l_l_e_t_i_n. Now copy any OPDX or similar + /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 _s_h_o_w_/_f_i_l_e_s command with an extension for the bulletin + above using the show/files command with an extension for the bulletin directory you have just created, like this .... @@ -2552,11 +1562,11 @@ You can see that in the files area (basically the packclus directory) - there is a file called _n_e_w_s and a directory called _b_u_l_l_e_t_i_n. You can - also see that dates they were created. In the case of the file _n_e_w_s, + 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 _n_e_w_s you would simply issue the command .... + file called news you would simply issue the command .... @@ -2616,7 +1626,7 @@ The page length will of course depend on what you have it set to! - 1111..44.. TThhee AAlliiaasseess ffiillee + 7.4. The Aliases file You will find a file in /spider/cmd/ called Aliases. First, copy this file to /spider/local_cmd/Aliases and edit this file. You will see @@ -2780,7 +1790,7 @@ the results once you have set an alias. - 1111..55.. CCoonnssoollee..ppll + 7.5. 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 @@ -2792,13 +1802,13 @@ edit the file with your favourite editor. - 1111..66.. UUppddaattiinngg kkeepplleerr ddaattaa + 7.6. Updating kepler data Spider has a powerful and flexible show/satellite command. In order for this to be accurate, the kepler data has to be updated regularly. In general, this data is available as an email or via cluster mail. Updating it is simple. First you need to export the mail message as a - file. You do this with the _e_x_p_o_r_t command from the cluster prompt as + file. You do this with the export command from the cluster prompt as the sysop. For example ... @@ -2812,7 +1822,7 @@ /spider/perl directory. Now login to a VT as sysop and cd /spider/perl. There is a command in - the perl directory called _c_o_n_v_k_e_p_s_._p_l. All we need to do now is + the perl directory called convkeps.pl. All we need to do now is convert the file like so ... @@ -2836,9 +1846,9 @@ - 1111..77.. TThhee QQRRZZ ccaallllbbooookk + 7.7. The QRZ callbook - The command _s_h_/_q_r_z will only work once you have followed a few simple + The command sh/qrz will only work once you have followed a few simple steps. First you need to get a user ID and password from qrz.com. Simply go to the site and create one. Secondly you need to copy the file /spider/perl/Internet.pm to /spider/local and alter it to match @@ -2847,7 +1857,7 @@ proprieter of qrz.com for allowing this access. - 1122.. CCVVSS + 8. CVS CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your @@ -2878,7 +1888,7 @@ steps which are listed below ... - First login as the user _s_y_s_o_p. Next you need to connect to the CVS + First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... @@ -2953,7 +1963,7 @@ Now the magic part! From now on when you want to update, simply - connect to the Internet and then, as the user _s_y_s_o_p ... + connect to the Internet and then, as the user sysop ... @@ -2971,7 +1981,7 @@ You will find any changes documented in the /spider/Changes file. - 1133.. TThhee DDXXSSppiiddeerr ccoommmmaanndd sseett + 9. 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 @@ -2980,9 +1990,9 @@ is the permissions level needed to use the command. - 1133..11.. aacccceepptt//aannnnoouunnccee ((00)) + 9.1. accept/announce (0) - aacccceepptt//aannnnoouunnccee [[00--99]] <<ppaatttteerrnn>> Set an accept filter line for announce + accept/announce [0-9] <pattern> Set an accept filter line for announce Create an 'accept this announce' line for a filter. @@ -3042,9 +2052,9 @@ but this probably for advanced users... - 1133..22.. aacccceepptt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.2. accept/announce (extended for sysops) (8) - aacccceepptt//aannnnoouunnccee <<ccaallll>> [[iinnppuutt]] [[00--99]]<<ppaatttteerrnn>> Announce filter sysop + accept/announce <call> [input] [0-9]<pattern> Announce filter sysop version @@ -3061,9 +2071,9 @@ - 1133..33.. aacccceepptt//ssppoottss ((00)) + 9.3. accept/spots (0) - aacccceepptt//aannnnoouunnccee [[00--99]] <<ppaatttteerrnn>> Set an accept filter line for spots + accept/announce [0-9] <pattern> Set an accept filter line for spots Create an 'accept this spot' line for a filter. @@ -3122,9 +2132,9 @@ but this probably for advanced users... - 1133..44.. aacccceepptt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.4. accept/spots (extended for sysops) (8) - aacccceepptt//ssppoottss <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> Spot filter sysop version + 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 @@ -3142,9 +2152,9 @@ - 1133..55.. aacccceepptt//wwccyy ((00)) + 9.5. accept/wcy (0) - aacccceepptt//wwccyy [[00--99]] <<ppaatttteerrnn>> 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 @@ -3175,9 +2185,9 @@ See HELP FILTER for information. - 1133..66.. aacccceepptt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.6. accept/wcy (extended for sysops) (8) - aacccceepptt//wwccyy <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WCY filter sysop version + 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 @@ -3192,9 +2202,9 @@ - 1133..77.. aacccceepptt//wwwwvv ((00)) + 9.7. accept/wwv (0) - aacccceepptt//wwwwvv [[00--99]] <<ppaatttteerrnn>> 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 @@ -3232,9 +2242,9 @@ - 1133..88.. aacccceepptt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.8. accept/wwv (extended for sysops) (8) - aacccceepptt//wwwwvv <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WWV filter sysop version + 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 @@ -3252,18 +2262,18 @@ - 1133..99.. aannnnoouunnccee ((00)) + 9.9. announce (0) - aannnnoouunnccee <<tteexxtt>> 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 - 1133..1100.. aannnnoouunnccee ffuullll ((00)) + 9.10. announce full (0) - aannnnoouunnccee ffuullll <<tteexxtt>> Send an announcement cluster wide + announce full <text> Send an announcement cluster wide This command will send your announcement across the whole cluster @@ -3271,26 +2281,26 @@ - 1133..1111.. aannnnoouunnccee ssyyssoopp ((55)) + 9.11. announce sysop (5) - aannnnoouunnccee ssyyssoopp <<tteexxtt>> + announce sysop <text> Send an announcement to Sysops only - 1133..1122.. aapprrooppooss ((00)) + 9.12. apropos (0) - aapprrooppooss <<ssttrriinngg>> 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. - 1133..1133.. bbyyee ((00)) + 9.13. bye (0) - bbyyee Exit from the cluster + bye Exit from the cluster This will disconnect you from the cluster @@ -3298,9 +2308,9 @@ - 1133..1144.. ccaattcchhuupp ((55)) + 9.14. catchup (5) - ccaattcchhuupp <<nnooddee__ccaallll>> AAllll||[[<<mmssggnnoo>> ......]] Mark a message as sent + catchup <node_call> All|[<msgno> ...] Mark a message as sent When you send messages the fact that you have forwarded it to another @@ -3333,9 +2343,9 @@ Order is not important. - 1133..1155.. cclleeaarr//ssppoottss ((00)) + 9.15. clear/spots (0) - cclleeaarr//ssppoottss [[11||aallll]] 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 @@ -3382,9 +2392,9 @@ - 1133..1166.. ccoonnnneecctt ((55)) + 9.16. connect (5) - ccoonnnneecctt <<ccaallllssiiggnn>> Start a connection to another DX Cluster + connect <callsign> Start a connection to another DX Cluster Start a connection process that will culminate in a new connection to @@ -3394,21 +2404,21 @@ cluster <callsign>. - 1133..1177.. ddbbaavvaaiill ((00)) + 9.17. dbavail (0) - ddbbaavvaaiill 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. - 1133..1188.. ddbbccrreeaattee ((99)) + 9.18. dbcreate (9) - ddbbccrreeaattee <<nnaammee>> Create a database entry - ddbbccrreeaattee <<nnaammee>> cchhaaiinn <<nnaammee>> [[<<nnaammee>>....]] Create a chained database + dbcreate <name> Create a database entry + dbcreate <name> chain <name> [<name>..] Create a chained database entry - ddbbccrreeaattee <<nnaammee>> rreemmoottee <<nnooddee>> Create a remote database entry + dbcreate <name> remote <node> Create a remote database entry DBCREATE allows you to define a database in the system. It doesn't @@ -3471,9 +2481,9 @@ databases. See DBSHOW for generic database enquiry - 1133..1199.. ddbbiimmppoorrtt ((99)) + 9.19. dbimport (9) - ddbbiimmppoorrtt <<ddbbnnaammee>> Import AK1A data into a database + dbimport <dbname> Import AK1A data into a database If you want to import or update data in bulk to a database you can use @@ -3486,9 +2496,9 @@ oblast database held locally. - 1133..2200.. ddbbrreemmoovvee ((99)) + 9.20. dbremove (9) - ddbbrreemmoovvee <<ddbbnnaammee>> Delete a database + dbremove <dbname> Delete a database DBREMOVE will completely remove a database entry and also delete any @@ -3510,9 +2520,9 @@ You have been warned. - 1133..2211.. ddbbsshhooww ((00)) + 9.21. dbshow (0) - ddbbsshhooww <<ddbbnnaammee>> <<kkeeyy>> 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 @@ -3539,9 +2549,9 @@ - 1133..2222.. ddeebbuugg ((99)) + 9.22. debug (9) - ddeebbuugg Set the cluster program into debug mode + debug Set the cluster program into debug mode Executing this command will only have an effect if you are running the @@ -3558,16 +2568,16 @@ finished. - 1133..2233.. ddiirreeccttoorryy ((00)) + 9.23. directory (0) - ddiirreeccttoorryy List messages - ddiirreeccttoorryy oowwnn List your own messages - ddiirreeccttoorryy nneeww List all new messages - ddiirreeccttoorryy ttoo <<ccaallll>> List all messages to <call> - ddiirreeccttoorryy ffrroomm <<ccaallll>> List all messages from <call> - ddiirreeccttoorryy ssuubbjjeecctt <<ssttrriinngg>> List all messages with <string> in subject - ddiirreeccttoorryy <<nnnn>> List last <nn> messages - ddiirreeccttoorryy <<ffrroomm>>--<<ttoo>> List messages <from> message <to> message + directory List messages + directory own List your own messages + directory new List all new messages + directory to <call> List all messages to <call> + directory from <call> List all messages from <call> + directory subject <string> List all messages with <string> in subject + directory <nn> List last <nn> messages + directory <from>-<to> List messages <from> message <to> message List the messages in the messages directory. @@ -3602,23 +2612,23 @@ - 1133..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 9.24. directory (extended for sysops) (5) Works just like the user command except that sysops can see ALL messages. - 1133..2255.. ddiissccoonnnneecctt ((88)) + 9.25. disconnect (8) - ddiissccoonnnneecctt <<ccaallll>> [[<<ccaallll>> ......]] Disconnect a user or node + disconnect <call> [<call> ...] Disconnect a user or node Disconnect any <call> connected locally - 1133..2266.. ddxx ((00)) + 9.26. dx (0) - ddxx [[bbyy <<ccaallll>>]] <<ffrreeqq>> <<ccaallll>> <<rreemmaarrkkss>> 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 @@ -3658,9 +2668,9 @@ cluster. See SHOW/BANDS for more information. - 1133..2277.. eexxppoorrtt ((99)) + 9.27. export (9) - eexxppoorrtt <<mmssggnnoo>> <<ffiilleennaammee>> Export a message to a file + export <msgno> <filename> Export a message to a file Export a message to a file. This command can only be executed on a @@ -3676,9 +2686,9 @@ EXPORT 2345 /tmp/a - 1133..2288.. eexxppoorrtt__uusseerrss ((99)) + 9.28. export_users (9) - eexxppoorrtt__uusseerrss [[<<ffiilleennaammee>>]] Export the users database to ascii + export_users [<filename>] Export the users database to ascii Export the users database to a file in ascii format. If no filename is @@ -3694,9 +2704,9 @@ - 1133..2299.. ffoorrwwaarrdd//llaattlloonngg ((88)) + 9.29. forward/latlong (8) - ffoorrwwaarrdd//llaattlloonngg <<nnooddee__ccaallll>> Send latitude and longitude information to + forward/latlong <node_call> Send latitude and longitude information to another cluster @@ -3704,13 +2714,13 @@ 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 _s_e_t_/_d_x_g_r_i_d enabled. This could be a LOT of information though, + have set/dxgrid enabled. This could be a LOT of information though, so it is not recommended on slow links. - 1133..3300.. ffoorrwwaarrdd//ooppeerrnnaammee ((11)) + 9.30. forward/opername (1) - ffoorrwwaarrdd//ooppeerrnnaammee <<ccaallll>> Send out information on this <call> to all + forward/opername <call> Send out information on this <call> to all clusters @@ -3720,9 +2730,9 @@ available. - 1133..3311.. hheellpp ((00)) + 9.31. help (0) - hheellpp <<ccmmdd>> Get help on a command + help <cmd> Get help on a command All commands can be abbreviated, so SHOW/DX can be abbreviated to @@ -3733,9 +2743,9 @@ commands to look at with HELP. - 1133..3322.. iinniitt ((55)) + 9.32. init (5) - iinniitt <<nnooddee ccaallll>> Re-initialise a link to an AK1A compatible node + 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 @@ -3747,9 +2757,9 @@ Best of luck - you will need it. - 1133..3333.. kkiillll ((00)) + 9.33. kill (0) - kkiillll <<mmssggnnoo>> [[<<mmssggnnoo>> ....]] 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 @@ -3760,11 +2770,11 @@ - 1133..3344.. kkiillll ((55)) + 9.34. kill (5) - kkiillll <<mmssggnnoo>> [[<<mmssggnnoo>> ......]] Remove or erase a message from the system - kkiillll ffrroomm <<ccaallll>> Remove all messages from a callsign - kkiillll ttoo <<ccaallll>> Remove all messages to a callsign + 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 @@ -3773,9 +2783,9 @@ As a sysop you can kill any message on the system. - 1133..3355.. kkiillll ffuullll ((55)) + 9.35. kill full (5) - kkiillll ffuullll <<mmssggnnoo>> [[<<mmssggnnoo>>]] Delete a message from the whole cluster + kill full <msgno> [<msgno>] Delete a message from the whole cluster Delete a message (usually a 'bulletin') from the whole cluster system. @@ -3784,9 +2794,9 @@ same subject will be deleted. Beware! - 1133..3366.. lliinnkkss ((00)) + 9.36. links (0) - lliinnkkss 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 @@ -3794,9 +2804,9 @@ - 1133..3377.. llooaadd//aalliiaasseess ((99)) + 9.37. load/aliases (9) - llooaadd//aalliiaasseess Reload the command alias table + load/aliases Reload the command alias table Reload the /spider/cmd/Aliases file after you have editted it. You @@ -3805,9 +2815,9 @@ - 1133..3388.. llooaadd//bbaaddddxx ((99)) + 9.38. load/baddx (9) - llooaadd//bbaaddddxx Reload the bad DX table + load/baddx Reload the bad DX table Reload the /spider/data/baddx.pl file if you have changed it manually @@ -3815,9 +2825,9 @@ if spotted, will not be passed on. FR0G and TEST are classic examples. - 1133..3399.. llooaadd//bbaaddmmssgg ((99)) + 9.39. load/badmsg (9) - llooaadd//bbaaddmmssgg Reload the bad message table + load/badmsg Reload the bad message table Reload the /spider/msg/badmsg.pl file if you have changed it manually @@ -3826,9 +2836,9 @@ each message. If any of them match then that message is immediately deleted on receipt. - 1133..4400.. llooaadd//bbaaddwwoorrddss ((99)) + 9.40. load/badwords (9) - llooaadd//bbaaddwwoorrddss Reload the badwords file + load/badwords Reload the badwords file Reload the /spider/data/badwords file if you have changed it manually @@ -3840,18 +2850,18 @@ ignored. - 1133..4411.. llooaadd//bbaannddss ((99)) + 9.41. load/bands (9) - llooaadd//bbaannddss Reload the band limits table + 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. - 1133..4422.. llooaadd//ccmmdd__ccaacchhee ((99)) + 9.42. load/cmd_cache (9) - llooaadd//ccmmdd__ccaacchhee Reload the automatic command cache + load/cmd_cache Reload the automatic command cache Normally, if you change a command file in the cmd or local_cmd tree it @@ -3862,17 +2872,17 @@ was just after a cluster restart. - 1133..4433.. llooaadd//ffoorrwwaarrdd ((99)) + 9.43. load/forward (9) - llooaadd//ffoorrwwaarrdd Reload the msg forwarding routing table + 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. - 1133..4444.. llooaadd//mmeessssaaggeess ((99)) + 9.44. load/messages (9) - llooaadd//mmeessssaaggeess Reload the system messages file + load/messages Reload the system messages file If you change the /spider/perl/Messages file (usually whilst @@ -3883,18 +2893,18 @@ unknown message 'xxxx' in lang 'en' - 1133..4455.. llooaadd//pprreeffiixxeess ((99)) + 9.45. load/prefixes (9) - llooaadd//pprreeffiixxeess Reload the prefix table + 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. - 1133..4466.. mmeerrggee ((55)) + 9.46. merge (5) - mmeerrggee <<nnooddee>> [[<<nnoo ssppoottss>>//<<nnoo wwwwvv>>]] Ask for the latest spots and WWV + 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 @@ -3907,9 +2917,9 @@ data). - 1133..4477.. mmssgg ((99)) + 9.47. msg (9) - mmssgg <<ccmmdd>> <<mmssggnnoo>> [[ddaattaa ......]] Alter various message parameters + msg <cmd> <msgno> [data ...] Alter various message parameters Alter message parameters like To, From, Subject, whether private or @@ -3943,9 +2953,9 @@ This will display more information on the message than DIR does. - 1133..4488.. ppcc ((88)) + 9.48. pc (8) - ppcc <<ccaallll>> <<tteexxtt>> Send text (eg PC Protocol) to <call> + pc <call> <text> Send text (eg PC Protocol) to <call> Send some arbitrary text to a locally connected callsign. No @@ -3961,9 +2971,9 @@ pc G1TLH Try doing that properly!!! - 1133..4499.. ppiinngg ((11)) + 9.49. ping (1) - ppiinngg <<nnooddee>> Check the link quality between nodes + ping <node> Check the link quality between nodes his command allows you to send a frame to another cluster node on the @@ -3974,9 +2984,9 @@ - 1133..5500.. rrccmmdd ((11)) + 9.50. rcmd (1) - rrccmmdd <<nnooddee ccaallll>> <<ccmmdd>> Send a command to another DX cluster + rcmd <node call> <cmd> Send a command to another DX cluster This command allows you to send nearly any command to another DX @@ -3988,10 +2998,10 @@ whether you have permission to send this command at all. - 1133..5511.. rreeaadd ((00)) + 9.51. read (0) - rreeaadd Read the next unread personal message addressed to you - rreeaadd <<mmssggnnoo>> Read the specified message + 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 @@ -3999,17 +3009,17 @@ - 1133..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 9.52. read (extended for sysops) (5) - rreeaadd <<mmssggnnoo>> Read a message on the system + read <msgno> Read a message on the system As a sysop you may read any message on the system - 1133..5533.. rreejjeecctt//aannnnoouunnccee + 9.53. reject/announce - rreejjeecctt//aannnnoouunnccee [[00--99]] <<ppaatttteerrnn>> Set a reject filter for announce + reject/announce [0-9] <pattern> Set a reject filter for announce Create an 'reject this announce' line for a filter. @@ -4061,9 +3071,9 @@ but this probably for advanced users... - 1133..5544.. rreejjeecctt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.54. reject/announce (extended for sysops) (8) - rreejjeecctt//aannnnoouunnccee <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> Announce filter sysop + reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version @@ -4080,9 +3090,9 @@ - 1133..5555.. rreejjeecctt//ssppoottss ((00)) + 9.55. reject/spots (0) - rreejjeecctt//ssppoottss [[00--99]] <<ppaatttteerrnn>> Set a reject filter line for spots + reject/spots [0-9] <pattern> Set a reject filter line for spots Create a 'reject this spot' line for a filter. @@ -4141,9 +3151,9 @@ but this probably for advanced users... - 1133..5566.. rreejjeecctt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.56. reject/spots (extended for sysops) (8) - rreejjeecctt//ssppoottss <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> Reject spot filter sysop + reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop version @@ -4166,9 +3176,9 @@ - 1133..5577.. rreejjeecctt//wwccyy ((00)) + 9.57. reject/wcy (0) - rreejjeecctt//wwccyy [[00--99]] <<ppaatttteerrnn>> 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 @@ -4198,9 +3208,9 @@ See HELP FILTER for information. - 1133..5588.. rreejjeecctt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.58. reject/wcy (extended for sysops) (8) - rreejjeecctt//wwccyy <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WCY reject filter sysop + reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop version @@ -4210,9 +3220,9 @@ reject/wcy gb7djk all - 1133..5599.. rreejjeecctt//wwwwvv ((00)) + 9.59. reject/wwv (0) - rreejjeecctt//wwwwvv [[00--99]] <<ppaatttteerrnn>> 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 @@ -4250,9 +3260,9 @@ See HELP FILTER for information. - 1133..6600.. rreejjeecctt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 9.60. reject/wwv (extended for sysops) (8) - rreejjeecctt//wwwwvv <<ccaallll>> [[iinnppuutt]] [[00--99]] <<ppaatttteerrnn>> WWV reject filter sysop + reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop version @@ -4270,13 +3280,13 @@ - 1133..6611.. rreeppllyy ((00)) + 9.61. reply (0) - rreeppllyy Reply (privately) to the last message that you have read - rreeppllyy <<mmssggnnoo>> Reply (privately) to the specified message - rreeppllyy BB <<mmssggnnoo>> Reply as a Bulletin to the specified message - rreeppllyy NNOOPPrriivvaattee <<mmssggnnoo>> Reply as a Bulletin to the specified message - rreeppllyy RRRR <<mmssggnnoo>> Reply to the specified message with read receipt + 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 @@ -4288,13 +3298,13 @@ - 1133..6622.. sseenndd ((00)) + 9.62. send (0) - sseenndd <<ccaallll>> [[<<ccaallll>> ......]] Send a message to one or more callsigns - sseenndd RRRR <<ccaallll>> Send a message and ask for a read receipt - sseenndd CCOOPPYY <<mmssggnnoo>> <<ccaallll>> Send a copy of a message to someone - sseenndd PPRRIIVVAATTEE <<ccaallll>> Send a personal message - sseenndd NNOOPPRRIIVVAATTEE <<ccaallll>> Send a message to all stations + 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 @@ -4322,34 +3332,34 @@ is an alias for SEND PRIVATE - 1133..6633.. sseett//aaddddrreessss ((00)) + 9.63. set/address (0) - sseett//aaddddrreessss <<yyoouurr__aaddddrreessss>> Record your postal address + set/address <your_address> Record your postal address Literally, record your address details on the cluster. - 1133..6644.. sseett//aannnnoouunnccee ((00)) + 9.64. set/announce (0) - sseett//aannnnoouunnccee Allow announce messages + set/announce Allow announce messages Allow announce messages to arrive at your terminal. - 1133..6655.. sseett//aarrcclluusstteerr ((55)) + 9.65. set/arcluster (5) - sseett//aarrcclluusstteerr <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call an AR- + 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 - 1133..6666.. sseett//bbaaddddxx ((88)) + 9.66. set/baddx (8) - sseett//bbaaddddxx <<ccaallll>> Stop words we do not wish to see in the callsign + set/baddx <call> Stop words we do not wish to see in the callsign field of a dx spot being propagated @@ -4377,9 +3387,9 @@ - 1133..6677.. sseett//bbaaddnnooddee ((66)) + 9.67. set/badnode (6) - sseett//bbaaddnnooddee <<nnooddee__ccaallll>> Stop spots from this node_call being + set/badnode <node_call> Stop spots from this node_call being propagated @@ -4411,9 +3421,9 @@ FILTERing. - 1133..6688.. sseett//bbaaddssppootttteerr ((88)) + 9.68. set/badspotter (8) - sseett//bbaaddssppootttteerr <<ccaallll>> Stop spots from this callsign being propagated + set/badspotter <call> Stop spots from this callsign being propagated Setting a callsign as a 'badspotter' will prevent spots from this @@ -4445,69 +3455,69 @@ FILTERing. - 1133..6699.. sseett//bbeeeepp ((00)) + 9.69. set/beep (0) - sseett//bbeeeepp Add beeps to terminal messages + set/beep Add beeps to terminal messages Add a beep to DX and other terminal messages. - 1133..7700.. sseett//ccllxx ((55)) + 9.70. set/clx (5) - sseett//ccllxx <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call a CLX type + set/clx <node_call> [<node_call> ...] Make the node_call a CLX type node Set the node_call as a CLX type node - 1133..7711.. sseett//ddeebbuugg ((99)) + 9.71. set/debug (9) - sseett//ddeebbuugg <<nnaammee>> Add a debug level to the debug set + 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 _s_h_o_w_/_d_e_b_u_g command. + You can show what levels you are logging with the show/debug command. You can remove a debug level with unset/debug <name> - 1133..7722.. sseett//ddxx ((00)) + 9.72. set/dx (0) - sseett//ddxxAllow DX messages to arrive at your terminal + set/dxAllow DX messages to arrive at your terminal - You can stop DX messages with the _u_n_s_e_t_/_d_x command + You can stop DX messages with the unset/dx command - 1133..7733.. sseett//ddxxggrriidd ((00)) + 9.73. set/dxgrid (0) - sseett//ddxxggrriiddAllow 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 _u_n_s_e_t_/_d_x_g_r_i_d command + end of a DX spot. If this is the case, use the unset/dxgrid command to remove the grid squares. - 1133..7744.. sseett//ddxxnneett ((55)) + 9.74. set/dxnet (5) - sseett//ddxxnneett <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call a DXNet + set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet type node Set the node_call as a DXNet type node - 1133..7755.. sseett//eecchhoo ((00)) + 9.75. set/echo (0) - sseett//eecchhoo Make the cluster echo your input + set/echo Make the cluster echo your input If you are connected via a telnet session, different implimentations @@ -4515,27 +3525,27 @@ 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 _u_n_s_e_t_/_e_c_h_o command + 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. - 1133..7766.. sseett//hheerree ((00)) + 9.76. set/here (0) - sseett//hheerree 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 - _u_n_s_e_t_/_h_e_r_e command to let people know you are away. This simply puts + unset/here command to let people know you are away. This simply puts brackets around your callsign to indicate you are not available. - 1133..7777.. sseett//hhoommeennooddee ((00)) + 9.77. set/homenode (0) - sseett//hhoommeennooddee <<nnooddee__ccaallll>> Set your home cluster + set/homenode <node_call> Set your home cluster Tell the cluster system where you normally connect to. Any Messages @@ -4552,9 +3562,9 @@ - 1133..7788.. sseett//hhooppss ((88)) + 9.78. set/hops (8) - sseett//hhooppss <<nnooddee__ccaallll>> aannnn||ssppoottss||wwwwvv||wwccyy <<nn>> Set hop count + 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. @@ -4575,9 +3585,9 @@ creates a filter and works in conjunction with the filter system. - 1133..7799.. sseett//iissoollaattee ((99)) + 9.79. set/isolate (9) - sseett//iissoollaattee <<nnooddee ccaallll>> Isolate a node from the rest of the network + 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 @@ -4593,22 +3603,22 @@ You can remove the isolation with the command unset/isolate. - 1133..8800.. sseett//llaanngguuaaggee ((00)) + 9.80. set/language (0) - sseett//llaanngguuaaggee <<llaanngguuaaggee>> 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 _e_n (English) and _n_l (Dutch). + Currently the languages available are en (English) and nl (Dutch). - 1133..8811.. sseett//llooccaattiioonn ((00)) + 9.81. set/location (0) - sseett//llooccaattiioonn <<llaatt aanndd lloonngg>> 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 _s_e_t_/_q_r_a command which will do the conversion for you. + the set/qra command which will do the conversion for you. @@ -4618,9 +3628,9 @@ - 1133..8822.. sseett//ssyyss__llooccaattiioonn ((99)) + 9.82. set/sys_location (9) - sseett//ssyyss__llooccaattiioonn <<llaatt && lloonngg>> Set your cluster latitude and longitude + set/sys_location <lat & long> Set your cluster latitude and longitude In order to get accurate headings and such like you must tell the @@ -4636,28 +3646,28 @@ - 1133..8833.. sseett//llooggiinniinnffoo ((00)) + 9.83. set/logininfo (0) - sseett//llooggiinniinnffoo 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 _u_n_s_e_t_/_l_o_g_i_n_i_n_f_o command. + You can stop these messages by using the unset/logininfo command. - 1133..8844.. sseett//lloocckkoouutt ((99)) + 9.84. set/lockout (9) - sseett//lloocckkoouutt <<ccaallll>> Stop a callsign connecting to the cluster + set/lockout <call> Stop a callsign connecting to the cluster - You can show who is locked out with the _s_h_o_w_/_l_o_c_k_o_u_t command. To - allow the user to connect again, use the _u_n_s_e_t_/_l_o_c_k_o_u_t command. + You can show who is locked out with the show/lockout command. To + allow the user to connect again, use the unset/lockout command. - 1133..8855.. sseett//nnaammee ((00)) + 9.85. set/name (0) - sseett//nnaammee <<yyoouurr__nnaammee>> Set your name + set/name <your_name> Set your name Tell the cluster what your name is, eg:- @@ -4670,9 +3680,9 @@ - 1133..8866.. sseett//nnooddee ((99)) + 9.86. set/node (9) - sseett//nnooddee <<ccaallll>> [[<<ccaallll>> ......]] Make the callsign an AK1A cluster + 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 @@ -4692,12 +3702,12 @@ - To see what your nodes are set to, use the _s_h_o_w_/_n_o_d_e_s command. + To see what your nodes are set to, use the show/nodes command. - 1133..8877.. sseett//oobbssccoouunntt ((99)) + 9.87. set/obscount (9) - sseett//oobbssccoouunntt <<ccoouunntt>> <<nnooddee ccaallll>> Set the 'pump-up' obsolescence + set/obscount <count> <node call> Set the 'pump-up' obsolescence counter @@ -4716,9 +3726,9 @@ minutes, it is disconnected. - 1133..8888.. sseett//ppaaggee ((00)) + 9.88. set/page (0) - sseett//ppaaggee <<nn>> 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 @@ -4737,9 +3747,9 @@ - 1133..8899.. sseett//ppaasssswwoorrdd ((99)) + 9.89. set/password (9) - sseett//ppaasssswwoorrdd <<ccaallllssiiggnn>> <<ssttrriinngg>> Set a users password + set/password <callsign> <string> Set a users password The password for a user can only be set by a full sysop. The string @@ -4750,9 +3760,9 @@ - 1133..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) + 9.90. set/pinginterval (9) - sseett//ppiinnggiinntteerrvvaall <<ttiimmee>> <<nnooddee ccaallll>> Set the ping time to neighbouring + set/pinginterval <time> <node call> Set the ping time to neighbouring nodes @@ -4771,9 +3781,9 @@ for more information. - 1133..9911.. sseett//pprriivviilleeggee ((99)) + 9.91. set/privilege (9) - sseett//pprriivviilleeggee <<nn>> <<ccaallll>> [[<<ccaallll>> ......]] Set the privilege level on a + set/privilege <n> <call> [<call> ...] Set the privilege level on a call @@ -4797,23 +3807,23 @@ connection your privilege will automatically be set to 0. - 1133..9922.. sseett//ssppiiddeerr ((55)) + 9.92. set/spider (5) - sseett//ssppiiddeerr <<nnooddee__ccaallll>> [[<<nnooddee__ccaallll>> ......]] Make the node_call a DXSpider + set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider type node Set the node_call as a DXSpider type node - 1133..9933.. sseett//ssyyss__qqrraa ((99)) + 9.93. set/sys_qra (9) - sseett//ssyyss__qqrraa <<llooccaattoorr>> Set your cluster QRA locator + set/sys_qra <locator> Set your cluster QRA locator - 1133..9944.. sseett//qqrraa ((00)) + 9.94. set/qra (0) - sseett//qqrraa <<llooccaattoorr>> Set your QRA locator + set/qra <locator> Set your QRA locator Tell the system what your QRA (or Maidenhead) locator is. If you have @@ -4828,9 +3838,9 @@ - 1133..9955.. sseett//qqtthh ((00)) + 9.95. set/qth (0) - sseett//qqtthh <<yyoouurr QQTTHH>> Set your QTH + set/qth <your QTH> Set your QTH Tell the system where your are. For example:- @@ -4843,79 +3853,79 @@ - 1133..9966.. sseett//ttaallkk ((00)) + 9.96. set/talk (0) - sseett//ttaallkk 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 _u_n_s_e_t_/_t_a_l_k command. + talks with the unset/talk command. - 1133..9977.. sseett//wwccyy ((00)) + 9.97. set/wcy (0) - sseett//wwccyy 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 _u_n_s_e_t_/_w_c_y command. + WCY messages with the unset/wcy command. - 1133..9988.. sseett//wwwwvv ((00)) + 9.98. set/wwv (0) - sseett//wwwwvv 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 _u_n_s_e_t_/_w_w_v command. + WWV messages with the unset/wwv command. - 1133..9999.. sseett//wwxx ((00)) + 9.99. set/wx (0) - sseett//wwxx 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 _u_n_s_e_t_/_w_x command. + WX messages with the unset/wx command. - 1133..110000.. sshhooww//bbaaddddxx ((11)) + 9.100. show/baddx (1) - sshhooww//bbaaddddxxShow all the bad dx calls in the system + 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. - 1133..110011.. sshhooww//bbaaddnnooddee ((66)) + 9.101. show/badnode (6) - sshhooww//bbaaddnnooddee Show all the bad nodes in the system + 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. - 1133..110022.. sshhooww//bbaaddssppootttteerr ((11)) + 9.102. show/badspotter (1) - sshhooww//bbaaddssppootttteerr Show all the bad spotters in the system + 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. - 1133..110033.. sshhooww//ccoonnffiigguurraattiioonn ((00)) + 9.103. show/configuration (0) - sshhooww//ccoonnffiigguurraattiioonn [[<<nnooddee>>]] 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 _n_o_d_e, you can + 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 @@ -4923,27 +3933,27 @@ BE WARNED: the list that is returned can be VERY long - 1133..110044.. sshhooww//ccoonnffiigguurraattiioonn//nnooddee ((00)) + 9.104. show/configuration/node (0) - sshhooww//ccoonnffiigguurraattiioonn//nnooddee Show all the nodes connected + show/configuration/node Show all the nodes connected Show all the nodes connected locally and the nodes they have connected. - 1133..110055.. sshhooww//ccoonnnneecctt ((11)) + 9.105. show/connect (1) - sshhooww//ccoonnnneecctt Show all the active connections + 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. - 1133..110066.. sshhooww//ddaattee ((00)) + 9.106. show/date (0) - sshhooww//ddaattee [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show the local time + show/date [<prefix>|<callsign>] Show the local time This is very nearly the same as SHOW/TIME, the only difference the @@ -4954,17 +3964,17 @@ including DST) at the prefixes or callsigns that you specify. - 1133..110077.. sshhooww//ddeebbuugg ((99)) + 9.107. show/debug (9) - sshhooww//ddeebbuugg Show what levels of debug you are logging + show/debug Show what levels of debug you are logging - The levels can be set with _s_e_t_/_d_e_b_u_g + The levels can be set with set/debug - 1133..110088.. sshhooww//ddxx ((00)) + 9.108. show/dx (0) - sshhooww//ddxx [[ooppttiioonnss]] 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 @@ -5026,9 +4036,9 @@ - 1133..110099.. sshhooww//ddxxcccc ((00)) + 9.109. show/dxcc (0) - sshhooww//ddxxcccc <<pprreeffiixx>> 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 @@ -5047,9 +4057,9 @@ - 1133..111100.. sshhooww//ffiilleess ((00)) + 9.110. show/files (0) - sshhooww//ffiilleess [[<<ffiilleeaarreeaa>> [[<<ssttrriinngg>>]]]] List the contents of a filearea + show/files [<filearea> [<string>]] List the contents of a filearea SHOW/FILES on its own will show you a list of the various fileareas @@ -5080,26 +4090,26 @@ - 1133..111111.. sshhooww//ffiilltteerr ((00)) + 9.111. show/filter (0) - sshhooww//ffiilltteerr 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. - 1133..111122.. sshhooww//ffiilltteerr ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 9.112. show/filter (extended for sysops) (5) - sshhooww//ffiilltteerr <<ccaallllssiiggnn>> Show the filters set by <callsign> + show/filter <callsign> Show the filters set by <callsign> A sysop can look at any filters that have been set. - 1133..111133.. sshhooww//hhooppss ((88)) + 9.113. show/hops (8) - sshhooww//hhooppss <<nnooddee__ccaallll>> [[aannnn||ssppoottss||wwccyy||wwwwvv||]] Show the hop counts for a + show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node @@ -5108,26 +4118,26 @@ the categories will be listed. - 1133..111144.. sshhooww//iissoollaattee ((11)) + 9.114. show/isolate (1) - sshhooww//iissoollaattee Show a list of isolated nodes + show/isolate Show a list of isolated nodes Show which nodes are currently set to be isolated. - 1133..111155.. sshhooww//lloocckkoouutt ((99)) + 9.115. show/lockout (9) - sshhooww//lloocckkoouutt Show a list of excluded callsigns + 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 _s_e_t_/_l_o_c_k_o_u_t command + cluster locally with the set/lockout command - 1133..111166.. sshhooww//lloogg ((88)) + 9.116. show/log (8) - sshhooww//lloogg [[<<ccaallllssiiggnn>>]] Show excerpts from the system log + show/log [<callsign>] Show excerpts from the system log This command outputs a short section of the system log. On its own it @@ -5135,9 +4145,9 @@ show output from the log associated with that callsign. - 1133..111177.. sshhooww//mmoooonn ((00)) + 9.117. show/moon (0) - sshhooww//mmoooonn [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show moon rise and set times + show/moon [<prefix>|<callsign>] Show moon rise and set times Show the Moon rise and set times for a (list of) prefixes or @@ -5165,9 +4175,9 @@ - 1133..111188.. sshhooww//mmuuff ((00)) + 9.118. show/muf (0) - sshhooww//mmuuff <<pprreeffiixx>> [[<<hhoouurrss>>]][[lloonngg]] Show the likely propagation to + show/muf <prefix> [<hours>][long] Show the likely propagation to <prefix> @@ -5256,9 +4266,9 @@ terrible accurate, but it is included for completeness. - 1133..111199.. sshhooww//nnooddee ((11)) + 9.119. show/node (1) - sshhooww//nnooddee [[<<nnooddee__ccaallll>> ......]] Show the type and version number of nodes + 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 @@ -5266,9 +4276,9 @@ the non-user callsigns known to the system will be displayed. - 1133..112200.. sshhooww//pprreeffiixx ((00)) + 9.120. show/prefix (0) - sshhooww//pprreeffiixx <<ccaallllssiiggnn>> Interrogate the prefix database + show/prefix <callsign> Interrogate the prefix database This command takes the <callsign> (which can be a full or partial @@ -5278,9 +4288,9 @@ See also SHOW/DXCC - 1133..112211.. sshhooww//pprrooggrraamm ((55)) + 9.121. show/program (5) - sshhooww//pprrooggrraamm Show the locations of all the included program modules + show/program Show the locations of all the included program modules Show the name and location where every program module was load from. @@ -5288,10 +4298,10 @@ from. - 1133..112222.. sshhooww//qqrraa ((00)) + 9.122. show/qra (0) - sshhooww//qqrraa <<llooccaattoorr>> [[<<llooccaattoorr>>]] Show the distance between locators - sshhooww//qqrraa <<llaatt>> <<lloonngg>> Convert latitude and longitude to a locator + 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 @@ -5324,9 +4334,9 @@ - 1133..112233.. sshhooww//qqrrzz ((00)) + 9.123. show/qrz (0) - sshhooww//qqrrzz <<ccaallllssiiggnn>> 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 @@ -5334,9 +4344,9 @@ provided for users of this software by http://www.qrz.com - 1133..112244.. sshhooww//rroouuttee ((00)) + 9.124. show/route (0) - sshhooww//rroouuttee <<ccaallllssiiggnn>> 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 @@ -5350,9 +4360,9 @@ - 1133..112255.. sshhooww//ssaatteelllliittee ((00)) + 9.125. show/satellite (0) - sshhooww//ssaatteelllliittee <<nnaammee>> [[<<hhoouurrss>> <<iinntteerrvvaall>>]] Show satellite tracking + show/satellite <name> [<hours> <interval>] Show satellite tracking data @@ -5383,9 +4393,9 @@ - 1133..112266.. sshhooww//ssuunn ((00)) + 9.126. show/sun (0) - sshhooww//ssuunn [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show sun rise and set times + show/sun [<prefix>|<callsign>] Show sun rise and set times Show the sun rise and set times for a (list of) prefixes or callsigns, @@ -5410,9 +4420,9 @@ - 1133..112277.. sshhooww//ttiimmee ((00)) + 9.127. show/time (0) - sshhooww//ttiimmee [[<<pprreeffiixx>>||<<ccaallllssiiggnn>>]] Show the local time + show/time [<prefix>|<callsign>] Show the local time If no prefixes or callsigns are given then this command returns the @@ -5421,20 +4431,20 @@ including DST) at the prefixes or callsigns that you specify. - 1133..112288.. sshhooww//wwccyy ((00)) + 9.128. show/wcy (0) - sshhooww//wwccyy Show the last 10 WCY broadcasts - sshhooww//wwccyy <<nn>> Show the last <n> WCY broadcasts + 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 - 1133..112299.. sshhooww//wwwwvv ((00)) + 9.129. show/wwv (0) - sshhooww//wwwwvv Show the last 10 WWV broadcasts - sshhooww//wwwwvv <<nn>> Show the last <n> WWV broadcasts + 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 @@ -5442,18 +4452,18 @@ - 1133..113300.. sshhuuttddoowwnn ((55)) + 9.130. shutdown (5) - sshhuuttddoowwnn Shutdown the cluster + 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. - 1133..113311.. ssppooooff ((99)) + 9.131. spoof (9) - ssppooooff <<ccaallllssiiggnn>> <<ccoommmmaanndd>> Run commands as another user + spoof <callsign> <command> Run commands as another user This is a very simple yet powerful command for the sysop. It allows @@ -5462,9 +4472,9 @@ like home_node for example. - 1133..113322.. ssttaatt//ddbb ((55)) + 9.132. stat/db (5) - ssttaatt//ddbb <<ddbbnnaammee>> Show the status of a database + stat/db <dbname> Show the status of a database Show the internal status of a database descriptor. @@ -5476,9 +4486,9 @@ - 1133..113333.. ssttaatt//cchhaannnneell ((55)) + 9.133. stat/channel (5) - ssttaatt//cchhaannnneell <<ccaallllssiiggnn>> Show the status of a channel on the cluster + stat/channel <callsign> Show the status of a channel on the cluster Show the internal status of the channel object either for the channel @@ -5487,9 +4497,9 @@ Only the fields that are defined (in perl term) will be displayed. - 1133..113344.. ssttaatt//mmssgg ((55)) + 9.134. stat/msg (5) - ssttaatt//mmssgg <<mmssggnnoo>> Show the status of a message + stat/msg <msgno> Show the status of a message This command shows the internal status of a message and includes @@ -5497,9 +4507,9 @@ etc etc. - 1133..113355.. ssttaatt//uusseerr ((55)) + 9.135. stat/user (5) - ssttaatt//uusseerr <<ccaallllssiiggnn>> Show the full status of a user + stat/user <callsign> Show the full status of a user Shows the full contents of a user record including all the secret @@ -5508,9 +4518,9 @@ Only the fields that are defined (in perl term) will be displayed. - 1133..113366.. ssyyssoopp ((00)) + 9.136. sysop (0) - ssyyssoopp 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 @@ -5547,11 +4557,11 @@ case sensitive. - 1133..113377.. ttaallkk ((00)) + 9.137. talk (0) - ttaallkk <<ccaallllssiiggnn>> Enter talk mode with <callsign> - ttaallkk <<ccaallllssiiggnn>> <<tteexxtt>> Send a text message to <callsign> - ttaallkk <<ccaallllssiiggnn>> >> <<nnooddee__ccaallll>> [[<<tteexxtt>>]] Send a text message to + 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> @@ -5598,9 +4608,9 @@ - 1133..113388.. ttyyppee ((00)) + 9.138. type (0) - ttyyppee <<ffiilleeaarreeaa>>//<<nnaammee>> 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 @@ -5617,28 +4627,28 @@ content. - 1133..113399.. wwhhoo ((00)) + 9.139. who (0) - wwhhoo 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 - 1133..114400.. wwxx ((00)) + 9.140. wx (0) - wwxx <<tteexxtt>> Send a weather message to local users - wwxx ffuullll <<tteexxtt>> Send a weather message to all cluster users + 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 - 1133..114411.. wwxx ((eennhhaanncceedd ffoorr ssyyssooppss)) ((55)) + 9.141. wx (enhanced for sysops) (5) - wwxx ssyyssoopp <<tteexxtt>> Send a weather message to other clusters only + wx sysop <text> Send a weather message to other clusters only Send a weather message only to other cluster nodes and not to general diff --git a/txt/installation.txt b/txt/installation.txt new file mode 100644 index 00000000..b816e4f5 --- /dev/null +++ b/txt/installation.txt @@ -0,0 +1,1518 @@ + The DXSpider Installation Manual v1.47 + Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS, + (ianmaude@btinternet.com) + + + A reference for SysOps of the DXSpider DXCluster program. + ______________________________________________________________________ + + Table of Contents + + + 1. Linux Installation (Original version by Iain Philipps, G0RDI) + + 1.1 Introduction + 1.2 Preparation + 1.3 Installing the software + 1.4 Setting callsigns etc + 1.5 Starting up for the first time + 1.6 The Client program + + 2. Linux quick installation guide + + 3. Configuration + + 3.1 Allowing ax25 connects from users + 3.2 Allowing telnet connects from users + 3.3 Setting up telnet connects (from 1.47 onwards) + 3.4 Setting up for AGW Engine (1.47 onwards) + 3.5 Setting up node connects + 3.6 Connection scripts + 3.7 Starting the connection + 3.8 Telnet echo + 3.9 Autostarting the cluster + + 4. Microsoft Windows Installation + + 4.1 Introduction + 4.2 The requirements + 4.3 The system + 4.4 Perl + 4.5 Additional packages + 4.6 Getting Spider + + 5. Installing the software + + 5.1 The AGW packet engine + 5.2 Setting up the initial user files + 5.3 Incoming telnets + 5.4 Connecting to other clusters + + 6. General Information + + 6.1 The crontab file + + + ______________________________________________________________________ + + 1. Linux Installation (Original version by Iain Philipps, G0RDI) + + 1.1. Introduction + + This section describes the installation of DX Spider v1.47 on a RedHat + Linux Distribution. Wherever possible I will try to include + differences for other distributions. I do not intend to try and cover + the installation of Linux or the setup of the AX25 utilities. If you + need help on this then read Iains original installation guide that + comes with the Spider distribution. + + + I am assuming a general knowledge of Linux and its commands. You + should know how to use tar and how to edit files using your favourite + editor. + + + The crucial ingredient for all of this is Perl. Earlier versions of + Spider required perl 5.004, however it is now STRONGLY recommended + that you use at least version 5.005_03 as this is the version being + used in the development of Spider. + + + In addition to the standard Red Hat distribution you will require the + following modules from http://www.cpan.org/CPAN.html ... + + + + o Data-Dumper-2.101.tar.gz + + o TimeDate-1.10.tar.gz + + o IO-1.20.tar.gz (for perl 5.00403 and lower) + + o Net-Telnet-3.02.tar.gz + + o Curses-1.05.tar.gz + + o Time-HiRes-01.20.tar.gz + + + Do get the latest versions of these packages and install them but use + the above list as the earliest versions usable. + + + 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.47 for this section but of course you would use the latest + version. + + + Login as root and create a user to run the cluster under. UNDER NO + CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use the name + sysop. You can call it anything you wish. Depending on your security + requirements you may wish to use an existing user, however this is + your own choice. + + + + + # adduser -m sysop + + + + + + Now set a password for the user ... + + + + + + + # passwd sysop + # New UNIX password: + # Retype new UNIX password: + passwd: all authentication tokens updated successfully + + + + + + 1.3. Installing the software + + Now to unpack the DX Spider distribution, set symbolic links and group + permissions. Copy the tarball to /home/sysop and do the following. + + + + # cd ~sysop + # tar xvfz spider-1.47.tar.gz + # ln -s ~sysop/spider /spider + # groupadd -g 251 spider (or another number) + + + + + If you do not have the command groupadd available to you simply add a + line in /etc/group by hand. + + + + # vi /etc/group (or your favorite editor) + + + + + You also need to add some others to the group, including your own + callsign (this will be used as an alias) and root. The finished line + in /etc/group should look something like this + + spider:x:251:sysop,g0vgs,root + + + The next step is to set the permissions on the Spider directory tree + and files .... + + + + # chown -R sysop.spider spider + # find . -type d -exec chmod 2775 {} \; + # find . -type f -exec chmod 775 {} \; + + + + + + This last step allows various users of the group spider to have write + access to all the directories. This is not really needed just yet but + will be useful when web interfaces start to appear. + + + Finally, you need to fix the permissions on the ax25_call and + netrom_call programs. Check where they are with the locate command + and alter the permissions with the chmod command like this .. + + + + + # chown root ax25_call netrom_call + # chmod 4775 ax25_call netrom_call + + + + + + 1.4. Setting callsigns etc + + Now login to your machine as the user you created earlier. In my case + that user is called sysop. Once logged in, issue the following + commands .... + + + + $ cd /spider + $ mkdir local + $ mkdir local_cmd + $ cp perl/DXVars.pm.issue local/DXVars.pm + $ cd local + $ vi DXVars.pm (or your favourite editor) + + + + + + Using the distributed DXVars.pm as a a template, set your cluster + callsign, sysop callsign and other user info to suit your own + environment. Note that this a perl file which will be parsed and + executed as part of the cluster. If you get it wrong then perl will + complain when you start the cluster process. It is important only to + alter the text of any section. Some of the lines look a little odd. + Take this line for example .... + + $myemail = "ianmaude\@btinternet.com"; + + + There appears to be an extra slash in there. However this has to be + there for the file to work so leave it in. + + + PLEASE USE CAPITAL LETTERS FOR CALLSIGNS + + + DON'T alter any file in /spider/perl, they are overwritten with every + release. Any files or commands you place in /spider/local or + /spider/local_cmd will automagically be used in preference to the ones + in /spider/perl EVEN while the cluster is running! + + + Save the new file and change directory to ../perl .... + + + + $ cd ../perl + + + + + + Now type the following command which creates the basic user file with + you as the sysop. + + + + + $ ./create_sysop.pl + + + + + + 1.5. Starting up for the first time + + We can now bring spider up for the first time and see if all is well + or not! It should look something like this ... + + + + $ ./cluster.pl + DXSpider DX Cluster Version 1.47 + Copyright (c) 1998 Dirk Koopman G1TLH + loading prefixes ... + loading band data ... + loading user file system ... + starting listener ... + reading existing message headers + reading cron jobs + orft we jolly well go ... + + + + + + If all is well then login on another term or console as sysop and cd + to /spider/src. Now issue the following command ... + + + + $ ./client + + + + + + This should log you into the cluster as the sysop under the alias + callsign we set earlier. In this case the callsign is G0VGS. The + cluster callsign is set in the DXVars.pm file in /spider/local. In + this case we will assume that this was set as GB7MBC. You should + therefore see this when you login .... + + + + G0VGS de GB7MBC 19-Nov-1999 2150Z > + + + + + If you do, congratulations! If not, look over the instructions again, + you have probably missed something out. You can shut spider down + again with the command .... + + + + shutdown + + + + + + and both the cluster and the client should return to Linux prompts. + + 1.6. The Client program + + In earlier versions of Spider, all the processes were Perl scripts. + This was fine but with a lot of users your computer memory would soon + be used up. To combat this a new client was written in "C". This + client only works for incoming connects at the moment. Before you can + use it though it has to be "made". CD to /spider/src and type make. + You should see the output on your screen and hopefully now have a + small C program called client. Leave it in this directory. + + + + 2. Linux quick installation guide + + This section is designed for experienced Spider sysops who want to + install Spider from scratch. It is simply a check list of things that + need to be done without any explanations. The name in brackets at the + end of each line is the user that should be doing that process. + + + o Login as root + + o Get the additional CPAN modules and install them (root) + + o Create the "sysop" user and set a password (root) + + o Put the Spider tarball in sysop and untar it (root) + + o ln -s sysop/spider /spider (root) + + o groupadd -g 251 spider (root) + + o Add any more users you need to the group entry in /etc/group (root) + + o Set the permissions on the spider tree (root) + + o Fix permissions on ax25_call and netrom_call (root) + + o Login as the sysop user + + o cd to /spider (sysop) + + o mkdir local (sysop) + + o mkdir local_cmd (sysop) + + o cp perl/DXVars.pm.issue local/DXVars.pm (sysop) + + o cd to /spider/local and edit DXVars to set your details (sysop) + + o cd ../perl (sysop) + + o ./create_sysop.pl (sysop) + + o ./cluster.pl (sysop) + + Spider should now be running and you should be able to login using the + client program. + + + o Login as root + + o Enter the correct line in ax25d.conf (root) + + o Enter the correct line in /etc/services (root) + + o Enter the correct line in /etc/inetd.conf (root) + + o killall -HUP inetd (root) + + Spider should now be able to accept logins via telnet, netrom and + ax25. + + + o Login as sysop + + o Start the cluster (sysop) + + o set/node and type for links (sysop) + + o Write any connect scripts (sysop) + + o Edit /spider/crontab as required (sysop) + + o Edit any other files as necessary (sysop) + + o Set filters, hops and forwarding files (sysop) + + o Login as root + + o Enter the correct line in /etc/inittab (root) + + + 3. Configuration + + 3.1. Allowing ax25 connects from users + + As stated previously, the aim of this document is not to tell you how + to configure Linux or the ax25 utilities. However, you do need to add + a line in your ax25d.conf to allow connections to DXSpider for your + users. For each interface that you wish to allow connections on, use + the following format ... + + + + default * * * * * * - sysop /spider/src/client client %u ax25 + + + + + or, if you wish your users to be able to use SSID's on their callsigns + .. + + + + default * * * * * * - sysop /spider/src/client client %s ax25 + + + + + For most purposes this is not desirable. The only time you probably + will need this is when you need to allow other cluster nodes that are + using SSID's in. In this case it would probably be better to use the + first example and then add a specific line for that node like this: + + + + GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 + default * * * * * * - sysop /spider/src/client client %u ax25 + + + + 3.2. Allowing telnet connects from users + + + From version 1.47 there is a new (more efficient) way of doing this + (see next section) but, if you prefer, the method of doing it + described here will continue to work just fine. + + + Allowing telnet connections is quite simple. Firstly you need to add + a line in /etc/services to allow connections to a port number, like + this .... + + + + spdlogin 8000/tcp # spider anonymous login port + + + + + Then add a line in /etc/inetd.conf like this .... + + + + spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet + + + + + + Once this is done, you need to restart inetd like this .... + + + + killall -HUP inetd + + + + + + + Now login as sysop and cd spider/src. You can test that spider is + accepting telnet logins by issuing the following command .... + + + + ./client login telnet + + + + + You should get a login prompt and on issuing a callsign, you will be + given access to the cluster. Note, you will not get a password login. + There seems no good reason for a password prompt to be given so it is + not asked for. + + + Assuming all is well, then try a telnet from your linux console .... + + + + telnet localhost 8000 + + + + + + You should now get the login prompt and be able to login as before. + + + 3.3. Setting up telnet connects (from 1.47 onwards) + + From version 1.47 you can choose to allow the perl cluster.pl program + to allow connections directly (i.e. not via the /spider/src/client + interface program). If you are using Windows then this is the only + method available of allowing incoming telnet connections. + + + To do this you need first to remove any line that you may previously + have set up in /etc/inetd.conf. Remember to:- + + + + killall -HUP inetd + + + + + + to make the change happen... + + + Having done that, you need to copy the file /spider/perl/Listeners.pm + to /spider/local and then edit it. You will need to uncomment the line + containing "0.0.0.0" and select the correct port to listen on. So that + it looks like this:- + + + + @listen = ( + ["0.0.0.0", 8000], + ); + + + + + + As standard, the listener will listen on all interfaces + simultaneously. If you require more control than this, you can + specify each interface individually:- + + + + @listen = ( + ["gb7baa.dxcluster.net", 8000], + ["44.131.16.2", 6300], + ); + + + + + + This will only be successful if the IP addresses on each interface are + static. If you are using some kind of dynamic IP addressing then the + 'default' method is the only one that will work. + + + Restart the cluster.pl program to enable the listener. + + + One important difference with the internal listener is that no echoing + is done by the cluster program. Users will need to set 'local-echo' on + in their telnet clients if it isn't set automatically (as per the + standards). Needless to say this will probably only apply to Windows + users. + + + 3.4. Setting up for AGW Engine (1.47 onwards) + + AGW Engine is a Windows based ax25 stack. You can connect to an AGW + engine from Linux as well as Windows based machines. + + + In order to enable access to an AGW Engine you need to copy + /spider/perl/AGWConnect.pm to /spider/local and edit it. Specifically + you must:- + + + o set $enable to 1. + + o set $login and $passwd to the values set up in your AGW + installation. If you haven't set any there, then you should not + touch these values. + + o You can connect to a remote AGW engine (ie on some other machine) + by changing $addr and $port appropriately. + + o Restart the cluster.pl program + + + + + 3.5. Setting up node connects + + In order to allow cluster node connections, spider needs to know that + the connecting callsign is a cluster node. This is the case whether + the connect is incoming or outgoing. In spider this is a simple task + and can be done in runtime. + + + Later versions of Spider can distinguish different software and treat + them differently. For example, the WCY beacon cannot be handles by + AK1A type nodes as AK1A does not know what to do with PC73. There are + 4 different types of node at present and although they may not have + any major differences at the moment, it allows for compatibility. The + 4 types are ... + + + + set/node (AK1A type) + set/spider + set/dxnet + set/clx + + + + + + For now, we will assume that the cluster we are going to connect to is + an AK1A type node. + + + Start up the cluster as you did before and login as the sysop with + client. The cluster node I am wanting to make a connection to is + GB7BAA but you would obviously use whatever callsign you required. At + the prompt type ... + + + + set/node gb7baa + + + + + + The case does not matter as long as you have a version of DXSpider + later than 1.33. Earlier versions required the callsign to be in + upper case. + + + That is now set, it is as simple as that. To prove it, login on yet + another console as sysop, cd to spider/src and issue the command ... + + + + ./client gb7baa (using the callsign you set as a node) + + + + + + You should get an initialisation string from DXSpider like this ... + + + + ./client gb7baa + PC38^GB7MBC^~ + + + + + If the callsign you just set up as a cluster node is for an incoming + connect, this is all that needs to be done. If the connection is to + be outgoing then a connection script needs to be written. + + + Sometimes you make a mistake... Honest, it does happen. If you want + to make a node back to being a normal user, regardless of what type it + is, do: + + + + unset/node gb7baa + + + + + + 3.6. Connection scripts + + Because DXSpider operates under Linux, connections can be made using + just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all + possible examples. Connect scripts live in the /spider/connect + directory and are simple ascii files. Writing a script for + connections is therefore relatively simple. + + + The connect scripts consist of lines which start with the following + keywords or symbols:- + + + + # All lines starting with a # are ignored, as are completely blank + lines. + + timeout + timeout followed by a number is the number of seconds to wait + for a command to complete. If there is no timeout specified in + the script then the default is 60 seconds. + + + abort + abort is a regular expression containing one or more strings to + look for to abort a connection. This is a perl regular + expression and is executed ignoring case. + + + connect + connect followed by ax25, agw (for Windows users) or telnet and + some type dependent information. In the case of a telnet + connection, there can be up to two parameters. The first is the + ip address or hostname of the computer you wish to connect to + and the second is the port number you want to use (this can be + left out if it is a normal telnet session). In the case of an + ax25 session then this would normally be a call to ax25_call or + netrom_call as in the example above. It is your responsibility + to get your node and other ax25 parameters to work before going + down this route! + + + ' line in a chat type script. The words/phrases normally come in + pairs, either can be empty. Each line reads input from the + connection until it sees the string (or perl regular expression) + contained in the left hand string. If the left hand string is + empty then it doesn't read or wait for anything. The comparison + is done ignoring case. When the left hand string has found what + it is looking for (if it is) then the right hand string is sent + to the connection. This process is repeated for every line of + chat script. + + + client + client starts the connection, put the arguments you would want + here if you were starting the client program manually. You only + need this if the script has a different name to the callsign you + are trying to connect to (i.e. you have a script called other + which actually connects to GB7DJK-1 [instead of a script called + gb7djk-1]). + + + There are many possible ways to configure the script but here are + three examples, one for a NETRom/AX25 connect, one for AGW engines and + one for tcp/ip. + + + + timeout 60 + abort (Busy|Sorry|Fail) + # don't forget to chmod 4775 netrom_call! + connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh + # you can leave this out if you call the script 'gb7dxm' + client gb7dxm ax25 + + + + + + + + + + timeout 60 + abort (Busy|Sorry|Fail) + # this does exactly the same as the previous example + # the '1' is the AGW port number to connect thru for g1tlh + connect agw 1 g1tlh + # you can leave this out if you call the script 'gb7dxm' + client gb7dxm ax25 + + + + + + + + + timeout 15 + connect telnet dirkl.tobit.co.uk + # tell GB7DJK-1 that it is connected to GB7DJK + # you can leave this out if you call this script 'gb7djk' + client gb7djk telnet + + + + + + Both these examples assume that everything is set up properly at the + other end. You will find other examples in the /spider/examples + directory. + + + 3.7. Starting the connection + + You start the connection, from within a sysop enabled cluster login, + by typing in the word connect followed by a script name like this .... + + + + G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1 + connection to GB7DJK-1 started + G0VGS de GB7MBC 13-Dec-1998 2043Z > + + + + + This will start a connection using the script called gb7djk-1. You + can follow the connection by watching the term or console from where + you started cluster.pl. From version 1.47 onwards, you will need to + set/debug connect first. You should see something like this ... + + + + + + + + + + + + + + + + + + + <- D G1TLH connect gb7djk-1 + -> D G1TLH connection to GB7DJK-1 started + -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > + timeout set to 15 + CONNECT sort: telnet command: dirkl.tobit.co.uk + CHAT "login" -> "gb7djk" + received " + Red Hat Linux release 5.1 (Manhattan) + Kernel 2.0.35 on an i586 + " + received "login: " + sent "gb7djk" + CHAT "word" -> "gb7djk" + received "gb7djk" + received "Password: " + sent "gb7djk" + Connected to GB7DJK-1, starting normal protocol + <- O GB7DJK-1 telnet + -> B GB7DJK-1 0 + GB7DJK-1 channel func state 0 -> init + <- D GB7DJK-1 + <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 + <- D GB7DJK-1 PC38^GB7DJK-1^~ + <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime + 0 00:00^5447^~ + etc + + + + + + With later versions of Spider there is a set/login command for users. + This tells them when a user or node logs in or out. If you do not add + a line to your scripts after the final line (or before the client line + which should always be last if needed) then the login/logout + information will be sent to users before the login actually completes. + This means if a node is unreachable, it will continue sending logins + and logouts to users even though it is not actually connecting. To + avoid this use the following line ... + + + + + + + + + In a script, this might look like ... + + + + timeout 35 + abort (Busy|Sorry|Fail) + connect telnet mary 3000 + + + + + + 3.8. Telnet echo + + Cluster links in particular suffer greatly from the presence of telnet + echo. This is caused by the telnet negotiation itself and can create + at worst severe loops. At best it creates unnecessary bandwidth and + large logfiles! There are things that can be done to limit this + problem but will not always work dependent on the route taken to + connect. + + + Telnet echo itself should only be a problem if the connection is being + made to the telnet port (23). This port uses special rules that + include echo negotiation. If the connection is to a different port, + such as 7300, this negotiation does not happen and therefore no echo + should be present. + + + Sometimes it is not possible to make a direct connection to another + node and this can cause problems. There is a way of trying to + suppress the telnet echo but this will not always work, unfortunately + it is difficult to be more specific. Here is an example of what I + mean ... + + + + timeout 35 + abort (Busy|Sorry|Fail) + connect telnet mary.lancs.ac.uk + + + + + So, the first connection is made by Spider. This is fine as Spider + uses the Net_Telnet script from within perl. This actually uses TCP + rather than TELNET so no negotiation will be done on the first + connection. Once connected to mary.lancs.ac.uk, the command is sent + to suppress echo. Now a telnet is made to a cluster node that is + accepting connections on port 23. The problem with this link is that + the negotiation is made by the remote machine, therefore you have no + control over it. The chances are that this link will create echo and + there will be no way you can stop it. + + + + 3.9. Autostarting the cluster + + Ok, you should now have DXSpider running nicely and allowing connects + by cluster nodes or users. However, it has to be shutdown and + restarted manually. It would be much easier to have it start + automatically. + + + This is not only a way to start the cluster automatically, it also + works as a watchdog, checking the sanity of DXSpider and respawning it + should it crash for any reason. Before doing the following, shutdown + the cluster as you did earlier. + + + Login as root and bring up the /etc/inittab file in your favourite + editor. Add the following lines to the file near the end ... + + + + ##Start DXSpider on bootup and respawn it should it crash + DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + + + + + + This line works fine for RedHat distributions. It is also fine for + SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like + this ... + DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + + + + + + The line required for Slackware distributions is slightly different. + My thanks to Aurelio, PA3EZL for this information. + + + + DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7 + + + + + + This will automatically start DXSpider on tty7 (ALT-F7) on bootup and + restart it should it crash for any reason. + + + 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. + + + 4. Microsoft Windows Installation + + 4.1. Introduction + + IMPORTANT: + + What you'll be left with once you've followed these instructions is + (hopefully) a working DX Spider v1.47 system that is capable of + accepting or originating "internet" connections, plus inbound AX.25 + and TCP/IP radio connections. If the absence of outbound radio + connections is a serious limitation for you, it would be better for + you to wait a couple more weeks until this support has been added. + + On the other hand, you may have an enquiring mind, or better yet, may + be looking for a useful way of connecting your current (perhaps) AK1A + cluster "to the internet" via some networking mechanism (BPQEther, + etc) or other. I won't be producing instructions for the latter case, + because I don't have an AK1A to play with. But someone might ... + + Whatever, this document is intended to get you started with DX Spider + in a Microsoft Windows (TM) environment. It's not intended to teach + you anything other than how to perform a minimum configuration of a DX + Spider installation and have it able to connect across "the internet" + to other DX Clusters, while accepting inbound TELNET and radio + connections. + + + 4.2. The requirements + + The very first things you're going to need are (in order of + importance):- + + + o A cup of good, strong tea + + o A supported Windows platform with an internet connection so you can + download the necessary software bits and bobs directly to it. There + are other ways, but this is preferable. + + + o Another cup of good, strong tea + + o If all goes according to plan, about an hour to spare + + o Plenty of good, strong tea + + + 4.3. The system + + The platform I used to generate these instructions was a "vanilla" + Microsoft Windows Me 4.90.3000 system, with a 700MHz AMD Athlon + processor and 96 Mb memory. I've also personally verified that it runs + on my laptop (Pentium 266MHz, 32 Mb memory, Windows 98 SE v4.10.2222 + A) and a computer that I assembled from a random pile of junk (AMD + K6-2 333MHz, 64 Mb memory, Windows 98 v4.10.1998). As a result, I have + reason to believe that what I'm about to describe will perform equally + on any 32-bit MS Windows environment with 32 Mb of memory. + + Because of the changes that have recently been made to the core + "cluster.pl" module and the introduction of a very lightweight + "winclient.pl", I have a sneaking suspicion that this will now run on + any platform that has reasonably complete support for Perl. Is there + someone out there with both an enquiring mind and (say) a Macintosh, + for instance? + + Please bear in mind, though, that my instructions relate solely to how + to get this going under a Microsoft Windows environment, and I have + zero intention of trying to make them say otherwise. + + + 4.4. Perl + + Install your chosen Perl environment. Unless you have a very good + reason for not doing so, I strongly suggest that you use ActivePerl + v5.6. For my testing & development, I used build 623. You can get + this from:- + http://www.activestate.com/Products/ActivePerl/Download.html + + You will need to choose either the MSI or the AS package. My + recommendation is that you choose the MSI package and deal with the + consequences if your system isn't equipped with support for the latest + MS Installer; you'll be better off in the long run. The build 623 + download is 7,460 KB, so now is a really good time to have some tea if + you're on a slow dial-up connection. + + During installation, please ensure that you do choose the options to + "Add Perl to the PATH environment variable" and "Create Perl file + extension association"; it will make your life so much easier. Once + the installation is finished, be sure to reboot your PC. You probably + won't be told anywhere else that this needs to be done now, but it + does. Really. + + Once you've rebooted, open a "DOS box" (Start > Run > command might do + it, if you can't find it elsewhere) and from wherever it lands, type + PERL -v <ENTER> (it's better if that's a lower-case be rewarded with + some interesting information about your Perl installation. If you're + not, you must go back to the beginning and discover what went wrong + and fix it. It's pointless to proceed unless this simple check is + passed. Assuming it did work, you may now move on. + + + 4.5. Additional packages + + Some extensions ("packages") need to be added to the base Perl + distribution, and we'll do this next. If you're using the Perl I + recommended, and don't know any better for yourself, then just blindly + following these instructions will work just fine. If that didn't + describe you, then you're on your own. + + Visit the following URL: + + http://www.activestate.com/PPMPackages/zips/6xx-builds-only/ + + and download the following files:- + + + + Data-Dumper.zip + Net-Telnet.zip + TimeDate.zip + Time-HiRes.zip + DB_File.zip + + + + + Make yourself a convenient directory to unpack all of these zip files + into (I put mine in "D:\ppm>") and do the following (the bits you type + in are blue ). Note that where these files land will be directly + related to where you chose to install your ActivePerl (mine, as you + can probably guess from what follows, went into "D:\Perl"):- + + + + D:\ppm>ppm install Data-Dumper.ppd + Installing package 'Data-Dumper.ppd' + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp + Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib + Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html + Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm + Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist + D:\ppm> + + + + + I'm not going to bother you with exhaustive details of the rest of + them, but suffice it to say you need to: + + + + ppm install DB_File.ppd + ppm install Net-Telnet.ppd + ppm install TimeDate.ppd + ppm install Time-HiRes.ppd + + + + + If all that seemed to work OK, time to move along. Before anyone who + is familiar with PPM tells me that we didn't need to download and keep + those files locally, I knew that. I also knew that PPM is sometimes + awkward to configure via firewalls, and that sometimes the + repositories don't always work the way we'd hope. I do it that way + because it suits me. + + + + + + 4.6. Getting Spider + + Get the current version of the DX Spider distribution. This needs to + be v1.47 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 my package from:- + + http://www.dcc.rsgb.org/WinSpider.zip + + or if you want the lastest CVS version (which is produced every night) + + http://www.dxcluster.org/download/CVSlatest.tgz + + If you went down the CVS route, then everything will be nicely set out + on your local disk. If you got the ZIP file, unpack it to somewhere + convenient. The following examples assume that you put it on drive + "C:\", for convenience. + + NOTE: This distribution method will go away as soon as the first v1.47 + tarball is released. You can use WinZip to unpack that, and my life + will be made easier by not needing to keep this .ZIP file updated. + + + 5. Installing the software + + Ensure that your CVS session or your unZIPped file have left you with + a directory "C:\spider\local"; if not, go to "C:\spider\" and create + one. If "C:\spider" is missing, go back and figure out why, because it + shouldn't be. + + Now create your own local copy of the DXVars.pm file by:- + + + + copy c:\spider\perl\DXVars.pm.issue + c:\spider\local\DXVars.pm + + + + + Now you'll need to edit this file using a text editor. If nothing + else, you can simply + + + + cd \spider\local + + + + + and then + + + + notepad DXVars.pm + + + + + to bring up an editor window containing the file. As an absolute + minimum you must adjust the following items in DXVars.pm:- + + + o $mycall - Should hold the callsign of your DX Cluster + + + o $myname - The SysOp's first name + + o $myalias - the SysOp's callsign. Cannot be the same as $mycall! + + You really also ought to update the $mylatitude, $mylongitude, $myqth + and $myemail variables. And unless you are absolutely certain you know + what you're doing, you should change nothing else in this file. + + + 5.1. The AGW packet engine + + On the assumption that you'll be using the SV2AGW Packet Engine to + interface your radios to the cluster, you should now create your own + local copy of AGWConnect.pm by:- + + + + copy c:\spider\perl\AGWConnect.pm + c:\spider\local\AGWConnect.pm + + + + + and then + + + + notepad AGWConnect.pm + + + + + to bring up an editor window containing the file. You must consider + adjusting the following items in AGWConnect.pm:- + + + o $enable - set to '1' to enable AGWPE interface + + o $login - the login ID you chose when you set up the SV2AGW + security :-) + + o $passwd - password that matches $login + + + 5.2. Setting up the initial user files + + Next you need to create the initial user files, etc. A tool is + supplied which will do this for you. To run the tool:- + + + + cd \spider\perl + perl create_sysop.pl + + + + + If all goes according to plan, you will see no output from this + program, and after a brief wait, your DOS prompt will be returned. + + Depending on how brave you are, you might now care to try the + following:- + + + + + perl cluster.pl + + + + + If you did everything you were told, your DOS window will now hold a + display which looks something like:- + + + + DXSpider DX Cluster Version 1.47 + Copyright (c) 1998-2001 Dirk Koopman G1TLH + loading prefixes ... + loading band data ... + loading user file system ... + starting listeners ... + Internal port: localhost 27754 + load badwords: Ok + reading in duplicate spot and WWV info ... + reading existing message headers ... + load badmsg: Ok + load forward: Ok + load swop: Ok + @msg = 0 before delete + @msg = 0 after delete + reading cron jobs ...v cron: reading /spider/cmd/crontab + cron: adding 1 0 * * 0 + DXUser::export("$main::data/user_asc") + reading database descriptors ... + doing local initialisation ... + orft we jolly well go ... + queue msg (0) + + + + + Now, if that's what you've got, you are very nearly home and dry (in + as far as these particular experiments are concerned, anyhow) + + To access your new cluster (from the local machine) find yourself + another "DOS box" and do the following:- + + + + cd \spider\perl + perl winclient.pl + + + + + If you are rewarded with a display which looks something like:- + + + + Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47 + 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) + + + 5.3. Incoming telnets + + If you want to enable inbound "TELNET" connections, you've got a + little more work to do. From a handy "DOS box" that's not doing + anything else, do the following:- + + + + copy \spider\perl\listeners.pm \spider\local + cd \spider\local + notepad listeners.pm + + + + + The following lines 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. + + 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 an amount of effort on your + part to read, understand and implement what needs to be done to set + this up. + + + 5.4. Connecting to other clusters + + If you want to connect this to another cluster, then you'll want to + negotiate a link with someone. For experimental purposes, I'm happy to + allow folk to connect to GB7DXA (spud.ath.cx), on the understanding + that the system may or may not be there and may or may not be + connected to anything particularly useful at any given moment. Contact + me by Email if you want me to set up a connection for you. + + + 6. General Information + + The following relates to all versions of DXSpider and is not platform + related. + + + 6.1. The crontab file + + Login as sysop and create a file in /spider/local_cmd called crontab. + Edit it with your favourite editor and add a line like this (I have + included a comment) + + + + # check every 10 minutes to see if gb7xxx is connected and if not + # start a connect job going + + 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') + + + + The callsign involved will be the callsign of the cluster node you are + going to connect to. This will now check every 10 minutes to see if + gb7xxx is connected, if it is then nothing will be done. If it is + not, then a connect attempt will be started. + + + There are probably lots of other things you could use this crontab + file for. If you want to know more about it, look at the DXSpider + website at the cron page where it is explained more fully. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/txt/wininstallation.txt b/txt/wininstallation.txt deleted file mode 100644 index 2f055da6..00000000 --- a/txt/wininstallation.txt +++ /dev/null @@ -1,462 +0,0 @@ - The Installation Guide for DXSpider under Microsoft Windows - Iain Philipps, G0RDI (g0rdi@77hz.com) - $Date$ $Revision$ - - DX Spider under Microsoft Windows (TM) - ______________________________________________________________________ - - Table of Contents - - - 1. Introduction - - 1.1 The requirements - 1.2 The system - 1.3 Perl - 1.4 Additional packages - 1.5 Getting Spider - - 2. Installing the software - - 2.1 The AGW packet engine - 2.2 Setting up the initial user files - 2.3 Incoming telnets - 2.4 Connecting to other clusters - - - ______________________________________________________________________ - - 1. Introduction - - IMPORTANT: - - What you'll be left with once you've followed these instructions is - (hopefully) a working DX Spider v1.47 system that is capable of - accepting or originating "internet" connections, plus inbound AX.25 - and TCP/IP radio connections. If the absence of outbound radio - connections is a serious limitation for you, it would be better for - you to wait a couple more weeks until this support has been added. - - On the other hand, you may have an enquiring mind, or better yet, may - be looking for a useful way of connecting your current (perhaps) AK1A - cluster "to the internet" via some networking mechanism (BPQEther, - etc) or other. I won't be producing instructions for the latter case, - because I don't have an AK1A to play with. But someone might ... - - Whatever, this document is intended to get you started with DX Spider - in a Microsoft Windows (TM) environment. It's not intended to teach - you anything other than how to perform a minimum configuration of a DX - Spider installation and have it able to connect across "the internet" - to other DX Clusters, while accepting inbound TELNET and radio - connections. - - - 1.1. The requirements - - The very first things you're going to need are (in order of - importance):- - - - o A cup of good, strong tea - - o A supported Windows platform with an internet connection so you can - download the necessary software bits and bobs directly to it. There - are other ways, but this is preferable. - - - o Another cup of good, strong tea - - o If all goes according to plan, about an hour to spare - - o Plenty of good, strong tea - - - 1.2. The system - - The platform I used to generate these instructions was a "vanilla" - Microsoft Windows Me 4.90.3000 system, with a 700MHz AMD Athlon - processor and 96 Mb memory. I've also personally verified that it runs - on my laptop (Pentium 266MHz, 32 Mb memory, Windows 98 SE v4.10.2222 - A) and a computer that I assembled from a random pile of junk (AMD - K6-2 333MHz, 64 Mb memory, Windows 98 v4.10.1998). As a result, I have - reason to believe that what I'm about to describe will perform equally - on any 32-bit MS Windows environment with 32 Mb of memory. - - Because of the changes that have recently been made to the core - "cluster.pl" module and the introduction of a very lightweight - "winclient.pl", I have a sneaking suspicion that this will now run on - any platform that has reasonably complete support for Perl. Is there - someone out there with both an enquiring mind and (say) a Macintosh, - for instance? - - Please bear in mind, though, that my instructions relate solely to how - to get this going under a Microsoft Windows environment, and I have - zero intention of trying to make them say otherwise. - - - 1.3. Perl - - Install your chosen Perl environment. Unless you have a very good - reason for not doing so, I strongly suggest that you use ActivePerl - v5.6. For my testing & development, I used build 623. You can get - this from:- - http://www.activestate.com/Products/ActivePerl/Download.html - - You will need to choose either the MSI or the AS package. My - recommendation is that you choose the MSI package and deal with the - consequences if your system isn't equipped with support for the latest - MS Installer; you'll be better off in the long run. The build 623 - download is 7,460 KB, so now is a really good time to have some tea if - you're on a slow dial-up connection. - - During installation, please ensure that you do choose the options to - "Add Perl to the PATH environment variable" and "Create Perl file - extension association"; it will make your life so much easier. Once - the installation is finished, be sure to reboot your PC. You probably - won't be told anywhere else that this needs to be done now, but it - does. Really. - - Once you've rebooted, open a "DOS box" (Start > Run > command might do - it, if you can't find it elsewhere) and from wherever it lands, type - PERL -v <ENTER> (it's better if that's a lower-case be rewarded with - some interesting information about your Perl installation. If you're - not, you must go back to the beginning and discover what went wrong - and fix it. It's pointless to proceed unless this simple check is - passed. Assuming it did work, you may now move on. - - - 1.4. Additional packages - - Some extensions ("packages") need to be added to the base Perl - distribution, and we'll do this next. If you're using the Perl I - recommended, and don't know any better for yourself, then just blindly - following these instructions will work just fine. If that didn't - describe you, then you're on your own. - - Visit the following URL: - - http://www.activestate.com/PPMPackages/zips/6xx-builds-only/ - - and download the following files:- - - - - Data-Dumper.zip - Net-Telnet.zip - TimeDate.zip - Time-HiRes.zip - DB_File.zip - - - - - Make yourself a convenient directory to unpack all of these zip files - into (I put mine in "D:\ppm>") and do the following (the bits you type - in are blue ). Note that where these files land will be directly - related to where you chose to install your ActivePerl (mine, as you - can probably guess from what follows, went into "D:\Perl"):- - - - - D:\ppm>ppm install Data-Dumper.ppd - Installing package 'Data-Dumper.ppd' - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp - Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib - Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html - Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm - Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist - D:\ppm> - - - - - I'm not going to bother you with exhaustive details of the rest of - them, but suffice it to say you need to: - - - - ppm install DB_File.ppd - ppm install Net-Telnet.ppd - ppm install TimeDate.ppd - ppm install Time-HiRes.ppd - - - - - If all that seemed to work OK, time to move along. Before anyone who - is familiar with PPM tells me that we didn't need to download and keep - those files locally, I knew that. I also knew that PPM is sometimes - awkward to configure via firewalls, and that sometimes the - repositories don't always work the way we'd hope. I do it that way - because it suits me. - - - - - - 1.5. Getting Spider - - Get the current version of the DX Spider distribution. This needs to - be v1.47 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 my package from:- - - http://www.dcc.rsgb.org/WinSpider.zip - - or if you want the lastest CVS version (which is produced every night) - - http://www.dxcluster.org/download/CVSlatest.tgz - - If you went down the CVS route, then everything will be nicely set out - on your local disk. If you got the ZIP file, unpack it to somewhere - convenient. The following examples assume that you put it on drive - "C:\", for convenience. - - NOTE: This distribution method will go away as soon as the first v1.47 - tarball is released. You can use WinZip to unpack that, and my life - will be made easier by not needing to keep this .ZIP file updated. - - - 2. Installing the software - - Ensure that your CVS session or your unZIPped file have left you with - a directory "C:\spider\local"; if not, go to "C:\spider\" and create - one. If "C:\spider" is missing, go back and figure out why, because it - shouldn't be. - - Now create your own local copy of the DXVars.pm file by:- - - - - copy c:\spider\perl\DXVars.pm.issue - c:\spider\local\DXVars.pm - - - - - Now you'll need to edit this file using a text editor. If nothing - else, you can simply - - - - cd \spider\local - - - - - and then - - - - notepad DXVars.pm - - - - - to bring up an editor window containing the file. As an absolute - minimum you must adjust the following items in DXVars.pm:- - - - o $mycall - Should hold the callsign of your DX Cluster - - - o $myname - The SysOp's first name - - o $myalias - the SysOp's callsign. Cannot be the same as $mycall! - - You really also ought to update the $mylatitude, $mylongitude, $myqth - and $myemail variables. And unless you are absolutely certain you know - what you're doing, you should change nothing else in this file. - - - 2.1. The AGW packet engine - - On the assumption that you'll be using the SV2AGW Packet Engine to - interface your radios to the cluster, you should now create your own - local copy of AGWConnect.pm by:- - - - - copy c:\spider\perl\AGWConnect.pm - c:\spider\local\AGWConnect.pm - - - - - and then - - - - notepad AGWConnect.pm - - - - - to bring up an editor window containing the file. You must consider - adjusting the following items in AGWConnect.pm:- - - - o $enable - set to '1' to enable AGWPE interface - - o $login - the login ID you chose when you set up the SV2AGW - security :-) - - o $passwd - password that matches $login - - - 2.2. Setting up the initial user files - - Next you need to create the initial user files, etc. A tool is - supplied which will do this for you. To run the tool:- - - - - cd \spider\perl - perl create_sysop.pl - - - - - If all goes according to plan, you will see no output from this - program, and after a brief wait, your DOS prompt will be returned. - - Depending on how brave you are, you might now care to try the - following:- - - - - - perl cluster.pl - - - - - If you did everything you were told, your DOS window will now hold a - display which looks something like:- - - - - DXSpider DX Cluster Version 1.47 - Copyright (c) 1998-2001 Dirk Koopman G1TLH - loading prefixes ... - loading band data ... - loading user file system ... - starting listeners ... - Internal port: localhost 27754 - load badwords: Ok - reading in duplicate spot and WWV info ... - reading existing message headers ... - load badmsg: Ok - load forward: Ok - load swop: Ok - @msg = 0 before delete - @msg = 0 after delete - reading cron jobs ...v cron: reading /spider/cmd/crontab - cron: adding 1 0 * * 0 - DXUser::export("$main::data/user_asc") - reading database descriptors ... - doing local initialisation ... - orft we jolly well go ... - queue msg (0) - - - - - Now, if that's what you've got, you are very nearly home and dry (in - as far as these particular experiments are concerned, anyhow) - - To access your new cluster (from the local machine) find yourself - another "DOS box" and do the following:- - - - - cd \spider\perl - perl winclient.pl - - - - - If you are rewarded with a display which looks something like:- - - - - Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47 - 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) - - - 2.3. Incoming telnets - - If you want to enable inbound "TELNET" connections, you've got a - little more work to do. From a handy "DOS box" that's not doing - anything else, do the following:- - - - - copy \spider\perl\listeners.pm \spider\local - cd \spider\local - notepad listeners.pm - - - - - The following lines 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. - - 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 an amount of effort on your - part to read, understand and implement what needs to be done to set - this up. - - - 2.4. Connecting to other clusters - - If you want to connect this to another cluster, then you'll want to - negotiate a link with someone. For experimental purposes, I'm happy to - allow folk to connect to GB7DXA (spud.ath.cx), on the understanding - that the system may or may not be there and may or may not be - connected to anything particularly useful at any given moment. Contact - me by Email if you want me to set up a connection for you. - - Last updated: 15-Apr-01 - - - - - - - - - - - - - - - - - - - - -