- The DXSpider Administration Manual v1.47
+ The DXSpider Administration Manual v1.48
Ian Maude, G0VGS, (ianmaude@btinternet.com)
-
+ Version 1.48 August 2001 revision 1.1
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
- 1. Hop control
-
- 1.1 Basic hop control
- 1.2 Isolating networks
-
- 2. Filtering (Old Style upto v1.44)
-
- 2.1 Spots
- 2.2 Announcements
- 2.3 WWV
-
- 3. Filtering (New Style v1.45 and later)
+ 1. Routing and Filtering
- 3.1 General filter rules
- 3.2 Types of filter
- 3.3 Filter options
- 3.4 Default filters
- 3.5 Advanced filtering
+ 1.1 Introduction
+ 1.2 Route Filters
+ 1.3 The node_default filter
+ 1.4 General route filtering
+ 1.5 General filter rules
+ 1.6 Types of filter
+ 1.7 Filter options
+ 1.8 Default filters
+ 1.9 Advanced filtering
+ 1.10 Basic hop control
+ 1.11 Isolating networks
- 4. Other filters
+ 2. Other filters
- 4.1 Filtering Mail
- 4.2 Filtering DX callouts (Depricated)
- 4.3 Filtering words from text fields in Announce, Talk and DX spots
+ 2.1 Filtering Mail
+ 2.2 Filtering DX callouts (Depricated)
+ 2.3 Filtering words from text fields in Announce, Talk and DX spots
- 5. Mail
+ 3. Mail
- 5.1 Personal mail
- 5.2 Bulletin mail
- 5.3 Forward.pl
- 5.4 The msg command
- 5.5 Message status
- 5.6 Filtering mail
- 5.7 Distribution lists
- 5.8 BBS interface
+ 3.1 Personal mail
+ 3.2 Bulletin mail
+ 3.3 Forward.pl
+ 3.4 The msg command
+ 3.5 Message status
+ 3.6 Filtering mail
+ 3.7 Distribution lists
+ 3.8 BBS interface
- 6. Databases
+ 4. Databases
- 6.1 Creating databases
- 6.2 Importing databases
- 6.3 Checking available databases
- 6.4 Looking up databases
- 6.5 Removing databases
+ 4.1 Creating databases
+ 4.2 Importing databases
+ 4.3 Checking available databases
+ 4.4 Looking up databases
+ 4.5 Removing databases
- 7. Information, files and useful programs
+ 5. Information, files and useful programs
- 7.1 MOTD
- 7.2 Downtime message
- 7.3 Other text messages
- 7.4 The Aliases file
- 7.5 Console.pl
- 7.6 Updating kepler data
- 7.7 The QRZ callbook
+ 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
- 8. CVS
+ 6. CVS
- 9. The DXSpider command set
+ 7. The DXSpider command set
- 9.1 accept/announce (0)
- 9.2 accept/announce (extended for sysops) (8)
- 9.3 accept/spots (0)
- 9.4 accept/spots (extended for sysops) (8)
- 9.5 accept/wcy (0)
- 9.6 accept/wcy (extended for sysops) (8)
- 9.7 accept/wwv (0)
- 9.8 accept/wwv (extended for sysops) (8)
- 9.9 announce (0)
- 9.10 announce full (0)
- 9.11 announce sysop (5)
- 9.12 apropos (0)
- 9.13 bye (0)
- 9.14 catchup (5)
- 9.15 clear/spots (0)
- 9.16 connect (5)
- 9.17 dbavail (0)
- 9.18 dbcreate (9)
- 9.19 dbimport (9)
- 9.20 dbremove (9)
- 9.21 dbshow (0)
- 9.22 debug (9)
- 9.23 directory (0)
- 9.24 directory (extended for sysops) (5)
- 9.25 disconnect (8)
- 9.26 dx (0)
- 9.27 export (9)
- 9.28 export_users (9)
- 9.29 forward/latlong (8)
- 9.30 forward/opername (1)
- 9.31 help (0)
- 9.32 init (5)
- 9.33 kill (0)
- 9.34 kill (5)
- 9.35 kill full (5)
- 9.36 links (0)
- 9.37 load/aliases (9)
- 9.38 load/baddx (9)
- 9.39 load/badmsg (9)
- 9.40 load/badwords (9)
- 9.41 load/bands (9)
- 9.42 load/cmd_cache (9)
- 9.43 load/forward (9)
- 9.44 load/messages (9)
- 9.45 load/prefixes (9)
- 9.46 merge (5)
- 9.47 msg (9)
- 9.48 pc (8)
- 9.49 ping (1)
- 9.50 rcmd (1)
- 9.51 read (0)
- 9.52 read (extended for sysops) (5)
- 9.53 reject/announce
- 9.54 reject/announce (extended for sysops) (8)
- 9.55 reject/spots (0)
- 9.56 reject/spots (extended for sysops) (8)
- 9.57 reject/wcy (0)
- 9.58 reject/wcy (extended for sysops) (8)
- 9.59 reject/wwv (0)
- 9.60 reject/wwv (extended for sysops) (8)
- 9.61 reply (0)
- 9.62 send (0)
- 9.63 set/address (0)
- 9.64 set/announce (0)
- 9.65 set/arcluster (5)
- 9.66 set/baddx (8)
- 9.67 set/badnode (6)
- 9.68 set/badspotter (8)
- 9.69 set/beep (0)
- 9.70 set/clx (5)
- 9.71 set/debug (9)
- 9.72 set/dx (0)
- 9.73 set/dxgrid (0)
- 9.74 set/dxnet (5)
- 9.75 set/echo (0)
- 9.76 set/here (0)
- 9.77 set/homenode (0)
- 9.78 set/hops (8)
- 9.79 set/isolate (9)
- 9.80 set/language (0)
- 9.81 set/location (0)
- 9.82 set/sys_location (9)
- 9.83 set/logininfo (0)
- 9.84 set/lockout (9)
- 9.85 set/name (0)
- 9.86 set/node (9)
- 9.87 set/obscount (9)
- 9.88 set/page (0)
- 9.89 set/password (9)
- 9.90 set/pinginterval (9)
- 9.91 set/privilege (9)
- 9.92 set/spider (5)
- 9.93 set/sys_qra (9)
- 9.94 set/qra (0)
- 9.95 set/qth (0)
- 9.96 set/talk (0)
- 9.97 set/wcy (0)
- 9.98 set/wwv (0)
- 9.99 set/wx (0)
- 9.100 show/baddx (1)
- 9.101 show/badnode (6)
- 9.102 show/badspotter (1)
- 9.103 show/configuration (0)
- 9.104 show/configuration/node (0)
- 9.105 show/connect (1)
- 9.106 show/date (0)
- 9.107 show/debug (9)
- 9.108 show/dx (0)
- 9.109 show/dxcc (0)
- 9.110 show/files (0)
- 9.111 show/filter (0)
- 9.112 show/filter (extended for sysops) (5)
- 9.113 show/hops (8)
- 9.114 show/isolate (1)
- 9.115 show/lockout (9)
- 9.116 show/log (8)
- 9.117 show/moon (0)
- 9.118 show/muf (0)
- 9.119 show/node (1)
- 9.120 show/prefix (0)
- 9.121 show/program (5)
- 9.122 show/qra (0)
- 9.123 show/qrz (0)
- 9.124 show/route (0)
- 9.125 show/satellite (0)
- 9.126 show/sun (0)
- 9.127 show/time (0)
- 9.128 show/wcy (0)
- 9.129 show/wwv (0)
- 9.130 shutdown (5)
- 9.131 spoof (9)
- 9.132 stat/db (5)
- 9.133 stat/channel (5)
- 9.134 stat/msg (5)
- 9.135 stat/user (5)
- 9.136 sysop (0)
- 9.137 talk (0)
- 9.138 type (0)
- 9.139 who (0)
- 9.140 wx (0)
- 9.141 wx (enhanced for sysops) (5)
+ 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)
______________________________________________________________________
- 1. Hop control
-
- Starting with version 1.13 there is simple hop control available on a
- per node basis. Also it is possible to isolate a network completely so
- that you get all the benefits of being on that network, but can't pass
- on information from it to any other networks you may be connected to
- (or vice versa).
-
-
- 1.1. Basic hop control
-
- In /spider/data you will find a file called hop_table.pl. This is the
- file that controls your hop count settings. It has a set of default
- hops on the various PC frames and also a set for each node you want to
- alter the hops for. You may be happy with the default settings of
- course, but this powerful tool can help to protect and improve the
- network. The file will look something like this ...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- #
- # hop table construction
- #
-
- package DXProt;
-
- # default hopcount to use
- $def_hopcount = 5;
-
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
-
-
- # the per node hop control thingy
-
-
- %nodehops =
-
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- };
-
-
-
-
-
- Each set of hops is contained within a pair of curly braces and
- contains a series of PC frame types. PC11 for example is a DX spot.
- The figures here are not exhaustive but should give you a good idea of
- how the file works.
-
-
- You can alter this file at any time, including whilst the cluster is
- running. If you alter the file during runtime, the command load/hops
- will bring your changes into effect.
+ 1. Routing and Filtering
+ 1.1. Introduction
+ From DXSpider version 1.48, major changes were introduced to the way
+ node connections are treated. This is part of an ongoing process to
+ remove problems with loops and to enable talk and other functions to
+ propagate across the whole of the worldwide cluster network. In fact,
+ in a Spider network, it would be useful, perhaps even necessary to
+ have loops. This would give real resilience to the network, meaning
+ that if a link dropped, the information flow would simply come in and
+ go out via a different route. Of course, we do not have a complete
+ network of Spider nodes, there are other programs out there. Some of
+ these do not have any protection from loops. Certainly AK1A does not
+ handle loops well at all. It is therefore necessary to have some form
+ of protection for these nodes.
- 1.2. Isolating networks
- It is possible to isolate networks from each other on a "gateway" node
- using the set/isolate <node_call> command.
+ 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 effect of this is to partition an isolated network completely from
- another nodes connected to your node. Your node will appear on and
- otherwise behave normally on every network to which you are connected,
- but data from an isolated network will not cross onto any other
- network or vice versa. However all the spot, announce and WWV traffic
- and personal messages will still be handled locally (because you are a
- real node on all connected networks), that is locally connected users
- will appear on all networks and will be able to access and receive
- information from all networks transparently. All routed messages will
- be sent as normal, so if a user on one network knows that you are a
- gateway for another network, he can still still send a talk/announce
- etc message via your node and it will be routed across.
-
+ The new functionality introduced in version 1.48 is filtering the node
+ and user protocol frames on a "per interface" basis. We call this
+ route filtering. This is used instead of isolation.
- 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.
+ What this really means is that you can control more or less completely
+ which PC protocol frames, to do with user and node management, pass to
+ each of your partner nodes. You can also limit what comes into your
+ node from your partners. You can even control the settings that your
+ partner node has for the routing information that it sends to you
+ (using the rcmd command).
- 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
- ....
+ 1.2. Route Filters
+ Initially when route filters were being tested we generated a
+ "default" filter. Unfortunately it quickly became apparent that this
+ might suit the UK cluster network but didn't really fit anybody else.
+ However using a default filter is an appropriate thing to do. How, is
+ explained further on.
- $in = [
- [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
- ];
+ The first thing that you must do is determine whether you need to do
+ 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.
+ 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.
+ All the filters in Spider work in basically the same way. You can
+ either accept or reject various options in order to create the filter
+ rules you wish to achieve. Some filters are user settable, others can
+ only be altered by the sysop. Route filtering can only be done by the
+ sysop.
- There is a lot more on filtering in the next section.
+ Anyway, without further discouragement, let me start the process of
+ explanation.
- 2. Filtering (Old Style upto v1.44)
- Filters can be set for spots, announcements and WWV. You will find
- the directories for these under /spider/filter. You will find some
- examples in the directories with the suffix .issue. There are two
- types of filter, one for incoming information and one for outgoing
- information. Outgoing filters are in the form CALLSIGN.pl and
- incoming filters are in the form in_CALLSIGN.pl. Filters can be set
- for both nodes and users.
+ 1.3. The node_default filter
+ All normal systems should have a default routing filter and it should
+ usually be set to send only the normal, unlooped, view of your
+ "national" network. Here in the UK that means nodes from the UK and
+ Eire, in EU it is more complex as the networks there grew up in a more
+ intertwined way.
- All filters work in basically the same way. There are several
- elements delimited by commas. There can be many lines in the filter
- and they are read from the top by the program. When writing a filter
- you need to think carefully about just what you want to achieve. You
- are either going to write a filter to accept or to reject. Think of a
- filter as having 2 main elements. For a reject filter, you would have
- a line or multiple lines rejecting the things you do not wish to
- receive and then a default line accepting everything else that is not
- included in the filter. Likewise, for an accept filter, you would
- have a line or multiple lines accepting the things you wish to receive
- and a default line rejecting everthing else.
- In the example below, a user requires a filter that would only return
- SSB spots posted in Europe on the HF bands. This is achieved by first
- rejecting the CW section of each HF band and rejecting all of VHF, UHF
- etc based on frequency. Secondly, a filter rule is set based on CQ
- zones to only accept spots posted in Europe. Lastly, a default filter
- rule is set to reject anything outside the filter.
+ The generic commands are:-
- $in = [
- [ 0, 0, 'r', # reject all CW spots
- [
- 1800.0, 1850.0,
- 3500.0, 3600.0,
- 7000.0, 7040.0,
- 14000.0, 14100.0,
- 18068.0, 18110.0,
- 21000.0, 21150.0,
- 24890.0, 24930.0,
- 28000.0, 28180.0,
- 30000.0, 49000000000.0,
- ] ,1 ],
- [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
- [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-
-
-
-
-
- The actual elements of each filter are described more fully in the
- following sections.
-
-
- 2.1. Spots
-
- The elements of the Spot filter are ....
-
-
-
- [action, field_no, sort, possible_values, hops]
-
-
-
-
-
- There are 3 elements here to look at. Firstly, the action element.
- This is very simple and only 2 possible states exist, accept (1) or
- drop (0).
+ reject/route node_default <filter_option>
+ or
- The second element is the field_no. There are 13 possiblities to
- choose from here ....
+ accept/route node_default <filter_option>
+ where filter_option is one of the following ...
+ call <prefixes>
+ call_dxcc <numbers>
+ call_itu <numbers>
+ call_zone <numbers>
+ channel <prefixes>
+ channel_dxcc <numbers>
+ channel_itu <numbers>
+ channel_zone <numbers>
- 0 = frequency
- 1 = call
- 2 = date in unix format
- 3 = comment
- 4 = spotter
- 5 = spotted dxcc country
- 6 = spotter's dxcc country
- 7 = origin
- 8 = spotted itu
- 9 = spotted cq
- 10 = spotter's itu
- 11 = spotter's cq
- 12 = callsign of the channel on which the spot has appeared
+ Please be careful if you alter this setting, it will affect ALL your
+ links!
- The third element tells us what to expect in the fourth element.
- There are 4 possibilities ....
+ 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:-
- n - numeric list of numbers e.g. [ 1,2,3 ]
- r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
- a - an alphanumeric regex
- d - the default rule
+ 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).
- The fifth element is simply the hops to set in this filter. This
- would only be used if the filter was for a node of course and
- overrides the hop count in hop_table.pl.
+ 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:
- So, let's look at an example spot filter. It does not matter in the
- example who the filter is to be used for. So, what do we need in the
- filter? We need to filter the spots the user/node requires and also
- set a default rule for anything else outside the filter. Below is a
- simple filter that stops spots arriving from outside Europe.
+ rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
- $in = [
- [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
- [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
+ 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.
- So the filter is wrapped in between a pair of square brackets. This
- tells Spider to look in between these limits. Then each line is
- contained within its own square brackets and ends with a comma. Lets
- look carefully at the first line. The first element is 0 (drop).
- Therefore anything we put on this line will not be accepted. The next
- element is 4. This means we are filtering by the spotter. The third
- element is the letter "a" which tells the program to expect an
- alphanumeric expression in the fourth element. The fourth element is
- a list of letters separated by the pipe symbol.
+ 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:-
- What this line does is tell the program to drop any spots posted by
- anyone in the USA, Canada or Japan.
+ set/debug filter
- The second line is the default rule for anything else. The "d" tells
- us this and the line simply reads... accept anything else.
- You can add as many lines as you need to complete the filter but if
- there are several lines of the same type it is neater to enclose them
- all as one line. An example of this is where specific bands are set.
- We could write this like this ....
+ After you have got tired of that, to put it back the way it was:-
- [ 0,0,'r',[1800.0, 2000.0], 1],
- [ 0,0,'r',[10100.0, 10150.0], 1],
- [ 0,0,'r',[14000.0, 14350.0], 1],
- [ 0,0,'r',[18000.0, 18200.0], 1],
+ unset/debug filter
- But the line below achieves the same thing and is more efficient ....
+ 1.4. General route filtering
+ Exactly the same rules apply for general route filtering. You would
+ use either an accept filter or a reject filter like this ...
- [ 0, 0, 'r',
- [
- 1800.0, 2000.0, # top band
- 10100.0, 10150.0, # WARC
- 14000.0, 14350.0, # 20m
- 18000.0, 18200.0, # WARC
- [ ,1 ],
+ reject/route <node_call> <filter_option>
+ or
+ accept/route <node_call> <filter_option>
- 2.2. Announcements
+ Here are some examples of route filters ...
- # This is an example announce or filter allowing only West EU announces
- #
- # The element list is:-
- # 0 - callsign of announcer
- # 1 - destination * = all, <callsign> = routed to the node
- # 2 - text
- # 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
- # 4 - origin
- # 5 - 0 - announce, 1 - wx
- # 6 - channel callsign (the interface from which this spot came)
+ 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)
- $in = [
- [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
- [ 0, 0, 'd', 0 ]
- ];
+ In practice you will either be opening the default filter out for a
+ partner by defining a specific filter for that callsign:-
- In this example, only the prefixes listed will be allowed. It is
- possible to be quite specific. The Dutch prefix "P" is followed by
- several secondary identifiers which are allowed. So, in the example,
- "PA" or "PE" would be ok but not "PG". It is even possible to allow
- information from a single callsign. In the example this is DK0WCY, to
- allow the posting of his Aurora Beacon.
+ acc/route gb7baa all
+ acc/route gb7baa input all
- 2.3. WWV
+ or restricting it quite a lot, in fact making it very nearly like an
+ isolated node, like this:-
- # This is an example WWV filter
- #
- # The element list is:-
- # 0 - nominal unix date of spot (ie the day + hour:13)
- # 1 - the hour
- # 2 - SFI
- # 3 - K
- # 4 - I
- # 5 - text
- # 6 - spotter
- # 7 - origin
- # 8 - incoming interface callsign
- # this one doesn't filter, it just sets the hop count to 6 and is
- # used mainly just to override any isolation from WWV coming from
- # the internet.
- $in = [
- [ 1, 0, 'd', 0, 6 ]
- ];
+ 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 should be noted that the filter will start to be used only once a
- user/node has logged out and back in again.
- I am not going to spend any more time on these filters now as they
- will become more "comprehensive" in the near future.
+ It is possible to do much more complex rules, there are up to 10
+ accept/reject pairs per callsign per filter. For more information see
+ the next section.
- 3. Filtering (New Style v1.45 and later)
- 3.1. General filter rules
+ 1.5. General filter rules
Upto v1.44 it was not possible for the user to set their own filters.
From v1.45 though that has all changed. It is now possible to set
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 .....
+
+
+ accept/spots .....
+ reject/spots .....
the same principles to all types of filter.
- 3.2. Types of filter
+ 1.6. Types of filter
There are two main types of filter, accept or reject. You can use
either to achieve the result you want dependent on your own preference
- 3.3. Filter options
+ 1.7. Filter options
You can filter in several different ways. The options are listed in
the various helpfiles for accept, reject and filter.
- 3.4. Default filters
+ 1.8. Default filters
Sometimes all that is needed is a general rule for node connects.
This can be done with a node_default filter. This rule will always be
to add a rule for the hops for spots also.
- 3.5. Advanced filtering
+ 1.9. Advanced filtering
Once you are happy with the results you get, you may like to
experiment.
VHF/UHF spots from EU.
+ 1.10. Basic hop control
+
+ In /spider/data you will find a file called hop_table.pl. This is the
+ file that controls your hop count settings. It has a set of default
+ hops on the various PC frames and also a set for each node you want to
+ alter the hops for. You may be happy with the default settings of
+ course, but this powerful tool can help to protect and improve the
+ network. The file will look something like this ...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # hop table construction
+ #
+
+ package DXProt;
+
+ # default hopcount to use
+ $def_hopcount = 5;
+
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
+
+
+ # the per node hop control thingy
+
+
+ %nodehops =
+
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
+
+
+
+
+
+ Each set of hops is contained within a pair of curly braces and
+ contains a series of PC frame types. PC11 for example is a DX spot.
+ The figures here are not exhaustive but should give you a good idea of
+ how the file works.
+
+
+ You can alter this file at any time, including whilst the cluster is
+ running. If you alter the file during runtime, the command load/hops
+ will bring your changes into effect.
+
+
+
+ 1.11. Isolating networks
+
+ It is possible to isolate networks from each other on a "gateway" node
+ using the set/isolate <node_call> command.
+
+
+ The effect of this is to partition an isolated network completely from
+ another node connected to your node. Your node will appear on and
+ otherwise behave normally on every network to which you are connected,
+ but data from an isolated network will not cross onto any other
+ network or vice versa. However all the spot, announce and WWV traffic
+ and personal messages will still be handled locally (because you are a
+ real node on all connected networks), that is locally connected users
+ will appear on all networks and will be able to access and receive
+ information from all networks transparently. All routed messages will
+ be sent as normal, so if a user on one network knows that you are a
+ gateway for another network, he can still still send a talk/announce
+ etc message via your node and it will be routed across.
+
+
+ The only limitation currently is that non-private messages cannot be
+ passed down isolated links regardless of whether they are generated
+ locally. This will change when the bulletin routing facility is added.
+
+
+ If you use isolate on a node connection you will continue to receive
+ all information from the isolated partner, however you will not pass
+ any information back to the isolated node. There are times when you
+ would like to forward only spots across a link (maybe during a contest
+ for example). To do this, isolate the node in the normal way and put
+ in a filter in the /spider/filter/spots directory to override the
+ isolate. This filter can be very simple and consists of just one line
+ ....
+
+
+
+ $in = [
+ [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
+ ];
+
+
+
- 4. Other filters
- 4.1. Filtering Mail
+ 2. Other filters
+
+ 2.1. Filtering Mail
In the /spider/msg directory you will find a file called
badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
-
-
# the list of regexes for messages that we won't store having
# received them (bear in mind that we must receive them fully before
# we can bin them)
etc in a particular country.
- 4.2. Filtering DX callouts (Depricated)
+ 2.2. Filtering DX callouts (Depricated)
From version 1.47, this method is replaced by the command set/baddx
- 4.3. Filtering words from text fields in Announce, Talk and DX spots
+ 2.3. Filtering words from text fields in Announce, Talk and DX spots
Create a file in /spider/data called badwords. The format is quite
simple. Lines beginning with # are ignored so comments can be added.
load/badwords.
- 5. Mail
+ 3. Mail
DXSpider deals seamlessly with standard AK1A type mail. It supports
both personal and bulletin mail and the sysop has additional commands
The cluster mail is automatically deleted after 30 days unless the
sysop sets the "keep" flag using the msg command.
- 5.1. Personal mail
+ 3.1. Personal mail
Personal mail is sent using the sp command. This is actually the
default method of sending mail and so a simple s for send will do. A
section, so I will not duplicate them here.
- 5.2. Bulletin mail
+ 3.2. Bulletin mail
Bulletin mail is sent by using the sb command. This is one of the
most common mistakes users make when sending mail. They send a
Bulletin addresses can be set using the Forward.pl file.
- 5.3. Forward.pl
+ 3.3. Forward.pl
DXSpider receives all and any mail sent to it without any alterations
needed in files. Because personal and bulletin mail are treated
- 5.4. The msg command
+ 3.4. The msg command
The msg command is a very powerful and flexible tool for the sysop.
It allows the sysop to alter to and from fields and make other changes
user.
- 5.5. Message status
+ 3.5. Message status
You can check on a message from within the cluster by using the
command stat/msg. This will give you additional information on the
- 5.6. Filtering mail
+ 3.6. Filtering mail
This is described in the section on Other filters so I will not
duplicate it here.
- 5.7. Distribution lists
+ 3.7. Distribution lists
Distribution lists are simply a list of users to send certain types of
mail to. An example of this is mail you only wish to send to other
list.
- 5.8. BBS interface
+ 3.8. BBS interface
Spider provides a simple BBS interface. No input is required from the
sysop of the cluster at all. The BBS simply sets the cluster as a BBS
using the Forward.pl file very carefully.
- 6. Databases
+ 4. 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.
- 6.1. Creating databases
+ 4.1. Creating databases
Creating a database could not be more simple. All the commands are
sent from the cluster prompt as the sysop user.
chain can be a remote database.
- 6.2. Importing databases
+ 4.2. Importing databases
The only databases that Spider can currently import are the standard
AK1A databases such as OBLAST or the DB0SDX qsl and address database.
does not exist.
- 6.3. Checking available databases
+ 4.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
- 6.4. Looking up databases
+ 4.4. Looking up databases
To look for information in a defined database, simply use the dbshow
command, for example ...
Now you can simply use show/buckmaster or an abreviation.
- 6.5. Removing databases
+ 4.5. Removing databases
To delete an existing database you use the dbremove command. For
example ...
created from scratch if you still required it.
- 7. Information, files and useful programs
+ 5. Information, files and useful programs
- 7.1. MOTD
+ 5.1. MOTD
One of the more important things a cluster sysop needs to do is to get
information to his users. The simplest way to do this is to have a
to the cluster.
- 7.2. Downtime message
+ 5.2. Downtime message
If for any reason the cluster is down, maybe for upgrade or
maintenance but the machine is still running, a message can be sent to
actually running.
- 7.3. Other text messages
+ 5.3. Other text messages
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
The page length will of course depend on what you have it set to!
- 7.4. The Aliases file
+ 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
the results once you have set an alias.
- 7.5. Console.pl
+ 5.5. Console.pl
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
edit the file with your favourite editor.
- 7.6. Updating kepler data
+ 5.6. Updating kepler data
Spider has a powerful and flexible show/satellite command. In order
for this to be accurate, the kepler data has to be updated regularly.
- 7.7. The QRZ callbook
+ 5.7. The QRZ callbook
The command sh/qrz will only work once you have followed a few simple
steps. First you need to get a user ID and password from qrz.com.
proprieter of qrz.com for allowing this access.
- 8. CVS
+ 6. CVS
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
You will find any changes documented in the /spider/Changes file.
- 9. The DXSpider command set
+ 7. The DXSpider command set
Below is a complete list of commands available from the cluster
prompt. Most maintenance tasks are automatic but there are some
is the permissions level needed to use the command.
- 9.1. accept/announce (0)
+ 7.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
but this probably for advanced users...
- 9.2. accept/announce (extended for sysops) (8)
+ 7.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
- 9.3. accept/spots (0)
+ 7.3. accept/route (8)
+
+ accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
+ routing
+
+
+ Create an 'accept this routing PC Protocol' line for a filter.
+
+
+ An accept filter line means that if a PC16/17/19/21/24/41/50 matches
+ this filter it is passed thru that interface. See HELP FILTERING for
+ more info. Please read this to understand how filters work - it will
+ save a lot of grief later on.
+
+
+ You can use any of the following things in this line:-
+
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
+
+
+
+ some examples:-
+
+
+
+ acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
+ You can use the tag 'all' to accept everything eg:
+
+
+
+ acc/route all
+
+
+
+
+
+ 7.4. accept/spots (0)
accept/announce [0-9] <pattern> Set an accept filter line for spots
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
this is more efficient than saying simply: freq HF (but don't get too
hung up about that)
+
some examples:-
acc/spot 3 all
-
-
-
but this probably for advanced users...
- 9.4. accept/spots (extended for sysops) (8)
+ 7.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
- 9.5. accept/wcy (0)
+ 7.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
See HELP FILTER for information.
- 9.6. accept/wcy (extended for sysops) (8)
+ 7.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
- 9.7. accept/wwv (0)
+ 7.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
See HELP FILTER for information.
-
-
- 9.8. accept/wwv (extended for sysops) (8)
+ 7.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
- 9.9. announce (0)
+
+ 7.10. announce (0)
announce <text> Send an announcement to local users
Send an announcement to LOCAL users only, where <text> is the text of
- the announcement you wish to broadcast
+ the announcement you wish to broadcast. If you do not wish to receive
+ announces, use the set/noannounce command. Any announces made by a
+ sysop will override set/noannounce.
- 9.10. announce full (0)
+ 7.11. announce full (0)
announce full <text> Send an announcement cluster wide
- 9.11. announce sysop (5)
+ 7.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 9.12. apropos (0)
+ 7.13. apropos (0)
apropos <string> Search the help database
print the names of all the commands that may be relevant.
- 9.13. bye (0)
+ 7.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
-
-
- 9.14. catchup (5)
+ 7.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
Order is not important.
- 9.15. clear/spots (0)
+ 7.16. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
- 9.16. connect (5)
+
+
+ 7.17. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 9.17. dbavail (0)
+ 7.18. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 9.18. dbcreate (9)
+ 7.19. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
No checking is done to see if the any of the chained databases exist,
in fact it is usually better to do the above statement first then do
each of the chained databases.
+
Databases can exist offsite. To define a database that lives on
another node do:
It would be normal for you to add an entry into your local Aliases
file to allow people to use the 'SHOW/<dbname>' style syntax. So you
would need to add a line like:-
-
-
-
's' => [
..
..
databases. See DBSHOW for generic database enquiry
- 9.19. dbimport (9)
+ 7.20. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 9.20. dbremove (9)
+ 7.21. dbremove (9)
dbremove <dbname> Delete a database
You have been warned.
- 9.21. dbshow (0)
+ 7.22. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
+
This is the generic user interface to the database to the database
system. It is expected that the sysop will add an entry to the local
Aliases file so that users can use the more familiar AK1A style of
- 9.22. debug (9)
+ 7.23. debug (9)
debug Set the cluster program into debug mode
finished.
- 9.23. directory (0)
+ 7.24. directory (0)
directory List messages
directory own List your own messages
You can combine some of the various directory commands together eg:-
-
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
- 9.24. directory (extended for sysops) (5)
+ 7.25. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 9.25. disconnect (8)
+ 7.26. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 9.26. dx (0)
+ 7.27. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
-
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
- DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
cluster. See SHOW/BANDS for more information.
- 9.27. export (9)
+ 7.28. export (9)
export <msgno> <filename> Export a message to a file
EXPORT 2345 /tmp/a
- 9.28. export_users (9)
+ 7.29. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
-
-
- 9.29. forward/latlong (8)
+ 7.30. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 9.30. forward/opername (1)
+ 7.31. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 9.31. help (0)
+ 7.32. help (0)
help <cmd> Get help on a command
commands to look at with HELP.
- 9.32. init (5)
+ 7.33. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 9.33. kill (0)
+ 7.34. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
-
-
-
- 9.34. kill (5)
+ 7.35. kill (5)
kill <msgno> [<msgno> ...] Remove or erase a message from the system
kill from <call> Remove all messages from a callsign
As a sysop you can kill any message on the system.
- 9.35. kill full (5)
+ 7.36. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
- 9.36. links (0)
+
+
+ 7.37. links (0)
links Show which nodes are physically connected
- 9.37. load/aliases (9)
+ 7.38. load/aliases (9)
load/aliases Reload the command alias table
- 9.38. load/baddx (9)
+ 7.39. load/baddx (9)
load/baddx Reload the bad DX table
if spotted, will not be passed on. FR0G and TEST are classic examples.
- 9.39. load/badmsg (9)
+ 7.40. load/badmsg (9)
load/badmsg Reload the bad message table
each message. If any of them match then that message is immediately
deleted on receipt.
- 9.40. load/badwords (9)
+
+ 7.41. load/badwords (9)
load/badwords Reload the badwords file
ignored.
- 9.41. load/bands (9)
+ 7.42. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 9.42. load/cmd_cache (9)
+ 7.43. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
was just after a cluster restart.
- 9.43. load/forward (9)
+ 7.44. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 9.44. load/messages (9)
+ 7.45. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 9.45. load/prefixes (9)
+ 7.46. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 9.46. merge (5)
+ 7.47. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 9.47. msg (9)
+ 7.48. 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
This will display more information on the message than DIR does.
- 9.48. pc (8)
+ 7.49. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
You can also use in the same way as a talk command to a connected user
but without any processing, added of "from <blah> to <blah>" or
whatever.
+
pc G1TLH Try doing that properly!!!
- 9.49. ping (1)
+ 7.50. ping (1)
ping <node> Check the link quality between nodes
- 9.50. rcmd (1)
+ 7.51. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
Cluster node that is connected to the system.
+
Whether you get any output is dependant on a) whether the other system
knows that the node callsign of this cluster is in fact a node b)
whether the other system is allowing RCMDs from this node and c)
whether you have permission to send this command at all.
- 9.51. read (0)
+ 7.52. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 9.52. read (extended for sysops) (5)
+ 7.53. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 9.53. reject/announce
+ 7.54. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
but this probably for advanced users...
- 9.54. reject/announce (extended for sysops) (8)
+ 7.55. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
- 9.55. reject/spots (0)
+ 7.56. reject/route (8)
+
+ reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
+ routing
+
+
+ Create an 'reject this routing PC Protocol' line for a filter.
+
+
+ An reject filter line means that if a PC16/17/19/21/24/41/50 matches
+ this filter it is NOT passed thru that interface. See HELP FILTERING
+ for more info. Please read this to understand how filters work - it
+ will save a lot of grief later on. You can use any of the following
+ things in this line:-
+
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
+
+
+
+ some examples:-
+
+
+
+
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+
+
+
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ rej/route all (equiv to [very] restricted mode)
+
+
+
+
+
+ 7.57. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
+
You can use the tag 'all' to reject everything eg:
but this probably for advanced users...
- 9.56. reject/spots (extended for sysops) (8)
+ 7.58. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
+ reject/spot db0sue-7 1 by_zone 14,15,16
+ reject/spot node_default all
+ set/hops node_default 10
-
-
-
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
+ reject/spot user_default by G,M,2
- 9.57. reject/wcy (0)
+ 7.59. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
See HELP FILTER for information.
- 9.58. reject/wcy (extended for sysops) (8)
+
+ 7.60. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 9.59. reject/wwv (0)
+ 7.61. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
See HELP FILTER for information.
- 9.60. reject/wwv (extended for sysops) (8)
+ 7.62. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
-
-
-
-
- 9.61. reply (0)
+ 7.63. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
-
- 9.62. send (0)
+ 7.64. send (0)
send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
is an alias for SEND PRIVATE
- 9.63. set/address (0)
+ 7.65. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 9.64. set/announce (0)
+ 7.66. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
-
- 9.65. set/arcluster (5)
+ 7.67. set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 9.66. set/baddx (8)
+ 7.68. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
-
Setting a word as 'baddx' will prevent spots with that word in the
callsign field of a DX spot from going any further. They will not be
displayed and they will not be sent onto other nodes.
- 9.67. set/badnode (6)
+ 7.69. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 9.68. set/badspotter (8)
+ 7.70. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
FILTERing.
- 9.69. set/beep (0)
+ 7.71. set/beep (0)
set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 9.70. set/clx (5)
+ 7.72. set/bbs (5)
+
+ set/bbs <call> [<call>..]Make <call> a BBS
+
+
+ 7.73. set/clx (5)
set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
node
Set the node_call as a CLX type node
- 9.71. set/debug (9)
+ 7.74. 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>
- 9.72. set/dx (0)
+ 7.75. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
-
-
- 9.73. set/dxgrid (0)
+ 7.76. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 9.74. set/dxnet (5)
+ 7.77. set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 9.75. set/echo (0)
+ 7.78. 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.
- 9.76. set/here (0)
+ 7.79. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
- 9.77. set/homenode (0)
+
+
+ 7.80. set/homenode (0)
set/homenode <node_call> Set your home cluster
-
-
- 9.78. set/hops (8)
+ 7.81. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
creates a filter and works in conjunction with the filter system.
- 9.79. set/isolate (9)
+ 7.82. 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.
- 9.80. set/language (0)
+ 7.83. set/language (0)
set/language <language> Set the language you wish to use
You can select the language that you want the cluster to use.
Currently the languages available are en (English) and nl (Dutch).
-
- 9.81. set/location (0)
+ 7.84. set/location (0)
set/location <lat and long> Set your latitude and longitude
- 9.82. set/sys_location (9)
+
+ 7.85. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
- 9.83. set/logininfo (0)
+ 7.86. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 9.84. set/lockout (9)
+ 7.87. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 9.85. set/name (0)
+ 7.88. set/name (0)
set/name <your_name> Set your name
set/name Dirk
-
-
-
- 9.86. set/node (9)
+ 7.89. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
-
-
- set/spider
- set/dxnet
- set/clx
- set/arcluster
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
To see what your nodes are set to, use the show/nodes command.
- 9.87. set/obscount (9)
+ 7.90. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 9.88. set/page (0)
+ 7.91. set/page (0)
set/page <n> Set the number of lines per page
- 9.89. set/password (9)
+
+ 7.92. set/password (9)
set/password <callsign> <string> Set a users password
type password.
-
- 9.90. set/pinginterval (9)
+ 7.93. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 9.91. set/privilege (9)
+ 7.94. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
connection your privilege will automatically be set to 0.
- 9.92. set/spider (5)
+ 7.95. set/spider (5)
set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
+
Set the node_call as a DXSpider type node
- 9.93. set/sys_qra (9)
+ 7.96. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 9.94. set/qra (0)
+ 7.97. set/qra (0)
set/qra <locator> Set your QRA locator
- 9.95. set/qth (0)
+ 7.98. set/qth (0)
set/qth <your QTH> Set your QTH
- 9.96. set/talk (0)
+ 7.99. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 9.97. set/wcy (0)
+ 7.100. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 9.98. set/wwv (0)
+ 7.101. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
Allow WWV information to be seen at your console. You can switch off
WWV messages with the unset/wwv command.
-
- 9.99. set/wx (0)
+ 7.102. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
-
-
-
- 9.100. show/baddx (1)
+ 7.103. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 9.101. show/badnode (6)
+ 7.104. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 9.102. show/badspotter (1)
+ 7.105. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 9.103. show/configuration (0)
+ 7.106. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 9.104. show/configuration/node (0)
+ 7.107. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 9.105. show/connect (1)
+ 7.108. show/connect (1)
show/connect Show all the active connections
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
-
-
- 9.106. show/date (0)
+ 7.109. show/date (0)
show/date [<prefix>|<callsign>] Show the local time
This is very nearly the same as SHOW/TIME, the only difference the
format of the date string if no arguments are given.
+
If no prefixes or callsigns are given then this command returns the
local time and UTC as the computer has it right now. If you give some
prefixes then it will show UTC and UTC + the local offset (not
including DST) at the prefixes or callsigns that you specify.
- 9.107. show/debug (9)
+ 7.110. show/debug (9)
show/debug Show what levels of debug you are logging
The levels can be set with set/debug
- 9.108. show/dx (0)
+ 7.111. show/dx (0)
show/dx [options] interrogate the spot database
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
-
-
-
e.g.
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
- 9.109. show/dxcc (0)
+ 7.112. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
- 9.110. show/files (0)
+ 7.113. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
-
See also TYPE - to see the contents of a file.
-
- 9.111. show/filter (0)
+ 7.114. show/filter (0)
show/filter Show the filters you have set
displays all the filters set - for all the various categories.
- 9.112. show/filter (extended for sysops) (5)
+ 7.115. show/filter (extended for sysops) (5)
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 9.113. show/hops (8)
+ 7.116. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 9.114. show/isolate (1)
+ 7.117. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 9.115. show/lockout (9)
+ 7.118. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 9.116. show/log (8)
+ 7.119. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 9.117. show/moon (0)
+ 7.120. 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.
- 9.118. show/muf (0)
+ 7.121. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
- SH/MUF W
+ SH/MUF W
+
+
+
produces:
terrible accurate, but it is included for completeness.
- 9.119. show/node (1)
+ 7.122. 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.
- 9.120. show/prefix (0)
+ 7.123. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
See also SHOW/DXCC
- 9.121. show/program (5)
+
+
+ 7.124. show/program (5)
show/program Show the locations of all the included program modules
from.
- 9.122. show/qra (0)
+ 7.125. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
- 9.123. show/qrz (0)
+ 7.126. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
- 9.124. show/route (0)
+
+
+
+ 7.127. show/route (0)
show/route <callsign> Show the route to <callsign>
- sh/route n2tly
+ sh/route n2tly
- 9.125. show/satellite (0)
+ 7.128. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
- 9.126. show/sun (0)
+ 7.129. 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:-
- 9.127. show/time (0)
+ 7.130. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 9.128. show/wcy (0)
+ 7.131. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 9.129. show/wwv (0)
+ 7.132. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 9.130. shutdown (5)
+ 7.133. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 9.131. spoof (9)
+ 7.134. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
- 9.132. stat/db (5)
+
+
+
+ 7.135. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
-
-
- 9.133. stat/channel (5)
+ 7.136. 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.
- 9.134. stat/msg (5)
+ 7.137. stat/msg (5)
stat/msg <msgno> Show the status of a message
etc etc.
- 9.135. stat/user (5)
+ If no message number is given then the status of the message system is
+ displayed.
+
+
+ 7.138. stat/route_node (5)
+
+ stat/route_node <callsign> Show the data in a Route::Node object
+
+
+ 7.139. stat/route_user (5)
+
+ stat/route_user <callsign> Show the data in a Route::User object
+
+
+ 7.140. 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.
- 9.136. sysop (0)
+ 7.141. sysop (0)
sysop Regain your privileges if you login remotely
or 2 0 5 7 3
or 20573
+
+
+
They will all match. If there is no password you will still be offered
numbers but nothing will happen when you input a string. Any match is
case sensitive.
- 9.137. talk (0)
+ 7.142. 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
- 9.138. type (0)
+ 7.143. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
enter:-
+
TYPE bulletins/arld051
content.
- 9.139. who (0)
+ 7.144. who (0)
who Show who is physically connected locally
what sort of connection they have
- 9.140. wx (0)
+ 7.145. 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
- 9.141. wx (enhanced for sysops) (5)
+ 7.146. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
projects / spider.git / blobdiff