X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=3cdb45bde8dde09625d12fd18d842eec0623e182;hb=551887c98fa231f03aa2a1829e7ef00ca3e097b9;hp=d8078515dd125c5efae856265fa768b1e498f5d3;hpb=8e862ce4b386889bc91c34ec788df0bd1a062c6c;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index d8078515..3cdb45bd 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,7 @@ - The DXSpider Administration Manual v1.49 - Ian Maude, G0VGS, (ianmaude@btinternet.com) - December 2001 revision 1.2 + The DXSpider Administration Manual v1.50 + Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll, + K1XX, (k1xx@ptcnh.net) + July 2002 revision 0.1 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -61,7 +62,6 @@ - 1. Routing and Filtering @@ -116,184 +116,191 @@ 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) + 6.9 Connecting logging programs + + 7. Java Web applet + + 8. Security + + 8.1 Registration + 8.2 Passwords + + 9. CVS + + 9.1 CVS from a Linux platform + 9.2 CVS from a Windows platform + + 10. The DXSpider command set + + 10.1 accept/announce (0) + 10.2 accept/announce (extended for sysops) (8) + 10.3 accept/route (8) + 10.4 accept/spots (0) + 10.5 accept/spots (extended for sysops) (8) + 10.6 accept/wcy (0) + 10.7 accept/wcy (extended for sysops) (8) + 10.8 accept/wwv (0) + 10.9 accept/wwv (extended for sysops) (8) + 10.10 announce (0) + 10.11 announce full (0) + 10.12 announce sysop (5) + 10.13 apropos (0) + 10.14 bye (0) + 10.15 catchup (5) + 10.16 clear/announce (8) + 10.17 clear/route (8) + 10.18 clear/spots (0) + 10.19 clear/spots (extended for sysops) (8) + 10.20 clear/wcy (0) + 10.21 clear/wcy (extended for sysops) (8) + 10.22 clear/wwv (0) + 10.23 clear/wwv (extended for sysops) (8) + 10.24 connect (5) + 10.25 dbavail (0) + 10.26 dbcreate (9) + 10.27 dbimport (9) + 10.28 dbremove (9) + 10.29 dbshow (0) + 10.30 debug (9) + 10.31 delete/user (9) + 10.32 demonstrate (9) + 10.33 directory (0) + 10.34 directory (extended for sysops) (5) + 10.35 disconnect (8) + 10.36 dx (0) + 10.37 export (9) + 10.38 export_users (9) + 10.39 filtering (0) + 10.40 forward/latlong (8) + 10.41 forward/opername (1) + 10.42 help (0) + 10.43 init (5) + 10.44 kill (0) + 10.45 kill (5) + 10.46 kill full (5) + 10.47 kill/expunge (6) + 10.48 links (0) + 10.49 load/aliases (9) + 10.50 load/badmsg (9) + 10.51 load/badwords (9) + 10.52 load/bands (9) + 10.53 load/cmd_cache (9) + 10.54 load/forward (9) + 10.55 load/messages (9) + 10.56 load/prefixes (9) + 10.57 merge (5) + 10.58 msg (9) + 10.59 pc (8) + 10.60 ping (1) + 10.61 rcmd (1) + 10.62 read (0) + 10.63 read (extended for sysops) (5) + 10.64 reject/announce + 10.65 reject/announce (extended for sysops) (8) + 10.66 reject/route (8) + 10.67 reject/spots (0) + 10.68 reject/spots (extended for sysops) (8) + 10.69 reject/wcy (0) + 10.70 reject/wcy (extended for sysops) (8) + 10.71 reject/wwv (0) + 10.72 reject/wwv (extended for sysops) (8) + 10.73 reply (0) + 10.74 send (0) + 10.75 set/address (0) + 10.76 set/announce (0) + 10.77 set/arcluster (5) + 10.78 set/baddx (8) + 10.79 set/badnode (6) + 10.80 set/badspotter (8) + 10.81 set/badword (8) + 10.82 set/beep (0) + 10.83 set/bbs (5) + 10.84 set/clx (5) + 10.85 set/debug (9) + 10.86 set/dx (0) + 10.87 set/dxgrid (0) + 10.88 set/dxnet (5) + 10.89 set/echo (0) + 10.90 set/email (0) + 10.91 set/here (0) + 10.92 set/homenode (0) + 10.93 set/hops (8) + 10.94 set/isolate (9) + 10.95 set/language (0) + 10.96 set/location (0) + 10.97 set/sys_location (9) + 10.98 set/logininfo (0) + 10.99 set/lockout (9) + 10.100 set/name (0) + 10.101 set/node (9) + 10.102 set/obscount (9) + 10.103 set/page (0) + 10.104 set/password (0) + 10.105 set/password (9) + 10.106 set/pinginterval (9) + 10.107 set/privilege (9) + 10.108 set/spider (5) + 10.109 set/sys_qra (9) + 10.110 set/qra (0) + 10.111 set/qth (0) + 10.112 set/register (9) + 10.113 set/talk (0) + 10.114 set/wcy (0) + 10.115 set/wwv (0) + 10.116 set/wx (0) + 10.117 show/baddx (1) + 10.118 show/badnode (6) + 10.119 show/badspotter (1) + 10.120 show/badword (1) + 10.121 show/configuration (0) + 10.122 show/configuration/node (0) + 10.123 show/connect (1) + 10.124 show/date (0) + 10.125 show/debug (9) + 10.126 show/dx (0) + 10.127 show/dxcc (0) + 10.128 sh/dxstats (0) + 10.129 show/files (0) + 10.130 show/filter (0) + 10.131 show/filter (extended for sysops) (5) + 10.132 show/hfstats (0) + 10.133 show/hftable (0) + 10.134 show/hops (8) + 10.135 show/isolate (1) + 10.136 show/lockout (9) + 10.137 show/log (8) + 10.138 show/moon (0) + 10.139 show/muf (0) + 10.140 show/newconfiguration (0) + 10.141 show/newconfiguration/node (0) + 10.142 show/node (1) + 10.143 show/prefix (0) + 10.144 show/program (5) + 10.145 show/qra (0) + 10.146 show/qrz (0) + 10.147 show/registered (9) + 10.148 show/route (0) + 10.149 show/satellite (0) + 10.150 show/sun (0) + 10.151 show/time (0) + 10.152 show/vhfstats (0) + 10.153 show/vhftable (0) + 10.154 show/wcy (0) + 10.155 show/wwv (0) + 10.156 shutdown (5) + 10.157 spoof (9) + 10.158 stat/db (5) + 10.159 stat/channel (5) + 10.160 stat/msg (5) + 10.161 stat/route_node (5) + 10.162 stat/route_user (5) + 10.163 stat/user (5) + 10.164 sysop (0) + 10.165 talk (0) + 10.166 type (0) + 10.167 who (0) + 10.168 wx (0) + 10.169 wx (enhanced for sysops) (5) ______________________________________________________________________ @@ -321,8 +328,6 @@ called passive mode. A more detailed explanation of isolation is given further below. This system is still available and, for simple networks, is probably all that you need. - - The new functionality introduced in version 1.48 allows filtering the node and user protocol frames on a "per interface" basis. We call this route filtering. This is used instead of isolation. @@ -389,11 +394,10 @@ "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. + The generic commands are:- - The generic commands are:- - reject/route node_default or @@ -456,8 +460,6 @@ rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38 - - What this does is accept node and user information for our national network from nodes that are in our national network, but rejects such information from anyone else. Although it doesn't explicitly say so, @@ -524,8 +526,6 @@ acc/route gb7baa input all - - or restricting it quite a lot, in fact making it very nearly like an isolated node, like this:- @@ -963,7 +963,7 @@ The set/hops command overrides any hops that you have set otherwise. - You can set what hops have been set using the show/hops command. + You can show what hops have been set using the show/hops command. 1.12. Isolating networks @@ -1233,6 +1233,9 @@ To force the cluster to reread the file use load/forward + NB: If a user tries to send mail to a bulletin address that does not + exist in this file, they will get an error. + 3.4. The msg command @@ -1249,9 +1252,6 @@ - - - MSG TO - change TO callsign to MSG FRom - change FROM callsign to MSG PRrivate - set private flag @@ -1364,7 +1364,7 @@ # startup script example # # set maximum no of spots allowed to 100 - # set/var $Spot::maxspots = 1 + # set/var $Spot::maxspots = 100 # # Set registration on # set/var $main::reqreg = 1 @@ -1378,12 +1378,25 @@ As usual, any text behind a # is treated as a comment and not read. + To use this file, simply rename it from startup.issue to startup. In + our example above there are three options. The first option is the + amount of spots that a user can request with the sh/dx command. + Normally the default is to give 10 spots unless the user specifies + more. Without this line enabled, the maximum a user can request is + 100 spots. Depending on your link quality you may wish to enable more + or less by specifying the number. + + + The other 2 options are dealt with more fully in the security section. + Secondly, it is used to store the login scripts for users and nodes. Currently this can only be done by the sysop but it is envisaged that eventually users will be able to set their own. An example is included in the distibution but here is a further example. + + # # G0FYD # @@ -1437,8 +1450,6 @@ dbcreate - - 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. @@ -1503,14 +1514,14 @@ - dbavail - DB Name Location Chain - qsl Local - buck GB7ADX - hftest GB7DXM - G0VGS de GB7MBC 3-Feb-2001 1925Z > + dbavail + DB Name Location Chain + qsl Local + buck GB7ADX + hftest GB7DXM + G0VGS de GB7MBC 3-Feb-2001 1925Z > @@ -1571,8 +1582,6 @@ /spider/data called motd and edit it to say whatever you want. It is purely a text file and will be sent automatically to anyone logging in to the cluster. - - 6.2. MOTD_NOR This message of the day file lives in the same directory as the @@ -1580,8 +1589,6 @@ 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 @@ -1641,13 +1648,12 @@ An example would look like this .... - - sh/files bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z + You can see that in the files area (basically the packclus directory) there is a file called news and a directory called bulletin. You can also see that dates they were created. In the case of the file news, @@ -1707,292 +1713,268 @@ + The page length will of course depend on what you have it set to! 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 - something like this ... + You will find a file in /spider/cmd/ called Aliases. This is the file + that controls what a user gets when issuing a command. It is also + possible to create your own aliases for databases and files you create + locally. + You should not alter the original file in /spider/cmd/ but create a + new file with the same name in /spider/local_cmd. This means that any + new Aliases files that is downloaded will not overwrite your self + created Aliases and also that you do not override any new Aliases with + your copy in /spider/local_cmd/. You must remember that any files you + store in /spider/local/ or /spider/local_cmd override the originals if + the same lines are used in both files. + The best way of dealing with all this then is to only put your own + locally created Aliases in the copy in /spider/local_cmd. The example + below is currently in use at GB7MBC. + # + # Local Aliases File + # + package CmdAlias; + %alias = ( + 'n' => [ + '^news$', 'type news', 'type', + ], + 's' => [ + '^sh\w*/buck$', 'show/qrz', 'show', + '^sh\w*/hftest$', 'dbshow hftest', 'dbshow', + '^sh\w*/qsl$', 'dbshow qsl', 'dbshow', + '^sh\w*/vhf$', 'dbshow vhf', 'dbshow', + '^sh\w*/vhftest$', 'dbshow vhftest', 'dbshow', + ], + ) + Each alphabetical section should be preceded by the initial letter and + the section should be wrapped in square brackets as you can see. The + syntax is straightforward. The first section on each line is the new + command that will be allowed once the alias is included. The second + section is the command it is replacing and the last section is the + actual command that is being used. + The eagle-eyed amongst you will have noticed that in the first + section, the new alias command has a '^' at the start and a '$' at the + end. Basically these force a perfect match on the alias. The '^' + says match the beginning exactly and the with similar commands. + I have 3 different types of alias in this file. At the top is an + alias for 'news'. This is a file I have created in the + /spider/packclus/ directory where I can inform users of new + developments or points of interest. In it's initial form a user would + have to use the command type news. The alias allows them to simply + type news to get the info. Second is an alias for the show/qrz + command so that those users used to the original show/buck command in + AK1A will not get an error, and the rest of the lines are for locally + created databases so that a user can type show/hftest instead of + having to use the command dbshow hftest which is not as intuitive. + This file is just an example and you should edit it to your own + requirements. Once created, simply issue the command load/alias at + the cluster prompt as the sysop user and the aliases should be + available. + 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 + 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. + 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. + 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 + would export message number 5467 as a file called keps.in in the + /spider/perl directory. + Now login to a VT as sysop and cd /spider/perl. There is a command in + the perl directory called convkeps.pl. All we need to do now is + convert the file like so ... + ./convkeps.pl keps.in + Now go back to the cluster and issue the command ... + load/keps + That is it! the kepler data has been updated. + 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. + 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. + 6.9. Connecting logging programs + There appear to be very few logging programs out there that support + telnet especially the popular ones like LogEQF, Turbolog etc. This + can make it difficult to connect to your own cluster! The way to do + it is to make the logging program think it has a TNC attached to a com + port on the logging PC and 'push' a linux login out to it. This is + achieved very simply by the use of agetty. + All that is required is to add a line in /etc/inittab to have the + client ready for a connection on the com port of your choice. + Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1 + for com2 etc. - #!/usr/bin/perl - # provide some standard aliases for commands for terminally - # helpless ak1a user (helpless in the sense that they never - # read nor understand help files) - # This file is automagically reloaded if its modification time is - # later than the one stored in CmdAlias.pm + c4:2345:respawn:/sbin/agetty -L 9600 ttyS1 - # PLEASE make this file consistant with reality! (the patterns MUST - # match the filenames!) - # Don't alter this file, copy it into the local_cmd tree and modify it. - # This file will be replaced everytime I issue a new release. - # You only need to put aliases in here for commands that don't work as - # you desire naturally, e.g sh/dx on its own just works as you expect - # so you need not add it as an alias. + Add this after the standard runlevel lines in /etc/inittab. The above + line works on ttyS1 (com2). Now as root, issue the command telinit q + and it should be ready for connection. All that is required is a 3 + wire serial lead (tx, rx and signal ground). Tell you logging program + to use 8n1 at 9600 baud and you should see a Linux login prompt. + Login as normal and then telnet from there to the cluster. - package CmdAlias; - %alias = ( - '?' => [ - '^\?', 'apropos', 'apropos', - ], - 'a' => [ - '^ann.*/full', 'announce full', 'announce', - '^ann.*/sysop', 'announce sysop', 'announce', - '^ann.*/(.*)$', 'announce $1', 'announce', - ], - 'b' => [ - ], - 'c' => [ - ], - 'd' => [ - '^del', 'kill', 'kill', - '^del\w*/fu', 'kill full', 'kill', - '^di\w*/a\w*', 'directory all', 'directory', - '^di\w*/b\w*', 'directory bulletins', 'directory', - '^di\w*/n\w*', 'directory new', 'directory', - '^di\w*/o\w*', 'directory own', 'directory', - '^di\w*/s\w*', 'directory subject', 'directory', - '^di\w*/t\w*', 'directory to', 'directory', - '^di\w*/f\w*', 'directory from', 'directory', - '^di\w*/(\d+)', 'directory $1', 'directory', - ], - 'e' => [ - ], - 'f' => [ - ], - 'g' => [ - ], - 'h' => [ - ], - 'i' => [ - ], - 'j' => [ - ], - 'k' => [ - ], - 'l' => [ - '^l$', 'directory', 'directory', - '^ll$', 'directory', 'directory', - '^ll/(\d+)', 'directory $1', 'directory', - ], - 'm' => [ - ], - 'n' => [ - '^news', 'type news', 'type', - ], - 'o' => [ - ], - 'p' => [ - ], - 'q' => [ - '^q', 'bye', 'bye', - ], - 'r' => [ - '^r$', 'read', 'read', - '^rcmd/(\S+)', 'rcmd $1', 'rcmd', - ], - 's' => [ - '^s/p$', 'send', 'send', - '^sb$', 'send noprivate', 'send', - '^set/home$', 'set/homenode', 'set/homenode', - '^set/nobe', 'unset/beep', 'unset/beep', - '^set/nohe', 'unset/here', 'unset/here', - '^set/noan', 'unset/announce', 'unset/announce', - '^set/nodx', 'unset/dx', 'unset/dx', - '^set/nota', 'unset/talk', 'unset/talk', - '^set/noww', 'unset/wwv', 'unset/wwv', - '^set/nowx', 'unset/wx', 'unset/wx', - '^sh$', 'show', 'show', - '^sh\w*/buck', 'dbshow buck', 'dbshow', - '^sh\w*/bu', 'show/files bulletins', 'show/files', - '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration', - '^sh\w*/c$', 'show/configuration', 'show/configuration', - '^sh\w*/com', 'dbavail', 'dbavail', - '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx', - '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx', - '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx', - '^sh\w*/email', 'dbshow email', 'dbshow', - '^sh\w*/hftest', 'dbshow hftest', 'dbshow', - '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow', - '^sh\w*/qsl', 'dbshow qsl', 'dbshow', - '^sh\w*/tnc', 'who', 'who', - '^sh\w*/up', 'show/cluster', 'show/cluster', - '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv', - '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv', - '^sp$', 'send', 'send', - - ], - 't' => [ - '^ta$', 'talk', 'talk', - '^t$', 'talk', 'talk', - ], - 'u' => [ - ], - 'v' => [ - ], - 'w' => [ - '^wx/full', 'wx full', 'wx', - '^wx/sysop', 'wx sysop', 'wx', - ], - 'x' => [ - ], - 'y' => [ - ], - 'z' => [ - ], - ) + 7. Java Web applet + In the spider tree will be a directory spider-web. This is a neat + little java web applet that can be run from a website. The applet + must run on the same machine as the cluster. The included README file + is shown below. + I should comment here that the applet is precompiled, that is, ready + to go. It was compiled using JDK1.3.1. If your version is earlier + than this then it may not work. Should that be the case you need to + recompile or update your JDK. To recompile do the following ... - You can create aliases for commands at will. Beware though, these may - not always turn out as you think. Care is needed and you need to test - the results once you have set an alias. + cd /spider/spider-web + rm *.class + /usr/bin/javac spiderclient.java - 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 - 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. + I have used /usr/bin/javac as an example, your path to javac may be + different. - 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. - 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 - - - - - - would export message number 5467 as a file called keps.in in the - /spider/perl directory. + Spider-WEB v0.6b - 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 ... + Completely based on a clx web client written in Java by dl6dbh + (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz) + The webserver has to run on the same machine as your DxSpider software! + It is assumed that you have Java installed. You need JDK1.3.1 at least. - ./convkeps.pl keps.in + Installation instructions (Performed as root): + Put all the files in the spider-web directory into a newly created directory + under the DocumentRoot of your websever for instance 'client'. In my case + this is: /home/httpd/html/client/ although ymmv. For Suse the correct + path should be /usr/local/httpd/htdocs/client/ for example. + Move spider.cgi to the cgi-bin directory of your webserver, in my case that is + /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be + /usr/local/httpd/cgi-bin/ for example. + Change the permissions of the files to ensure they are correct, obviously you + will need to use the correct path the the files according to your system: + chmod 755 /home/httpd/html/cgi-bin/spider.cgi + chmod -R 755 /home/httpd/html/client/ - Now go back to the cluster and issue the command ... + By default the spider.cgi script should pick up your hostname (As long as this + is set correctly). If it does not or your hostname differs from the name that + you attach to the public address that you are using, then edit spider.cgi : + # Uncomment and set the hostname manually here if the above fails. + # $HOSTNAME = "gb7mbc.spoo.org" ; + $PORT = "8000" ; - load/keps + telnet (see Listeners.pm) + NOTE: If you can start the console but cannot connect to the cluster from it, + then it is possible that the machine you are on cannot resolve the hostname of + your cluster machine. If this is the case, you need to set your hostname + manually as above. + You also need to set the $NODECALL variable. This prints the name of your + choosing (probably your cluster callsign) on the html page. + You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi - That is it! the kepler data has been updated. - 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. - 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. - - - 7. Security + 8. Security From version 1.49 DXSpider has some additional security features. These are not by any means meant to be exhaustive, however they do @@ -2001,7 +1983,7 @@ security. - 7.1. Registration + 8.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 @@ -2043,8 +2025,7 @@ registered users, use the command show/register. - - 7.2. Passwords + 8.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 @@ -2062,6 +2043,7 @@ + at the cluster prompt. This can also be added to the /spider/scripts/startup file as above to make the change permanent. @@ -2085,12 +2067,15 @@ - 8. CVS + 9. CVS + + 9.1. CVS from a Linux platform CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your DXSpider installation to the latest sources by using a few simple - commands. + commands. A graphical interface to CVS for Windows is explained in + the next section. Please be aware that if you update your system using CVS, it is @@ -2110,6 +2095,7 @@ CVS repository and then update your Spider source. There are several steps which are listed below ... + First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... @@ -2188,8 +2174,10 @@ - cd /spider - cvs -z3 update -d + + + cd /spider + cvs -z3 update -d @@ -2203,16 +2191,142 @@ You will find any changes documented in the /spider/Changes file. - 9. The DXSpider command set + 9.2. CVS from a Windows platform + + After the initial setup, an update to your DXSpider software is no + more than a couple of clicks away. This section is intended to + explain and illustrate the use of the WinCVS application to update + your DXSpider software. The current stable version of WinCVS is Ver. + 1.2. You can get this software at: + + http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip + + Pick your download mirror and then install WinCVS after the download + is complete. + + In this next section I have included a series of links to .jpg files + to take advantage of the picture and 1000 words equivalency. The .jpg + files are in the C:\spider\html directory. If someone using a Linux + system is reading this section from boredom, the files are in + /home/sysop/spider/html. One aside, a Linux user can also get a copy + of gcvs and do your updates graphically as opposed to from the command + line. The following descriptions are almost identical between WinCvs + and gcvs. The following screen shots have duplicate links, depending + upon whether you are viewing this information under the Windows or + Linux operating system. + + When WinCVS is installed, running, and you are connected to the + internet, the initial screen looks like: + + initial.jpg + + If you want, you can also look at these .jpg files with another viewer + that might provide some better clarity to the image. On the left is + the directory tree for your hard disk. Notice that the spider + directory has a gray highlight. + + To start configuring WinCVS, click on Admin at the top of the screen + and then Preferences. This should get you: + + pref-gen.jpg + + In the top line for CVSROOT, enter: + + + anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login + + + + + and select + + + + "passwd" file on the cvs server + + + + + for Authentication on the General tab. + + Next, move to the right to the Ports tab. + + pref-ports.jpg + + In here, check the box on the second line down for the "pserver" port. + Enter a port number of 2401. + + Finally, go to the WinCvs tab all the way to the right. + + pref-wincvs.jpg + + Enter Notepad as the viewer to open files. For the HOME folder, put + "C:\spider" and click OK because the configuration is now complete. + + You are now ready to upgrade your copy of DXSpider. Click on the + greyed Spider folder shown in the directory tree on the left of the + WinCVS display. Two things should happen. The Spider folder will be + selected and the greyed-out arrow located just below the word Query in + the top line will turn to solid green. + + For anyone using gcvs under Linux, the green arrow is located on the + extreme left of the display, under the word File. A gcvs screen looks + like: + + gcvs.jpg + + Click on the now green arrow to start the download process. An Update + Settings box will be displayed to which you can simply say OK. + + update-OK.jpg + + For future reference, the Update Settings box is the place where you + can enter information to revert to a prior version of DXSpider. + Information on reverting to a Before Date is contained in the WinCVS + manual. + + After a short period of time, a series of file names will scroll by in + the lower pane of the WinCVS window. Eventually you should see + + + *****CVS exited normally with code 0***** + + + + + appear in the lower pane. You're done. The updated files are in + place ready for you to stop and then restart your DXSpider. After the + restart, you're running with the latest version of DXSpider. + + completed.jpg + + To paraphrase from the CVS section... Now the magic part! From now on + when you want to update, simply connect to the Internet and start + WinCVS. + + + + + + Click on the greyed-out Spider directory in the left screen + Click on the green down arrow + Click OK on the Update Settings dialog box + Restart your Spider software + + + + + + 10. The DXSpider command set Below is a complete list of commands available from the cluster prompt. Most maintenance tasks are automatic but there are some commands that are useful for a sysop. These are listed below in alphabetical order. The number in brackets following the command name - is the permissions level needed to use the command. + is the permissions level needed to use the command - 9.1. accept/announce (0) + 10.1. accept/announce (0) accept/announce [0-9] Set an accept filter line for announce @@ -2242,6 +2356,8 @@ dest eg: 6MUK,WDX (distros) + + some examples:- @@ -2257,7 +2373,8 @@ - acc/ann by G,M,2 + + acc/ann by G,M,2 @@ -2275,7 +2392,7 @@ but this probably for advanced users... - 9.2. accept/announce (extended for sysops) (8) + 10.2. accept/announce (extended for sysops) (8) accept/announce [input] [0-9] Announce filter sysop version @@ -2294,7 +2411,7 @@ - 9.3. accept/route (8) + 10.3. accept/route (8) accept/route [0-9] Set an 'accept' filter line for routing @@ -2308,6 +2425,7 @@ 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:- @@ -2322,9 +2440,6 @@ origin_zone - - - some examples:- @@ -2346,7 +2461,7 @@ - 9.4. accept/spots (0) + 10.4. accept/spots (0) accept/spots [0-9] Set an accept filter line for spots @@ -2358,6 +2473,10 @@ passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on. + Please read the following section carefully. Though it looks similar, + reformatting, corrections, and hopefully clarifications have been + added. + You can use any of the following things in this line:- @@ -2374,19 +2493,66 @@ - freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m - on same as 'freq' - call eg: G,PA,HB9 - info eg: iota or qsl - by - call_dxcc eg: 61,62 (from eg: sh/pre G) + + + + + + + + + + + + + + Filters for the station being spotted: + call + call G --> G1AAA, GJ2BBB, GU3CCC, etc will be spotted + call K --> K1XX, K1XXX will be spotted + W1XX, W1XXX will NOT be spotted + call PA --> PA3EZL will be spotted + PB2FG will NOT be spotted + + call_dxcc + call_dxcc G --> G1AAA will be spotted + GU1AAA will NOT be spotted (different country) + call_dxcc K --> K1XX, W1XX will be spotted (same country) + call_dxcc 139 --> PA3EZL and PB2FG will be spotted + call_itu call_zone - by_dxcc + + Filters for the callsign of the station doing the spotting: + by + by G --> spots from G1AAA, GJ2BBB, GU3CCC, etc will be spotted + by K --> spots from K1XX, K1XXX will be spotted + spots from W1XX, W1XXX will NOT be spotted + + by_dxcc + by_dxcc G --> spots from G1AAA will be spotted + spots from GU1AAA will NOT be spotted (different + country) + by_dxcc K --> spots from K1XX, W1XX will be spotted (same country) + by_dxcc 139 --> spots from PA3EZL or PB2FG will be spotted + by_itu by_zone - origin + + Filters for the callsign of the "node" doing the spotting: + origin + origin K --> spots from a node starting with K will be spotted + spots from a node starting with KK will NOT be spotted + spots from a node starting with W will NOT be spotted + + Filters for the callsign of the connected node or user (channel) doing the spotting: channel + channel W1HR --> spots from the connected node W1HR will be spotted + channel K1QX --> spots from the connected user K1QX will be spotted + + info eg: iota or qsl + freq eg: 0/30000 or hf or hf/cw or 6m,4m,2m + on same as 'freq' @@ -2406,8 +2572,6 @@ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - You can use the tag 'all' to accept everything, eg: @@ -2420,7 +2584,7 @@ but this probably for advanced users... - 9.5. accept/spots (extended for sysops) (8) + 10.5. accept/spots (extended for sysops) (8) accept/spots [input] [0-9] Spot filter sysop version @@ -2440,7 +2604,7 @@ - 9.6. accept/wcy (0) + 10.6. accept/wcy (0) accept/wcy [0-9] set an accept WCY filter @@ -2473,7 +2637,8 @@ See HELP FILTER for information. - 9.7. accept/wcy (extended for sysops) (8) + + 10.7. accept/wcy (extended for sysops) (8) accept/wcy [input] [0-9] WCY filter sysop version @@ -2490,7 +2655,7 @@ - 9.8. accept/wwv (0) + 10.8. accept/wwv (0) accept/wwv [0-9] Set an accept WWV filter @@ -2500,21 +2665,15 @@ - - - - - - - by eg: G,M,2 - origin - origin_dxcc eg: 61,62 (from eg: sh/pre G) - origin_itu - origin_zone - by_dxcc - by_itu - by_zone - channel + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + by_dxcc + by_itu + by_zone + channel @@ -2534,7 +2693,7 @@ See HELP FILTER for information. - 9.9. accept/wwv (extended for sysops) (8) + 10.9. accept/wwv (extended for sysops) (8) accept/wwv [input] [0-9] WWV filter sysop version @@ -2544,17 +2703,18 @@ - accept/wwv db0sue-7 1 by_zone 4 - accept/wwv node_default all - set/hops node_default 10 - accept/wwv user_default by W,K + accept/wwv db0sue-7 1 by_zone 4 + accept/wwv node_default all + set/hops node_default 10 + accept/wwv user_default by W,K - 9.10. announce (0) + + 10.10. announce (0) announce Send an announcement to local users @@ -2565,14 +2725,17 @@ sysop will override set/noannounce. - 9.11. announce full (0) + 10.11. announce full (0) announce full Send an announcement cluster wide This command will send your announcement across the whole cluster network. - 9.12. announce sysop (5) + + + + 10.12. announce sysop (5) announce sysop @@ -2580,7 +2743,7 @@ Send an announcement to Sysops only - 9.13. apropos (0) + 10.13. apropos (0) apropos Search the help database @@ -2589,7 +2752,7 @@ print the names of all the commands that may be relevant. - 9.14. bye (0) + 10.14. bye (0) bye Exit from the cluster @@ -2597,7 +2760,7 @@ This will disconnect you from the cluster - 9.15. catchup (5) + 10.15. catchup (5) catchup All|[ ...] Mark a message as sent @@ -2632,7 +2795,7 @@ Order is not important. - 9.16. clear/announce (8) + 10.16. clear/announce (8) clear/announce [input] [0-9|all] Clear an announce filter line @@ -2642,7 +2805,7 @@ node_default or user_default. - 9.17. clear/route (8) + 10.17. clear/route (8) clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line @@ -2656,7 +2819,7 @@ node_default or user_default. - 9.18. clear/spots (0) + 10.18. clear/spots (0) clear/spots [1|all] Clear a spot filter line @@ -2673,7 +2836,6 @@ - and you say:- @@ -2704,7 +2866,7 @@ the filter will be completely removed. - 9.19. clear/spots (extended for sysops) (8) + 10.19. clear/spots (extended for sysops) (8) clear/spots [input] [0-9|all] Clear a spot filter line @@ -2713,7 +2875,7 @@ node_default or user_default. - 9.20. clear/wcy (0) + 10.20. clear/wcy (0) clear/wcy [1|all] Clear a WCY filter line @@ -2724,7 +2886,7 @@ see CLEAR/SPOTS for a more detailed explanation. - 9.21. clear/wcy (extended for sysops) (8) + 10.21. clear/wcy (extended for sysops) (8) clear/wcy [input] [0-9|all] Clear a WCY filter line @@ -2733,18 +2895,17 @@ node_default or user_default. - 9.22. clear/wwv (0) + 10.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) + 10.23. clear/wwv (extended for sysops) (8) clear/wwv [input] [0-9|all] Clear a WWV filter line @@ -2753,7 +2914,7 @@ node_default or user_default. - 9.24. connect (5) + 10.24. connect (5) connect Start a connection to another DX Cluster @@ -2765,7 +2926,7 @@ cluster . - 9.25. dbavail (0) + 10.25. dbavail (0) dbavail Show a list of all the databases in the system @@ -2774,7 +2935,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. - 9.26. dbcreate (9) + 10.26. dbcreate (9) dbcreate Create a database entry dbcreate chain [..] Create a chained database @@ -2835,7 +2996,6 @@ to allow - SH/BUCK g1tlh to work as they may be used to. @@ -2844,7 +3004,7 @@ databases. See DBSHOW for generic database enquiry - 9.27. dbimport (9) + 10.27. dbimport (9) dbimport Import AK1A data into a database @@ -2859,7 +3019,7 @@ oblast database held locally. - 9.28. dbremove (9) + 10.28. dbremove (9) dbremove Delete a database @@ -2873,6 +3033,7 @@ DBREMOVE oblast + will remove the oblast database from the system and it will also remove the associated datafile. @@ -2883,7 +3044,7 @@ You have been warned. - 9.29. dbshow (0) + 10.29. dbshow (0) dbshow Display an entry, if it exists, in a database @@ -2902,6 +3063,9 @@ but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with: + + + DBSHOW buck G1TLH @@ -2909,7 +3073,7 @@ - 9.30. debug (9) + 10.30. debug (9) debug Set the cluster program into debug mode @@ -2928,7 +3092,7 @@ finished. - 9.31. delete/user (9) + 10.31. delete/user (9) delete/user Delete a user from the User Database @@ -2941,8 +3105,30 @@ It goes without saying that you should use this command CAREFULLY! + 10.32. demonstrate (9) + + demonstrate Demonstrate a command to another user + + + This command is provided so that sysops can demonstrate commands to + other users. It runs a command as though that user had typed it in and + then sends the output to that user, together with the command that + caused it. + - 9.32. directory (0) + + DEMO g7brn sh/dx iota oc209 + DEMO g1tlh set/here + + + + + Note that this command is similar to SPOOF and will have the same side + effects. Commands are run at the privilege of the user which is being + demonstrated to. + + + 10.33. directory (0) directory List messages directory own List your own messages @@ -2966,11 +3152,9 @@ - - - DIR TO G1TLH 5 - or - DIR SUBJECT IOTA 200-250 + DIR TO G1TLH 5 + or + DIR SUBJECT IOTA 200-250 @@ -2980,21 +3164,23 @@ - DIR/T G1* 10 - DIR/S QSL 10-100 5 + + + DIR/T G1* 10 + DIR/S QSL 10-100 5 - 9.33. directory (extended for sysops) (5) + 10.34. directory (extended for sysops) (5) Works just like the user command except that sysops can see ALL messages. - 9.34. disconnect (8) + 10.35. disconnect (8) disconnect [ ...] Disconnect a user or node @@ -3002,7 +3188,7 @@ Disconnect any connected locally - 9.35. dx (0) + 10.36. dx (0) dx [by ] Send a DX spot @@ -3033,8 +3219,7 @@ - - DX by G1TLH FR0G 144.600 he isn't on the cluster + DX by G1TLH FR0G 144.600 he isn't on the cluster @@ -3043,11 +3228,10 @@ cluster. See SHOW/BANDS for more information. - 9.36. export (9) + 10.37. export (9) export 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 @@ -3061,7 +3245,7 @@ EXPORT 2345 /tmp/a - 9.37. export_users (9) + 10.38. export_users (9) export_users [] Export the users database to ascii @@ -3077,7 +3261,7 @@ check is made on the filename (if any) that you specify. - 9.38. filtering (0) + 10.39. filtering (0) filtering Filtering things in DXSpider @@ -3179,6 +3363,7 @@ clear/spots 1 + To remove the filter in its entirty:- clear/spots all @@ -3209,7 +3394,7 @@ The next filter line lets through just VHF/UHF spots from EU. - 9.39. forward/latlong (8) + 10.40. forward/latlong (8) forward/latlong Send latitude and longitude information to another cluster @@ -3223,7 +3408,7 @@ so it is not recommended on slow links. - 9.40. forward/opername (1) + 10.41. forward/opername (1) forward/opername Send out information on this to all clusters @@ -3235,7 +3420,7 @@ available. - 9.41. help (0) + 10.42. help (0) help Get help on a command @@ -3248,7 +3433,7 @@ commands to look at with HELP. - 9.42. init (5) + 10.43. init (5) init Re-initialise a link to an AK1A compatible node @@ -3262,7 +3447,7 @@ Best of luck - you will need it. - 9.43. kill (0) + 10.44. kill (0) kill [ ..] Delete a message from the local system @@ -3272,7 +3457,7 @@ the sysop). - 9.44. kill (5) + 10.45. kill (5) kill [ ...] Remove or erase a message from the system kill from Remove all messages from a callsign @@ -3285,7 +3470,7 @@ As a sysop you can kill any message on the system. - 9.45. kill full (5) + 10.46. kill full (5) kill full [] Delete a message from the whole cluster @@ -3296,9 +3481,7 @@ same subject will be deleted. Beware! - - - 9.46. kill/expunge (6) + 10.47. kill/expunge (6) kill/expunge [..]Expunge a message @@ -3313,8 +3496,7 @@ It otherwise is used in the same way as the KILL command. - - 9.47. links (0) + 10.48. links (0) links Show which nodes are physically connected @@ -3324,7 +3506,7 @@ - 9.48. load/aliases (9) + 10.49. load/aliases (9) load/aliases Reload the command alias table @@ -3334,7 +3516,7 @@ running in order for the changes to take effect. - 9.49. load/badmsg (9) + 10.50. load/badmsg (9) load/badmsg Reload the bad message table @@ -3346,7 +3528,7 @@ deleted on receipt. - 9.50. load/badwords (9) + 10.51. load/badwords (9) load/badwords Reload the bad words table @@ -3360,15 +3542,16 @@ ignored. - 9.51. load/bands (9) + 10.52. load/bands (9) 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. - 9.52. load/cmd_cache (9) + 10.53. load/cmd_cache (9) load/cmd_cache Reload the automatic command cache @@ -3379,9 +3562,7 @@ 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. - - - 9.53. load/forward (9) + 10.54. load/forward (9) load/forward Reload the msg forwarding routing table @@ -3389,7 +3570,7 @@ whilst the cluster is running. - 9.54. load/messages (9) + 10.55. load/messages (9) load/messages Reload the system messages file @@ -3402,7 +3583,7 @@ unknown message 'xxxx' in lang 'en' - 9.55. load/prefixes (9) + 10.56. load/prefixes (9) load/prefixes Reload the prefix table @@ -3411,7 +3592,7 @@ manually whilst the cluster is running. - 9.56. merge (5) + 10.57. merge (5) merge [/] Ask for the latest spots and WWV @@ -3426,30 +3607,41 @@ data). - 9.57. msg (9) + 10.58. msg (9) msg [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 - change TO callsign to - MSG FRom - change FROM callsign to - MSG PRrivate - set private flag - MSG NOPRrivate - unset private flag - MSG RR - set RR flag - MSG NORR - unset RR flag - MSG KEep - set the keep flag (message won't be deleted ever) - MSG NOKEep - unset the keep flag - MSG SUbject - change the subject to - MSG WAittime - remove any waitting time for this message - MSG NOREad - mark message as unread - MSG REad - mark message as read - MSG QUeue - queue any outstanding bulletins - MSG QUeue 1 - queue any outstanding private messages + + + + + + + + + + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waitting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages @@ -3461,7 +3653,7 @@ This will display more information on the message than DIR does. - 9.58. pc (8) + 10.59. pc (8) pc Send text (eg PC Protocol) to @@ -3480,7 +3672,7 @@ pc G1TLH Try doing that properly!!! - 9.59. ping (1) + 10.60. ping (1) ping Check the link quality between nodes @@ -3493,10 +3685,7 @@ - - - - 9.60. rcmd (1) + 10.61. rcmd (1) rcmd Send a command to another DX cluster @@ -3504,13 +3693,14 @@ This command allows you to send nearly any command to another DX Cluster node that is connected to the system. + Whether you get any output is dependant on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all. - 9.61. read (0) + 10.62. read (0) read Read the next unread personal message addressed to you read Read the specified message @@ -3521,7 +3711,7 @@ - 9.62. read (extended for sysops) (5) + 10.63. read (extended for sysops) (5) read Read a message on the system @@ -3529,7 +3719,7 @@ As a sysop you may read any message on the system - 9.63. reject/announce + 10.64. reject/announce reject/announce [0-9] Set a reject filter for announce @@ -3561,7 +3751,6 @@ - some examples:- @@ -3583,7 +3772,7 @@ but this probably for advanced users... - 9.64. reject/announce (extended for sysops) (8) + 10.65. reject/announce (extended for sysops) (8) reject/announce [input] [0-9] Announce filter sysop version @@ -3602,7 +3791,7 @@ - 9.65. reject/route (8) + 10.66. reject/route (8) reject/route [0-9] Set an 'reject' filter line for routing @@ -3628,11 +3817,16 @@ origin_itu origin_zone + + + + some examples:- - rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) + + rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) @@ -3648,7 +3842,7 @@ - 9.66. reject/spots (0) + 10.67. reject/spots (0) reject/spots [0-9] Set a reject filter line for spots @@ -3694,6 +3888,10 @@ rej/spot 1 on hf rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16) + + + + You can use the tag 'all' to reject everything eg: @@ -3706,7 +3904,7 @@ but this probably for advanced users... - 9.67. reject/spots (extended for sysops) (8) + 10.68. reject/spots (extended for sysops) (8) reject/spots [input] [0-9] Reject spot filter sysop version @@ -3727,7 +3925,7 @@ - 9.68. reject/wcy (0) + 10.69. reject/wcy (0) reject/wcy [0-9] Set a reject WCY filter @@ -3760,7 +3958,7 @@ - 9.69. reject/wcy (extended for sysops) (8) + 10.70. reject/wcy (extended for sysops) (8) reject/wcy [input] [0-9] WCY reject filter sysop version @@ -3772,7 +3970,7 @@ reject/wcy gb7djk all - 9.70. reject/wwv (0) + 10.71. reject/wwv (0) reject/wwv [0-9] Set a reject WWV filter @@ -3810,7 +4008,7 @@ See HELP FILTER for information. - 9.71. reject/wwv (extended for sysops) (8) + 10.72. reject/wwv (extended for sysops) (8) reject/wwv [input] [0-9] WWV reject filter sysop version @@ -3826,7 +4024,7 @@ reject/wwv user_default by W - 9.72. reply (0) + 10.73. reply (0) reply Reply (privately) to the last message that you have read reply Reply (privately) to the specified message @@ -3843,7 +4041,7 @@ further details) - 9.73. send (0) + 10.74. send (0) send [ ...] Send a message to one or more callsigns send RR Send a message and ask for a read receipt @@ -3877,7 +4075,7 @@ is an alias for SEND PRIVATE - 9.74. set/address (0) + 10.75. set/address (0) set/address Record your postal address @@ -3885,14 +4083,14 @@ Literally, record your address details on the cluster. - 9.75. set/announce (0) + 10.76. set/announce (0) set/announce Allow announce messages Allow announce messages to arrive at your terminal. - 9.76. set/arcluster (5) + 10.77. set/arcluster (5) set/arcluster [ ...] Make the node_call an AR- Cluster type node @@ -3901,7 +4099,7 @@ Set the node_call as an AR-Cluster type node - 9.77. set/baddx (8) + 10.78. set/baddx (8) set/baddx Stop words we do not wish to see in the callsign field of a dx spot being propagated @@ -3930,7 +4128,7 @@ - 9.78. set/badnode (6) + 10.79. set/badnode (6) set/badnode Stop spots from this node_call being propagated @@ -3964,7 +4162,7 @@ FILTERing. - 9.79. set/badspotter (8) + 10.80. set/badspotter (8) set/badspotter Stop spots from this callsign being propagated @@ -3998,7 +4196,7 @@ FILTERing. - 9.80. set/badword (8) + 10.81. set/badword (8) set/badword Stop things with this word being propogated @@ -4020,19 +4218,19 @@ - 9.81. set/beep (0) + 10.82. set/beep (0) set/beep Add beeps to terminal messages Add a beep to DX and other terminal messages. - 9.82. set/bbs (5) + 10.83. set/bbs (5) set/bbs [..]Make a BBS - 9.83. set/clx (5) + 10.84. set/clx (5) set/clx [ ...] Make the node_call a CLX type node @@ -4041,7 +4239,7 @@ Set the node_call as a CLX type node - 9.84. set/debug (9) + 10.85. set/debug (9) set/debug Add a debug level to the debug set @@ -4055,7 +4253,7 @@ You can remove a debug level with unset/debug - 9.85. set/dx (0) + 10.86. set/dx (0) set/dxAllow DX messages to arrive at your terminal @@ -4063,7 +4261,7 @@ You can stop DX messages with the unset/dx command - 9.86. set/dxgrid (0) + 10.87. set/dxgrid (0) set/dxgridAllow grid squares on the end of DX messages @@ -4073,7 +4271,7 @@ to remove the grid squares. - 9.87. set/dxnet (5) + 10.88. set/dxnet (5) set/dxnet [ ...] Make the node_call a DXNet type node @@ -4082,7 +4280,7 @@ Set the node_call as a DXNet type node - 9.88. set/echo (0) + 10.89. set/echo (0) set/echo Make the cluster echo your input @@ -4099,7 +4297,7 @@ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 9.89. set/email (0) + 10.90. set/email (0) set/email Set email address(es) and forward your personals @@ -4119,7 +4317,7 @@ UNSET/EMAIL - 9.90. set/here (0) + 10.91. set/here (0) set/here Set the here flag @@ -4130,7 +4328,7 @@ brackets around your callsign to indicate you are not available. - 9.91. set/homenode (0) + 10.92. set/homenode (0) set/homenode Set your home cluster @@ -4147,7 +4345,7 @@ - 9.92. set/hops (8) + 10.93. set/hops (8) set/hops ann|spots|wwv|wcy Set hop count @@ -4167,7 +4365,7 @@ creates a filter and works in conjunction with the filter system. - 9.93. set/isolate (9) + 10.94. set/isolate (9) set/isolate Isolate a node from the rest of the network @@ -4185,7 +4383,7 @@ You can remove the isolation with the command unset/isolate. - 9.94. set/language (0) + 10.95. set/language (0) set/language Set the language you wish to use @@ -4194,7 +4392,7 @@ Currently the languages available are en (English) and nl (Dutch). - 9.95. set/location (0) + 10.96. set/location (0) set/location Set your latitude and longitude @@ -4211,7 +4409,7 @@ - 9.96. set/sys_location (9) + 10.97. set/sys_location (9) set/sys_location Set your cluster latitude and longitude @@ -4228,7 +4426,7 @@ - 9.97. set/logininfo (0) + 10.98. set/logininfo (0) set/logininfo Show logins and logouts of nodes and users @@ -4238,7 +4436,7 @@ - 9.98. set/lockout (9) + 10.99. set/lockout (9) set/lockout Stop a callsign connecting to the cluster @@ -4247,7 +4445,7 @@ allow the user to connect again, use the unset/lockout command. - 9.99. set/name (0) + 10.100. set/name (0) set/name Set your name @@ -4262,7 +4460,7 @@ - 9.100. set/node (9) + 10.101. set/node (9) set/node [ ...] Make the callsign an AK1A cluster @@ -4288,7 +4486,7 @@ - 9.101. set/obscount (9) + 10.102. set/obscount (9) set/obscount Set the 'pump-up' obsolescence counter @@ -4309,7 +4507,7 @@ minutes, it is disconnected. - 9.102. set/page (0) + 10.103. set/page (0) set/page Set the number of lines per page @@ -4329,7 +4527,7 @@ The setting is stored in your user profile. - 9.103. set/password (0) + 10.104. set/password (0) set/password Set your own password @@ -4344,7 +4542,7 @@ type, depending on the type of telnet client you have. - 9.104. set/password (9) + 10.105. set/password (9) set/password Set a users password @@ -4370,7 +4568,7 @@ password. - 9.105. set/pinginterval (9) + 10.106. set/pinginterval (9) set/pinginterval