+ # the per node hop control thingy
+
+
+ %nodehops =
+
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
+
+
+
+
+
+ Each set of hops is contained within a pair of curly braces and
+ contains a 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. 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 set 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 set/isolate <node_call> command.
+
+
+ The effect of this is to partition an isolated network completely from
+ another node connected to your node. Your node will appear on and
+ otherwise behave normally on every network to which you are connected,
+ but data from an isolated network will not cross onto any other
+ network or vice versa. However all the spot, announce and WWV traffic
+ and personal messages will still be handled locally (because you are a
+ real node on all connected networks), that is locally connected users
+ will appear on all networks and will be able to access and receive
+ information from all networks transparently. All routed messages will
+ 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.
+
+
+ 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.
+
+
+ 2. Other filters
+
+ 2.1. Filtering Mail
+
+ In the /spider/msg directory you will find a file called
+ badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
+ original looks something like this ....
+
+
+
+
+ # the list of regexes for messages that we won't store having
+ # received them (bear in mind that we must receive them fully before
+ # we can bin them)
+
+
+ # The format of each line is as follows
+
+ # type source pattern
+ # P/B/F T/F/O/S regex
+
+ # type: P - private, B - bulletin (msg), F - file (ak1a bull)
+ # source: T - to field, F - from field, O - origin, S - subject
+ # pattern: a perl regex on the field requested
+
+ # Currently only type B and P msgs are affected by this code.
+ #
+ # The list is read from the top down, the first pattern that matches
+ # causes the action to be taken.
+
+ # The pattern can be undef or 0 in which case it will always be selected
+ # for the action specified
+
+
+
+ package DXMsg;
+
+ @badmsg = (
+ );
+
+