X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=txt%2Fadminmanual.txt;h=d82170ac182f5bf0d33125d5e0958d7c5488ebce;hb=b1d4f4f651821a3ecefdd59ddb09ce9d190b66d6;hp=cca9536bcbde93601608dda1c21ea8456b6b86a5;hpb=1cbfebb5c8503d55f0c03545be1f7be172376dfb;p=spider.git diff --git a/txt/adminmanual.txt b/txt/adminmanual.txt index cca9536b..d82170ac 100644 --- a/txt/adminmanual.txt +++ b/txt/adminmanual.txt @@ -1,6 +1,6 @@ - The DXSpider Administration Manual v1.47 + The DXSpider Administration Manual v1.48 Ian Maude, G0VGS, (ianmaude@btinternet.com) - Version 1.47 April 2001 revision 1.0 + Version 1.49 November 2001 revision 1.1 A reference for SysOps of the DXSpider DXCluster program. ______________________________________________________________________ @@ -64,59 +64,63 @@ - 1. Hop control + 1. Routing and Filtering - 1.1 Basic hop control - 1.2 Isolating networks + 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. Filtering (Old Style upto v1.44) + 2. Other filters - 2.1 Spots - 2.2 Announcements - 2.3 WWV + 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. Filtering (New Style v1.45 and later) + 3. Mail - 3.1 General filter rules - 3.2 Types of filter - 3.3 Filter options - 3.4 Default filters - 3.5 Advanced filtering + 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. Other filters + 4. Scripts - 4.1 Filtering Mail - 4.2 Filtering DX callouts (Depricated) - 4.3 Filtering words from text fields in Announce, Talk and DX spots + 5. Databases - 5. Mail + 5.1 Creating databases + 5.2 Importing databases + 5.3 Checking available databases + 5.4 Looking up databases + 5.5 Removing databases - 5.1 Personal mail - 5.2 Bulletin mail - 5.3 Forward.pl - 5.4 The msg command - 5.5 Message status - 5.6 Filtering mail - 5.7 Distribution lists - 5.8 BBS interface + 6. Information, files and useful programs - 6. Databases + 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.1 Creating databases - 6.2 Importing databases - 6.3 Checking available databases - 6.4 Looking up databases - 6.5 Removing databases + 7. Security - 7. Information, files and useful programs - - 7.1 MOTD - 7.2 Downtime message - 7.3 Other text messages - 7.4 The Aliases file - 7.5 Console.pl - 7.6 Updating kepler data - 7.7 The QRZ callbook + 7.1 Registration + 7.2 Passwords 8. CVS @@ -124,588 +128,427 @@ 9.1 accept/announce (0) 9.2 accept/announce (extended for sysops) (8) - 9.3 accept/spots (0) - 9.4 accept/spots (extended for sysops) (8) - 9.5 accept/wcy (0) - 9.6 accept/wcy (extended for sysops) (8) - 9.7 accept/wwv (0) - 9.8 accept/wwv (extended for sysops) (8) - 9.9 announce (0) - 9.10 announce full (0) - 9.11 announce sysop (5) - 9.12 apropos (0) - 9.13 bye (0) - 9.14 catchup (5) - 9.15 clear/spots (0) - 9.16 connect (5) - 9.17 dbavail (0) - 9.18 dbcreate (9) - 9.19 dbimport (9) - 9.20 dbremove (9) - 9.21 dbshow (0) - 9.22 debug (9) - 9.23 directory (0) - 9.24 directory (extended for sysops) (5) - 9.25 disconnect (8) - 9.26 dx (0) - 9.27 export (9) - 9.28 export_users (9) - 9.29 forward/latlong (8) - 9.30 forward/opername (1) - 9.31 help (0) - 9.32 init (5) - 9.33 kill (0) - 9.34 kill (5) - 9.35 kill full (5) - 9.36 links (0) - 9.37 load/aliases (9) - 9.38 load/baddx (9) - 9.39 load/badmsg (9) - 9.40 load/badwords (9) - 9.41 load/bands (9) - 9.42 load/cmd_cache (9) - 9.43 load/forward (9) - 9.44 load/messages (9) - 9.45 load/prefixes (9) - 9.46 merge (5) - 9.47 msg (9) - 9.48 pc (8) - 9.49 ping (1) - 9.50 rcmd (1) - 9.51 read (0) - 9.52 read (extended for sysops) (5) - 9.53 reject/announce - 9.54 reject/announce (extended for sysops) (8) - 9.55 reject/spots (0) - 9.56 reject/spots (extended for sysops) (8) - 9.57 reject/wcy (0) - 9.58 reject/wcy (extended for sysops) (8) - 9.59 reject/wwv (0) - 9.60 reject/wwv (extended for sysops) (8) - 9.61 reply (0) - 9.62 send (0) - 9.63 set/address (0) - 9.64 set/announce (0) - 9.65 set/arcluster (5) - 9.66 set/baddx (8) - 9.67 set/badnode (6) - 9.68 set/badspotter (8) - 9.69 set/beep (0) - 9.70 set/clx (5) - 9.71 set/debug (9) - 9.72 set/dx (0) - 9.73 set/dxgrid (0) - 9.74 set/dxnet (5) - 9.75 set/echo (0) - 9.76 set/here (0) - 9.77 set/homenode (0) - 9.78 set/hops (8) - 9.79 set/isolate (9) - 9.80 set/language (0) - 9.81 set/location (0) - 9.82 set/sys_location (9) - 9.83 set/logininfo (0) - 9.84 set/lockout (9) - 9.85 set/name (0) - 9.86 set/node (9) - 9.87 set/obscount (9) - 9.88 set/page (0) - 9.89 set/password (9) - 9.90 set/pinginterval (9) - 9.91 set/privilege (9) - 9.92 set/spider (5) - 9.93 set/sys_qra (9) - 9.94 set/qra (0) - 9.95 set/qth (0) - 9.96 set/talk (0) - 9.97 set/wcy (0) - 9.98 set/wwv (0) - 9.99 set/wx (0) - 9.100 show/baddx (1) - 9.101 show/badnode (6) - 9.102 show/badspotter (1) - 9.103 show/configuration (0) - 9.104 show/configuration/node (0) - 9.105 show/connect (1) - 9.106 show/date (0) - 9.107 show/debug (9) - 9.108 show/dx (0) - 9.109 show/dxcc (0) - 9.110 show/files (0) - 9.111 show/filter (0) - 9.112 show/filter (extended for sysops) (5) - 9.113 show/hops (8) - 9.114 show/isolate (1) - 9.115 show/lockout (9) - 9.116 show/log (8) - 9.117 show/moon (0) - 9.118 show/muf (0) - 9.119 show/node (1) - 9.120 show/prefix (0) - 9.121 show/program (5) - 9.122 show/qra (0) - 9.123 show/qrz (0) - 9.124 show/route (0) - 9.125 show/satellite (0) - 9.126 show/sun (0) - 9.127 show/time (0) - 9.128 show/wcy (0) - 9.129 show/wwv (0) - 9.130 shutdown (5) - 9.131 spoof (9) - 9.132 stat/db (5) - 9.133 stat/channel (5) - 9.134 stat/msg (5) - 9.135 stat/user (5) - 9.136 sysop (0) - 9.137 talk (0) - 9.138 type (0) - 9.139 who (0) - 9.140 wx (0) - 9.141 wx (enhanced for sysops) (5) + 9.3 accept/route (8) + 9.4 accept/spots (0) + 9.5 accept/spots (extended for sysops) (8) + 9.6 accept/wcy (0) + 9.7 accept/wcy (extended for sysops) (8) + 9.8 accept/wwv (0) + 9.9 accept/wwv (extended for sysops) (8) + 9.10 announce (0) + 9.11 announce full (0) + 9.12 announce sysop (5) + 9.13 apropos (0) + 9.14 bye (0) + 9.15 catchup (5) + 9.16 clear/announce (8) + 9.17 clear/route (8) + 9.18 clear/spots (0) + 9.19 clear/spots (extended for sysops) (8) + 9.20 clear/wcy (0) + 9.21 clear/wcy (extended for sysops) (8) + 9.22 clear/wwv (0) + 9.23 clear/wwv (extended for sysops) (8) + 9.24 connect (5) + 9.25 dbavail (0) + 9.26 dbcreate (9) + 9.27 dbimport (9) + 9.28 dbremove (9) + 9.29 dbshow (0) + 9.30 debug (9) + 9.31 delete/user (9) + 9.32 directory (0) + 9.33 directory (extended for sysops) (5) + 9.34 disconnect (8) + 9.35 dx (0) + 9.36 export (9) + 9.37 export_users (9) + 9.38 filtering (0) + 9.39 forward/latlong (8) + 9.40 forward/opername (1) + 9.41 help (0) + 9.42 init (5) + 9.43 kill (0) + 9.44 kill (5) + 9.45 kill full (5) + 9.46 kill/expunge (6) + 9.47 links (0) + 9.48 load/aliases (9) + 9.49 load/badmsg (9) + 9.50 load/badwords (9) + 9.51 load/bands (9) + 9.52 load/cmd_cache (9) + 9.53 load/forward (9) + 9.54 load/messages (9) + 9.55 load/prefixes (9) + 9.56 merge (5) + 9.57 msg (9) + 9.58 pc (8) + 9.59 ping (1) + 9.60 rcmd (1) + 9.61 read (0) + 9.62 read (extended for sysops) (5) + 9.63 reject/announce + 9.64 reject/announce (extended for sysops) (8) + 9.65 reject/route (8) + 9.66 reject/spots (0) + 9.67 reject/spots (extended for sysops) (8) + 9.68 reject/wcy (0) + 9.69 reject/wcy (extended for sysops) (8) + 9.70 reject/wwv (0) + 9.71 reject/wwv (extended for sysops) (8) + 9.72 reply (0) + 9.73 send (0) + 9.74 set/address (0) + 9.75 set/announce (0) + 9.76 set/arcluster (5) + 9.77 set/baddx (8) + 9.78 set/badnode (6) + 9.79 set/badspotter (8) + 9.80 set/badword (8) + 9.81 set/beep (0) + 9.82 set/bbs (5) + 9.83 set/clx (5) + 9.84 set/debug (9) + 9.85 set/dx (0) + 9.86 set/dxgrid (0) + 9.87 set/dxnet (5) + 9.88 set/echo (0) + 9.89 set/email (0) + 9.90 set/here (0) + 9.91 set/homenode (0) + 9.92 set/hops (8) + 9.93 set/isolate (9) + 9.94 set/language (0) + 9.95 set/location (0) + 9.96 set/sys_location (9) + 9.97 set/logininfo (0) + 9.98 set/lockout (9) + 9.99 set/name (0) + 9.100 set/node (9) + 9.101 set/obscount (9) + 9.102 set/page (0) + 9.103 set/password (0) + 9.104 set/password (9) + 9.105 set/pinginterval (9) + 9.106 set/privilege (9) + 9.107 set/spider (5) + 9.108 set/sys_qra (9) + 9.109 set/qra (0) + 9.110 set/qth (0) + 9.111 set/register (9) + 9.112 set/talk (0) + 9.113 set/wcy (0) + 9.114 set/wwv (0) + 9.115 set/wx (0) + 9.116 show/baddx (1) + 9.117 show/badnode (6) + 9.118 show/badspotter (1) + 9.119 show/badword (1) + 9.120 show/configuration (0) + 9.121 show/configuration/node (0) + 9.122 show/connect (1) + 9.123 show/date (0) + 9.124 show/debug (9) + 9.125 show/dx (0) + 9.126 show/dxcc (0) + 9.127 sh/dxstats (0) + 9.128 show/files (0) + 9.129 show/filter (0) + 9.130 show/filter (extended for sysops) (5) + 9.131 show/hfstats (0) + 9.132 show/hftable (0) + 9.133 show/hops (8) + 9.134 show/isolate (1) + 9.135 show/lockout (9) + 9.136 show/log (8) + 9.137 show/moon (0) + 9.138 show/muf (0) + 9.139 show/newconfiguration (0) + 9.140 show/newconfiguration/node (0) + 9.141 show/node (1) + 9.142 show/prefix (0) + 9.143 show/program (5) + 9.144 show/qra (0) + 9.145 show/qrz (0) + 9.146 show/registered (9) + 9.147 show/route (0) + 9.148 show/satellite (0) + 9.149 show/sun (0) + 9.150 show/time (0) + 9.151 show/vhfstats (0) + 9.152 show/vhftable (0) + 9.153 show/wcy (0) + 9.154 show/wwv (0) + 9.155 shutdown (5) + 9.156 spoof (9) + 9.157 stat/db (5) + 9.158 stat/channel (5) + 9.159 stat/msg (5) + 9.160 stat/route_node (5) + 9.161 stat/route_user (5) + 9.162 stat/user (5) + 9.163 sysop (0) + 9.164 talk (0) + 9.165 type (0) + 9.166 who (0) + 9.167 wx (0) + 9.168 wx (enhanced for sysops) (5) ______________________________________________________________________ - 1. Hop control - - Starting with version 1.13 there is simple hop control available on a - per node basis. Also it is possible to isolate a network completely so - that you get all the benefits of being on that network, but can't pass - on information from it to any other networks you may be connected to - (or vice versa). - - - 1.1. Basic hop control - - In /spider/data you will find a file called hop_table.pl. This is the - file that controls your hop count settings. It has a set of default - hops on the various PC frames and also a set for each node you want to - alter the hops for. You may be happy with the default settings of - course, but this powerful tool can help to protect and improve the - network. The file will look something like this ... - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # - # hop table construction - # - - package DXProt; - - # default hopcount to use - $def_hopcount = 5; - - # some variable hop counts based on message type - %hopcount = - ( - 11 => 10, - 16 => 10, - 17 => 10, - 19 => 10, - 21 => 10, - ); - - - # the per node hop control thingy - - - %nodehops = - - GB7ADX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - - GB7UDX => { 11 => 8, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - GB7BAA => { - 11 => 5, - 12 => 8, - 16 => 8, - 17 => 8, - 19 => 8, - 21 => 8, - }, - }; - - - - + 1. Routing and Filtering - Each set of hops is contained within a pair of curly braces and - contains a series of PC frame types. PC11 for example is a DX spot. - The figures here are not exhaustive but should give you a good idea of - how the file works. - - - You can alter this file at any time, including whilst the cluster is - running. If you alter the file during runtime, the command load/hops - will bring your changes into effect. - - - - 1.2. Isolating networks - - 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 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 - .... + 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 = [ - [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count - ]; + 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). - There is a lot more on filtering in the next section. + 1.2. Route Filters - 2. Filtering (Old Style upto v1.44) + 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. - Filters can be set for spots, announcements and WWV. You will find - the directories for these under /spider/filter. You will find some - examples in the directories with the suffix .issue. There are two - types of filter, one for incoming information and one for outgoing - information. Outgoing filters are in the form CALLSIGN.pl and - incoming filters are in the form in_CALLSIGN.pl. Filters can be set - for both nodes and users. + 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. - All filters work in basically the same way. There are several - elements delimited by commas. There can be many lines in the filter - and they are read from the top by the program. When writing a filter - you need to think carefully about just what you want to achieve. You - are either going to write a filter to accept or to reject. Think of a - filter as having 2 main elements. For a reject filter, you would have - a line or multiple lines rejecting the things you do not wish to - receive and then a default line accepting everything else that is not - included in the filter. Likewise, for an accept filter, you would - have a line or multiple lines accepting the things you wish to receive - and a default line rejecting everthing else. + 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. - 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. + 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. - $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 - ]; + 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. - The actual elements of each filter are described more fully in the - following sections. + 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. - 2.1. Spots - The elements of the Spot filter are .... + The generic commands are:- + reject/route node_default - [action, field_no, sort, possible_values, hops] + or + accept/route node_default - 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). + where filter_option is one of the following ... - The second element is the field_no. There are 13 possiblities to - choose from here .... + 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:- - 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 + acc/route node_default call_dxcc 61,38 + acc/route node_default call gb7djk - The third element tells us what to expect in the fourth element. - There are 4 possibilities .... + GB7DJK uses the first of these. The DXCC countries can be obtained + from the show/prefix command. - 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 example filters shown control output TO all your partner nodes + unless they have a specific filter applied to them (see next section). + It is also possible to control the incoming routing information that + you are prepared to accept FROM your partner nodes. The reason this is + necessary is to make sure that stuff like mail, pings and similar + commands a) go down the correct links and b) don't loop around + excessively. Again using GB7DJK as an example a typical default input + filter would be something like: - 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. + rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38 - 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. + 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. - $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 - ]; + 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:- + set/debug filter - 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. + After you have got tired of that, to put it back the way it was:- - The second line is the default rule for anything else. The "d" tells - us this and the line simply reads... accept anything else. + unset/debug filter - 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], + 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 ... - But the line below achieves the same thing and is more efficient .... + reject/route + or + accept/route - [ 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 ], + Here are some examples of route filters ... - 2.2. Announcements + 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) - # 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 practice you will either be opening the default filter out for a + partner by defining a specific filter for that callsign:- + acc/route gb7baa all + acc/route gb7baa input all - 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. - 2.3. WWV + or restricting it quite a lot, in fact making it very nearly like an + isolated node, like this:- + acc/route pi4ehv-8 call gb7djk + rej/route pi4ehv-8 input call_dxcc 61,38 - # 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 ] - ]; + This last example takes everything except UK and Eire from PI4EHV-8 + but only sends him my local configuration (just a PC19 for GB7DJK and + PC16s for my local users). + It is possible to write much more complex rules, there are up to 10 + accept/reject pairs per callsign per filter. For more information see + the next section. - 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. - - 3. Filtering (New Style v1.45 and later) - - 3.1. General filter rules + 1.5. General filter rules Upto v1.44 it was not possible for the user to set their own filters. From v1.45 though that has all changed. It is now possible to set @@ -721,9 +564,12 @@ the DXSpider system. They all use the same general mechanism. - In general terms you can create a 'reject' or an 'accept' filter which + In general terms you can create a "reject" or an "accept" filter which can have up to 10 lines in it. You do this using, for example ... + + + accept/spots ..... reject/spots ..... @@ -764,7 +610,7 @@ the same principles to all types of filter. - 3.2. Types of filter + 1.6. Types of filter There are two main types of filter, accept or reject. You can use either to achieve the result you want dependent on your own preference @@ -790,6 +636,7 @@ then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16. + If you set a reject filter like this ... @@ -856,6 +703,9 @@ 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 @@ -874,9 +724,6 @@ reject/spots 1 on hf/ssb - - - would redefine our earlier example, or @@ -896,13 +743,13 @@ - 3.3. Filter options + 1.7. Filter options You can filter in several different ways. The options are listed in the various helpfiles for accept, reject and filter. - 3.4. Default filters + 1.8. Default filters Sometimes all that is needed is a general rule for node connects. This can be done with a node_default filter. This rule will always be @@ -928,7 +775,7 @@ to add a rule for the hops for spots also. - 3.5. Advanced filtering + 1.9. Advanced filtering Once you are happy with the results you get, you may like to experiment. @@ -943,9 +790,6 @@ 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 @@ -963,23 +807,179 @@ VHF/UHF spots from EU. + 1.10. Basic hop control + + In /spider/data you will find a file called hop_table.pl. This is the + file that controls your hop count settings. It has a set of default + hops on the various PC frames and also a set for each node you want to + alter the hops for. You may be happy with the default settings of + course, but this powerful tool can help to protect and improve the + network. The file will look something like this ... + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + # + # hop table construction + # + + package DXProt; + + # default hopcount to use + $def_hopcount = 5; + + # some variable hop counts based on message type + %hopcount = + ( + 11 => 10, + 16 => 10, + 17 => 10, + 19 => 10, + 21 => 10, + ); + + + # the per node hop control thingy + + + %nodehops = + + GB7ADX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + + GB7UDX => { 11 => 8, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + GB7BAA => { + 11 => 5, + 12 => 8, + 16 => 8, + 17 => 8, + 19 => 8, + 21 => 8, + }, + }; + + + + + + Each set of hops is contained within a pair of curly braces and + contains a series of PC frame types. PC11 for example is a DX spot. + The figures here are not exhaustive but should give you a good idea of + how the file works. + + + You can alter this file at any time, including whilst the cluster is + running. If you alter the file during runtime, the command load/hops + will bring your changes into effect. + + + + 1.11. Hop Control on Specific Nodes + + You can set a callsign specific hop count for any of the standard + filter options so:- + + + + set/hops gb7djk spot 4 + set/hops node_default route 10 + set/hops gb7baa wcy 5 + + + + + all work on their specific area of the protocol. - 4. Other filters - 4.1. Filtering Mail + The set/hops command overrides any hops that you have set otherwise. - 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 .... + You can set what hops have been set using the show/hops command. + + + 1.12. Isolating networks + + It is possible to isolate networks from each other on a "gateway" node + using the set/isolate 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. + 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 .... @@ -1028,86 +1028,79 @@ etc in a particular country. - 4.2. Filtering DX callouts (Depricated) - From version 1.47, this method is replaced by the command set/baddx + 2.2. Filtering words from text fields in Announce, Talk and DX spots + From version 1.48 onwards the interface to this has changed. You can + now use the commands set/badword to add words that you are not + prepared to see on the cluster, unset/badword to allow that word again + and show/badword to list the words that you have set. - 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 .... + 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. + 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters + 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:- + set/baddx + set/badspotter + set/badnode + These work in the same as the set/badword command, you can add any + words or callsigns or whatever to the appropriate database. For + example, to stop a spot from a particular node you do: - # the 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 - ); + set/badnode gb7djk gb7dxc + a bad spotter: - Again, this is simply a list of names we do not want to see in the - spotted field of a DX callout. + set/badspotter b0mb p1rat nocall - 4.3. Filtering words from text fields in Announce, Talk and DX spots - Create a file in /spider/data called badwords. The format is quite - simple. Lines beginning with # are ignored so comments can be added. - An example file is below ... + and some bad dx: - # Below is a list of words we do not wish to see on the cluster - grunge grunged grunging - splodge splodger splodging - grince - fluffle + set/baddx video wsjt - 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. + 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. - 5. Mail + 3. Mail DXSpider deals seamlessly with standard AK1A type mail. It supports both personal and bulletin mail and the sysop has additional commands @@ -1120,15 +1113,14 @@ The cluster mail is automatically deleted after 30 days unless the sysop sets the "keep" flag using the msg command. - 5.1. Personal mail + + 3.1. Personal mail Personal mail is sent using the sp command. This is actually the default method of sending mail and so a simple s for send will do. A full list of the send commands and options is in the command set section, so I will not duplicate them here. - - - 5.2. Bulletin mail + 3.2. Bulletin mail Bulletin mail is sent by using the sb command. This is one of the most common mistakes users make when sending mail. They send a @@ -1140,7 +1132,7 @@ Bulletin addresses can be set using the Forward.pl file. - 5.3. Forward.pl + 3.3. Forward.pl DXSpider receives all and any mail sent to it without any alterations needed in files. Because personal and bulletin mail are treated @@ -1155,72 +1147,41 @@ + # + # 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; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - # - # 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 = ( - ); + @forward = ( + ); @@ -1234,7 +1195,7 @@ - 5.4. The msg command + 3.4. The msg command The msg command is a very powerful and flexible tool for the sysop. It allows the sysop to alter to and from fields and make other changes @@ -1244,28 +1205,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 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 + 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 @@ -1274,7 +1227,7 @@ user. - 5.5. Message status + 3.5. Message status You can check on a message from within the cluster by using the command stat/msg. This will give you additional information on the @@ -1299,17 +1252,13 @@ Times read: 0 G0VGS de GB7MBC 28-Jan-2001 1308Z > - - - - - 5.6. Filtering mail + 3.6. Filtering mail This is described in the section on Other filters so I will not duplicate it here. - 5.7. Distribution lists + 3.7. Distribution lists Distribution lists are simply a list of users to send certain types of mail to. An example of this is mail you only wish to send to other @@ -1318,6 +1267,7 @@ 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) @@ -1329,7 +1279,7 @@ list. - 5.8. BBS interface + 3.8. BBS interface Spider provides a simple BBS interface. No input is required from the sysop of the cluster at all. The BBS simply sets the cluster as a BBS @@ -1342,7 +1292,90 @@ using the Forward.pl file very carefully. - 6. Databases + 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. + + + + + + + + + + + + # + # startup script example + # + # set maximum no of spots allowed to 100 + # set/var $Spot::maxspots = 1 + # + # Set registration on + # set/var $main::reqreg = 1 + # + # Set passwords on + # set/var $main::passwdreq = 1 + # + + + + + + As usual, any text behind a # is treated as a comment and not read. + + Secondly, it is used to store the login scripts for users and nodes. + Currently this can only be done by the sysop but it is envisaged that + eventually users will be able to set their own. An example is + included in the distibution but here is a further example. + + + + # + # G0FYD + # + blank + + sh/wwv 3 + blank + + sh/dx + blank + + t g0jhc You abt? + blank + + + + + + The 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. + + + 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 Spider allows the creation of local or remote databases. It supports chained databases, allowing several different databases to be scanned @@ -1351,7 +1384,7 @@ database but will expand with time. - 6.1. Creating databases + 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. @@ -1384,6 +1417,9 @@ 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... @@ -1399,7 +1435,7 @@ chain can be a remote database. - 6.2. Importing databases + 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. @@ -1414,12 +1450,11 @@ - This will update the existing local oblast database or create it if it does not exist. - 6.3. Checking available databases + 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 @@ -1438,7 +1473,7 @@ - 6.4. Looking up databases + 5.4. Looking up databases To look for information in a defined database, simply use the dbshow command, for example ... @@ -1464,7 +1499,7 @@ Now you can simply use show/buckmaster or an abreviation. - 6.5. Removing databases + 5.5. Removing databases To delete an existing database you use the dbremove command. For example ... @@ -1481,10 +1516,9 @@ If you remove a database it ceases to exist and would have to be created from scratch if you still required it. + 6. Information, files and useful programs - 7. Information, files and useful programs - - 7.1. MOTD + 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 @@ -1495,7 +1529,14 @@ to the cluster. - 7.2. Downtime message + 6.2. MOTD_NOR + + This message of the day file lives in the same directory as the + standard motd file but is only sent to non-registered users. Once + registered they will receive the same message as any other user. + + + 6.3. Downtime message If for any reason the cluster is down, maybe for upgrade or maintenance but the machine is still running, a message can be sent to @@ -1506,7 +1547,7 @@ actually running. - 7.3. Other text messages + 6.4. Other text messages You can set other text messages to be read by the user if they input the file name. This could be for news items or maybe information for @@ -1516,6 +1557,7 @@ like. These can be listed by the user with the command .... + show/files @@ -1579,46 +1621,46 @@ + show/files bulletin + opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z + opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z + opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z + opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z + opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z + opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z + opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z + opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z + opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z + opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z + opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z + opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z + opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z + Press Enter to continue, A to abort (16 lines) > - show/files bulletin - opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z - opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z - opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z - opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z - opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z - opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z - opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z - opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z - opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z - opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z - opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z - opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z - opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z - Press Enter to continue, A to abort (16 lines) > + You can now read any file in this directory using the type command, + like this .... - You can now read any file in this directory using the type command, - like this .... - type bulletin/opdx391 - Ohio/Penn DX Bulletin No. 391 - The Ohio/Penn Dx PacketCluster - DX Bulletin No. 391 - BID: $OPDX.391 - January 11, 1999 - Editor Tedd Mirgliotta, KB8NW - Provided by BARF-80 BBS Cleveland, Ohio - Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!) - Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX - Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH - & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR, - Press Enter to continue, A to abort (508 lines) > + type bulletin/opdx391 + Ohio/Penn DX Bulletin No. 391 + The Ohio/Penn Dx PacketCluster + DX Bulletin No. 391 + BID: $OPDX.391 + January 11, 1999 + Editor Tedd Mirgliotta, KB8NW + Provided by BARF-80 BBS Cleveland, Ohio + Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!) + Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX + Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH + & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR, + Press Enter to continue, A to abort (508 lines) > @@ -1626,7 +1668,7 @@ The page length will of course depend on what you have it set to! - 7.4. The Aliases file + 6.5. The Aliases file You will find a file in /spider/cmd/ called Aliases. First, copy this file to /spider/local_cmd/Aliases and edit this file. You will see @@ -1648,6 +1690,30 @@ + + + + + + + + + + + + + + + + + + + + + + + + #!/usr/bin/perl # provide some standard aliases for commands for terminally @@ -1790,7 +1856,7 @@ the results once you have set an alias. - 7.5. Console.pl + 6.6. Console.pl In later versions of Spider a simple console program is provided for the sysop. This has a type ahead buffer with line editing facilities @@ -1802,7 +1868,7 @@ edit the file with your favourite editor. - 7.6. Updating kepler data + 6.7. Updating kepler data Spider has a powerful and flexible show/satellite command. In order for this to be accurate, the kepler data has to be updated regularly. @@ -1846,7 +1912,7 @@ - 7.7. The QRZ callbook + 6.8. The QRZ callbook The command sh/qrz will only work once you have followed a few simple steps. First you need to get a user ID and password from qrz.com. @@ -1857,22 +1923,109 @@ proprieter of qrz.com for allowing this access. + 7. Security + + From version 1.49 DXSpider has some additional security features. + These are not by any means meant to be exhaustive, however they do + afford some security against piracy. These two new features can be + used independently of each other or in concert to tighten the + security. + + + 7.1. Registration + + The basic principle of registration is simple. If a user is not + registered by the sysop, then they have read-only access to the + cluster. The only thing they can actually send is a talk or a message + to the sysop. In order for them to be able to spot, send announces or + talks etc the sysop must register them with the set/register command, + like this ... + + + + set/register g0vgs + + + + + The user g0vgs can now fully use the cluster. In order to enable + registration, you can issue the command ... + + + + set/var $main::reqreg = 1 + + + + + Any users that are not registered will now see the motd_nor file + rather than the motd file as discussed in the Information, files and + useful programs section. + + + Entering this line at the prompt will only last for the time the + cluster is running of course and would not be present on a restart. + To make the change permanent, add the above line to + /spider/scripts/startup. To read more on the startup file, see the + section on Information, files and useful programs. + + + To unregister a user use unset/register and to show the list of + registered users, use the command show/register. + + + 7.2. Passwords + + At the moment, passwords only affect users who login to a DXSpider + cluster node via telnet. If a user requires a password, they can + either set it themselves or have the sysop enter it for them by using + the set/password command. Any users who already have passwords, such + as remote sysops, will be asked for their passwords automatically by + the cluster. Using passwords in this way means that the user has a + choice on whether to have a password or not. To force the use of + passwords at login, issue the command ... + + + + set/var $main::passwdreq = 1 + + + + + at the cluster prompt. This can also be added to the + /spider/scripts/startup file as above to make the change permanent. + + + Of course, if you do this you will have to assign a password for each + of your users. If you were asking them to register, it is anticipated + that you would ask them to send you a message both to ask to be + registered and to give you the password they wish to use. + + + Should a user forget their password, it can be reset by the sysop by + first removing the existing password and then setting a new one like + so ... + + + + unset/password g0vgs + set/password g0vgs new_password + + + + + 8. CVS CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held at Sourceforge. This means that it is possible to update your DXSpider installation to the latest sources by using a few simple - commands. - - - 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!!! + commands. - 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 @@ -1891,7 +2044,6 @@ First login as the user sysop. Next you need to connect to the CVS repository. You do this with the command below ... - cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login @@ -1911,7 +2063,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. @@ -1978,6 +2129,7 @@ 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. @@ -2024,8 +2176,6 @@ some examples:- - - acc/ann dest 6MUK acc/ann 2 by_zone 14,15,16 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16) @@ -2044,6 +2194,9 @@ 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 @@ -2071,7 +2224,59 @@ - 9.3. accept/spots (0) + 9.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) + + + + + + You can use the tag 'all' to accept everything eg: + + + + acc/route all + + + + + + 9.4. accept/spots (0) accept/announce [0-9] Set an accept filter line for spots @@ -2103,13 +2308,12 @@ - - 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 - this is more efficient than saying simply: freq HF (but don't get too hung up about that) + some examples:- @@ -2132,7 +2336,7 @@ but this probably for advanced users... - 9.4. accept/spots (extended for sysops) (8) + 9.5. accept/spots (extended for sysops) (8) accept/spots [input] [0-9] Spot filter sysop version @@ -2152,7 +2356,7 @@ - 9.5. accept/wcy (0) + 9.6. accept/wcy (0) accept/wcy [0-9] set an accept WCY filter @@ -2162,15 +2366,23 @@ - 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 @@ -2185,7 +2397,7 @@ See HELP FILTER for information. - 9.6. accept/wcy (extended for sysops) (8) + 9.7. accept/wcy (extended for sysops) (8) accept/wcy [input] [0-9] WCY filter sysop version @@ -2202,7 +2414,7 @@ - 9.7. accept/wwv (0) + 9.8. accept/wwv (0) accept/wwv [0-9] Set an accept WWV filter @@ -2228,7 +2440,6 @@ for example - accept/wwv by_zone 4 @@ -2240,9 +2451,7 @@ See HELP FILTER for information. - - - 9.8. accept/wwv (extended for sysops) (8) + 9.9. accept/wwv (extended for sysops) (8) accept/wwv [input] [0-9] WWV filter sysop version @@ -2262,16 +2471,18 @@ - 9.9. announce (0) + 9.10. announce (0) 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. - 9.10. announce full (0) + 9.11. announce full (0) announce full Send an announcement cluster wide @@ -2281,7 +2492,7 @@ - 9.11. announce sysop (5) + 9.12. announce sysop (5) announce sysop @@ -2289,16 +2500,17 @@ Send an announcement to Sysops only - 9.12. apropos (0) + 9.13. apropos (0) 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. - 9.13. bye (0) + 9.14. bye (0) bye Exit from the cluster @@ -2306,9 +2518,7 @@ This will disconnect you from the cluster - - - 9.14. catchup (5) + 9.15. catchup (5) catchup All|[ ...] Mark a message as sent @@ -2343,7 +2553,32 @@ Order is not important. - 9.15. clear/spots (0) + 9.16. clear/announce (8) + + clear/announce [input] [0-9|all] Clear an announce filter + line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 9.17. clear/route (8) + + clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line + + + This command allows you to clear (remove) a line in a route filter or + to remove the whole filter. + + + see CLEAR/SPOTS for a more detailed explanation. + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 9.18. clear/spots (0) clear/spots [1|all] Clear a spot filter line @@ -2374,7 +2609,7 @@ - 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) @@ -2391,8 +2626,59 @@ the filter will be completely removed. + 9.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. + + + + + + 9.20. clear/wcy (0) + + clear/wcy [1|all] Clear a WCY filter line + + + This command allows you to clear (remove) a line in a WCY filter or to + remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. + + + 9.21. clear/wcy (extended for sysops) (8) + + clear/wcy [input] [0-9|all] Clear a WCY filter line - 9.16. connect (5) + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 9.22. clear/wwv (0) + + clear/wwv [1|all] Clear a WWV filter line + + + This command allows you to clear (remove) a line in a WWV filter or to + remove the whole filter. + + see CLEAR/SPOTS for a more detailed explanation. + + + 9.23. clear/wwv (extended for sysops) (8) + + clear/wwv [input] [0-9|all] Clear a WWV filter line + + + A sysop can clear an input or normal output filter for a user or the + node_default or user_default. + + + 9.24. connect (5) connect Start a connection to another DX Cluster @@ -2404,7 +2690,7 @@ cluster . - 9.17. dbavail (0) + 9.25. dbavail (0) dbavail Show a list of all the databases in the system @@ -2413,7 +2699,7 @@ defined in the system. It is also aliased to SHOW/COMMAND. - 9.18. dbcreate (9) + 9.26. dbcreate (9) dbcreate Create a database entry dbcreate chain [..] Create a chained database @@ -2440,6 +2726,7 @@ 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: @@ -2481,7 +2768,9 @@ databases. See DBSHOW for generic database enquiry - 9.19. dbimport (9) + + + 9.27. dbimport (9) dbimport Import AK1A data into a database @@ -2496,7 +2785,7 @@ oblast database held locally. - 9.20. dbremove (9) + 9.28. dbremove (9) dbremove Delete a database @@ -2520,7 +2809,7 @@ You have been warned. - 9.21. dbshow (0) + 9.29. dbshow (0) dbshow Display an entry, if it exists, in a database @@ -2547,9 +2836,7 @@ - - - 9.22. debug (9) + 9.30. debug (9) debug Set the cluster program into debug mode @@ -2568,7 +2855,21 @@ finished. - 9.23. directory (0) + 9.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! + + + + 9.32. directory (0) directory List messages directory own List your own messages @@ -2601,9 +2902,6 @@ You can abbreviate all the commands to one letter and use ak1a syntax:- - - - DIR/T G1* 10 DIR/S QSL 10-100 5 @@ -2612,13 +2910,13 @@ - 9.24. directory (extended for sysops) (5) + 9.33. directory (extended for sysops) (5) Works just like the user command except that sysops can see ALL messages. - 9.25. disconnect (8) + 9.34. disconnect (8) disconnect [ ...] Disconnect a user or node @@ -2626,7 +2924,7 @@ Disconnect any connected locally - 9.26. dx (0) + 9.35. dx (0) dx [by ] Send a DX spot @@ -2636,11 +2934,9 @@ - - - DX FR0G 144.600 - DX 144.600 FR0G - DX 144600 FR0G + DX FR0G 144.600 + DX 144.600 FR0G + DX 144600 FR0G @@ -2668,11 +2964,10 @@ cluster. See SHOW/BANDS for more information. - 9.27. export (9) + 9.36. export (9) export Export a message to a file - Export a message to a file. This command can only be executed on a local console with a fully privileged user. The file produced will be in a form ready to be imported back into the cluster by placing it in @@ -2686,7 +2981,7 @@ EXPORT 2345 /tmp/a - 9.28. export_users (9) + 9.37. export_users (9) export_users [] Export the users database to ascii @@ -2702,9 +2997,140 @@ check is made on the filename (if any) that you specify. + 9.38. filtering (0) + + filtering Filtering things in DXSpider + + + There are a number of things you can filter in the DXSpider system. + They all use the same general mechanism. + + In general terms you can create a 'reject' or an 'accept' filter which + can have up to 10 lines in it. You do this using, for example:- + + accept/spots ..... reject/spots ..... + + where ..... are the specific commands for that type of filter. There + are filters for spots, wwv, announce, wcy and (for sysops) connects. + See each different accept or reject command reference for more + details. + + There is also a command to clear out one or more lines in a filter and + one to show you what you have set. They are:- + + clear/spots 1 clear/spots all + + and + + show/filter + + There is clear/xxxx command for each type of filter. + + For now we are going to use spots for the examples, but you can apply + the principles to all types of filter. + + There are two main types of filter 'accept' or 'reject'; which you use + depends entirely on how you look at the world and what is least + writing to achieve what you want. Each filter has 10 lines (of any + length) which are tried in order. If a line matches then the action + you have specified is taken (ie reject means ignore it and accept + means gimme it). + + The important thing to remember is that if you specify a 'reject' + filter (all the lines in it say 'reject/spots' (for instance) then if + a spot comes in that doesn't match any of the lines then you will get + it BUT if you specify an 'accept' filter then any spots that don't + match are dumped. For example if I have a one line accept filter:- + + accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + + then automatically you will ONLY get VHF spots from or to CQ zones 14 + 15 and 16. If you set a reject filter like: + + reject/spots on hf/cw + + Then you will get everything EXCEPT HF CW spots, If you am interested + in IOTA and will work it even on CW then you could say:- + + reject/spots on hf/cw and not info iota + + But in that case you might only be interested in iota and say:- + + accept/spots not on hf/cw or info iota + + which is exactly the same. You should choose one or the other until + you are confortable with the way it works. Yes, you can mix them + (actually you can have an accept AND a reject on the same line) but + don't try this at home until you can analyse the results that you get + without ringing up the sysop for help. + + You can arrange your filter lines into logical units, either for your + own understanding or simply convenience. I have one set frequently:- + + reject/spots 1 on hf/cw reject/spots 2 on 50000/1400000 not (by_zone + 14,15,16 or call_zone 14,15,16) + + What this does is to ignore all HF CW spots (being a class B I can't + read any CW and couldn't possibly be interested in HF :-) and also + rejects any spots on VHF which don't either originate or spot someone + in Europe. + + This is an exmaple where you would use the line number (1 and 2 in + this case), if you leave the digit out, the system assumes '1'. Digits + + You can leave the word 'and' out if you want, it is implied. You can + use any number of brackets to make the 'expression' as you want it. + There are things called precedence rules working here which mean that + you will NEED brackets in a situation like line 2 because, without it, + will assume:- + + (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 + + annoying, but that is the way it is. If you use OR - use brackets. + Whilst we are here CASE is not important. 'And BY_Zone' is just 'and + by_zone'. + + If you want to alter your filter you can just redefine one or more + lines of it or clear out one line. For example:- + + reject/spots 1 on hf/ssb + + or + + clear/spots 1 + + + To remove the filter in its entirty:- + + clear/spots all + + There are similar CLEAR commands for the other filters:- + clear/announce clear/wcy clear/wwv - 9.29. forward/latlong (8) + ADVANCED USERS:- + + Once you are happy with the results you get, you may like to + experiment. + + my example that filters hf/cw spots and accepts vhf/uhf spots from EU + can be written with a mixed filter, eg: + + rej/spot on hf/cw acc/spot on 0/30000 acc/spot 2 on 50000/1400000 and + (by_zone 14,15,16 or call_zone 14,15,16) + + each filter slot actually has a 'reject' slot and an 'accept' slot. + The reject slot is executed BEFORE the accept slot. + + It was mentioned earlier that after a reject test that doesn't match, + the default for following tests is 'accept', the reverse is true for + first, any non hf/cw spot is passed to the accept line, which lets + thru everything else on HF. + + The next filter line lets through just VHF/UHF spots from EU. + + + 9.39. forward/latlong (8) forward/latlong Send latitude and longitude information to another cluster @@ -2718,7 +3144,7 @@ so it is not recommended on slow links. - 9.30. forward/opername (1) + 9.40. forward/opername (1) forward/opername Send out information on this to all clusters @@ -2730,7 +3156,7 @@ available. - 9.31. help (0) + 9.41. help (0) help Get help on a command @@ -2743,7 +3169,7 @@ commands to look at with HELP. - 9.32. init (5) + 9.42. init (5) init Re-initialise a link to an AK1A compatible node @@ -2757,7 +3183,7 @@ Best of luck - you will need it. - 9.33. kill (0) + 9.43. kill (0) kill [ ..] Delete a message from the local system @@ -2767,10 +3193,7 @@ the sysop). - - - - 9.34. kill (5) + 9.44. kill (5) kill [ ...] Remove or erase a message from the system kill from Remove all messages from a callsign @@ -2783,7 +3206,7 @@ As a sysop you can kill any message on the system. - 9.35. kill full (5) + 9.45. kill full (5) kill full [] Delete a message from the whole cluster @@ -2794,7 +3217,22 @@ same subject will be deleted. Beware! - 9.36. links (0) + 9.46. kill/expunge (6) + + kill/expunge [..]Expunge a message + + + Deleting a message using the normal KILL commands only marks that + message for deletion. The actual deletion only happens later (usually + two days later). + + The KILL EXPUNGE command causes the message to be truly deleted more + or less immediately. + + It otherwise is used in the same way as the KILL command. + + + 9.47. links (0) links Show which nodes are physically connected @@ -2804,7 +3242,7 @@ - 9.37. load/aliases (9) + 9.48. load/aliases (9) load/aliases Reload the command alias table @@ -2814,18 +3252,7 @@ running in order for the changes to take effect. - - 9.38. load/baddx (9) - - load/baddx Reload the bad DX table - - - Reload the /spider/data/baddx.pl file if you have changed it manually - whilst the cluster is running. This table contains the DX Calls that, - if spotted, will not be passed on. FR0G and TEST are classic examples. - - - 9.39. load/badmsg (9) + 9.49. load/badmsg (9) load/badmsg Reload the bad message table @@ -2836,9 +3263,10 @@ each message. If any of them match then that message is immediately deleted on receipt. - 9.40. load/badwords (9) - load/badwords Reload the badwords file + 9.50. load/badwords (9) + + load/badwords Reload the bad words table Reload the /spider/data/badwords file if you have changed it manually @@ -2850,7 +3278,7 @@ ignored. - 9.41. load/bands (9) + 9.51. load/bands (9) load/bands Reload the band limits table @@ -2859,7 +3287,7 @@ whilst the cluster is running. - 9.42. load/cmd_cache (9) + 9.52. load/cmd_cache (9) load/cmd_cache Reload the automatic command cache @@ -2870,9 +3298,7 @@ delete a command in the local_cmd tree and want to use the normal one again. Execute this command to reset everything back to the state it was just after a cluster restart. - - - 9.43. load/forward (9) + 9.53. load/forward (9) load/forward Reload the msg forwarding routing table @@ -2880,7 +3306,7 @@ whilst the cluster is running. - 9.44. load/messages (9) + 9.54. load/messages (9) load/messages Reload the system messages file @@ -2893,7 +3319,7 @@ unknown message 'xxxx' in lang 'en' - 9.45. load/prefixes (9) + 9.55. load/prefixes (9) load/prefixes Reload the prefix table @@ -2902,7 +3328,7 @@ manually whilst the cluster is running. - 9.46. merge (5) + 9.56. merge (5) merge [/] Ask for the latest spots and WWV @@ -2917,7 +3343,7 @@ data). - 9.47. msg (9) + 9.57. msg (9) msg [data ...] Alter various message parameters @@ -2928,20 +3354,30 @@ - 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 @@ -2953,7 +3389,7 @@ This will display more information on the message than DIR does. - 9.48. pc (8) + 9.58. pc (8) pc Send text (eg PC Protocol) to @@ -2968,10 +3404,11 @@ 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!!! - 9.49. ping (1) + 9.59. ping (1) ping Check the link quality between nodes @@ -2984,7 +3421,7 @@ - 9.50. rcmd (1) + 9.60. rcmd (1) rcmd Send a command to another DX cluster @@ -2992,13 +3429,14 @@ This command allows you to send nearly any command to another DX Cluster node that is connected to the system. + Whether you get any output is dependant on a) whether the other system knows that the node callsign of this cluster is in fact a node b) whether the other system is allowing RCMDs from this node and c) whether you have permission to send this command at all. - 9.51. read (0) + 9.61. read (0) read Read the next unread personal message addressed to you read Read the specified message @@ -3009,7 +3447,7 @@ - 9.52. read (extended for sysops) (5) + 9.62. read (extended for sysops) (5) read Read a message on the system @@ -3017,7 +3455,7 @@ As a sysop you may read any message on the system - 9.53. reject/announce + 9.63. reject/announce reject/announce [0-9] Set a reject filter for announce @@ -3033,19 +3471,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) @@ -3071,7 +3508,7 @@ but this probably for advanced users... - 9.54. reject/announce (extended for sysops) (8) + 9.64. reject/announce (extended for sysops) (8) reject/announce [input] [0-9] Announce filter sysop version @@ -3090,7 +3527,58 @@ - 9.55. reject/spots (0) + 9.65. 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) + + + + + + 9.66. reject/spots (0) reject/spots [0-9] Set a reject filter line for spots @@ -3139,6 +3627,7 @@ + You can use the tag 'all' to reject everything eg: @@ -3151,7 +3640,7 @@ but this probably for advanced users... - 9.56. reject/spots (extended for sysops) (8) + 9.67. reject/spots (extended for sysops) (8) reject/spots [input] [0-9] Reject spot filter sysop version @@ -3162,21 +3651,17 @@ + reject/spot db0sue-7 1 by_zone 14,15,16 + reject/spot node_default all + set/hops node_default 10 - - - - reject/spot db0sue-7 1 by_zone 14,15,16 - reject/spot node_default all - set/hops node_default 10 - - reject/spot user_default by G,M,2 + reject/spot user_default by G,M,2 - 9.57. reject/wcy (0) + 9.68. reject/wcy (0) reject/wcy [0-9] Set a reject WCY filter @@ -3208,7 +3693,8 @@ See HELP FILTER for information. - 9.58. reject/wcy (extended for sysops) (8) + + 9.69. reject/wcy (extended for sysops) (8) reject/wcy [input] [0-9] WCY reject filter sysop version @@ -3220,7 +3706,7 @@ reject/wcy gb7djk all - 9.59. reject/wwv (0) + 9.70. reject/wwv (0) reject/wwv [0-9] Set a reject WWV filter @@ -3230,17 +3716,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 @@ -3260,7 +3744,7 @@ See HELP FILTER for information. - 9.60. reject/wwv (extended for sysops) (8) + 9.71. reject/wwv (extended for sysops) (8) reject/wwv [input] [0-9] WWV reject filter sysop version @@ -3276,11 +3760,7 @@ reject/wwv user_default by W - - - - - 9.61. reply (0) + 9.72. reply (0) reply Reply (privately) to the last message that you have read reply Reply (privately) to the specified message @@ -3297,8 +3777,7 @@ further details) - - 9.62. send (0) + 9.73. send (0) send [ ...] Send a message to one or more callsigns send RR Send a message and ask for a read receipt @@ -3332,7 +3811,7 @@ is an alias for SEND PRIVATE - 9.63. set/address (0) + 9.74. set/address (0) set/address Record your postal address @@ -3340,15 +3819,14 @@ Literally, record your address details on the cluster. - 9.64. set/announce (0) + 9.75. set/announce (0) set/announce Allow announce messages Allow announce messages to arrive at your terminal. - - 9.65. set/arcluster (5) + 9.76. set/arcluster (5) set/arcluster [ ...] Make the node_call an AR- Cluster type node @@ -3357,13 +3835,12 @@ Set the node_call as an AR-Cluster type node - 9.66. set/baddx (8) + 9.77. set/baddx (8) 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. @@ -3387,7 +3864,7 @@ - 9.67. set/badnode (6) + 9.78. set/badnode (6) set/badnode Stop spots from this node_call being propagated @@ -3421,7 +3898,7 @@ FILTERing. - 9.68. set/badspotter (8) + 9.79. set/badspotter (8) set/badspotter Stop spots from this callsign being propagated @@ -3455,15 +3932,41 @@ FILTERing. - 9.69. set/beep (0) + 9.80. set/badword (8) - set/beep Add beeps to terminal messages + 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 + + will allow text with this word again. + + + + 9.81. set/beep (0) + + set/beep Add beeps to terminal messages Add a beep to DX and other terminal messages. - 9.70. set/clx (5) + 9.82. set/bbs (5) + + set/bbs [..]Make a BBS + + + 9.83. set/clx (5) set/clx [ ...] Make the node_call a CLX type node @@ -3472,7 +3975,7 @@ Set the node_call as a CLX type node - 9.71. set/debug (9) + 9.84. set/debug (9) set/debug Add a debug level to the debug set @@ -3486,7 +3989,7 @@ You can remove a debug level with unset/debug - 9.72. set/dx (0) + 9.85. set/dx (0) set/dxAllow DX messages to arrive at your terminal @@ -3494,9 +3997,7 @@ You can stop DX messages with the unset/dx command - - - 9.73. set/dxgrid (0) + 9.86. set/dxgrid (0) set/dxgridAllow grid squares on the end of DX messages @@ -3506,7 +4007,7 @@ to remove the grid squares. - 9.74. set/dxnet (5) + 9.87. set/dxnet (5) set/dxnet [ ...] Make the node_call a DXNet type node @@ -3515,7 +4016,7 @@ Set the node_call as a DXNet type node - 9.75. set/echo (0) + 9.88. set/echo (0) set/echo Make the cluster echo your input @@ -3532,7 +4033,27 @@ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. - 9.76. set/here (0) + 9.89. set/email (0) + + 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 + + + 9.90. set/here (0) set/here Set the here flag @@ -3543,7 +4064,7 @@ brackets around your callsign to indicate you are not available. - 9.77. set/homenode (0) + 9.91. set/homenode (0) set/homenode Set your home cluster @@ -3560,9 +4081,7 @@ - - - 9.78. set/hops (8) + 9.92. set/hops (8) set/hops ann|spots|wwv|wcy Set hop count @@ -3571,9 +4090,6 @@ 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 @@ -3585,7 +4101,7 @@ creates a filter and works in conjunction with the filter system. - 9.79. set/isolate (9) + 9.93. set/isolate (9) set/isolate Isolate a node from the rest of the network @@ -3603,7 +4119,7 @@ You can remove the isolation with the command unset/isolate. - 9.80. set/language (0) + 9.94. set/language (0) set/language Set the language you wish to use @@ -3612,7 +4128,7 @@ Currently the languages available are en (English) and nl (Dutch). - 9.81. set/location (0) + 9.95. set/location (0) set/location Set your latitude and longitude @@ -3628,7 +4144,8 @@ - 9.82. set/sys_location (9) + + 9.96. set/sys_location (9) set/sys_location Set your cluster latitude and longitude @@ -3639,14 +4156,13 @@ example:- - SET/LOCATION 52 22 N 0 57 E - 9.83. set/logininfo (0) + 9.97. set/logininfo (0) set/logininfo Show logins and logouts of nodes and users @@ -3656,7 +4172,7 @@ - 9.84. set/lockout (9) + 9.98. set/lockout (9) set/lockout Stop a callsign connecting to the cluster @@ -3665,7 +4181,7 @@ allow the user to connect again, use the unset/lockout command. - 9.85. set/name (0) + 9.99. set/name (0) set/name Set your name @@ -3680,7 +4196,7 @@ - 9.86. set/node (9) + 9.100. set/node (9) set/node [ ...] Make the callsign an AK1A cluster @@ -3692,20 +4208,21 @@ + set/spider + set/dxnet + set/clx + set/arcluster + - set/spider - set/dxnet - set/clx - set/arcluster + To see what your nodes are set to, use the show/nodes command. - To see what your nodes are set to, use the show/nodes command. - 9.87. set/obscount (9) + 9.101. set/obscount (9) set/obscount Set the 'pump-up' obsolescence counter @@ -3726,7 +4243,7 @@ minutes, it is disconnected. - 9.88. set/page (0) + 9.102. set/page (0) set/page Set the number of lines per page @@ -3746,21 +4263,48 @@ The setting is stored in your user profile. + 9.103. set/password (0) - 9.89. set/password (9) + set/password Set your own password + + + This command only works for a 'telnet' user (currently). It will only + work if you have a password already set. This initial password can + only be set by the sysop. + + When you execute this command it will ask you for your old password, + then ask you to type in your new password twice (to make sure you get + it right). You may or may not see the data echoed on the screen as you + type, depending on the type of telnet client you have. + + + 9.104. set/password (9) set/password Set a users password The password for a user can only be set by a full sysop. The string - can contain any characters but any spaces are removed (you can type in - spaces - but they won't appear in the password). You can see the - result with STAT/USER. The password is the usual 30 character baycom - type password. + can contain any characters. + + The way this field is used depends on context. If it is being used in + the SYSOP command context then you are offered 5 random numbers and + you have to supply the corresponding letters. This is now mainly for + ax25 connections. + + If it is being used on incoming telnet connections then, if a password + is set or the: + + set/var $main::passwdreq = 1 + command is executed in the startup script, then a password prompt is + given after the normal 'login: ' prompt. + The command "unset/password" is provided to allow a sysop to remove a + users password completely in case a user forgets or loses their + password. - 9.90. set/pinginterval (9) + + 9.105. set/pinginterval (9) set/pinginterval