X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fhops.html;h=ebe3b479c611f397faa152a05ded31e442a3e7c1;hb=refs%2Fheads%2Fnewpc92timings;hp=5ffa84c38ab11323ce2842debc6a8e7be20099ad;hpb=cce161221036760959ff1d0b7628a55942bf558a;p=spider.git diff --git a/html/hops.html b/html/hops.html index 5ffa84c3..ebe3b479 100644 --- a/html/hops.html +++ b/html/hops.html @@ -5,6 +5,7 @@ + @@ -19,7 +20,7 @@

-Last modified: Sun Dec 20 18:15:15 GMT 1998 +Last modified: Fri Jan 19 14:25:13 GMT 2001

Introduction

@@ -41,11 +42,11 @@ Last modified: Sun Dec 20 18:15:15 GMT 1998 values.

From version 1.13 onwards a new mechanism has been introduced - which uses a file called /spider/data/hop_count.pl. The + which uses a file called /spider/data/hop_table.pl. The prefered way of doing basic hop control is now to create this file and modify it as you wish. Eventually this file will contain all the hop control and related information. An example of the - hop_count.pl file can be found in the + hop_table.pl file can be found in the /spider/examples directory.

You can change this file at any time, including when the @@ -57,7 +58,7 @@ Last modified: Sun Dec 20 18:15:15 GMT 1998 From version 1.13 it is possible to control the number of hops to each node. This is done by adding information to the %nodehops perl - variable in the hop_count.pl file (as described above). This + variable in the hop_table.pl file (as described above). This variable is a perl "hash of hashes", which means that you create an entry for every callsign you wish to control and then one line for every PC protocol message that you wish to alter. @@ -66,7 +67,7 @@ Last modified: Sun Dec 20 18:15:15 GMT 1998 so you can set the hops as a whole for all PC messages to just that callsign. This is overridden by any specific hop counts you may have. -

Example hop_count.pl File

+

Example hop_table.pl File

An example for you:- @@ -120,7 +121,7 @@ $def_hopcount = 15; is working at least as well as advertised) you should keep the default hop counts down to the sort of levels shown above. -

Isolated Networks

+

Isolated Networks

It is possible to isolate networks from each other on a "gateway" node using the set/isolate <node call> command.