The DXSpider Administration Manual v1.48
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.48 August 2001 revision 1.1
+ Version 1.49 November 2001 revision 1.0
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1.1 Introduction
1.2 Route Filters
- 1.3 The default_node filter
+ 1.3 The node_default filter
1.4 General route filtering
1.5 General filter rules
1.6 Types of filter
1.8 Default filters
1.9 Advanced filtering
1.10 Basic hop control
- 1.11 Isolating networks
+ 1.11 Hop Control on Specific Nodes
+ 1.12 Isolating networks
2. Other filters
2.1 Filtering Mail
- 2.2 Filtering DX callouts (Depricated)
- 2.3 Filtering words from text fields in Announce, Talk and DX spots
+ 2.2 Filtering words from text fields in Announce, Talk and DX spots
+ 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters
3. Mail
3.7 Distribution lists
3.8 BBS interface
- 4. Databases
-
- 4.1 Creating databases
- 4.2 Importing databases
- 4.3 Checking available databases
- 4.4 Looking up databases
- 4.5 Removing databases
-
- 5. Information, files and useful programs
-
- 5.1 MOTD
- 5.2 Downtime message
- 5.3 Other text messages
- 5.4 The Aliases file
- 5.5 Console.pl
- 5.6 Updating kepler data
- 5.7 The QRZ callbook
-
- 6. CVS
-
- 7. The DXSpider command set
-
- 7.1 accept/announce (0)
- 7.2 accept/announce (extended for sysops) (8)
- 7.3 accept/route (8)
- 7.4 accept/spots (0)
- 7.5 accept/spots (extended for sysops) (8)
- 7.6 accept/wcy (0)
- 7.7 accept/wcy (extended for sysops) (8)
- 7.8 accept/wwv (0)
- 7.9 accept/wwv (extended for sysops) (8)
- 7.10 announce (0)
- 7.11 announce full (0)
- 7.12 announce sysop (5)
- 7.13 apropos (0)
- 7.14 bye (0)
- 7.15 catchup (5)
- 7.16 clear/spots (0)
- 7.17 connect (5)
- 7.18 dbavail (0)
- 7.19 dbcreate (9)
- 7.20 dbimport (9)
- 7.21 dbremove (9)
- 7.22 dbshow (0)
- 7.23 debug (9)
- 7.24 directory (0)
- 7.25 directory (extended for sysops) (5)
- 7.26 disconnect (8)
- 7.27 dx (0)
- 7.28 export (9)
- 7.29 export_users (9)
- 7.30 forward/latlong (8)
- 7.31 forward/opername (1)
- 7.32 help (0)
- 7.33 init (5)
- 7.34 kill (0)
- 7.35 kill (5)
- 7.36 kill full (5)
- 7.37 links (0)
- 7.38 load/aliases (9)
- 7.39 load/baddx (9)
- 7.40 load/badmsg (9)
- 7.41 load/badwords (9)
- 7.42 load/bands (9)
- 7.43 load/cmd_cache (9)
- 7.44 load/forward (9)
- 7.45 load/messages (9)
- 7.46 load/prefixes (9)
- 7.47 merge (5)
- 7.48 msg (9)
- 7.49 pc (8)
- 7.50 ping (1)
- 7.51 rcmd (1)
- 7.52 read (0)
- 7.53 read (extended for sysops) (5)
- 7.54 reject/announce
- 7.55 reject/announce (extended for sysops) (8)
- 7.56 reject/route (8)
- 7.57 reject/spots (0)
- 7.58 reject/spots (extended for sysops) (8)
- 7.59 reject/wcy (0)
- 7.60 reject/wcy (extended for sysops) (8)
- 7.61 reject/wwv (0)
- 7.62 reject/wwv (extended for sysops) (8)
- 7.63 reply (0)
- 7.64 send (0)
- 7.65 set/address (0)
- 7.66 set/announce (0)
- 7.67 set/arcluster (5)
- 7.68 set/baddx (8)
- 7.69 set/badnode (6)
- 7.70 set/badspotter (8)
- 7.71 set/beep (0)
- 7.72 set/bbs (5)
- 7.73 set/clx (5)
- 7.74 set/debug (9)
- 7.75 set/dx (0)
- 7.76 set/dxgrid (0)
- 7.77 set/dxnet (5)
- 7.78 set/echo (0)
- 7.79 set/here (0)
- 7.80 set/homenode (0)
- 7.81 set/hops (8)
- 7.82 set/isolate (9)
- 7.83 set/language (0)
- 7.84 set/location (0)
- 7.85 set/sys_location (9)
- 7.86 set/logininfo (0)
- 7.87 set/lockout (9)
- 7.88 set/name (0)
- 7.89 set/node (9)
- 7.90 set/obscount (9)
- 7.91 set/page (0)
- 7.92 set/password (9)
- 7.93 set/pinginterval (9)
- 7.94 set/privilege (9)
- 7.95 set/spider (5)
- 7.96 set/sys_qra (9)
- 7.97 set/qra (0)
- 7.98 set/qth (0)
- 7.99 set/talk (0)
- 7.100 set/wcy (0)
- 7.101 set/wwv (0)
- 7.102 set/wx (0)
- 7.103 show/baddx (1)
- 7.104 show/badnode (6)
- 7.105 show/badspotter (1)
- 7.106 show/configuration (0)
- 7.107 show/configuration/node (0)
- 7.108 show/connect (1)
- 7.109 show/date (0)
- 7.110 show/debug (9)
- 7.111 show/dx (0)
- 7.112 show/dxcc (0)
- 7.113 show/files (0)
- 7.114 show/filter (0)
- 7.115 show/filter (extended for sysops) (5)
- 7.116 show/hops (8)
- 7.117 show/isolate (1)
- 7.118 show/lockout (9)
- 7.119 show/log (8)
- 7.120 show/moon (0)
- 7.121 show/muf (0)
- 7.122 show/node (1)
- 7.123 show/prefix (0)
- 7.124 show/program (5)
- 7.125 show/qra (0)
- 7.126 show/qrz (0)
- 7.127 show/route (0)
- 7.128 show/satellite (0)
- 7.129 show/sun (0)
- 7.130 show/time (0)
- 7.131 show/wcy (0)
- 7.132 show/wwv (0)
- 7.133 shutdown (5)
- 7.134 spoof (9)
- 7.135 stat/db (5)
- 7.136 stat/channel (5)
- 7.137 stat/msg (5)
- 7.138 stat/route_node (5)
- 7.139 stat/route_user (5)
- 7.140 stat/user (5)
- 7.141 sysop (0)
- 7.142 talk (0)
- 7.143 type (0)
- 7.144 who (0)
- 7.145 wx (0)
- 7.146 wx (enhanced for sysops) (5)
+ 4. Scripts
+
+ 5. Databases
+
+ 5.1 Creating databases
+ 5.2 Importing databases
+ 5.3 Checking available databases
+ 5.4 Looking up databases
+ 5.5 Removing databases
+
+ 6. Information, files and useful programs
+
+ 6.1 MOTD
+ 6.2 MOTD_NOR
+ 6.3 Downtime message
+ 6.4 Other text messages
+ 6.5 The Aliases file
+ 6.6 Console.pl
+ 6.7 Updating kepler data
+ 6.8 The QRZ callbook
+ 6.9 Scripts
+
+ 7. Security
+
+ 7.1 Registration
+ 7.2 Passwords
+
+ 8. CVS
+
+ 9. The DXSpider command set
+
+ 9.1 accept/announce (0)
+ 9.2 accept/announce (extended for sysops) (8)
+ 9.3 accept/route (8)
+ 9.4 accept/spots (0)
+ 9.5 accept/spots (extended for sysops) (8)
+ 9.6 accept/wcy (0)
+ 9.7 accept/wcy (extended for sysops) (8)
+ 9.8 accept/wwv (0)
+ 9.9 accept/wwv (extended for sysops) (8)
+ 9.10 announce (0)
+ 9.11 announce full (0)
+ 9.12 announce sysop (5)
+ 9.13 apropos (0)
+ 9.14 bye (0)
+ 9.15 catchup (5)
+ 9.16 clear/spots (0)
+ 9.17 connect (5)
+ 9.18 dbavail (0)
+ 9.19 dbcreate (9)
+ 9.20 dbimport (9)
+ 9.21 dbremove (9)
+ 9.22 dbshow (0)
+ 9.23 debug (9)
+ 9.24 directory (0)
+ 9.25 directory (extended for sysops) (5)
+ 9.26 disconnect (8)
+ 9.27 dx (0)
+ 9.28 export (9)
+ 9.29 export_users (9)
+ 9.30 forward/latlong (8)
+ 9.31 forward/opername (1)
+ 9.32 help (0)
+ 9.33 init (5)
+ 9.34 kill (0)
+ 9.35 kill (5)
+ 9.36 kill full (5)
+ 9.37 links (0)
+ 9.38 load/aliases (9)
+ 9.39 load/badmsg (9)
+ 9.40 load/bands (9)
+ 9.41 load/cmd_cache (9)
+ 9.42 load/forward (9)
+ 9.43 load/messages (9)
+ 9.44 load/prefixes (9)
+ 9.45 merge (5)
+ 9.46 msg (9)
+ 9.47 pc (8)
+ 9.48 ping (1)
+ 9.49 rcmd (1)
+ 9.50 read (0)
+ 9.51 read (extended for sysops) (5)
+ 9.52 reject/announce
+ 9.53 reject/announce (extended for sysops) (8)
+ 9.54 reject/route (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/bbs (5)
+ 9.71 set/clx (5)
+ 9.72 set/debug (9)
+ 9.73 set/dx (0)
+ 9.74 set/dxgrid (0)
+ 9.75 set/dxnet (5)
+ 9.76 set/echo (0)
+ 9.77 set/here (0)
+ 9.78 set/homenode (0)
+ 9.79 set/hops (8)
+ 9.80 set/isolate (9)
+ 9.81 set/language (0)
+ 9.82 set/location (0)
+ 9.83 set/sys_location (9)
+ 9.84 set/logininfo (0)
+ 9.85 set/lockout (9)
+ 9.86 set/name (0)
+ 9.87 set/node (9)
+ 9.88 set/obscount (9)
+ 9.89 set/page (0)
+ 9.90 set/password (9)
+ 9.91 set/pinginterval (9)
+ 9.92 set/privilege (9)
+ 9.93 set/spider (5)
+ 9.94 set/sys_qra (9)
+ 9.95 set/qra (0)
+ 9.96 set/qth (0)
+ 9.97 set/talk (0)
+ 9.98 set/wcy (0)
+ 9.99 set/wwv (0)
+ 9.100 set/wx (0)
+ 9.101 show/baddx (1)
+ 9.102 show/badnode (6)
+ 9.103 show/badspotter (1)
+ 9.104 show/configuration (0)
+ 9.105 show/configuration/node (0)
+ 9.106 show/connect (1)
+ 9.107 show/date (0)
+ 9.108 show/debug (9)
+ 9.109 show/dx (0)
+ 9.110 show/dxcc (0)
+ 9.111 show/files (0)
+ 9.112 show/filter (0)
+ 9.113 show/filter (extended for sysops) (5)
+ 9.114 show/hops (8)
+ 9.115 show/isolate (1)
+ 9.116 show/lockout (9)
+ 9.117 show/log (8)
+ 9.118 show/moon (0)
+ 9.119 show/muf (0)
+ 9.120 show/node (1)
+ 9.121 show/prefix (0)
+ 9.122 show/program (5)
+ 9.123 show/qra (0)
+ 9.124 show/qrz (0)
+ 9.125 show/route (0)
+ 9.126 show/satellite (0)
+ 9.127 show/sun (0)
+ 9.128 show/time (0)
+ 9.129 show/wcy (0)
+ 9.130 show/wwv (0)
+ 9.131 shutdown (5)
+ 9.132 spoof (9)
+ 9.133 stat/db (5)
+ 9.134 stat/channel (5)
+ 9.135 stat/msg (5)
+ 9.136 stat/route_node (5)
+ 9.137 stat/route_user (5)
+ 9.138 stat/user (5)
+ 9.139 sysop (0)
+ 9.140 talk (0)
+ 9.141 type (0)
+ 9.142 who (0)
+ 9.143 wx (0)
+ 9.144 wx (enhanced for sysops) (5)
______________________________________________________________________
of protection for these nodes.
- This is achieved by using filtering on a route basis. There is a
- default setting to help to protect the network, especially useful for
- new and inexperienced SysOps. The idea is simple. When Spider is
- started for the first time and a connection is made to or from another
- node, the default is to only send the nodes you already have that are
- in your own zone. For example, in the UK the default setting would be
- to send only UK nodes to any connection. This can be filtered further
- (down to a single node if needed) or expanded as required.
+ In fact DXSpider has had a simple system for some time which is called
+ isolation. This is similar to what in other systems such as clx, is
+ called passive mode. A more detailed explanation of isolation is given
+ further below. This system is still available and, for simple
+ networks, is probably all that you need.
+ The new functionality introduced in version 1.48 allows filtering the
+ node and user protocol frames on a "per interface" basis. We call this
+ route filtering. This is used instead of isolation.
+
+
+ What this really means is that you can control more or less completely
+ which user and node management PC protocol frames pass to each of your
+ partner nodes. You can also limit what comes into your node from your
+ partners. It is even possible to control the settings that your
+ partner node has for the routing information that it sends to you
+ (using the rcmd command).
+
1.2. Route Filters
- As mentioned in the introduction, a default setting exists. If this
- is all you want to use then that is fine, you have nothing else to do.
- However, if you want to make any alterations then you need to know a
- bit about filters.
+ Initially when route filters were being tested we generated a
+ "default" filter. Unfortunately it quickly became apparent that this
+ might suit the UK cluster network but didn't really fit anybody else.
+ However using a default filter is an appropriate thing to do. How, is
+ explained further on.
+
+ The first thing that you must do is determine whether you need to use
+ route filtering at all. If you are a "normal" node with two or three
+ partners and you arranged in an "official" non-looping tree type
+ network, then you do not need to do route filtering and you will feel
+ a lot better for not getting involved. If you are successfully using
+ isolation then you also probably don't need to use route filtering.
+ To put it simply, you should not mix Isolation and Route Filtering.
+ It will work, of sorts, but you will not get the expected results. If
+ you are using Isolation sucessfully at the moment, do not get involved
+ in Route Filtering unless you have a good supply of aspirin! Once you
+ have started down the road of Route Filtering, do not use Isolation
+ either. Use one or the other, not both.
- It is possible to reset the default setting for node connections
- should you wish to do so, however this can be dangerous to the network
- unless you have some experience in how all this works.... be careful!
- It is also possible to change settings for one connection only. You
- can, therefore, have many different filters set dependent on the
- amount of node links you have.
+
+ You will only require this functionality if you are "well-connected".
+ What that means is that you are connected to several different parts
+ of (say) the EU cluster and, at the same time, also connected to two
+ or three places in the US which, in turn are connected back to the EU.
+ This is called a "loop" and if you are seriously looped then you need
+ filtering.
I should at this stage give a little bit of background on filters.
sysop.
- 1.3. The default_node filter
- As discussed previously, a default setting exists that only sends
- nodes from your own zone. This can be overridden by using the
- default_node filter option like this ...
+ Anyway, without further discouragement, let me start the process of
+ explanation.
+ 1.3. The node_default filter
+
+ All normal systems should have a default routing filter and it should
+ usually be set to send only the normal, unlooped, view of your
+ "national" network. Here in the UK that means nodes from the UK and
+ Eire, in EU it is more complex as the networks there grew up in a more
+ intertwined way.
- reject/route default_node <filter_option>
- or
- accept/route default_node <filter_option>
+ The generic commands are:-
+ reject/route node_default <filter_option>
+
+ or
+
+ accept/route node_default <filter_option>
+
+
where filter_option is one of the following ...
call_dxcc <numbers>
call_itu <numbers>
call_zone <numbers>
- origin_dxcc <numbers>
- origin_itu <numbers>
- origin_zone <numbers>
+ channel_dxcc <numbers>
+ channel_itu <numbers>
+ channel_zone <numbers>
+ Please be careful if you alter this setting, it will affect ALL your
+ links! Remember, this is a default filter for node connections, not a
+ per link default.
+ For the default routing filter then you have two real choices: either
+ a "national" view or the "safe" option of only your own callsign.
+ Examples of each (for my node: GB7DJK) are:-
+
+
+
+ acc/route node_default call_dxcc 61,38
+ acc/route node_default call gb7djk
+
+
+
+
+ GB7DJK uses the first of these. The DXCC countries can be obtained
+ from the show/prefix command.
+
+
+ The example filters shown control output TO all your partner nodes
+ unless they have a specific filter applied to them (see next section).
+
+
+ It is also possible to control the incoming routing information that
+ you are prepared to accept FROM your partner nodes. The reason this is
+ necessary is to make sure that stuff like mail, pings and similar
+ commands a) go down the correct links and b) don't loop around
+ excessively. Again using GB7DJK as an example a typical default input
+ filter would be something like:
+
+
+
+ rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
+
+
+
+
+ What this does is accept node and user information for our national
+ network from nodes that are in our national network, but rejects such
+ information from anyone else. Although it doesn't explicitly say so,
+ by implication, any other node information (not from the UK and Eire)
+ is accepted.
+
+
+ As I imagine it will take a little while to get one's head around all
+ of this you can study the effect of any rules that you try by watching
+ the debug output after having done:-
+
+
+
+ set/debug filter
+
+
+
+
+ After you have got tired of that, to put it back the way it was:-
+
+
+
+ unset/debug filter
+
- Please be careful if you alter this setting, it will affect ALL your
- links!
1.4. General route filtering
- where filter_option is one of the following ...
+ Here are some examples of route filters ...
- call <prefixes>
- call_dxcc <numbers>
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes>
- origin_dxcc <numbers>
- origin_itu <numbers>
- origin_zone <numbers>
+ rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes)
+ rej/route all (equiv to [very] restricted mode)
+ acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+ In practice you will either be opening the default filter out for a
+ partner by defining a specific filter for that callsign:-
- Here are some examples of route filters ...
+ acc/route gb7baa all
+ acc/route gb7baa input all
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
- rej/route all (equiv to [very] restricted mode)
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
+
+ or restricting it quite a lot, in fact making it very nearly like an
+ isolated node, like this:-
+
+
+
+ acc/route pi4ehv-8 call gb7djk
+ rej/route pi4ehv-8 input call_dxcc 61,38
+
+ This last example takes everything except UK and Eire from PI4EHV-8
+ but only sends him my local configuration (just a PC19 for GB7DJK and
+ PC16s for my local users).
+
+
+ It is possible to write much more complex rules, there are up to 10
+ accept/reject pairs per callsign per filter. For more information see
+ the next section.
+
1.5. General filter rules
the DXSpider system. They all use the same general mechanism.
- In general terms you can create a 'reject' or an 'accept' filter which
+ 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 ...
-
- show/filter
+ show/filter
+
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
-
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.
clear/spots 1
+
+
+
To remove all the filter lines in the spot filter ...
You can filter in several different ways. The options are listed in
the various helpfiles for accept, reject and filter.
-
1.8. Default filters
Sometimes all that is needed is a general rule for node connects.
+ #
+ # 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.11. Hop Control on Specific Nodes
+ You can set a callsign specific hop count for any of the standard
+ filter options so:-
+ set/hops gb7djk spot 4
+ set/hops node_default route 10
+ set/hops gb7baa wcy 5
+ all work on their specific area of the protocol.
+ The set/hops command overrides any hops that you have set otherwise.
+ You can set what hops have been set using the show/hops command.
-
-
-
-
-
-
-
-
-
-
-
-
- #
- # 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.11. Isolating networks
+ 1.12. Isolating networks
It is possible to isolate networks from each other on a "gateway" node
using the set/isolate <node_call> command.
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
- ];
-
-
-
+ for example). To do this, isolate the node in the normal way and use
+ an acc/spot >call< all filter to override the isolate.
2. Other filters
-
-
-
-
-
-
-
-
-
-
-
-
# 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)
etc in a particular country.
- 2.2. Filtering DX callouts (Depricated)
- From version 1.47, this method is replaced by the command set/baddx
+ 2.2. Filtering words from text fields in Announce, Talk and DX spots
+ From version 1.48 onwards the interface to this has changed. You can
+ now use the commands set/badword to add words that you are not
+ prepared to see on the cluster, unset/badword to allow that word again
+ and show/badword to list the words that you have set.
- 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 ....
+ If you have a previous /spider/data/badwords, the first time you start
+ the node, it will read and convert this file to the new commands. The
+ old style file will then be removed.
+ 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
+ There are a number of commands that control whether a spot progresses
+ any further by regarding it as "bad" in some way.
+ A DX Spot has a number of fields which can be checked to see whether
+ they contain "bad" values, they are: the DX callsign itself, the
+ Spotter and the Originating Node.
+ There are a set of commands which allow the sysop to control whether a
+ spot continues:-
+ set/baddx
+ set/badspotter
+ set/badnode
+ These work in the same as the set/badword command, you can add any
+ words or callsigns or whatever to the appropriate database. For
+ example, to stop a spot from a particular node you do:
- # the list of dx spot addresses that we don't store and don't pass on
- package DXProt;
+ set/badnode gb7djk gb7dxc
- @baddx = qw
-
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
- );
+ a bad spotter:
- Again, this is simply a list of names we do not want to see in the
- spotted field of a DX callout.
+ set/badspotter b0mb p1rat nocall
- 2.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 ...
+ and some bad dx:
- # Below is a list of words we do not wish to see on the cluster
- grunge grunged grunging
- splodge splodger splodging
- grince
- fluffle
+ set/baddx video wsjt
- 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.
+ You can remove a word using the appropriate unset command
+ (unset/baddx, unset/badspotter, unset/badnode) or list them using one
+ of show/baddx, show/badspotter and show/badnode.
3. Mail
The cluster mail is automatically deleted after 30 days unless the
sysop sets the "keep" flag using the msg command.
+
3.1. Personal mail
Personal mail is sent using the sp command. This is actually the
default method of sending mail and so a simple s for send will do. A
full list of the send commands and options is in the command set
section, so I will not duplicate them here.
-
-
3.2. Bulletin mail
Bulletin mail is sent by using the sb command. This is one of the
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #
- # 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 = (
- );
+ #
+ # 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 = (
+ );
-
-
-
-
-
-
-
-
- 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
+ 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
Times read: 0
G0VGS de GB7MBC 28-Jan-2001 1308Z >
-
-
-
-
3.6. Filtering mail
This is described in the section on Other filters so I will not
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)
using the Forward.pl file very carefully.
- 4. Databases
+ 4. Scripts
+
+ From 1.48 onwards it will become increasingly possible to control
+ DXSpider's operation with scripts of various kinds.
+
+
+ In the first instance, in 1.48, the sysop can create, with their
+ favorite text editor, files in the directory /spider/scripts which
+ contain any legal command for a callsign or class of connection which
+ will be executed at logon.
+
+
+
+ The filename is the callsign of the connection that you want the
+ script to operate on, eg: /spider/scripts/g1tlh. The filenames are
+ always in lower case on those architectures where this makes a
+ difference.
+
+
+ In addition to the callsign specific scripts there are three others:-
+
+
+
+
+
+
+ startup
+ user_default
+ node_default
+
+
+
+
+ The startup script is executed immediately after all initialisation of
+ the node is done, but before any connections are possible.
+
+
+ The user_default script is executed for every user that does NOT
+ already have a specific script.
+
+
+ The node_default script is executed for every node that doesn't have a
+ specific script.
+
+
+ There are a couple of examples in the /spider/scripts directory.
+
+
+ 5. Databases
Spider allows the creation of local or remote databases. It supports
chained databases, allowing several different databases to be scanned
database but will expand with time.
- 4.1. Creating databases
+ 5.1. Creating databases
Creating a database could not be more simple. All the commands are
sent from the cluster prompt as the sysop user.
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...
chain can be a remote database.
- 4.2. Importing databases
+ 5.2. Importing databases
The only databases that Spider can currently import are the standard
AK1A databases such as OBLAST or the DB0SDX qsl and address database.
does not exist.
- 4.3. Checking available databases
+ 5.3. Checking available databases
Once a database is created, you will want to check that it has been
added. To do this use the dbavail command. This will output the
- 4.4. Looking up databases
+ 5.4. Looking up databases
To look for information in a defined database, simply use the dbshow
command, for example ...
Now you can simply use show/buckmaster or an abreviation.
- 4.5. Removing databases
+ 5.5. Removing databases
To delete an existing database you use the dbremove command. For
example ...
created from scratch if you still required it.
- 5. Information, files and useful programs
+ 6. Information, files and useful programs
- 5.1. MOTD
+ 6.1. MOTD
One of the more important things a cluster sysop needs to do is to get
information to his users. The simplest way to do this is to have a
to the cluster.
- 5.2. Downtime message
+ 6.2. MOTD_NOR
+
+ This message of the day file lives in the same directory as the
+ standard motd file but is only sent to non-registered users. Once
+ registered they will receive the same message as any other user.
+
+
+ 6.3. Downtime message
If for any reason the cluster is down, maybe for upgrade or
maintenance but the machine is still running, a message can be sent to
actually running.
- 5.3. Other text messages
+
+
+
+ 6.4. Other text messages
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
like. These can be listed by the user with the command ....
+
show/files
- type news
-
-
+ type news
- To look what is in the bulletin directory you issue the command ....
+ To look what is in the bulletin directory you issue the command ....
- 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) >
+ 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) >
The page length will of course depend on what you have it set to!
- 5.4. The Aliases file
+ 6.5. 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
-
-
-
-
-
-
-
-
-
#!/usr/bin/perl
# provide some standard aliases for commands for terminally
the results once you have set an alias.
- 5.5. Console.pl
+ 6.6. Console.pl
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
edit the file with your favourite editor.
- 5.6. Updating kepler data
+ 6.7. Updating kepler data
Spider has a powerful and flexible show/satellite command. In order
for this to be accurate, the kepler data has to be updated regularly.
- 5.7. The QRZ callbook
+ 6.8. The QRZ callbook
The command sh/qrz will only work once you have followed a few simple
steps. First you need to get a user ID and password from qrz.com.
proprieter of qrz.com for allowing this access.
- 6. CVS
+ 6.9. Scripts
+
+ The directory /spider/scripts is used for several things. Firstly it
+ contains a file called startup that can be used to call in any changes
+ to the cluster from the default settings on startup. Examples of this
+ include how many spots it is possible to get with the sh/dx command,
+ whether you want registration/passwords to be permanently on etc. An
+ example file is shown below and is included in the distribution as
+ startup.issue.
+
+
+
+ #
+ # startup script example
+ #
+ # set maximum no of spots allowed to 100
+ # set/var $Spot::maxspots = 1
+ #
+ # Set registration on
+ # set/var $main::reqreg = 1
+ #
+ # Set passwords on
+ # set/var $main::passwdreq = 1
+ #
+
+
+
+
+ Secondly, it is used to store the login scripts for users. Currently
+ this can only be done by the sysop but it is envisaged that eventually
+ users will be able to set their own. An example is included in the
+ distibution but here is a further example.
+
+
+
+ #
+ # G0FYD
+ #
+ blank +
+ sh/wwv 3
+ blank +
+ sh/dx
+ blank +
+ t g0jhc You abt?
+ blank +
+
+
+
+
+ The lines in between commands can simply insert a blank line or a
+ character such as a + sign to make the output easier to read.
+
+
+
+
+ 7. Security
+
+ From version 1.49 DXSpider has some additional security features.
+ These are not by any means meant to be exhaustive, however they do
+ afford some security against piracy. These two new features can be
+ used independently of each other or in concert to tighten the
+ security.
+
+
+ 7.1. Registration
+
+ The basic principle of registration is simple. If a user is not
+ registered by the sysop, then they have read-only access to the
+ cluster. The only thing they can actually send is a talk or a message
+ to the sysop. In order for them to be able to spot, send announces or
+ talks etc the sysop must register them with the set/register command,
+ like this ...
+
+
+
+ set/register g0vgs
+
+
+
+
+ The user g0vgs can now fully use the cluster. In order to enable
+ registration, you can issue the command ...
+
+
+
+ set/var $main::reqreg = 1
+
+
+
+
+ Any users that are not registered will now see the motd_nor file
+ rather than the motd file as discussed in the Information, files and
+ useful programs section.
+
+
+ Entering this line at the prompt will only last for the time the
+ cluster is running of course and would not be present on a restart.
+ To make the change permanent, add the above line to
+ /spider/scripts/startup. To read more on the startup file, see the
+ section on Information, files and useful programs.
+
+
+ To unregister a user use unset/register and to show the list of
+ registered users, use the command show/register.
+
+
+ 7.2. Passwords
+
+ At the moment, passwords only affect users who login to a DXSpider
+ cluster node via telnet. If a user requires a password, they can
+ either set it themselves or have the sysop enter it for them by using
+ the set/password command. Any users who already have passwords, such
+ as remote sysops, will be asked for their passwords automatically by
+ the cluster. Using passwords in this way means that the user has a
+ choice on whether to have a password or not. To force the use of
+ passwords at login, issue the command ...
+
+
+
+ set/var $main::passwdreq = 1
+
+ at the cluster prompt. This can also be added to the
+ /spider/scripts/startup file as above to make the change permanent.
+
+
+ Of course, if you do this you will have to assign a password for each
+ of your users. If you were asking them to register, it is anticipated
+ that you would ask them to send you a message both to ask to be
+ registered and to give you the password they wish to use.
+
+
+ Should a user forget their password, it can be reset by the sysop by
+ first removing the existing password and then setting a new one like
+ so ...
+
+
+
+ unset/password g0vgs
+ set/password g0vgs new_password
+
+
+
+
+
+ 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
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!!!
+ Please be aware that if you update your system using CVS, it is
+ possible that you could be running code that is very beta and not
+ fully tested. There is a possibility that it could be unstable.
I am of course assuming that you have a machine with both DXSpider and
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.
-
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.
- 7. The DXSpider command set
+ 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
is the permissions level needed to use the command.
- 7.1. accept/announce (0)
+ 9.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
- acc/ann by G,M,2
+
+ 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...
- 7.2. accept/announce (extended for sysops) (8)
+ 9.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
- 7.3. accept/route (8)
+ 9.3. accept/route (8)
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
routing
origin_zone <numbers>
-
-
-
some examples:-
acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
+
+
+
You can use the tag 'all' to accept everything eg:
- 7.4. accept/spots (0)
+ 9.4. accept/spots (0)
accept/announce [0-9] <pattern> Set an accept filter line for spots
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
acc/spot 3 all
+
+
+
but this probably for advanced users...
- 7.5. accept/spots (extended for sysops) (8)
+ 9.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
- 7.6. accept/wcy (0)
+ 9.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
See HELP FILTER for information.
- 7.7. accept/wcy (extended for sysops) (8)
+ 9.7. accept/wcy (extended for sysops) (8)
accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
- accept/wcy node_default all
- set/hops node_default 10
+ accept/wcy node_default all
+ set/hops node_default 10
- 7.8. accept/wwv (0)
+ 9.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
See HELP FILTER for information.
- 7.9. accept/wwv (extended for sysops) (8)
+ 9.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
+
This version allows a sysop to set a filter for a callsign as well as
the default for nodes and users eg:-
-
- 7.10. announce (0)
+ 9.10. announce (0)
announce <text> Send an announcement to local users
sysop will override set/noannounce.
- 7.11. announce full (0)
+ 9.11. announce full (0)
announce full <text> Send an announcement cluster wide
- 7.12. announce sysop (5)
+ 9.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 7.13. apropos (0)
+ 9.13. apropos (0)
apropos <string> Search the help database
print the names of all the commands that may be relevant.
- 7.14. bye (0)
+ 9.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
- 7.15. catchup (5)
+ 9.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
Order is not important.
- 7.16. clear/spots (0)
+ 9.16. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
-
-
- 7.17. connect (5)
+ 9.17. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 7.18. dbavail (0)
+ 9.18. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 7.19. dbcreate (9)
+ 9.19. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
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
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' => [
..
..
databases. See DBSHOW for generic database enquiry
- 7.20. dbimport (9)
+ 9.20. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 7.21. dbremove (9)
+ 9.21. dbremove (9)
dbremove <dbname> Delete a database
For example:
+
DBREMOVE oblast
will remove the oblast database from the system and it will also
You have been warned.
- 7.22. dbshow (0)
+ 9.22. 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
- 7.23. debug (9)
+ 9.23. debug (9)
debug Set the cluster program into debug mode
finished.
- 7.24. directory (0)
+ 9.24. directory (0)
directory List messages
directory own List your own messages
You can combine some of the various directory commands together eg:-
+
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
- 7.25. directory (extended for sysops) (5)
+ 9.25. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 7.26. disconnect (8)
+ 9.26. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 7.27. dx (0)
+ 9.27. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
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 by G1TLH FR0G 144.600 he isn't on the cluster
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
cluster. See SHOW/BANDS for more information.
- 7.28. export (9)
+ 9.28. export (9)
export <msgno> <filename> Export a message to a file
EXPORT 2345 /tmp/a
- 7.29. export_users (9)
+ 9.29. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
- 7.30. forward/latlong (8)
+ 9.30. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 7.31. forward/opername (1)
+ 9.31. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 7.32. help (0)
+ 9.32. help (0)
help <cmd> Get help on a command
commands to look at with HELP.
- 7.33. init (5)
+ 9.33. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 7.34. kill (0)
+ 9.34. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
- 7.35. kill (5)
+ 9.35. kill (5)
kill <msgno> [<msgno> ...] Remove or erase a message from the system
kill from <call> Remove all messages from a callsign
As a sysop you can kill any message on the system.
-
- 7.36. kill full (5)
+ 9.36. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
-
-
- 7.37. links (0)
+ 9.37. links (0)
links Show which nodes are physically connected
- 7.38. load/aliases (9)
+ 9.38. load/aliases (9)
load/aliases Reload the command alias table
running in order for the changes to take effect.
-
- 7.39. 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.
-
-
- 7.40. load/badmsg (9)
+ 9.39. load/badmsg (9)
load/badmsg Reload the bad message table
deleted on receipt.
- 7.41. 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.
-
-
- 7.42. load/bands (9)
+ 9.40. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 7.43. load/cmd_cache (9)
+ 9.41. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
was just after a cluster restart.
- 7.44. load/forward (9)
+
+ 9.42. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 7.45. load/messages (9)
+ 9.43. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 7.46. load/prefixes (9)
+ 9.44. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 7.47. merge (5)
+ 9.45. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 7.48. msg (9)
+ 9.46. 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
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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
This will display more information on the message than DIR does.
- 7.49. pc (8)
+ 9.47. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
pc G1TLH Try doing that properly!!!
- 7.50. ping (1)
+ 9.48. ping (1)
ping <node> Check the link quality between nodes
- 7.51. rcmd (1)
+ 9.49. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
whether you have permission to send this command at all.
- 7.52. read (0)
+ 9.50. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 7.53. read (extended for sysops) (5)
+ 9.51. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 7.54. reject/announce
+ 9.52. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
but this probably for advanced users...
- 7.55. reject/announce (extended for sysops) (8)
+ 9.53. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
- 7.56. reject/route (8)
+ 9.54. reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
routing
- 7.57. reject/spots (0)
+ 9.55. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
but this probably for advanced users...
- 7.58. reject/spots (extended for sysops) (8)
+ 9.56. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
- 7.59. reject/wcy (0)
+ 9.57. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
- 7.60. reject/wcy (extended for sysops) (8)
+ 9.58. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 7.61. reject/wwv (0)
+ 9.59. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
See HELP FILTER for information.
- 7.62. reject/wwv (extended for sysops) (8)
+ 9.60. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
- 7.63. reply (0)
+ 9.61. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
- 7.64. send (0)
+ 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
is an alias for SEND PRIVATE
- 7.65. set/address (0)
+ 9.63. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 7.66. set/announce (0)
+ 9.64. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
- 7.67. set/arcluster (5)
+ 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
- 7.68. set/baddx (8)
+ 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
- 7.69. set/badnode (6)
+ 9.67. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 7.70. set/badspotter (8)
+ 9.68. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
FILTERing.
- 7.71. set/beep (0)
+ 9.69. set/beep (0)
set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 7.72. set/bbs (5)
+ 9.70. set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
- 7.73. set/clx (5)
+ 9.71. 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
- 7.74. set/debug (9)
+ 9.72. set/debug (9)
set/debug <name> Add a debug level to the debug set
You can remove a debug level with unset/debug <name>
- 7.75. set/dx (0)
+ 9.73. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
- 7.76. set/dxgrid (0)
+ 9.74. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 7.77. set/dxnet (5)
+ 9.75. 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
- 7.78. set/echo (0)
+ 9.76. set/echo (0)
set/echo Make the cluster echo your input
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 7.79. set/here (0)
+ 9.77. set/here (0)
set/here Set the here flag
- 7.80. set/homenode (0)
+ 9.78. set/homenode (0)
set/homenode <node_call> Set your home cluster
- 7.81. set/hops (8)
+ 9.79. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
creates a filter and works in conjunction with the filter system.
- 7.82. set/isolate (9)
+ 9.80. set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
You can remove the isolation with the command unset/isolate.
- 7.83. set/language (0)
+ 9.81. 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).
- 7.84. set/location (0)
+ 9.82. set/location (0)
set/location <lat and long> Set your latitude and longitude
- 7.85. set/sys_location (9)
+ 9.83. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
- 7.86. set/logininfo (0)
+ 9.84. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 7.87. set/lockout (9)
+ 9.85. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 7.88. set/name (0)
+ 9.86. set/name (0)
set/name <your_name> Set your name
set/name Dirk
- 7.89. set/node (9)
+ 9.87. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
To see what your nodes are set to, use the show/nodes command.
- 7.90. set/obscount (9)
+ 9.88. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 7.91. set/page (0)
+ 9.89. set/page (0)
set/page <n> Set the number of lines per page
- 7.92. set/password (9)
+ 9.90. set/password (9)
set/password <callsign> <string> Set a users password
type password.
- 7.93. set/pinginterval (9)
+ 9.91. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 7.94. set/privilege (9)
+ 9.92. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
connection your privilege will automatically be set to 0.
- 7.95. set/spider (5)
+ 9.93. 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
- 7.96. set/sys_qra (9)
+ 9.94. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 7.97. set/qra (0)
+ 9.95. set/qra (0)
set/qra <locator> Set your QRA locator
- 7.98. set/qth (0)
+ 9.96. set/qth (0)
set/qth <your QTH> Set your QTH
- 7.99. set/talk (0)
+ 9.97. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 7.100. set/wcy (0)
+ 9.98. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 7.101. set/wwv (0)
+ 9.99. 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.
- 7.102. set/wx (0)
+ 9.100. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
- 7.103. show/baddx (1)
+ 9.101. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 7.104. show/badnode (6)
+ 9.102. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 7.105. show/badspotter (1)
+ 9.103. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 7.106. show/configuration (0)
+ 9.104. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 7.107. show/configuration/node (0)
+ 9.105. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 7.108. show/connect (1)
+ 9.106. 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.
- 7.109. show/date (0)
+ 9.107. show/date (0)
show/date [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 7.110. show/debug (9)
+ 9.108. show/debug (9)
show/debug Show what levels of debug you are logging
The levels can be set with set/debug
- 7.111. show/dx (0)
+ 9.109. show/dx (0)
show/dx [options] interrogate the spot database
- 7.112. show/dxcc (0)
+ 9.110. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
- 7.113. show/files (0)
+ 9.111. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
See also TYPE - to see the contents of a file.
- 7.114. show/filter (0)
+ 9.112. show/filter (0)
show/filter Show the filters you have set
displays all the filters set - for all the various categories.
- 7.115. show/filter (extended for sysops) (5)
+ 9.113. 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.
- 7.116. show/hops (8)
+ 9.114. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 7.117. show/isolate (1)
+ 9.115. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 7.118. show/lockout (9)
+ 9.116. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 7.119. show/log (8)
+ 9.117. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 7.120. show/moon (0)
+ 9.118. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
- 7.121. show/muf (0)
+ 9.119. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
terrible accurate, but it is included for completeness.
- 7.122. show/node (1)
+ 9.120. show/node (1)
show/node [<node_call> ...] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 7.123. show/prefix (0)
+ 9.121. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
- 7.124. show/program (5)
+ 9.122. show/program (5)
show/program Show the locations of all the included program modules
from.
- 7.125. show/qra (0)
+ 9.123. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
- 7.126. show/qrz (0)
+ 9.124. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
- 7.127. show/route (0)
+ 9.125. show/route (0)
show/route <callsign> Show the route to <callsign>
- 7.128. show/satellite (0)
+ 9.126. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
- 7.129. show/sun (0)
+ 9.127. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
- 7.130. show/time (0)
+ 9.128. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 7.131. show/wcy (0)
+ 9.129. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 7.132. show/wwv (0)
+ 9.130. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 7.133. shutdown (5)
+ 9.131. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 7.134. spoof (9)
+ 9.132. spoof (9)
spoof <callsign> <command> Run commands as another user
- 7.135. stat/db (5)
+ 9.133. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
- 7.136. stat/channel (5)
+ 9.134. stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
Only the fields that are defined (in perl term) will be displayed.
- 7.137. stat/msg (5)
+ 9.135. stat/msg (5)
stat/msg <msgno> Show the status of a message
displayed.
- 7.138. stat/route_node (5)
+ 9.136. stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
- 7.139. stat/route_user (5)
+ 9.137. stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
- 7.140. stat/user (5)
+ 9.138. stat/user (5)
stat/user <callsign> Show the full status of a user
Only the fields that are defined (in perl term) will be displayed.
- 7.141. sysop (0)
+ 9.139. sysop (0)
sysop Regain your privileges if you login remotely
case sensitive.
- 7.142. talk (0)
+ 9.140. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
- 7.143. type (0)
+ 9.141. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
content.
- 7.144. who (0)
+ 9.142. who (0)
who Show who is physically connected locally
what sort of connection they have
- 7.145. wx (0)
+ 9.143. wx (0)
wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users
extreme that may indicate enhanced conditions
- 7.146. wx (enhanced for sysops) (5)
+ 9.144. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
projects / spider.git / blobdiff