1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
5 <TITLE>The DXSpider Installation and Administration Manual : Hop control</TITLE>
6 <LINK HREF="adminmanual-6.html" REL=next>
7 <LINK HREF="adminmanual-4.html" REL=previous>
8 <LINK HREF="adminmanual.html#toc5" REL=contents>
9 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="adminmanual-6.html">Next</A>
13 <A HREF="adminmanual-4.html">Previous</A>
14 <A HREF="adminmanual.html#toc5">Contents</A>
16 <H2><A NAME="s5">5. Hop control</A></H2>
18 <P>Starting with version 1.13 there is simple hop control available on a per
19 node basis. Also it is possible to isolate a network completely so that you
20 get all the benefits of being on that network, but can't pass on information
21 from it to any other networks you may be connected to (or vice versa).
23 <H2><A NAME="ss5.1">5.1 Basic hop control</A>
26 <P>In /spider/data you will find a file called hop_table.pl. This is the file
27 that controls your hop count settings. It has a set of default hops on the
28 various PC frames and also a set for each node you want to alter the hops for.
29 You may be happy with the default settings of course, but this powerful tool
30 can help to protect and improve the network. The file will look something
36 # hop table construction
41 # default hopcount to use
44 # some variable hop counts based on message type
55 # the per node hop control thingy
87 <P>Each set of hops is contained within a pair of curly braces and contains a
88 series of PC frame types. PC11 for example is a DX spot. The figures here
89 are not exhaustive but should give you a good idea of how the file works.
91 <P>You can alter this file at any time, including whilst the cluster is running.
92 If you alter the file during runtime, the command <EM>load/hops</EM> will
93 bring your changes into effect.
95 <H2><A NAME="ss5.2">5.2 Isolating networks</A>
98 <P>It is possible to isolate networks from each other on a "gateway" node using the
99 <EM>set/isolate <node_call></EM> command.
101 <P>The effect of this is to partition an isolated network completely from another
102 nodes connected to your node. Your node will appear on and otherwise behave
103 normally on every network to which you are connected, but data from an isolated
104 network will not cross onto any other network or vice versa. However all the
105 spot, announce and WWV traffic and personal messages will still be handled
106 locally (because you are a real node on all connected networks), that is locally
107 connected users will appear on all networks and will be able to access and
108 receive information from all networks transparently. All routed messages will
109 be sent as normal, so if a user on one network knows that you are a gateway for
110 another network, he can still still send a talk/announce etc message via your
111 node and it will be routed across.
113 <P>The only limitation currently is that non-private messages cannot be passed down
114 isolated links regardless of whether they are generated locally. This will change
115 when the bulletin routing facility is added.
117 <P>If you use isolate on a node connection you will continue to receive all
118 information from the isolated partner, however you will not pass any information
119 back to the isolated node. There are times when you would like to forward only
120 spots across a link (maybe during a contest for example). To do this, isolate
121 the node in the normal way and put in a filter in the /spider/filter/spots
122 directory to override the isolate. This filter can be very simple and consists
123 of just one line ....
128 [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
133 <P>There is a lot more on filtering in the next section.
136 <A HREF="adminmanual-6.html">Next</A>
137 <A HREF="adminmanual-4.html">Previous</A>
138 <A HREF="adminmanual.html#toc5">Contents</A>