minor adds and changes

[spider.git] / html / adminmanual-1.html

diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html
index 1fb0df409d562287ba0b8d87a6162f032078635d..0a7924945ad3124ab4bcd84e69dffa0421ff1eb8 100644 (file)
--- a/html/adminmanual-1.html
+++ b/html/adminmanual-1.html
@@ -32,21 +32,21 @@ handle loops well at all.  It is therefore necessary to have some form
 of protection for these nodes.
 <P>
 <P>In fact DXSpider has had a simple system for some time which is called
 of protection for these nodes.
 <P>
 <P>In fact DXSpider has had a simple system for some time which is called

-<I>isolation</I>. This is similar to what, in other systems such as 
+<I>isolation</I>. This is similar to what in other systems such as 

 <B>clx</B>, is called <I>passive mode</I>. A more detailed explanation
 of <I>isolation</I> is given further below. This system is still available
 and, for simple networks, is probably all that you need.
 <P>
 <B>clx</B>, is called <I>passive mode</I>. A more detailed explanation
 of <I>isolation</I> is given further below. This system is still available
 and, for simple networks, is probably all that you need.
 <P>

-<P>The new functionality introduced in version 1.48 is filtering the node
+<P>The new functionality introduced in version 1.48 allows filtering the node

 and user protocol frames on a "per interface" basis. We call this
 <I>route filtering</I>. This is used <B>instead of</B>
 <I>isolation</I>. 
 <P>
 <P>What this really means is that you can control more or less completely
 and user protocol frames on a "per interface" basis. We call this
 <I>route filtering</I>. This is used <B>instead of</B>
 <I>isolation</I>. 
 <P>
 <P>What this really means is that you can control more or less completely

-which PC protocol frames, to do with user and node management, pass to
-each of your partner nodes. You can also limit what comes into your
-node from your partners. You can even control the settings that your
-partner node has for the routing information that it sends to you
+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 <I>rcmd</I> command).
 <P>
 <H2><A NAME="ss1.2">1.2 Route Filters</A>
 (using the <I>rcmd</I> command).
 <P>
 <H2><A NAME="ss1.2">1.2 Route Filters</A>


@@ -58,18 +58,25 @@ 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.
 <P>
 However using a default filter is an appropriate thing to do. How, is
 explained further on.
 <P>

-<P>The first thing that you must do is determine whether you need to do route filtering <B>at all</B>. If you are a "normal" node with two or three partners
-and you arranged in an "official" non-looping tree type network, then <B>you do 
-not need to do route filtering</B> and you will feel a lot better for not 
-getting involved. If you are successfully using <I>isolation</I> then you
-also probably don't need to use route filtering.
-<P>
-<P>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.
+<P>The first thing that you must do is determine whether you need to use 
+route filtering <B>at all</B>. If you are a "normal" node with two or 
+three partners and you arranged in an "official" non-looping tree type 
+network, then <B>you do not need to do route filtering</B> and you will 
+feel a lot better for not getting involved. If you are successfully using 
+<I>isolation</I> then you also probably don't need to use route filtering.
+<P>
+<P>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.
+<P>
+<P>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.

 <P>
 <P>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
 <P>
 <P>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


@@ -117,7 +124,8 @@ channel_zone &lt;numbers&gt;
 </PRE>
 </CODE></BLOCKQUOTE>
 <P>Please be careful if you alter this setting, it will affect 
 </PRE>
 </CODE></BLOCKQUOTE>
 <P>Please be careful if you alter this setting, it will affect 

-<B><I>ALL</I></B> your links!
+<B><I>ALL</I></B> your links!  Remember, this is a <I>default</I>
+filter for node connections, not a <I>per link</I> default.

 <P>
 <P>For the default routing filter then you have two real choices: either
 a "national" view or the "safe" option of only your own
 <P>
 <P>For the default routing filter then you have two real choices: either
 a "national" view or the "safe" option of only your own


@@ -154,9 +162,9 @@ 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.
 <P>
 by implication, any other node information (not from the UK and Eire)
 is accepted.
 <P>

-<P>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:-
+<P>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:-

 <P>
 <BLOCKQUOTE><CODE>
 <PRE>
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>


@@ -191,8 +199,8 @@ accept/route &lt;node_call&gt; &lt;filter_option&gt;
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>

-rej/route gb7djk call_dxcc 61,38 (everything except  UK+EIRE nodes)
-rej/route all     (equiv to [very] restricted mode)
+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)
 </PRE>
 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
 acc/route gb7djk call gb7djk     (equiv to SET/ISOLATE)
 </PRE>


@@ -206,7 +214,8 @@ acc/route gb7baa all
 acc/route gb7baa input all
 </PRE>
 </CODE></BLOCKQUOTE>
 acc/route gb7baa input all
 </PRE>
 </CODE></BLOCKQUOTE>

-<P>or restricting it quite a lot, in fact making it very nearly like an <I>isolated</I> node, like this:-
+<P>or restricting it quite a lot, in fact making it very nearly like an 
+<I>isolated</I> node, like this:-

 <P>
 <BLOCKQUOTE><CODE>
 <PRE>
 <P>
 <BLOCKQUOTE><CODE>
 <PRE>


@@ -218,9 +227,9 @@ rej/route pi4ehv-8 input call_dxcc 61,38
 but only sends him my local configuration (just a PC19 for GB7DJK and
 PC16s for my local users).
 <P>
 but only sends him my local configuration (just a PC19 for GB7DJK and
 PC16s for my local users).
 <P>

-<P>It is possible to do <B>much</B> more complex rules, there are up to 10
-accept/reject pairs per callsign per filter. For more information see the 
-next section. 
+<P>It is possible to write <B>much</B> more complex rules, there are up 
+to 10 accept/reject pairs per callsign per filter. For more information 
+see the next section. 

 <P>
 <P>
 <H2><A NAME="ss1.5">1.5 General filter rules</A>
 <P>
 <P>
 <H2><A NAME="ss1.5">1.5 General filter rules</A>


@@ -552,8 +561,7 @@ 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
 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 <EM>acc/spot &gt;call&lt; all</EM>ilter in the
-to override the isolate. 
+an <EM>acc/spot &gt;call&lt; all</EM> filter to override the isolate. 

 <P>
 <HR>
 <A HREF="adminmanual-2.html">Next</A>
 <P>
 <HR>
 <A HREF="adminmanual-2.html">Next</A>