X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=10a4805cd2261165f0c5cb239fc86428ad8dc285;hb=d2c1a8cb2a31725e3b9084aee3ec43e585e3273f;hp=0b4766ed4c0e32cb0d75e8d081d67bee4f7021ac;hpb=4c92a7711c41cc7ba1c60d5a49a94db239032ac1;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 0b4766ed..10a4805c 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -11,23 +11,662 @@ # # Comment lines are indented before printing # +=== 0^ACCEPT/ANNOUNCE [0-9] ^Set an 'accept' filter line for announce +Create an 'accept this announce' line for a filter. + +An accept filter line means that if the announce matches this filter it is +passed onto the user. 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:- + + info eg: iota or qsl + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + origin_zone + by_dxcc + by_itu + by_zone + channel + wx 1 filter WX announces + dest eg: 6MUK,WDX (distros) + +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) +or + acc/ann by G,M,2 + +You can use the tag 'all' to accept everything eg: + + acc/ann all + +but this probably for advanced users... + +=== 8^ACCEPT/ANNOUNCE [input] [0-9] ^Announce filter sysop version +This version allows a sysop to set a filter for a callsign as well as the +default for nodes and users eg:- + + accept/ann by G,M,2 + accept/ann input node_default by G,M,2 + accept/ann user_default by G,M,2 + +=== 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 or: G,GM,GW + call_zone + origin really the interface it came in on + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + 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 + + +=== 0^ACCEPT/SPOTS [0-9] ^Set an 'accept' filter line for spots +Create an 'accept this spot' line for a filter. + +An accept filter line means that if the spot matches this filter it is +passed onto the user. 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:- + + 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) + call_itu or: G,GM,GW + call_zone + by_dxcc + by_itu + by_zone + origin + channel + +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:- + + acc/spot 1 on hf/cw + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + +You can use the tag 'all' to accept everything, eg: + + acc/spot 3 all + +but this probably for advanced users... + + +=== 8^ACCEPT/SPOTS [input] [0-9] ^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:- + + accept/spot db0sue-7 1 by_zone 14,15,16 + accept/spot node_default all + set/hops node_default 10 + + accept/spot user_default by G,M,2 + +=== 0^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 can +filter on the following fields:- + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + origin_zone + by_dxcc + by_itu + by_zone + channel + +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). + +This command is really provided for future use. + +See HELP FILTER for information. + +=== 8^ACCEPT/WCY [input] [0-9] ^WCY filter sysop version +This version allows a sysop to set a filter for a callsign as well as the +default for nodes and users eg:- + + accept/wcy node_default all + set/hops node_default 10 + +=== 0^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 can +filter on the following fields:- + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + origin_zone + by_dxcc + by_itu + by_zone + channel + +for example + + accept/wwv by_zone 4 + +is probably the only useful thing to do (which will only show WWV broadcasts +by stations in the US). + +See HELP FILTER for information. + +=== 8^ACCEPT/WWV [input] [0-9] ^WWV filter sysop version +This version allows a sysop to set a filter for a callsign as well as the +default for nodes and users eg:- + + accept/wwv db0sue-7 1 by_zone 4 + accept/wwv node_default all + set/hops node_default 10 + + accept/wwv user_default by W,K + === 0^ANNOUNCE ^Send an announcement to LOCAL users only + is the text of the announcement you wish to broadcast === 0^ANNOUNCE FULL ^Send an announcement cluster wide This will send your announcement cluster wide === 5^ANNOUNCE SYSOP ^Send an announcement to Sysops only -=== 0^ANNOUNCE- - is the text of the announcement you wish to broadcast +=== 0^APROPOS ^Search help database for +Search the help database for (it isn't case sensitive), and print +the names of all the commands that may be relevant. + +=== 0^BLANK [] []^Print nn (default 1) blank lines (or strings) +In its basic form this command prints one or more blank lines. However if +you pass it a string it will replicate the string for the width of the +screen (default 80) and then print that one or more times, so: + + blank 2 + +prints two blank lines + + blank - + +prints a row of - characters once. + + blank abc + +prints 'abcabcabcabcabcabc....' + +This is really only of any use in a script file and you can print a maximum +of 9 lines. === 0^BYE^Exit from the cluster This will disconnect you from the cluster - -=== 0^DX ^Send a DX spot throughout the cluster - is compared against the available bands set up in the cluster. -see show/bands for more information. +=== 5^CATCHUP All|[ ...]^Mark a message as sent +=== 5^UNCATCHUP All|[msgno> ...]^Unmark a message as sent +When you send messages the fact that you have forwarded it to another node +is remembered so that it isn't sent again. When you have a new partner +node and you add their callsign to your /spider/msg/forward.pl file, all +outstanding non-private messages will be forwarded to them. This may well +be ALL the non-private messages. You can prevent this by using these +commmands:- + + catchup GB7DJK all + catchup GB7DJK 300 301 302 303 500-510 + +and to undo what you have just done:- + + uncatchup GB7DJK all + uncatchup GB7DJK 300 301 302 303 500-510 + +which will arrange for them to be forward candidates again. + +Order is not important. + +=== 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line +This command allows you to clear (remove) a line in a annouce filter or to +remove the whole filter. + +see CLEAR/SPOTS for a more detailed explanation. + +=== 8^CLEAR/ANNOUNCE [input] [0-9|all]^Clear a announce filter line +A sysop can clear an input or normal output filter for a user or the +node_default or user_default. + +=== 0^CLEAR/ROUTE [1|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. + +=== 8^CLEAR/ROUTE [input] [0-9|all]^Clear a route filter line +A sysop can clear an input or normal output filter for a user or the +node_default or user_default. + +=== 0^CLEAR/SPOTS [0-9|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:- + + acc/spot 1 on hf/cw + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + +and you say:- + + clear/spot 1 + +you will be left with:- + + acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16) + +If you do: + + clear/spot all + +the filter will be completely removed. + +=== 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. + +=== 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. + +=== 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. + +=== 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. + +=== 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. + +=== 5^CONNECT ^Start a connection to another DX Cluster +Start a connection process that will culminate in a new connection to the +DX cluster . This process creates a new 'client' process which will +use the script in /spider/connect/ to effect the 'chat' exchange +necessary to traverse the network(s) to logon to the cluster . + +=== 9^DELETE/USER ...^Delete this 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! + +=== 0^DBAVAIL^Show a list of all the Databases in the system +Title says it all really, this command lists all the databases defined +in the system. It is also aliased to SHOW/COMMAND. + +=== 9^DBCREATE ^Create a database entry +=== 9^DBCREATE chain [..]^Create a chained database entry +=== 9^DBCREATE remote ^Create a remote database entry +DBCREATE allows you to define a database in the system. It doesn't actually +create anything, just defines it. + +The databases that are created are simple DB_File hash databases, they are +therefore already 'indexed'. + +You can define a local database with the first form of the command eg: + + DBCREATE oblast + +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 staement first then do each of +the chained databases. + +Databases can exist offsite. To define a database that lives on another +node do: + + DBCREATE buckmaster remote gb7dxc + +Remote databases cannot be chained; however, the last database in a +a chain can be a remote database eg: + + DBCREATE qsl chain gb7dxc + +To see what databases have been defined do: + + DBAVAIL (or it will have been aliased to SHOW/COMMAND) + +It would be normal for you to add an entry into your local Aliases file +to allow people to use the 'SHOW/' style syntax. So you would +need to add a line like:- + + 's' => [ + .. + .. + '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', + .. + .. + ], + +to allow + + SH/BUCK g1tlh + +to work as they may be used to. + +See DBIMPORT for the importing of existing AK1A format data to databases. +See DBSHOW for generic database enquiry + +=== 9^DBIMPORT ^Import AK1A data into a database +If you want to import or update data in bulk to a database you can use +this command. It will either create or update entries into an existing +database. For example:- + + DBIMPORT oblast /tmp/OBLAST.FUL + +will import the standard OBLAST database that comes with AK1A into the +oblast database held locally. + +=== 9^DBREMOVE ^Delete a database +DBREMOVE will completely remove a database entry and also delete any data +file that is associated with it. + +There is no warning, no comeback, no safety net. + +For example: + + DBREMOVE oblast + +will remove the oblast database from the system and it will also remove +the associated datafile. + +I repeat: + +There is no warning, no comeback, no safety net. + +You have been warned. + +=== 0^DBSHOW ^Display an entry, if it exists, in a database +This is the generic user interface to the database to the database system. +It is expected that the sysop will add an entry to the local Aliases file +so that users can use the more familiar AK1A style of enquiry such as: + + SH/BUCK G1TLH + +but if he hasn't and the database really does exist (use DBAVAIL or +SHOW/COMMAND to find out) you can do the same thing with: + + DBSHOW buck G1TLH + +=== 9^DEBUG^Set the cluster program into debug mode +Executing this command will only have an effect if you are running the cluster +in debug mode i.e. + + perl -d cluster.pl + +It will interrupt the cluster just after the debug command has finished. + +=== 0^DIRECTORY^List messages +=== 0^DIRECTORY ALL^List all messages +=== 0^DIRECTORY OWN^List your own messages +=== 0^DIRECTORY NEW^List all new messages +=== 0^DIRECTORY TO ^List all messages to +=== 0^DIRECTORY FROM ^List all messages from +=== 0^DIRECTORY SUBJECT ^List all messages with in subject +=== 0^DIRECTORY ^List last messages +=== 0^DIRECTORY -^List messages message message +List the messages in the messages directory. + +If there is a 'p' one space after the message number then it is a +personal message. If there is a '-' between the message number and the +'p' then this indicates that the message has been read. + +You can use shell escape characters such as '*' and '?' in the +fields. + +You can combine some of the various directory commands together eg:- + + DIR TO G1TLH 5 +or + DIR SUBJECT IOTA 200-250 + +You can abbreviate all the commands to one letter and use ak1a syntax:- + + DIR/T G1* 10 + DIR/S QSL 10-100 5 + +=== 5^DIRECTORY-^ +Sysops can see all users' messages. + +=== 8^DISCONNECT [ ...]^Disconnect a user or cluster +Disconnect any connected locally + +=== 0^DX [BY ] ^Send a DX spot +This is how you send a DX Spot to other users. You can, in fact, now +enter the and the either way round. + + DX FR0G 144.600 + DX 144.600 FR0G + DX 144600 FR0G + +will all give the same result. You can add some remarks to the end +of the command and they will be added to the spot. + + DX FR0G 144600 this is a test + +You can credit someone else by saying:- + + DX by G1TLH FR0G 144.600 he isn't on the cluster + +The is compared against the available bands set up in the +cluster. See SHOW/BANDS for more information. + +=== 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 the import +directory (/spider/msg/import). + +This command cannot overwrite an existing file. This is to provide some +measure of security. Any files written will owned by the same user as the +main cluster, otherwise you can put the new files anywhere the cluster can +access. For example:- + + EXPORT 2345 /tmp/a + +=== 9^EXPORT_USERS []^Export the users database to ascii +Export the users database to a file in ascii format. If no filename +is given then it will export the file to /spider/data/user_asc. + +If the file already exists it will be renamed to .o. In fact +up to 5 generations of the file can be kept each one with an extra 'o' on the +suffix. + +BE WARNED: this will write to any file you have write access to. No check is +made on the filename (if any) that you specify. + +=== 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 +'0'-'9' are available. + +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 +'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 +thru everything else on HF. + +The next filter line lets through just VHF/UHF spots from EU. + +=== 8^FORWARD/LATLONG ^Send latitude and longitude information to another cluster +This command sends all the latitude and longitude information that 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 +SET/DXGRID enabled. This could be a LOT of information though, so +it is not recommended on slow links. + +=== 1^FORWARD/OPERNAM ^Send out information on this to all clusters +This command sends out any information held in the user file which can +be broadcast in PC41 protocol packets. This information is Name, QTH, Location +and Homenode. PC41s are only sent for the information that is available. + === 0^HELP^The HELP Command HELP is available for a number of commands. The syntax is:- @@ -36,7 +675,726 @@ HELP is available for a number of commands. The syntax is:- Where is the name of the command you want help on. All commands can be abbreviated, so SHOW/DX can be abbreviated -to SH/DX, ANNOUNCE can be shorted to AN and so on. +to SH/DX, ANNOUNCE can be shortened to AN and so on. + +Look at the APROPOS command which will search the help database +for the you specify and give you a list of likely commands +to look at with HELP. + +=== 5^INIT ^Re-initialise a link to an AK1A compatible node +This command attempts to re-initialise a link to a (usually) AK1A node +that has got confused, usually by a protocol loop of some kind. It may +work - but you usually will be better off simply disconnecting it (or +better, if it is a real AK1A node, doing an RCMD DISC/F ). + +Best of luck - you will need it. + +=== 0^KILL [ [ [/]^Ask for the latest spots and WWV +MERGE allows you to bring your spot and wwv database up to date. By default +it will request the last 10 spots and 5 WWVs from the node you select. The +node must be connected locally. + +You can request any number of spots or wwv and although they will be appended +to your databases they will not duplicate any that have recently been added +(the last 2 days for spots and last month for WWV data). + +=== 9^MSG [data ... ]^Alter various message parameters +Alter message parameters like To, From, Subject, whether private or bulletin +or return receipt (RR) is required or whether to keep this message from timing +out. + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waitting time for this message + MSG NOREad - mark message as unread + MSG REad - mark message as read + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages + +You can look at the status of a message by using:- + + STAT/MSG + +This will display more information on the message than DIR does. + +=== 8^PC ^Send text (eg PC Protocol) to +Send some arbitrary text to a locally connected callsign. No +processing is done on the text. This command allows you to send PC +Protocol to unstick things if problems arise (messages get stuck +etc). eg:- + + pc gb7djk PC33^GB7TLH^GB7DJK^400^ +or + pc G1TLH Try doing that properly!!! + +=== 0^KILL [ ...]^Remove or erase a message from the system +You can get rid of any message to or originating from your callsign using +this command. You can remove more than one message at a time. + +=== 5^KILL -^Remove a range of messages from the system +=== 5^KILL FROM ^Remove all messages from a callsign +=== 5^KILL TO ^Remove all messages to a callsign +=== 5^KILL FULL [ ^Send arbitrary text to a connected callsign +Send any text you like to the callsign requested. This is used mainly to send +PC protocol to connected nodes either for testing or to unstick things. + +You can also use in the same way as a talk command to a connected user but +without any processing, added of "from to ^Check the link quality between nodes +This command allows you to send a frame to another cluster node on +the network and get a return frame. The time it takes to do this +is a good indication of the quality of the link. The actual time +it takes is output to the console in seconds. +Any visible cluster node can be PINGed. + +=== 1^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. + +=== 0^READ^Read the next unread personal message addressed to you +=== 0^READ ^Read the specified message +You can read any messages that are sent as 'non-personal' and also any +message either sent by or sent to your callsign. + +=== 5^READ-^ +As a sysop you may read any message on the system + +=== 0^REJECT/ANNOUNCE [0-9] ^Set a 'reject' filter line for announce +Create an 'reject this announce' line for a filter. + +A reject filter line means that if the announce matches this filter it is +passed onto the user. 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:- + + info eg: iota or qsl + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + origin_zone + by_dxcc + by_itu + by_zone + channel + wx 1 filter WX announces + dest eg: 6MUK,WDX (distros) + +some examples:- + + rej/ann by_zone 14,15,16 and not by G,M,2 + +You can use the tag 'all' to reject everything eg: + + rej/ann all + +but this probably for advanced users... + +=== 8^REJECT/ANNOUNCE [input] [0-9] ^Announce filter sysop version +This version allows a sysop to set a filter for a callsign as well as the +default for nodes and users eg:- + + reject/ann by G,M,2 + reject/ann input node_default by G,M,2 + reject/ann user_default by G,M,2 + +=== 0^REJECT/SPOTS [0-9] ^Set a 'reject' filter line for spots +Create a 'reject this spot' line for a filter. + +A reject filter line means that if the spot matches this filter it is +dumped (not passed on). See HELP 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:- + + 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) + call_itu or: G,GM,GW + call_zone + by_dxcc + by_itu + by_zone + origin + channel + +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: on HF (but don't get +too hung up about that) + +some examples:- + + rej/spot 1 on hf + rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16) + +You can use the tag 'all' to reject everything eg: + + rej/spot 3 all + +but this probably for advanced users... + +=== 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 or: G,GM,GW + call_zone + origin really the interface it came in on + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + 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) + +=== 8^REJECT/SPOTS [input] [0-9] ^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:- + + 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 + +=== 0^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 can +filter on the following fields:- + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + origin_zone + by_dxcc + by_itu + by_zone + channel + +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). + +This command is really provided for future use. + +See HELP FILTER for information. + +=== 8^REJECT/WCY [input] [0-9] ^WCY 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:- + + reject/wcy gb7djk all + +=== 0^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 can +filter on the following fields:- + + by eg: G,M,2 + origin + origin_dxcc eg: 61,62 (from eg: sh/pre G) + origin_itu or: G,GM,GW + origin_zone + by_dxcc + by_itu + by_zone + channel + +for example + + reject/wwv by_zone 14,15,16 + +is probably the only useful thing to do (which will only show WWV broadcasts +by stations in the US). + +See HELP FILTER for information. + +=== 8^REJECT/WWV [input] [0-9] ^WWV 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:- + + reject/wwv db0sue-7 1 by_zone 4 + reject/wwv node_default all + + reject/wwv user_default by W + +=== 0^REPLY^Reply (privately) to the last message that you have read +=== 0^REPLY ^Reply (privately) to the specified message +=== 0^REPLY B ^Reply as a Bulletin to the specified message +=== 0^REPLY NOPrivate ^Reply as a Bulletin to the specified message +=== 0^REPLY RR ^Reply to the specified message with read receipt +You can reply to a message and the subject will automatically have +"Re:" inserted in front of it, if it isn't already present. + +You can also use all the extra qualifiers such as RR, PRIVATE, +NOPRIVATE, B that you can use with the SEND command (see SEND +for further details) + +=== 0^SEND [ ...]^Send a message to one or more callsigns +=== 0^SEND RR ^Send a message and ask for a read receipt +=== 0^SEND COPY ^Send a copy of a message to someone +=== 0^SEND PRIVATE ^Send a personal message +=== 0^SEND NOPRIVATE ^Send a message to all stations +All the SEND commands will create a message which will be sent either to +an individual callsign or to one of the 'bulletin' addresses. + +SEND on its own acts as though you had typed SEND PRIVATE, that is +it will mark the message as personal and send it to the cluster node that +that callsign is connected to. + +You can have more than one callsign in all of the SEND commands. + +You can have multiple qualifiers so that you can have for example:- + + SEND RR COPY 123 PRIVATE G1TLH G0RDI + +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. + +SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) +SP is an alias for SEND PRIVATE + +=== 0^SET/ADDRESS ^Record your postal address + +=== 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal +=== 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal + +=== 0^SET/ANNTALK^Allow talk like announce messages on your terminal +=== 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal +The announce system on legacy cluster nodes is used as a talk +substitute because the network is so poorly connected. If you: + + unset/anntalk + +you will suppress several of these announces, you may miss the odd +useful one as well, but you would probably miss them anyway in the +welter of useless ones. + + set/anntalk + +allows you to see them again. This is the default. + +=== 5^SET/ARCLUSTER [..]^Make the callsign an AR-Cluster node + +=== 8^SET/BADDX ..^Stop callsigns in a dx spot being propagated +=== 8^UNSET/BADDX ..^Propagate a dx spot with this callsign again +Setting a word as 'baddx' will prevent spots with that word in the +'spotted' field (as in: DX 14001.1 FR0G)of a DX spot 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/baddx FORSALE VIDEO FR0G + +To allow a word again, use the following command ... + + unset/baddx VIDEO + +=== 8^SET/BADNODE ..^Stop spots from this node being propagated +=== 8^UNSET/BADNODE ..^Allow spots from this node again +Setting a callsign as a 'badnode' will prevent spots from that node +going any further. They will not be displayed and they will not be +sent onto other nodes. + +The call must be a full eg:- + + set/badnode K1TTT + +will stop anything from K1TTT. If you want SSIDs as well then you must +enter them specifically. + + unset/badnode K1TTT + +will allow spots from him again. + +Use with extreme care. This command may well be superceeded by FILTERing. + +=== 8^SET/BADSPOTTER ..^Stop spots from this callsign being propagated +=== 8^UNSET/BADSPOTTER ..^Allow spots from this callsign again +Setting a callsign as a 'badspotter' will prevent spots from this callsign +going any further. They will not be displayed and they will not be +sent onto other nodes. + +The call must be written in full, no wild cards are allowed eg:- + + set/badspotter VE2STN + +will stop anything from VE2STN. If you want SSIDs as well then you must +enter them specifically. + + unset/badspotter VE2STN + +will allow spots from him again. + +Use with extreme care. This command may well be superceded by FILTERing. + +=== 8^SET/BADWORD ..^Stop things with this word being propagated +=== 8^UNSET/BADWORD ..^Propagate things with this word again +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/badspotter annihilated + +will allow text with this word again. + +=== 0^SET/BEEP^Add a beep to DX and other messages on your terminal +=== 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal + +=== 5^SET/BBS [..]^Make the callsign a BBS + +=== 5^SET/CLX [..]^Make the callsign an CLX node + +=== 9^SET/DEBUG ^Add a debug level to the debug set +=== 9^UNSET/DEBUG ^Remove a debug level from 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 SHOW/DEBUG + +=== 0^SET/DX^Allow DX messages to come out on your terminal +=== 0^UNSET/DX^Stop DX messages coming out on your terminal + +=== 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements +=== 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements +A standard feature which is enabled in version 1.43 and above is +that if the spotter's grid square is known it is output on the end +of a DX announcement (there is just enough room). Some user programs +cannot cope with this. You can use this command to reset (or set) +this feature. + +=== 5^SET/DXNET [..]^Make the callsign an DXNet node + +=== 0^SET/ECHO^Make the cluster echo your input +=== 0^UNSET/ECHO^Stop the cluster echoing your input +If you are connected via a telnet session, different implimentations +of telnet handle echo differently depending on whether you are +connected via port 23 or some other port. You can use this command +to change the setting appropriately. + +The setting is stored in your user profile. + +YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. + +=== 0^SET/HERE^Tell the system you are present at your terminal +=== 0^UNSET/HERE^Tell the system you are absent from your terminal + +=== 0^SET/HOMENODE ^Set your normal cluster callsign +Tell the cluster system where you normally connect to. Any Messages sent +to you will normally find their way there should you not be connected. +eg:- + SET/HOMENODE gb7djk + +=== 8^SET/HOPS ann|spots|route|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. + +=== 9^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 protocol +member of its network and can see all spots on it, but nothing either leaks +out from it nor goes back into from the rest of the nodes connected to you. + +You can potentially connect several nodes in this way. + +=== 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network +Remove isolation from a node - SET/ISOLATE + +=== 0^SET/LANGUAGE ^Set the language you want to use +You can select the language that you want the cluster to use. Currently +the languages available are en (english) and nl (dutch). + +=== 0^SET/LOCATION ^Set your latitude and longitude +=== 9^SET/SYS_LOCATION ^Set your cluster latitude and longitude +In order to get accurate headings and such like you must tell the system +what your latitude and longitude is. If you have not yet done a SET/QRA +then this command will set your QRA locator for you. For example:- + SET/LOCATION 52 22 N 0 57 E + +=== 0^SET/LOGININFO^Inform when a station logs in locally +=== 0^UNSET/LOGININFO^Inform when a station logs out locally + +=== 9^SET/LOCKOUT ^Stop a callsign connecting to the cluster +=== 9^UNSET/LOCKOUT ^Allow a callsign to connect to the cluster + +=== 0^SET/NAME ^Set your name +Tell the system what your name is eg:- + SET/NAME Dirk + +=== 5^SET/NODE [..]^Make the callsign an AK1A cluster +Tell the system that the call(s) are to be treated as AK1A cluster and +fed PC Protocol rather normal user commands. + +=== 8^SET/OBSCOUNT ^Set the 'pump-up' obscelence counter +From 1.35 onwards neighbouring nodes are pinged at regular intervals (see +SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' +counter which is decremented on every outgoing ping and then reset to +the 'obscount' value on every incoming ping. The default value of this +parameter is 2. + +What this means is that a neighbouring node will be pinged twice at +(default) 300 second intervals and if no reply has been heard just before +what would be the third attempt, that node is disconnected. + +If a ping is heard then the obscount is reset to the full value. Using +default values, if a node has not responded to a ping within 15 minutes, +it is disconnected. + +You can set this parameter between 1 and 9. + +It is STRONGLY recommended that you don't change the default. + +=== 0^SET/PAGE ^Set the lines per page +Tell the system how many lines you wish on a page when the number of line +of output from a command is more than this. The default is 20. Setting it +explicitly to 0 will disable paging. + SET/PAGE 30 + SET/PAGE 0 + +The setting is stored in your user profile. + +=== 9^SET/PINGINTERVAL