-<P>This section describes the installation of DX Spider v1.46 on a
-<A HREF="http://www.redhat.com">RedHat</A> Linux Distribution.
-Wherever possible I will try to include differences for other distributions.
-I do not intend to try and cover the installation of Linux or the setup
-of the AX25 utilities. If you need help on this then read Iains original
-installation guide that comes with the Spider distribution.
-<P>
-<P>I am assuming a general knowledge of Linux and its commands. You should
-know how to use <EM>tar</EM> and how to edit files using your favourite editor.
-<P>
-<P>The crucial ingredient for all of this is
-<A HREF="http://www.perl.org">Perl</A>. Earlier versions of
-Spider required perl 5.004, however it is now <I>STRONGLY</I> recommended
-that you use at least version 5.005_03 as this is the version being used
-in the development of Spider.
-<P>
-<P>In addition to the standard Red Hat distribution you will require the
-following modules from
-<A HREF="http://www.cpan.org/CPAN.html">http://www.cpan.org/CPAN.html</A> ...
+<P>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.
+<P>
+<P>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.
+<P>
+<P>
+<H2><A NAME="ss1.2">1.2 Route Filters</A>
+</H2>
+
+<P>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.
+<P>
+<P>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.
+<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
+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.
+<P>
+<H2><A NAME="ss1.3">1.3 The default_node filter</A>
+</H2>
+
+<P>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 ...