X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-1.html;h=11d83731fda321787008b802ab71f28457823ee9;hb=0ee6f846f6d6eadd92f531137e29674464d62030;hp=78a3afcce12c625dae012178036e7a2516ed98be;hpb=6624dcdf07d628e8d6a16fc6549edf40be25b7b2;p=spider.git diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html index 78a3afcc..11d83731 100644 --- a/html/adminmanual-1.html +++ b/html/adminmanual-1.html @@ -2,7 +2,7 @@
--
This is achieved by using filtering on a route basis. There is a -default setting to help to protect the network, especially useful for new -and inexperienced SysOps. The idea is simple. When Spider is started -for the first time and a connection is made to or from another node, -the default is to only send the nodes you already have that are in your -own zone. For example, in the UK the default setting would be to send -only UK nodes to any connection. This can be filtered further (down to -a single node if needed) or expanded as required. +
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).
As mentioned in the introduction, a default setting exists. If this is -all you want to use then that is fine, you have nothing else to do. -However, if you want to make any alterations then you need to know -a bit about filters. -
-
It is possible to reset the default setting for node connections should -you wish to do so, however this can be dangerous to the network unless -you have some experience in how all this works.... be careful! It is -also possible to change settings for one connection only. You can, -therefore, have many different filters set dependent on the amount of -node links you have. +
Initially when route filters were being tested we generated a +"default" filter. Unfortunately it quickly became apparent that this +might suit the UK cluster network but didn't really fit anybody else. +However using a default filter is an appropriate thing to do. How, is +explained further on. +
+
The first thing that you must do is determine whether you need to use +route filtering at all. If you are a "normal" node with two or +three partners and you arranged in an "official" non-looping tree type +network, then you do not need to do route filtering and you will +feel a lot better for not getting involved. If you are successfully using +isolation then you also probably don't need to use route filtering. +
+
To put it simply, you should not mix Isolation and Route Filtering. It +will work, of sorts, but you will not get the expected results. If you +are using Isolation sucessfully at the moment, do not get involved in +Route Filtering unless you have a good supply of aspirin! Once you have +started down the road of Route Filtering, do not use Isolation either. +Use one or the other, not both. +
+
You will only require this functionality if you are "well-connected". What +that means is that you are connected to several different parts of (say) +the EU cluster and, at the same time, also connected to two or three places +in the US which, in turn are connected back to the EU. This is called a +"loop" and if you are seriously looped then you need filtering.
I should at this stage give a little bit of background on filters. All the filters in Spider work in basically the same way. You can either @@ -62,23 +84,31 @@ 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. +
+
As discussed previously, a default setting exists that only sends nodes -from your own zone. This can be overridden by using the default_node -filter option like this ... +
All normal systems should have a default routing filter and it should +usually be set to send only the normal, unlooped, view of your +"national" network. Here in the UK that means nodes from the UK and +Eire, in EU it is more complex as the networks there grew up in a more +intertwined way. +
+
+The generic commands are:-
-reject/route default_node <filter_option>
+reject/route node_default <filter_option>
or
-accept/route default_node <filter_option>
+accept/route node_default <filter_option>
-
where filter_option is one of the following ...
@@ -87,15 +117,67 @@ call <prefixes>
call_dxcc <numbers>
call_itu <numbers>
call_zone <numbers>
-origin <prefixes>
-origin_dxcc <numbers>
-origin_itu <numbers>
-origin_zone <numbers>
+channel <prefixes>
+channel_dxcc <numbers>
+channel_itu <numbers>
+channel_zone <numbers>
-
Please be careful if you alter this setting, it will affect -ALL your links! +ALL your links! Remember, this is a default +filter for node connections, not a per link default. +
+
For the default routing filter then you have two real choices: either +a "national" view or the "safe" option of only your own +callsign. Examples of each (for my node: GB7DJK) are:- +
+
+
+acc/route node_default call_dxcc 61,38
+acc/route node_default call gb7djk
+
+
+GB7DJK uses the first of these. The DXCC countries can be obtained from the +show/prefix command. +
+
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: +
+
+
+rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
+
+
+What this does is accept node and user information for our national +network from nodes that are in our national network, but rejects such +information from anyone else. Although it doesn't explicitly say so, +by implication, any other node information (not from the UK and Eire) +is accepted. +
+
As I imagine it will take a little while to get one's head around all of +this you can study the effect of any rules that you try by watching the +debug output after having done:- +
+
+
+set/debug filter
+
+
+After you have got tired of that, to put it back the way it was:- +
+
+
+unset/debug filter
+
+
-
where filter_option is one of the following ... +
Here are some examples of route filters ...
-call <prefixes>
-call_dxcc <numbers>
-call_itu <numbers>
-call_zone <numbers>
-origin <prefixes>
-origin_dxcc <numbers>
-origin_itu <numbers>
-origin_zone <numbers>
+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)
+In practice you will either be opening the default filter out for a +partner by defining a specific filter for that callsign:-
-
Here are some examples of route filters ... +
+
+acc/route gb7baa all
+acc/route gb7baa input all
+
+
+or restricting it quite a lot, in fact making it very nearly like an +isolated node, like this:-
-rej/route gb7djk call_dxcc 61,38 (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)
+acc/route pi4ehv-8 call gb7djk
+rej/route pi4ehv-8 input call_dxcc 61,38
+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. +
-
In general terms you can create a 'reject' or an 'accept' filter which can have +
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 ...
@@ -422,11 +515,48 @@ $def_hopcount = 5;
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.
+
SHould any of the nodecalls include an ssid, it is important to wrap the
+whole call in single quotes, like this ...
+
+
+
+ 'DB0FHF-15' => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+
+If you do not do this, you will get errors and the file will not work as
+expected.
+
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 Isolating networks
+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.
+
+
The set/hops command overrides any hops that you have set otherwise.
+
+
You can show 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
@@ -444,25 +574,12 @@ be sent as normal, so if a user on one network knows that you are a gateway for
another network, he can still still send a talk/announce etc message via your
node and it will be routed across.
-
The only limitation currently is that non-private messages cannot be passed down
-isolated links regardless of whether they are generated locally. This will change
-when the bulletin routing facility is added.
-
-
If you use isolate on a node connection you will continue to receive all
-information from the isolated partner, however you will not pass any information
-back to the isolated node. There are times when you would like to forward only
-spots across a link (maybe during a contest for example). To do this, isolate
-the node in the normal way and put in a filter in the /spider/filter/spots
-directory to override the isolate. This filter can be very simple and consists
-of just one line ....
-
-
-
-$in = [
- [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
-];
-
-
+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.
Next