X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=ac268bdc4c00b65a21f40dacacb50c3756ace0b9;hb=2bd682330ce9b04c95ddf05715cfb643da2df0ea;hp=158990c36b5cef02928adbe38b2fb5f6f1da9fd7;hpb=39e32c88a046b35281a6b1e6e8cf20703b4a9a03;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 158990c3..ac268bdc 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -362,18 +362,19 @@ made on the filename (if any) that you specify. 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:- +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. +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:- +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 @@ -384,25 +385,26 @@ and 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. +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). +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:- +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 freq 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: +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 freq hf/cw @@ -415,35 +417,38 @@ But in that case you might only be interested in iota and say:- accept/spots not freq 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. +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:- +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 freq/cw reject/spots 2 freq 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. +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. +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:- +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:- (freq 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'. +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:- @@ -462,20 +467,21 @@ 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: +my example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, eg: rej/spot freq hf/cw acc/spot freq 0/30000 acc/spot 2 freq 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. +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. +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. @@ -799,6 +805,24 @@ SP is an alias for SEND PRIVATE === 5^SET/ARCLUSTER [..]^Make the callsign an AR-Cluster node +=== 6^SET/BADNODE ^Stop spots from this callsign being propagated +=== 6^UNSET/BADNODE ^Allow spots from this callsign 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 can be a full or partial call (or a prefix), eg:- + + set/badnode K1TTT + +will stop anything from K1TTT (including any SSID's) + + unset/badnode K1TTT + +will allow spots from him again. + +Use with extreme care. This command may well be superceeded by FILTERing. + === 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 @@ -840,6 +864,19 @@ to you will normally find their way there should you not be connected. eg:- SET/HOMENODE gb7djk +=== 8^SET/HOPS ann|spots|wwv|wcy ^Set hop count +Set the hop count for a particular type of broadcast for a node. + +This command allows you to set up special hop counts for a node +for currently: announce, spots, wwv and wcy broadcasts. + +eg: + set/hops gb7djk ann 10 + set/hops gb7mbc spots 20 + +Set SHOW/HOPS for information on what is already set. This command +creates a filter and works in conjunction with the filter system. + === 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 @@ -959,6 +996,10 @@ Tell the system where you are. For example:- === 0^SET/WX^Allow WX messages to come out on your terminal === 0^UNSET/WX^Stop WX messages coming out on your terminal +=== 6^SHOW/BADNODE^Show all the bad nodes in the system +Display all the bad node callsigns in the system, see SET/BADNODE +for more information. + === 0^SHOW/CALL ^Show any callbook details on a callsign This command queries an international callbook server on the internet and returns any information available for that callsign. @@ -1047,6 +1088,11 @@ See also TYPE - to see the contents of a file. Show the contents of all the filters that are set. This command displays all the filters set - for all the various categories. +=== 8^SHOW/HOPS [ann|spots|wcy|wwv]^Show the hop counts for a node +This command shows the hop counts set up for a node. You can specify +which category you want to see. If you leave the category out then +all the categories will be listed. + === 1^SHOW/ISOLATE^Show list of ISOLATED nodes === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns