The DXSpider Administration Manual v1.48
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.48 September 2001 revision 1.2
+ Version 1.49 November 2001 revision 1.1
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
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)
+ 6.2 MOTD_NOR
+ 6.3 Downtime message
+ 6.4 Other text messages
+ 6.5 The Aliases file
+ 6.6 Console.pl
+ 6.7 Updating kepler data
+ 6.8 The QRZ callbook
+
+ 7. Security
+
+ 7.1 Registration
+ 7.2 Passwords
+
+ 8. CVS
+
+ 9. The DXSpider command set
+
+ 9.1 accept/announce (0)
+ 9.2 accept/announce (extended for sysops) (8)
+ 9.3 accept/route (8)
+ 9.4 accept/spots (0)
+ 9.5 accept/spots (extended for sysops) (8)
+ 9.6 accept/wcy (0)
+ 9.7 accept/wcy (extended for sysops) (8)
+ 9.8 accept/wwv (0)
+ 9.9 accept/wwv (extended for sysops) (8)
+ 9.10 announce (0)
+ 9.11 announce full (0)
+ 9.12 announce sysop (5)
+ 9.13 apropos (0)
+ 9.14 bye (0)
+ 9.15 catchup (5)
+ 9.16 clear/announce (8)
+ 9.17 clear/route (8)
+ 9.18 clear/spots (0)
+ 9.19 clear/spots (extended for sysops) (8)
+ 9.20 clear/wcy (0)
+ 9.21 clear/wcy (extended for sysops) (8)
+ 9.22 clear/wwv (0)
+ 9.23 clear/wwv (extended for sysops) (8)
+ 9.24 connect (5)
+ 9.25 dbavail (0)
+ 9.26 dbcreate (9)
+ 9.27 dbimport (9)
+ 9.28 dbremove (9)
+ 9.29 dbshow (0)
+ 9.30 debug (9)
+ 9.31 delete/user (9)
+ 9.32 directory (0)
+ 9.33 directory (extended for sysops) (5)
+ 9.34 disconnect (8)
+ 9.35 dx (0)
+ 9.36 export (9)
+ 9.37 export_users (9)
+ 9.38 filtering (0)
+ 9.39 forward/latlong (8)
+ 9.40 forward/opername (1)
+ 9.41 help (0)
+ 9.42 init (5)
+ 9.43 kill (0)
+ 9.44 kill (5)
+ 9.45 kill full (5)
+ 9.46 kill/expunge (6)
+ 9.47 links (0)
+ 9.48 load/aliases (9)
+ 9.49 load/badmsg (9)
+ 9.50 load/badwords (9)
+ 9.51 load/bands (9)
+ 9.52 load/cmd_cache (9)
+ 9.53 load/forward (9)
+ 9.54 load/messages (9)
+ 9.55 load/prefixes (9)
+ 9.56 merge (5)
+ 9.57 msg (9)
+ 9.58 pc (8)
+ 9.59 ping (1)
+ 9.60 rcmd (1)
+ 9.61 read (0)
+ 9.62 read (extended for sysops) (5)
+ 9.63 reject/announce
+ 9.64 reject/announce (extended for sysops) (8)
+ 9.65 reject/route (8)
+ 9.66 reject/spots (0)
+ 9.67 reject/spots (extended for sysops) (8)
+ 9.68 reject/wcy (0)
+ 9.69 reject/wcy (extended for sysops) (8)
+ 9.70 reject/wwv (0)
+ 9.71 reject/wwv (extended for sysops) (8)
+ 9.72 reply (0)
+ 9.73 send (0)
+ 9.74 set/address (0)
+ 9.75 set/announce (0)
+ 9.76 set/arcluster (5)
+ 9.77 set/baddx (8)
+ 9.78 set/badnode (6)
+ 9.79 set/badspotter (8)
+ 9.80 set/badword (8)
+ 9.81 set/beep (0)
+ 9.82 set/bbs (5)
+ 9.83 set/clx (5)
+ 9.84 set/debug (9)
+ 9.85 set/dx (0)
+ 9.86 set/dxgrid (0)
+ 9.87 set/dxnet (5)
+ 9.88 set/echo (0)
+ 9.89 set/email (0)
+ 9.90 set/here (0)
+ 9.91 set/homenode (0)
+ 9.92 set/hops (8)
+ 9.93 set/isolate (9)
+ 9.94 set/language (0)
+ 9.95 set/location (0)
+ 9.96 set/sys_location (9)
+ 9.97 set/logininfo (0)
+ 9.98 set/lockout (9)
+ 9.99 set/name (0)
+ 9.100 set/node (9)
+ 9.101 set/obscount (9)
+ 9.102 set/page (0)
+ 9.103 set/password (0)
+ 9.104 set/password (9)
+ 9.105 set/pinginterval (9)
+ 9.106 set/privilege (9)
+ 9.107 set/spider (5)
+ 9.108 set/sys_qra (9)
+ 9.109 set/qra (0)
+ 9.110 set/qth (0)
+ 9.111 set/register (9)
+ 9.112 set/talk (0)
+ 9.113 set/wcy (0)
+ 9.114 set/wwv (0)
+ 9.115 set/wx (0)
+ 9.116 show/baddx (1)
+ 9.117 show/badnode (6)
+ 9.118 show/badspotter (1)
+ 9.119 show/badword (1)
+ 9.120 show/configuration (0)
+ 9.121 show/configuration/node (0)
+ 9.122 show/connect (1)
+ 9.123 show/date (0)
+ 9.124 show/debug (9)
+ 9.125 show/dx (0)
+ 9.126 show/dxcc (0)
+ 9.127 sh/dxstats (0)
+ 9.128 show/files (0)
+ 9.129 show/filter (0)
+ 9.130 show/filter (extended for sysops) (5)
+ 9.131 show/hfstats (0)
+ 9.132 show/hftable (0)
+ 9.133 show/hops (8)
+ 9.134 show/isolate (1)
+ 9.135 show/lockout (9)
+ 9.136 show/log (8)
+ 9.137 show/moon (0)
+ 9.138 show/muf (0)
+ 9.139 show/newconfiguration (0)
+ 9.140 show/newconfiguration/node (0)
+ 9.141 show/node (1)
+ 9.142 show/prefix (0)
+ 9.143 show/program (5)
+ 9.144 show/qra (0)
+ 9.145 show/qrz (0)
+ 9.146 show/registered (9)
+ 9.147 show/route (0)
+ 9.148 show/satellite (0)
+ 9.149 show/sun (0)
+ 9.150 show/time (0)
+ 9.151 show/vhfstats (0)
+ 9.152 show/vhftable (0)
+ 9.153 show/wcy (0)
+ 9.154 show/wwv (0)
+ 9.155 shutdown (5)
+ 9.156 spoof (9)
+ 9.157 stat/db (5)
+ 9.158 stat/channel (5)
+ 9.159 stat/msg (5)
+ 9.160 stat/route_node (5)
+ 9.161 stat/route_user (5)
+ 9.162 stat/user (5)
+ 9.163 sysop (0)
+ 9.164 talk (0)
+ 9.165 type (0)
+ 9.166 who (0)
+ 9.167 wx (0)
+ 9.168 wx (enhanced for sysops) (5)
______________________________________________________________________
The generic commands are:-
-
-
reject/route node_default <filter_option>
or
Please be careful if you alter this setting, it will affect ALL your
links! Remember, this is a default filter for node connections, not a
per link default.
+
+
For the default routing filter then you have two real choices: either
a "national" view or the "safe" option of only your own callsign.
Examples of each (for my node: GB7DJK) are:-
Exactly the same rules apply for general route filtering. You would
use either an accept filter or a reject filter like this ...
+
+
+
reject/route <node_call> <filter_option>
or
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
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
reject/spots 1 on hf/ssb
-
-
-
would redefine our earlier example, or
the various helpfiles for accept, reject and filter.
-
-
-
1.8. Default filters
Sometimes all that is needed is a general rule for node connects.
acc/spot on 0/30000
acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-
-
-
Note that the first filter has not been specified with a number. This
will automatically be assumed to be number 1. In this case, we have
said reject all HF spots in the CW section of the bands but accept all
- #
- # hop table construction
- #
- package DXProt;
- # default hopcount to use
- $def_hopcount = 5;
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
- # the per node hop control thingy
- %nodehops =
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- };
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #
+ # hop table construction
+ #
+
+ package DXProt;
+
+ # default hopcount to use
+ $def_hopcount = 5;
+
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
+
+
+ # the per node hop control thingy
+
+
+ %nodehops =
+
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
will bring your changes into effect.
+
1.11. Hop Control on Specific Nodes
You can set a callsign specific hop count for any of the standard
+
+
+
+
+
# 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)
DXSpider's operation with scripts of various kinds.
- In the first instance, in 1.48, the sysop can create, with their
- favorite text editor, files in the directory /spider/scripts which
- contain any legal command for a callsign or class of connection which
- will be executed at logon.
+ The directory /spider/scripts is where it all happens and is used for
+ several things. Firstly it contains a file called startup that can be
+ used to call in any changes to the cluster from the default settings
+ on startup. This script is executed immediately after all
+ initialisation of the node is done but before any connections are
+ possible. Examples of this include how many spots it is possible to
+ get with the sh/dx command, whether you want registration/passwords to
+ be permanently on etc. An example file is shown below and is included
+ in the distribution as startup.issue.
- The filename is the callsign of the connection that you want the
- script to operate on, eg: /spider/scripts/g1tlh. The filenames are
- always in lower case on those architectures where this makes a
- difference.
- In addition to the callsign specific scripts there are three others:-
- startup
- user_default
- node_default
+ #
+ # startup script example
+ #
+ # set maximum no of spots allowed to 100
+ # set/var $Spot::maxspots = 1
+ #
+ # Set registration on
+ # set/var $main::reqreg = 1
+ #
+ # Set passwords on
+ # set/var $main::passwdreq = 1
+ #
+
+
+
+
+
+ As usual, any text behind a # is treated as a comment and not read.
+
+ Secondly, it is used to store the login scripts for users and nodes.
+ Currently this can only be done by the sysop but it is envisaged that
+ eventually users will be able to set their own. An example is
+ included in the distibution but here is a further example.
+ #
+ # G0FYD
+ #
+ blank +
+ sh/wwv 3
+ blank +
+ sh/dx
+ blank +
+ t g0jhc You abt?
+ blank +
- The startup script is executed immediately after all initialisation of
- the node is done, but before any connections are possible.
- The user_default script is executed for every user that does NOT
- already have a specific script.
+ The lines in between commands can simply insert a blank line or a
+ character such as a + sign to make the output easier to read. Simply
+ create this script with your favourite editor and save it with the
+ callsign of the user as the filename. Filenames should always be in
+ lower case.
- The node_default script is executed for every node that doesn't have a
- specific script.
+ Commands can be inserted in the same way for nodes. A node may wish a
+ series of commands to be issued on login, such as a merge command for
+ example.
- There are a couple of examples in the /spider/scripts directory.
+
+ Thirdly, there are 2 default scripts for users and nodes who do not
+ have a specifically defined script. These are user_default and
+ node_default
5. Databases
+
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...
-
This will update the existing local oblast database or create it if it
does not exist.
If you remove a database it ceases to exist and would have to be
created from scratch if you still required it.
-
6. Information, files and useful programs
6.1. MOTD
to the cluster.
- 6.2. Downtime message
+ 6.2. MOTD_NOR
+
+ This message of the day file lives in the same directory as the
+ standard motd file but is only sent to non-registered users. Once
+ registered they will receive the same message as any other user.
+
+
+ 6.3. Downtime message
If for any reason the cluster is down, maybe for upgrade or
maintenance but the machine is still running, a message can be sent to
actually running.
- 6.3. Other text messages
+ 6.4. Other text messages
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
like. These can be listed by the user with the command ....
+
show/files
+ show/files bulletin
+ opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
+ opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
+ opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
+ opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
+ opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
+ opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
+ opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
+ opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
+ opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
+ opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
+ opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
+ opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
+ opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
+ Press Enter to continue, A to abort (16 lines) >
- show/files bulletin
- opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
- opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
- opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
- opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
- opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
- opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
- opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
- opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
- opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
- opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
- opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
- opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
- opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
- Press Enter to continue, A to abort (16 lines) >
+ You can now read any file in this directory using the type command,
+ like this ....
- You can now read any file in this directory using the type command,
- like this ....
- type bulletin/opdx391
- Ohio/Penn DX Bulletin No. 391
- The Ohio/Penn Dx PacketCluster
- DX Bulletin No. 391
- BID: $OPDX.391
- January 11, 1999
- Editor Tedd Mirgliotta, KB8NW
- Provided by BARF-80 BBS Cleveland, Ohio
- Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
- Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
- Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
- & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
- Press Enter to continue, A to abort (508 lines) >
+ type bulletin/opdx391
+ Ohio/Penn DX Bulletin No. 391
+ The Ohio/Penn Dx PacketCluster
+ DX Bulletin No. 391
+ BID: $OPDX.391
+ January 11, 1999
+ Editor Tedd Mirgliotta, KB8NW
+ Provided by BARF-80 BBS Cleveland, Ohio
+ Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
+ Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
+ Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
+ & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
+ Press Enter to continue, A to abort (508 lines) >
The page length will of course depend on what you have it set to!
- 6.4. The Aliases file
+ 6.5. The Aliases file
You will find a file in /spider/cmd/ called Aliases. First, copy this
file to /spider/local_cmd/Aliases and edit this file. You will see
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
#!/usr/bin/perl
# provide some standard aliases for commands for terminally
the results once you have set an alias.
- 6.5. Console.pl
+ 6.6. Console.pl
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
edit the file with your favourite editor.
- 6.6. Updating kepler data
+ 6.7. Updating kepler data
Spider has a powerful and flexible show/satellite command. In order
for this to be accurate, the kepler data has to be updated regularly.
- 6.7. The QRZ callbook
+ 6.8. The QRZ callbook
The command sh/qrz will only work once you have followed a few simple
steps. First you need to get a user ID and password from qrz.com.
proprieter of qrz.com for allowing this access.
- 7. CVS
+ 7. Security
+
+ From version 1.49 DXSpider has some additional security features.
+ These are not by any means meant to be exhaustive, however they do
+ afford some security against piracy. These two new features can be
+ used independently of each other or in concert to tighten the
+ security.
+
+
+ 7.1. Registration
+
+ The basic principle of registration is simple. If a user is not
+ registered by the sysop, then they have read-only access to the
+ cluster. The only thing they can actually send is a talk or a message
+ to the sysop. In order for them to be able to spot, send announces or
+ talks etc the sysop must register them with the set/register command,
+ like this ...
+
+
+
+ set/register g0vgs
+
+
+
+
+ The user g0vgs can now fully use the cluster. In order to enable
+ registration, you can issue the command ...
+
+
+
+ set/var $main::reqreg = 1
+
+
+
+
+ Any users that are not registered will now see the motd_nor file
+ rather than the motd file as discussed in the Information, files and
+ useful programs section.
+
+
+ Entering this line at the prompt will only last for the time the
+ cluster is running of course and would not be present on a restart.
+ To make the change permanent, add the above line to
+ /spider/scripts/startup. To read more on the startup file, see the
+ section on Information, files and useful programs.
+
+
+ To unregister a user use unset/register and to show the list of
+ registered users, use the command show/register.
+
+
+ 7.2. Passwords
+
+ At the moment, passwords only affect users who login to a DXSpider
+ cluster node via telnet. If a user requires a password, they can
+ either set it themselves or have the sysop enter it for them by using
+ the set/password command. Any users who already have passwords, such
+ as remote sysops, will be asked for their passwords automatically by
+ the cluster. Using passwords in this way means that the user has a
+ choice on whether to have a password or not. To force the use of
+ passwords at login, issue the command ...
+
+
+
+ set/var $main::passwdreq = 1
+
+
+
+
+ at the cluster prompt. This can also be added to the
+ /spider/scripts/startup file as above to make the change permanent.
+
+
+ Of course, if you do this you will have to assign a password for each
+ of your users. If you were asking them to register, it is anticipated
+ that you would ask them to send you a message both to ask to be
+ registered and to give you the password they wish to use.
+
+
+ Should a user forget their password, it can be reset by the sysop by
+ first removing the existing password and then setting a new one like
+ so ...
+
+
+
+ unset/password g0vgs
+ set/password g0vgs new_password
+
+
+
+
+
+ 8. CVS
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
First login as the user sysop. Next you need to connect to the CVS
repository. You do this with the command below ...
-
cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+
+
This command is all on one line.
You will find any changes documented in the /spider/Changes file.
- 8. The DXSpider command set
+ 9. The DXSpider command set
Below is a complete list of commands available from the cluster
prompt. Most maintenance tasks are automatic but there are some
is the permissions level needed to use the command.
- 8.1. accept/announce (0)
+ 9.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
some examples:-
-
-
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+
but this probably for advanced users...
- 8.2. accept/announce (extended for sysops) (8)
+ 9.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
- 8.3. accept/route (8)
+ 9.3. accept/route (8)
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
routing
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>
-
You can use the tag 'all' to accept everything eg:
- 8.4. accept/spots (0)
+ 9.4. accept/spots (0)
accept/announce [0-9] <pattern> Set an accept filter line for spots
-
-
For frequencies, you can use any of the band names defined in
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
acc/spot 3 all
+
+
+
but this probably for advanced users...
- 8.5. accept/spots (extended for sysops) (8)
+ 9.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
- 8.6. accept/wcy (0)
+ 9.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+
+
+
+
+
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
See HELP FILTER for information.
- 8.7. accept/wcy (extended for sysops) (8)
+ 9.7. accept/wcy (extended for sysops) (8)
accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
- accept/wcy node_default all
- set/hops node_default 10
+ accept/wcy node_default all
+ set/hops node_default 10
- 8.8. accept/wwv (0)
+ 9.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
for example
-
accept/wwv by_zone 4
See HELP FILTER for information.
- 8.9. accept/wwv (extended for sysops) (8)
+ 9.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
-
- 8.10. announce (0)
+ 9.10. announce (0)
announce <text> Send an announcement to local users
sysop will override set/noannounce.
- 8.11. announce full (0)
+ 9.11. announce full (0)
announce full <text> Send an announcement cluster wide
- 8.12. announce sysop (5)
+ 9.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 8.13. apropos (0)
+ 9.13. apropos (0)
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.
- 8.14. bye (0)
+ 9.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
- 8.15. catchup (5)
+ 9.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
Order is not important.
- 8.16. clear/spots (0)
+ 9.16. clear/announce (8)
+
+ clear/announce [input] <callsign> [0-9|all] Clear an announce filter
+ line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.17. clear/route (8)
+
+ clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line
+
+
+ This command allows you to clear (remove) a line in a route filter or
+ to remove the whole filter.
+
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.18. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
the filter will be completely removed.
+ 9.19. clear/spots (extended for sysops) (8)
+
+ clear/spots [input] <callsign> [0-9|all] Clear a spot filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
- 8.17. connect (5)
+
+
+ 9.20. clear/wcy (0)
+
+ clear/wcy [1|all] Clear a WCY filter line
+
+
+ This command allows you to clear (remove) a line in a WCY filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+
+ 9.21. clear/wcy (extended for sysops) (8)
+
+ clear/wcy [input] <callsign> [0-9|all] Clear a WCY filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.22. clear/wwv (0)
+
+ clear/wwv [1|all] Clear a WWV filter line
+
+
+ This command allows you to clear (remove) a line in a WWV filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+
+ 9.23. clear/wwv (extended for sysops) (8)
+
+ clear/wwv [input] <callsign> [0-9|all] Clear a WWV filter line
+
+
+ A sysop can clear an input or normal output filter for a user or the
+ node_default or user_default.
+
+
+ 9.24. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 8.18. dbavail (0)
+ 9.25. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 8.19. dbcreate (9)
+ 9.26. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
It would be normal for you to add an entry into your local Aliases
file to allow people to use the 'SHOW/<dbname>' style syntax. So you
would need to add a line like:-
+
+
+
's' => [
..
..
databases. See DBSHOW for generic database enquiry
- 8.20. dbimport (9)
+
+
+ 9.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 8.21. dbremove (9)
+ 9.28. dbremove (9)
dbremove <dbname> Delete a database
You have been warned.
- 8.22. dbshow (0)
+ 9.29. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
-
This is the generic user interface to the database to the database
system. It is expected that the sysop will add an entry to the local
Aliases file so that users can use the more familiar AK1A style of
-
-
- 8.23. debug (9)
+ 9.30. debug (9)
debug Set the cluster program into debug mode
finished.
- 8.24. directory (0)
+ 9.31. delete/user (9)
+
+ delete/user <callsign> Delete a user from the User Database
+
+
+ This command will completely remove a one or more users from the
+ database.
+
+ There is NO SECOND CHANCE.
+
+ It goes without saying that you should use this command CAREFULLY!
+
+
+
+ 9.32. directory (0)
directory List messages
directory own List your own messages
You can combine some of the various directory commands together eg:-
+
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
You can abbreviate all the commands to one letter and use ak1a
syntax:-
-
-
-
DIR/T G1* 10
DIR/S QSL 10-100 5
- 8.25. directory (extended for sysops) (5)
+ 9.33. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 8.26. disconnect (8)
+ 9.34. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 8.27. dx (0)
+ 9.35. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
- DX by G1TLH FR0G 144.600 he isn't on the cluster
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
cluster. See SHOW/BANDS for more information.
- 8.28. export (9)
+ 9.36. export (9)
export <msgno> <filename> Export a message to a file
-
Export a message to a file. This command can only be executed on a
local console with a fully privileged user. The file produced will be
in a form ready to be imported back into the cluster by placing it in
EXPORT 2345 /tmp/a
- 8.29. export_users (9)
+ 9.37. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
- 8.30. forward/latlong (8)
+ 9.38. filtering (0)
+
+ filtering Filtering things in DXSpider
+
+
+ There are a number of things you can filter in the DXSpider system.
+ They all use the same general mechanism.
+
+ In general terms you can create a 'reject' or an 'accept' filter which
+ can have up to 10 lines in it. You do this using, for example:-
+
+ accept/spots ..... reject/spots .....
+
+ where ..... are the specific commands for that type of filter. There
+ are filters for spots, wwv, announce, wcy and (for sysops) connects.
+ See each different accept or reject command reference for more
+ details.
+
+ There is also a command to clear out one or more lines in a filter and
+ one to show you what you have set. They are:-
+
+ clear/spots 1 clear/spots all
+
+ and
+
+ show/filter
+
+ There is clear/xxxx command for each type of filter.
+
+ For now we are going to use spots for the examples, but you can apply
+ the principles to all types of filter.
+
+ There are two main types of filter 'accept' or 'reject'; which you use
+ depends entirely on how you look at the world and what is least
+ writing to achieve what you want. Each filter has 10 lines (of any
+ length) which are tried in order. If a line matches then the action
+ you have specified is taken (ie reject means ignore it and accept
+ means gimme it).
+
+ The important thing to remember is that if you specify a 'reject'
+ filter (all the lines in it say 'reject/spots' (for instance) then if
+ a spot comes in that doesn't match any of the lines then you will get
+ it BUT if you specify an 'accept' filter then any spots that don't
+ match are dumped. For example if I have a one line accept filter:-
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+ then automatically you will ONLY get VHF spots from or to CQ zones 14
+ 15 and 16. If you set a reject filter like:
+
+ reject/spots on hf/cw
+
+ Then you will get everything EXCEPT HF CW spots, If you am interested
+ in IOTA and will work it even on CW then you could say:-
+
+ reject/spots on hf/cw and not info iota
+
+ But in that case you might only be interested in iota and say:-
+
+ accept/spots not on hf/cw or info iota
+
+ which is exactly the same. You should choose one or the other until
+ you are confortable with the way it works. Yes, you can mix them
+ (actually you can have an accept AND a reject on the same line) but
+ don't try this at home until you can analyse the results that you get
+ without ringing up the sysop for help.
+
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. I have one set frequently:-
+
+ reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone
+ 14,15,16 or call_zone 14,15,16)
+
+ What this does is to ignore all HF CW spots (being a class B I can't
+ read any CW and couldn't possibly be interested in HF :-) and also
+ rejects any spots on VHF which don't either originate or spot someone
+ in Europe.
+
+ This is an exmaple where you would use the line number (1 and 2 in
+ this case), if you leave the digit out, the system assumes '1'. Digits
+
+ You can leave the word 'and' out if you want, it is implied. You can
+ use any number of brackets to make the 'expression' as you want it.
+ There are things called precedence rules working here which mean that
+ you will NEED brackets in a situation like line 2 because, without it,
+ will assume:-
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+ annoying, but that is the way it is. If you use OR - use brackets.
+ Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
+ by_zone'.
+
+ If you want to alter your filter you can just redefine one or more
+ lines of it or clear out one line. For example:-
+
+ reject/spots 1 on hf/ssb
+
+ or
+
+ clear/spots 1
+
+
+ To remove the filter in its entirty:-
+
+ clear/spots all
+
+ There are similar CLEAR commands for the other filters:-
+
+ clear/announce clear/wcy clear/wwv
+
+ ADVANCED USERS:-
+
+ Once you are happy with the results you get, you may like to
+ experiment.
+
+ my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+ can be written with a mixed filter, eg:
+
+ rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and
+ (by_zone 14,15,16 or call_zone 14,15,16)
+
+ each filter slot actually has a 'reject' slot and an 'accept' slot.
+ The reject slot is executed BEFORE the accept slot.
+
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ first, any non hf/cw spot is passed to the accept line, which lets
+ thru everything else on HF.
+
+ The next filter line lets through just VHF/UHF spots from EU.
+
+
+ 9.39. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 8.31. forward/opername (1)
+ 9.40. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 8.32. help (0)
+ 9.41. help (0)
help <cmd> Get help on a command
commands to look at with HELP.
- 8.33. init (5)
+ 9.42. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 8.34. kill (0)
+ 9.43. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
- 8.35. kill (5)
+ 9.44. kill (5)
kill <msgno> [<msgno> ...] Remove or erase a message from the system
kill from <call> Remove all messages from a callsign
As a sysop you can kill any message on the system.
- 8.36. kill full (5)
+ 9.45. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
+ 9.46. kill/expunge (6)
+
+ kill/expunge <msgno> [<msgno>..]Expunge a message
+
+
+ Deleting a message using the normal KILL commands only marks that
+ message for deletion. The actual deletion only happens later (usually
+ two days later).
+
+ The KILL EXPUNGE command causes the message to be truly deleted more
+ or less immediately.
+
+ It otherwise is used in the same way as the KILL command.
- 8.37. links (0)
+ 9.47. links (0)
links Show which nodes are physically connected
- 8.38. load/aliases (9)
+ 9.48. load/aliases (9)
load/aliases Reload the command alias table
running in order for the changes to take effect.
- 8.39. load/badmsg (9)
+ 9.49. load/badmsg (9)
load/badmsg Reload the bad message table
deleted on receipt.
- 8.40. load/bands (9)
+ 9.50. load/badwords (9)
+
+ load/badwords Reload the bad words table
+
+
+ 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.
+
+
+ 9.51. load/bands (9)
load/bands Reload the band limits table
whilst the cluster is running.
- 8.41. load/cmd_cache (9)
+ 9.52. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
delete a command in the local_cmd tree and want to use the normal one
again. Execute this command to reset everything back to the state it
was just after a cluster restart.
-
-
- 8.42. load/forward (9)
+ 9.53. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 8.43. load/messages (9)
+ 9.54. 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
cluster session by executing this command. You need to do this if get
unknown message 'xxxx' in lang 'en'
- 8.44. load/prefixes (9)
+ 9.55. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 8.45. merge (5)
+ 9.56. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 8.46. msg (9)
+ 9.57. msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+
+
+
+
+
+
+
+
+
+
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
STAT/MSG <msgno>
-
This will display more information on the message than DIR does.
- 8.47. pc (8)
+ 9.58. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
pc G1TLH Try doing that properly!!!
- 8.48. ping (1)
+ 9.59. ping (1)
ping <node> Check the link quality between nodes
- 8.49. rcmd (1)
+ 9.60. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
Cluster node that is connected to the system.
+
Whether you get any output is dependant on a) whether the other system
knows that the node callsign of this cluster is in fact a node b)
whether the other system is allowing RCMDs from this node and c)
whether you have permission to send this command at all.
- 8.50. read (0)
+ 9.61. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 8.51. read (extended for sysops) (5)
+ 9.62. read (extended for sysops) (5)
read <msgno> Read a message on the system
-
As a sysop you may read any message on the system
- 8.52. reject/announce
+ 9.63. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
but this probably for advanced users...
- 8.53. reject/announce (extended for sysops) (8)
+ 9.64. reject/announce (extended for sysops) (8)
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
- 8.54. reject/route (8)
+ 9.65. reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
routing
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
- 8.55. reject/spots (0)
+ 9.66. 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
+
You can use the tag 'all' to reject everything eg:
but this probably for advanced users...
- 8.56. reject/spots (extended for sysops) (8)
+ 9.67. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
+ reject/spot db0sue-7 1 by_zone 14,15,16
+ reject/spot node_default all
+ set/hops node_default 10
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
+ reject/spot user_default by G,M,2
- 8.57. reject/wcy (0)
+ 9.68. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
See HELP FILTER for information.
- 8.58. reject/wcy (extended for sysops) (8)
+
+ 9.69. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 8.59. reject/wwv (0)
+ 9.70. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
See HELP FILTER for information.
- 8.60. reject/wwv (extended for sysops) (8)
+ 9.71. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
-
-
-
-
- 8.61. reply (0)
+ 9.72. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
-
- 8.62. send (0)
+ 9.73. send (0)
send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
is an alias for SEND PRIVATE
- 8.63. set/address (0)
+ 9.74. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 8.64. set/announce (0)
+ 9.75. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
-
- 8.65. set/arcluster (5)
+ 9.76. set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 8.66. set/baddx (8)
+ 9.77. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
-
Setting a word as 'baddx' will prevent spots with that word in the
callsign field of a DX spot from going any further. They will not be
displayed and they will not be sent onto other nodes.
- 8.67. set/badnode (6)
+ 9.78. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 8.68. set/badspotter (8)
+ 9.79. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
FILTERing.
- 8.69. set/beep (0)
+ 9.80. set/badword (8)
- set/beep Add beeps to terminal messages
+ set/badword <word> Stop things with this word being propogated
+
+
+ Setting a word as a 'badword' will prevent things like spots,
+ announces or talks with this word in the the text part from going any
+ further. They will not be displayed and they will not be sent onto
+ other nodes.
+ The word must be written in full, no wild cards are allowed eg:-
+
+ set/badword annihilate annihilated annihilation
+
+ will stop anything with these words in the text.
+
+ unset/badword annihilated
+
+ will allow text with this word again.
+
+
+
+ 9.81. set/beep (0)
+
+ set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 8.70. set/bbs (5)
+ 9.82. set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
- 8.71. set/clx (5)
+ 9.83. 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
- 8.72. set/debug (9)
+ 9.84. set/debug (9)
set/debug <name> Add a debug level to the debug set
You can remove a debug level with unset/debug <name>
- 8.73. set/dx (0)
+ 9.85. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
- 8.74. set/dxgrid (0)
+ 9.86. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 8.75. set/dxnet (5)
+ 9.87. set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 8.76. set/echo (0)
+ 9.88. set/echo (0)
set/echo Make the cluster echo your input
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 8.77. set/here (0)
+ 9.89. set/email (0)
+
+ set/email <email_address> Set email address(es) and forward your
+ personals
+
+
+ If any personal messages come in for your callsign then you can use
+ these commands to control whether they are forwarded onto your email
+ address. To enable the forwarding do something like:-
+
+ SET/EMAIL mike.tubby@somewhere.com
+
+ You can have more than one email address (each one separated by a
+ space). Emails are forwarded to all the email addresses you specify.
+
+ You can disable forwarding by:-
+
+ UNSET/EMAIL
+
+
+ 9.90. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
- 8.78. set/homenode (0)
+ 9.91. set/homenode (0)
set/homenode <node_call> Set your home cluster
- 8.79. set/hops (8)
+
+ 9.92. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
This command allows you to set up special hop counts for a node for
currently: announce, spots, wwv and wcy broadcasts.
-
-
-
eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
creates a filter and works in conjunction with the filter system.
- 8.80. set/isolate (9)
+ 9.93. set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
You can remove the isolation with the command unset/isolate.
- 8.81. set/language (0)
+ 9.94. set/language (0)
set/language <language> Set the language you wish to use
Currently the languages available are en (English) and nl (Dutch).
- 8.82. set/location (0)
+ 9.95. set/location (0)
set/location <lat and long> Set your latitude and longitude
- 8.83. set/sys_location (9)
+
+ 9.96. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
example:-
-
SET/LOCATION 52 22 N 0 57 E
- 8.84. set/logininfo (0)
+ 9.97. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 8.85. set/lockout (9)
+ 9.98. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 8.86. set/name (0)
+ 9.99. set/name (0)
set/name <your_name> Set your name
- 8.87. set/node (9)
+ 9.100. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
+ set/spider
+ set/dxnet
+ set/clx
+ set/arcluster
+
- set/spider
- set/dxnet
- set/clx
- set/arcluster
+ To see what your nodes are set to, use the show/nodes command.
- To see what your nodes are set to, use the show/nodes command.
- 8.88. set/obscount (9)
+ 9.101. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 8.89. set/page (0)
+ 9.102. set/page (0)
set/page <n> Set the number of lines per page
The setting is stored in your user profile.
+ 9.103. set/password (0)
- 8.90. set/password (9)
+ set/password Set your own password
+
+
+ This command only works for a 'telnet' user (currently). It will only
+ work if you have a password already set. This initial password can
+ only be set by the sysop.
+
+ When you execute this command it will ask you for your old password,
+ then ask you to type in your new password twice (to make sure you get
+ it right). You may or may not see the data echoed on the screen as you
+ type, depending on the type of telnet client you have.
+
+
+ 9.104. set/password (9)
set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The string
- can contain any characters but any spaces are removed (you can type in
- spaces - but they won't appear in the password). You can see the
- result with STAT/USER. The password is the usual 30 character baycom
- type password.
+ can contain any characters.
+
+ The way this field is used depends on context. If it is being used in
+ the SYSOP command context then you are offered 5 random numbers and
+ you have to supply the corresponding letters. This is now mainly for
+ ax25 connections.
+
+ If it is being used on incoming telnet connections then, if a password
+ is set or the:
+
+ set/var $main::passwdreq = 1
+
+ command is executed in the startup script, then a password prompt is
+ given after the normal 'login: ' prompt.
+ The command "unset/password" is provided to allow a sysop to remove a
+ users password completely in case a user forgets or loses their
+ password.
- 8.91. set/pinginterval (9)
+ 9.105. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 8.92. set/privilege (9)
+ 9.106. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
connection your privilege will automatically be set to 0.
- 8.93. set/spider (5)
+
+
+
+ 9.107. set/spider (5)
set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
Set the node_call as a DXSpider type node
- 8.94. set/sys_qra (9)
+ 9.108. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 8.95. set/qra (0)
+ 9.109. set/qra (0)
set/qra <locator> Set your QRA locator
- 8.96. set/qth (0)
+ 9.110. set/qth (0)
set/qth <your QTH> Set your QTH
- 8.97. set/talk (0)
+ 9.111. set/register (9)
+
+ set/register <call> Mark a user as registered
+
+
+ Registration is a concept that you can switch on by executing the
+
+ set/var $main::regreq = 1
+
+ command (usually in your startup file)
+
+ If a user is NOT registered then, firstly, instead of the normal motd
+ file (/spider/data/motd) being sent to the user at startup, the user
+ is sent the motd_nor file instead. Secondly, the non registered user
+ only has READ-ONLY access to the node. The non-registered user cannot
+ use DX, ANN etc.
+
+ The only exception to this is that a non-registered user can TALK or
+ SEND messages to the sysop.
+
+ To unset a user use the 'unset/register' command
+
+
+ 9.112. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 8.98. set/wcy (0)
+ 9.113. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 8.99. set/wwv (0)
+ 9.114. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
WWV messages with the unset/wwv command.
- 8.100. set/wx (0)
+ 9.115. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
-
-
-
- 8.101. show/baddx (1)
+ 9.116. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 8.102. show/badnode (6)
+ 9.117. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 8.103. show/badspotter (1)
+ 9.118. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 8.104. show/configuration (0)
+ 9.119. show/badword (1)
+
+ show/badword Show all the bad words in the system
+
+
+ Display all the bad words in the system, see SET/BADWORD for more
+ information.
+
+
+ 9.120. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 8.105. show/configuration/node (0)
+ 9.121. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 8.106. show/connect (1)
+ 9.122. show/connect (1)
show/connect Show all the active connections
the node. This command gives slightly more information than WHO.
- 8.107. show/date (0)
+ 9.123. 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.
- 8.108. show/debug (9)
+ 9.124. show/debug (9)
show/debug Show what levels of debug you are logging
The levels can be set with set/debug
- 8.109. show/dx (0)
+
+
+
+ 9.125. show/dx (0)
show/dx [options] interrogate the spot database
- 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
- 8.110. show/dxcc (0)
+
+
+ 9.126. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
- 8.111. show/files (0)
+ 9.127. sh/dxstats (0)
+
+ sh/dxstats Show the DX Statistics for last 31 days
+
+
+ Show the total DX spots for the last 31 days
+
+
+
+ 9.128. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
See also TYPE - to see the contents of a file.
-
- 8.112. show/filter (0)
+ 9.129. 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.
- 8.113. show/filter (extended for sysops) (5)
+ 9.130. show/filter (extended for sysops) (5)
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 8.114. show/hops (8)
+ 9.131. show/hfstats (0)
+
+ show/hfstats Show the HF DX Statistics for last 31 days
+
+
+ Show the HF DX spots breakdown by band for the last 31 days
+
+
+ 9.132. show/hftable (0)
+
+ show/hftable Show the HF DX Spotter Table for your country
+
+
+ Show the HF DX Spotter table for your country for the last 31 days
+
+
+ 9.133. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 8.115. show/isolate (1)
+ 9.134. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 8.116. show/lockout (9)
+ 9.135. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 8.117. show/log (8)
+ 9.136. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 8.118. show/moon (0)
+ 9.137. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
- 8.119. show/muf (0)
+ 9.138. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
SH/MUF W
+
+
+
produces:
indicating that you will have weak, fading circuits on top band and
80m but usable signals on 40m (about S3).
- inputing:-
+ inputting:-
terrible accurate, but it is included for completeness.
- 8.120. show/node (1)
+ 9.139. show/newconfiguration (0)
+
+ show/newconfiguration [<node>] Show all the nodes and users visible
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected.
+
+ This command produces essentially the same information as
+ SHOW/CONFIGURATION except that it shows all the duplication of any
+ routes that might be present It also uses a different format which may
+ not take up quite as much space if you don't have any loops.
+
+ BE WARNED: the list that is returned can be VERY long
+
+
+ 9.140. show/newconfiguration/node (0)
+
+ show/newconfiguration/node Show all the nodes connected locally
+
+
+ Show all the nodes connected to this node in the new format.
+
+
+ 9.141. show/node (1)
show/node [<node_call> ...] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 8.121. show/prefix (0)
+ 9.142. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
See also SHOW/DXCC
- 8.122. show/program (5)
+
+
+ 9.143. show/program (5)
show/program Show the locations of all the included program modules
from.
- 8.123. show/qra (0)
+ 9.144. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
SH/QRA IO92QL
SH/QRA JN06 IN73
-
-
-
The first example will show the distance and bearing to the locator
from yourself, the second example will calculate the distance and
bearing from the first locator to the second. You can use 4 or 6
- 8.124. show/qrz (0)
+ 9.145. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
- 8.125. show/route (0)
+ 9.146. show/registered (9)
+
+ show/registered [<prefix>[ Show the registered users
+
+
+ 9.147. show/route (0)
show/route <callsign> Show the route to <callsign>
- sh/route n2tly
+ sh/route n2tly
- 8.126. show/satellite (0)
+ 9.148. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
give information for the next three hours for every five minute
period.
+
You can alter the number of hours and the step size, within certain
limits.
- 8.127. show/sun (0)
+ 9.149. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
- 8.128. show/time (0)
+ 9.150. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 8.129. show/wcy (0)
+ 9.151. show/vhfstats (0)
+
+ show/vhfstats Show the VHF DX Statistics for last 31 days
+
+
+ Show the VHF DX spots breakdown by band for the last 31 days
+
+
+ 9.152. show/vhftable (0)
+
+ show/vhftable Show the VHF DX Spotter Table for your country
+
+ Show the VHF DX Spotter table for your country for the last 31 days
+
+
+ 9.153. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 8.130. show/wwv (0)
+ 9.154. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 8.131. shutdown (5)
+ 9.155. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 8.132. spoof (9)
+ 9.156. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
- 8.133. stat/db (5)
+ 9.157. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
-
-
- 8.134. stat/channel (5)
+ 9.158. stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
Only the fields that are defined (in perl term) will be displayed.
-
- 8.135. stat/msg (5)
+ 9.159. stat/msg (5)
stat/msg <msgno> Show the status of a message
displayed.
- 8.136. stat/route_node (5)
+ 9.160. stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
- 8.137. stat/route_user (5)
+ 9.161. stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
- 8.138. stat/user (5)
+ 9.162. stat/user (5)
stat/user <callsign> Show the full status of a user
Only the fields that are defined (in perl term) will be displayed.
- 8.139. sysop (0)
+ 9.163. sysop (0)
sysop Regain your privileges if you login remotely
-
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
case sensitive.
- 8.140. talk (0)
+ 9.164. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
To leave talk mode type:
+
+
/EX
- 8.141. type (0)
+
+
+
+ 9.165. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
content.
- 8.142. who (0)
+ 9.166. who (0)
who Show who is physically connected locally
what sort of connection they have
- 8.143. wx (0)
+ 9.167. wx (0)
wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users
extreme that may indicate enhanced conditions
- 8.144. wx (enhanced for sysops) (5)
+ 9.168. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
+
+
+
+
+
+
projects / spider.git / blobdiff