- The DXSpider Installation and Administration Manual
+ The DXSpider Administration Manual v1.48
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.30 January 2001
+ Version 1.48 August 2001 revision 1.1
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
- 1. Installation (Original version by Iain Phillips, G0RDI)
+ 1. Routing and Filtering
1.1 Introduction
- 1.2 Preparation
- 1.3 Installing the software
- 1.4 Setting callsigns etc
- 1.5 Starting up for the first time
-
- 2. The Client program
-
- 3. Configuration
-
- 3.1 Allowing ax25 connects from users
- 3.2 Allowing telnet connects from users
- 3.3 Setting up node connects
- 3.4 Connection scripts
- 3.5 Starting the connection
- 3.6 Telnet echo
-
- 4. Automating things
-
- 4.1 Autostarting the cluster
- 4.2 The crontab file
-
- 5. Hop control
-
- 5.1 Basic hop control
- 5.2 Isolating networks
-
- 6. Filtering (Old Style upto v1.44)
-
- 6.1 Spots
- 6.2 Announcements
- 6.3 WWV
-
- 7. Filtering (New Style v1.45 and later)
-
- 7.1 General filter rules
- 7.2 Types of filter
- 7.3 Filter options
- 7.4 Default filters
- 7.5 Advanced filtering
-
- 8. Other filters
-
- 8.1 Filtering Mail
- 8.2 Filtering DX callouts (Depricated)
- 8.3 Filtering words from text fields in Announce, Talk and DX spots
-
- 9. Information, files and useful programs
-
- 9.1 MOTD
- 9.2 Downtime message
- 9.3 Other text messages
- 9.4 The Aliases file
- 9.5 Forward.pl
- 9.6 Distribution lists
- 9.7 Console.pl
- 9.8 BBS interface
-
- 10. CVS
-
- 11. The DXSpider command set
-
- 11.1 accept/announce (0)
- 11.2 accept/announce (extended for sysops) (8)
- 11.3 accept/spots (0)
- 11.4 accept/spots (extended for sysops) (8)
- 11.5 accept/wcy (0)
- 11.6 accept/wcy (extended for sysops) (8)
- 11.7 accept/wwv (0)
- 11.8 accept/wwv (extended for sysops) (8)
- 11.9 announce (0)
- 11.10 announce full (0)
- 11.11 announce sysop (5)
- 11.12 apropos (0)
- 11.13 bye (0)
- 11.14 catchup (5)
- 11.15 clear/spots (0)
- 11.16 connect (5)
- 11.17 dbavail (0)
- 11.18 dbcreate (9)
- 11.19 dbimport (9)
- 11.20 dbremove (9)
- 11.21 dbshow (0)
- 11.22 debug (9)
- 11.23 directory (0)
- 11.24 directory (extended for sysops) (5)
- 11.25 disconnect (8)
- 11.26 dx (0)
- 11.27 export (9)
- 11.28 export_users (9)
- 11.29 forward/latlong (8)
- 11.30 forward/opername (1)
- 11.31 help (0)
- 11.32 init (5)
- 11.33 kill (0)
- 11.34 kill (5)
- 11.35 kill full (5)
- 11.36 links (0)
- 11.37 load/aliases (9)
- 11.38 load/baddx (9)
- 11.39 load/badmsg (9)
- 11.40 load/badwords (9)
- 11.41 load/bands (9)
- 11.42 load/cmd_cache (9)
- 11.43 load/forward (9)
- 11.44 load/messages (9)
- 11.45 load/prefixes (9)
- 11.46 merge (5)
- 11.47 msg (9)
- 11.48 pc (8)
- 11.49 ping (1)
- 11.50 rcmd (1)
- 11.51 read (0)
- 11.52 read (extended for sysops) (5)
- 11.53 reject/announce
- 11.54 reject/announce (extended for sysops) (8)
- 11.55 reject/spots (0)
- 11.56 reject/spots (extended for sysops) (8)
- 11.57 reject/wcy (0)
- 11.58 reject/wcy (extended for sysops) (8)
- 11.59 reject/wwv (0)
- 11.60 reject/wwv (extended for sysops) (8)
- 11.61 reply (0)
- 11.62 send (0)
- 11.63 set/address (0)
- 11.64 set/announce (0)
- 11.65 set/arcluster (5)
- 11.66 set/baddx (8)
- 11.67 set/badnode (6)
- 11.68 set/badspotter (8)
- 11.69 set/beep (0)
- 11.70 set/clx (5)
- 11.71 set/debug (9)
- 11.72 set/dx (0)
- 11.73 set/dxgrid (0)
- 11.74 set/dxnet (5)
- 11.75 set/echo (0)
- 11.76 set/here (0)
- 11.77 set/homenode (0)
- 11.78 set/hops (8)
- 11.79 set/isolate (9)
- 11.80 set/language (0)
- 11.81 set/location (0)
- 11.82 set/sys_location (9)
- 11.83 set/logininfo (0)
- 11.84 set/lockout (9)
- 11.85 set/name (0)
- 11.86 set/node (9)
- 11.87 set/obscount (9)
- 11.88 set/page (0)
- 11.89 set/password (9)
- 11.90 set/pinginterval (9)
- 11.91 set/privilege (9)
- 11.92 set/spider (5)
- 11.93 set/sys_qra (9)
- 11.94 set/qra (0)
- 11.95 set/qth (0)
- 11.96 set/talk (0)
- 11.97 set/wcy (0)
- 11.98 set/wwv (0)
- 11.99 set/wx (0)
- 11.100 show/baddx (1)
- 11.101 show/badnode (6)
- 11.102 show/badspotter (1)
- 11.103 show/date (0)
- 11.104 show/dx (0)
- 11.105 show/dxcc (0)
- 11.106 show/files (0)
- 11.107 show/filter (0)
- 11.108 show/filter (extended for sysops) (5)
- 11.109 show/hops (8)
- 11.110 show/isolate (1)
- 11.111 show/lockout (9)
- 11.112 show/moon (0)
- 11.113 show/muf (0)
- 11.114 show/node (1)
- 11.115 show/prefix (0)
- 11.116 show/program (5)
- 11.117 show/qra (0)
- 11.118 show/qrz (0)
- 11.119 show/route (0)
- 11.120 show/satellite (0)
- 11.121 show/sun (0)
- 11.122 show/time (0)
- 11.123 show/wcy (0)
- 11.124 show/wwv (0)
- 11.125 shutdown (5)
- 11.126 spoof (9)
- 11.127 stat/db (5)
- 11.128 stat/channel (5)
- 11.129 stat/msg (5)
- 11.130 stat/user (5)
- 11.131 sysop (0)
- 11.132 talk (0)
- 11.133 type (0)
- 11.134 who (0)
- 11.135 wx (0)
- 11.136 wx (enhanced for sysops) (5)
+ 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 Hop Control on Specific Nodes
+ 1.12 Isolating networks
+
+ 2. Other filters
+
+ 2.1 Filtering Mail
+ 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.4 The msg command
+ 3.5 Message status
+ 3.6 Filtering mail
+ 3.7 Distribution lists
+ 3.8 BBS interface
+
+ 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 Downtime message
+ 6.3 Other text messages
+ 6.4 The Aliases file
+ 6.5 Console.pl
+ 6.6 Updating kepler data
+ 6.7 The QRZ callbook
+
+ 7. CVS
+
+ 8. The DXSpider command set
+
+ 8.1 accept/announce (0)
+ 8.2 accept/announce (extended for sysops) (8)
+ 8.3 accept/route (8)
+ 8.4 accept/spots (0)
+ 8.5 accept/spots (extended for sysops) (8)
+ 8.6 accept/wcy (0)
+ 8.7 accept/wcy (extended for sysops) (8)
+ 8.8 accept/wwv (0)
+ 8.9 accept/wwv (extended for sysops) (8)
+ 8.10 announce (0)
+ 8.11 announce full (0)
+ 8.12 announce sysop (5)
+ 8.13 apropos (0)
+ 8.14 bye (0)
+ 8.15 catchup (5)
+ 8.16 clear/spots (0)
+ 8.17 connect (5)
+ 8.18 dbavail (0)
+ 8.19 dbcreate (9)
+ 8.20 dbimport (9)
+ 8.21 dbremove (9)
+ 8.22 dbshow (0)
+ 8.23 debug (9)
+ 8.24 directory (0)
+ 8.25 directory (extended for sysops) (5)
+ 8.26 disconnect (8)
+ 8.27 dx (0)
+ 8.28 export (9)
+ 8.29 export_users (9)
+ 8.30 forward/latlong (8)
+ 8.31 forward/opername (1)
+ 8.32 help (0)
+ 8.33 init (5)
+ 8.34 kill (0)
+ 8.35 kill (5)
+ 8.36 kill full (5)
+ 8.37 links (0)
+ 8.38 load/aliases (9)
+ 8.39 load/badmsg (9)
+ 8.40 load/bands (9)
+ 8.41 load/cmd_cache (9)
+ 8.42 load/forward (9)
+ 8.43 load/messages (9)
+ 8.44 load/prefixes (9)
+ 8.45 merge (5)
+ 8.46 msg (9)
+ 8.47 pc (8)
+ 8.48 ping (1)
+ 8.49 rcmd (1)
+ 8.50 read (0)
+ 8.51 read (extended for sysops) (5)
+ 8.52 reject/announce
+ 8.53 reject/announce (extended for sysops) (8)
+ 8.54 reject/route (8)
+ 8.55 reject/spots (0)
+ 8.56 reject/spots (extended for sysops) (8)
+ 8.57 reject/wcy (0)
+ 8.58 reject/wcy (extended for sysops) (8)
+ 8.59 reject/wwv (0)
+ 8.60 reject/wwv (extended for sysops) (8)
+ 8.61 reply (0)
+ 8.62 send (0)
+ 8.63 set/address (0)
+ 8.64 set/announce (0)
+ 8.65 set/arcluster (5)
+ 8.66 set/baddx (8)
+ 8.67 set/badnode (6)
+ 8.68 set/badspotter (8)
+ 8.69 set/beep (0)
+ 8.70 set/bbs (5)
+ 8.71 set/clx (5)
+ 8.72 set/debug (9)
+ 8.73 set/dx (0)
+ 8.74 set/dxgrid (0)
+ 8.75 set/dxnet (5)
+ 8.76 set/echo (0)
+ 8.77 set/here (0)
+ 8.78 set/homenode (0)
+ 8.79 set/hops (8)
+ 8.80 set/isolate (9)
+ 8.81 set/language (0)
+ 8.82 set/location (0)
+ 8.83 set/sys_location (9)
+ 8.84 set/logininfo (0)
+ 8.85 set/lockout (9)
+ 8.86 set/name (0)
+ 8.87 set/node (9)
+ 8.88 set/obscount (9)
+ 8.89 set/page (0)
+ 8.90 set/password (9)
+ 8.91 set/pinginterval (9)
+ 8.92 set/privilege (9)
+ 8.93 set/spider (5)
+ 8.94 set/sys_qra (9)
+ 8.95 set/qra (0)
+ 8.96 set/qth (0)
+ 8.97 set/talk (0)
+ 8.98 set/wcy (0)
+ 8.99 set/wwv (0)
+ 8.100 set/wx (0)
+ 8.101 show/baddx (1)
+ 8.102 show/badnode (6)
+ 8.103 show/badspotter (1)
+ 8.104 show/configuration (0)
+ 8.105 show/configuration/node (0)
+ 8.106 show/connect (1)
+ 8.107 show/date (0)
+ 8.108 show/debug (9)
+ 8.109 show/dx (0)
+ 8.110 show/dxcc (0)
+ 8.111 show/files (0)
+ 8.112 show/filter (0)
+ 8.113 show/filter (extended for sysops) (5)
+ 8.114 show/hops (8)
+ 8.115 show/isolate (1)
+ 8.116 show/lockout (9)
+ 8.117 show/log (8)
+ 8.118 show/moon (0)
+ 8.119 show/muf (0)
+ 8.120 show/node (1)
+ 8.121 show/prefix (0)
+ 8.122 show/program (5)
+ 8.123 show/qra (0)
+ 8.124 show/qrz (0)
+ 8.125 show/route (0)
+ 8.126 show/satellite (0)
+ 8.127 show/sun (0)
+ 8.128 show/time (0)
+ 8.129 show/wcy (0)
+ 8.130 show/wwv (0)
+ 8.131 shutdown (5)
+ 8.132 spoof (9)
+ 8.133 stat/db (5)
+ 8.134 stat/channel (5)
+ 8.135 stat/msg (5)
+ 8.136 stat/route_node (5)
+ 8.137 stat/route_user (5)
+ 8.138 stat/user (5)
+ 8.139 sysop (0)
+ 8.140 talk (0)
+ 8.141 type (0)
+ 8.142 who (0)
+ 8.143 wx (0)
+ 8.144 wx (enhanced for sysops) (5)
______________________________________________________________________
- 1\b1.\b. I\bIn\bns\bst\bta\bal\bll\bla\bat\bti\bio\bon\bn (\b(O\bOr\bri\big\bgi\bin\bna\bal\bl v\bve\ber\brs\bsi\bio\bon\bn b\bby\by I\bIa\bai\bin\bn P\bPh\bhi\bil\bll\bli\bip\bps\bs,\b, G\bG0\b0R\bRD\bDI\bI)\b)
+ 1. Routing and Filtering
- Last modified: 24 January 2001 by Ian Maude, G0VGS
+ 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\b1.\b.1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
- This section describes the installation of DX Spider v1.35 on a RedHat
- Linux Distribution. I do not intend to try and cover the installation
- of Linux or the setup of the AX25 utilities. If you need help on this
- then read Iains original HOWTO on the DXSpider website.
+ 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.
- I am assuming a general knowledge of Linux and its commands. You
- should know how to use _\bt_\ba_\br and how to edit files using your favourite
- editor.
+ 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 crucial ingredient for all of this is Perl 5.004. Now I know Perl
- 5.005 is out and this will almost certainly work with it, but RedHat
- 5.1 comes with 5.004. _\bB_\be _\bW_\ba_\br_\bn_\be_\bd, earlier versions of RedHat d\bdo\bo n\bno\bot\bt
- come with 5.004 as standard, you need to upgrade
+ 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).
- In addition to the standard Red Hat distribution you will require the
- following CPAN modules: -
+ 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.
- +\bo MD5-1.7.tar.gz
+ 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.
- +\bo Data-Dumper-2.10.tar.gz
- +\bo FreezeThaw-0.3.tar.gz
+ 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.
- +\bo MLDBM-2.00.tar.gz
- +\bo TimeDate-1.08.tar.gz
+ 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.
- +\bo IO-1.20.tar.gz
- +\bo Net-Telnet-3.02.tar.gz
- +\bo Curses-1.05.tar.gz
+ Anyway, without further discouragement, let me start the process of
+ explanation.
- +\bo Time-HiRes-01.20.tar.gz
+ 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.
- _\bD_\bo get the latest versions of these packages and install them but use
- the above list as the earliest versions usable.
- 1\b1.\b.2\b2.\b. P\bPr\bre\bep\bpa\bar\bra\bat\bti\bio\bon\bn
+ The generic commands are:-
- I will assume that you have already downloaded the latest tarball of
- the DXSpider software and are ready to install it. I am assuming
- version 1.35 for this section but of course you would use the latest
- version.
- Login as root and create a user to run the cluster under. _\bU_\bN_\bD_\bE_\bR _\bN_\bO
- _\bC_\bI_\bR_\bC_\bU_\bM_\bS_\bT_\bA_\bN_\bC_\bE_\bS _\bU_\bS_\bE _\bR_\bO_\bO_\bT _\bA_\bS _\bT_\bH_\bI_\bS _\bU_\bS_\bE_\bR_\b!. I am going to use the name
- _\bs_\by_\bs_\bo_\bp. You can call it anything you wish. Depending on your security
- requirements you may wish to use an existing user, however this is
- your own choice.
+ reject/route node_default <filter_option>
+ or
-
- # adduser -m sysop
-
-
-
-
-
- Now set a password for the user ...
-
-
-
- # passwd sysop
- # New UNIX password:
- # Retype new UNIX password:
- passwd: all authentication tokens updated successfully
-
-
-
-
-
- 1\b1.\b.3\b3.\b. I\bIn\bns\bst\bta\bal\bll\bli\bin\bng\bg t\bth\bhe\be s\bso\bof\bft\btw\bwa\bar\bre\be
-
- Now to unpack the DX Spider distribution, set symbolic links and group
- permissions. Copy the tarball to /home/sysop and do the following.
+ accept/route node_default <filter_option>
- # cd ~sysop
- # tar xvfz spider-1.35.tar.gz
- # ln -s ~sysop/spider /spider
- # groupadd -g 251 spider (or another number)
+ where filter_option is one of the following ...
- If you do not have the command _\bg_\br_\bo_\bu_\bp_\ba_\bd_\bd available to you simply add a
- line in /etc/group by hand.
+ call <prefixes>
+ call_dxcc <numbers>
+ call_itu <numbers>
+ call_zone <numbers>
+ channel <prefixes>
+ channel_dxcc <numbers>
+ channel_itu <numbers>
+ channel_zone <numbers>
- # vi /etc/group (or your favorite editor)
+ Please be careful if you alter this setting, it will affect ALL your
+ links!
+ 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:-
- You also need to add some others to the group, including your own
- callsign (this will be used as an alias) and root. The finished line
- in /etc/group should look something like this
- spider:x:251:sysop,g0vgs,root
- The next step is to set the permissions on the Spider directory tree
- and files ....
+ acc/route node_default call_dxcc 61,38
+ acc/route node_default call gb7djk
- # chown -R sysop.spider spider
- # find . -type d -exec chmod 2775 {} \;
- # find . -type f -exec chmod 775 {} \;
+ 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:
- This last step allows various users of the group _\bs_\bp_\bi_\bd_\be_\br to have write
- access to all the directories. This is not really needed just yet but
- will be useful when web interfaces start to appear.
- Finally, you need to fix the permissions on the ax25_call and
- netrom_call programs. Check where they are with the _\bl_\bo_\bc_\ba_\bt_\be command
- and alter the permissions with the _\bc_\bh_\bm_\bo_\bd command like this ..
+ rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
- # chown root ax25_call netrom_call
- # chmod 4775 ax25_call netrom_call
+ 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:-
- 1\b1.\b.4\b4.\b. S\bSe\bet\btt\bti\bin\bng\bg c\bca\bal\bll\bls\bsi\big\bgn\bns\bs e\bet\btc\bc
- Now login to your machine as the user you created earlier. In my case
- that user is called _\bs_\by_\bs_\bo_\bp. Once logged in, issue the following
- commands ....
+ set/debug filter
- $ cd /spider
- $ mkdir local
- $ mkdir local_cmd
- $ cp perl/DXVars.pm.issue local/DXVars.pm
- $ cd local
- $ vi DXVars.pm (or your favourite editor)
+ After you have got tired of that, to put it back the way it was:-
+ unset/debug filter
- Using the distributed DXVars.pm as a a template, set your cluster
- callsign, sysop callsign and other user info to suit your own
- environment. Note that this a perl file which will be parsed and
- executed as part of the cluster. If you get it wrong then perl will
- complain when you start the cluster process. It is important only to
- alter the text of any section. Some of the lines look a little odd.
- Take this line for example ....
- $myemail = "ianmaude\@btinternet.com";
- There appears to be an extra slash in there. However this has to be
- there for the file to work so leave it in.
+ 1.4. General route filtering
- P\bPL\bLE\bEA\bAS\bSE\bE U\bUS\bSE\bE C\bCA\bAP\bPI\bIT\bTA\bAL\bL L\bLE\bET\bTT\bTE\bER\bRS\bS F\bFO\bOR\bR C\bCA\bAL\bLL\bLS\bSI\bIG\bGN\bNS\bS
+ Exactly the same rules apply for general route filtering. You would
+ use either an accept filter or a reject filter like this ...
- DON'T alter the DXVars.pm (or any other file) in /spider/perl, they
- are overwritten with every release. Any files or commands you place in
- /spider/local or /spider/local_cmd will automagically be used in
- preference to the ones in /spider/perl EVEN while the cluster is
- running!
- Save the new file and change directory to ../perl ....
+ reject/route <node_call> <filter_option>
- $ cd ../perl
+ or
+ accept/route <node_call> <filter_option>
- Now type the following command which creates the basic user file with
- you as the sysop.
+ Here are some examples of route filters ...
- $ create_sysop.pl
+ 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)
- 1\b1.\b.5\b5.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg u\bup\bp f\bfo\bor\br t\bth\bhe\be f\bfi\bir\brs\bst\bt t\bti\bim\bme\be
+ In practice you will either be opening the default filter out for a
+ partner by defining a specific filter for that callsign:-
- We can now bring spider up for the first time and see if all is well
- or not! It should look something like this ...
+ acc/route gb7baa all
+ acc/route gb7baa input all
- $ cluster.pl
- DXSpider DX Cluster Version 1.35
- Copyright (c) 1998 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listener ...
- reading existing message headers
- reading cron jobs
- orft we jolly well go ...
+ or restricting it quite a lot, in fact making it very nearly like an
+ isolated node, like this:-
- If all is well then login on another term or console as _\bs_\by_\bs_\bo_\bp and cd
- to /spider/perl. Now issue the following command ...
+ acc/route pi4ehv-8 call gb7djk
+ rej/route pi4ehv-8 input call_dxcc 61,38
- $ client.pl
+ 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 do much more complex rules, there are up to 10
+ accept/reject pairs per callsign per filter. For more information see
+ the next section.
- This should log you into the cluster as the sysop under the alias
- callsign we set earlier. In this case the callsign is G0VGS. The
- cluster callsign is set in the DXVars.pm file in /spider/local. In
- this case we will assume that this was set as GB7MBC. You should
- therefore see this when you login ....
+ 1.5. General filter rules
- G0VGS de GB7MBC 19-Nov-1999 2150Z >
+ Upto v1.44 it was not possible for the user to set their own filters.
+ From v1.45 though that has all changed. It is now possible to set
+ filters for just about anything you wish. If you have just updated
+ from an older version of DXSpider you will need to update your new
+ filters. You do not need to do anything with your old filters, they
+ will be renamed as you update.
+ There are 3 basic commands involved in setting and manipulating
+ filters. These are accept, reject and clear. First we will look
+ generally at filtering. There are a number of things you can filter in
+ the DXSpider system. They all use the same general mechanism.
- If you do, congratulations! If not, look over the instructions again,
- you have probably missed something out. You can shut spider down
- again with the command ....
+ 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 ...
- shutdown
+ accept/spots .....
+ reject/spots .....
- and both the cluster and the client should return to Linux prompts.
+ 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.
- 2\b2.\b. T\bTh\bhe\be C\bCl\bli\bie\ben\bnt\bt p\bpr\bro\bog\bgr\bra\bam\bm
+ There is also a command to clear out one or more lines in a filter.
+ They are ...
- In earlier versions of Spider, all the processes were Perl scripts.
- This was fine but with a lot of users your computer memory would soon
- be used up. To combat this a new client was written in "C". This
- client only works for _\bi_\bn_\bc_\bo_\bm_\bi_\bn_\bg connects at the moment. Before you can
- use it though it has to be "made". CD to /spider/src and type _\bm_\ba_\bk_\be.
- You should see the output on your screen and hopefully now have a
- small C program called _\bc_\bl_\bi_\be_\bn_\bt. Leave it in this directory.
- 3\b3.\b. C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn
+ clear/spots 1
+ clear/spots all
- 3\b3.\b.1\b1.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg a\bax\bx2\b25\b5 c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
- As stated previously, the aim of this document is not to tell you how
- to configure Linux or the ax25 utilities. However, you do need to add
- a line in your ax25d.conf to allow connections to DXSpider for your
- users. For each interface that you wish to allow connections on, use
- the following format ...
+ There is clear/xxxx command for each type of filter.
- default * * * * * * - sysop /spider/src/client client %u ax25
+ and you can check that your filters have worked by the command ...
- 3\b3.\b.2\b2.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
+ show/filter
- Allowing telnet connections is quite simple. Firstly you need to add
- a line in /etc/services to allow connections to a port number, like
- this ....
- spdlogin 8000/tcp # spider anonymous login port
+ For now we are going to use spots for the examples, but you can apply
+ the same principles to all types of filter.
+ 1.6. Types of filter
- Then add a line in /etc/inetd.conf like this ....
+ There are two main types of filter, accept or reject. You can use
+ either to achieve the result you want dependent on your own preference
+ and which is more simple to do. It is pointless writing 8 lines of
+ reject filters when 1 accept filter would do the same thing! Each
+ filter has 10 lines (of any length) which are tried in order. If a
+ line matches then the action you have specified is taken (ie reject
+ means ignore it and accept means take it)
+ If you specify reject filters, then any lines that arrive that match
+ the filter will be dumped but all else will be accepted. If you use
+ an accept filter, then ONLY the lines in the filter will be accepted
+ and all else will be dumped. For example if you have a single line
+ accept filter ...
- spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
- This needs to be added above the standard services such as ftp, telnet
- etc. Once this is done, you need to restart inetd like this ....
+ then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
- killall -HUP inetd
+ If you set a reject filter like this ...
+ reject/spots on hf/cw
- Now login as _\bs_\by_\bs_\bo_\bp and cd spider/perl. You can test that spider is
- accepting telnet logins by issuing the following command ....
+ Then you will get everything EXCEPT HF CW spots. You could make this
+ single filter even more flexible. For example, if you are interested
+ in IOTA and will work it even on CW even though normally you are not
+ interested in CW, then you could say ...
- client.pl login telnet
+ reject/spots on hf/cw and not info iota
- You should get a login prompt and on issuing a callsign, you will be
- given access to the cluster. Note, you will not get a password login.
- There seems no good reason for a password prompt to be given so it is
- not asked for.
+ But in that case you might only be interested in iota and say:-
- Assuming all is well, then try a telnet from your linux console ....
+ accept/spots not on hf/cw or info iota
- telnet localhost 8000
+ which achieves exactly the same thing. You should choose one or the
+ other until you are comfortable with the way it works. You can mix
+ them if you wish (actually you can have an accept AND a reject on the
+ same line) but don't attempt this until you are sure you know what you
+ are doing!
- You should now get the login prompt and be able to login as before.
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. Here is an example ...
- 3\b3.\b.3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
- In order to allow cluster node connections, spider needs to know that
- the connecting callsign is a cluster node. This is the case whether
- the connect is incoming or outgoing. In spider this is a simple task
- and can be done in runtime.
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
- Later versions of Spider can distinguish different software and treat
- them differently. For example, the WCY beacon cannot be handles by
- AK1A type nodes as AK1A does not know what to do with PC73. There are
- 4 different types of node at present and although they may not have
- any major differences at the moment, it allows for compatibility. The
- 4 types are ...
+ 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.
- set/node (AK1A type)
- set/spider
- set/dxnet
- set/clx
+ This is an example where you would use a line number (1 and 2 in this
+ case), if you leave the digit out, the system assumes '1'. Digits
+ '0'-'9' are available. This make it easier to see just what filters
+ you have set. It also makes it more simple to remove individual
+ filters, during a contest for example.
+ You will notice in the above example that the second line has
+ brackets. Look at the line logically. You can see there are 2
+ separate sections to it. We are saying reject spots that are VHF or
+ above APART from those in zones 14, 15 and 16 (either spotted there or
+ originated there). If you did not have the brackets to separate the 2
+ sections, then Spider would read it logically from the front and see a
+ different expression entirely ...
- For now, we will assume that the cluster we are going to connect to is
- an AK1A type node.
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
- Start up the cluster as you did before and login as the sysop with
- client.pl. The cluster node I am wanting to make a connection to is
- GB7BAA but you would obviously use whatever callsign you required. At
- the prompt type ...
+ 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'.
- set/node gb7baa
+ As mentioned earlier, setting several filters can be more flexible
+ than simply setting one complex one. Doing it in this way means that
+ if you want to alter your filter you can just redefine or remove one
+ or more lines of it or one line. For example ...
+ reject/spots 1 on hf/ssb
- The case does not matter as long as you have a version of DXSpider
- later than 1.33. Earlier versions required the callsign to be in
- upper case.
- That is now set, it is as simple as that. To prove it, login on yet
- another console as sysop and issue the command ...
+ would redefine our earlier example, or
- client.pl gb7baa (using the callsign you set as a node)
+ clear/spots 1
+ To remove all the filter lines in the spot filter ...
- You should get an initialisation string from DXSpider like this ...
+ clear/spots all
- client.pl gb7baa
- PC38^GB7MBC^~
- If the callsign you just set up as a cluster node is for an incoming
- connect, this is all that needs to be done. If the connection is to
- be outgoing then a connection script needs to be written.
+ 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\b3.\b.4\b4.\b. C\bCo\bon\bnn\bne\bec\bct\bti\bio\bon\bn s\bsc\bcr\bri\bip\bpt\bts\bs
- Because DXSpider operates under Linux, connections can be made using
- just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
- possible examples. Connect scripts live in the /spider/connect
- directory and are simple ascii files. Writing a script for
- connections is therefore relatively simple.
- The connect scripts consist of lines which start with the following
- keywords or symbols:-
+ 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
+ followed, even if the link is isolated, unless another filter is set
+ specifically. Default rules can be set for nodes and users. They can
+ be set for spots, announces, WWV and WCY. They can also be used for
+ hops. An example might look like this ...
- # All lines starting with a # are ignored, as are completely
- blank lines.
- timeout timeout followed by a number is the number of seconds to wait for a
- command to complete. If there is no timeout specified in the script
- then the default is 60 seconds.
- abort abort is a regular expression containing one or more strings to look
- for to abort a connection. This is a perl regular expression and is
- executed ignoring case.
+ accept/spot node_default by_zone 14,15,16,20,33
+ set/hops node_default spot 50
- connect connect followed by ax25 or telnet and some type dependent
- information. In the case of a telnet connection, there can be up to
- two parameters.
- The first is the ip address or hostname of the computer you wish to
- connect to and the second is the port number you want to use (this
- can be left out if it is a normal telnet session).
- In the case of an ax25 session then this would normally be a call to
- ax25_call or netrom_call as in the example above. It is your
- responsibility to get your node and other ax25 parameters to work
- before going down this route!
- ' line in a chat type script. The words/phrases normally come in pairs,
- either can be empty. Each line reads input from the connection until
- it sees the string (or perl regular expression) contained in the
- left hand string. If the left hand string is empty then it doesn't
- read or wait for anything. The comparison is done ignoring case.
- When the left hand string has found what it is looking for (if it is)
- then the right hand string is sent to the connection.
- This process is repeated for every line of chat script.
- client client starts the connection, put the arguments you would want here
- if you were starting the client program manually. You only need this
- if the script has a different name to the callsign you are trying to
- connect to (i.e. you have a script called other which actually
- connects to GB7DJK-1 [instead of a script called gb7djk-1]).
+ This filter is for spots only, you could set others for announce, WWV
+ and WCY. This filter would work for ALL nodes unless a specific
+ filter is written to override it for a particular node. You can also
+ set a user_default should you require. It is important to note that
+ default filters should be considered to be "connected". By this I
+ mean that should you override the default filter for spots, you need
+ to add a rule for the hops for spots also.
+ 1.9. Advanced filtering
- There are many possible ways to configure the script but here are two
- examples, one for a NETRom/AX25 connect and one for tcp/ip.
+ Once you are happy with the results you get, you may like to
+ experiment.
+ The previous example that filters hf/cw spots and accepts vhf/uhf
+ spots from EU can be written with a mixed filter, for example ...
- timeout 60
- abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
- # you can leave this out if you call the script 'gb7dxm'
- client gb7dxm ax25
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+ Note that the first filter has not been specified with a number. This
+ will automatically be assumed to be number 1. In this case, we have
+ said reject all HF spots in the CW section of the bands but accept all
+ others at HF. Also accept anything in VHF and above spotted in or by
+ operators in the zones 14, 15 and 16. Each filter slot actually has a
+ 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
+ the accept slot.
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ 'accept'. In the example what happens is that the reject is executed
+ first, any non hf/cw spot is passed to the accept line, which lets
+ through everything else on HF. The next filter line lets through just
+ VHF/UHF spots from EU.
- timeout 15
- connect telnet dirkl.tobit.co.uk
- # tell GB7DJK-1 that it is connected to GB7DJK
- # you can leave this out if you call this script 'gb7djk'
- client gb7djk telnet
+ 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
+ #
- Both these examples assume that everything is set up properly at the
- other end. You will find other examples in the /spider/examples
- directory.
+ package DXProt;
+ # default hopcount to use
+ $def_hopcount = 5;
- 3\b3.\b.5\b5.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bco\bon\bnn\bne\bec\bct\bti\bio\bon\bn
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
- You start the connection, from within a sysop enabled cluster login,
- by typing in the word _\bc_\bo_\bn_\bn_\be_\bc_\bt followed by a script name like this ....
+ # the per node hop control thingy
- G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
- connection to GB7DJK-1 started
- G0VGS de GB7MBC 13-Dec-1998 2043Z >
+ %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,
+ },
+ };
- This will start a connection using the script called _\bg_\bb_\b7_\bd_\bj_\bk_\b-_\b1. You
- can follow the connection by watching the term or console from where
- you started _\bc_\bl_\bu_\bs_\bt_\be_\br_\b._\bp_\bl. You should see something like this ...
- <- D G1TLH connect gb7djk-1
- -> D G1TLH connection to GB7DJK-1 started
- -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
- timeout set to 15
- CONNECT sort: telnet command: dirkl.tobit.co.uk
- CHAT "login" -> "gb7djk"
- received "
- Red Hat Linux release 5.1 (Manhattan)
- Kernel 2.0.35 on an i586
- "
- received "login: "
- sent "gb7djk"
- CHAT "word" -> "gb7djk"
- received "gb7djk"
- received "Password: "
- sent "gb7djk"
- Connected to GB7DJK-1, starting normal protocol
- <- O GB7DJK-1 telnet
- -> B GB7DJK-1 0
- GB7DJK-1 channel func state 0 -> init
- <- D GB7DJK-1
- <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
- <- D GB7DJK-1 PC38^GB7DJK-1^~
- <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
- 0 00:00^5447^~
- etc
+ Each set of hops is contained within a pair of curly braces and
+ contains a series of PC frame types. PC11 for example is a DX spot.
+ The figures here are not exhaustive but should give you a good idea of
+ how the file works.
+ You can alter this file at any time, including whilst the cluster is
+ running. If you alter the file during runtime, the command load/hops
+ will bring your changes into effect.
+ 1.11. Hop Control on Specific Nodes
- With later versions of Spider there is a set/login command for users.
- This tells them when a user or node logs in or out. If you do not add
- a line to your scripts after the final line (or before the client line
- which should always be last if needed) then the login/logout
- information will be sent to users _\bb_\be_\bf_\bo_\br_\be the login actually completes.
- This means if a node is unreachable, it will continue sending logins
- and logouts to users even though it is not actually connecting. To
- avoid this use the following line ...
+ You can set a callsign specific hop count for any of the standard
+ filter options so:-
+ set/hops gb7djk spot 4
+ set/hops node_default route 10
+ set/hops gb7baa wcy 5
+ all work on their specific area of the protocol.
- In a script, this might look like ...
+ The set/hops command overrides any hops that you have set otherwise.
- timeout 35
- abort (Busy|Sorry|Fail)
- connect telnet mary 3000
+ You can set 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.
- 3\b3.\b.6\b6.\b. T\bTe\bel\bln\bne\bet\bt e\bec\bch\bho\bo
+ 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.
- Cluster links in particular suffer greatly from the presence of telnet
- echo. This is caused by the telnet negotiation itself and can create
- at worst severe loops. At best it creates unnecessary bandwidth and
- large logfiles! There are things that can be done to limit this
- problem but will not always work dependent on the route taken to
- connect.
+ 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 use
+ an acc/spot >call< allilter in the to override the isolate.
- Telnet echo itself should only be a problem if the connection is being
- made to the telnet port (23). This port uses special rules that
- include echo negotiation. If the connection is to a different port,
- such as 8000, this negotiation does not happen and therefore no echo
- should be present.
+ 2. Other filters
- Sometimes it is not possible to make a direct connection to another
- node and this can cause problems. There is a way of trying to
- suppress the telnet echo but this will not always work, unfortunately
- it is difficult to be more specific. Here is an example of what I
- mean ...
+ 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
+ original looks something like this ....
- timeout 35
- abort (Busy|Sorry|Fail)
- connect telnet mary.lancs.ac.uk
+ # 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
- So, the first connection is made by Spider. This is fine as Spider
- uses the Net_Telnet script from within perl. This actually uses TCP
- rather than TELNET so no negotiation will be done on the first
- connection. Once connected to mary.lancs.ac.uk, the command is sent
- to suppress echo. Now a telnet is made to a cluster node that is
- accepting connections on port 23. The problem with this link is that
- the negotiation is made by the remote machine, therefore you have no
- control over it. The chances are that this link will create echo and
- there will be no way you can stop it.
+ # 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.
- 4\b4.\b. A\bAu\but\bto\bom\bma\bat\bti\bin\bng\bg t\bth\bhi\bin\bng\bgs\bs
+ # The pattern can be undef or 0 in which case it will always be selected
+ # for the action specified
- Ok, you should now have DXSpider running nicely and allowing connects
- by cluster nodes or users. However, it has to be shutdown and
- restarted manually and if connection scripts fail they have to be
- started again manually too, not much use if you are not at the
- console! So, in this section we will automate both. Firstly starting
- the cluster.
- 4\b4.\b.1\b1.\b. A\bAu\but\bto\bos\bst\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bcl\blu\bus\bst\bte\ber\br
+ package DXMsg;
- This is not only a way to start the cluster automatically, it also
- works as a watchdog, checking the sanity of DXSpider and respawning it
- should it crash for any reason. Before doing the following, shutdown
- the cluster as you did earlier.
+ @badmsg = (
+ );
- Login as root and bring up the /etc/inittab file in your favourite
- editor. Add the following lines to the file near the end ...
- ##Start DXSpider on bootup and respawn it should it crash
- DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+ I think this is fairly self explanatory. It is simply a list of
+ subject headers that we do not want to pass on to either the users of
+ the cluster or the other cluster nodes that we are linked to. This is
+ usually because of rules and regulations pertaining to items for sale
+ etc in a particular country.
+ 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.
- This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
- restart it should it crash for any reason.
+ 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.
- As root type the command _\bt_\be_\bl_\bi_\bn_\bi_\bt _\bq. DXSpider should start up
- immediately. You will see the output on tty7 and if you login as
- _\bs_\by_\bs_\bo_\bp you should find everything running nicely.
+ 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
- So far so good, now to automate script connections...
+ There are a number of commands that control whether a spot progresses
+ any further by regarding it as "bad" in some way.
- 4\b4.\b.2\b2.\b. T\bTh\bhe\be c\bcr\bro\bon\bnt\bta\bab\bb f\bfi\bil\ble\be
- Login as _\bs_\by_\bs_\bo_\bp and create a file in /spider/local_cmd called crontab.
- Edit it with your favourite editor and add a line like this (I have
- included a comment)
+ A DX Spot has a number of fields which can 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:-
- # check every 10 minutes to see if gb7xxx is connected and if not
- # start a connect job going
- 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
+ set/baddx
+ set/badspotter
+ set/badnode
+ These work in the same as the set/badword command, you can add any
+ words or callsigns or whatever to the appropriate database. For
+ example, to stop a spot from a particular node you do:
- The callsign involved will be the callsign of the cluster node you are
- going to connect to. This will now check every 10 minutes to see if
- gb7xxx is connected, if it is then nothing will be done. If it is
- not, then a connect attempt will be started.
- There are probably lots of other things you could use this crontab
- file for. If you want to know more about it, look at the DXSpider
- website at the cron page where it is explained more fully.
+ set/badnode gb7djk gb7dxc
- 5\b5.\b. H\bHo\bop\bp c\bco\bon\bnt\btr\bro\bol\bl
- 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).
+ a bad spotter:
- 5\b5.\b.1\b1.\b. B\bBa\bas\bsi\bic\bc h\bho\bop\bp c\bco\bon\bnt\btr\bro\bol\bl
- 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 ...
+ set/badspotter b0mb p1rat nocall
+ and some bad dx:
+ set/baddx video wsjt
+ You can remove a word using the appropriate unset command
+ (unset/baddx, unset/badspotter, unset/badnode) or list them using one
+ of show/baddx, show/badspotter and show/badnode.
+ 3. Mail
+ DXSpider deals seamlessly with standard AK1A type mail. It supports
+ both personal and bulletin mail and the sysop has additional commands
+ to ensure that mail gets to where it is meant. DXSpider will send
+ mail almost immediately, assuming that the target is on line.
+ However, only one mail message is dealt with at any one time. If a
+ mail message is already being sent or recieved, then the new message
+ will be queued until it has finished.
+ The cluster mail is automatically deleted after 30 days unless the
+ sysop sets the "keep" flag using the msg command.
+ 3.1. Personal mail
+ Personal mail is sent using the sp command. This is actually the
+ default method of sending mail and so a simple s for send will do. A
+ full list of the send commands and options is in the command set
+ section, so I will not duplicate them here.
+ 3.2. Bulletin mail
+ Bulletin mail is sent by using the sb command. This is one of the
+ most common mistakes users make when sending mail. They send a
+ bulletin mail with s or sp instead of sb and of course the message
+ never leaves the cluster. This can be rectified by the sysop by using
+ the msg command.
+ Bulletin addresses can be set using the Forward.pl file.
+ 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
+ differently, there is no need for a list of accepted bulletin
+ addresses. It is necessary, however, to tell the program which links
+ accept which bulletins. For example, it is pointless sending
+ bulletins addresses to "UK" to any links other than UK ones. The file
+ that does this is called forward.pl and lives in /spider/msg. At
+ default, like other spider files it is named forward.pl.issue. Rename
+ it to forward.pl and edit the file to match your requirements. The
+ format is below ...
+ #
+ # this is an example message forwarding file for the system
+ #
+ # The format of each line is as follows
+ #
+ # type to/from/at pattern action destinations
+ # P/B/F T/F/A regex I/F [ call [, call ...] ]
+ #
+ # type: P - private, B - bulletin (msg), F - file (ak1a bull)
+ # to/from/at: T - to field, F - from field, A - home bbs, O - origin
+ # pattern: a perl regex on the field requested
+ # action: I - ignore, F - forward
+ # destinations: a reference to an array containing node callsigns
+ #
+ # if it is non-private and isn't in here then it won't get forwarded
+ #
+ # Currently only type B msgs are affected by this code.
+ #
+ # The list is read from the top down, the first pattern that matches
+ # causes the action to be taken.
+ #
+ # The pattern can be undef or 0 in which case it will always be selected
+ # for the action specified
+ #
+ # If the BBS list is undef or 0 and the action is 'F' (and it matches the
+ # pattern) then it will always be forwarded to every node that doesn't have
+ # it (I strongly recommend you don't use this unless you REALLY mean it, if
+ # you allow a new link with this on EVERY bull will be forwarded immediately
+ # on first connection)
+ #
+ package DXMsg;
+ @forward = (
+ );
+ 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
- #
- # hop table construction
- #
- package DXProt;
+ 3.4. The msg command
- # default hopcount to use
- $def_hopcount = 5;
+ The msg command is a very powerful and flexible tool for the sysop.
+ It allows the sysop to alter to and from fields and make other changes
+ to manage the cluster mail.
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
+ Here is a full list of the various options ...
- # the per node hop control thingy
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waiting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
- %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 _\bl_\bo_\ba_\bd_\b/_\bh_\bo_\bp_\bs
- will bring your changes into effect.
-
-
-
- 5\b5.\b.2\b2.\b. I\bIs\bso\bol\bla\bat\bti\bin\bng\bg n\bne\bet\btw\bwo\bor\brk\bks\bs
-
- It is possible to isolate networks from each other on a "gateway" node
- using the _\bs_\be_\bt_\b/_\bi_\bs_\bo_\bl_\ba_\bt_\be _\b<_\bn_\bo_\bd_\be_\b__\bc_\ba_\bl_\bl_\b> command.
-
-
- The effect of this is to partition an isolated network completely from
- another nodes connected to your node. Your node will appear on and
- otherwise behave normally on every network to which you are connected,
- but data from an isolated network will not cross onto any other
- network or vice versa. However all the spot, announce and WWV traffic
- and personal messages will still be handled locally (because you are a
- real node on all connected networks), that is locally connected users
- will appear on all networks and will be able to access and receive
- information from all networks transparently. All routed messages will
- be sent as normal, so if a user on one network knows that you are a
- gateway for another network, he can still still send a talk/announce
- etc message via your node and it will be routed across.
-
-
- The only limitation currently is that non-private messages cannot be
- passed down isolated links regardless of whether they are generated
- locally. This will change when the bulletin routing facility is added.
-
-
- If you use isolate on a node connection you will continue to receive
- all information from the isolated partner, however you will not pass
- any information back to the isolated node. There are times when you
- would like to forward only spots across a link (maybe during a contest
- for example). To do this, isolate the node in the normal way and put
- in a filter in the /spider/filter/spots directory to override the
- isolate. This filter can be very simple and consists of just one line
- ....
-
-
-
- $in = [
- [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
- ];
-
-
-
-
-
- There is a lot more on filtering in the next section.
-
-
- 6\b6.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(O\bOl\bld\bd S\bSt\bty\byl\ble\be u\bup\bpt\bto\bo v\bv1\b1.\b.4\b44\b4)\b)
-
- 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 _\b._\bi_\bs_\bs_\bu_\be. There are two
- types of filter, one for incoming information and one for outgoing
- information. Outgoing filters are in the form _\bC_\bA_\bL_\bL_\bS_\bI_\bG_\bN_\b._\bp_\bl and
- incoming filters are in the form _\bi_\bn_\b__\bC_\bA_\bL_\bL_\bS_\bI_\bG_\bN_\b._\bp_\bl. Filters can be set
- for both nodes and users.
-
-
- All filters work in basically the same way. There are several
- elements delimited by commas. There can be many lines in the filter
- and they are read from the top by the program. When writing a filter
- you need to think carefully about just what you want to achieve. You
- are either going to write a filter to _\ba_\bc_\bc_\be_\bp_\bt or to _\br_\be_\bj_\be_\bc_\bt. Think of a
- filter as having 2 main elements. For a reject filter, you would have
- a line or multiple lines rejecting the things you do not wish to
- receive and then a default line accepting everything else that is not
- included in the filter. Likewise, for an accept filter, you would
- have a line or multiple lines accepting the things you wish to receive
- and a default line rejecting everthing else.
-
-
- In the example below, a user requires a filter that would only return
- SSB spots posted in Europe on the HF bands. This is achieved by first
- rejecting the CW section of each HF band and rejecting all of VHF, UHF
- etc based on frequency. Secondly, a filter rule is set based on CQ
- zones to only accept spots posted in Europe. Lastly, a default filter
- rule is set to reject anything outside the filter.
-
-
-
- $in = [
- [ 0, 0, 'r', # reject all CW spots
- [
- 1800.0, 1850.0,
- 3500.0, 3600.0,
- 7000.0, 7040.0,
- 14000.0, 14100.0,
- 18068.0, 18110.0,
- 21000.0, 21150.0,
- 24890.0, 24930.0,
- 28000.0, 28180.0,
- 30000.0, 49000000000.0,
- ] ,1 ],
- [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
- [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-
-
-
-
-
- The actual elements of each filter are described more fully in the
- following sections.
-
-
- 6\b6.\b.1\b1.\b. S\bSp\bpo\bot\bts\bs
-
- The elements of the Spot filter are ....
-
-
-
- [action, field_no, sort, possible_values, hops]
-
-
-
-
-
- There are 3 elements here to look at. Firstly, the action element.
- This is very simple and only 2 possible states exist, accept (1) or
- drop (0).
-
-
- The second element is the field_no. There are 13 possiblities to
- choose from here ....
-
-
-
-
-
-
-
-
- 0 = frequency
- 1 = call
- 2 = date in unix format
- 3 = comment
- 4 = spotter
- 5 = spotted dxcc country
- 6 = spotter's dxcc country
- 7 = origin
- 8 = spotted itu
- 9 = spotted cq
- 10 = spotter's itu
- 11 = spotter's cq
- 12 = callsign of the channel on which the spot has appeared
-
-
-
-
-
- The third element tells us what to expect in the fourth element.
- There are 4 possibilities ....
-
-
-
- n - numeric list of numbers e.g. [ 1,2,3 ]
- r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
- a - an alphanumeric regex
- d - the default rule
-
-
-
-
-
- The fifth element is simply the hops to set in this filter. This
- would only be used if the filter was for a node of course and
- overrides the hop count in hop_table.pl.
-
-
- So, let's look at an example spot filter. It does not matter in the
- example who the filter is to be used for. So, what do we need in the
- filter? We need to filter the spots the user/node requires and also
- set a default rule for anything else outside the filter. Below is a
- simple filter that stops spots arriving from outside Europe.
-
-
-
- $in = [
- [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
- [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-
-
-
-
-
- So the filter is wrapped in between a pair of square brackets. This
- tells Spider to look in between these limits. Then each line is
- contained within its own square brackets and ends with a comma. Lets
- look carefully at the first line. The first element is 0 (drop).
- Therefore anything we put on this line will not be accepted. The next
- element is 4. This means we are filtering by the spotter. The third
- element is the letter "a" which tells the program to expect an
- alphanumeric expression in the fourth element. The fourth element is
- a list of letters separated by the pipe symbol.
-
-
-
- What this line does is tell the program to drop any spots posted by
- anyone in the USA, Canada or Japan.
-
-
- The second line is the default rule for anything else. The "d" tells
- us this and the line simply reads... accept anything else.
-
-
- You can add as many lines as you need to complete the filter but if
- there are several lines of the same type it is neater to enclose them
- all as one line. An example of this is where specific bands are set.
- We could write this like this ....
-
-
-
- [ 0,0,'r',[1800.0, 2000.0], 1],
- [ 0,0,'r',[10100.0, 10150.0], 1],
- [ 0,0,'r',[14000.0, 14350.0], 1],
- [ 0,0,'r',[18000.0, 18200.0], 1],
-
-
-
-
-
- But the line below achieves the same thing and is more efficient ....
-
-
-
- [ 0, 0, 'r',
- [
- 1800.0, 2000.0, # top band
- 10100.0, 10150.0, # WARC
- 14000.0, 14350.0, # 20m
- 18000.0, 18200.0, # WARC
- [ ,1 ],
-
-
-
-
-
-
- 6\b6.\b.2\b2.\b. A\bAn\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs
-
-
-
-
- # This is an example announce or filter allowing only West EU announces
- #
- # The element list is:-
- # 0 - callsign of announcer
- # 1 - destination * = all, <callsign> = routed to the node
- # 2 - text
- # 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
- # 4 - origin
- # 5 - 0 - announce, 1 - wx
- # 6 - channel callsign (the interface from which this spot came)
-
- $in = [
- [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
- [ 0, 0, 'd', 0 ]
- ];
-
-
-
-
-
- In this example, only the prefixes listed will be allowed. It is
- possible to be quite specific. The Dutch prefix "P" is followed by
- several secondary identifiers which are allowed. So, in the example,
- "PA" or "PE" would be ok but not "PG". It is even possible to allow
- information from a single callsign. In the example this is DK0WCY, to
- allow the posting of his Aurora Beacon.
-
-
- 6\b6.\b.3\b3.\b. W\bWW\bWV\bV
-
-
-
-
- # This is an example WWV filter
- #
- # The element list is:-
- # 0 - nominal unix date of spot (ie the day + hour:13)
- # 1 - the hour
- # 2 - SFI
- # 3 - K
- # 4 - I
- # 5 - text
- # 6 - spotter
- # 7 - origin
- # 8 - incoming interface callsign
-
- # this one doesn't filter, it just sets the hop count to 6 and is
- # used mainly just to override any isolation from WWV coming from
- # the internet.
-
- $in = [
- [ 1, 0, 'd', 0, 6 ]
- ];
-
-
-
-
-
- It should be noted that the filter will start to be used only once a
- user/node has logged out and back in again.
-
- I am not going to spend any more time on these filters now as they
- will become more "comprehensive" in the near future.
-
-
- 7\b7.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(N\bNe\bew\bw S\bSt\bty\byl\ble\be v\bv1\b1.\b.4\b45\b5 a\ban\bnd\bd l\bla\bat\bte\ber\br)\b)
-
- 7\b7.\b.1\b1.\b. G\bGe\ben\bne\ber\bra\bal\bl f\bfi\bil\blt\bte\ber\br r\bru\bul\ble\bes\bs
-
- Upto v1.44 it was not possible for the user to set their own filters.
- From v1.45 though that has all changed. It is now possible to set
- filters for just about anything you wish. If you have just updated
- from an older version of DXSpider you will need to update your new
- filters. You do not need to do anything with your old filters, they
- will be renamed as you update.
-
-
- There are 3 basic commands involved in setting and manipulating
- filters. These are _\ba_\bc_\bc_\be_\bp_\bt, _\br_\be_\bj_\be_\bc_\bt and _\bc_\bl_\be_\ba_\br. First we will look
- generally at filtering. There are a number of things you can filter in
- the DXSpider system. They all use the same general mechanism.
-
-
- In general terms you can create a 'reject' or an 'accept' filter which
- can have up to 10 lines in it. You do this using, for example ...
-
- accept/spots .....
- reject/spots .....
-
-
-
-
- where ..... are the specific commands for that type of filter. There
- are filters for spots, wwv, announce, wcy and (for sysops) connects.
- See each different accept or reject command reference for more
- details.
-
- There is also a command to clear out one or more lines in a filter.
- They are ...
-
-
-
- clear/spots 1
- clear/spots all
-
-
-
-
- There is clear/xxxx command for each type of filter.
-
-
- and you can check that your filters have worked by the command ...
-
-
-
-
- show/filter
-
-
-
-
-
- For now we are going to use spots for the examples, but you can apply
- the same principles to all types of filter.
-
-
- 7\b7.\b.2\b2.\b. T\bTy\byp\bpe\bes\bs o\bof\bf f\bfi\bil\blt\bte\ber\br
-
- There are two main types of filter, _\ba_\bc_\bc_\be_\bp_\bt or _\br_\be_\bj_\be_\bc_\bt. You can use
- either to achieve the result you want dependent on your own preference
- and which is more simple to do. It is pointless writing 8 lines of
- reject filters when 1 accept filter would do the same thing! Each
- filter has 10 lines (of any length) which are tried in order. If a
- line matches then the action you have specified is taken (ie reject
- means ignore it and accept means take it)
-
-
- If you specify reject filters, then any lines that arrive that match
- the filter will be dumped but all else will be accepted. If you use
- an accept filter, then ONLY the lines in the filter will be accepted
- and all else will be dumped. For example if you have a single line
- _\ba_\bc_\bc_\be_\bp_\bt filter ...
-
-
-
- accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
-
- then you will _\bO_\bN_\bL_\bY get VHF spots _\bf_\br_\bo_\bm or _\bt_\bo CQ zones 14, 15 and 16.
-
- If you set a reject filter like this ...
-
-
-
- reject/spots on hf/cw
-
-
-
-
- Then you will get everything _\bE_\bX_\bC_\bE_\bP_\bT HF CW spots. You could make this
- single filter even more flexible. For example, if you are interested
- in IOTA and will work it even on CW even though normally you are not
- interested in CW, then you could say ...
-
-
-
- reject/spots on hf/cw and not info iota
-
-
-
-
- But in that case you might only be interested in iota and say:-
-
-
-
- accept/spots not on hf/cw or info iota
-
-
-
-
- which achieves exactly the same thing. You should choose one or the
- other until you are comfortable with the way it works. You can mix
- them if you wish (actually you can have an accept AND a reject on the
- same line) but don't attempt this until you are sure you know what you
- are doing!
-
-
- You can arrange your filter lines into logical units, either for your
- own understanding or simply convenience. Here is an example ...
-
-
-
- reject/spots 1 on hf/cw
- reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
-
- What this does is to ignore all HF CW spots and also rejects any spots
- on VHF which don't either originate or spot someone in Europe.
-
-
- This is an example where you would use a line number (1 and 2 in this
- case), if you leave the digit out, the system assumes '1'. Digits
- '0'-'9' are available. This make it easier to see just what filters
- you have set. It also makes it more simple to remove individual
- filters, during a contest for example.
-
-
- You will notice in the above example that the second line has
- brackets. Look at the line logically. You can see there are 2
- separate sections to it. We are saying reject spots that are VHF or
- above _\bA_\bP_\bA_\bR_\bT from those in zones 14, 15 and 16 (either spotted there or
- originated there). If you did not have the brackets to separate the 2
- sections, then Spider would read it logically from the front and see a
- different expression entirely ...
- (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-
-
-
-
- The simple way to remember this is, if you use OR - use brackets.
- Whilst we are here CASE is not important. 'And BY_Zone' is just the
- same as 'and by_zone'.
- As mentioned earlier, setting several filters can be more flexible
- than simply setting one complex one. Doing it in this way means that
- if you want to alter your filter you can just redefine or remove one
- or more lines of it or one line. For example ...
+ These commands are simply typed from within the cluster as the sysop
+ user.
+ 3.5. Message status
- reject/spots 1 on hf/ssb
+ You can check on a message from within the cluster by using the
+ command stat/msg. This will give you additional information on the
+ message number including which nodes have received it, which node it
+ was received from and when etc. Here is an example of the output of
+ the command ...
+ G0VGS de GB7MBC 28-Jan-2001 1308Z >
+ stat/msg 6869
+ From: GB7DJK
+ Msg Time: 26-Jan-2001 1302Z
+ Msgno: 6869
+ Origin: GB7DJK
+ Size: 8012
+ Subject: AMSAT 2line KEPS 01025.AMSAT
+ To: UK
+ Got it Nodes: GB7BAA, GB7ADX
+ Private: 0
+ Read Confirm: 0
+ Times read: 0
+ G0VGS de GB7MBC 28-Jan-2001 1308Z >
- would redefine our earlier example, or
+ 3.6. Filtering mail
+ This is described in the section on Other filters so I will not
+ duplicate it here.
- clear/spots 1
+ 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
+ sysops. In /spider/msg there is a directory called distro. You put
+ any distibution lists in here. For example, here is a file called
+ SYSOP.pl that caters for the UK sysops.
- To remove all the filter lines in the spot filter ...
+ qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+ GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
+ GB7DXK GB7DXI GB7DXS)
- clear/spots all
+ Any mail sent to "sysop" would only be sent to the callsigns in this
+ list.
+ 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
+ and pushes any required mail to the cluster. No mail can flow from
+ Spider to the BBS, the interface is one-way.
- 7\b7.\b.3\b3.\b. F\bFi\bil\blt\bte\ber\br o\bop\bpt\bti\bio\bon\bns\bs
- You can filter in several different ways. The options are listed in
- the various helpfiles for accept, reject and filter.
+ Please be careful not to flood the cluster network with unnecessary
+ mail. Make sure you only send mail to the clusters that want it by
+ using the Forward.pl file very carefully.
- 7\b7.\b.4\b4.\b. D\bDe\bef\bfa\bau\bul\blt\bt f\bfi\bil\blt\bte\ber\brs\bs
+ 4. Scripts
- Sometimes all that is needed is a general rule for node connects.
- This can be done with a node_default filter. This rule will always be
- followed, even if the link is isolated, unless another filter is set
- specifically. Default rules can be set for nodes and users. They can
- be set for spots, announces, WWV and WCY. They can also be used for
- hops. An example might look like this ...
+ From 1.48 onwards it will become increasingly possible to control
+ DXSpider's operation with scripts of various kinds.
+ In the first instance, in 1.48, the sysop can create, with their
+ favorite text editor, files in the directory /spider/scripts which
+ contain any legal command for a callsign or class of connection which
+ will be executed at logon.
- accept/spot node_default by_zone 14,15,16,20,33
- set/hops node_default spot 50
+ The filename are the callsign of the connection that you want the
+ script to operate on, eg: /spider/scripts/g1tlh. The filenames are
+ always in lower case on those architectures where this makes a
+ difference.
- This filter is for spots only, you could set others for announce, WWV
- and WCY. This filter would work for ALL nodes unless a specific
- filter is written to override it for a particular node. You can also
- set a user_default should you require. It is important to note that
- default filters should be considered to be "connected". By this I
- mean that should you override the default filter for spots, you need
- to add a rule for the hops for spots also.
+ In addition to the callsign specific scripts there are three others:-
- 7\b7.\b.5\b5.\b. A\bAd\bdv\bva\ban\bnc\bce\bed\bd f\bfi\bil\blt\bte\ber\bri\bin\bng\bg
- Once you are happy with the results you get, you may like to
- experiment.
- The previous example that filters hf/cw spots and accepts vhf/uhf
- spots from EU can be written with a mixed filter, for example ...
+ startup
+ user_default
+ node_default
- 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)
+ The startup script is executed immediately after all initialisation of
+ the node is done, but before any connections are possible.
- 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 _\br_\be_\bj_\be_\bc_\bt _\ba_\bl_\bl _\bH_\bF _\bs_\bp_\bo_\bt_\bs _\bi_\bn _\bt_\bh_\be _\bC_\bW _\bs_\be_\bc_\bt_\bi_\bo_\bn _\bo_\bf _\bt_\bh_\be _\bb_\ba_\bn_\bd_\bs _\bb_\bu_\bt _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bl_\bl
- _\bo_\bt_\bh_\be_\br_\bs _\ba_\bt _\bH_\bF_\b. _\bA_\bl_\bs_\bo _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bn_\by_\bt_\bh_\bi_\bn_\bg _\bi_\bn _\bV_\bH_\bF _\ba_\bn_\bd _\ba_\bb_\bo_\bv_\be _\bs_\bp_\bo_\bt_\bt_\be_\bd _\bi_\bn _\bo_\br _\bb_\by
- _\bo_\bp_\be_\br_\ba_\bt_\bo_\br_\bs _\bi_\bn _\bt_\bh_\be _\bz_\bo_\bn_\be_\bs _\b1_\b4_\b, _\b1_\b5 _\ba_\bn_\bd _\b1_\b6. Each filter slot actually has a
- 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
- the accept slot.
+ The user_default script is executed for every user that does NOT
+ already have a specific script.
- It was mentioned earlier that after a reject test that doesn't match,
- the default for following tests is 'accept', the reverse is true for
- 'accept'. In the example what happens is that the reject is executed
- first, any non hf/cw spot is passed to the accept line, which lets
- through everything else on HF. The next filter line lets through just
- VHF/UHF spots from EU.
+ The node_default script is executed for every node that doesn't have a
+ specific script.
+ There are a couple of examples in the /spider/scripts directory.
- 8\b8.\b. O\bOt\bth\bhe\ber\br f\bfi\bil\blt\bte\ber\brs\bs
- 8\b8.\b.1\b1.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg M\bMa\bai\bil\bl
+ 5. Databases
- In the /spider/msg directory you will find a file called
- badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
- original looks something like this ....
+ Spider allows the creation of local or remote databases. It supports
+ chained databases, allowing several different databases to be scanned
+ with one simple command. Importing of databases is limited at present
+ to the standard AK1A databases such as OBLAST and the DB0SDX QSL
+ database but will expand with time.
+ 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.
+ To create a database you use the command dbcreate. It can be used in
+ 3 different ways like so ..
+ dbcreate <name>
+ To simply create a database locally, you just tell the command the
+ name of the database. This does not create the actual database, it
+ simply defines it to say that it exists.
+ dbcreate <name> chain <name> [<name>...]
- # 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)
+ This creates a chained database entry. The first database will be
+ scanned, then the second, the third etc...
- # 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
+ dbcreate <name> remote <name>
- # 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
+ 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...
- package DXMsg;
- @badmsg = (
- );
+ dbcreate buckmaster remote gb7dxc
+ Remote databases cannot be chained, however, the last database in a
+ chain can be a remote database.
- I think this is fairly self explanatory. It is simply a list of
- subject headers that we do not want to pass on to either the users of
- the cluster or the other cluster nodes that we are linked to. This is
- usually because of rules and regulations pertaining to items for sale
- etc in a particular country.
+ 5.2. Importing databases
- 8\b8.\b.2\b2.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg D\bDX\bX c\bca\bal\bll\blo\bou\but\bts\bs (\b(D\bDe\bep\bpr\bri\bic\bca\bat\bte\bed\bd)\b)
+ The only databases that Spider can currently import are the standard
+ AK1A databases such as OBLAST or the DB0SDX qsl and address database.
+ This will be added to with time.
- _\bF_\br_\bo_\bm _\bv_\be_\br_\bs_\bi_\bo_\bn _\b1_\b._\b4_\b7_\b, _\bt_\bh_\bi_\bs _\bm_\be_\bt_\bh_\bo_\bd _\bi_\bs _\br_\be_\bp_\bl_\ba_\bc_\be_\bd _\bb_\by _\bt_\bh_\be _\bc_\bo_\bm_\bm_\ba_\bn_\bd _\bs_\be_\bt_\b/_\bb_\ba_\bd_\bd_\bx
+ To import such a database, first put the file somewhere useful like
+ /tmp and then issue the following command ...
- 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 ....
+ dbimport oblast /tmp/OBLAST.FUL
+ This will update the existing local oblast database or create it if it
+ does not exist.
+ 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
+ available databases. For example ...
+ dbavail
+ DB Name Location Chain
+ qsl Local
+ buck GB7ADX
+ hftest GB7DXM
+ G0VGS de GB7MBC 3-Feb-2001 1925Z >
+ 5.4. Looking up databases
- # the list of dx spot addresses that we don't store and don't pass on
+ To look for information in a defined database, simply use the dbshow
+ command, for example ...
- package DXProt;
- @baddx = qw
+ dbshow buckmaster G0YLM
+
+
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
- );
+ will show the information for the callsign G0YLM from the buckmaster
+ database if it exists. To make things more standard for the users you
+ can add an entry in the Aliases file so that it looks like a standard
+ show command like this ...
- Again, this is simply a list of names we do not want to see in the
- spotted field of a DX callout.
- 8\b8.\b.3\b3.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg w\bwo\bor\brd\bds\bs f\bfr\bro\bom\bm t\bte\bex\bxt\bt f\bfi\bie\bel\bld\bds\bs i\bin\bn A\bAn\bnn\bno\bou\bun\bnc\bce\be,\b, T\bTa\bal\blk\bk a\ban\bnd\bd D\bDX\bX s\bsp\bpo\bot\bts\bs
+ Now you can simply use show/buckmaster or an abreviation.
- Create a file in /spider/data called _\bb_\ba_\bd_\bw_\bo_\br_\bd_\bs. The format is quite
- simple. Lines beginning with # are ignored so comments can be added.
- An example file is below ...
+ 5.5. Removing databases
+ To delete an existing database you use the dbremove command. For
+ example ...
- # Below is a list of words we do not wish to see on the cluster
- grunge grunged grunging
- splodge splodger splodging
- grince
- fluffle
+ dbremove oblast
- Multiple words can be used on the same line as shown. Obviously these
- are just examples :-)
- You can reload the file from the cluster prompt as sysop with
- load/badwords.
+ 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.
- 9\b9.\b. I\bIn\bnf\bfo\bor\brm\bma\bat\bti\bio\bon\bn,\b, f\bfi\bil\ble\bes\bs a\ban\bnd\bd u\bus\bse\bef\bfu\bul\bl p\bpr\bro\bog\bgr\bra\bam\bms\bs
+ 6. Information, files and useful programs
- 9\b9.\b.1\b1.\b. M\bMO\bOT\bTD\bD
+ 6.1. MOTD
One of the more important things a cluster sysop needs to do is to get
information to his users. The simplest way to do this is to have a
to the cluster.
- 9\b9.\b.2\b2.\b. D\bDo\bow\bwn\bnt\bti\bim\bme\be m\bme\bes\bss\bsa\bag\bge\be
+ 6.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.
- 9\b9.\b.3\b3.\b. O\bOt\bth\bhe\ber\br t\bte\bex\bxt\bt m\bme\bes\bss\bsa\bag\bge\bes\bs
+ 6.3. Other text messages
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
new users. To set this up, make a directory under /spider called
- _\bp_\ba_\bc_\bk_\bc_\bl_\bu_\bs. Under this directory you can create files called _\bn_\be_\bw_\bs or
- _\bn_\be_\bw_\bu_\bs_\be_\br for example. In fact you can create files with any names you
+ packclus. Under this directory you can create files called news or
+ newuser for example. In fact you can create files with any names you
like. These can be listed by the user with the command ....
-
show/files
- If the file they want to read is called _\bn_\be_\bw_\bs. You could also set an
- alias for this in the Alias file to allow them just to type _\bn_\be_\bw_\bs
+ If the file they want to read is called news. You could also set an
+ alias for this in the Alias file to allow them just to type news
You can also store other information in this directory, either
directly or nested under directories. One use for this would be to
store DX bulletins such as the OPDX bulletins. These can be listed
and read by the user. To keep things tidy, make a directory under
- /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. Now copy any OPDX or similar
+ /spider/packclus called bulletin. Now copy any OPDX or similar
bulletins into it. These can be listed by the user in the same way as
- above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletins
+ above using the show/files command with an extension for the bulletin
directory you have just created, like this ....
- show/files bulletins
+ show/files bulletin
sh/files
- bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+ 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 _\bn_\be_\bw_\bs and a directory called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. You can
- also see that dates they were created. In the case of the file _\bn_\be_\bw_\bs,
+ there is a file called news and a directory called bulletin. You can
+ also see that dates they were created. In the case of the file news,
you can also see the time it was last modified, a good clue as to
whether the file has been updated since you last read it. To read the
- file called _\bn_\be_\bw_\bs you would simply issue the command ....
+ file called news you would simply issue the command ....
- To look what is in the bulletins directory you issue the command ....
+ To look what is in the bulletin directory you issue the command ....
+
+
- show/files bulletins
- 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) >
- type bulletins/opdx391
+ type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
The page length will of course depend on what you have it set to!
- 9\b9.\b.4\b4.\b. T\bTh\bhe\be A\bAl\bli\bia\bas\bse\bes\bs f\bfi\bil\ble\be
+ 6.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
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
#!/usr/bin/perl
# provide some standard aliases for commands for terminally
the results once you have set an alias.
- 9\b9.\b.5\b5.\b. F\bFo\bor\brw\bwa\bar\brd\bd.\b.p\bpl\bl
+ 6.5. Console.pl
- DXSpider receives all and any mail sent to it without any alterations
- needed in files. Because personal and bulletin mail are treated
- differently, there is no need for a list of accepted bulletin
- addresses. It is necessary, however, to tell the program which links
- accept which bulletins. For example, it is pointless sending
- bulletins addresses to "UK" to any links other than UK ones. The file
- that does this is called forward.pl and lives in /spider/msg. At
- default, like other spider files it is named forward.pl.issue. Rename
- it to forward.pl and edit the file to match your requirements. The
- format is below ...
+ In later versions of Spider a simple console program is provided for
+ the sysop. This has a type ahead buffer with line editing facilities
+ and colour for spots, announces etc. To use this program, simply use
+ console.pl instead of client.
+ To edit the colours, copy /spider/perl/Console.pl to /spider/local and
+ edit the file with your favourite editor.
- #
- # this is an example message forwarding file for the system
- #
- # The format of each line is as follows
- #
- # type to/from/at pattern action destinations
- # P/B/F T/F/A regex I/F [ call [, call ...] ]
- #
- # type: P - private, B - bulletin (msg), F - file (ak1a bull)
- # to/from/at: T - to field, F - from field, A - home bbs, O - origin
- # pattern: a perl regex on the field requested
- # action: I - ignore, F - forward
- # destinations: a reference to an array containing node callsigns
- #
- # if it is non-private and isn't in here then it won't get forwarded
- #
- # Currently only type B msgs are affected by this code.
- #
- # The list is read from the top down, the first pattern that matches
- # causes the action to be taken.
- #
- # The pattern can be undef or 0 in which case it will always be selected
- # for the action specified
- #
- # If the BBS list is undef or 0 and the action is 'F' (and it matches the
- # pattern) then it will always be forwarded to every node that doesn't have
- # it (I strongly recommend you don't use this unless you REALLY mean it, if
- # you allow a new link with this on EVERY bull will be forwarded immediately
- # on first connection)
- #
- package DXMsg;
+ 6.6. Updating kepler data
- @forward = (
- );
+ Spider has a powerful and flexible show/satellite command. In order
+ for this to be accurate, the kepler data has to be updated regularly.
+ In general, this data is available as an email or via cluster mail.
+ Updating it is simple. First you need to export the mail message as a
+ file. You do this with the export command from the cluster prompt as
+ the sysop. For example ...
+ export 5467 /spider/perl/keps.in
- 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
+ would export message number 5467 as a file called keps.in in the
+ /spider/perl directory.
- 9\b9.\b.6\b6.\b. D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn l\bli\bis\bst\bts\bs
+ 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 ...
- Distribution lists are simply a list of users to send certain types of
- mail to. An example of this is mail you only wish to send to other
- sysops. In /spider/msg there is a directory called _\bd_\bi_\bs_\bt_\br_\bo. You put
- any distibution lists in here. For example, here is a file called
- SYSOP.pl that caters for the UK sysops.
+ ./convkeps.pl keps.in
- qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
+ Now go back to the cluster and issue the command ...
- Any mail sent to "sysop" would only be sent to the callsigns in this
- list.
- 9\b9.\b.7\b7.\b. C\bCo\bon\bns\bso\bol\ble\be.\b.p\bpl\bl
+ load/keps
- In later versions of Spider a simple console program is provided for
- the sysop. This has a type ahead buffer with line editing facilities
- and colour for spots, announces etc. To use this program, simply use
- console.pl instead of client.pl.
- To edit the colours, copy /spider/perl/Console.pl to /spider/local and
- edit the file with your favourite editor.
+ That is it! the kepler data has been updated.
- 9\b9.\b.8\b8.\b. B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be
- Spider provides a simple BBS interface. No input is required from the
- sysop of the cluster at all. The BBS simply sets the cluster as a BBS
- and pushes any required mail to the cluster. No mail can flow from
- Spider to the BBS, the interface is one-way.
- Please be careful not to flood the cluster network with unnecessary
- mail. Make sure you only send mail to the clusters that want it by
- using the Forward.pl file very carefully.
+ 6.7. The QRZ callbook
+ The command sh/qrz will only work once you have followed a few simple
+ steps. First you need to get a user ID and password from qrz.com.
+ Simply go to the site and create one. Secondly you need to copy the
+ file /spider/perl/Internet.pm to /spider/local and alter it to match
+ your user ID and password. You also at this point need to set
+ $allow=1 to complete the setup. Many thanks to Fred Lloyd, the
+ proprieter of qrz.com for allowing this access.
- 1\b10\b0.\b. C\bCV\bVS\bS
+
+ 7. 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
steps which are listed below ...
- First login as the user _\bs_\by_\bs_\bo_\bp. Next you need to connect to the CVS
+ First login as the user sysop. Next you need to connect to the CVS
repository. You do this with the command below ...
What happens next depends on whether you have an existing installation
that you want to update with the latest and greatest or whether you
just want to see what is there and/or run it on a new machine for
- testing. Either way you will want to change directory to a new place,
- if you want to update an existing installation then I suggest /tmp,
- otherwise choose a suitable place according to the normal installation
- instructions.
+ testing.
+
+ If you are installing Spider from CVS then change directory to
+ /home/sysop
+
+ If you are wanting to update Spider then cd to /tmp
+
The next step will create a brand new 'spider' directory in your
-
-
- tar cvfz /tmp/s.tgz spider
- cd /
- tar xvfzp /tmp/s.tgz
+ tar cvfz /tmp/s.tgz spider
+ cd /
+ tar xvfzp /tmp/s.tgz
Remember to recompile the C client (cd /spider/src; make)
- At this point the files have been upgraded. You can (usually) restrt
+ 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
Now the magic part! From now on when you want to update, simply
- connect to the Internet and then, as the user _\bs_\by_\bs_\bo_\bp ...
+ connect to the Internet and then, as the user sysop ...
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.
- 1\b11\b1.\b. T\bTh\bhe\be D\bDX\bXS\bSp\bpi\bid\bde\ber\br c\bco\bom\bmm\bma\ban\bnd\bd s\bse\bet\bt
+ 8. 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.
- 1\b11\b1.\b.1\b1.\b. a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)
+ 8.1. accept/announce (0)
- a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set an accept filter line for announce
+ accept/announce [0-9] <pattern> Set an accept filter line for announce
Create an 'accept this announce' line for a filter.
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:-
- acc/ann dest 6MUK
- acc/ann 2 by_zone 14,15,16
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+
+
+
+
+ or
+
+
+
+ acc/ann by G,M,2
+
+
+
+
+ This filter would only allow announces that were posted buy UK
+ stations. You can use the tag 'all' to accept everything eg:
+ acc/ann all
+
+
+
+
+ but this probably for advanced users...
+
+
+ 8.2. accept/announce (extended for sysops) (8)
+
+ accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
+ version
+
+
+ This version allows a sysop to set a filter for a callsign as well as
+ the default for nodes and users eg:-
+
+
+ accept/ann by G,M,2
+ accept/ann input node_default by G,M,2
+ accept/ann user_default by G,M,2
- or
+ 8.3. accept/route (8)
- acc/ann by G,M,2
+ accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
+ routing
+ Create an 'accept this routing PC Protocol' line for a filter.
- This filter would only allow announces that were posted buy UK
- stations. You can use the tag 'all' to accept everything eg:
+ 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:-
- acc/ann all
+ 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>
- but this probably for advanced users...
- 1\b11\b1.\b.2\b2.\b. a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
- a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<c
\bca
\bal
\bll
\bl>
\b> [
\b[i
\bin
\bnp
\bpu
\but
\bt]
\b] [
\b[0
\b0-
\b-9
\b9]
\b]<
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Announce filter sysop
- version
+ some examples:-
- This version allows a sysop to set a filter for a callsign as well as
- the default for nodes and users eg:-
+ 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:
- accept/ann by G,M,2
- accept/ann input node_default by G,M,2
- accept/ann user_default by G,M,2
+ acc/route all
- 1\b11\b1.\b.3\b3.\b. a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)
+ 8.4. accept/spots (0)
- a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set an accept filter line for spots
+ accept/announce [0-9] <pattern> Set an accept filter line for spots
Create an 'accept this spot' line for a filter.
acc/spot 3 all
-
-
but this probably for advanced users...
- 1\b11\b1.\b.4\b4.\b. a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.5. accept/spots (extended for sysops) (8)
- a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Spot filter sysop version
+ accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
This version allows a sysop to set a filter for a callsign as well as
- 1\b11\b1.\b.5\b5.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 8.6. accept/wcy (0)
- a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> set an accept WCY filter
+ accept/wcy [0-9] <pattern> set an accept WCY filter
It is unlikely that you will want to do this, but if you do then you
See HELP FILTER for information.
- 1\b11\b1.\b.6\b6.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.7. accept/wcy (extended for sysops) (8)
- a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WCY filter sysop version
+ accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as
- 1\b11\b1.\b.7\b7.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 8.8. accept/wwv (0)
- a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set an accept WWV filter
+ accept/wwv [0-9] <pattern> Set an accept WWV filter
It is unlikely that you will want to do this, but if you do then you
See HELP FILTER for information.
- 1\b11\b1.\b.8\b8.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.9. accept/wwv (extended for sysops) (8)
- a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WWV filter sysop version
+ accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as
- 1\b11\b1.\b.9\b9.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)
+ 8.10. announce (0)
- a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<t\bte\bex\bxt\bt>\b> Send an announcement to local users
+ announce <text> Send an announcement to local users
Send an announcement to LOCAL users only, where <text> is the text of
- the announcement you wish to broadcast
+ 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.
- 1\b11\b1.\b.1\b10\b0.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl (\b(0\b0)\b)
+ 8.11. announce full (0)
- a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send an announcement cluster wide
+ announce full <text> Send an announcement cluster wide
This command will send your announcement across the whole cluster
- 1\b11\b1.\b.1\b11\b1.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp (\b(5\b5)\b)
+ 8.12. announce sysop (5)
- a\ban\bnn\bno\bou\bun\bnc\bce\be s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b>
+ announce sysop <text>
Send an announcement to Sysops only
- 1\b11\b1.\b.1\b12\b2.\b. a\bap\bpr\bro\bop\bpo\bos\bs (\b(0\b0)\b)
+ 8.13. apropos (0)
- a\bap\bpr\bro\bop\bpo\bos\bs <\b<s\bst\btr\bri\bin\bng\bg>\b> Search the help database
+ apropos <string> Search the help database
Search the help database for <string> (it isn't case sensitive), and
print the names of all the commands that may be relevant.
- 1\b11\b1.\b.1\b13\b3.\b. b\bby\bye\be (\b(0\b0)\b)
+ 8.14. bye (0)
- b\bby\bye\be Exit from the cluster
+ bye Exit from the cluster
This will disconnect you from the cluster
- 1\b11\b1.\b.1\b14\b4.\b. c\bca\bat\btc\bch\bhu\bup\bp (\b(5\b5)\b)
+ 8.15. catchup (5)
- c\bca\bat\btc\bch\bhu\bup\bp <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> A\bAl\bll\bl|\b|[\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b..\b.]\b] Mark a message as sent
+ catchup <node_call> All|[<msgno> ...] Mark a message as sent
When you send messages the fact that you have forwarded it to another
and to undo what you have just done:-
+
+
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
Order is not important.
- 1\b11\b1.\b.1\b15\b5.\b. c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)
+ 8.16. clear/spots (0)
- c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a spot filter line
+ clear/spots [1|all] Clear a spot filter line
This command allows you to clear (remove) a line in a spot filter or
- 1\b11\b1.\b.1\b16\b6.\b. c\bco\bon\bnn\bne\bec\bct\bt (\b(5\b5)\b)
- c\bco\bon\bnn\bne\bec\bct\bt <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Start a connection to another DX Cluster
+ 8.17. connect (5)
+
+ connect <callsign> Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to
cluster <callsign>.
- 1\b11\b1.\b.1\b17\b7.\b. d\bdb\bba\bav\bva\bai\bil\bl (\b(0\b0)\b)
+ 8.18. dbavail (0)
- d\bdb\bba\bav\bva\bai\bil\bl Show a list of all the databases in the system
+ dbavail Show a list of all the databases in the system
The title says it all really, this command lists all the databases
defined in the system. It is also aliased to SHOW/COMMAND.
- 1\b11\b1.\b.1\b18\b8.\b. d\bdb\bbc\bcr\bre\bea\bat\bte\be (\b(9\b9)\b)
+ 8.19. dbcreate (9)
- d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> Create a database entry
- d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> c\bch\bha\bai\bin\bn <\b<n\bna\bam\bme\be>\b> [\b[<\b<n\bna\bam\bme\be>\b>.\b..\b.]\b] Create a chained database
+ dbcreate <name> Create a database entry
+ dbcreate <name> chain <name> [<name>..] Create a chained database
entry
- d\bdb\bbc\bcr\bre\bea\bat\bte\be <\b<n\bna\bam\bme\be>\b> r\bre\bem\bmo\bot\bte\be <\b<n\bno\bod\bde\be>\b> Create a remote database entry
+ dbcreate <name> remote <node> Create a remote database entry
DBCREATE allows you to define a database in the system. It doesn't
It would be normal for you to add an entry into your local Aliases
file to allow people to use the 'SHOW/<dbname>' style syntax. So you
would need to add a line like:-
-
-
-
-
-
- 's' => [
- ..
- ..
- '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
- ..
- ..
- ],
+ 's' => [
+ ..
+ ..
+ '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+ ..
+ ..
+ ],
databases. See DBSHOW for generic database enquiry
- 1\b11\b1.\b.1\b19\b9.\b. d\bdb\bbi\bim\bmp\bpo\bor\brt\bt (\b(9\b9)\b)
+ 8.20. dbimport (9)
- d\bdb\bbi\bim\bmp\bpo\bor\brt\bt <\b<d\bdb\bbn\bna\bam\bme\be>\b> Import AK1A data into a database
+ dbimport <dbname> Import AK1A data into a database
If you want to import or update data in bulk to a database you can use
oblast database held locally.
- 1\b11\b1.\b.2\b20\b0.\b. d\bdb\bbr\bre\bem\bmo\bov\bve\be (\b(9\b9)\b)
+ 8.21. dbremove (9)
- d\bdb\bbr\bre\bem\bmo\bov\bve\be <\b<d\bdb\bbn\bna\bam\bme\be>\b> Delete a database
+ dbremove <dbname> Delete a database
DBREMOVE will completely remove a database entry and also delete any
You have been warned.
- 1\b11\b1.\b.2\b21\b1.\b. d\bdb\bbs\bsh\bho\bow\bw (\b(0\b0)\b)
+ 8.22. dbshow (0)
- d\bdb\bbs\bsh\bho\bow\bw <\b<d\bdb\bbn\bna\bam\bme\be>\b> <\b<k\bke\bey\by>\b> Display an entry, if it exists, in a database
+ dbshow <dbname> <key> Display an entry, if it exists, in a database
- 1\b11\b1.\b.2\b22\b2.\b. d\bde\beb\bbu\bug\bg (\b(9\b9)\b)
+ 8.23. debug (9)
- d\bde\beb\bbu\bug\bg Set the cluster program into debug mode
+ debug Set the cluster program into debug mode
Executing this command will only have an effect if you are running the
finished.
- 1\b11\b1.\b.2\b23\b3.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by (\b(0\b0)\b)
+ 8.24. directory (0)
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by List messages
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by o\bow\bwn\bn List your own messages
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by n\bne\bew\bw List all new messages
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by t\bto\bo <\b<c\bca\bal\bll\bl>\b> List all messages to <call>
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b> List all messages from <call>
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by s\bsu\bub\bbj\bje\bec\bct\bt <\b<s\bst\btr\bri\bin\bng\bg>\b> List all messages with <string> in subject
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<n\bnn\bn>\b> List last <nn> messages
- d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<f\bfr\bro\bom\bm>\b>-\b-<\b<t\bto\bo>\b> List messages <from> message <to> message
+ directory List messages
+ directory own List your own messages
+ directory new List all new messages
+ directory to <call> List all messages to <call>
+ directory from <call> List all messages from <call>
+ directory subject <string> List all messages with <string> in subject
+ directory <nn> List last <nn> messages
+ directory <from>-<to> List messages <from> message <to> message
List the messages in the messages directory.
- 1\b11\b1.\b.2\b24\b4.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 8.25. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 1\b11\b1.\b.2\b25\b5.\b. d\bdi\bis\bsc\bco\bon\bnn\bne\bec\bct\bt (\b(8\b8)\b)
+ 8.26. disconnect (8)
- d\bdi\bis\bsc\bco\bon\bnn\bne\bec\bct\bt <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Disconnect a user or node
+ disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 1\b11\b1.\b.2\b26\b6.\b. d\bdx\bx (\b(0\b0)\b)
+ 8.27. dx (0)
- d\bdx\bx [\b[b\bby\by <\b<c\bca\bal\bll\bl>\b>]\b] <\b<f\bfr\bre\beq\bq>\b> <\b<c\bca\bal\bll\bl>\b> <\b<r\bre\bem\bma\bar\brk\bks\bs>\b> Send a DX spot
+ dx [by <call>] <freq> <call> <remarks> Send a DX spot
This is how you send a DX Spot to other users. You can, in fact, now
cluster. See SHOW/BANDS for more information.
- 1\b11\b1.\b.2\b27\b7.\b. e\bex\bxp\bpo\bor\brt\bt (\b(9\b9)\b)
+ 8.28. export (9)
- e\bex\bxp\bpo\bor\brt\bt <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<f\bfi\bil\ble\ben\bna\bam\bme\be>\b> Export a message to a file
+ export <msgno> <filename> Export a message to a file
Export a message to a file. This command can only be executed on a
EXPORT 2345 /tmp/a
- 1\b11\b1.\b.2\b28\b8.\b. e\bex\bxp\bpo\bor\brt\bt_\b_u\bus\bse\ber\brs\bs (\b(9\b9)\b)
+ 8.29. export_users (9)
- e\bex\bxp\bpo\bor\brt\bt_\b_u\bus\bse\ber\brs\bs [\b[<\b<f\bfi\bil\ble\ben\bna\bam\bme\be>\b>]\b] Export the users database to ascii
+ export_users [<filename>] Export the users database to ascii
Export the users database to a file in ascii format. If no filename is
check is made on the filename (if any) that you specify.
- 1\b11\b1.\b.2\b29\b9.\b. f\bfo\bor\brw\bwa\bar\brd\bd/\b/l\bla\bat\btl\blo\bon\bng\bg (\b(8\b8)\b)
+ 8.30. forward/latlong (8)
- f\bfo\bor\brw\bwa\bar\brd\bd/\b/l\bla\bat\btl\blo\bon\bng\bg <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Send latitude and longitude information to
+ forward/latlong <node_call> Send latitude and longitude information to
another cluster
your cluster is holding against callsigns. One advantage of recieving
this information is that more locator information is held by you.
This means that more locators are given on the DX line assuming you
- have _\bs_\be_\bt_\b/_\bd_\bx_\bg_\br_\bi_\bd enabled. This could be a LOT of information though,
+ have set/dxgrid enabled. This could be a LOT of information though,
so it is not recommended on slow links.
- 1\b11\b1.\b.3\b30\b0.\b. f\bfo\bor\brw\bwa\bar\brd\bd/\b/o\bop\bpe\ber\brn\bna\bam\bme\be (\b(1\b1)\b)
+ 8.31. forward/opername (1)
- f\bfo\bor\brw\bwa\bar\brd\bd/\b/o\bop\bpe\ber\brn\bna\bam\bme\be <\b<c\bca\bal\bll\bl>\b> Send out information on this <call> to all
+ forward/opername <call> Send out information on this <call> to all
clusters
available.
- 1\b11\b1.\b.3\b31\b1.\b. h\bhe\bel\blp\bp (\b(0\b0)\b)
+ 8.32. help (0)
- h\bhe\bel\blp\bp <\b<c\bcm\bmd\bd>\b> Get help on a command
+ help <cmd> Get help on a command
All commands can be abbreviated, so SHOW/DX can be abbreviated to
commands to look at with HELP.
- 1\b11\b1.\b.3\b32\b2.\b. i\bin\bni\bit\bt (\b(5\b5)\b)
+ 8.33. init (5)
- i\bin\bni\bit\bt <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Re-initialise a link to an AK1A compatible node
+ init <node call> Re-initialise a link to an AK1A compatible node
This command attempts to re-initialise a link to a (usually) AK1A node
Best of luck - you will need it.
- 1\b11\b1.\b.3\b33\b3.\b. k\bki\bil\bll\bl (\b(0\b0)\b)
+ 8.34. kill (0)
- k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b.]\b] Delete a message from the local system
+ kill <msgno> [<msgno> ..] Delete a message from the local system
Delete a message from the local system. You will only be able to
the sysop).
- 1\b11\b1.\b.3\b34\b4.\b. k\bki\bil\bll\bl (\b(5\b5)\b)
+ 8.35. kill (5)
- k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b..\b.]\b] Remove or erase a message from the system
- k\bki\bil\bll\bl f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b> Remove all messages from a callsign
- k\bki\bil\bll\bl t\bto\bo <\b<c\bca\bal\bll\bl>\b> Remove all messages to a callsign
+ kill <msgno> [<msgno> ...] Remove or erase a message from the system
+ kill from <call> Remove all messages from a callsign
+ kill to <call> Remove all messages to a callsign
You can get rid of any message to or originating from your callsign
As a sysop you can kill any message on the system.
- 1\b11\b1.\b.3\b35\b5.\b. k\bki\bil\bll\bl f\bfu\bul\bll\bl (\b(5\b5)\b)
+ 8.36. kill full (5)
- k\bki\bil\bll\bl f\bfu\bul\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b>]\b] Delete a message from the whole cluster
+ kill full <msgno> [<msgno>] Delete a message from the whole cluster
Delete a message (usually a 'bulletin') from the whole cluster system.
- 1\b11\b1.\b.3\b36\b6.\b. l\bli\bin\bnk\bks\bs (\b(0\b0)\b)
+ 8.37. links (0)
- l\bli\bin\bnk\bks\bs Show which nodes are physically connected
+ links Show which nodes are physically connected
This is a quick listing that shows which links are connected and some
- 1\b11\b1.\b.3\b37\b7.\b. l\blo\boa\bad\bd/\b/a\bal\bli\bia\bas\bse\bes\bs (\b(9\b9)\b)
+ 8.38. load/aliases (9)
- l\blo\boa\bad\bd/\b/a\bal\bli\bia\bas\bse\bes\bs Reload the command alias table
+ load/aliases Reload the command alias table
Reload the /spider/cmd/Aliases file after you have editted it. You
running in order for the changes to take effect.
+ 8.39. load/badmsg (9)
- 1\b11\b1.\b.3\b38\b8.\b. l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx (\b(9\b9)\b)
-
- l\blo\boa\bad\bd/\b/b\bba\bad\bdd\bdx\bx 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.
-
-
- 1\b11\b1.\b.3\b39\b9.\b. l\blo\boa\bad\bd/\b/b\bba\bad\bdm\bms\bsg\bg (\b(9\b9)\b)
-
- l\blo\boa\bad\bd/\b/b\bba\bad\bdm\bms\bsg\bg Reload the bad message table
+ load/badmsg Reload the bad message table
Reload the /spider/msg/badmsg.pl file if you have changed it manually
deleted on receipt.
- 1\b11\b1.\b.4\b40\b0.\b. l\blo\boa\bad\bd/\b/b\bba\bad\bdw\bwo\bor\brd\bds\bs (\b(9\b9)\b)
-
- l\blo\boa\bad\bd/\b/b\bba\bad\bdw\bwo\bor\brd\bds\bs Reload the badwords file
-
-
- Reload the /spider/data/badwords file if you have changed it manually
- whilst the cluster is running. This file contains a list of words
- which, if found on certain text portions of PC protocol, will cause
- those protocol frames to be rejected. It will all put out a message if
- any of these words are used on the announce, dx and talk commands. The
- words can be one or more on a line, lines starting with '#' are
- ignored.
+ 8.40. load/bands (9)
-
- 1\b11\b1.\b.4\b41\b1.\b. l\blo\boa\bad\bd/\b/b\bba\ban\bnd\bds\bs (\b(9\b9)\b)
-
- l\blo\boa\bad\bd/\b/b\bba\ban\bnd\bds\bs Reload the band limits table
+ load/bands Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually
whilst the cluster is running.
- 1\b11\b1.\b.4\b42\b2.\b. l\blo\boa\bad\bd/\b/c\bcm\bmd\bd_\b_c\bca\bac\bch\bhe\be (\b(9\b9)\b)
+ 8.41. load/cmd_cache (9)
- l\blo\boa\bad\bd/\b/c\bcm\bmd\bd_\b_c\bca\bac\bch\bhe\be Reload the automatic command cache
+ load/cmd_cache Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree it
was just after a cluster restart.
- 1\b11\b1.\b.4\b43\b3.\b. l\blo\boa\bad\bd/\b/f\bfo\bor\brw\bwa\bar\brd\bd (\b(9\b9)\b)
+ 8.42. load/forward (9)
- l\blo\boa\bad\bd/\b/f\bfo\bor\brw\bwa\bar\brd\bd Reload the msg forwarding routing table
+ load/forward Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it manually
whilst the cluster is running.
- 1\b11\b1.\b.4\b44\b4.\b. l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs (\b(9\b9)\b)
-
- l\blo\boa\bad\bd/\b/m\bme\bes\bss\bsa\bag\bge\bes\bs Reload the system messages file
+ 8.43. load/messages (9)
+ load/messages Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst
fiddling/writing ne commands) you can have them take effect during a
unknown message 'xxxx' in lang 'en'
- 1\b11\b1.\b.4\b45\b5.\b. l\blo\boa\bad\bd/\b/p\bpr\bre\bef\bfi\bix\bxe\bes\bs (\b(9\b9)\b)
+ 8.44. load/prefixes (9)
- l\blo\boa\bad\bd/\b/p\bpr\bre\bef\bfi\bix\bxe\bes\bs Reload the prefix table
+ load/prefixes Reload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed it
manually whilst the cluster is running.
- 1\b11\b1.\b.4\b46\b6.\b. m\bme\ber\brg\bge\be (\b(5\b5)\b)
+ 8.45. merge (5)
- m\bme\ber\brg\bge\be <\b<n\bno\bod\bde\be>\b> [\b[<\b<n\bno\bo s\bsp\bpo\bot\bts\bs>\b>/\b/<\b<n\bno\bo w\bww\bwv\bv>\b>]\b] Ask for the latest spots and WWV
+ merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By
data).
- 1\b11\b1.\b.4\b47\b7.\b. m\bms\bsg\bg (\b(9\b9)\b)
+ 8.46. msg (9)
- m\bms\bsg\bg <\b<c\bcm\bmd\bd>\b> <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[d\bda\bat\bta\ba .\b..\b..\b.]\b] Alter various message parameters
+ 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
STAT/MSG <msgno>
+
This will display more information on the message than DIR does.
- 1\b11\b1.\b.4\b48\b8.\b. p\bpc\bc (\b(8\b8)\b)
+ 8.47. pc (8)
- p\bpc\bc <\b<c\bca\bal\bll\bl>\b> <\b<t\bte\bex\bxt\bt>\b> Send text (eg PC Protocol) to <call>
+ pc <call> <text> Send text (eg PC Protocol) to <call>
Send some arbitrary text to a locally connected callsign. No
pc G1TLH Try doing that properly!!!
- 1\b11\b1.\b.4\b49\b9.\b. p\bpi\bin\bng\bg (\b(1\b1)\b)
+ 8.48. ping (1)
- p\bpi\bin\bng\bg <\b<n\bno\bod\bde\be>\b> Check the link quality between nodes
+ ping <node> Check the link quality between nodes
his command allows you to send a frame to another cluster node on the
- 1\b11\b1.\b.5\b50\b0.\b. r\brc\bcm\bmd\bd (\b(1\b1)\b)
+ 8.49. rcmd (1)
- r\brc\bcm\bmd\bd <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> <\b<c\bcm\bmd\bd>\b> Send a command to another DX cluster
+ rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
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.
- 1\b11\b1.\b.5\b51\b1.\b. r\bre\bea\bad\bd (\b(0\b0)\b)
+ 8.50. read (0)
- r\bre\bea\bad\bd Read the next unread personal message addressed to you
- r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read the specified message
+ read Read the next unread personal message addressed to you
+ read <msgno> Read the specified message
You can read any messages that are sent as 'non-personal' and also any
- 1\b11\b1.\b.5\b52\b2.\b. r\bre\bea\bad\bd (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 8.51. read (extended for sysops) (5)
+
+ read <msgno> Read a message on the system
- r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read a message on the system
As a sysop you may read any message on the system
- 1\b11\b1.\b.5\b53\b3.\b. r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be
+ 8.52. reject/announce
- r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject filter for announce
+ reject/announce [0-9] <pattern> Set a reject filter for announce
Create an 'reject this announce' line for a filter.
but this probably for advanced users...
- 1\b11\b1.\b.5\b54\b4.\b. r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.53. reject/announce (extended for sysops) (8)
- r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Announce filter sysop
+ reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
the default for nodes and users eg:-
-
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2
- 1\b11\b1.\b.5\b55\b5.\b. r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs (\b(0\b0)\b)
+ 8.54. 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)
+
+
- r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject filter line for spots
+
+
+ 8.55. reject/spots (0)
+
+ reject/spots [0-9] <pattern> Set a reject filter line for spots
Create a 'reject this spot' line for a filter.
+
A reject filter line means that if the spot matches this filter it is
dumped (not passed on). See HELP FILTERS for more info. Please read
this to understand how filters work - it will save a lot of grief
but this probably for advanced users...
- 1\b11\b1.\b.5\b56\b6.\b. r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.56. reject/spots (extended for sysops) (8)
- r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Reject spot filter sysop
+ 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 user_default by G,M,2
+ 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
- 1\b11\b1.\b.5\b57\b7.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 8.57. reject/wcy (0)
- r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject WCY filter
+ reject/wcy [0-9] <pattern> Set a reject WCY filter
It is unlikely that you will want to do this, but if you do then you
-
-
-
-
-
-
-
-
-
- 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.
- 1\b11\b1.\b.5\b58\b8.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.58. reject/wcy (extended for sysops) (8)
- r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WCY reject filter sysop
+ reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 1\b11\b1.\b.5\b59\b9.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 8.59. reject/wwv (0)
- r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> Set a reject WWV filter
+ reject/wwv [0-9] <pattern> Set a reject WWV filter
It is unlikely that you will want to do this, but if you do then you
- 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.
- 1\b11\b1.\b.6\b60\b0.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(8\b8)\b)
+ 8.60. reject/wwv (extended for sysops) (8)
- r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv <\b<c\bca\bal\bll\bl>\b> [\b[i\bin\bnp\bpu\but\bt]\b] [\b[0\b0-\b-9\b9]\b] <\b<p\bpa\bat\btt\bte\ber\brn\bn>\b> WWV reject filter sysop
+ reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
- 1\b11\b1.\b.6\b61\b1.\b. r\bre\bep\bpl\bly\by (\b(0\b0)\b)
+ 8.61. reply (0)
- r\bre\bep\bpl\bly\by Reply (privately) to the last message that you have read
- r\bre\bep\bpl\bly\by <\b<m\bms\bsg\bgn\bno\bo>\b> Reply (privately) to the specified message
- r\bre\bep\bpl\bly\by B\bB <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
- r\bre\bep\bpl\bly\by N\bNO\bOP\bPr\bri\biv\bva\bat\bte\be <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
- r\bre\bep\bpl\bly\by R\bRR\bR <\b<m\bms\bsg\bgn\bno\bo>\b> Reply to the specified message with read receipt
+ reply Reply (privately) to the last message that you have read
+ reply <msgno> Reply (privately) to the specified message
+ reply B <msgno> Reply as a Bulletin to the specified message
+ reply NOPrivate <msgno> Reply as a Bulletin to the specified message
+ reply RR <msgno> Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have
further details)
- 1\b11\b1.\b.6\b62\b2.\b. s\bse\ben\bnd\bd (\b(0\b0)\b)
- s\bse\ben\bnd\bd <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Send a message to one or more callsigns
- s\bse\ben\bnd\bd R\bRR\bR <\b<c\bca\bal\bll\bl>\b> Send a message and ask for a read receipt
- s\bse\ben\bnd\bd C\bCO\bOP\bPY\bY <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<c\bca\bal\bll\bl>\b> Send a copy of a message to someone
- s\bse\ben\bnd\bd P\bPR\bRI\bIV\bVA\bAT\bTE\bE <\b<c\bca\bal\bll\bl>\b> Send a personal message
- s\bse\ben\bnd\bd N\bNO\bOP\bPR\bRI\bIV\bVA\bAT\bTE\bE <\b<c\bca\bal\bll\bl>\b> Send a message to all stations
+ 8.62. send (0)
+
+ send <call> [<call> ...] Send a message to one or more callsigns
+ send RR <call> Send a message and ask for a read receipt
+ send COPY <msgno> <call> Send a copy of a message to someone
+ send PRIVATE <call> Send a personal message
+ send NOPRIVATE <call> Send a message to all stations
All the SEND commands will create a message which will be sent either
-
- SEND RR COPY 123 PRIVATE G1TLH G0RDI
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
is an alias for SEND PRIVATE
- 1\b11\b1.\b.6\b63\b3.\b. s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs (\b(0\b0)\b)
+ 8.63. set/address (0)
- s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs <\b<y\byo\bou\bur\br_\b_a\bad\bdd\bdr\bre\bes\bss\bs>\b> Record your postal address
+ set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 1\b11\b1.\b.6\b64\b4.\b. s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be (\b(0\b0)\b)
+ 8.64. set/announce (0)
- s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be Allow announce messages
+ set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
- 1\b11\b1.\b.6\b65\b5.\b. s\bse\bet\bt/\b/a\bar\brc\bcl\blu\bus\bst\bte\ber\br (\b(5\b5)\b)
+ 8.65. set/arcluster (5)
- s\bse\bet\bt/\b/a\bar\brc\bcl\blu\bus\bst\bte\ber\br <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the node_call an AR-
+ set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 1\b11\b1.\b.6\b66\b6.\b. s\bse\bet\bt/\b/b\bba\bad\bdd\bdx\bx (\b(8\b8)\b)
+ 8.66. set/baddx (8)
- s\bse\bet\bt/\b/b\bba\bad\bdd\bdx\bx <\b<c\bca\bal\bll\bl>\b> Stop words we do not wish to see in the callsign
+ set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
+
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.
- 1\b11\b1.\b.6\b67\b7.\b. s\bse\bet\bt/\b/b\bba\bad\bdn\bno\bod\bde\be (\b(6\b6)\b)
+ 8.67. set/badnode (6)
- s\bse\bet\bt/\b/b\bba\bad\bdn\bno\bod\bde\be <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Stop spots from this node_call being
+ set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 1\b11\b1.\b.6\b68\b8.\b. s\bse\bet\bt/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br (\b(8\b8)\b)
+ 8.68. set/badspotter (8)
- s\bse\bet\bt/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br <\b<c\bca\bal\bll\bl>\b> Stop spots from this callsign being propagated
+ set/badspotter <call> Stop spots from this callsign being propagated
Setting a callsign as a 'badspotter' will prevent spots from this
Use with extreme care. This command may well be superceded by
FILTERing.
- 1\b11\b1.\b.6\b69\b9.\b. s\bse\bet\bt/\b/b\bbe\bee\bep\bp (\b(0\b0)\b)
- s\bse\bet\bt/\b/b\bbe\bee\bep\bp Add beeps to terminal messages
+
+ 8.69. set/beep (0)
+
+ set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 1\b11\b1.\b.7\b70\b0.\b. s\bse\bet\bt/\b/c\bcl\blx\bx (\b(5\b5)\b)
+ 8.70. set/bbs (5)
+
+ set/bbs <call> [<call>..]Make <call> a BBS
- s\bse\bet\bt/\b/c\bcl\blx\bx <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the node_call a CLX type
+
+ 8.71. set/clx (5)
+
+ set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
node
Set the node_call as a CLX type node
- 1\b11\b1.\b.7\b71\b1.\b. s\bse\bet\bt/\b/d\bde\beb\bbu\bug\bg (\b(9\b9)\b)
+ 8.72. set/debug (9)
+
+ set/debug <name> Add a debug level to the debug set
+
- s\bse\bet\bt/\b/d\bde\beb\bbu\bug\bg <\b<n\bna\bam\bme\be>\b> 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 this level with unset/debug <name>
+ You can show what levels you are logging with the show/debug command.
+ You can remove a debug level with unset/debug <name>
- 1\b11\b1.\b.7\b72\b2.\b. s\bse\bet\bt/\b/d\bdx\bx (\b(0\b0)\b)
- s\bse\bet\bt/\b/d\bdx\bxAllow DX messages to arrive at your terminal
+ 8.73. set/dx (0)
+ set/dxAllow DX messages to arrive at your terminal
- You can stop DX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx command
+ You can stop DX messages with the unset/dx command
- 1\b11\b1.\b.7\b73\b3.\b. s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd (\b(0\b0)\b)
- s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bdAllow grid squares on the end of DX messages
+ 8.74. set/dxgrid (0)
+
+ set/dxgridAllow grid squares on the end of DX messages
Some logging programs do not like the additional information at the
- end of a DX spot. If this is the case, use the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx_\bg_\br_\bi_\bd command
+ end of a DX spot. If this is the case, use the unset/dxgrid command
to remove the grid squares.
- 1\b11\b1.\b.7\b74\b4.\b. s\bse\bet\bt/\b/d\bdx\bxn\bne\bet\bt (\b(5\b5)\b)
+ 8.75. set/dxnet (5)
- s\bse\bet\bt/\b/d\bdx\bxn\bne\bet\bt <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the node_call a DXNet
+ set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 1\b11\b1.\b.7\b75\b5.\b. s\bse\bet\bt/\b/e\bec\bch\bho\bo (\b(0\b0)\b)
+ 8.76. set/echo (0)
- s\bse\bet\bt/\b/e\bec\bch\bho\bo Make the cluster echo your input
+ set/echo Make the cluster echo your input
If you are connected via a telnet session, different implimentations
connected via port 23 or some other port. You can use this command to
change the setting appropriately.
- You can remove the echo with the _\bu_\bn_\bs_\be_\bt_\b/_\be_\bc_\bh_\bo command
+ You can remove the echo with the unset/echo command
The setting is stored in your user profile.
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 1\b11\b1.\b.7\b76\b6.\b. s\bse\bet\bt/\b/h\bhe\ber\bre\be (\b(0\b0)\b)
+ 8.77. set/here (0)
- s\bse\bet\bt/\b/h\bhe\ber\bre\be Set the here flag
+ set/here Set the here flag
Let others on the cluster know you are here by only displaying your
callsign. If you are away from your terminal you can use the
- _\bu_\bn_\bs_\be_\bt_\b/_\bh_\be_\br_\be command to let people know you are away. This simply puts
+ unset/here command to let people know you are away. This simply puts
brackets around your callsign to indicate you are not available.
- 1\b11\b1.\b.7\b77\b7.\b. s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be (\b(0\b0)\b)
+ 8.78. set/homenode (0)
- s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Set your home cluster
+ set/homenode <node_call> Set your home cluster
Tell the cluster system where you normally connect to. Any Messages
+ 8.79. set/hops (8)
- 1\b11\b1.\b.7\b78\b8.\b. s\bse\bet\bt/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
-
- s\bse\bet\bt/\b/h\bho\bop\bps\bs <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> a\ban\bnn\bn|\b|s\bsp\bpo\bot\bts\bs|\b|w\bww\bwv\bv|\b|w\bwc\bcy\by <\b<n\bn>\b> Set hop count
+ set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
Set the hop count for a particular type of broadcast for a node.
creates a filter and works in conjunction with the filter system.
- 1\b11\b1.\b.7\b79\b9.\b. s\bse\bet\bt/\b/i\bis\bso\bol\bla\bat\bte\be (\b(9\b9)\b)
+ 8.80. set/isolate (9)
- s\bse\bet\bt/\b/i\bis\bso\bol\bla\bat\bte\be <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Isolate a node from the rest of the network
+ set/isolate <node call> Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full
You can remove the isolation with the command unset/isolate.
- 1\b11\b1.\b.8\b80\b0.\b. s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be (\b(0\b0)\b)
+ 8.81. set/language (0)
- s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be <\b<l\bla\ban\bng\bgu\bua\bag\bge\be>\b> Set the language you wish to use
+ set/language <language> Set the language you wish to use
You can select the language that you want the cluster to use.
- Currently the languages available are _\be_\bn (English) and _\bn_\bl (Dutch).
+ Currently the languages available are en (English) and nl (Dutch).
- 1\b11\b1.\b.8\b81\b1.\b. s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn (\b(0\b0)\b)
+ 8.82. set/location (0)
- s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt a\ban\bnd\bd l\blo\bon\bng\bg>\b> Set your latitude and longitude
+ set/location <lat and long> Set your latitude and longitude
You can set your latitude and longitude manually or alternatively use
- the _\bs_\be_\bt_\b/_\bq_\br_\ba command which will do the conversion for you.
+ the set/qra command which will do the conversion for you.
+ 8.83. set/sys_location (9)
- 1\b11\b1.\b.8\b82\b2.\b. s\bse\bet\bt/\b/s\bsy\bys\bs_\b_l\blo\boc\bca\bat\bti\bio\bon\bn (\b(9\b9)\b)
-
- s\bse\bet\bt/\b/s\bsy\bys\bs_\b_l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt &\b& l\blo\bon\bng\bg>\b> Set your cluster latitude and longitude
+ set/sys_location <lat & long> Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the
- 1\b11\b1.\b.8\b83\b3.\b. s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo (\b(0\b0)\b)
+ 8.84. set/logininfo (0)
- s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo Show logins and logouts of nodes and users
+ set/logininfo Show logins and logouts of nodes and users
Show users and nodes when they log in and out of the local cluster.
- You can stop these messages by using the _\bu_\bn_\bs_\be_\bt_\b/_\bl_\bo_\bg_\bi_\bn_\bi_\bn_\bf_\bo command.
-
+ You can stop these messages by using the unset/logininfo command.
- 1\b11\b1.\b.8\b84\b4.\b. s\bse\bet\bt/\b/l\blo\boc\bck\bko\bou\but\bt (\b(9\b9)\b)
- s\bse\bet\bt/\b/l\blo\boc\bck\bko\bou\but\bt <\b<c\bca\bal\bll\bl>\b> Stop a callsign connecting to the cluster
+ 8.85. set/lockout (9)
+ set/lockout <call> Stop a callsign connecting to the cluster
- You can show who is locked out with the _\bs_\bh_\bo_\bw_\b/_\bl_\bo_\bc_\bk_\bo_\bu_\bt command. To
- allow the user to connect again, use the _\bu_\bn_\bs_\be_\bt_\b/_\bl_\bo_\bc_\bk_\bo_\bu_\bt command.
+ You can show who is locked out with the show/lockout command. To
+ allow the user to connect again, use the unset/lockout command.
- 1\b11\b1.\b.8\b85\b5.\b. s\bse\bet\bt/\b/n\bna\bam\bme\be (\b(0\b0)\b)
+ 8.86. set/name (0)
- s\bse\bet\bt/\b/n\bna\bam\bme\be <\b<y\byo\bou\bur\br_\b_n\bna\bam\bme\be>\b> Set your name
+ set/name <your_name> Set your name
Tell the cluster what your name is, eg:-
- 1\b11\b1.\b.8\b86\b6.\b. s\bse\bet\bt/\b/n\bno\bod\bde\be (\b(9\b9)\b)
+ 8.87. set/node (9)
- s\bse\bet\bt/\b/n\bno\bod\bde\be <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the callsign an AK1A cluster
+ set/node <call> [<call> ...] Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster and
- 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 _\bs_\bh_\bo_\bw_\b/_\bn_\bo_\bd_\be_\bs command.
- 1\b11\b1.\b.8\b87\b7.\b. s\bse\bet\bt/\b/o\bob\bbs\bsc\bco\bou\bun\bnt\bt (\b(9\b9)\b)
+ To see what your nodes are set to, use the show/nodes command.
- s\bse\bet\bt/\b/o\bob\bbs\bsc\bco\bou\bun\bnt\bt <\b<c\bco\bou\bun\bnt\bt>\b> <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Set the 'pump-up' obsolescence
+
+ 8.88. set/obscount (9)
+
+ set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
+ 8.89. set/page (0)
-
-
- 1\b11\b1.\b.8\b88\b8.\b. s\bse\bet\bt/\b/p\bpa\bag\bge\be (\b(0\b0)\b)
-
- s\bse\bet\bt/\b/p\bpa\bag\bge\be <\b<n\bn>\b> Set the number of lines per page
+ set/page <n> Set the number of lines per page
Tell the system how many lines you wish on a page when the number of
- 1\b11\b1.\b.8\b89\b9.\b. s\bse\bet\bt/\b/p\bpa\bas\bss\bsw\bwo\bor\brd\bd (\b(9\b9)\b)
+ 8.90. set/password (9)
- s\bse\bet\bt/\b/p\bpa\bas\bss\bsw\bwo\bor\brd\bd <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<s\bst\btr\bri\bin\bng\bg>\b> Set a users password
+ set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The string
type password.
- 1\b11\b1.\b.9\b90\b0.\b. s\bse\bet\bt/\b/p\bpi\bin\bng\bgi\bin\bnt\bte\ber\brv\bva\bal\bl (\b(9\b9)\b)
- s\bse\bet\bt/\b/p\bpi\bin\bng\bgi\bin\bnt\bte\ber\brv\bva\bal\bl <\b<t\bti\bim\bme\be>\b> <\b<n\bno\bod\bde\be c\bca\bal\bll\bl>\b> Set the ping time to neighbouring
+ 8.91. set/pinginterval (9)
+
+ set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 1\b11\b1.\b.9\b91\b1.\b. s\bse\bet\bt/\b/p\bpr\bri\biv\bvi\bil\ble\beg\bge\be (\b(9\b9)\b)
+ 8.92. set/privilege (9)
- s\bse\bet\bt/\b/p\bpr\bri\biv\bvi\bil\ble\beg\bge\be <\b<n\bn>\b> <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Set the privilege level on a
+ set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
-
- 0 - normal user
- 1 - allow remote nodes normal user RCMDs
- 5 - various privileged commands (including shutdown, but not disc-
- connect), the normal level for another node.
- 8 - more privileged commands (including disconnect)
- 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
- LEVEL.
+ 0 - normal user
+ 1 - allow remote nodes normal user RCMDs
+ 5 - various privileged commands (including shutdown, but not disc-
+ connect), the normal level for another node.
+ 8 - more privileged commands (including disconnect)
+ 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
+ LEVEL.
connection your privilege will automatically be set to 0.
- 1\b11\b1.\b.9\b92\b2.\b. s\bse\bet\bt/\b/s\bsp\bpi\bid\bde\ber\br (\b(5\b5)\b)
+ 8.93. set/spider (5)
- s\bse\bet\bt/\b/s\bsp\bpi\bid\bde\ber\br <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Make the node_call a DXSpider
+ set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
Set the node_call as a DXSpider type node
- 1\b11\b1.\b.9\b93\b3.\b. s\bse\bet\bt/\b/s\bsy\bys\bs_\b_q\bqr\bra\ba (\b(9\b9)\b)
+ 8.94. set/sys_qra (9)
- s\bse\bet\bt/\b/s\bsy\bys\bs_\b_q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your cluster QRA locator
+ set/sys_qra <locator> Set your cluster QRA locator
- 1\b11\b1.\b.9\b94\b4.\b. s\bse\bet\bt/\b/q\bqr\bra\ba (\b(0\b0)\b)
+ 8.95. set/qra (0)
- s\bse\bet\bt/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your QRA locator
+ set/qra <locator> Set your QRA locator
Tell the system what your QRA (or Maidenhead) locator is. If you have
- 1\b11\b1.\b.9\b95\b5.\b. s\bse\bet\bt/\b/q\bqt\bth\bh (\b(0\b0)\b)
+ 8.96. set/qth (0)
- s\bse\bet\bt/\b/q\bqt\bth\bh <\b<y\byo\bou\bur\br Q\bQT\bTH\bH>\b> Set your QTH
+ set/qth <your QTH> Set your QTH
Tell the system where your are. For example:-
- 1\b11\b1.\b.9\b96\b6.\b. s\bse\bet\bt/\b/t\bta\bal\blk\bk (\b(0\b0)\b)
+ 8.97. set/talk (0)
- s\bse\bet\bt/\b/t\bta\bal\blk\bk Allow talk messages to be seen at your console
+ set/talk Allow talk messages to be seen at your console
Allow talk messages to arrive at your console. You can switch off
- talks with the _\bu_\bn_\bs_\be_\bt_\b/_\bt_\ba_\bl_\bk command.
+ talks with the unset/talk command.
- 1\b11\b1.\b.9\b97\b7.\b. s\bse\bet\bt/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 8.98. set/wcy (0)
- s\bse\bet\bt/\b/w\bwc\bcy\by Allow WCY messages to be seen at your console
+ set/wcy Allow WCY messages to be seen at your console
Allow WCY information to be seen at your console. You can switch off
- WCY messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bc_\by command.
+ WCY messages with the unset/wcy command.
- 1\b11\b1.\b.9\b98\b8.\b. s\bse\bet\bt/\b/w\bww\bwv\bv (\b(0\b0)\b)
+ 8.99. set/wwv (0)
- s\bse\bet\bt/\b/w\bww\bwv\bv Allow WWV messages to be seen at your console
+ set/wwv Allow WWV messages to be seen at your console
Allow WWV information to be seen at your console. You can switch off
- WWV messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bw_\bv command.
+ WWV messages with the unset/wwv command.
- 1\b11\b1.\b.9\b99\b9.\b. s\bse\bet\bt/\b/w\bwx\bx (\b(0\b0)\b)
+ 8.100. set/wx (0)
- s\bse\bet\bt/\b/w\bwx\bx Allow WX messages to be seen at your console
+ set/wx Allow WX messages to be seen at your console
Allow WX information to be seen at your console. You can switch off
- WX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bx command.
+ WX messages with the unset/wx command.
+
- 1\b11\b1.\b.1\b10\b00\b0.\b. s\bsh\bho\bow\bw/\b/b\bba\bad\bdd\bdx\bx (\b(1\b1)\b)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bdd\bdx\bxShow all the bad dx calls in the system
+
+ 8.101. show/baddx (1)
+
+ show/baddxShow all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDX for more
information.
- 1\b11\b1.\b.1\b10\b01\b1.\b. s\bsh\bho\bow\bw/\b/b\bba\bad\bdn\bno\bod\bde\be (\b(6\b6)\b)
+ 8.102. show/badnode (6)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bdn\bno\bod\bde\be Show all the bad nodes in the system
+ show/badnode Show all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODE for
more information.
- 1\b11\b1.\b.1\b10\b02\b2.\b. s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\br (\b(1\b1)\b)
+ 8.103. show/badspotter (1)
- s\bsh\bho\bow\bw/\b/b\bba\bad\bds\bsp\bpo\bot\btt\bte\ber\brShow all the bad spotters in the system
+ show/badspotter Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see
SET/BADSPOTTER for more information.
- 1\b11\b1.\b.1\b10\b03\b3.\b. s\bsh\bho\bow\bw/\b/d\bda\bat\bte\be (\b(0\b0)\b)
+ 8.104. show/configuration (0)
+
+ show/configuration [<node>] Show all visible nodes and their users
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected. With the optional node, you can
+ specify a particular node to look at.
+
+ This command is normally abbreviated to: sh/c
+
+ BE WARNED: the list that is returned can be VERY long
+
+
+ 8.105. show/configuration/node (0)
+
+ show/configuration/node Show all the nodes connected
+
+
+ Show all the nodes connected locally and the nodes they have
+ connected.
+
+
+ 8.106. show/connect (1)
+
+ show/connect Show all the active connections
+
- s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
+ This command shows information on all the active connections known to
+ the node. This command gives slightly more information than WHO.
+
+
+ 8.107. 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.
- 1\b11\b1.\b.1\b10\b04\b4.\b. s\bsh\bho\bow\bw/\b/d\bdx\bx (\b(0\b0)\b)
+ 8.108. show/debug (9)
+
+ show/debug Show what levels of debug you are logging
+
+
+ The levels can be set with set/debug
+
- s\bsh\bho\bow\bw/\b/d\bdx\bx [\b[o\bop\bpt\bti\bio\bon\bns\bs]\b] interrogate the spot database
+ 8.109. show/dx (0)
+
+ show/dx [options] interrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop
- 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
+
+
+
- 1\b11\b1.\b.1\b10\b05\b5.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxc\bcc\bc (\b(0\b0)\b)
- s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> Interrogate the spot database by country
+ 8.110. show/dxcc (0)
+
+ show/dxcc <prefix> Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial
- 1\b11\b1.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs (\b(0\b0)\b)
+ 8.111. show/files (0)
- s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs [\b[<\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b> [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b]]\b] List the contents of a filearea
+ show/files [<filearea> [<string>]] List the contents of a filearea
SHOW/FILES on its own will show you a list of the various fileareas
See also TYPE - to see the contents of a file.
- 1\b11\b1.\b.1\b10\b07\b7.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(0\b0)\b)
- s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br Show the filters you have set
+ 8.112. 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.
- 1\b11\b1.\b.1\b10\b08\b8.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br (\b(e\bex\bxt\bte\ben\bnd\bde\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 8.113. show/filter (extended for sysops) (5)
+
+ show/filter <callsign> Show the filters set by <callsign>
- s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 1\b11\b1.\b.1\b10\b09\b9.\b. s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs (\b(8\b8)\b)
+ 8.114. show/hops (8)
- s\bsh\bho\bow\bw/\b/h\bho\bop\bps\bs <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[a\ban\bnn\bn|\b|s\bsp\bpo\bot\bts\bs|\b|w\bwc\bcy\by|\b|w\bww\bwv\bv|\b|]\b] Show the hop counts for a
+ show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 1\b11\b1.\b.1\b11\b10\b0.\b. s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be (\b(1\b1)\b)
+ 8.115. show/isolate (1)
- s\bsh\bho\bow\bw/\b/i\bis\bso\bol\bla\bat\bte\be Show a list of isolated nodes
+ show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 1\b11\b1.\b.1\b11\b11\b1.\b. s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt (\b(9\b9)\b)
+ 8.116. show/lockout (9)
- s\bsh\bho\bow\bw/\b/l\blo\boc\bck\bko\bou\but\bt Show a list of excluded callsigns
+ show/lockout Show a list of excluded callsigns
Show a list of callsigns that have been excluded (locked out) of the
- cluster locally with the _\bs_\be_\bt_\b/_\bl_\bo_\bc_\bk_\bo_\bu_\bt command
+ cluster locally with the set/lockout command
+
+ 8.117. show/log (8)
- 1\b11\b1.\b.1\b11\b12\b2.\b. s\bsh\bho\bow\bw/\b/m\bmo\boo\bon\bn (\b(0\b0)\b)
+ show/log [<callsign>] Show excerpts from the system log
- s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show moon rise and set times
+
+ This command outputs a short section of the system log. On its own it
+ will output a general logfile. With the optional callsign it will
+ show output from the log associated with that callsign.
+
+
+ 8.118. 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
- 1\b11\b1.\b.1\b11\b13\b3.\b. s\bsh\bho\bow\bw/\b/m\bmu\buf\bf (\b(0\b0)\b)
+ 8.119. show/muf (0)
- s\bsh\bho\bow\bw/\b/m\bmu\buf\bf <\b<p\bpr\bre\bef\bfi\bix\bx>\b> [\b[<\b<h\bho\bou\bur\brs\bs>\b>]\b][\b[l\blo\bon\bng\bg]\b] Show the likely propagation to
+ show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
+
This command allow you to estimate the likelihood of you contacting a
station with the prefix you have specified. The output assumes a
modest power of 20dBW and receiver sensitivity of -123dBm (about
SH/MUF W
-
-
-
produces:
inputing:-
+
SH/MUF W 24
terrible accurate, but it is included for completeness.
- 1\b11\b1.\b.1\b11\b14\b4.\b. s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be (\b(1\b1)\b)
+ 8.120. show/node (1)
- s\bsh\bho\bow\bw/\b/n\bno\bod\bde\be [\b[<\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Show the type and version number of nodes
+ show/node [<node_call> ...] Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the
the non-user callsigns known to the system will be displayed.
- 1\b11\b1.\b.1\b11\b15\b5.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx (\b(0\b0)\b)
+ 8.121. show/prefix (0)
- s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Interrogate the prefix database
+ show/prefix <callsign> Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial
See also SHOW/DXCC
+ 8.122. show/program (5)
-
- 1\b11\b1.\b.1\b11\b16\b6.\b. s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm (\b(5\b5)\b)
-
- s\bsh\bho\bow\bw/\b/p\bpr\bro\bog\bgr\bra\bam\bm Show the locations of all the included program modules
+ show/program Show the locations of all the included program modules
Show the name and location where every program module was load from.
from.
- 1\b11\b1.\b.1\b11\b17\b7.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba (\b(0\b0)\b)
+ 8.123. show/qra (0)
- s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> [\b[<\b<l\blo\boc\bca\bat\bto\bor\br>\b>]\b] Show the distance between locators
- s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\bla\bat\bt>\b> <\b<l\blo\bon\bng\bg>\b> Convert latitude and longitude to a locator
+ show/qra <locator> [<locator>] Show the distance between locators
+ show/qra <lat> <long> Convert latitude and longitude to a locator
This is a multipurpose command that allows you either to calculate the
given on the command line) the distance and beraing from your station
to the locator. For example:-
+
+
SH/QRA IO92QL
SH/QRA JN06 IN73
- 1\b11\b1.\b.1\b11\b18\b8.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz (\b(0\b0)\b)
+ 8.124. show/qrz (0)
- s\bsh\bho\bow\bw/\b/q\bqr\brz\bz <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show any callbook details on a callsign
+ show/qrz <callsign> Show any callbook details on a callsign
This command queries the QRZ callbook server on the internet and
provided for users of this software by http://www.qrz.com
- 1\b11\b1.\b.1\b11\b19\b9.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be (\b(0\b0)\b)
+ 8.125. show/route (0)
- s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the route to <callsign>
+ show/route <callsign> Show the route to <callsign>
This command allows you to see to which node the callsigns specified
- sh/route n2tly
+ sh/route n2tly
- 1\b11\b1.\b.1\b12\b20\b0.\b. s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be (\b(0\b0)\b)
+ 8.126. show/satellite (0)
- s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be <\b<n\bna\bam\bme\be>\b> [\b[<\b<h\bho\bou\bur\brs\bs>\b> <\b<i\bin\bnt\bte\ber\brv\bva\bal\bl>\b>]\b] Show satellite tracking
+ show/satellite <name> [<hours> <interval>] Show satellite tracking
data
- 1\b11\b1.\b.1\b12\b21\b1.\b. s\bsh\bho\bow\bw/\b/s\bsu\bun\bn (\b(0\b0)\b)
+ 8.127. show/sun (0)
- s\bsh\bho\bow\bw/\b/s\bsu\bun\bn [\b[<\b<p\bpr\bre\bef\bfi\bix\bx>\b>|\b|<\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b>]\b] Show sun rise and set times
+ show/sun [<prefix>|<callsign>] Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns,
- 1\b11\b1.\b.1\b12\b22\b2.\b. s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be (\b(0\b0)\b)
+ 8.128. show/time (0)
- s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be [\b[<\b<p\bpr\bre\bef\bfi\bix\bx>\b>|\b|<\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b>]\b] Show the local time
+ show/time [<prefix>|<callsign>] Show the local time
If no prefixes or callsigns are given then this command returns the
including DST) at the prefixes or callsigns that you specify.
- 1\b11\b1.\b.1\b12\b23\b3.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by (\b(0\b0)\b)
+ 8.129. show/wcy (0)
- s\bsh\bho\bow\bw/\b/w\bwc\bcy\by Show the last 10 WCY broadcasts
- s\bsh\bho\bow\bw/\b/w\bwc\bcy\by <\b<n\bn>\b> Show the last <n> WCY broadcasts
+ show/wcy Show the last 10 WCY broadcasts
+ show/wcy <n> Show the last <n> WCY broadcasts
Display the most recent WCY information that has been received by the
system
+ 8.130. show/wwv (0)
-
- 1\b11\b1.\b.1\b12\b24\b4.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv (\b(0\b0)\b)
-
- s\bsh\bho\bow\bw/\b/w\bww\bwv\bv Show the last 10 WWV broadcasts
- s\bsh\bho\bow\bw/\b/w\bww\bwv\bv <\b<n\bn>\b> Show the last <n> WWV broadcasts
+ show/wwv Show the last 10 WWV broadcasts
+ show/wwv <n> Show the last <n> WWV broadcasts
Display the most recent WWV information that has been received by the
- 1\b11\b1.\b.1\b12\b25\b5.\b. s\bsh\bhu\but\btd\bdo\bow\bwn\bn (\b(5\b5)\b)
+ 8.131. shutdown (5)
- s\bsh\bhu\but\btd\bdo\bow\bwn\bn Shutdown the cluster
+ shutdown Shutdown the cluster
Shutdown the cluster and disconnect all the users. If you have Spider
set to respawn in /etc/inittab it will of course restart.
- 1\b11\b1.\b.1\b12\b26\b6.\b. s\bsp\bpo\boo\bof\bf (\b(9\b9)\b)
+ 8.132. spoof (9)
- s\bsp\bpo\boo\bof\bf <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b> Run commands as another user
+ spoof <callsign> <command> Run commands as another user
This is a very simple yet powerful command for the sysop. It allows
like home_node for example.
- 1\b11\b1.\b.1\b12\b27\b7.\b. s\bst\bta\bat\bt/\b/d\bdb\bb (\b(5\b5)\b)
+ 8.133. stat/db (5)
- s\bst\bta\bat\bt/\b/d\bdb\bb <\b<d\bdb\bbn\bna\bam\bme\be>\b> Show the status of a database
+ stat/db <dbname> Show the status of a database
Show the internal status of a database descriptor.
other than a sysop.
- 1\b11\b1.\b.1\b12\b28\b8.\b. s\bst\bta\bat\bt/\b/c\bch\bha\ban\bnn\bne\bel\bl (\b(5\b5)\b)
- s\bst\bta\bat\bt/\b/c\bch\bha\ban\bnn\bne\bel\bl <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the status of a channel on the cluster
+
+ 8.134. stat/channel (5)
+
+ stat/channel <callsign> Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel
Only the fields that are defined (in perl term) will be displayed.
- 1\b11\b1.\b.1\b12\b29\b9.\b. s\bst\bta\bat\bt/\b/m\bms\bsg\bg (\b(5\b5)\b)
+ 8.135. stat/msg (5)
- s\bst\bta\bat\bt/\b/m\bms\bsg\bg <\b<m\bms\bsg\bgn\bno\bo>\b> Show the status of a message
+ stat/msg <msgno> Show the status of a message
This command shows the internal status of a message and includes
etc etc.
+ If no message number is given then the status of the message system is
+ displayed.
+
+
+ 8.136. stat/route_node (5)
+
+ stat/route_node <callsign> Show the data in a Route::Node object
- 1\b11\b1.\b.1\b13\b30\b0.\b. s\bst\bta\bat\bt/\b/u\bus\bse\ber\br (\b(5\b5)\b)
+ 8.137. stat/route_user (5)
- s\bst\bta\bat\bt/\b/u\bus\bse\ber\br <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the full status of a user
+ stat/route_user <callsign> Show the data in a Route::User object
+
+
+ 8.138. stat/user (5)
+
+ stat/user <callsign> Show the full status of a user
Shows the full contents of a user record including all the secret
Only the fields that are defined (in perl term) will be displayed.
- 1\b11\b1.\b.1\b13\b31\b1.\b. s\bsy\bys\bso\bop\bp (\b(0\b0)\b)
+ 8.139. sysop (0)
- s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely
+ sysop Regain your privileges if you login remotely
The system automatically reduces your privilege level to that of a
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
+
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
case sensitive.
- 1\b11\b1.\b.1\b13\b32\b2.\b. t\bta\bal\blk\bk (\b(0\b0)\b)
+ 8.140. talk (0)
- t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Enter talk mode with <callsign>
- t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<t\bte\bex\bxt\bt>\b> Send a text message to <callsign>
- t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> >\b> <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b] Send a text message to
+ talk <callsign> Enter talk mode with <callsign>
+ talk <callsign> <text> Send a text message to <callsign>
+ talk <callsign> > <node_call> [<text>] Send a text message to
<callsign> via <node_call>
cluster system. You can send it to anyone you can see with a
SHOW/CONFIGURATION command, they don't have to be connected locally.
-
The second form of TALK is used when other cluster nodes are connected
with restricted information. This usually means that they don't send
the user information usually associated with logging on and off the
To leave talk mode type:
-
-
/EX
- 1\b11\b1.\b.1\b13\b33\b3.\b. t\bty\byp\bpe\be (\b(0\b0)\b)
+ 8.141. type (0)
- t\bty\byp\bpe\be <\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b>/\b/<\b<n\bna\bam\bme\be>\b> Look at a file in one of the fileareas
+ type <filearea>/<name> Look at a file in one of the fileareas
Type out the contents of a file in a filearea. So, for example, in
content.
- 1\b11\b1.\b.1\b13\b34\b4.\b. w\bwh\bho\bo (\b(0\b0)\b)
+ 8.142. who (0)
- w\bwh\bho\bo Show who is physically connected locally
+ who Show who is physically connected locally
This is a quick listing that shows which callsigns are connected and
what sort of connection they have
- 1\b11\b1.\b.1\b13\b35\b5.\b. w\bwx\bx (\b(0\b0)\b)
- w\bwx\bx <\b<t\bte\bex\bxt\bt>\b> Send a weather message to local users
- w\bwx\bx f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send a weather message to all cluster users
+
+ 8.143. wx (0)
+
+ wx <text> Send a weather message to local users
+ wx full <text> Send a weather message to all cluster users
Weather messages can sometimes be useful if you are experiencing an
extreme that may indicate enhanced conditions
- 1\b11\b1.\b.1\b13\b36\b6.\b. w\bwx\bx (\b(e\ben\bnh\bha\ban\bnc\bce\bed\bd f\bfo\bor\br s\bsy\bys\bso\bop\bps\bs)\b) (\b(5\b5)\b)
+ 8.144. wx (enhanced for sysops) (5)
- w\bwx\bx s\bsy\bys\bso\bop\bp <\b<t\bte\bex\bxt\bt>\b> Send a weather message to other clusters only
+ wx sysop <text> Send a weather message to other clusters only
Send a weather message only to other cluster nodes and not to general
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
projects / spider.git / blobdiff