Installation (Original version by Iain Phillips, G0RDI)
-Last modified: 13 January 2001 by Ian Maude, G0VGS
+Last modified: 24 January 2001 by Ian Maude, G0VGS
Introduction
@@ -1674,6 +1674,19 @@ announces etc. To use this program, simply use console.pl instead of client.pl.
To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
file with your favourite editor.
+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.
+
CVS
@@ -1810,7 +1823,7 @@ 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 eg: iota or qsl
by eg: G,M,2
origin
@@ -1823,28 +1836,28 @@ You can use any of the following things in this line:-
channel
wx 1 filter WX announces
dest 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...
@@ -1859,11 +1872,11 @@ but this probably for advanced users...
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
-
+
accept/spots (0)
@@ -1883,7 +1896,7 @@ 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 eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on same as 'freq'
call eg: G,PA,HB9
@@ -1897,7 +1910,7 @@ You can use any of the following things in this line:-
by_zone
origin
channel
-
+
For frequencies, you can use any of the band names defined in
@@ -1908,16 +1921,16 @@ 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...
@@ -1932,13 +1945,13 @@ but this probably for advanced users...
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
-
+
accept/wcy (0)
@@ -1951,7 +1964,7 @@ default for nodes and users eg:-
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-
+
by eg: G,M,2
origin
origin_dxcc eg: 61,62 (from eg: sh/pre G)
@@ -1961,7 +1974,7 @@ filter on the following fields:-
by_itu
by_zone
channel
-
+
There are no examples because WCY Broadcasts only come from one place and
@@ -1983,10 +1996,10 @@ 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
-
+
accept/wwv (0)
@@ -1999,7 +2012,7 @@ default for nodes and users eg:-
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-
+
by eg: G,M,2
origin
origin_dxcc eg: 61,62 (from eg: sh/pre G)
@@ -2009,13 +2022,13 @@ filter on the following fields:-
by_itu
by_zone
channel
-
+
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).
@@ -2034,13 +2047,13 @@ 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
-
+
announce (0)
@@ -2112,17 +2125,17 @@ 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.
@@ -2141,28 +2154,28 @@ 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.
@@ -2316,16 +2329,16 @@ 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
-
+
debug (9)
@@ -2373,18 +2386,18 @@ 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
-
+
directory (extended for sysops) (5)
@@ -2413,24 +2426,24 @@ Disconnect any <call> connected locally
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.
@@ -2564,6 +2577,7 @@ As a sysop you can kill any message on the system.
kill full (5)
+
kill full <msgno> [<msgno>] Delete a message from the
whole cluster
@@ -2601,6 +2615,8 @@ changes to take effect.
load/baddx (9)
+
+
load/baddx Reload the bad DX table
@@ -2841,7 +2857,7 @@ 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 eg: iota or qsl
by eg: G,M,2
origin
@@ -2854,19 +2870,19 @@ You can use any of the following things in this line:-
channel
wx 1 filter WX announces
dest 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...
@@ -2881,11 +2897,11 @@ but this probably for advanced users...
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
-
+
reject/spots (0)
@@ -2904,7 +2920,7 @@ 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 eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on same as 'freq'
call eg: G,PA,HB9
@@ -2918,7 +2934,7 @@ You can use any of the following things in this line:-
by_zone
origin
channel
-
+
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 -
@@ -2928,16 +2944,16 @@ too hung up about that)
some examples:-
-
+
rej/spot 1 on hf
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-
+
You can use the tag 'all' to reject everything eg:
-
+
rej/spot 3 all
-
+
but this probably for advanced users...
@@ -2953,13 +2969,13 @@ but this probably for advanced users...
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
-
+
reject/wcy (0)
@@ -2972,7 +2988,7 @@ default for nodes and users eg:-
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-
+
by eg: G,M,2
origin
origin_dxcc eg: 61,62 (from eg: sh/pre G)
@@ -2982,7 +2998,7 @@ filter on the following fields:-
by_itu
by_zone
channel
-
+
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).
@@ -3016,7 +3032,7 @@ default for nodes and users eg:-
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
-
+
by eg: G,M,2
origin
origin_dxcc eg: 61,62 (from eg: sh/pre G)
@@ -3026,13 +3042,13 @@ filter on the following fields:-
by_itu
by_zone
channel
-
+
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).
@@ -3050,12 +3066,12 @@ See HELP FILTER for information.
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
-
+
reply (0)
@@ -3103,9 +3119,9 @@ 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.
@@ -3159,15 +3175,15 @@ 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
-
+
set/badnode (6)
@@ -3184,15 +3200,15 @@ 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.
@@ -3212,16 +3228,16 @@ 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.
@@ -3335,9 +3351,9 @@ 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
-
+
set/hops (8)
@@ -3353,11 +3369,11 @@ 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.
@@ -3402,9 +3418,9 @@ the languages available are en (English) and nl (Dutch).
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
-
+
set/sys_location (9)
@@ -3419,9 +3435,9 @@ 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
-
+
set/logininfo (0)
@@ -3456,9 +3472,9 @@ To allow the user to connect again, use the unset/lockout command.
Tell the cluster what your name is, eg:-
-
+
set/name Dirk
-
+
set/node (9)
@@ -3473,12 +3489,12 @@ 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.
@@ -3517,10 +3533,10 @@ 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.
@@ -3616,9 +3632,9 @@ 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
-
+
set/qth (0)
@@ -3630,9 +3646,9 @@ correctly (assuming your locator is correct ;-). For example:-
Tell the system where your are. For example:-
-
+
set/qth East Dereham, Norfolk
-
+
set/talk (0)
@@ -3742,7 +3758,7 @@ If you just type SHOW/DX you will get the last so many spots
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)
@@ -3772,11 +3788,11 @@ iota [<iota>] - If the iota island number is missing it will
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
@@ -3784,7 +3800,7 @@ e.g.
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
-
+
show/dxcc (0)
@@ -3801,10 +3817,10 @@ 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
-
+
show/files (0)
@@ -3819,9 +3835,9 @@ 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.
@@ -3829,9 +3845,9 @@ 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.
@@ -3915,10 +3931,10 @@ that you are connected to.
For example:-
-
+
SH/MOON
SH/MOON G1TLH W5UN
-
+
show/muf (0)
@@ -3964,13 +3980,13 @@ 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
@@ -3979,24 +3995,24 @@ produces:
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
@@ -4058,10 +4074,10 @@ 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
@@ -4071,9 +4087,9 @@ 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
-
+
show/qrz (0)
@@ -4098,9 +4114,9 @@ is provided for users of this software by http://www.qrz.com
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
-
+
show/satellite (0)
@@ -4128,10 +4144,10 @@ Each pass in a period is separated with a row of '-----' characters
So for example:-
-
+
SH/SAT AO-10
SH/SAT FENGYUN1 12 2
-
+
show/sun (0)
@@ -4155,10 +4171,10 @@ that you are connected to.
For example:-
-
+
SH/SUN
SH/SUN G1TLH K9CW ZS
-
+
show/time (0)
@@ -4291,19 +4307,19 @@ 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
@@ -4344,16 +4360,16 @@ 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
-
+
type (0)
@@ -4367,9 +4383,9 @@ 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.