X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=622d272a33ae3adbfd16e83984aff182c687d745;hb=e39c09e699ff7ae8b54702299dfffce16755dbdb;hp=c2a3f93c2ba789377c14dac178f32883e2ba88e9;hpb=61660841afb3901002602e4956f09de5567bc950;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index c2a3f93c..622d272a 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,7 @@ - The DXSpider Installation and Administration Manual - Ian Maude, G0VGS, (ianmaude@btinternet.com) - $Date$ $Revision$ + The DXSpider Administration Manual v1.50 + Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and Charlie Carroll, + K1XX, (k1xx@ptcnh.net) + February 2003 revision 0.3 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -9,2860 +10,1969 @@ + 1. Routing and Filtering + 1.1 Introduction + 1.2 Route Filters + 1.3 The node_default filter + 1.4 General route filtering + 1.5 General filter rules + 1.6 Types of filter + 1.7 Filter options + 1.8 Default filters + 1.9 Advanced filtering + 1.10 Basic hop control + 1.11 Hop Control on Specific Nodes + 1.12 Isolating networks + + 2. Other filters + 2.1 Filtering Mail + 2.2 Filtering words from text fields in Announce, Talk and DX spots + 2.3 Stopping (possibly bad) DX Spots from Nodes or Spotters + + 3. Mail + 3.1 Personal mail + 3.2 Bulletin mail + 3.3 Forward.pl + 3.4 The msg command + 3.5 Message status + 3.6 Filtering mail + 3.7 Distribution lists + 3.8 BBS interface + + 4. Scripts + 5. Databases + 5.1 Creating databases + 5.2 Importing databases + 5.3 Checking available databases + 5.4 Looking up databases + 5.5 Removing databases + + 6. Information, files and useful programs + 6.1 MOTD + 6.2 MOTD_NOR + 6.3 Downtime message + 6.4 Other text messages + 6.5 The Aliases file + 6.6 Console.pl + 6.7 Updating kepler data + 6.8 The QRZ callbook + 6.9 Connecting logging programs + + 7. Java Web applet + 8. Web based statistics + 9. Security + 9.1 Registration + 9.2 Passwords + + 10. CVS + 10.1 CVS from a Linux platform + 10.2 CVS from a Windows platform + + 11. The DXSpider command set + 11.1 accept/announce (0) + 11.2 accept/announce (extended for sysops) (8) + 11.3 accept/route (8) + 11.4 accept/spots (0) + 11.5 accept/spots (extended for sysops) (8) + 11.6 accept/wcy (0) + 11.7 accept/wcy (extended for sysops) (8) + 11.8 accept/wwv (0) + 11.9 accept/wwv (extended for sysops) (8) + 11.10 announce (0) + 11.11 announce full (0) + 11.12 announce sysop (5) + 11.13 apropos (0) + 11.14 bye (0) + 11.15 catchup (5) + 11.16 clear/announce (8) + 11.17 clear/route (8) + 11.18 clear/spots (0) + 11.19 clear/spots (extended for sysops) (8) + 11.20 clear/wcy (0) + 11.21 clear/wcy (extended for sysops) (8) + 11.22 clear/wwv (0) + 11.23 clear/wwv (extended for sysops) (8) + 11.24 connect (5) + 11.25 dbavail (0) + 11.26 dbcreate (9) + 11.27 dbimport (9) + 11.28 dbremove (9) + 11.29 dbshow (0) + 11.30 debug (9) + 11.31 delete/user (9) + 11.32 demonstrate (9) + 11.33 directory (0) + 11.34 directory (extended for sysops) (5) + 11.35 disconnect (8) + 11.36 dx (0) + 11.37 export (9) + 11.38 export_users (9) + 11.39 filtering (0) + 11.40 forward/latlong (8) + 11.41 forward/opername (1) + 11.42 help (0) + 11.43 init (5) + 11.44 kill (0) + 11.45 kill (5) + 11.46 kill full (5) + 11.47 kill/expunge (6) + 11.48 links (0) + 11.49 load/aliases (9) + 11.50 load/badmsg (9) + 11.51 load/badwords (9) + 11.52 load/bands (9) + 11.53 load/cmd_cache (9) + 11.54 load/forward (9) + 11.55 load/messages (9) + 11.56 load/prefixes (9) + 11.57 merge (5) + 11.58 msg (9) + 11.59 pc (8) + 11.60 ping (1) + 11.61 rcmd (1) + 11.62 read (0) + 11.63 read (extended for sysops) (5) + 11.64 reject/announce + 11.65 reject/announce (extended for sysops) (8) + 11.66 reject/route (8) + 11.67 reject/spots (0) + 11.68 reject/spots (extended for sysops) (8) + 11.69 reject/wcy (0) + 11.70 reject/wcy (extended for sysops) (8) + 11.71 reject/wwv (0) + 11.72 reject/wwv (extended for sysops) (8) + 11.73 reply (0) + 11.74 send (0) + 11.75 set/address (0) + 11.76 set/announce (0) + 11.77 set/arcluster (5) + 11.78 set/baddx (8) + 11.79 set/badnode (6) + 11.80 set/badspotter (8) + 11.81 set/badword (8) + 11.82 set/beep (0) + 11.83 set/bbs (5) + 11.84 set/clx (5) + 11.85 set/debug (9) + 11.86 set/dx (0) + 11.87 set/dxgrid (0) + 11.88 set/dxnet (5) + 11.89 set/echo (0) + 11.90 set/email (0) + 11.91 set/here (0) + 11.92 set/homenode (0) + 11.93 set/hops (8) + 11.94 set/isolate (9) + 11.95 set/language (0) + 11.96 set/location (0) + 11.97 set/sys_location (9) + 11.98 set/logininfo (0) + 11.99 set/lockout (9) + 11.100 set/name (0) + 11.101 set/node (9) + 11.102 set/obscount (9) + 11.103 set/page (0) + 11.104 set/password (0) + 11.105 set/password (9) + 11.106 set/pinginterval (9) + 11.107 set/privilege (9) + 11.108 set/spider (5) + 11.109 set/sys_qra (9) + 11.110 set/qra (0) + 11.111 set/qth (0) + 11.112 set/register (9) + 11.113 set/talk (0) + 11.114 set/wcy (0) + 11.115 set/wwv (0) + 11.116 set/wx (0) + 11.117 show/baddx (1) + 11.118 show/badnode (6) + 11.119 show/badspotter (1) + 11.120 show/badword (1) + 11.121 show/configuration (0) + 11.122 show/configuration/node (0) + 11.123 show/connect (1) + 11.124 show/date (0) + 11.125 show/debug (9) + 11.126 show/dx (0) + 11.127 show/dxcc (0) + 11.128 sh/dxstats (0) + 11.129 show/files (0) + 11.130 show/filter (0) + 11.131 show/filter (extended for sysops) (5) + 11.132 show/hfstats (0) + 11.133 show/hftable (0) + 11.134 show/hops (8) + 11.135 show/isolate (1) + 11.136 show/lockout (9) + 11.137 show/log (8) + 11.138 show/moon (0) + 11.139 show/muf (0) + 11.140 show/newconfiguration (0) + 11.141 show/newconfiguration/node (0) + 11.142 show/node (1) + 11.143 show/prefix (0) + 11.144 show/program (5) + 11.145 show/qra (0) + 11.146 show/qrz (0) + 11.147 show/registered (9) + 11.148 show/route (0) + 11.149 show/satellite (0) + 11.150 show/sun (0) + 11.151 show/time (0) + 11.152 show/vhfstats (0) + 11.153 show/vhftable (0) + 11.154 show/wcy (0) + 11.155 show/wwv (0) + 11.156 shutdown (5) + 11.157 spoof (9) + 11.158 stat/db (5) + 11.159 stat/channel (5) + 11.160 stat/msg (5) + 11.161 stat/route_node (5) + 11.162 stat/route_user (5) + 11.163 stat/user (5) + 11.164 sysop (0) + 11.165 talk (0) + 11.166 type (0) + 11.167 who (0) + 11.168 wx (0) + 11.169 wx (enhanced for sysops) (5) + ______________________________________________________________________ + 1. Routing and Filtering + 1.1. Introduction + From DXSpider version 1.48, major changes were introduced to the way + node connections are treated. This is part of an ongoing process to + remove problems with loops and to enable talk and other functions to + propagate across the whole of the worldwide cluster network. In fact, + in a Spider network, it would be useful, perhaps even necessary to + have loops. This would give real resilience to the network, meaning + that if a link dropped, the information flow would simply come in and + go out via a different route. Of course, we do not have a complete + network of Spider nodes, there are other programs out there. Some of + these do not have any protection from loops. Certainly AK1A does not + handle loops well at all. It is therefore necessary to have some form + of protection for these nodes. + In fact DXSpider has had a simple system for some time which is called + isolation. This is similar to what in other systems such as clx, is + called passive mode. A more detailed explanation of isolation is given + further below. This system is still available and, for simple + networks, is probably all that you need. + The new functionality introduced in version 1.48 allows filtering the + node and user protocol frames on a "per interface" basis. We call this + route filtering. This is used instead of isolation. + What this really means is that you can control more or less completely + which user and node management PC protocol frames pass to each of your + partner nodes. You can also limit what comes into your node from your + partners. It is even possible to control the settings that your + partner node has for the routing information that it sends to you + (using the rcmd command). + 1.2. Route Filters + Initially when route filters were being tested we generated a + "default" filter. Unfortunately it quickly became apparent that this + might suit the UK cluster network but didn't really fit anybody else. + However using a default filter is an appropriate thing to do. How, is + explained further on. + The first thing that you must do is determine whether you need to use + route filtering at all. If you are a "normal" node with two or three + partners and you arranged in an "official" non-looping tree type + network, then you do not need to do route filtering and you will feel + a lot better for not getting involved. If you are successfully using + isolation then you also probably don't need to use route filtering. + To put it simply, you should not mix Isolation and Route Filtering. + It will work, of sorts, but you will not get the expected results. If + you are using Isolation sucessfully at the moment, do not get involved + in Route Filtering unless you have a good supply of aspirin! Once you + have started down the road of Route Filtering, do not use Isolation + either. Use one or the other, not both. + You will only require this functionality if you are "well-connected". + What that means is that you are connected to several different parts + of (say) the EU cluster and, at the same time, also connected to two + or three places in the US which, in turn are connected back to the EU. + This is called a "loop" and if you are seriously looped then you need + filtering. + I should at this stage give a little bit of background on filters. + All the filters in Spider work in basically the same way. You can + either accept or reject various options in order to create the filter + rules you wish to achieve. Some filters are user settable, others can + only be altered by the sysop. Route filtering can only be done by the + sysop. + Anyway, without further discouragement, let me start the process of + explanation. + 1.3. The node_default filter + All normal systems should have a default routing filter and it should + usually be set to send only the normal, unlooped, view of your + "national" network. Here in the UK that means nodes from the UK and + Eire, in EU it is more complex as the networks there grew up in a more + intertwined way. + The generic commands are:- + reject/route node_default + or + accept/route node_default + where filter_option is one of the following ... + call + call_dxcc + call_itu + call_zone + channel + channel_dxcc + channel_itu + channel_zone + Please be careful if you alter this setting, it will affect ALL your + links! Remember, this is a default filter for node connections, not a + per link default. + For the default routing filter then you have two real choices: either + a "national" view or the "safe" option of only your own callsign. + Examples of each (for my node: GB7DJK) are:- + acc/route node_default call_dxcc 61,38 + acc/route node_default call gb7djk + GB7DJK uses the first of these. The DXCC countries can be obtained + from the show/prefix command. - 1. Installation (Original version by Iain Philipps, G0RDI) - - 1.1 Introduction - 1.2 Preparation - 1.3 Installing the software - 1.4 Setting callsigns etc - 1.5 Starting up for the first time - 1.6 The Client program - - 2. Quick installation guide - - 3. Configuration - - 3.1 Allowing ax25 connects from users - 3.2 Allowing telnet connects from users - 3.3 Setting up telnet connects (from 1.47 onwards) - 3.4 Setting up for AGW Engine (1.47 onwards) - 3.5 Setting up node connects - 3.6 Connection scripts - 3.7 Starting the connection - 3.8 Telnet echo - - 4. Automating things - - 4.1 Autostarting the cluster - 4.2 The crontab file - - 5. Hop control - - 5.1 Basic hop control - 5.2 Isolating networks - - 6. Filtering (Old Style upto v1.44) - - 6.1 Spots - 6.2 Announcements - 6.3 WWV - - 7. Filtering (New Style v1.45 and later) - - 7.1 General filter rules - 7.2 Types of filter - 7.3 Filter options - 7.4 Default filters - 7.5 Advanced filtering - - 8. Other filters - - 8.1 Filtering Mail - 8.2 Filtering DX callouts (Depricated) - 8.3 Filtering words from text fields in Announce, Talk and DX spots - - 9. Mail - - 9.1 Personal mail - 9.2 Bulletin mail - 9.3 Forward.pl - 9.4 The msg command - 9.5 Message status - 9.6 Filtering mail - 9.7 Distribution lists - 9.8 BBS interface - - 10. Databases - - 10.1 Creating databases - 10.2 Importing databases - 10.3 Checking available databases - 10.4 Looking up databases - 10.5 Removing databases - - 11. Information, files and useful programs - - 11.1 MOTD - 11.2 Downtime message - 11.3 Other text messages - 11.4 The Aliases file - 11.5 Console.pl - 11.6 Updating kepler data - 11.7 The QRZ callbook - - 12. CVS - - 13. The DXSpider command set - - 13.1 accept/announce (0) - 13.2 accept/announce (extended for sysops) (8) - 13.3 accept/spots (0) - 13.4 accept/spots (extended for sysops) (8) - 13.5 accept/wcy (0) - 13.6 accept/wcy (extended for sysops) (8) - 13.7 accept/wwv (0) - 13.8 accept/wwv (extended for sysops) (8) - 13.9 announce (0) - 13.10 announce full (0) - 13.11 announce sysop (5) - 13.12 apropos (0) - 13.13 bye (0) - 13.14 catchup (5) - 13.15 clear/spots (0) - 13.16 connect (5) - 13.17 dbavail (0) - 13.18 dbcreate (9) - 13.19 dbimport (9) - 13.20 dbremove (9) - 13.21 dbshow (0) - 13.22 debug (9) - 13.23 directory (0) - 13.24 directory (extended for sysops) (5) - 13.25 disconnect (8) - 13.26 dx (0) - 13.27 export (9) - 13.28 export_users (9) - 13.29 forward/latlong (8) - 13.30 forward/opername (1) - 13.31 help (0) - 13.32 init (5) - 13.33 kill (0) - 13.34 kill (5) - 13.35 kill full (5) - 13.36 links (0) - 13.37 load/aliases (9) - 13.38 load/baddx (9) - 13.39 load/badmsg (9) - 13.40 load/badwords (9) - 13.41 load/bands (9) - 13.42 load/cmd_cache (9) - 13.43 load/forward (9) - 13.44 load/messages (9) - 13.45 load/prefixes (9) - 13.46 merge (5) - 13.47 msg (9) - 13.48 pc (8) - 13.49 ping (1) - 13.50 rcmd (1) - 13.51 read (0) - 13.52 read (extended for sysops) (5) - 13.53 reject/announce - 13.54 reject/announce (extended for sysops) (8) - 13.55 reject/spots (0) - 13.56 reject/spots (extended for sysops) (8) - 13.57 reject/wcy (0) - 13.58 reject/wcy (extended for sysops) (8) - 13.59 reject/wwv (0) - 13.60 reject/wwv (extended for sysops) (8) - 13.61 reply (0) - 13.62 send (0) - 13.63 set/address (0) - 13.64 set/announce (0) - 13.65 set/arcluster (5) - 13.66 set/baddx (8) - 13.67 set/badnode (6) - 13.68 set/badspotter (8) - 13.69 set/beep (0) - 13.70 set/clx (5) - 13.71 set/debug (9) - 13.72 set/dx (0) - 13.73 set/dxgrid (0) - 13.74 set/dxnet (5) - 13.75 set/echo (0) - 13.76 set/here (0) - 13.77 set/homenode (0) - 13.78 set/hops (8) - 13.79 set/isolate (9) - 13.80 set/language (0) - 13.81 set/location (0) - 13.82 set/sys_location (9) - 13.83 set/logininfo (0) - 13.84 set/lockout (9) - 13.85 set/name (0) - 13.86 set/node (9) - 13.87 set/obscount (9) - 13.88 set/page (0) - 13.89 set/password (9) - 13.90 set/pinginterval (9) - 13.91 set/privilege (9) - 13.92 set/spider (5) - 13.93 set/sys_qra (9) - 13.94 set/qra (0) - 13.95 set/qth (0) - 13.96 set/talk (0) - 13.97 set/wcy (0) - 13.98 set/wwv (0) - 13.99 set/wx (0) - 13.100 show/baddx (1) - 13.101 show/badnode (6) - 13.102 show/badspotter (1) - 13.103 show/date (0) - 13.104 show/debug (9) - 13.105 show/dx (0) - 13.106 show/dxcc (0) - 13.107 show/files (0) - 13.108 show/filter (0) - 13.109 show/filter (extended for sysops) (5) - 13.110 show/hops (8) - 13.111 show/isolate (1) - 13.112 show/lockout (9) - 13.113 show/log (8) - 13.114 show/moon (0) - 13.115 show/muf (0) - 13.116 show/node (1) - 13.117 show/prefix (0) - 13.118 show/program (5) - 13.119 show/qra (0) - 13.120 show/qrz (0) - 13.121 show/route (0) - 13.122 show/satellite (0) - 13.123 show/sun (0) - 13.124 show/time (0) - 13.125 show/wcy (0) - 13.126 show/wwv (0) - 13.127 shutdown (5) - 13.128 spoof (9) - 13.129 stat/db (5) - 13.130 stat/channel (5) - 13.131 stat/msg (5) - 13.132 stat/user (5) - 13.133 sysop (0) - 13.134 talk (0) - 13.135 type (0) - 13.136 who (0) - 13.137 wx (0) - 13.138 wx (enhanced for sysops) (5) - - - ______________________________________________________________________ - - 11.. IInnssttaallllaattiioonn ((OOrriiggiinnaall vveerrssiioonn bbyy IIaaiinn PPhhiilliippppss,, GG00RRDDII)) - - 11..11.. IInnttrroodduuccttiioonn - - This section describes the installation of DX Spider v1.46 on a RedHat - Linux Distribution. Wherever possible I will try to include - differences for other distributions. I do not intend to try and cover - the installation of Linux or the setup of the AX25 utilities. If you - need help on this then read Iains original installation guide that - comes with the Spider distribution. - - - I am assuming a general knowledge of Linux and its commands. You - should know how to use _t_a_r and how to edit files using your favourite - editor. - - - The crucial ingredient for all of this is Perl. Earlier versions of - Spider required perl 5.004, however it is now _S_T_R_O_N_G_L_Y recommended - that you use at least version 5.005_03 as this is the version being - used in the development of Spider. - - - In addition to the standard Red Hat distribution you will require the - following modules from http://www.cpan.org/CPAN.html ... - - - - +o Data-Dumper-2.101.tar.gz - - +o TimeDate-1.10.tar.gz - - +o IO-1.20.tar.gz (for perl 5.00403 and lower) - - +o Net-Telnet-3.02.tar.gz - - - +o Curses-1.05.tar.gz - - +o Time-HiRes-01.20.tar.gz - - - - _D_o get the latest versions of these packages and install them but use - the above list as the earliest versions usable. - - - 11..22.. PPrreeppaarraattiioonn + The example filters shown control output TO all your partner nodes + unless they have a specific filter applied to them (see next section). - I will assume that you have already downloaded the latest tarball of - the DXSpider software and are ready to install it. I am assuming - version 1.46 for this section but of course you would use the latest - version. + It is also possible to control the incoming routing information that + you are prepared to accept FROM your partner nodes. The reason this is + necessary is to make sure that stuff like mail, pings and similar + commands a) go down the correct links and b) don't loop around + excessively. Again using GB7DJK as an example a typical default input + filter would be something like: - Login as root and create a user to run the cluster under. _U_N_D_E_R _N_O - _C_I_R_C_U_M_S_T_A_N_C_E_S _U_S_E _R_O_O_T _A_S _T_H_I_S _U_S_E_R_!. I am going to use the name - _s_y_s_o_p. You can call it anything you wish. Depending on your security - requirements you may wish to use an existing user, however this is - your own choice. + rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38 - # adduser -m sysop + What this does is accept node and user information for our national + network from nodes that are in our national network, but rejects such + information from anyone else. Although it doesn't explicitly say so, + by implication, any other node information (not from the UK and Eire) + is accepted. + As I imagine it will take a little while to get one's head around all + of this you can study the effect of any rules that you try by watching + the debug output after having done:- - Now set a password for the user ... + set/debug filter - # passwd sysop - # New UNIX password: - # Retype new UNIX password: - passwd: all authentication tokens updated successfully + After you have got tired of that, to put it back the way it was:- + unset/debug filter - 11..33.. IInnssttaalllliinngg tthhee ssooffttwwaarree - Now to unpack the DX Spider distribution, set symbolic links and group - permissions. Copy the tarball to /home/sysop and do the following. + 1.4. General route filtering + Exactly the same rules apply for general route filtering. You would + use either an accept filter or a reject filter like this ... - # cd ~sysop - # tar xvfz spider-1.46.tar.gz - # ln -s ~sysop/spider /spider - # groupadd -g 251 spider (or another number) + reject/route + or - If you do not have the command _g_r_o_u_p_a_d_d available to you simply add a - line in /etc/group by hand. + accept/route - # vi /etc/group (or your favorite editor) + Here are some examples of route filters ... + rej/route gb7djk call_dxcc 61,38 (send everything except UK+EIRE nodes) + rej/route all (equiv to [very] restricted mode) + acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) + acc/route gb7djk call gb7djk (equiv to SET/ISOLATE) - You also need to add some others to the group, including your own - callsign (this will be used as an alias) and root. The finished line - in /etc/group should look something like this - spider:x:251:sysop,g0vgs,root + In practice you will either be opening the default filter out for a + partner by defining a specific filter for that callsign:- - The next step is to set the permissions on the Spider directory tree - and files .... + acc/route gb7baa all + acc/route gb7baa input all - # chown -R sysop.spider spider - # find . -type d -exec chmod 2775 {} \; - # find . -type f -exec chmod 775 {} \; + or restricting it quite a lot, in fact making it very nearly like an + isolated node, like this:- - This last step allows various users of the group _s_p_i_d_e_r to have write - access to all the directories. This is not really needed just yet but - will be useful when web interfaces start to appear. + acc/route pi4ehv-8 call gb7djk + rej/route pi4ehv-8 input call_dxcc 61,38 - Finally, you need to fix the permissions on the ax25_call and - netrom_call programs. Check where they are with the _l_o_c_a_t_e command - and alter the permissions with the _c_h_m_o_d command like this .. + This last example takes everything except UK and Eire from PI4EHV-8 + but only sends him my local configuration (just a PC19 for GB7DJK and + PC16s for my local users). - # chown root ax25_call netrom_call - # chmod 4775 ax25_call netrom_call + It is possible to write much more complex rules, there are up to 10 + accept/reject pairs per callsign per filter. For more information see + the next section. + 1.5. General filter rules + Upto v1.44 it was not possible for the user to set their own filters. + From v1.45 though that has all changed. It is now possible to set + filters for just about anything you wish. If you have just updated + from an older version of DXSpider you will need to update your new + filters. You do not need to do anything with your old filters, they + will be renamed as you update. - 11..44.. SSeettttiinngg ccaallllssiiggnnss eettcc - Now login to your machine as the user you created earlier. In my case - that user is called _s_y_s_o_p. Once logged in, issue the following - commands .... + There are 3 basic commands involved in setting and manipulating + filters. These are accept, reject and clear. First we will look + generally at filtering. There are a number of things you can filter in + the DXSpider system. They all use the same general mechanism. + 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 ... - $ cd /spider - $ mkdir local - $ mkdir local_cmd - $ cp perl/DXVars.pm.issue local/DXVars.pm - $ cd local - $ vi DXVars.pm (or your favourite editor) + accept/spots ..... + reject/spots ..... - Using the distributed DXVars.pm as a a template, set your cluster - callsign, sysop callsign and other user info to suit your own - environment. Note that this a perl file which will be parsed and - executed as part of the cluster. If you get it wrong then perl will - complain when you start the cluster process. It is important only to - alter the text of any section. Some of the lines look a little odd. - Take this line for example .... + 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. - $myemail = "ianmaude\@btinternet.com"; + There is also a command to clear out one or more lines in a filter. + They are ... - There appears to be an extra slash in there. However this has to be - there for the file to work so leave it in. + clear/spots 1 + clear/spots all - PPLLEEAASSEE UUSSEE CCAAPPIITTAALL LLEETTTTEERRSS FFOORR CCAALLLLSSIIGGNNSS - DON'T alter any file in /spider/perl, they are overwritten with every - release. Any files or commands you place in /spider/local or - /spider/local_cmd will automagically be used in preference to the ones - in /spider/perl EVEN while the cluster is running! + There is clear/xxxx command for each type of filter. - Save the new file and change directory to ../perl .... + and you can check that your filters have worked by the command ... - $ cd ../perl + show/filter + For now we are going to use spots for the examples, but you can apply + the same principles to all types of filter. - Now type the following command which creates the basic user file with - you as the sysop. + 1.6. Types of filter + There are two main types of filter, accept or reject. You can use + either to achieve the result you want dependent on your own preference + and which is more simple to do. It is pointless writing 8 lines of + reject filters when 1 accept filter would do the same thing! Each + filter has 10 lines (of any length) which are tried in order. If a + line matches then the action you have specified is taken (ie reject + means ignore it and accept means take it) - $ ./create_sysop.pl + If you specify reject filters, then any lines that arrive that match + the filter will be dumped but all else will be accepted. If you use + an accept filter, then ONLY the lines in the filter will be accepted + and all else will be dumped. For example if you have a single line + accept filter ... + accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - 11..55.. SSttaarrttiinngg uupp ffoorr tthhee ffiirrsstt ttiimmee - We can now bring spider up for the first time and see if all is well - or not! It should look something like this ... + then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16. + If you set a reject filter like this ... - $ ./cluster.pl - DXSpider DX Cluster Version 1.46 - Copyright (c) 1998 Dirk Koopman G1TLH - loading prefixes ... - loading band data ... - loading user file system ... - starting listener ... - reading existing message headers - reading cron jobs - orft we jolly well go ... + reject/spots on hf/cw - If all is well then login on another term or console as _s_y_s_o_p and cd - to /spider/src. Now issue the following command ... + Then you will get everything EXCEPT HF CW spots. You could make this + single filter even more flexible. For example, if you are interested + in IOTA and will work it even on CW even though normally you are not + interested in CW, then you could say ... - $ ./client + reject/spots on hf/cw and not info iota - This should log you into the cluster as the sysop under the alias - callsign we set earlier. In this case the callsign is G0VGS. The - cluster callsign is set in the DXVars.pm file in /spider/local. In - this case we will assume that this was set as GB7MBC. You should - therefore see this when you login .... + But in that case you might only be interested in iota and say:- - G0VGS de GB7MBC 19-Nov-1999 2150Z > + accept/spots not on hf/cw or info iota + which achieves exactly the same thing. You should choose one or the + other until you are comfortable with the way it works. You can mix + them if you wish (actually you can have an accept AND a reject on the + same line) but don't attempt this until you are sure you know what you + are doing! - If you do, congratulations! If not, look over the instructions again, - you have probably missed something out. You can shut spider down - again with the command .... + You can arrange your filter lines into logical units, either for your + own understanding or simply convenience. Here is an example ... - shutdown + reject/spots 1 on hf/cw + reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) + What this does is to ignore all HF CW spots and also rejects any spots + on VHF which don't either originate or spot someone in Europe. - and both the cluster and the client should return to Linux prompts. + This is an example where you would use a line number (1 and 2 in this + case), if you leave the digit out, the system assumes '1'. Digits + '0'-'9' are available. This make it easier to see just what filters + you have set. It also makes it more simple to remove individual + filters, during a contest for example. - 11..66.. TThhee CClliieenntt pprrooggrraamm - In earlier versions of Spider, all the processes were Perl scripts. - This was fine but with a lot of users your computer memory would soon - be used up. To combat this a new client was written in "C". This - client only works for _i_n_c_o_m_i_n_g connects at the moment. Before you can - use it though it has to be "made". CD to /spider/src and type _m_a_k_e. - You should see the output on your screen and hopefully now have a - small C program called _c_l_i_e_n_t. Leave it in this directory. + You will notice in the above example that the second line has + brackets. Look at the line logically. You can see there are 2 + separate sections to it. We are saying reject spots that are VHF or + above APART from those in zones 14, 15 and 16 (either spotted there or + originated there). If you did not have the brackets to separate the 2 + sections, then Spider would read it logically from the front and see a + different expression entirely ... - 22.. QQuuiicckk iinnssttaallllaattiioonn gguuiiddee + (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 - This section is designed for experienced Spider sysops who want to - install Spider from scratch. It is simply a check list of things that - need to be done without any explanations. The name in brackets at the - end of each line is the user that should be doing that process. - +o Login as root + The simple way to remember this is, if you use OR - use brackets. + Whilst we are here CASE is not important. 'And BY_Zone' is just the + same as 'and by_zone'. - +o Get the additional CPAN modules and install them (root) + As mentioned earlier, setting several filters can be more flexible + than simply setting one complex one. Doing it in this way means that + if you want to alter your filter you can just redefine or remove one + or more lines of it or one line. For example ... - +o Create the "sysop" user and set a password (root) - +o Put the Spider tarball in sysop and untar it (root) - +o ln -s sysop/spider /spider (root) + reject/spots 1 on hf/ssb - +o groupadd -g 251 spider (root) + would redefine our earlier example, or - +o Add any more users you need to the group entry in /etc/group (root) - +o Set the permissions on the spider tree (root) - +o Fix permissions on ax25_call and netrom_call (root) + clear/spots 1 - +o Login as the sysop user - +o cd to /spider (sysop) - +o mkdir local (sysop) + To remove all the filter lines in the spot filter ... - +o mkdir local_cmd (sysop) - +o cp perl/DXVars.pm.issue local/DXVars.pm (sysop) - +o cd to /spider/local and edit DXVars to set your details (sysop) + clear/spots all - +o cd ../perl (sysop) - +o ./create_sysop.pl (sysop) - +o ./cluster.pl (sysop) + 1.7. Filter options - Spider should now be running and you should be able to login using the - client program. + You can filter in several different ways. The options are listed in + the various helpfiles for accept, reject and filter. - +o Login as root + 1.8. Default filters - +o Enter the correct line in ax25d.conf (root) + Sometimes all that is needed is a general rule for node connects. + This can be done with a node_default filter. This rule will always be + followed, even if the link is isolated, unless another filter is set + specifically. Default rules can be set for nodes and users. They can + be set for spots, announces, WWV and WCY. They can also be used for + hops. An example might look like this ... - +o Enter the correct line in /etc/services (root) - +o Enter the correct line in /etc/inetd.conf (root) - +o killall -HUP inetd (root) + accept/spot node_default by_zone 14,15,16,20,33 + set/hops node_default spot 50 - Spider should now be able to accept logins via telnet, netrom and - ax25. - +o Login as sysop + This filter is for spots only, you could set others for announce, WWV + and WCY. This filter would work for ALL nodes unless a specific + filter is written to override it for a particular node. You can also + set a user_default should you require. It is important to note that + default filters should be considered to be "connected". By this I + mean that should you override the default filter for spots, you need + to add a rule for the hops for spots also. - +o Start the cluster (sysop) - +o set/node and type for links (sysop) + 1.9. Advanced filtering - +o Write any connect scripts (sysop) + Once you are happy with the results you get, you may like to + experiment. - +o Edit /spider/crontab as required (sysop) - +o Edit any other files as necessary (sysop) + The previous example that filters hf/cw spots and accepts vhf/uhf + spots from EU can be written with a mixed filter, for example ... - +o Set filters, hops and forwarding files (sysop) - +o Login as root - +o Enter the correct line in /etc/inittab (root) + rej/spot on hf/cw + acc/spot on 0/30000 + acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16) + Note that the first filter has not been specified with a number. This + will automatically be assumed to be number 1. In this case, we have + said reject all HF spots in the CW section of the bands but accept all + others at HF. Also accept anything in VHF and above spotted in or by + operators in the zones 14, 15 and 16. Each filter slot actually has a + 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE + the accept slot. - 33.. CCoonnffiigguurraattiioonn + It was mentioned earlier that after a reject test that doesn't match, + the default for following tests is 'accept', the reverse is true for + 'accept'. In the example what happens is that the reject is executed + first, any non hf/cw spot is passed to the accept line, which lets + through everything else on HF. The next filter line lets through just + VHF/UHF spots from EU. + 1.10. Basic hop control - 33..11.. AAlllloowwiinngg aaxx2255 ccoonnnneeccttss ffrroomm uusseerrss + In /spider/data you will find a file called hop_table.pl. This is the + file that controls your hop count settings. It has a set of default + hops on the various PC frames and also a set for each node you want to + alter the hops for. You may be happy with the default settings of + course, but this powerful tool can help to protect and improve the + network. The file will look something like this ... - As stated previously, the aim of this document is not to tell you how - to configure Linux or the ax25 utilities. However, you do need to add - a line in your ax25d.conf to allow connections to DXSpider for your - users. For each interface that you wish to allow connections on, use - the following format ... + # + # hop table construction + # - default * * * * * * - sysop /spider/src/client client %u ax25 + 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, + ); - or, if you wish your users to be able to use SSID's on their callsigns - .. + # the per node hop control thingy + %nodehops = + ( + GB7ADX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, - default * * * * * * - sysop /spider/src/client client %s ax25 + GB7UDX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + GB7BAA => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + ); + Each set of hops is contained within a pair of curly braces and + contains a series of PC frame types. PC11 for example is a DX spot. + The figures here are not exhaustive but should give you a good idea of + how the file works. - For most purposes this is not desirable. The only time you probably - will need this is when you need to allow other cluster nodes that are - using SSID's in. In this case it owuld probably be better to use the - first example and then add a specific line for that node like this: + SHould any of the nodecalls include an ssid, it is important to wrap + the whole call in single quotes, like this ... - GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25 - default * * * * * * - sysop /spider/src/client client %u ax25 + 'DB0FHF-15' => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + If you do not do this, you will get errors and the file will not work + as expected. - 33..22.. AAlllloowwiinngg tteellnneett ccoonnnneeccttss ffrroomm uusseerrss + You can alter this file at any time, including whilst the cluster is + running. If you alter the file during runtime, the command load/hops + will bring your changes into effect. - From version 1.47 there is a new (more efficient) way of doing this - (see next section) but, if you prefer, the method of doing it - described here will continue to work just fine. + 1.11. Hop Control on Specific Nodes - Allowing telnet connections is quite simple. Firstly you need to add - a line in /etc/services to allow connections to a port number, like - this .... + You can set a callsign specific hop count for any of the standard + filter options so:- - spdlogin 7300/tcp # spider anonymous login port + set/hops gb7djk spot 4 + set/hops node_default route 10 + set/hops gb7baa wcy 5 + all work on their specific area of the protocol. - Then add a line in /etc/inetd.conf like this .... + The set/hops command overrides any hops that you have set otherwise. - spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet + You can show what hops have been set using the show/hops command. + 1.12. Isolating networks - Once this is done, you need to restart inetd like this .... + It is possible to isolate networks from each other on a "gateway" node + using the set/isolate command. + The effect of this is to partition an isolated network completely from + another node connected to your node. Your node will appear on and + otherwise behave normally on every network to which you are connected, + but data from an isolated network will not cross onto any other + network or vice versa. However all the spot, announce and WWV traffic + and personal messages will still be handled locally (because you are a + real node on all connected networks), that is locally connected users + will appear on all networks and will be able to access and receive + information from all networks transparently. All routed messages will + be sent as normal, so if a user on one network knows that you are a + gateway for another network, he can still still send a talk/announce + etc message via your node and it will be routed across. - killall -HUP inetd + If you use isolate on a node connection you will continue to receive + all information from the isolated partner, however you will not pass + any information back to the isolated node. There are times when you + would like to forward only spots across a link (maybe during a contest + for example). To do this, isolate the node in the normal way and use + an acc/spot >call< all filter to override the isolate. + 2. Other filters + 2.1. Filtering Mail + In the /spider/msg directory you will find a file called + badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The + original looks something like this .... - Now login as _s_y_s_o_p and cd spider/src. You can test that spider is - accepting telnet logins by issuing the following command .... + # 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) - ./client login telnet + # The format of each line is as follows + # type source pattern + # P/B/F T/F/O/S regex + # type: P - private, B - bulletin (msg), F - file (ak1a bull) + # source: T - to field, F - from field, O - origin, S - subject + # pattern: a perl regex on the field requested - You should get a login prompt and on issuing a callsign, you will be - given access to the cluster. Note, you will not get a password login. - There seems no good reason for a password prompt to be given so it is - not asked for. + # Currently only type B and P msgs are affected by this code. + # + # The list is read from the top down, the first pattern that matches + # causes the action to be taken. + # The pattern can be undef or 0 in which case it will always be selected + # for the action specified - Assuming all is well, then try a telnet from your linux console .... + package DXMsg; - telnet localhost 7300 + @badmsg = ( + ); + I think this is fairly self explanatory. It is simply a list of + subject headers that we do not want to pass on to either the users of + the cluster or the other cluster nodes that we are linked to. This is + usually because of rules and regulations pertaining to items for sale + etc in a particular country. - You should now get the login prompt and be able to login as before. + 2.2. Filtering words from text fields in Announce, Talk and DX spots - 33..33.. SSeettttiinngg uupp tteellnneett ccoonnnneeccttss ((ffrroomm 11..4477 oonnwwaarrddss)) + From version 1.48 onwards the interface to this has changed. You can + now use the commands set/badword to add words that you are not + prepared to see on the cluster, unset/badword to allow that word again + and show/badword to list the words that you have set. - From version 1.47 you can chose to allow the perl cluster.pl program - to allow connections direct (i.e. not via the /spider/src/client - interface program). If you are using Windows then this is the only - method available of allowing incoming telnet connections. + If you have a previous /spider/data/badwords, the first time you start + the node, it will read and convert this file to the new commands. The + old style file will then be removed. - To do this you need first to remove any line that you may previously - have set up in /etc/inetd.conf. Remember to:- + 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters - killall -HUP inetd + There are a number of commands that control whether a spot progresses + any further by regarding it as "bad" in some way. + A DX Spot has a number of fields which can be checked to see whether + they contain "bad" values, they are: the DX callsign itself, the + Spotter and the Originating Node. + There are a set of commands which allow the sysop to control whether a + spot continues:- - to make the change happen... - Having done that then you need to copy the file - /spider/perl/Listeners.pm to /spider/local and then edit it. You will - need to uncomment the line containing "0.0.0.0" and select the correct - port to listen on. So that it looks like this:- - @listen = ( - ["0.0.0.0", 7300], - ); + set/baddx + set/badspotter + set/badnode + These work in the same as the set/badword command, you can add any + words or callsigns or whatever to the appropriate database. For + example, to stop a spot from a particular node you do: - As standard, the listener will listen on all interfaces - simultaniously. If you require more control than this, you can specify - each interface individually:- + set/badnode gb7djk gb7dxc - @listen = ( - ["gb7baa.dxcluster.net", 7300], - ["44.131.16.2", 6300], - ); + a bad spotter: + set/badspotter b0mb p1rat nocall - This will only be successful if the IP addresses on each interface are - static. If you are using some kind of dynamic IP addressing then the - 'default' method is the only one which will work. - Restart the cluster.pl program to enable the listener. + and some bad dx: - One important difference with the internal listener is that no echoing - is done by the cluster program. Users will need to set 'local-echo' on - in their telnet clients if it isn't set automatically (as per the - standards). Needless to say this will probably only apply to Windows - users. + set/baddx video wsjt - 33..44.. SSeettttiinngg uupp ffoorr AAGGWW EEnnggiinnee ((11..4477 oonnwwaarrddss)) - AGW Engine is a Windows based ax25 stack. You can connect to an AGW - engine from Linux as well as Windows based machines. + You can remove a word using the appropriate unset command + (unset/baddx, unset/badspotter, unset/badnode) or list them using one + of show/baddx, show/badspotter and show/badnode. - In order to enable access to an AGW Engine you need to copy - /spider/perl/AGWConnect.pm to /spider/local and edit it. Specifically - you must:- - +o set $enable to 1. + 3. Mail - +o set $login and $passwd to the values set up in your AGW - installation. If you haven't set any there, then you should not - touch these values. + DXSpider deals seamlessly with standard AK1A type mail. It supports + both personal and bulletin mail and the sysop has additional commands + to ensure that mail gets to where it is meant. DXSpider will send + mail almost immediately, assuming that the target is on line. + However, only one mail message is dealt with at any one time. If a + mail message is already being sent or recieved, then the new message + will be queued until it has finished. - +o You can connect to a remote AGW engine (ie on some other machine) - by changing $addr and $port appropriately. + The cluster mail is automatically deleted after 30 days unless the + sysop sets the "keep" flag using the msg command. - +o Restart the cluster.pl program + 3.1. Personal mail + Personal mail is sent using the sp command. This is actually the + default method of sending mail and so a simple s for send will do. A + full list of the send commands and options is in the command set + section, so I will not duplicate them here. + 3.2. Bulletin mail + Bulletin mail is sent by using the sb command. This is one of the + most common mistakes users make when sending mail. They send a + bulletin mail with s or sp instead of sb and of course the message + never leaves the cluster. This can be rectified by the sysop by using + the msg command. - 33..55.. SSeettttiinngg uupp nnooddee ccoonnnneeccttss + Bulletin addresses can be set using the Forward.pl file. - In order to allow cluster node connections, spider needs to know that - the connecting callsign is a cluster node. This is the case whether - the connect is incoming or outgoing. In spider this is a simple task - and can be done in runtime. + 3.3. Forward.pl - Later versions of Spider can distinguish different software and treat - them differently. For example, the WCY beacon cannot be handles by - AK1A type nodes as AK1A does not know what to do with PC73. There are - 4 different types of node at present and although they may not have - any major differences at the moment, it allows for compatibility. The - 4 types are ... + DXSpider receives all and any mail sent to it without any alterations + needed in files. Because personal and bulletin mail are treated + differently, there is no need for a list of accepted bulletin + addresses. It is necessary, however, to tell the program which links + accept which bulletins. For example, it is pointless sending + bulletins addresses to "UK" to any links other than UK ones. The file + that does this is called forward.pl and lives in /spider/msg. At + default, like other spider files it is named forward.pl.issue. Rename + it to forward.pl and edit the file to match your requirements. The + format is below ... - set/node (AK1A type) - set/spider - set/dxnet - set/clx - - - - - - For now, we will assume that the cluster we are going to connect to is - an AK1A type node. - - - Start up the cluster as you did before and login as the sysop with - client. The cluster node I am wanting to make a connection to is - GB7BAA but you would obviously use whatever callsign you required. At - the prompt type ... - - - - set/node gb7baa - - - - - - The case does not matter as long as you have a version of DXSpider - later than 1.33. Earlier versions required the callsign to be in - upper case. - - - That is now set, it is as simple as that. To prove it, login on yet - another console as sysop, cd to spider/src and issue the command ... - - + # + # this is an example message forwarding file for the system + # + # The format of each line is as follows + # + # type to/from/at pattern action destinations + # P/B/F T/F/A regex I/F [ call [, call ...] ] + # + # type: P - private, B - bulletin (msg), F - file (ak1a bull) + # to/from/at: T - to field, F - from field, A - home bbs, O - origin + # pattern: a perl regex on the field requested + # action: I - ignore, F - forward + # destinations: a reference to an array containing node callsigns + # + # if it is non-private and isn't in here then it won't get forwarded + # + # Currently only type B msgs are affected by this code. + # + # The list is read from the top down, the first pattern that matches + # causes the action to be taken. + # + # The pattern can be undef or 0 in which case it will always be selected + # for the action specified + # + # If the BBS list is undef or 0 and the action is 'F' (and it matches the + # pattern) then it will always be forwarded to every node that doesn't have + # it (I strongly recommend you don't use this unless you REALLY mean it, if + # you allow a new link with this on EVERY bull will be forwarded immediately + # on first connection) + # - ./client gb7baa (using the callsign you set as a node) + package DXMsg; + @forward = ( + ); + Simply insert a bulletin address and state in the brackets where you + wish that mail to go. For example, you can see here that mail sent to + "UK" will only be sent to the UK links and not to PA4AB-14. - You should get an initialisation string from DXSpider like this ... + To force the cluster to reread the file use load/forward - ./client gb7baa - PC38^GB7MBC^~ + NB: If a user tries to send mail to a bulletin address that does not + exist in this file, they will get an error. - If the callsign you just set up as a cluster node is for an incoming - connect, this is all that needs to be done. If the connection is to - be outgoing then a connection script needs to be written. + 3.4. The msg command - Sometimes you make a mistake... Honest, it does happen. If you want - to make a node back to being a normal user, regardless of what type it - is, do: + The msg command is a very powerful and flexible tool for the sysop. + It allows the sysop to alter to and from fields and make other changes + to manage the cluster mail. + Here is a full list of the various options ... - unset/node gb7baa + 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 waiting 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 + These commands are simply typed from within the cluster as the sysop + user. - 33..66.. CCoonnnneeccttiioonn ssccrriippttss - Because DXSpider operates under Linux, connections can be made using - just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all - possible examples. Connect scripts live in the /spider/connect - directory and are simple ascii files. Writing a script for - connections is therefore relatively simple. + 3.5. Message status + You can check on a message from within the cluster by using the + command stat/msg. This will give you additional information on the + message number including which nodes have received it, which node it + was received from and when etc. Here is an example of the output of + the command ... - The connect scripts consist of lines which start with the following - keywords or symbols:- + G0VGS de GB7MBC 28-Jan-2001 1308Z > + stat/msg 6869 + From: GB7DJK + Msg Time: 26-Jan-2001 1302Z + Msgno: 6869 + Origin: GB7DJK + Size: 8012 + Subject: AMSAT 2line KEPS 01025.AMSAT + To: UK + Got it Nodes: GB7BAA, GB7ADX + Private: 0 + Read Confirm: 0 + Times read: 0 + G0VGS de GB7MBC 28-Jan-2001 1308Z > - ## All lines starting with a # are ignored, as are completely blank - lines. - ttiimmeeoouutt - timeout followed by a number is the number of seconds to wait - for a command to complete. If there is no timeout specified in - the script then the default is 60 seconds. + 3.6. Filtering mail + This is described in the section on Other filters so I will not + duplicate it here. - aabboorrtt - abort is a regular expression containing one or more strings to - look for to abort a connection. This is a perl regular - expression and is executed ignoring case. + 3.7. Distribution lists - ccoonnnneecctt - connect followed by ax25, agw (for Windows users) or telnet and - some type dependent information. In the case of a telnet - connection, there can be up to two parameters. The first is the - ip address or hostname of the computer you wish to connect to - and the second is the port number you want to use (this can be - left out if it is a normal telnet session). In the case of an - ax25 session then this would normally be a call to ax25_call or - netrom_call as in the example above. It is your responsibility - to get your node and other ax25 parameters to work before going - down this route! + Distribution lists are simply a list of users to send certain types of + mail to. An example of this is mail you only wish to send to other + sysops. In /spider/msg there is a directory called distro. You put + any distibution lists in here. For example, here is a file called + SYSOP.pl that caters for the UK sysops. - '' line in a chat type script. The words/phrases normally come in - pairs, either can be empty. Each line reads input from the - connection until it sees the string (or perl regular expression) - contained in the left hand string. If the left hand string is - empty then it doesn't read or wait for anything. The comparison - is done ignoring case. When the left hand string has found what - it is looking for (if it is) then the right hand string is sent - to the connection. This process is repeated for every line of - chat script. + qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX + GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH + GB7DXK GB7DXI GB7DXS) - cclliieenntt - client starts the connection, put the arguments you would want - here if you were starting the client program manually. You only - need this if the script has a different name to the callsign you - are trying to connect to (i.e. you have a script called other - which actually connects to GB7DJK-1 [instead of a script called - gb7djk-1]). + Any mail sent to "sysop" would only be sent to the callsigns in this + list. - There are many possible ways to configure the script but here are - three examples, one for a NETRom/AX25 connect, one for AGW engines and - one for tcp/ip. + 3.8. BBS interface + Spider provides a simple BBS interface. No input is required from the + sysop of the cluster at all. The BBS simply sets the cluster as a BBS + and pushes any required mail to the cluster. No mail can flow from + Spider to the BBS, the interface is one-way. - timeout 60 - abort (Busy|Sorry|Fail) - # don't forget to chmod 4775 netrom_call! - connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh - # you can leave this out if you call the script 'gb7dxm' - client gb7dxm ax25 + Please be careful not to flood the cluster network with unnecessary + mail. Make sure you only send mail to the clusters that want it by + using the Forward.pl file very carefully. + 4. Scripts + From 1.48 onwards it will become increasingly possible to control + DXSpider's operation with scripts of various kinds. + The directory /spider/scripts is where it all happens and is used for + several things. Firstly it contains a file called startup that can be + used to call in any changes to the cluster from the default settings + on startup. This script is executed immediately after all + initialisation of the node is done but before any connections are + possible. Examples of this include how many spots it is possible to + get with the sh/dx command, whether you want registration/passwords to + be permanently on etc. An example file is shown below and is included + in the distribution as startup.issue. - timeout 60 - abort (Busy|Sorry|Fail) - # this does exactly the same as the previous example - # the '1' is the AGW port number to connect thru for g1tlh - connect agw 1 g1tlh - # you can leave this out if you call the script 'gb7dxm' - client gb7dxm ax25 + # + # startup script example + # + # set maximum no of spots allowed to 100 + # set/var $Spot::maxspots = 100 + # + # Set registration on + # set/var $main::reqreg = 1 + # + # Set passwords on + # set/var $main::passwdreq = 1 + # + As usual, any text behind a # is treated as a comment and not read. + To use this file, simply rename it from startup.issue to startup. In + our example above there are three options. The first option is the + amount of spots that a user can request with the sh/dx command. + Normally the default is to give 10 spots unless the user specifies + more. Without this line enabled, the maximum a user can request is + 100 spots. Depending on your link quality you may wish to enable more + or less by specifying the number. + The other 2 options are dealt with more fully in the security section. - timeout 15 - connect telnet dirkl.tobit.co.uk - # tell GB7DJK-1 that it is connected to GB7DJK - # you can leave this out if you call this script 'gb7djk' - client gb7djk telnet + 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 + - Both these examples assume that everything is set up properly at the - other end. You will find other examples in the /spider/examples - directory. + The lines in between commands can simply insert a blank line or a + character such as a + sign to make the output easier to read. Simply + create this script with your favourite editor and save it with the + callsign of the user as the filename. Filenames should always be in + lower case. + Commands can be inserted in the same way for nodes. A node may wish a + series of commands to be issued on login, such as a merge command for + example. - 33..77.. SSttaarrttiinngg tthhee ccoonnnneeccttiioonn - You start the connection, from within a sysop enabled cluster login, - by typing in the word _c_o_n_n_e_c_t followed by a script name like this .... + 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 - G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1 - connection to GB7DJK-1 started - G0VGS de GB7MBC 13-Dec-1998 2043Z > + Spider allows the creation of local or remote databases. It supports + chained databases, allowing several different databases to be scanned + with one simple command. Importing of databases is limited at present + to the standard AK1A databases such as OBLAST and the DB0SDX QSL + database but will expand with time. + 5.1. Creating databases + Creating a database could not be more simple. All the commands are + sent from the cluster prompt as the sysop user. - This will start a connection using the script called _g_b_7_d_j_k_-_1. You - can follow the connection by watching the term or console from where - you started _c_l_u_s_t_e_r_._p_l. From version 1.47 onwards, you will need to - set/debug connect first. You should see something like this ... + To create a database you use the command dbcreate. It can be used in + 3 different ways like so .. - <- D G1TLH connect gb7djk-1 - -> D G1TLH connection to GB7DJK-1 started - -> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z > - timeout set to 15 - CONNECT sort: telnet command: dirkl.tobit.co.uk - CHAT "login" -> "gb7djk" - received " - Red Hat Linux release 5.1 (Manhattan) - Kernel 2.0.35 on an i586 - " - received "login: " - sent "gb7djk" - CHAT "word" -> "gb7djk" - received "gb7djk" - received "Password: " - sent "gb7djk" - Connected to GB7DJK-1, starting normal protocol - <- O GB7DJK-1 telnet - -> B GB7DJK-1 0 - GB7DJK-1 channel func state 0 -> init - <- D GB7DJK-1 - <- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1 - <- D GB7DJK-1 PC38^GB7DJK-1^~ - <- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime - 0 00:00^5447^~ - etc + 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. - With later versions of Spider there is a set/login command for users. - This tells them when a user or node logs in or out. If you do not add - a line to your scripts after the final line (or before the client line - which should always be last if needed) then the login/logout - information will be sent to users _b_e_f_o_r_e the login actually completes. - This means if a node is unreachable, it will continue sending logins - and logouts to users even though it is not actually connecting. To - avoid this use the following line ... + dbcreate chain [...] + This creates a chained database entry. The first database will be + scanned, then the second, the third etc... - In a script, this might look like ... + dbcreate remote - timeout 35 - abort (Busy|Sorry|Fail) - connect telnet mary 3000 + 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... + dbcreate buckmaster remote gb7dxc - 33..88.. TTeellnneett eecchhoo - Cluster links in particular suffer greatly from the presence of telnet - echo. This is caused by the telnet negotiation itself and can create - at worst severe loops. At best it creates unnecessary bandwidth and - large logfiles! There are things that can be done to limit this - problem but will not always work dependent on the route taken to - connect. + Remote databases cannot be chained, however, the last database in a + chain can be a remote database. - Telnet echo itself should only be a problem if the connection is being - made to the telnet port (23). This port uses special rules that - include echo negotiation. If the connection is to a different port, - such as 7300, this negotiation does not happen and therefore no echo - should be present. + 5.2. Importing databases + The only databases that Spider can currently import are the standard + AK1A databases such as OBLAST or the DB0SDX qsl and address database. + This will be added to with time. - Sometimes it is not possible to make a direct connection to another - node and this can cause problems. There is a way of trying to - suppress the telnet echo but this will not always work, unfortunately - it is difficult to be more specific. Here is an example of what I - mean ... + To import such a database, first put the file somewhere useful like + /tmp and then issue the following command ... - timeout 35 - abort (Busy|Sorry|Fail) - connect telnet mary.lancs.ac.uk + dbimport oblast /tmp/OBLAST.FUL + This will update the existing local oblast database or create it if it + does not exist. - So, the first connection is made by Spider. This is fine as Spider - uses the Net_Telnet script from within perl. This actually uses TCP - rather than TELNET so no negotiation will be done on the first - connection. Once connected to mary.lancs.ac.uk, the command is sent - to suppress echo. Now a telnet is made to a cluster node that is - accepting connections on port 23. The problem with this link is that - the negotiation is made by the remote machine, therefore you have no - control over it. The chances are that this link will create echo and - there will be no way you can stop it. + 5.3. Checking available databases + Once a database is created, you will want to check that it has been + added. To do this use the dbavail command. This will output the + available databases. For example ... - 44.. AAuuttoommaattiinngg tthhiinnggss - Ok, you should now have DXSpider running nicely and allowing connects - by cluster nodes or users. However, it has to be shutdown and - restarted manually and if connection scripts fail they have to be - started again manually too, not much use if you are not at the - console! So, in this section we will automate both. Firstly starting - the cluster. + dbavail + DB Name Location Chain + qsl Local + buck GB7ADX + hftest GB7DXM + G0VGS de GB7MBC 3-Feb-2001 1925Z > - 44..11.. AAuuttoossttaarrttiinngg tthhee cclluusstteerr - This is not only a way to start the cluster automatically, it also - works as a watchdog, checking the sanity of DXSpider and respawning it - should it crash for any reason. Before doing the following, shutdown - the cluster as you did earlier. + 5.4. Looking up databases - Login as root and bring up the /etc/inittab file in your favourite - editor. Add the following lines to the file near the end ... + To look for information in a defined database, simply use the dbshow + command, for example ... - ##Start DXSpider on bootup and respawn it should it crash - DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + dbshow buckmaster G0YLM + will show the information for the callsign G0YLM from the buckmaster + database if it exists. To make things more standard for the users you + can add an entry in the Aliases file so that it looks like a standard + show command like this ... - This line works fine for RedHat distributions. It is also fine for - SuSE up to 7.0. From Suse 7.1 you need to add runlevels 2 and 5 like - this ... + Now you can simply use show/buckmaster or an abreviation. - DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7 + 5.5. Removing databases + To delete an existing database you use the dbremove command. For + example ... + dbremove oblast - The line required for Slackware distributions is slightly different. - My thanks to Aurelio, PA3EZL for this information. + would remove the oblast database and its associated datafile from the + system. There are no warnings or recovery possible from this command. + If you remove a database it ceases to exist and would have to be + created from scratch if you still required it. - DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7 + 6. Information, files and useful programs + 6.1. MOTD + One of the more important things a cluster sysop needs to do is to get + information to his users. The simplest way to do this is to have a + banner that is sent to the user on login. This is know as a "message + of the day" or "motd". To set this up, simply create a file in + /spider/data called motd and edit it to say whatever you want. It is + purely a text file and will be sent automatically to anyone logging in + to the cluster. + 6.2. MOTD_NOR + This message of the day file lives in the same directory as the + standard motd file but is only sent to non-registered users. Once + registered they will receive the same message as any other user. - This will automatically start DXSpider on tty7 (ALT-F7) on bootup and - restart it should it crash for any reason. + 6.3. Downtime message - As root type the command _t_e_l_i_n_i_t _q. DXSpider should start up - immediately. You will see the output on tty7 and if you login as - _s_y_s_o_p you should find everything running nicely. + 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 + the user advising them of the fact. This message lives in the + /spider/data directory and is called "offline". Simply create the + file and edit it to say whatever you wish. This file will be sent to + a user attempting to log into the cluster when DXSpider is not + actually running. - So far so good, now to automate script connections... + 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 + new users. To set this up, make a directory under /spider called + packclus. Under this directory you can create files called news or + newuser for example. In fact you can create files with any names you + like. These can be listed by the user with the command .... - 44..22.. TThhee ccrroonnttaabb ffiillee - Login as _s_y_s_o_p and create a file in /spider/local_cmd called crontab. - Edit it with your favourite editor and add a line like this (I have - included a comment) + show/files + They can be read by the user by typing the command .... - # check every 10 minutes to see if gb7xxx is connected and if not - # start a connect job going - 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx') + type news + If the file they want to read is called news. You could also set an + alias for this in the Alias file to allow them just to type news - The callsign involved will be the callsign of the cluster node you are - going to connect to. This will now check every 10 minutes to see if - gb7xxx is connected, if it is then nothing will be done. If it is - not, then a connect attempt will be started. + You can also store other information in this directory, either + directly or nested under directories. One use for this would be to + store DX bulletins such as the OPDX bulletins. These can be listed + and read by the user. To keep things tidy, make a directory under + /spider/packclus called bulletin. Now copy any OPDX or similar + bulletins into it. These can be listed by the user in the same way as + above using the show/files command with an extension for the bulletin + directory you have just created, like this .... - There are probably lots of other things you could use this crontab - file for. If you want to know more about it, look at the DXSpider - website at the cron page where it is explained more fully. + show/files bulletin - 55.. HHoopp ccoonnttrrooll - Starting with version 1.13 there is simple hop control available on a - per node basis. Also it is possible to isolate a network completely so - that you get all the benefits of being on that network, but can't pass - on information from it to any other networks you may be connected to - (or vice versa). + An example would look like this .... - 55..11.. BBaassiicc hhoopp ccoonnttrrooll + sh/files + bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z - In /spider/data you will find a file called hop_table.pl. This is the - file that controls your hop count settings. It has a set of default - hops on the various PC frames and also a set for each node you want to - alter the hops for. You may be happy with the default settings of - course, but this powerful tool can help to protect and improve the - network. The file will look something like this ... + 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, + you can also see the time it was last modified, a good clue as to + whether the file has been updated since you last read it. To read the + file called news you would simply issue the command .... + type news + To look what is in the bulletin directory you issue the command .... + show/files bulletin + opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z + opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z + opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z + opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z + opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z + opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z + opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z + opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z + opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z + opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z + opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z + opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z + opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z + Press Enter to continue, A to abort (16 lines) > + 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) > + 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. 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. - # - # hop table construction - # - package DXProt; + # + # Local Aliases File + # - # default hopcount to use - $def_hopcount = 5; + package CmdAlias; - # some variable hop counts based on message type - %hopcount = - ( - 11 => 10, - 16 => 10, - 17 => 10, - 19 => 10, - 21 => 10, - ); + %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', + ], + ) - # the per node hop control thingy + 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. - %nodehops = - GB7ADX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, + 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. - GB7UDX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - GB7BAA => { - 11 => 5, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - }; - - - - - - Each set of hops is contained within a pair of curly braces and - contains a series of PC frame types. PC11 for example is a DX spot. - The figures here are not exhaustive but should give you a good idea of - how the file works. - - - You can alter this file at any time, including whilst the cluster is - running. If you alter the file during runtime, the command _l_o_a_d_/_h_o_p_s - will bring your changes into effect. - - - - 55..22.. IIssoollaattiinngg nneettwwoorrkkss - - It is possible to isolate networks from each other on a "gateway" node - using the _s_e_t_/_i_s_o_l_a_t_e _<_n_o_d_e___c_a_l_l_> command. - - - The effect of this is to partition an isolated network completely from - another nodes connected to your node. Your node will appear on and - otherwise behave normally on every network to which you are connected, - but data from an isolated network will not cross onto any other - network or vice versa. However all the spot, announce and WWV traffic - and personal messages will still be handled locally (because you are a - real node on all connected networks), that is locally connected users - will appear on all networks and will be able to access and receive - information from all networks transparently. All routed messages will - be sent as normal, so if a user on one network knows that you are a - gateway for another network, he can still still send a talk/announce - etc message via your node and it will be routed across. - - - The only limitation currently is that non-private messages cannot be - passed down isolated links regardless of whether they are generated - locally. This will change when the bulletin routing facility is added. - - - If you use isolate on a node connection you will continue to receive - all information from the isolated partner, however you will not pass - any information back to the isolated node. There are times when you - would like to forward only spots across a link (maybe during a contest - for example). To do this, isolate the node in the normal way and put - in a filter in the /spider/filter/spots directory to override the - isolate. This filter can be very simple and consists of just one line - .... - - - - $in = [ - [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count - ]; - - - - - - There is a lot more on filtering in the next section. - - - 66.. FFiilltteerriinngg ((OOlldd SSttyyllee uuppttoo vv11..4444)) - - Filters can be set for spots, announcements and WWV. You will find - the directories for these under /spider/filter. You will find some - examples in the directories with the suffix _._i_s_s_u_e. There are two - types of filter, one for incoming information and one for outgoing - information. Outgoing filters are in the form _C_A_L_L_S_I_G_N_._p_l and - incoming filters are in the form _i_n___C_A_L_L_S_I_G_N_._p_l. Filters can be set - for both nodes and users. - - - All filters work in basically the same way. There are several - elements delimited by commas. There can be many lines in the filter - and they are read from the top by the program. When writing a filter - you need to think carefully about just what you want to achieve. You - are either going to write a filter to _a_c_c_e_p_t or to _r_e_j_e_c_t. Think of a - filter as having 2 main elements. For a reject filter, you would have - a line or multiple lines rejecting the things you do not wish to - receive and then a default line accepting everything else that is not - included in the filter. Likewise, for an accept filter, you would - have a line or multiple lines accepting the things you wish to receive - and a default line rejecting everthing else. - - - In the example below, a user requires a filter that would only return - SSB spots posted in Europe on the HF bands. This is achieved by first - rejecting the CW section of each HF band and rejecting all of VHF, UHF - etc based on frequency. Secondly, a filter rule is set based on CQ - zones to only accept spots posted in Europe. Lastly, a default filter - rule is set to reject anything outside the filter. - - - - $in = [ - [ 0, 0, 'r', # reject all CW spots - [ - 1800.0, 1850.0, - 3500.0, 3600.0, - 7000.0, 7040.0, - 14000.0, 14100.0, - 18068.0, 18110.0, - 21000.0, 21150.0, - 24890.0, 24930.0, - 28000.0, 28180.0, - 30000.0, 49000000000.0, - ] ,1 ], - [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU - [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else - ]; - - - - - - The actual elements of each filter are described more fully in the - following sections. - - - 66..11.. SSppoottss - - The elements of the Spot filter are .... - - - - [action, field_no, sort, possible_values, hops] - - - - - - There are 3 elements here to look at. Firstly, the action element. - This is very simple and only 2 possible states exist, accept (1) or - drop (0). - - - The second element is the field_no. There are 13 possiblities to - choose from here .... - - - - - - - - - 0 = frequency - 1 = call - 2 = date in unix format - 3 = comment - 4 = spotter - 5 = spotted dxcc country - 6 = spotter's dxcc country - 7 = origin - 8 = spotted itu - 9 = spotted cq - 10 = spotter's itu - 11 = spotter's cq - 12 = callsign of the channel on which the spot has appeared - - - - - - The third element tells us what to expect in the fourth element. - There are 4 possibilities .... - - - - n - numeric list of numbers e.g. [ 1,2,3 ] - r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ] - a - an alphanumeric regex - d - the default rule - - - - - - The fifth element is simply the hops to set in this filter. This - would only be used if the filter was for a node of course and - overrides the hop count in hop_table.pl. - - - So, let's look at an example spot filter. It does not matter in the - example who the filter is to be used for. So, what do we need in the - filter? We need to filter the spots the user/node requires and also - set a default rule for anything else outside the filter. Below is a - simple filter that stops spots arriving from outside Europe. - - - - $in = [ - [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric - [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else - ]; - - - - - - So the filter is wrapped in between a pair of square brackets. This - tells Spider to look in between these limits. Then each line is - contained within its own square brackets and ends with a comma. Lets - look carefully at the first line. The first element is 0 (drop). - Therefore anything we put on this line will not be accepted. The next - element is 4. This means we are filtering by the spotter. The third - element is the letter "a" which tells the program to expect an - alphanumeric expression in the fourth element. The fourth element is - a list of letters separated by the pipe symbol. - - - - What this line does is tell the program to drop any spots posted by - anyone in the USA, Canada or Japan. - - - The second line is the default rule for anything else. The "d" tells - us this and the line simply reads... accept anything else. - - - You can add as many lines as you need to complete the filter but if - there are several lines of the same type it is neater to enclose them - all as one line. An example of this is where specific bands are set. - We could write this like this .... - - - - [ 0,0,'r',[1800.0, 2000.0], 1], - [ 0,0,'r',[10100.0, 10150.0], 1], - [ 0,0,'r',[14000.0, 14350.0], 1], - [ 0,0,'r',[18000.0, 18200.0], 1], - - - - - - But the line below achieves the same thing and is more efficient .... - - - - [ 0, 0, 'r', - [ - 1800.0, 2000.0, # top band - 10100.0, 10150.0, # WARC - 14000.0, 14350.0, # 20m - 18000.0, 18200.0, # WARC - [ ,1 ], - - - - - - - 66..22.. AAnnnnoouunncceemmeennttss - - - - - # This is an example announce or filter allowing only West EU announces - # - # The element list is:- - # 0 - callsign of announcer - # 1 - destination * = all, = routed to the node - # 2 - text - # 3 - * - sysop, - special list eg 6MUK, ' ', normal announce - # 4 - origin - # 5 - 0 - announce, 1 - wx - # 6 - channel callsign (the interface from which this spot came) - - $in = [ - [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ], - [ 0, 0, 'd', 0 ] - ]; - - - - - - In this example, only the prefixes listed will be allowed. It is - possible to be quite specific. The Dutch prefix "P" is followed by - several secondary identifiers which are allowed. So, in the example, - "PA" or "PE" would be ok but not "PG". It is even possible to allow - information from a single callsign. In the example this is DK0WCY, to - allow the posting of his Aurora Beacon. - - - 66..33.. WWWWVV - - - - - # This is an example WWV filter - # - # The element list is:- - # 0 - nominal unix date of spot (ie the day + hour:13) - # 1 - the hour - # 2 - SFI - # 3 - K - # 4 - I - # 5 - text - # 6 - spotter - # 7 - origin - # 8 - incoming interface callsign - - # this one doesn't filter, it just sets the hop count to 6 and is - # used mainly just to override any isolation from WWV coming from - # the internet. - - $in = [ - [ 1, 0, 'd', 0, 6 ] - ]; - - - - - - It should be noted that the filter will start to be used only once a - user/node has logged out and back in again. - - I am not going to spend any more time on these filters now as they - will become more "comprehensive" in the near future. - - - 77.. FFiilltteerriinngg ((NNeeww SSttyyllee vv11..4455 aanndd llaatteerr)) - - 77..11.. GGeenneerraall ffiilltteerr rruulleess - - Upto v1.44 it was not possible for the user to set their own filters. - From v1.45 though that has all changed. It is now possible to set - filters for just about anything you wish. If you have just updated - from an older version of DXSpider you will need to update your new - filters. You do not need to do anything with your old filters, they - will be renamed as you update. - - - There are 3 basic commands involved in setting and manipulating - filters. These are _a_c_c_e_p_t, _r_e_j_e_c_t and _c_l_e_a_r. First we will look - generally at filtering. There are a number of things you can filter in - the DXSpider system. They all use the same general mechanism. - - - In general terms you can create a 'reject' or an 'accept' filter which - can have up to 10 lines in it. You do this using, for example ... - - accept/spots ..... - reject/spots ..... - - - - - where ..... are the specific commands for that type of filter. There - are filters for spots, wwv, announce, wcy and (for sysops) connects. - See each different accept or reject command reference for more - details. - - There is also a command to clear out one or more lines in a filter. - They are ... - - - - clear/spots 1 - clear/spots all - - - - - There is clear/xxxx command for each type of filter. - - - and you can check that your filters have worked by the command ... - - - - - show/filter - - - - - - For now we are going to use spots for the examples, but you can apply - the same principles to all types of filter. - - - 77..22.. TTyyppeess ooff ffiilltteerr - - There are two main types of filter, _a_c_c_e_p_t or _r_e_j_e_c_t. You can use - either to achieve the result you want dependent on your own preference - and which is more simple to do. It is pointless writing 8 lines of - reject filters when 1 accept filter would do the same thing! Each - filter has 10 lines (of any length) which are tried in order. If a - line matches then the action you have specified is taken (ie reject - means ignore it and accept means take it) - - - If you specify reject filters, then any lines that arrive that match - the filter will be dumped but all else will be accepted. If you use - an accept filter, then ONLY the lines in the filter will be accepted - and all else will be dumped. For example if you have a single line - _a_c_c_e_p_t filter ... - - - - accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - - - - - then you will _O_N_L_Y get VHF spots _f_r_o_m or _t_o CQ zones 14, 15 and 16. - - If you set a reject filter like this ... - - - - reject/spots on hf/cw - - - - - Then you will get everything _E_X_C_E_P_T HF CW spots. You could make this - single filter even more flexible. For example, if you are interested - in IOTA and will work it even on CW even though normally you are not - interested in CW, then you could say ... - - - - reject/spots on hf/cw and not info iota - - - - - But in that case you might only be interested in iota and say:- - - - - accept/spots not on hf/cw or info iota - - - - - which achieves exactly the same thing. You should choose one or the - other until you are comfortable with the way it works. You can mix - them if you wish (actually you can have an accept AND a reject on the - same line) but don't attempt this until you are sure you know what you - are doing! - - - You can arrange your filter lines into logical units, either for your - own understanding or simply convenience. Here is an example ... - - - - reject/spots 1 on hf/cw - reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) - - - - - What this does is to ignore all HF CW spots and also rejects any spots - on VHF which don't either originate or spot someone in Europe. - - - This is an example where you would use a line number (1 and 2 in this - case), if you leave the digit out, the system assumes '1'. Digits - '0'-'9' are available. This make it easier to see just what filters - you have set. It also makes it more simple to remove individual - filters, during a contest for example. - - - You will notice in the above example that the second line has - brackets. Look at the line logically. You can see there are 2 - separate sections to it. We are saying reject spots that are VHF or - above _A_P_A_R_T from those in zones 14, 15 and 16 (either spotted there or - originated there). If you did not have the brackets to separate the 2 - sections, then Spider would read it logically from the front and see a - different expression entirely ... - (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 - - - - - The simple way to remember this is, if you use OR - use brackets. - Whilst we are here CASE is not important. 'And BY_Zone' is just the - same as 'and by_zone'. - - As mentioned earlier, setting several filters can be more flexible - than simply setting one complex one. Doing it in this way means that - if you want to alter your filter you can just redefine or remove one - or more lines of it or one line. For example ... - - - - reject/spots 1 on hf/ssb - - - - - would redefine our earlier example, or - - - - clear/spots 1 - - - - - To remove all the filter lines in the spot filter ... - - - - clear/spots all - - - - - - 77..33.. FFiilltteerr ooppttiioonnss - - You can filter in several different ways. The options are listed in - the various helpfiles for accept, reject and filter. - - - 77..44.. DDeeffaauulltt ffiilltteerrss - - Sometimes all that is needed is a general rule for node connects. - This can be done with a node_default filter. This rule will always be - followed, even if the link is isolated, unless another filter is set - specifically. Default rules can be set for nodes and users. They can - be set for spots, announces, WWV and WCY. They can also be used for - hops. An example might look like this ... - - - - accept/spot node_default by_zone 14,15,16,20,33 - set/hops node_default spot 50 - - - - - This filter is for spots only, you could set others for announce, WWV - and WCY. This filter would work for ALL nodes unless a specific - filter is written to override it for a particular node. You can also - set a user_default should you require. It is important to note that - default filters should be considered to be "connected". By this I - mean that should you override the default filter for spots, you need - to add a rule for the hops for spots also. - - - 77..55.. AAddvvaanncceedd ffiilltteerriinngg - - Once you are happy with the results you get, you may like to - experiment. - - - The previous example that filters hf/cw spots and accepts vhf/uhf - spots from EU can be written with a mixed filter, for example ... - - - - rej/spot on hf/cw - acc/spot on 0/30000 - acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16) - - - - - Note that the first filter has not been specified with a number. This - will automatically be assumed to be number 1. In this case, we have - said _r_e_j_e_c_t _a_l_l _H_F _s_p_o_t_s _i_n _t_h_e _C_W _s_e_c_t_i_o_n _o_f _t_h_e _b_a_n_d_s _b_u_t _a_c_c_e_p_t _a_l_l - _o_t_h_e_r_s _a_t _H_F_. _A_l_s_o _a_c_c_e_p_t _a_n_y_t_h_i_n_g _i_n _V_H_F _a_n_d _a_b_o_v_e _s_p_o_t_t_e_d _i_n _o_r _b_y - _o_p_e_r_a_t_o_r_s _i_n _t_h_e _z_o_n_e_s _1_4_, _1_5 _a_n_d _1_6. Each filter slot actually has a - 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE - the accept slot. - - - It was mentioned earlier that after a reject test that doesn't match, - the default for following tests is 'accept', the reverse is true for - 'accept'. In the example what happens is that the reject is executed - first, any non hf/cw spot is passed to the accept line, which lets - through everything else on HF. The next filter line lets through just - VHF/UHF spots from EU. - - - - 88.. OOtthheerr ffiilltteerrss - - 88..11.. FFiilltteerriinngg MMaaiill - - In the /spider/msg directory you will find a file called - badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The - original looks something like this .... - - - - - - - - - - - - - - - - - - # the list of regexes for messages that we won't store having - # received them (bear in mind that we must receive them fully before - # we can bin them) - - - # The format of each line is as follows - - # type source pattern - # P/B/F T/F/O/S regex - - # type: P - private, B - bulletin (msg), F - file (ak1a bull) - # source: T - to field, F - from field, O - origin, S - subject - # pattern: a perl regex on the field requested - - # Currently only type B and P msgs are affected by this code. - # - # The list is read from the top down, the first pattern that matches - # causes the action to be taken. - - # The pattern can be undef or 0 in which case it will always be selected - # for the action specified - - - - package DXMsg; - - @badmsg = ( - ); - - - - - - I think this is fairly self explanatory. It is simply a list of - subject headers that we do not want to pass on to either the users of - the cluster or the other cluster nodes that we are linked to. This is - usually because of rules and regulations pertaining to items for sale - etc in a particular country. - - - 88..22.. FFiilltteerriinngg DDXX ccaalllloouuttss ((DDeepprriiccaatteedd)) - - _F_r_o_m _v_e_r_s_i_o_n _1_._4_7_, _t_h_i_s _m_e_t_h_o_d _i_s _r_e_p_l_a_c_e_d _b_y _t_h_e _c_o_m_m_a_n_d _s_e_t_/_b_a_d_d_x - - - In the same way as mail, there are some types of spot we do not wish - to pass on to users or linked cluster nodes. In the /spider/data - directory you will find a file called baddx.pl.issue. Rename this to - baddx.pl and edit the file. The original looks like this .... - - - - - - - - - - - - - - - - - - # the list of dx spot addresses that we don't store and don't pass on - - - package DXProt; - - @baddx = qw - - FROG - SALE - FORSALE - WANTED - P1RATE - PIRATE - TEST - DXTEST - NIL - NOCALL - ); - - - - - - Again, this is simply a list of names we do not want to see in the - spotted field of a DX callout. - - - - 88..33.. FFiilltteerriinngg wwoorrddss ffrroomm tteexxtt ffiieellddss iinn AAnnnnoouunnccee,, TTaallkk aanndd DDXX ssppoottss - - Create a file in /spider/data called _b_a_d_w_o_r_d_s. The format is quite - simple. Lines beginning with # are ignored so comments can be added. - An example file is below ... - - - - # Below is a list of words we do not wish to see on the cluster - grunge grunged grunging - splodge splodger splodging - grince - fluffle - - - - - Multiple words can be used on the same line as shown. Obviously these - are just examples :-) - - - You can reload the file from the cluster prompt as sysop with - load/badwords. - - - 99.. MMaaiill - - DXSpider deals seamlessly with standard AK1A type mail. It supports - both personal and bulletin mail and the sysop has additional commands - to ensure that mail gets to where it is meant. DXSpider will send - mail almost immediately, assuming that the target is on line. - However, only one mail message is dealt with at any one time. If a - mail message is already being sent or recieved, then the new message - will be queued until it has finished. - - The cluster mail is automatically deleted after 30 days unless the - sysop sets the "keep" flag using the _m_s_g command. - - 99..11.. PPeerrssoonnaall mmaaiill - - Personal mail is sent using the _s_p command. This is actually the - default method of sending mail and so a simple _s for send will do. A - full list of the send commands and options is in the _c_o_m_m_a_n_d _s_e_t - section, so I will not duplicate them here. - - - 99..22.. BBuulllleettiinn mmaaiill - - Bulletin mail is sent by using the _s_b command. This is one of the - most common mistakes users make when sending mail. They send a - bulletin mail with _s or _s_p instead of _s_b and of course the message - never leaves the cluster. This can be rectified by the sysop by using - the _m_s_g command. - - - Bulletin addresses can be set using the Forward.pl file. - - - 99..33.. FFoorrwwaarrdd..ppll - - DXSpider receives all and any mail sent to it without any alterations - needed in files. Because personal and bulletin mail are treated - differently, there is no need for a list of accepted bulletin - addresses. It is necessary, however, to tell the program which links - accept which bulletins. For example, it is pointless sending - bulletins addresses to "UK" to any links other than UK ones. The file - that does this is called forward.pl and lives in /spider/msg. At - default, like other spider files it is named forward.pl.issue. Rename - it to forward.pl and edit the file to match your requirements. The - format is below ... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # - # this is an example message forwarding file for the system - # - # The format of each line is as follows - # - # type to/from/at pattern action destinations - # P/B/F T/F/A regex I/F [ call [, call ...] ] - # - # type: P - private, B - bulletin (msg), F - file (ak1a bull) - # to/from/at: T - to field, F - from field, A - home bbs, O - origin - # pattern: a perl regex on the field requested - # action: I - ignore, F - forward - # destinations: a reference to an array containing node callsigns - # - # if it is non-private and isn't in here then it won't get forwarded - # - # Currently only type B msgs are affected by this code. - # - # The list is read from the top down, the first pattern that matches - # causes the action to be taken. - # - # The pattern can be undef or 0 in which case it will always be selected - # for the action specified - # - # If the BBS list is undef or 0 and the action is 'F' (and it matches the - # pattern) then it will always be forwarded to every node that doesn't have - # it (I strongly recommend you don't use this unless you REALLY mean it, if - # you allow a new link with this on EVERY bull will be forwarded immediately - # on first connection) - # - - package DXMsg; - - @forward = ( - ); - - - - - Simply insert a bulletin address and state in the brackets where you - wish that mail to go. For example, you can see here that mail sent to - "UK" will only be sent to the UK links and not to PA4AB-14. - - - To force the cluster to reread the file use load/forward - - - - 99..44.. TThhee mmssgg ccoommmmaanndd - - The _m_s_g command is a very powerful and flexible tool for the sysop. - It allows the sysop to alter to and from fields and make other changes - to manage the cluster mail. - - Here is a full list of the various options ... - - - - - - - - - - - - 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 waiting 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 - - - - - These commands are simply typed from within the cluster as the sysop - user. - - - 99..55.. MMeessssaaggee ssttaattuuss - - You can check on a message from within the cluster by using the - command _s_t_a_t_/_m_s_g. This will give you additional information on the - message number including which nodes have received it, which node it - was received from and when etc. Here is an example of the output of - the command ... - - - - G0VGS de GB7MBC 28-Jan-2001 1308Z > - stat/msg 6869 - From: GB7DJK - Msg Time: 26-Jan-2001 1302Z - Msgno: 6869 - Origin: GB7DJK - Size: 8012 - Subject: AMSAT 2line KEPS 01025.AMSAT - To: UK - Got it Nodes: GB7BAA, GB7ADX - Private: 0 - Read Confirm: 0 - Times read: 0 - G0VGS de GB7MBC 28-Jan-2001 1308Z > - - - - - - 99..66.. FFiilltteerriinngg mmaaiill - - This is described in the section on _O_t_h_e_r _f_i_l_t_e_r_s so I will not - duplicate it here. - - - 99..77.. DDiissttrriibbuuttiioonn lliissttss - - Distribution lists are simply a list of users to send certain types of - mail to. An example of this is mail you only wish to send to other - sysops. In /spider/msg there is a directory called _d_i_s_t_r_o. You put - any distibution lists in here. For example, here is a file called - SYSOP.pl that caters for the UK sysops. - - - qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX - GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH - GB7DXK GB7DXI GB7DXS) - - - - - Any mail sent to "sysop" would only be sent to the callsigns in this - list. - - - 99..88.. BBBBSS iinntteerrffaaccee - - Spider provides a simple BBS interface. No input is required from the - sysop of the cluster at all. The BBS simply sets the cluster as a BBS - and pushes any required mail to the cluster. No mail can flow from - Spider to the BBS, the interface is one-way. - - - Please be careful not to flood the cluster network with unnecessary - mail. Make sure you only send mail to the clusters that want it by - using the Forward.pl file very carefully. - - - 1100.. DDaattaabbaasseess - - Spider allows the creation of local or remote databases. It supports - chained databases, allowing several different databases to be scanned - with one simple command. Importing of databases is limited at present - to the standard AK1A databases such as OBLAST and the DB0SDX QSL - database but will expand with time. - - - 1100..11.. CCrreeaattiinngg ddaattaabbaasseess - - Creating a database could not be more simple. All the commands are - sent from the cluster prompt as the _s_y_s_o_p user. - - To create a database you use the command _d_b_c_r_e_a_t_e. It can be used in - 3 different ways like so .. - - - - 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. - - - - dbcreate chain [...] - - - - - This creates a chained database entry. The first database will be - scanned, then the second, the third etc... - - - - dbcreate remote - - 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... - - - - dbcreate buckmaster remote gb7dxc - - - - - Remote databases cannot be chained, however, the last database in a - chain can be a remote database. - - - 1100..22.. IImmppoorrttiinngg ddaattaabbaasseess - - The only databases that Spider can currently import are the standard - AK1A databases such as OBLAST or the DB0SDX qsl and address database. - This will be added to with time. - - To import such a database, first put the file somewhere useful like - /tmp and then issue the following command ... - - - - dbimport oblast /tmp/OBLAST.FUL + 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. - This will update the existing local oblast database or create it if it - does not exist. - 1100..33.. CChheecckkiinngg aavvaaiillaabbllee ddaattaabbaasseess + 6.6. Console.pl - Once a database is created, you will want to check that it has been - added. To do this use the _d_b_a_v_a_i_l command. This will output the - available databases. For example ... + 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. - dbavail - DB Name Location Chain - qsl Local - buck GB7ADX - hftest GB7DXM - G0VGS de GB7MBC 3-Feb-2001 1925Z > + 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 ... - 1100..44.. LLooookkiinngg uupp ddaattaabbaasseess + export 5467 /spider/perl/keps.in - To look for information in a defined database, simply use the _d_b_s_h_o_w - command, for example ... + would export message number 5467 as a file called keps.in in the + /spider/perl directory. - dbshow buckmaster G0YLM + 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 ... - will show the information for the callsign G0YLM from the buckmaster - database if it exists. To make things more standard for the users you - can add an entry in the Aliases file so that it looks like a standard - _s_h_o_w command like this ... + ./convkeps.pl keps.in + Now go back to the cluster and issue the command ... + load/keps - Now you can simply use show/buckmaster or an abreviation. - 1100..55.. RReemmoovviinngg ddaattaabbaasseess + That is it! the kepler data has been updated. - To delete an existing database you use the _d_b_r_e_m_o_v_e command. For - example ... + 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. - dbremove oblast + 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. - would remove the oblast database and its associated datafile from the - system. There are no warnings or recovery possible from this command. - If you remove a database it ceases to exist and would have to be - created from scratch if you still required it. + 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. - 1111.. IInnffoorrmmaattiioonn,, ffiilleess aanndd uusseeffuull pprrooggrraammss - 1111..11.. MMOOTTDD + c4:2345:respawn:/sbin/agetty -L 9600 ttyS1 - One of the more important things a cluster sysop needs to do is to get - information to his users. The simplest way to do this is to have a - banner that is sent to the user on login. This is know as a "message - of the day" or "motd". To set this up, simply create a file in - /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. - 1111..22.. DDoowwnnttiimmee mmeessssaaggee + 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. - 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 - the user advising them of the fact. This message lives in the - /spider/data directory and is called "offline". Simply create the - file and edit it to say whatever you wish. This file will be sent to - a user attempting to log into the cluster when DXSpider is not - actually running. + 7. Java Web applet - 1111..33.. OOtthheerr tteexxtt mmeessssaaggeess + 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. - You can set other text messages to be read by the user if they input - the file name. This could be for news items or maybe information for - new users. To set this up, make a directory under /spider called - _p_a_c_k_c_l_u_s. Under this directory you can create files called _n_e_w_s or - _n_e_w_u_s_e_r for example. In fact you can create files with any names you - like. These can be listed by the user with the command .... + 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 ... - show/files + cd /spider/spider-web + rm *.class + /usr/bin/javac spiderclient.java - They can be read by the user by typing the command .... + I have used /usr/bin/javac as an example, your path to javac may be + different. - type news + Spider-WEB v0.6b + Completely based on a clx web client written in Java by dl6dbh + (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz) + The webserver has to run on the same machine as your DxSpider software! + It is assumed that you have Java installed. You need JDK1.3.1 at least. - If the file they want to read is called _n_e_w_s. You could also set an - alias for this in the Alias file to allow them just to type _n_e_w_s + 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. - You can also store other information in this directory, either - directly or nested under directories. One use for this would be to - store DX bulletins such as the OPDX bulletins. These can be listed - and read by the user. To keep things tidy, make a directory under - /spider/packclus called _b_u_l_l_e_t_i_n. Now copy any OPDX or similar - bulletins into it. These can be listed by the user in the same way as - above using the _s_h_o_w_/_f_i_l_e_s command with an extension for the bulletin - directory you have just created, like this .... + 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/ - show/files bulletin + By default the spider.cgi script should pick up your hostname (As long as this + is set correctly). If it does not or your hostname differs from the name that + you attach to the public address that you are using, then edit spider.cgi : + # Uncomment and set the hostname manually here if the above fails. + # $HOSTNAME = "gb7mbc.spoo.org" ; + $PORT = "8000" ; + telnet (see Listeners.pm) + NOTE: If you can start the console but cannot connect to the cluster from it, + then it is possible that the machine you are on cannot resolve the hostname of + your cluster machine. If this is the case, you need to set your hostname + manually as above. - An example would look like this .... + 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 - sh/files - bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z + 8. Web based statistics + From version 1.50, you can use the freeware software MRTG to produce + really nice graphical statistics on your web site. For an example try + http://www.gb7mbc.net/mrtg/stats.html. - You can see that in the files area (basically the packclus directory) - there is a file called _n_e_w_s and a directory called _b_u_l_l_e_t_i_n. You can - also see that dates they were created. In the case of the file _n_e_w_s, - you can also see the time it was last modified, a good clue as to - whether the file has been updated since you last read it. To read the - file called _n_e_w_s you would simply issue the command .... + The following should help you get it all working. + First you need to download the latest version of MRTG from + http://people.ee.ethz.ch/~oetiker/webtools/mrtg/. You will also need + the following files.. - type news + libpng-1.0.14.tar.gz + zlib-1.1.4.tar.gz + gd-1.8.3.tar.gz - To look what is in the bulletin directory you issue the command .... + Login to your machine as the root user, put all the downloaded files + in /usr/local/src/ (or wherever you prefer) and untar and compile + them. All the information to compile and install these sources come + with them. After compilation and installation, you will find MRTG in + /usr/local/mrtg-2. + Now copy all the files in /usr/local/src/mrtg-2.9.22/images/ to + /spider/html/mrtg/ + You now need to make 2 symbolic links like below... - 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) > + ln -s /usr/local/mrtg-2/bin/mrtg /usr/bin/mrtg + ln -s /usr/local/mrtg-2/lib/mrtg2 /usr/lib/mrtg2 - You can now read any file in this directory using the type command, - like this .... + Now login to the cluster with your sysop callsign and run the command + "mrtg all". - 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) > + Now you are nearly there! Login as the sysop user and change to the + /spider/html/mrtg/ directory. Now run the command indexmaker as shown + below... + indexmaker --output stats.html --columns=1 --title "MRTG statistics for GB7DJK" ../../mrtg/mrtg.cfg - The page length will of course depend on what you have it set to! - 1111..44.. TThhee AAlliiaasseess ffiillee + Changing the callsign for your own cluster callsign of course! - 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 ... + And finally you need to login as the root user and create one last + symbolic link. Where this points will depend on where your html + documents are kept. For RedHat systems you use... + ln -s /home/sysop/spider/html/mrtg /home/httpd/html/mrtg + and for SuSE systems... + ln -s /home/sysop/spider/html/mrtg /usr/local/httpd/htdocs/mrtg + If you now point your browser to your website as below it should all + be happening! + http://www.xxx.xxx/mrtg/stats.html - #!/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 + Of course, to get the stats to update, you need to add some + information in the spider crontab file as below... - # 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. + # Update stats for mrtg on website + 00,05,10,15,20,25,30,35,40,45,50,55 * * * * run_cmd('mrtg all') - package CmdAlias; + This will update the site every 5 minutes. - %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' => [ - ], - ) + 9. Security + From version 1.49 DXSpider has some additional security features. + These are not by any means meant to be exhaustive, however they do + afford some security against piracy. These two new features can be + used independently of each other or in concert to tighten the + security. - 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. + 9.1. Registration + The basic principle of registration is simple. If a user is not + registered by the sysop, then they have read-only access to the + cluster. The only thing they can actually send is a talk or a message + to the sysop. In order for them to be able to spot, send announces or + talks etc the sysop must register them with the set/register command, + like this ... - 1111..55.. CCoonnssoollee..ppll - 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. + set/register g0vgs - To edit the colours, copy /spider/perl/Console.pl to /spider/local and - edit the file with your favourite editor. - 1111..66.. UUppddaattiinngg kkeepplleerr ddaattaa + The user g0vgs can now fully use the cluster. In order to enable + registration, you can issue the command ... - 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 _e_x_p_o_r_t command from the cluster prompt as - the sysop. For example ... + set/var $main::reqreg = 1 - export 5467 /spider/perl/keps.in + 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. - would export message number 5467 as a file called keps.in in the - /spider/perl directory. + To unregister a user use unset/register and to show the list of + registered users, use the command show/register. - Now login to a VT as sysop and cd /spider/perl. There is a command in - the perl directory called _c_o_n_v_k_e_p_s_._p_l. All we need to do now is - convert the file like so ... + 9.2. Passwords + At the moment, passwords only affect users who login to a DXSpider + cluster node via telnet. If a user requires a password, they can + either set it themselves or have the sysop enter it for them by using + the set/password command. Any users who already have passwords, such + as remote sysops, will be asked for their passwords automatically by + the cluster. Using passwords in this way means that the user has a + choice on whether to have a password or not. To force the use of + passwords at login, issue the command ... - ./convkeps.pl keps.in + set/var $main::passwdreq = 1 - Now go back to the cluster and issue the command ... + at the cluster prompt. This can also be added to the + /spider/scripts/startup file as above to make the change permanent. - load/keps + 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 ... - That is it! the kepler data has been updated. + unset/password g0vgs + set/password g0vgs new_password - 1111..77.. TThhee QQRRZZ ccaallllbbooookk + 10. CVS - The command _s_h_/_q_r_z 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. - 1122.. CCVVSS + 10.1. CVS from a Linux platform CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your DXSpider installation to the latest sources by using a few simple - commands. - + commands. A graphical interface to CVS for Windows is explained in + the next section. - THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST - INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! THIS - MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! YOU - HAVE BEEN WARNED!!! - - DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE - CONSEQUENCES!!! + Please be aware that if you update your system using CVS, it is + possible that you could be running code that is very beta and not + fully tested. There is a possibility that it could be unstable. I am of course assuming that you have a machine with both DXSpider and @@ -2878,7 +1988,7 @@ steps which are listed below ... - First login as the user _s_y_s_o_p. Next you need to connect to the CVS + First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... @@ -2901,7 +2011,6 @@ If you are wanting to update Spider then cd to /tmp - The next step will create a brand new 'spider' directory in your current directory. @@ -2918,8 +2027,6 @@ finished, you will have exactly the same as if you had untarred a full tarball PLUS some extra directories and files that CVS needs to do the magic that it does. - - Now if you are doing a new installation, that's it. Carry on as if you have just downloaded and untarred the lastest tarball. @@ -2934,7 +2041,6 @@ - This is assuming you downloaded to the /tmp directory of course. @@ -2953,7 +2059,7 @@ Now the magic part! From now on when you want to update, simply - connect to the Internet and then, as the user _s_y_s_o_p ... + connect to the Internet and then, as the user sysop ... @@ -2962,27 +2068,145 @@ - and your files will be updated. As above, remember to recompile the "C" client if it has been updated (CVS will tell you) and restart if any of the perl scripts have been altered or added, again, CVS will tell you. + You will find any changes documented in the /spider/Changes file. - 1133.. TThhee DDXXSSppiiddeerr ccoommmmaanndd sseett + 10.2. CVS from a Windows platform + + After the initial setup, an update to your DXSpider software is no + more than a couple of clicks away. This section is intended to + explain and illustrate the use of the WinCVS application to update + your DXSpider software. The current stable version of WinCVS is Ver. + 1.2. You can get this software at: + + http://prdownloads.sourceforge.net/cvsgui/WinCvs120.zip + + Pick your download mirror and then install WinCVS after the download + is complete. + + + In this next section I have included a series of links to .jpg files + to take advantage of the picture and 1000 words equivalency. The .jpg + files are in the C:\spider\html directory. If someone using a Linux + system is reading this section from boredom, the files are in + /home/sysop/spider/html. One aside, a Linux user can also get a copy + of gcvs and do your updates graphically as opposed to from the command + line. The following descriptions are almost identical between WinCvs + and gcvs. The following screen shots have duplicate links, depending + upon whether you are viewing this information under the Windows or + Linux operating system. + + When WinCVS is installed, running, and you are connected to the + internet, the initial screen looks like: + + initial.jpg + + If you want, you can also look at these .jpg files with another viewer + that might provide some better clarity to the image. On the left is + the directory tree for your hard disk. Notice that the spider + directory has a gray highlight. + + To start configuring WinCVS, click on Admin at the top of the screen + and then Preferences. This should get you: + + pref-gen.jpg + + 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 + + + + 11. The DXSpider command set Below is a complete list of commands available from the cluster prompt. Most maintenance tasks are automatic but there are some commands that are useful for a sysop. These are listed below in alphabetical order. The number in brackets following the command name - is the permissions level needed to use the command. + is the permissions level needed to use the command - 1133..11.. aacccceepptt//aannnnoouunnccee ((00)) + 11.1. accept/announce (0) - aacccceepptt//aannnnoouunnccee [[00--99]] <> Set an accept filter line for announce + accept/announce [0-9] Set an accept filter line for announce Create an 'accept this announce' line for a filter. @@ -2994,8 +2218,6 @@ You can use any of the following things in this line:- - - info eg: iota or qsl by eg: G,M,2 origin @@ -3011,7 +2233,6 @@ - some examples:- @@ -3022,7 +2243,6 @@ - or @@ -3031,20 +2251,21 @@ - This filter would only allow announces that were posted buy UK stations. You can use the tag 'all' to accept everything eg: - acc/ann all + acc/ann all + + but this probably for advanced users... - 1133..22.. aacccceepptt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 11.2. accept/announce (extended for sysops) (8) - aacccceepptt//aannnnoouunnccee <> [[iinnppuutt]] [[00--99]]<> Announce filter sysop + accept/announce [input] [0-9] Announce filter sysop version @@ -3059,11 +2280,56 @@ + 11.3. accept/route (8) + + accept/route [0-9] Set an 'accept' filter line for + routing + + + Create an 'accept this routing PC Protocol' line for a filter. + + + An accept filter line means that if a PC16/17/19/21/24/41/50 matches + this filter it is passed thru that interface. See HELP FILTERING for + more info. Please read this to understand how filters work - it will + save a lot of grief later on. + + + You can use any of the following things in this line:- + + + + call the callsign of the thingy + call_dxcc eg: 61,62 (from eg: sh/pre G) + call_itu + call_zone + origin really the interface it came in on + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + + + + some examples:- + + + + acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes) + acc/route gb7djk call gb7djk (equiv to SET/ISOLATE) - 1133..33.. aacccceepptt//ssppoottss ((00)) - aacccceepptt//aannnnoouunnccee [[00--99]] <> Set an accept filter line for spots + You can use the tag 'all' to accept everything eg: + + + + acc/route all + + + + 11.4. accept/spots (0) + + accept/spots [0-9] Set an accept filter line for spots Create an 'accept this spot' line for a filter. @@ -3073,25 +2339,62 @@ passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on. + + Please read the following section carefully. Though it looks similar, + reformatting, corrections, and hopefully clarifications have been + added. + You can use any of the following things in this line:- - freq 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 - channel + by_zone + + 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' @@ -3100,6 +2403,7 @@ thus: hf/ssb. You can also just have a simple range like: 0/30000 - this is more efficient than saying simply: freq HF (but don't get too hung up about that) + some examples:- @@ -3109,7 +2413,6 @@ - You can use the tag 'all' to accept everything, eg: @@ -3118,13 +2421,12 @@ - but this probably for advanced users... - 1133..44.. aacccceepptt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 11.5. accept/spots (extended for sysops) (8) - aacccceepptt//ssppoottss <> [[iinnppuutt]] [[00--99]] <> Spot filter sysop version + accept/spots [input] [0-9] Spot filter sysop version This version allows a sysop to set a filter for a callsign as well as @@ -3140,11 +2442,9 @@ + 11.6. accept/wcy (0) - - 1133..55.. aacccceepptt//wwccyy ((00)) - - aacccceepptt//wwccyy [[00--99]] <> set an accept WCY filter + accept/wcy [0-9] set an accept WCY filter It is unlikely that you will want to do this, but if you do then you @@ -3164,8 +2464,6 @@ - - There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). @@ -3175,9 +2473,9 @@ See HELP FILTER for information. - 1133..66.. aacccceepptt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 11.7. accept/wcy (extended for sysops) (8) - aacccceepptt//wwccyy <> [[iinnppuutt]] [[00--99]] <> WCY filter sysop version + accept/wcy [input] [0-9] WCY filter sysop version This version allows a sysop to set a filter for a callsign as well as @@ -3190,11 +2488,9 @@ + 11.8. accept/wwv (0) - - 1133..77.. aacccceepptt//wwwwvv ((00)) - - aacccceepptt//wwwwvv [[00--99]] <> Set an accept WWV filter + accept/wwv [0-9] Set an accept WWV filter It is unlikely that you will want to do this, but if you do then you @@ -3214,7 +2510,6 @@ - for example @@ -3223,7 +2518,6 @@ - is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). @@ -3231,10 +2525,9 @@ + 11.9. accept/wwv (extended for sysops) (8) - 1133..88.. aacccceepptt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) - - aacccceepptt//wwwwvv <> [[iinnppuutt]] [[00--99]] <> WWV filter sysop version + accept/wwv [input] [0-9] WWV filter sysop version This version allows a sysop to set a filter for a callsign as well as @@ -3250,20 +2543,20 @@ + 11.10. announce (0) - - 1133..99.. aannnnoouunnccee ((00)) - - aannnnoouunnccee <> Send an announcement to local users + announce Send an announcement to local users Send an announcement to LOCAL users only, where is the text of - the announcement you wish to broadcast + the announcement you wish to broadcast. If you do not wish to receive + announces, use the set/noannounce command. Any announces made by a + sysop will override set/noannounce. - 1133..1100.. aannnnoouunnccee ffuullll ((00)) + 11.11. announce full (0) - aannnnoouunnccee ffuullll <> Send an announcement cluster wide + announce full Send an announcement cluster wide This command will send your announcement across the whole cluster @@ -3271,36 +2564,34 @@ - 1133..1111.. aannnnoouunnccee ssyyssoopp ((55)) + 11.12. announce sysop (5) - aannnnoouunnccee ssyyssoopp <> + announce sysop Send an announcement to Sysops only - 1133..1122.. aapprrooppooss ((00)) + 11.13. apropos (0) - aapprrooppooss <> Search the help database + apropos Search the help database Search the help database for (it isn't case sensitive), and print the names of all the commands that may be relevant. - 1133..1133.. bbyyee ((00)) + 11.14. bye (0) - bbyyee Exit from the cluster + bye Exit from the cluster This will disconnect you from the cluster + 11.15. catchup (5) - - 1133..1144.. ccaattcchhuupp ((55)) - - ccaattcchhuupp <> AAllll||[[<> ......]] Mark a message as sent + catchup All|[ ...] Mark a message as sent When you send messages the fact that you have forwarded it to another @@ -3317,7 +2608,6 @@ - and to undo what you have just done:- @@ -3327,20 +2617,42 @@ - which will arrange for them to be forward candidates again. Order is not important. - 1133..1155.. cclleeaarr//ssppoottss ((00)) + 11.16. clear/announce (8) - cclleeaarr//ssppoottss [[11||aallll]] Clear a spot filter line + clear/announce [input] [0-9|all] Clear an announce filter + line - This command allows you to clear (remove) a line in a spot filter or + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 11.17. clear/route (8) + + clear/route [input] [0-9|all] Clear a route filter line + + + This command allows you to clear (remove) a line in a route filter or to remove the whole filter. + see CLEAR/SPOTS for a more detailed explanation. + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 11.18. clear/spots (0) + + clear/spots [1|all] Clear a spot filter line + + + This command allows you to clear (remove) a line in a spot filter or + to remove the whole filter. If you have a filter:- @@ -3350,7 +2662,6 @@ - and you say:- @@ -3359,13 +2670,11 @@ - you will be left with:- - acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) - + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) @@ -3377,14 +2686,62 @@ - the filter will be completely removed. + 11.19. clear/spots (extended for sysops) (8) + + clear/spots [input] [0-9|all] Clear a spot filter line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 11.20. clear/wcy (0) + + clear/wcy [1|all] Clear a WCY filter line + + + This command allows you to clear (remove) a line in a WCY filter or to + remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. + + + 11.21. clear/wcy (extended for sysops) (8) + + clear/wcy [input] [0-9|all] Clear a WCY filter line + + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 11.22. clear/wwv (0) + + clear/wwv [1|all] Clear a WWV filter line + + + This command allows you to clear (remove) a line in a WWV filter or to + remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. - 1133..1166.. ccoonnnneecctt ((55)) - ccoonnnneecctt <> Start a connection to another DX Cluster + 11.23. clear/wwv (extended for sysops) (8) + + clear/wwv [input] [0-9|all] Clear a WWV filter line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 11.24. connect (5) + + connect Start a connection to another DX Cluster Start a connection process that will culminate in a new connection to @@ -3394,21 +2751,21 @@ cluster . - 1133..1177.. ddbbaavvaaiill ((00)) + 11.25. dbavail (0) - ddbbaavvaaiill Show a list of all the databases in the system + dbavail Show a list of all the databases in the system The title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND. - 1133..1188.. ddbbccrreeaattee ((99)) + 11.26. dbcreate (9) - ddbbccrreeaattee <> Create a database entry - ddbbccrreeaattee <> cchhaaiinn <> [[<>....]] Create a chained database + dbcreate Create a database entry + dbcreate chain [..] Create a chained database entry - ddbbccrreeaattee <> rreemmoottee <> Create a remote database entry + dbcreate remote Create a remote database entry DBCREATE allows you to define a database in the system. It doesn't @@ -3424,12 +2781,12 @@ You can also chain databases with the addition of the 'chain' keyword. This will search each database one after the other. A typical example is: - DBCREATE sdx_qsl chain sql_ad No checking is done to see if the any of the chained databases exist, in fact it is usually better to do the above statement first then do each of the chained databases. + Databases can exist offsite. To define a database that lives on another node do: @@ -3460,7 +2817,6 @@ - to allow SH/BUCK g1tlh @@ -3471,9 +2827,9 @@ databases. See DBSHOW for generic database enquiry - 1133..1199.. ddbbiimmppoorrtt ((99)) + 11.27. dbimport (9) - ddbbiimmppoorrtt <> Import AK1A data into a database + dbimport Import AK1A data into a database If you want to import or update data in bulk to a database you can use @@ -3486,10 +2842,9 @@ oblast database held locally. - 1133..2200.. ddbbrreemmoovvee ((99)) - - ddbbrreemmoovvee <> Delete a database + 11.28. dbremove (9) + dbremove Delete a database DBREMOVE will completely remove a database entry and also delete any data file that is associated with it. @@ -3510,9 +2865,9 @@ You have been warned. - 1133..2211.. ddbbsshhooww ((00)) + 11.29. dbshow (0) - ddbbsshhooww <> <> Display an entry, if it exists, in a database + dbshow Display an entry, if it exists, in a database This is the generic user interface to the database to the database @@ -3526,7 +2881,6 @@ - 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: @@ -3536,12 +2890,9 @@ + 11.30. debug (9) - - - 1133..2222.. ddeebbuugg ((99)) - - ddeebbuugg Set the cluster program into debug mode + debug Set the cluster program into debug mode Executing this command will only have an effect if you are running the @@ -3553,21 +2904,54 @@ - It will interrupt the cluster just after the debug command has finished. + 11.31. delete/user (9) + + delete/user Delete a user from the User Database + + + This command will completely remove a one or more users from the + database. + + There is NO SECOND CHANCE. + + It goes without saying that you should use this command CAREFULLY! + + + 11.32. demonstrate (9) + + demonstrate Demonstrate a command to another user + + + This command is provided so that sysops can demonstrate commands to + other users. It runs a command as though that user had typed it in and + then sends the output to that user, together with the command that + caused it. + + + + DEMO g7brn sh/dx iota oc209 + DEMO g1tlh set/here + + + + 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. + - 1133..2233.. ddiirreeccttoorryy ((00)) + 11.33. directory (0) - ddiirreeccttoorryy List messages - ddiirreeccttoorryy oowwnn List your own messages - ddiirreeccttoorryy nneeww List all new messages - ddiirreeccttoorryy ttoo <> List all messages to - ddiirreeccttoorryy ffrroomm <> List all messages from - ddiirreeccttoorryy ssuubbjjeecctt <> List all messages with in subject - ddiirreeccttoorryy <> List last messages - ddiirreeccttoorryy <>--<> List messages message message + directory List messages + directory own List your own messages + directory new List all new messages + directory to List all messages to + directory from List all messages from + directory subject List all messages with in subject + directory List last messages + directory - List messages message message List the messages in the messages directory. @@ -3588,7 +2972,6 @@ - You can abbreviate all the commands to one letter and use ak1a syntax:- @@ -3599,26 +2982,23 @@ - - - - 1133..2244.. ddiirreeccttoorryy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 11.34. directory (extended for sysops) (5) Works just like the user command except that sysops can see ALL messages. - 1133..2255.. ddiissccoonnnneecctt ((88)) + 11.35. disconnect (8) - ddiissccoonnnneecctt <> [[<> ......]] Disconnect a user or node + disconnect [ ...] Disconnect a user or node Disconnect any connected locally - 1133..2266.. ddxx ((00)) + 11.36. dx (0) - ddxx [[bbyy <>]] <> <> <> Send a DX spot + dx [by ] Send a DX spot This is how you send a DX Spot to other users. You can, in fact, now @@ -3626,12 +3006,9 @@ - - - DX FR0G 144.600 - DX 144.600 FR0G - DX 144600 FR0G - + DX FR0G 144.600 + DX 144.600 FR0G + DX 144600 FR0G @@ -3644,7 +3021,6 @@ - You can credit someone else by saying:- @@ -3653,14 +3029,12 @@ - The is compared against the available bands set up in the cluster. See SHOW/BANDS for more information. + 11.37. export (9) - 1133..2277.. eexxppoorrtt ((99)) - - eexxppoorrtt <> <> Export a message to a file + export Export a message to a file Export a message to a file. This command can only be executed on a @@ -3676,9 +3050,9 @@ EXPORT 2345 /tmp/a - 1133..2288.. eexxppoorrtt__uusseerrss ((99)) + 11.38. export_users (9) - eexxppoorrtt__uusseerrss [[<>]] Export the users database to ascii + export_users [] Export the users database to ascii Export the users database to a file in ascii format. If no filename is @@ -3692,11 +3066,141 @@ check is made on the filename (if any) that you specify. + 11.39. filtering (0) + + filtering Filtering things in DXSpider + + + There are a number of things you can filter in the DXSpider system. + They all use the same general mechanism. + + In general terms you can create a 'reject' or an 'accept' filter which + can have up to 10 lines in it. You do this using, for example:- + + accept/spots ..... reject/spots ..... + + where ..... are the specific commands for that type of filter. There + are filters for spots, wwv, announce, wcy and (for sysops) connects. + See each different accept or reject command reference for more + details. + + There is also a command to clear out one or more lines in a filter and + one to show you what you have set. They are:- + + clear/spots 1 clear/spots all + + and + + show/filter + + There is clear/xxxx command for each type of filter. + + For now we are going to use spots for the examples, but you can apply + the principles to all types of filter. + + There are two main types of filter 'accept' or 'reject'; which you use + depends entirely on how you look at the world and what is least + writing to achieve what you want. Each filter has 10 lines (of any + length) which are tried in order. If a line matches then the action + you have specified is taken (ie reject means ignore it and accept + means gimme it). + + The important thing to remember is that if you specify a 'reject' + filter (all the lines in it say 'reject/spots' (for instance) then if + a spot comes in that doesn't match any of the lines then you will get + it BUT if you specify an 'accept' filter then any spots that don't + match are dumped. For example if I have a one line accept filter:- + + accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + then automatically you will ONLY get VHF spots from or to CQ zones 14 + 15 and 16. If you set a reject filter like: - 1133..2299.. ffoorrwwaarrdd//llaattlloonngg ((88)) + reject/spots on hf/cw - ffoorrwwaarrdd//llaattlloonngg <> Send latitude and longitude information to + Then you will get everything EXCEPT HF CW spots, If you am interested + in IOTA and will work it even on CW then you could say:- + + reject/spots on hf/cw and not info iota + + But in that case you might only be interested in iota and say:- + + accept/spots not on hf/cw or info iota + + which is exactly the same. You should choose one or the other until + you are confortable with the way it works. Yes, you can mix them + (actually you can have an accept AND a reject on the same line) but + don't try this at home until you can analyse the results that you get + without ringing up the sysop for help. + + You can arrange your filter lines into logical units, either for your + own understanding or simply convenience. I have one set frequently:- + + reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone + 14,15,16 or call_zone 14,15,16) + + What this does is to ignore all HF CW spots (being a class B I can't + read any CW and couldn't possibly be interested in HF :-) and also + rejects any spots on VHF which don't either originate or spot someone + in Europe. + + This is an exmaple where you would use the line number (1 and 2 in + this case), if you leave the digit out, the system assumes '1'. Digits + + You can leave the word 'and' out if you want, it is implied. You can + use any number of brackets to make the 'expression' as you want it. + There are things called precedence rules working here which mean that + you will NEED brackets in a situation like line 2 because, without it, + will assume:- + + (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 + + annoying, but that is the way it is. If you use OR - use brackets. + Whilst we are here CASE is not important. 'And BY_Zone' is just 'and + by_zone'. + + If you want to alter your filter you can just redefine one or more + lines of it or clear out one line. For example:- + + reject/spots 1 on hf/ssb + + or + + clear/spots 1 + + To remove the filter in its entirty:- + + clear/spots all + + There are similar CLEAR commands for the other filters:- + + clear/announce clear/wcy clear/wwv + + ADVANCED USERS:- + + Once you are happy with the results you get, you may like to + experiment. + + my example that filters hf/cw spots and accepts vhf/uhf spots from EU + can be written with a mixed filter, eg: + + rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and + (by_zone 14,15,16 or call_zone 14,15,16) + + each filter slot actually has a 'reject' slot and an 'accept' slot. + The reject slot is executed BEFORE the accept slot. + + It was mentioned earlier that after a reject test that doesn't match, + the default for following tests is 'accept', the reverse is true for + first, any non hf/cw spot is passed to the accept line, which lets + thru everything else on HF. + + The next filter line lets through just VHF/UHF spots from EU. + + + 11.40. forward/latlong (8) + + forward/latlong Send latitude and longitude information to another cluster @@ -3704,13 +3208,13 @@ your cluster is holding against callsigns. One advantage of recieving this information is that more locator information is held by you. This means that more locators are given on the DX line assuming you - have _s_e_t_/_d_x_g_r_i_d enabled. This could be a LOT of information though, + have set/dxgrid enabled. This could be a LOT of information though, so it is not recommended on slow links. - 1133..3300.. ffoorrwwaarrdd//ooppeerrnnaammee ((11)) + 11.41. forward/opername (1) - ffoorrwwaarrdd//ooppeerrnnaammee <> Send out information on this to all + forward/opername Send out information on this to all clusters @@ -3720,9 +3224,10 @@ available. - 1133..3311.. hheellpp ((00)) + 11.42. help (0) + + help Get help on a command - hheellpp <> Get help on a command All commands can be abbreviated, so SHOW/DX can be abbreviated to @@ -3733,9 +3238,9 @@ commands to look at with HELP. - 1133..3322.. iinniitt ((55)) + 11.43. init (5) - iinniitt <> Re-initialise a link to an AK1A compatible node + init Re-initialise a link to an AK1A compatible node This command attempts to re-initialise a link to a (usually) AK1A node @@ -3747,9 +3252,9 @@ Best of luck - you will need it. - 1133..3333.. kkiillll ((00)) + 11.44. kill (0) - kkiillll <> [[<> ....]] Delete a message from the local system + kill [ ..] Delete a message from the local system Delete a message from the local system. You will only be able to @@ -3757,14 +3262,11 @@ the sysop). + 11.45. kill (5) - - - 1133..3344.. kkiillll ((55)) - - kkiillll <> [[<> ......]] Remove or erase a message from the system - kkiillll ffrroomm <> Remove all messages from a callsign - kkiillll ttoo <> Remove all messages to a callsign + kill [ ...] Remove or erase a message from the system + kill from Remove all messages from a callsign + kill to Remove all messages to a callsign You can get rid of any message to or originating from your callsign @@ -3773,9 +3275,9 @@ As a sysop you can kill any message on the system. - 1133..3355.. kkiillll ffuullll ((55)) + 11.46. kill full (5) - kkiillll ffuullll <> [[<>]] Delete a message from the whole cluster + kill full [] Delete a message from the whole cluster Delete a message (usually a 'bulletin') from the whole cluster system. @@ -3784,40 +3286,46 @@ same subject will be deleted. Beware! - 1133..3366.. lliinnkkss ((00)) + 11.47. kill/expunge (6) - lliinnkkss Show which nodes are physically connected + kill/expunge [..]Expunge a message - This is a quick listing that shows which links are connected and some - information about them. See WHO for a list of all connections. + 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. - 1133..3377.. llooaadd//aalliiaasseess ((99)) + It otherwise is used in the same way as the KILL command. - llooaadd//aalliiaasseess Reload the command alias table - Reload the /spider/cmd/Aliases file after you have editted it. You - will need to do this if you change this file whilst the cluster is - running in order for the changes to take effect. + 11.48. links (0) + + links Show which nodes are physically connected + + This is a quick listing that shows which links are connected and some + information about them. See WHO for a list of all connections. - 1133..3388.. llooaadd//bbaaddddxx ((99)) - llooaadd//bbaaddddxx Reload the bad DX table + 11.49. load/aliases (9) + load/aliases Reload the command alias table - Reload the /spider/data/baddx.pl file if you have changed it manually - whilst the cluster is running. This table contains the DX Calls that, - if spotted, will not be passed on. FR0G and TEST are classic examples. + + Reload the /spider/cmd/Aliases file after you have editted it. You + will need to do this if you change this file whilst the cluster is + running in order for the changes to take effect. - 1133..3399.. llooaadd//bbaaddmmssgg ((99)) + 11.50. load/badmsg (9) - llooaadd//bbaaddmmssgg Reload the bad message table + load/badmsg Reload the bad message table Reload the /spider/msg/badmsg.pl file if you have changed it manually @@ -3826,9 +3334,10 @@ each message. If any of them match then that message is immediately deleted on receipt. - 1133..4400.. llooaadd//bbaaddwwoorrddss ((99)) - llooaadd//bbaaddwwoorrddss Reload the badwords file + 11.51. load/badwords (9) + + load/badwords Reload the bad words table Reload the /spider/data/badwords file if you have changed it manually @@ -3840,19 +3349,18 @@ ignored. - 1133..4411.. llooaadd//bbaannddss ((99)) + 11.52. load/bands (9) - llooaadd//bbaannddss Reload the band limits table + load/bands Reload the band limits table Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running. - 1133..4422.. llooaadd//ccmmdd__ccaacchhee ((99)) - - llooaadd//ccmmdd__ccaacchhee Reload the automatic command cache + 11.53. load/cmd_cache (9) + load/cmd_cache Reload the automatic command cache Normally, if you change a command file in the cmd or local_cmd tree it will automatially be picked up by the cluster program. Sometimes it @@ -3862,17 +3370,17 @@ was just after a cluster restart. - 1133..4433.. llooaadd//ffoorrwwaarrdd ((99)) + 11.54. load/forward (9) - llooaadd//ffoorrwwaarrdd Reload the msg forwarding routing table + load/forward Reload the msg forwarding routing table Reload the /spider/msg/forward.pl file if you have changed it manually whilst the cluster is running. - 1133..4444.. llooaadd//mmeessssaaggeess ((99)) + 11.55. load/messages (9) - llooaadd//mmeessssaaggeess Reload the system messages file + load/messages Reload the system messages file If you change the /spider/perl/Messages file (usually whilst @@ -3883,18 +3391,18 @@ unknown message 'xxxx' in lang 'en' - 1133..4455.. llooaadd//pprreeffiixxeess ((99)) + 11.56. load/prefixes (9) - llooaadd//pprreeffiixxeess Reload the prefix table + load/prefixes Reload the prefix table Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running. - 1133..4466.. mmeerrggee ((55)) + 11.57. merge (5) - mmeerrggee <> [[<>//<>]] Ask for the latest spots and WWV + merge [/] Ask for the latest spots and WWV MERGE allows you to bring your spot and wwv database up to date. By @@ -3907,9 +3415,9 @@ data). - 1133..4477.. mmssgg ((99)) + 11.58. msg (9) - mmssgg <> <> [[ddaattaa ......]] Alter various message parameters + msg [data ...] Alter various message parameters Alter message parameters like To, From, Subject, whether private or @@ -3918,21 +3426,20 @@ - 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 @@ -3943,9 +3450,9 @@ This will display more information on the message than DIR does. - 1133..4488.. ppcc ((88)) + 11.59. pc (8) - ppcc <> <> Send text (eg PC Protocol) to + pc Send text (eg PC Protocol) to Send some arbitrary text to a locally connected callsign. No @@ -3958,12 +3465,13 @@ You can also use in the same way as a talk command to a connected user but without any processing, added of "from to " or whatever. + pc G1TLH Try doing that properly!!! - 1133..4499.. ppiinngg ((11)) + 11.60. ping (1) - ppiinngg <> Check the link quality between nodes + ping Check the link quality between nodes his command allows you to send a frame to another cluster node on the @@ -3974,24 +3482,25 @@ - 1133..5500.. rrccmmdd ((11)) + 11.61. rcmd (1) - rrccmmdd <> <> Send a command to another DX cluster + rcmd 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. - 1133..5511.. rreeaadd ((00)) + 11.62. read (0) - rreeaadd Read the next unread personal message addressed to you - rreeaadd <> Read the specified message + read Read the next unread personal message addressed to you + read Read the specified message You can read any messages that are sent as 'non-personal' and also any @@ -3999,17 +3508,17 @@ - 1133..5522.. rreeaadd ((eexxtteennddeedd ffoorr ssyyssooppss)) ((55)) + 11.63. read (extended for sysops) (5) - rreeaadd <> Read a message on the system + read Read a message on the system As a sysop you may read any message on the system - 1133..5533.. rreejjeecctt//aannnnoouunnccee + 11.64. reject/announce - rreejjeecctt//aannnnoouunnccee [[00--99]] <> Set a reject filter for announce + reject/announce [0-9] Set a reject filter for announce Create an 'reject this announce' line for a filter. @@ -4023,20 +3532,18 @@ - - info eg: iota or qsl - 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 - wx 1 filter WX announces - dest eg: 6MUK,WDX (distros) - + info eg: iota or qsl + 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 + wx 1 filter WX announces + dest eg: 6MUK,WDX (distros) @@ -4048,7 +3555,6 @@ - You can use the tag 'all' to reject everything eg: @@ -4057,13 +3563,12 @@ - but this probably for advanced users... - 1133..5544.. rreejjeecctt//aannnnoouunnccee ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 11.65. reject/announce (extended for sysops) (8) - rreejjeecctt//aannnnoouunnccee <> [[iinnppuutt]] [[00--99]] <> Announce filter sysop + reject/announce [input] [0-9] Announce filter sysop version @@ -4078,11 +3583,53 @@ + 11.66. reject/route (8) + + reject/route [0-9] Set an 'reject' filter line for + routing + + + Create an 'reject this routing PC Protocol' line for a filter. + + + An reject filter line means that if a PC16/17/19/21/24/41/50 matches + this filter it is NOT passed thru that interface. See HELP FILTERING + for more info. Please read this to understand how filters work - it + will save a lot of grief later on. You can use any of the following + things in this line:- + + + + call the callsign of the thingy + call_dxcc eg: 61,62 (from eg: sh/pre G) + call_itu + call_zone + origin really the interface it came in on + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu + origin_zone + + + + some examples:- + + + + rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes) + + + + You can use the tag 'all' to reject everything eg: + + + + rej/route all (equiv to [very] restricted mode) - 1133..5555.. rreejjeecctt//ssppoottss ((00)) - rreejjeecctt//ssppoottss [[00--99]] <> Set a reject filter line for spots + 11.67. reject/spots (0) + + reject/spots [0-9] Set a reject filter line for spots Create a 'reject this spot' line for a filter. @@ -4112,7 +3659,6 @@ - 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 - @@ -4128,7 +3674,6 @@ - You can use the tag 'all' to reject everything eg: @@ -4137,38 +3682,31 @@ - but this probably for advanced users... - 1133..5566.. rreejjeecctt//ssppoottss ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 11.68. reject/spots (extended for sysops) (8) - rreejjeecctt//ssppoottss <> [[iinnppuutt]] [[00--99]] <> Reject spot filter sysop + reject/spots [input] [0-9] Reject spot filter sysop version - This version allows a sysop to set a filter for a callsign as well as - the default for nodes and users eg:- - - - - - - + This version allows a sysop to set a filter for a callsign as well as + the default for nodes and users eg:- - reject/spot db0sue-7 1 by_zone 14,15,16 - reject/spot node_default all - set/hops node_default 10 - reject/spot user_default by G,M,2 + reject/spot db0sue-7 1 by_zone 14,15,16 + reject/spot node_default all + set/hops node_default 10 + reject/spot user_default by G,M,2 - 1133..5577.. rreejjeecctt//wwccyy ((00)) + 11.69. reject/wcy (0) - rreejjeecctt//wwccyy [[00--99]] <> Set a reject WCY filter + reject/wcy [0-9] Set a reject WCY filter It is unlikely that you will want to do this, but if you do then you @@ -4188,7 +3726,6 @@ - There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). @@ -4198,9 +3735,10 @@ See HELP FILTER for information. - 1133..5588.. rreejjeecctt//wwccyy ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) - rreejjeecctt//wwccyy <> [[iinnppuutt]] [[00--99]] <> WCY reject filter sysop + 11.70. reject/wcy (extended for sysops) (8) + + reject/wcy [input] [0-9] WCY reject filter sysop version @@ -4210,9 +3748,9 @@ reject/wcy gb7djk all - 1133..5599.. rreejjeecctt//wwwwvv ((00)) + 11.71. reject/wwv (0) - rreejjeecctt//wwwwvv [[00--99]] <> Set a reject WWV filter + reject/wwv [0-9] Set a reject WWV filter It is unlikely that you will want to do this, but if you do then you @@ -4220,18 +3758,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 @@ -4243,16 +3778,15 @@ - is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US). See HELP FILTER for information. - 1133..6600.. rreejjeecctt//wwwwvv ((eexxtteennddeedd ffoorr ssyyssooppss)) ((88)) + 11.72. reject/wwv (extended for sysops) (8) - rreejjeecctt//wwwwvv <> [[iinnppuutt]] [[00--99]] <> WWV reject filter sysop + reject/wwv [input] [0-9] WWV reject filter sysop version @@ -4266,17 +3800,13 @@ reject/wwv user_default by W + 11.73. reply (0) - - - - 1133..6611.. rreeppllyy ((00)) - - rreeppllyy Reply (privately) to the last message that you have read - rreeppllyy <> Reply (privately) to the specified message - rreeppllyy BB <> Reply as a Bulletin to the specified message - rreeppllyy NNOOPPrriivvaattee <> Reply as a Bulletin to the specified message - rreeppllyy RRRR <> Reply to the specified message with read receipt + reply Reply (privately) to the last message that you have read + reply Reply (privately) to the specified message + reply B Reply as a Bulletin to the specified message + reply NOPrivate Reply as a Bulletin to the specified message + reply RR Reply to the specified message with read receipt You can reply to a message and the subject will automatically have @@ -4287,14 +3817,13 @@ further details) + 11.74. send (0) - 1133..6622.. sseenndd ((00)) - - sseenndd <> [[<> ......]] Send a message to one or more callsigns - sseenndd RRRR <> Send a message and ask for a read receipt - sseenndd CCOOPPYY <> <> Send a copy of a message to someone - sseenndd PPRRIIVVAATTEE <> Send a personal message - sseenndd NNOOPPRRIIVVAATTEE <> Send a message to all stations + send [ ...] Send a message to one or more callsigns + send RR Send a message and ask for a read receipt + send COPY Send a copy of a message to someone + send PRIVATE Send a personal message + send NOPRIVATE Send a message to all stations All the SEND commands will create a message which will be sent either @@ -4314,7 +3843,6 @@ - which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message. @@ -4322,38 +3850,36 @@ is an alias for SEND PRIVATE - 1133..6633.. sseett//aaddddrreessss ((00)) + 11.75. set/address (0) - sseett//aaddddrreessss <> Record your postal address + set/address Record your postal address Literally, record your address details on the cluster. - 1133..6644.. sseett//aannnnoouunnccee ((00)) + 11.76. set/announce (0) - sseett//aannnnoouunnccee Allow announce messages + set/announce Allow announce messages Allow announce messages to arrive at your terminal. + 11.77. set/arcluster (5) - 1133..6655.. sseett//aarrcclluusstteerr ((55)) - - sseett//aarrcclluusstteerr <> [[<> ......]] Make the node_call an AR- + set/arcluster [ ...] Make the node_call an AR- Cluster type node Set the node_call as an AR-Cluster type node - 1133..6666.. sseett//bbaaddddxx ((88)) + 11.78. set/baddx (8) - sseett//bbaaddddxx <> Stop words we do not wish to see in the callsign + set/baddx 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. @@ -4366,7 +3892,6 @@ - To allow a word again, use the following command ... @@ -4375,11 +3900,9 @@ + 11.79. set/badnode (6) - - 1133..6677.. sseett//bbaaddnnooddee ((66)) - - sseett//bbaaddnnooddee <> Stop spots from this node_call being + set/badnode Stop spots from this node_call being propagated @@ -4395,7 +3918,6 @@ - will stop anything from K1TTT (including any SSID's) @@ -4404,16 +3926,15 @@ - will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. - 1133..6688.. sseett//bbaaddssppootttteerr ((88)) + 11.80. set/badspotter (8) - sseett//bbaaddssppootttteerr <> Stop spots from this callsign being propagated + set/badspotter Stop spots from this callsign being propagated Setting a callsign as a 'badspotter' will prevent spots from this @@ -4428,7 +3949,6 @@ - will stop anything from VE2STN. If you want SSIDs as well then you must enter them specifically. @@ -4438,76 +3958,99 @@ - will allow spots from him again. Use with extreme care. This command may well be superceded by FILTERing. - 1133..6699.. sseett//bbeeeepp ((00)) + 11.81. set/badword (8) + + set/badword 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 - sseett//bbeeeepp Add beeps to terminal messages + will allow text with this word again. + + 11.82. set/beep (0) + + set/beep Add beeps to terminal messages + Add a beep to DX and other terminal messages. - 1133..7700.. sseett//ccllxx ((55)) + 11.83. set/bbs (5) + + set/bbs [..]Make a BBS - sseett//ccllxx <> [[<> ......]] Make the node_call a CLX type + + 11.84. set/clx (5) + + set/clx [ ...] Make the node_call a CLX type node Set the node_call as a CLX type node - 1133..7711.. sseett//ddeebbuugg ((99)) + 11.85. set/debug (9) - sseett//ddeebbuugg <> Add a debug level to the debug set + set/debug Add a debug level to the debug set You can choose to log several different levels. The levels are chan state msg cron connect - You can show what levels you are logging with the _s_h_o_w_/_d_e_b_u_g command. + You can show what levels you are logging with the show/debug command. You can remove a debug level with unset/debug - 1133..7722.. sseett//ddxx ((00)) - - sseett//ddxxAllow DX messages to arrive at your terminal - + 11.86. set/dx (0) - You can stop DX messages with the _u_n_s_e_t_/_d_x command + set/dxAllow DX messages to arrive at your terminal + You can stop DX messages with the unset/dx command - 1133..7733.. sseett//ddxxggrriidd ((00)) + 11.87. set/dxgrid (0) - sseett//ddxxggrriiddAllow grid squares on the end of DX messages + set/dxgridAllow grid squares on the end of DX messages Some logging programs do not like the additional information at the - end of a DX spot. If this is the case, use the _u_n_s_e_t_/_d_x_g_r_i_d command + end of a DX spot. If this is the case, use the unset/dxgrid command to remove the grid squares. - 1133..7744.. sseett//ddxxnneett ((55)) + 11.88. set/dxnet (5) - sseett//ddxxnneett <> [[<> ......]] Make the node_call a DXNet + set/dxnet [ ...] Make the node_call a DXNet type node Set the node_call as a DXNet type node - 1133..7755.. sseett//eecchhoo ((00)) + 11.89. set/echo (0) - sseett//eecchhoo Make the cluster echo your input + set/echo Make the cluster echo your input If you are connected via a telnet session, different implimentations @@ -4515,27 +4058,47 @@ connected via port 23 or some other port. You can use this command to change the setting appropriately. - You can remove the echo with the _u_n_s_e_t_/_e_c_h_o command + You can remove the echo with the unset/echo command The setting is stored in your user profile. YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 1133..7766.. sseett//hheerree ((00)) + 11.90. set/email (0) - sseett//hheerree Set the here flag + set/email Set email address(es) and forward your + personals + + + If any personal messages come in for your callsign then you can use + these commands to control whether they are forwarded onto your email + address. To enable the forwarding do something like:- + + SET/EMAIL mike.tubby@somewhere.com + + You can have more than one email address (each one separated by a + space). Emails are forwarded to all the email addresses you specify. + + You can disable forwarding by:- + + UNSET/EMAIL + + + 11.91. set/here (0) + + set/here Set the here flag Let others on the cluster know you are here by only displaying your callsign. If you are away from your terminal you can use the - _u_n_s_e_t_/_h_e_r_e command to let people know you are away. This simply puts + unset/here command to let people know you are away. This simply puts brackets around your callsign to indicate you are not available. - 1133..7777.. sseett//hhoommeennooddee ((00)) + 11.92. set/homenode (0) - sseett//hhoommeennooddee <> Set your home cluster + set/homenode Set your home cluster Tell the cluster system where you normally connect to. Any Messages @@ -4548,36 +4111,28 @@ + 11.93. set/hops (8) - - - - 1133..7788.. sseett//hhooppss ((88)) - - sseett//hhooppss <> aannnn||ssppoottss||wwwwvv||wwccyy <> Set hop count + set/hops ann|spots|wwv|wcy Set hop count Set the hop count for a particular type of broadcast for a node. This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts. - - - eg: set/hops gb7djk ann 10 set/hops gb7mbc spots 20 - Set SHOW/HOPS for information on what is already set. This command creates a filter and works in conjunction with the filter system. - 1133..7799.. sseett//iissoollaattee ((99)) + 11.94. set/isolate (9) - sseett//iissoollaattee <> Isolate a node from the rest of the network + set/isolate Isolate a node from the rest of the network Connect a node to your system in such a way that you are a full @@ -4593,22 +4148,22 @@ You can remove the isolation with the command unset/isolate. - 1133..8800.. sseett//llaanngguuaaggee ((00)) + 11.95. set/language (0) - sseett//llaanngguuaaggee <> Set the language you wish to use + set/language Set the language you wish to use You can select the language that you want the cluster to use. - Currently the languages available are _e_n (English) and _n_l (Dutch). + Currently the languages available are en (English) and nl (Dutch). - 1133..8811.. sseett//llooccaattiioonn ((00)) + 11.96. set/location (0) - sseett//llooccaattiioonn <> Set your latitude and longitude + set/location Set your latitude and longitude You can set your latitude and longitude manually or alternatively use - the _s_e_t_/_q_r_a command which will do the conversion for you. + the set/qra command which will do the conversion for you. @@ -4616,11 +4171,9 @@ + 11.97. set/sys_location (9) - - 1133..8822.. sseett//ssyyss__llooccaattiioonn ((99)) - - sseett//ssyyss__llooccaattiioonn <> Set your cluster latitude and longitude + set/sys_location Set your cluster latitude and longitude In order to get accurate headings and such like you must tell the @@ -4629,35 +4182,32 @@ example:- - SET/LOCATION 52 22 N 0 57 E + 11.98. set/logininfo (0) - - 1133..8833.. sseett//llooggiinniinnffoo ((00)) - - sseett//llooggiinniinnffoo Show logins and logouts of nodes and users + set/logininfo Show logins and logouts of nodes and users Show users and nodes when they log in and out of the local cluster. - You can stop these messages by using the _u_n_s_e_t_/_l_o_g_i_n_i_n_f_o command. + You can stop these messages by using the unset/logininfo command. - 1133..8844.. sseett//lloocckkoouutt ((99)) + 11.99. set/lockout (9) - sseett//lloocckkoouutt <> Stop a callsign connecting to the cluster + set/lockout Stop a callsign connecting to the cluster - You can show who is locked out with the _s_h_o_w_/_l_o_c_k_o_u_t command. To - allow the user to connect again, use the _u_n_s_e_t_/_l_o_c_k_o_u_t command. + You can show who is locked out with the show/lockout command. To + allow the user to connect again, use the unset/lockout command. - 1133..8855.. sseett//nnaammee ((00)) + 11.100. set/name (0) - sseett//nnaammee <> Set your name + set/name Set your name Tell the cluster what your name is, eg:- @@ -4668,11 +4218,9 @@ + 11.101. set/node (9) - - 1133..8866.. sseett//nnooddee ((99)) - - sseett//nnooddee <> [[<> ......]] Make the callsign an AK1A cluster + set/node [ ...] Make the callsign an AK1A cluster Tell the system that the call(s) are to be treated as AK1A cluster and @@ -4682,22 +4230,20 @@ + 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 _s_h_o_w_/_n_o_d_e_s command. + 11.102. set/obscount (9) - - 1133..8877.. sseett//oobbssccoouunntt ((99)) - - sseett//oobbssccoouunntt <> <> Set the 'pump-up' obsolescence + set/obscount Set the 'pump-up' obsolescence counter @@ -4716,9 +4262,9 @@ minutes, it is disconnected. - 1133..8888.. sseett//ppaaggee ((00)) + 11.103. set/page (0) - sseett//ppaaggee <> Set the number of lines per page + set/page Set the number of lines per page Tell the system how many lines you wish on a page when the number of @@ -4732,27 +4278,53 @@ - The setting is stored in your user profile. + 11.104. set/password (0) + + set/password Set your own password + + + This command only works for a 'telnet' user (currently). It will only + work if you have a password already set. This initial password can + only be set by the sysop. + + 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. + - 1133..8899.. sseett//ppaasssswwoorrdd ((99)) + 11.105. set/password (9) - sseett//ppaasssswwoorrdd <> <> Set a users password + set/password 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: - 1133..9900.. sseett//ppiinnggiinntteerrvvaall ((99)) + set/var $main::passwdreq = 1 - sseett//ppiinnggiinntteerrvvaall <> <> Set the ping time to neighbouring + command is executed in the startup script, then a password prompt is + given after the normal 'login: ' prompt. + + The command "unset/password" is provided to allow a sysop to remove a + users password completely in case a user forgets or loses their + password. + + + 11.106. set/pinginterval (9) + + set/pinginterval