- The DXSpider Administration Manual v1.48
- Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.48 August 2001 revision 1.1
+ The DXSpider Administration Manual v1.50
+ Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll,
+ K1XX, (k1xx@ptcnh.net)
+ February 2003 revision 0.3
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1. Routing and Filtering
-
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.1 Personal mail
3.2 Bulletin mail
3.3 Forward.pl
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 Connecting logging programs
+
+ 7. Java Web applet
+ 8. Web based statistics
+ 9. Security
+ 9.1 Registration
+ 9.2 Passwords
+
+ 10. CVS
+ 10.1 CVS from a Linux platform
+ 10.2 CVS from a Windows platform
+
+ 11. The DXSpider command set
+ 11.1 accept/announce (0)
+ 11.2 accept/announce (extended for sysops) (8)
+ 11.3 accept/route (8)
+ 11.4 accept/spots (0)
+ 11.5 accept/spots (extended for sysops) (8)
+ 11.6 accept/wcy (0)
+ 11.7 accept/wcy (extended for sysops) (8)
+ 11.8 accept/wwv (0)
+ 11.9 accept/wwv (extended for sysops) (8)
+ 11.10 announce (0)
+ 11.11 announce full (0)
+ 11.12 announce sysop (5)
+ 11.13 apropos (0)
+ 11.14 bye (0)
+ 11.15 catchup (5)
+ 11.16 clear/announce (8)
+ 11.17 clear/route (8)
+ 11.18 clear/spots (0)
+ 11.19 clear/spots (extended for sysops) (8)
+ 11.20 clear/wcy (0)
+ 11.21 clear/wcy (extended for sysops) (8)
+ 11.22 clear/wwv (0)
+ 11.23 clear/wwv (extended for sysops) (8)
+ 11.24 connect (5)
+ 11.25 dbavail (0)
+ 11.26 dbcreate (9)
+ 11.27 dbimport (9)
+ 11.28 dbremove (9)
+ 11.29 dbshow (0)
+ 11.30 debug (9)
+ 11.31 delete/user (9)
+ 11.32 demonstrate (9)
+ 11.33 directory (0)
+ 11.34 directory (extended for sysops) (5)
+ 11.35 disconnect (8)
+ 11.36 dx (0)
+ 11.37 export (9)
+ 11.38 export_users (9)
+ 11.39 filtering (0)
+ 11.40 forward/latlong (8)
+ 11.41 forward/opername (1)
+ 11.42 help (0)
+ 11.43 init (5)
+ 11.44 kill (0)
+ 11.45 kill (5)
+ 11.46 kill full (5)
+ 11.47 kill/expunge (6)
+ 11.48 links (0)
+ 11.49 load/aliases (9)
+ 11.50 load/badmsg (9)
+ 11.51 load/badwords (9)
+ 11.52 load/bands (9)
+ 11.53 load/cmd_cache (9)
+ 11.54 load/forward (9)
+ 11.55 load/messages (9)
+ 11.56 load/prefixes (9)
+ 11.57 merge (5)
+ 11.58 msg (9)
+ 11.59 pc (8)
+ 11.60 ping (1)
+ 11.61 rcmd (1)
+ 11.62 read (0)
+ 11.63 read (extended for sysops) (5)
+ 11.64 reject/announce
+ 11.65 reject/announce (extended for sysops) (8)
+ 11.66 reject/route (8)
+ 11.67 reject/spots (0)
+ 11.68 reject/spots (extended for sysops) (8)
+ 11.69 reject/wcy (0)
+ 11.70 reject/wcy (extended for sysops) (8)
+ 11.71 reject/wwv (0)
+ 11.72 reject/wwv (extended for sysops) (8)
+ 11.73 reply (0)
+ 11.74 send (0)
+ 11.75 set/address (0)
+ 11.76 set/announce (0)
+ 11.77 set/arcluster (5)
+ 11.78 set/baddx (8)
+ 11.79 set/badnode (6)
+ 11.80 set/badspotter (8)
+ 11.81 set/badword (8)
+ 11.82 set/beep (0)
+ 11.83 set/bbs (5)
+ 11.84 set/clx (5)
+ 11.85 set/debug (9)
+ 11.86 set/dx (0)
+ 11.87 set/dxgrid (0)
+ 11.88 set/dxnet (5)
+ 11.89 set/echo (0)
+ 11.90 set/email (0)
+ 11.91 set/here (0)
+ 11.92 set/homenode (0)
+ 11.93 set/hops (8)
+ 11.94 set/isolate (9)
+ 11.95 set/language (0)
+ 11.96 set/location (0)
+ 11.97 set/sys_location (9)
+ 11.98 set/logininfo (0)
+ 11.99 set/lockout (9)
+ 11.100 set/name (0)
+ 11.101 set/node (9)
+ 11.102 set/obscount (9)
+ 11.103 set/page (0)
+ 11.104 set/password (0)
+ 11.105 set/password (9)
+ 11.106 set/pinginterval (9)
+ 11.107 set/privilege (9)
+ 11.108 set/spider (5)
+ 11.109 set/sys_qra (9)
+ 11.110 set/qra (0)
+ 11.111 set/qth (0)
+ 11.112 set/register (9)
+ 11.113 set/talk (0)
+ 11.114 set/wcy (0)
+ 11.115 set/wwv (0)
+ 11.116 set/wx (0)
+ 11.117 show/baddx (1)
+ 11.118 show/badnode (6)
+ 11.119 show/badspotter (1)
+ 11.120 show/badword (1)
+ 11.121 show/configuration (0)
+ 11.122 show/configuration/node (0)
+ 11.123 show/connect (1)
+ 11.124 show/date (0)
+ 11.125 show/debug (9)
+ 11.126 show/dx (0)
+ 11.127 show/dxcc (0)
+ 11.128 sh/dxstats (0)
+ 11.129 show/files (0)
+ 11.130 show/filter (0)
+ 11.131 show/filter (extended for sysops) (5)
+ 11.132 show/hfstats (0)
+ 11.133 show/hftable (0)
+ 11.134 show/hops (8)
+ 11.135 show/isolate (1)
+ 11.136 show/lockout (9)
+ 11.137 show/log (8)
+ 11.138 show/moon (0)
+ 11.139 show/muf (0)
+ 11.140 show/newconfiguration (0)
+ 11.141 show/newconfiguration/node (0)
+ 11.142 show/node (1)
+ 11.143 show/prefix (0)
+ 11.144 show/program (5)
+ 11.145 show/qra (0)
+ 11.146 show/qrz (0)
+ 11.147 show/registered (9)
+ 11.148 show/route (0)
+ 11.149 show/satellite (0)
+ 11.150 show/sun (0)
+ 11.151 show/time (0)
+ 11.152 show/vhfstats (0)
+ 11.153 show/vhftable (0)
+ 11.154 show/wcy (0)
+ 11.155 show/wwv (0)
+ 11.156 shutdown (5)
+ 11.157 spoof (9)
+ 11.158 stat/db (5)
+ 11.159 stat/channel (5)
+ 11.160 stat/msg (5)
+ 11.161 stat/route_node (5)
+ 11.162 stat/route_user (5)
+ 11.163 stat/user (5)
+ 11.164 sysop (0)
+ 11.165 talk (0)
+ 11.166 type (0)
+ 11.167 who (0)
+ 11.168 wx (0)
+ 11.169 wx (enhanced for sysops) (5)
______________________________________________________________________
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
- reject/route default_node <filter_option>
+ 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.
- or
- accept/route default_node <filter_option>
+
+ The generic commands are:-
+
+ reject/route node_default <filter_option>
+
+ or
+
+ accept/route node_default <filter_option>
call_dxcc <numbers>
call_itu <numbers>
call_zone <numbers>
- origin <prefixes>
- origin_dxcc <numbers>
- origin_itu <numbers>
- origin_zone <numbers>
+ channel <prefixes>
+ channel_dxcc <numbers>
+ channel_itu <numbers>
+ channel_zone <numbers>
+
+ Please be careful if you alter this setting, it will affect ALL your
+ links! Remember, this is a default filter for node connections, not a
+ per link default.
+ For the default routing filter then you have two real choices: either
+ a "national" view or the "safe" option of only your own callsign.
+ Examples of each (for my node: GB7DJK) are:-
+
+
+
+ acc/route node_default call_dxcc 61,38
+ acc/route node_default call gb7djk
+
+
+
+ GB7DJK uses the first of these. The DXCC countries can be obtained
+ from the show/prefix command.
+
+
+ The example filters shown control output TO all your partner nodes
+ unless they have a specific filter applied to them (see next section).
+
+
+ It is also possible to control the incoming routing information that
+ you are prepared to accept FROM your partner nodes. The reason this is
+ necessary is to make sure that stuff like mail, pings and similar
+ commands a) go down the correct links and b) don't loop around
+ excessively. Again using GB7DJK as an example a typical default input
+ filter would be something like:
+
+
+
+ rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
+
+
+
+ What this does is accept node and user information for our national
+ network from nodes that are in our national network, but rejects such
+ information from anyone else. Although it doesn't explicitly say so,
+ by implication, any other node information (not from the UK and Eire)
+ is accepted.
+
+
+ As I imagine it will take a little while to get one's head around all
+ of this you can study the effect of any rules that you try by watching
+ the debug output after having done:-
+
+
+
+ set/debug filter
+
+
+
+ After you have got tired of that, to put it back the way it was:-
+
+
+
+ unset/debug filter
- Please be careful if you alter this setting, it will affect ALL your
- links!
1.4. General route filtering
+ Here are some examples of route filters ...
- where filter_option is one of the following ...
+ 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)
- call <prefixes>
- call_dxcc <numbers>
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes>
- origin_dxcc <numbers>
- origin_itu <numbers>
- origin_zone <numbers>
+ In practice you will either be opening the default filter out for a
+ partner by defining a specific filter for that callsign:-
+ acc/route gb7baa all
+ acc/route gb7baa input all
- Here are some examples of route filters ...
+ or restricting it quite a lot, in fact making it very nearly like an
+ isolated node, like this:-
- 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)
+ 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 ...
-
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
-
There is clear/xxxx command for each type of filter.
-
-
- show/filter
-
-
+ show/filter
-
then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
-
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
-
But in that case you might only be interested in iota and say:-
-
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.
-
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'.
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 ...
+ To remove all the filter lines in the spot filter ...
- clear/spots all
+ clear/spots all
-
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
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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
#
# hop table construction
#
%nodehops =
-
+ (
GB7ADX => { 11 => 8,
12 => 8,
16 => 8,
19 => 8,
21 => 8,
},
- };
-
-
+ );
how the file works.
+ SHould any of the nodecalls include an ssid, it is important to wrap
+ the whole call in single quotes, like this ...
+
+
+
+ 'DB0FHF-15' => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+
+
+ If you do not do this, you will get errors and the file will not work
+ as expected.
+
+
You can alter this file at any time, including whilst the cluster is
running. If you alter the file during runtime, the command load/hops
will bring your changes into effect.
+ 1.11. Hop Control on Specific Nodes
+
+ You can set a callsign specific hop count for any of the standard
+ filter options so:-
+
+
- 1.11. Isolating networks
+ set/hops gb7djk spot 4
+ set/hops node_default route 10
+ set/hops gb7baa wcy 5
+
+
+
+ all work on their specific area of the protocol.
+
+
+ The set/hops command overrides any hops that you have set otherwise.
+
+
+ You can show what hops have been set using the show/hops command.
+
+
+ 1.12. Isolating networks
It is possible to isolate networks from each other on a "gateway" node
using the set/isolate <node_call> command.
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)
+ # 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;
-
-
- # 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 = (
- );
-
-
+ @badmsg = (
+ );
etc in a particular country.
- 2.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 ....
+ 2.2. Filtering words from text fields in Announce, Talk and DX spots
+ From version 1.48 onwards the interface to this has changed. You can
+ now use the commands set/badword to add words that you are not
+ prepared to see on the cluster, unset/badword to allow that word again
+ and show/badword to list the words that you have set.
+ If you have a previous /spider/data/badwords, the first time you start
+ the node, it will read and convert this file to the new commands. The
+ old style file will then be removed.
+ 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
+ There are a number of commands that control whether a spot progresses
+ any further by regarding it as "bad" in some way.
+ A DX Spot has a number of fields which can be checked to see whether
+ they contain "bad" values, they are: the DX callsign itself, the
+ Spotter and the Originating Node.
+ There are a set of commands which allow the sysop to control whether a
+ spot continues:-
+ set/baddx
+ set/badspotter
+ set/badnode
- # the list of dx spot addresses that we don't store and don't pass on
+ 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:
- package DXProt;
-
- @baddx = qw
-
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
- );
+ set/badnode gb7djk gb7dxc
- Again, this is simply a list of names we do not want to see in the
- spotted field of a DX callout.
+ a bad spotter:
- 2.3. Filtering words from text fields in Announce, Talk and DX spots
+ set/badspotter b0mb p1rat nocall
- 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 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.
- You can reload the file from the cluster prompt as sysop with
- load/badwords.
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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
#
# this is an example message forwarding file for the system
#
-
Simply insert a bulletin address and state in the brackets where you
wish that mail to go. For example, you can see here that mail sent to
"UK" will only be sent to the UK links and not to PA4AB-14.
To force the cluster to reread the file use load/forward
+ NB: If a user tries to send mail to a bulletin address that does not
+ exist in this file, they will get an error.
+
3.4. The msg command
-
-
-
-
-
-
-
-
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
-
These commands are simply typed from within the cluster as the sysop
user.
-
-
3.6. Filtering mail
This is described in the section on Other filters so I will not
-
Any mail sent to "sysop" would only be sent to the callsigns in this
list.
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.
+
+
+ The directory /spider/scripts is where it all happens and is used for
+ several things. Firstly it contains a file called startup that can be
+ used to call in any changes to the cluster from the default settings
+ on startup. This script is executed immediately after all
+ initialisation of the node is done but before any connections are
+ possible. Examples of this include how many spots it is possible to
+ get with the sh/dx command, whether you want registration/passwords to
+ be permanently on etc. An example file is shown below and is included
+ in the distribution as startup.issue.
+
+
+
+ #
+ # startup script example
+ #
+ # set maximum no of spots allowed to 100
+ # set/var $Spot::maxspots = 100
+ #
+ # Set registration on
+ # set/var $main::reqreg = 1
+ #
+ # Set passwords on
+ # set/var $main::passwdreq = 1
+ #
+
+
+
+ As usual, any text behind a # is treated as a comment and not read.
+ To use this file, simply rename it from startup.issue to startup. In
+ our example above there are three options. The first option is the
+ amount of spots that a user can request with the sh/dx command.
+ Normally the default is to give 10 spots unless the user specifies
+ more. Without this line enabled, the maximum a user can request is
+ 100 spots. Depending on your link quality you may wish to enable more
+ or less by specifying the number.
+
+
+ The other 2 options are dealt with more fully in the security section.
+
+
+ Secondly, it is used to store the login scripts for users and nodes.
+ Currently this can only be done by the sysop but it is envisaged that
+ eventually users will be able to set their own. An example is
+ included in the distibution but here is a further example.
+
+
+
+ #
+ # G0FYD
+ #
+ blank +
+ sh/wwv 3
+ blank +
+ sh/dx
+ blank +
+ t g0jhc You abt?
+ blank +
+
+
+
+ The lines in between commands can simply insert a blank line or a
+ character such as a + sign to make the output easier to read. Simply
+ create this script with your favourite editor and save it with the
+ callsign of the user as the filename. Filenames should always be in
+ lower case.
+
+
+ Commands can be inserted in the same way for nodes. A node may wish a
+ series of commands to be issued on login, such as a merge command for
+ example.
+
+
+ Thirdly, there are 2 default scripts for users and nodes who do not
+ have a specifically defined script. These are user_default and
+ node_default
+
+
+ 5. Databases
Spider allows the creation of local or remote databases. It supports
chained databases, allowing several different databases to be scanned
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>
-
-
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.
-
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...
-
Remote databases cannot be chained, however, the last database in a
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.
-
This will update the existing local oblast database or create it if it
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
- dbavail
- DB Name Location Chain
- qsl Local
- buck GB7ADX
- hftest GB7DXM
- G0VGS de GB7MBC 3-Feb-2001 1925Z >
-
-
+ dbavail
+ DB Name Location Chain
+ qsl Local
+ buck GB7ADX
+ hftest GB7DXM
+ G0VGS de GB7MBC 3-Feb-2001 1925Z >
- 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 ...
-
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
-
-
-
-
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 ...
-
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.
- 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
/spider/data called motd and edit it to say whatever you want. It is
purely a text file and will be sent automatically to anyone logging in
to the cluster.
+ 6.2. MOTD_NOR
+ This message of the day file lives in the same directory as the
+ standard motd file but is only sent to non-registered users. Once
+ registered they will receive the same message as any other user.
- 5.2. Downtime message
+
+ 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
+ show/files
-
If the file they want to read is called news. You could also set an
alias for this in the Alias file to allow them just to type news
-
-
An 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,
-
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
-
- 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 ...
+ 6.5. The Aliases file
+ You will find a file in /spider/cmd/ called Aliases. This is the file
+ that controls what a user gets when issuing a command. It is also
+ possible to create your own aliases for databases and files you create
+ locally.
+ You should not alter the original file in /spider/cmd/ but create a
+ new file with the same name in /spider/local_cmd. This means that any
+ new Aliases files that is downloaded will not overwrite your self
+ created Aliases and also that you do not override any new Aliases with
+ your copy in /spider/local_cmd/. You must remember that any files you
+ store in /spider/local/ or /spider/local_cmd override the originals if
+ the same lines are used in both files.
+ The best way of dealing with all this then is to only put your own
+ locally created Aliases in the copy in /spider/local_cmd. The example
+ below is currently in use at GB7MBC.
+ #
+ # Local Aliases File
+ #
+ package CmdAlias;
+ %alias = (
+ 'n' => [
+ '^news$', 'type news', 'type',
+ ],
+ 's' => [
+ '^sh\w*/buck$', 'show/qrz', 'show',
+ '^sh\w*/hftest$', 'dbshow hftest', 'dbshow',
+ '^sh\w*/qsl$', 'dbshow qsl', 'dbshow',
+ '^sh\w*/vhf$', 'dbshow vhf', 'dbshow',
+ '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow',
+ ],
+ )
+ Each alphabetical section should be preceded by the initial letter and
+ the section should be wrapped in square brackets as you can see. The
+ syntax is straightforward. The first section on each line is the new
+ command that will be allowed once the alias is included. The second
+ section is the command it is replacing and the last section is the
+ actual command that is being used.
+ The eagle-eyed amongst you will have noticed that in the first
+ section, the new alias command has a '^' at the start and a '$' at the
+ end. Basically these force a perfect match on the alias. The '^'
+ says match the beginning exactly and the with similar commands.
- #!/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' => [
- ],
- )
-
+ I have 3 different types of alias in this file. At the top is an
+ alias for 'news'. This is a file I have created in the
+ /spider/packclus/ directory where I can inform users of new
+ developments or points of interest. In it's initial form a user would
+ have to use the command type news. The alias allows them to simply
+ type news to get the info. Second is an alias for the show/qrz
+ command so that those users used to the original show/buck command in
+ AK1A will not get an error, and the rest of the lines are for locally
+ created databases so that a user can type show/hftest instead of
+ having to use the command dbshow hftest which is not as intuitive.
+ This file is just an example and you should edit it to your own
+ requirements. Once created, simply issue the command load/alias at
+ the cluster prompt as the sysop user and the aliases should be
+ available.
- 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.
- 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.
-
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 ...
-
Now go back to the cluster and issue the command ...
- load/keps
-
+ load/keps
That is it! the kepler data has been updated.
-
-
- 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. Connecting logging programs
+
+ There appear to be very few logging programs out there that support
+ telnet especially the popular ones like LogEQF, Turbolog etc. This
+ can make it difficult to connect to your own cluster! The way to do
+ it is to make the logging program think it has a TNC attached to a com
+ port on the logging PC and 'push' a linux login out to it. This is
+ achieved very simply by the use of agetty.
+
+
+ All that is required is to add a line in /etc/inittab to have the
+ client ready for a connection on the com port of your choice.
+ Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
+ for com2 etc.
+
+
+
+ c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
+
+
+
+ Add this after the standard runlevel lines in /etc/inittab. The above
+ line works on ttyS1 (com2). Now as root, issue the command telinit q
+ and it should be ready for connection. All that is required is a 3
+ wire serial lead (tx, rx and signal ground). Tell you logging program
+ to use 8n1 at 9600 baud and you should see a Linux login prompt.
+ Login as normal and then telnet from there to the cluster.
+
+
+ 7. Java Web applet
+
+ In the spider tree will be a directory spider-web. This is a neat
+ little java web applet that can be run from a website. The applet
+ must run on the same machine as the cluster. The included README file
+ is shown below.
+
+
+ I should comment here that the applet is precompiled, that is, ready
+ to go. It was compiled using JDK1.3.1. If your version is earlier
+ than this then it may not work. Should that be the case you need to
+ recompile or update your JDK. To recompile do the following ...
+
+
+
+ cd /spider/spider-web
+ rm *.class
+ /usr/bin/javac spiderclient.java
+
+
+
+ I have used /usr/bin/javac as an example, your path to javac may be
+ different.
+
+
+ Spider-WEB v0.6b
+
+ Completely based on a clx web client written in Java by dl6dbh
+ (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
+
+ The webserver has to run on the same machine as your DxSpider software!
+
+ It is assumed that you have Java installed. You need JDK1.3.1 at least.
+
+ Installation instructions (Performed as root):
+
+ Put all the files in the spider-web directory into a newly created directory
+ under the DocumentRoot of your websever for instance 'client'. In my case
+ this is: /home/httpd/html/client/ although ymmv. For Suse the correct
+ path should be /usr/local/httpd/htdocs/client/ for example.
+
+ Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
+ /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
+ /usr/local/httpd/cgi-bin/ for example.
+
+ Change the permissions of the files to ensure they are correct, obviously you
+ will need to use the correct path the the files according to your system:
+
+ chmod 755 /home/httpd/html/cgi-bin/spider.cgi
+ chmod -R 755 /home/httpd/html/client/
+
+ By default the spider.cgi script should pick up your hostname (As long as this
+ is set correctly). If it does not or your hostname differs from the name that
+ you attach to the public address that you are using, then edit spider.cgi :
+
+ # Uncomment and set the hostname manually here if the above fails.
+ # $HOSTNAME = "gb7mbc.spoo.org" ;
+ $PORT = "8000" ;
+
+
+ telnet (see Listeners.pm)
+
+ NOTE: If you can start the console but cannot connect to the cluster from it,
+ then it is possible that the machine you are on cannot resolve the hostname of
+ your cluster machine. If this is the case, you need to set your hostname
+ manually as above.
+
+ You also need to set the $NODECALL variable. This prints the name of your
+ choosing (probably your cluster callsign) on the html page.
+
+ You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
+
+
+
+ 8. Web based statistics
+
+ From version 1.50, you can use the freeware software MRTG to produce
+ really nice graphical statistics on your web site. For an example try
+ http://www.gb7mbc.net/mrtg/stats.html.
+
+
+ The following should help you get it all working.
+
+
+ First you need to download the latest version of MRTG from
+ http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need
+ the following files..
+
+
+
+ libpng-1.0.14.tar.gz
+ zlib-1.1.4.tar.gz
+ gd-1.8.3.tar.gz
+
+
+
+ Login to your machine as the root user, put all the downloaded files
+ in /usr/local/src/ (or wherever you prefer) and untar and compile
+ them. All the information to compile and install these sources come
+ with them. After compilation and installation, you will find MRTG in
+ /usr/local/mrtg-2.
+
+
+ Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to
+ /spider/html/mrtg/
+
+
+ You now need to make 2 symbolic links like below...
+
+
+
+ ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg
+ ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2
+
+
+
+ Now login to the cluster with your sysop callsign and run the command
+ "mrtg all".
+
+
+ Now you are nearly there! Login as the sysop user and change to the
+ /spider/html/mrtg/ directory. Now run the command indexmaker as shown
+ below...
+
+
+
+ indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg
+
+
+
+ Changing the callsign for your own cluster callsign of course!
+
+
+ And finally you need to login as the root user and create one last
+ symbolic link. Where this points will depend on where your html
+ documents are kept. For RedHat systems you use...
+
+
+
+ ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg
+
+
+
+ and for SuSE systems...
+
+
+
+ ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg
+
+
+
+ If you now point your browser to your website as below it should all
+ be happening!
+
+
+
+ http://www.xxx.xxx/mrtg/stats.html
+
+
+
+ Of course, to get the stats to update, you need to add some
+ information in the spider crontab file as below...
+
+
+
+ # Update stats for mrtg on website
+ 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all')
+
+
+
+ This will update the site every 5 minutes.
+
+
+ 9. Security
+
+ From version 1.49 DXSpider has some additional security features.
+ These are not by any means meant to be exhaustive, however they do
+ afford some security against piracy. These two new features can be
+ used independently of each other or in concert to tighten the
+ security.
+
+
+ 9.1. Registration
+
+ The basic principle of registration is simple. If a user is not
+ registered by the sysop, then they have read-only access to the
+ cluster. The only thing they can actually send is a talk or a message
+ to the sysop. In order for them to be able to spot, send announces or
+ talks etc the sysop must register them with the set/register command,
+ like this ...
+
+
+
+ set/register g0vgs
+
+
+
+ The user g0vgs can now fully use the cluster. In order to enable
+ registration, you can issue the command ...
+
+ set/var $main::reqreg = 1
+
+
+
+ Any users that are not registered will now see the motd_nor file
+ rather than the motd file as discussed in the Information, files and
+ useful programs section.
+
+
+ Entering this line at the prompt will only last for the time the
+ cluster is running of course and would not be present on a restart.
+ To make the change permanent, add the above line to
+ /spider/scripts/startup. To read more on the startup file, see the
+ section on Information, files and useful programs.
+
+
+ To unregister a user use unset/register and to show the list of
+ registered users, use the command show/register.
+
+
+ 9.2. Passwords
+
+ At the moment, passwords only affect users who login to a DXSpider
+ cluster node via telnet. If a user requires a password, they can
+ either set it themselves or have the sysop enter it for them by using
+ the set/password command. Any users who already have passwords, such
+ as remote sysops, will be asked for their passwords automatically by
+ the cluster. Using passwords in this way means that the user has a
+ choice on whether to have a password or not. To force the use of
+ passwords at login, issue the command ...
+
+
+
+ set/var $main::passwdreq = 1
+
+
+
+ at the cluster prompt. This can also be added to the
+ /spider/scripts/startup file as above to make the change permanent.
+
+
+ Of course, if you do this you will have to assign a password for each
+ of your users. If you were asking them to register, it is anticipated
+ that you would ask them to send you a message both to ask to be
+ registered and to give you the password they wish to use.
+
+
+ Should a user forget their password, it can be reset by the sysop by
+ first removing the existing password and then setting a new one like
+ so ...
+
+
+
+ unset/password g0vgs
+ set/password g0vgs new_password
+
+
+
+ 10. CVS
+
+
+
+ 10.1. CVS from a Linux platform
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
DXSpider installation to the latest sources by using a few simple
- commands.
+ commands. A graphical interface to CVS for Windows is explained in
+ the next section.
- 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.
+
+
+ cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+
+
+
+ This command is all on one line.
+
+
+ Hopefully your screen should show you downloading files. The -z3
+ simply compresses the download to improve speed. When this has
+ finished, you will have exactly the same as if you had untarred a full
+ tarball PLUS some extra directories and files that CVS needs to do the
+ magic that it does.
+ Now if you are doing a new installation, that's it. Carry on as if
+ you have just downloaded and untarred the lastest tarball.
+
+
+ If you want to upgrade your current installation then do this ...
+
+
+
+ tar cvfz /tmp/s.tgz spider
+ cd /
+ tar xvfzp /tmp/s.tgz
+
+
+
+ This is assuming you downloaded to the /tmp directory of course.
+
+
+ NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the
+ permissions correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T
+ YOU?????
+
+ Remember to recompile the C client (cd /spider/src; make)
+
+
+ At this point the files have been upgraded. You can (usually) restart
+ the cluster in your own time. However, if you attempt to use any new
+ commands or features expect it to be fatal! At least your cluster
+ will have been restarted then so it will be too late to worry about
+ it!
+
+
+ Now the magic part! From now on when you want to update, simply
+ connect to the Internet and then, as the user sysop ...
+
+
+
+ cd /spider
+ cvs -z3 update -d
+
+
+
+ and your files will be updated. As above, remember to recompile the
+ "C" client if it has been updated (CVS will tell you) and restart if
+ any of the perl scripts have been altered or added, again, CVS will
+ tell you.
+
+
+ You will find any changes documented in the /spider/Changes file.
+
+
+ 10.2. CVS from a Windows platform
+
+ After the initial setup, an update to your DXSpider software is no
+ more than a couple of clicks away. This section is intended to
+ explain and illustrate the use of the WinCVS application to update
+ your DXSpider software. The current stable version of WinCVS is Ver.
+ 1.2. You can get this software at:
+
+ http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip
+
+ Pick your download mirror and then install WinCVS after the download
+ is complete.
+
+
+ In this next section I have included a series of links to .jpg files
+ to take advantage of the picture and 1000 words equivalency. The .jpg
+ files are in the C:\spider\html directory. If someone using a Linux
+ system is reading this section from boredom, the files are in
+ /home/sysop/spider/html. One aside, a Linux user can also get a copy
+ of gcvs and do your updates graphically as opposed to from the command
+ line. The following descriptions are almost identical between WinCvs
+ and gcvs. The following screen shots have duplicate links, depending
+ upon whether you are viewing this information under the Windows or
+ Linux operating system.
+
+ When WinCVS is installed, running, and you are connected to the
+ internet, the initial screen looks like:
+
+ initial.jpg
+
+ If you want, you can also look at these .jpg files with another viewer
+ that might provide some better clarity to the image. On the left is
+ the directory tree for your hard disk. Notice that the spider
+ directory has a gray highlight.
+
+ To start configuring WinCVS, click on Admin at the top of the screen
+ and then Preferences. This should get you:
+
+ pref-gen.jpg
- The next step will create a brand new 'spider' directory in your
- current directory.
+ In the top line for CVSROOT, enter:
- cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+ anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
- This command is all on one line.
+ and select
- 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.
+ "passwd" file on the cvs server
- Now if you are doing a new installation, that's it. Carry on as if
- you have just downloaded and untarred the lastest tarball.
+ for Authentication on the General tab.
- If you want to upgrade your current installation then do this ...
+ Next, move to the right to the Ports tab.
+ pref-ports.jpg
+ In here, check the box on the second line down for the "pserver" port.
+ Enter a port number of 2401.
- tar cvfz /tmp/s.tgz spider
- cd /
- tar xvfzp /tmp/s.tgz
+ Finally, go to the WinCvs tab all the way to the right.
+ pref-wincvs.jpg
+ Enter Notepad as the viewer to open files. For the HOME folder, put
+ "C:\spider" and click OK because the configuration is now complete.
+ You are now ready to upgrade your copy of DXSpider. Click on the
+ greyed Spider folder shown in the directory tree on the left of the
+ WinCVS display. Two things should happen. The Spider folder will be
+ selected and the greyed-out arrow located just below the word Query in
+ the top line will turn to solid green.
- This is assuming you downloaded to the /tmp directory of course.
+ For anyone using gcvs under Linux, the green arrow is located on the
+ extreme left of the display, under the word File. A gcvs screen looks
+ like:
+ gcvs.jpg
- 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?????
+ Click on the now green arrow to start the download process. An Update
+ Settings box will be displayed to which you can simply say OK.
- Remember to recompile the C client (cd /spider/src; make)
+ update-OK.jpg
+ For future reference, the Update Settings box is the place where you
+ can enter information to revert to a prior version of DXSpider.
+ Information on reverting to a Before Date is contained in the WinCVS
+ manual.
- 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!
+ After a short period of time, a series of file names will scroll by in
+ the lower pane of the WinCVS window. Eventually you should see
- Now the magic part! From now on when you want to update, simply
- connect to the Internet and then, as the user sysop ...
+ *****CVS exited normally with code 0*****
- cd /spider
- cvs -z3 update -d
+ appear in the lower pane. You're done. The updated files are in
+ place ready for you to stop and then restart your DXSpider. After the
+ restart, you're running with the latest version of DXSpider.
+ completed.jpg
+ To paraphrase from the CVS section... Now the magic part! From now on
+ when you want to update, simply connect to the Internet and start
+ WinCVS.
- 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.
+ Click on the greyed-out Spider directory in the left screen
+ Click on the green down arrow
+ Click OK on the Update Settings dialog box
+ Restart your Spider software
- You will find any changes documented in the /spider/Changes file.
- 7. The DXSpider command set
+ 11. The DXSpider command set
Below is a complete list of commands available from the cluster
prompt. Most maintenance tasks are automatic but there are some
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.
+ is the permissions level needed to use the command
- 7.1. accept/announce (0)
+ 11.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
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>
-
some examples:-
-
or
-
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
+ acc/ann all
+
+
but this probably for advanced users...
- 7.2. accept/announce (extended for sysops) (8)
+ 11.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
-
-
- 7.3. accept/route (8)
+ 11.3. accept/route (8)
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
routing
-
-
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:
+ You can use the tag 'all' to accept everything eg:
- acc/route all
+ acc/route all
- 7.4. accept/spots (0)
+ 11.4. accept/spots (0)
- accept/
announce [0-9] <pattern> Set an accept filter line for spots
+ accept/
spots [0-9] <pattern> Set an accept filter line for spots
Create an 'accept this spot' line for a filter.
passed onto the user. See HELP FILTERS for more info. Please read this
to understand how filters work - it will save a lot of grief later on.
+
+ Please read the following section carefully. Though it looks similar,
+ reformatting, corrections, and hopefully clarifications have been
+ added.
+
You can use any of the following things in this line:-
- 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)
+ Filters for the station being spotted:
+ call <letters of the prefix, but NOT country inclusive>
+ call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted
+ call K --> K1XX, K1XXX will be spotted
+ W1XX, W1XXX will NOT be spotted
+ call PA --> PA3EZL will be spotted
+ PB2FG will NOT be spotted
+
+ call_dxcc <numbers or prefixes>
+ call_dxcc G --> G1AAA will be spotted
+ GU1AAA will NOT be spotted (different country)
+ call_dxcc K --> K1XX, W1XX will be spotted (same country)
+ call_dxcc 139 --> PA3EZL and PB2FG will be spotted
+
call_itu <numbers>
call_zone <numbers>
- by_dxcc <numbers>
+
+ Filters for the callsign of the station doing the spotting:
+ by <letters of the prefix, but NOT country inclusive>
+ by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted
+ by K --> spots from K1XX, K1XXX will be spotted
+ spots from W1XX, W1XXX will NOT be spotted
+
+ by_dxcc <numbers or prefixes>
+ by_dxcc G --> spots from G1AAA will be spotted
+ spots from GU1AAA will NOT be spotted (different
+ country)
+ by_dxcc K --> spots from K1XX, W1XX will be spotted (same country)
+ by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted
+
by_itu <numbers>
by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
+ Filters for the callsign of the "node" doing the spotting:
+ origin <letters of the prefix, but NOT country inclusive>
+ origin K --> spots from a node starting with K will be spotted
+ spots from a node starting with KK will NOT be spotted
+ spots from a node starting with W will NOT be spotted
+
+ Filters for the callsign of the connected node or user (channel) doing the spotting:
+ channel <prefixes>
+ channel W1HR --> spots from the connected node W1HR will be spotted
+ channel K1QX --> spots from the connected user K1QX will be spotted
+ info <string> eg: iota or qsl
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
-
You can use the tag 'all' to accept everything, eg:
acc/spot 3 all
+
+
but this probably for advanced users...
- 7.5. accept/spots (extended for sysops) (8)
+ 11.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
-
-
- 7.6. accept/wcy (0)
+ 11.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
-
-
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).
See HELP FILTER for information.
- 7.7. accept/wcy (extended for sysops) (8)
+ 11.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)
+ 11.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
-
for example
-
is probably the only useful thing to do (which will only show WWV
broadcasts by stations in the US).
See HELP FILTER for information.
- 7.9. accept/wwv (extended for sysops) (8)
+
+ 11.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
-
-
-
- 7.10. announce (0)
+ 11.10. announce (0)
announce <text> Send an announcement to local users
sysop will override set/noannounce.
- 7.11. announce full (0)
+ 11.11. announce full (0)
announce full <text> Send an announcement cluster wide
- 7.12. announce sysop (5)
+ 11.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 7.13. apropos (0)
+ 11.13. apropos (0)
apropos <string> Search the help database
print the names of all the commands that may be relevant.
- 7.14. bye (0)
+ 11.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
- 7.15. catchup (5)
+ 11.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
-
and to undo what you have just done:-
-
which will arrange for them to be forward candidates again.
Order is not important.
- 7.16. clear/spots (0)
+ 11.16. clear/announce (8)
+
+ clear/announce <callsign> [input] [0-9|all] Clear an announce filter
+ line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 11.17. clear/route (8)
+
+ clear/route <callsign> [input] [0-9|all] Clear a route filter line
+
+
+ This command allows you to clear (remove) a line in a route filter or
+ to remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 11.18. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or
to remove the whole filter.
-
If you have a filter:-
-
and you say:-
-
you will be left with:-
-
If you do:
-
the filter will be completely removed.
+ 11.19. clear/spots (extended for sysops) (8)
+
+ clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 11.20. clear/wcy (0)
+
+ clear/wcy [1|all] Clear a WCY filter line
+
+
+ This command allows you to clear (remove) a line in a WCY filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+
+ 11.21. clear/wcy (extended for sysops) (8)
+
+ clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
+
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 11.22. clear/wwv (0)
+
+ clear/wwv [1|all] Clear a WWV filter line
+
+
+ This command allows you to clear (remove) a line in a WWV filter or to
+ remove the whole filter.
+ see CLEAR/SPOTS for a more detailed explanation.
- 7.17. connect (5)
+ 11.23. clear/wwv (extended for sysops) (8)
+
+ clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 11.24. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 7.18. dbavail (0)
+ 11.25. 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)
+ 11.26. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
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,
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' => [
..
..
-
to allow
SH/BUCK g1tlh
databases. See DBSHOW for generic database enquiry
- 7.20. dbimport (9)
+ 11.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 7.21. dbremove (9)
+ 11.28. dbremove (9)
dbremove <dbname> Delete a database
-
DBREMOVE will completely remove a database entry and also delete any
data file that is associated with it.
You have been warned.
- 7.22. dbshow (0)
+ 11.29. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
-
This is the generic user interface to the database to the database
system. It is expected that the sysop will add an entry to the local
Aliases file so that users can use the more familiar AK1A style of
-
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:
-
-
-
- 7.23. debug (9)
+ 11.30. debug (9)
debug Set the cluster program into debug mode
-
It will interrupt the cluster just after the debug command has
finished.
+ 11.31. delete/user (9)
+
+ delete/user <callsign> Delete a user from the User Database
+
+
+ This command will completely remove a one or more users from the
+ database.
+
+ There is NO SECOND CHANCE.
+
+ It goes without saying that you should use this command CAREFULLY!
+
+
+ 11.32. demonstrate (9)
+
+ demonstrate <call> <command> Demonstrate a command to another user
+
+
+ This command is provided so that sysops can demonstrate commands to
+ other users. It runs a command as though that user had typed it in and
+ then sends the output to that user, together with the command that
+ caused it.
+
+
+
+ DEMO g7brn sh/dx iota oc209
+ DEMO g1tlh set/here
+
+
- 7.24. directory (0)
+ Note that this command is similar to SPOOF and will have the same side
+ effects. Commands are run at the privilege of the user which is being
+ demonstrated to.
+
+
+ 11.33. directory (0)
directory List messages
directory own List your own messages
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:-
-
-
-
- 7.25. directory (extended for sysops) (5)
+ 11.34. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 7.26. disconnect (8)
+ 11.35. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 7.27. dx (0)
+ 11.36. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
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.
-
You can credit someone else by saying:-
-
- DX by G1TLH FR0G 144.600 he isn't on the cluster
-
+ 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.
-
- 7.28. export (9)
+ 11.37. export (9)
export <msgno> <filename> Export a message to a file
EXPORT 2345 /tmp/a
- 7.29. export_users (9)
+ 11.38. 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)
+ 11.39. filtering (0)
+
+ filtering Filtering things in DXSpider
+
+
+ There are a number of things you can filter in the DXSpider system.
+ They all use the same general mechanism.
+
+ In general terms you can create a 'reject' or an 'accept' filter which
+ can have up to 10 lines in it. You do this using, for example:-
+
+ accept/spots ..... reject/spots .....
+
+ where ..... are the specific commands for that type of filter. There
+ are filters for spots, wwv, announce, wcy and (for sysops) connects.
+ See each different accept or reject command reference for more
+ details.
+
+ There is also a command to clear out one or more lines in a filter and
+ one to show you what you have set. They are:-
+
+ clear/spots 1 clear/spots all
+
+ and
+
+ show/filter
+
+ There is clear/xxxx command for each type of filter.
+
+ For now we are going to use spots for the examples, but you can apply
+ the principles to all types of filter.
+
+ There are two main types of filter 'accept' or 'reject'; which you use
+ depends entirely on how you look at the world and what is least
+ writing to achieve what you want. Each filter has 10 lines (of any
+ length) which are tried in order. If a line matches then the action
+ you have specified is taken (ie reject means ignore it and accept
+ means gimme it).
+
+ The important thing to remember is that if you specify a 'reject'
+ filter (all the lines in it say 'reject/spots' (for instance) then if
+ a spot comes in that doesn't match any of the lines then you will get
+ it BUT if you specify an 'accept' filter then any spots that don't
+ match are dumped. For example if I have a one line accept filter:-
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+ then automatically you will ONLY get VHF spots from or to CQ zones 14
+ 15 and 16. If you set a reject filter like:
+
+ reject/spots on hf/cw
+
+ Then you will get everything EXCEPT HF CW spots, If you am interested
+ in IOTA and will work it even on CW then you could say:-
+
+ reject/spots on hf/cw and not info iota
+
+ But in that case you might only be interested in iota and say:-
+
+ accept/spots not on hf/cw or info iota
+
+ which is exactly the same. You should choose one or the other until
+ you are confortable with the way it works. Yes, you can mix them
+ (actually you can have an accept AND a reject on the same line) but
+ don't try this at home until you can analyse the results that you get
+ without ringing up the sysop for help.
+
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. I have one set frequently:-
+
+ reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone
+ 14,15,16 or call_zone 14,15,16)
+
+ What this does is to ignore all HF CW spots (being a class B I can't
+ read any CW and couldn't possibly be interested in HF :-) and also
+ rejects any spots on VHF which don't either originate or spot someone
+ in Europe.
+
+ This is an exmaple where you would use the line number (1 and 2 in
+ this case), if you leave the digit out, the system assumes '1'. Digits
+
+ You can leave the word 'and' out if you want, it is implied. You can
+ use any number of brackets to make the 'expression' as you want it.
+ There are things called precedence rules working here which mean that
+ you will NEED brackets in a situation like line 2 because, without it,
+ will assume:-
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+ annoying, but that is the way it is. If you use OR - use brackets.
+ Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
+ by_zone'.
+
+ If you want to alter your filter you can just redefine one or more
+ lines of it or clear out one line. For example:-
+
+ reject/spots 1 on hf/ssb
+
+ or
+
+ clear/spots 1
+
+ To remove the filter in its entirty:-
+
+ clear/spots all
+
+ There are similar CLEAR commands for the other filters:-
+
+ clear/announce clear/wcy clear/wwv
+
+ ADVANCED USERS:-
+
+ Once you are happy with the results you get, you may like to
+ experiment.
+
+ my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+ can be written with a mixed filter, eg:
+
+ rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and
+ (by_zone 14,15,16 or call_zone 14,15,16)
+
+ each filter slot actually has a 'reject' slot and an 'accept' slot.
+ The reject slot is executed BEFORE the accept slot.
+
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ first, any non hf/cw spot is passed to the accept line, which lets
+ thru everything else on HF.
+
+ The next filter line lets through just VHF/UHF spots from EU.
+
+
+ 11.40. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 7.31. forward/opername (1)
+ 11.41. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 7.32. help (0)
+ 11.42. help (0)
help <cmd> Get help on a command
+
All commands can be abbreviated, so SHOW/DX can be abbreviated to
SH/DX, ANNOUNCE can be shortened to AN and so on.
commands to look at with HELP.
- 7.33. init (5)
+ 11.43. 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)
+ 11.44. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
- 7.35. kill (5)
+ 11.45. 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)
+ 11.46. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
+ 11.47. kill/expunge (6)
+
+ kill/expunge <msgno> [<msgno>..]Expunge a message
+
+
+ Deleting a message using the normal KILL commands only marks that
+ message for deletion. The actual deletion only happens later (usually
+ two days later).
+
+
+ The KILL EXPUNGE command causes the message to be truly deleted more
+ or less immediately.
+ It otherwise is used in the same way as the KILL command.
- 7.37. links (0)
+
+
+ 11.48. links (0)
links Show which nodes are physically connected
- 7.38. load/aliases (9)
+ 11.49. 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)
+ 11.50. load/badmsg (9)
load/badmsg Reload the bad message table
deleted on receipt.
- 7.41. load/badwords (9)
+ 11.51. load/badwords (9)
- load/badwords Reload the badwords file
+ load/badwords Reload the bad words table
Reload the /spider/data/badwords file if you have changed it manually
ignored.
- 7.42. load/bands (9)
+ 11.52. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 7.43. load/cmd_cache (9)
+ 11.53. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
-
Normally, if you change a command file in the cmd or local_cmd tree it
will automatially be picked up by the cluster program. Sometimes it
can get confused if you are doing a lot of moving commands about or
was just after a cluster restart.
- 7.44. load/forward (9)
+ 11.54. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 7.45. load/messages (9)
+ 11.55. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 7.46. load/prefixes (9)
+ 11.56. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 7.47. merge (5)
+ 11.57. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 7.48. msg (9)
+ 11.58. msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
Alter message parameters like To, From, Subject, whether private or
bulletin or return receipt (RR) is required or whether to keep this
message from timing out.
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+ 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:-
This will display more information on the message than DIR does.
- 7.49. pc (8)
+ 11.59. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
pc G1TLH Try doing that properly!!!
- 7.50. ping (1)
+ 11.60. ping (1)
ping <node> Check the link quality between nodes
- 7.51. rcmd (1)
+ 11.61. 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)
+ 11.62. 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)
+ 11.63. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 7.54. reject/announce
+ 11.64. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
-
some examples:-
-
You can use the tag 'all' to reject everything eg:
-
but this probably for advanced users...
- 7.55. reject/announce (extended for sysops) (8)
+ 11.65. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
-
-
- 7.56. reject/route (8)
+ 11.66. reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
routing
-
-
some examples:-
-
rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
-
-
You can use the tag 'all' to reject everything eg:
-
-
- 7.57. reject/spots (0)
+ 11.67. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
-
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 -
-
-
You can use the tag 'all' to reject everything eg:
-
but this probably for advanced users...
- 7.58. reject/spots (extended for sysops) (8)
+ 11.68. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
-
-
- 7.59. reject/wcy (0)
+ 11.69. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
-
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).
- 7.60. reject/wcy (extended for sysops) (8)
+ 11.70. 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)
+ 11.71. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
-
for example
-
is probably the only useful thing to do (which will only show WWV
broadcasts by stations in the US).
See HELP FILTER for information.
- 7.62. reject/wwv (extended for sysops) (8)
+ 11.72. 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)
+ 11.73. 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)
+ 11.74. send (0)
send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
-
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.
is an alias for SEND PRIVATE
- 7.65. set/address (0)
+ 11.75. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 7.66. set/announce (0)
+ 11.76. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
- 7.67. set/arcluster (5)
+ 11.77. set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 7.68. set/baddx (8)
+ 11.78. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
-
To allow a word again, use the following command ...
-
-
- 7.69. set/badnode (6)
+ 11.79. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
-
will stop anything from K1TTT (including any SSID's)
-
will allow spots from him again.
Use with extreme care. This command may well be superceded by
FILTERing.
- 7.70. set/badspotter (8)
+ 11.80. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
-
will stop anything from VE2STN. If you want SSIDs as well then you
must enter them specifically.
-
will allow spots from him again.
Use with extreme care. This command may well be superceded by
FILTERing.
- 7.71. set/beep (0)
+ 11.81. set/badword (8)
- set/beep Add beeps to terminal messages
+ set/badword <word> Stop things with this word being propogated
+
+
+ Setting a word as a 'badword' will prevent things like spots,
+ announces or talks with this word in the the text part from going any
+ further. They will not be displayed and they will not be sent onto
+ other nodes.
+
+ The word must be written in full, no wild cards are allowed eg:-
+
+ set/badword annihilate annihilated annihilation
+
+ will stop anything with these words in the text.
+
+ unset/badword annihilated
+
+ will allow text with this word again.
+
+
+
+ 11.82. set/beep (0)
+ set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 7.72. set/bbs (5)
+ 11.83. set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
- 7.73. set/clx (5)
+ 11.84. set/clx (5)
set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
node
Set the node_call as a CLX type node
- 7.74. set/debug (9)
+ 11.85. set/debug (9)
set/debug <name> Add a debug level to the debug set
+
You can choose to log several different levels. The levels are
chan state msg cron connect
You can remove a debug level with unset/debug <name>
- 7.75. set/dx (0)
+ 11.86. 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)
+ 11.87. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 7.77. set/dxnet (5)
+ 11.88. set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 7.78. set/echo (0)
+ 11.89. 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)
+ 11.90. set/email (0)
+
+ set/email <email_address> Set email address(es) and forward your
+ personals
+
+
+ If any personal messages come in for your callsign then you can use
+ these commands to control whether they are forwarded onto your email
+ address. To enable the forwarding do something like:-
+
+ SET/EMAIL mike.tubby@somewhere.com
+
+ You can have more than one email address (each one separated by a
+ space). Emails are forwarded to all the email addresses you specify.
+
+ You can disable forwarding by:-
+
+ UNSET/EMAIL
+
+
+ 11.91. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
-
-
- 7.80. set/homenode (0)
+ 11.92. set/homenode (0)
set/homenode <node_call> Set your home cluster
-
-
- 7.81. set/hops (8)
+ 11.93. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
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.
- 7.82. set/isolate (9)
+ 11.94. 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)
+ 11.95. set/language (0)
set/language <language> Set the language you wish to use
You can select the language that you want the cluster to use.
Currently the languages available are en (English) and nl (Dutch).
- 7.84. set/location (0)
+
+ 11.96. set/location (0)
set/location <lat and long> Set your latitude and longitude
-
-
-
- 7.85. set/sys_location (9)
+ 11.97. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
example:-
-
SET/LOCATION 52 22 N 0 57 E
-
-
- 7.86. set/logininfo (0)
+ 11.98. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 7.87. set/lockout (9)
+ 11.99. 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)
+ 11.100. set/name (0)
set/name <your_name> Set your name
set/name Dirk
- 7.89. set/node (9)
+
+ 11.101. 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)
+
+ 11.102. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 7.91. set/page (0)
+ 11.103. set/page (0)
set/page <n> Set the number of lines per page
-
The setting is stored in your user profile.
+ 11.104. set/password (0)
+
+ set/password Set your own password
+
+ This command only works for a 'telnet' user (currently). It will only
+ work if you have a password already set. This initial password can
+ only be set by the sysop.
- 7.92. set/password (9)
+ When you execute this command it will ask you for your old password,
+ then ask you to type in your new password twice (to make sure you get
+ it right). You may or may not see the data echoed on the screen as you
+ type, depending on the type of telnet client you have.
+
+
+ 11.105. set/password (9)
set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The string
- can contain any characters 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.
+ can contain any characters.
+
+ The way this field is used depends on context. If it is being used in
+ the SYSOP command context then you are offered 5 random numbers and
+ you have to supply the corresponding letters. This is now mainly for
+ ax25 connections.
+
+ If it is being used on incoming telnet connections then, if a password
+ is set or the:
+ set/var $main::passwdreq = 1
- 7.93. set/pinginterval (9)
+ command is executed in the startup script, then a password prompt is
+ given after the normal 'login: ' prompt.
+
+ The command "unset/password" is provided to allow a sysop to remove a
+ users password completely in case a user forgets or loses their
+ password.
+
+
+ 11.106. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 7.94. set/privilege (9)
+ 11.107. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
-
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.
- 7.95. set/spider (5)
+
+ 11.108. set/spider (5)
set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
-
Set the node_call as a DXSpider type node
- 7.96. set/sys_qra (9)
+ 11.109. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 7.97. set/qra (0)
+ 11.110. set/qra (0)
set/qra <locator> Set your QRA locator
-
-
- 7.98. set/qth (0)
+ 11.111. set/qth (0)
set/qth <your QTH> Set your QTH
+ 11.112. set/register (9)
+
+ set/register <call> Mark a user as registered
+
+
+ Registration is a concept that you can switch on by executing the
+
+ set/var $main::regreq = 1
+ command (usually in your startup file)
- 7.99. set/talk (0)
+ If a user is NOT registered then, firstly, instead of the normal motd
+ file (/spider/data/motd) being sent to the user at startup, the user
+ is sent the motd_nor file instead. Secondly, the non registered user
+ only has READ-ONLY access to the node. The non-registered user cannot
+ use DX, ANN etc.
+
+ The only exception to this is that a non-registered user can TALK or
+ SEND messages to the sysop.
+
+ To unset a user use the 'unset/register' command
+
+
+ 11.113. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 7.100. set/wcy (0)
+ 11.114. 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)
+ 11.115. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
Allow WWV information to be seen at your console. You can switch off
WWV messages with the unset/wwv command.
- 7.102. set/wx (0)
+
+ 11.116. 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)
+ 11.117. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 7.104. show/badnode (6)
+ 11.118. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 7.105. show/badspotter (1)
+ 11.119. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 7.106. show/configuration (0)
+ 11.120. show/badword (1)
+
+ show/badword Show all the bad words in the system
+
+
+ Display all the bad words in the system, see SET/BADWORD for more
+ information.
+
+
+ 11.121. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 7.107. show/configuration/node (0)
+ 11.122. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 7.108. show/connect (1)
+ 11.123. show/connect (1)
show/connect Show all the active connections
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
- 7.109. show/date (0)
+
+
+ 11.124. 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)
+ 11.125. 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)
+
+ 11.126. show/dx (0)
show/dx [options] interrogate the spot database
-
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
- e.g.
+ e.g.
+
SH/DX 9m0
-
-
- 7.112. show/dxcc (0)
+ 11.127. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
-
SH/DXCC G
SH/DXCC W on 20m info iota
+ 11.128. sh/dxstats (0)
+
+ sh/dxstats Show the DX Statistics for last 31 days
+
+
+ Show the total DX spots for the last 31 days
- 7.113. show/files (0)
+
+ 11.129. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
-
where <filearea> is the name of the filearea you want to see the
contents of.
See also TYPE - to see the contents of a file.
- 7.114. show/filter (0)
+ 11.130. show/filter (0)
show/filter Show the filters you have set
-
Show the contents of all the filters that are set by you. This command
displays all the filters set - for all the various categories.
- 7.115. show/filter (extended for sysops) (5)
+ 11.131. show/filter (extended for sysops) (5)
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 7.116. show/hops (8)
+ 11.132. show/hfstats (0)
+
+ show/hfstats Show the HF DX Statistics for last 31 days
+
+
+ Show the HF DX spots breakdown by band for the last 31 days
+
+
+ 11.133. show/hftable (0)
+
+ show/hftable Show the HF DX Spotter Table for your country
+
+
+ Show the HF DX Spotter table for your country for the last 31 days
+
+
+ 11.134. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 7.117. show/isolate (1)
+ 11.135. 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)
+ 11.136. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 7.119. show/log (8)
+ 11.137. 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)
+ 11.138. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or
callsigns, together with the azimuth and elevation of the sun
currently at those locations.
+
If you don't specify any prefixes or callsigns, it will show the times
for your QTH (assuming you have set it with either SET/LOCATION or
SET/QRA), together with the current azimuth and elevation.
-
-
- 7.121. show/muf (0)
+ 11.139. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
- SH/MUF W
-
+ SH/MUF W
-
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
- inputing:-
+ inputting:-
-
will get you the above display, but with the next 24 hours worth of
propagation data.
-
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.
- 7.122. show/node (1)
+ 11.140. show/newconfiguration (0)
+
+ show/newconfiguration [<node>] Show all the nodes and users visible
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected.
+
+ This command produces essentially the same information as
+ SHOW/CONFIGURATION except that it shows all the duplication of any
+ routes that might be present It also uses a different format which may
+ not take up quite as much space if you don't have any loops.
+
+ BE WARNED: the list that is returned can be VERY long
+
+
+ 11.141. show/newconfiguration/node (0)
+
+ show/newconfiguration/node Show all the nodes connected locally
+
+
+ Show all the nodes connected to this node in the new format.
+
+
+ 11.142. show/node (1)
show/node [<node_call> ...] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 7.123. show/prefix (0)
+ 11.143. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
- 7.124. show/program (5)
+ 11.144. show/program (5)
show/program Show the locations of all the included program modules
from.
- 7.125. show/qra (0)
+ 11.145. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
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
-
-
- 7.126. show/qrz (0)
+ 11.146. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
+ 11.147. show/registered (9)
+ show/registered [<prefix>[ Show the registered users
- 7.127. show/route (0)
+ 11.148. show/route (0)
show/route <callsign> Show the route to <callsign>
-
-
- 7.128. show/satellite (0)
+ 11.149. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
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.
-
-
- 7.129. show/sun (0)
+ 11.150. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
If all else fails it will show the sunrise and set times for the node
that you are connected to.
-
For example:-
-
-
- 7.130. show/time (0)
+ 11.151. 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)
+ 11.152. show/vhfstats (0)
+
+ show/vhfstats Show the VHF DX Statistics for last 31 days
+
+
+ Show the VHF DX spots breakdown by band for the last 31 days
+
+
+ 11.153. show/vhftable (0)
+
+ show/vhftable Show the VHF DX Spotter Table for your country
+
+ Show the VHF DX Spotter table for your country for the last 31 days
+
+
+ 11.154. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 7.132. show/wwv (0)
+ 11.155. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 7.133. shutdown (5)
+ 11.156. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 7.134. spoof (9)
+ 11.157. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
-
-
-
- 7.135. stat/db (5)
+ 11.158. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
- 7.136. stat/channel (5)
+ 11.159. 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)
+ 11.160. stat/msg (5)
stat/msg <msgno> Show the status of a message
displayed.
- 7.138. stat/route_node (5)
+ 11.161. stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
- 7.139. stat/route_user (5)
+ 11.162. stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
- 7.140. stat/user (5)
+ 11.163. 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)
+ 11.164. sysop (0)
sysop Regain your privileges if you login remotely
-
you type:-
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
case sensitive.
- 7.142. talk (0)
+ 11.165. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
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:
-
-
- 7.143. type (0)
+ 11.166. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
-
See also SHOW/FILES to see what fileareas are available and a list of
content.
- 7.144. who (0)
+ 11.167. who (0)
who Show who is physically connected locally
what sort of connection they have
- 7.145. wx (0)
+ 11.168. 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)
+ 11.169. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / blobdiff