The crucial ingredient for all of this is Perl. Earlier versions of
Spider required perl 5.004, however it is now \e[4mSTRONGLY\e[24m recommended
- that you use at least version 5.005_03 as this is the version being
- used in the development of Spider.
+ that you use at least version 5.6.1 as this is the version being used
+ in the development of Spider.
In addition to the standard Red Hat distribution you will require the
- o Data-Dumper-2.101.tar.gz
+ o Data-Dumper-2.101.tar.gz \e[4mthis\e[24m \e[4mis\e[24m \e[4mincluded\e[24m \e[4min\e[24m \e[4mperl\e[24m \e[4m5.6.1\e[24m \e[4mand\e[24m \e[4mabove\e[0m
o TimeDate-1.10.tar.gz
- o IO-1.20.tar.gz (for perl 5.00403 and lower)
+ o IO-1.20.tar.gz (\e[4mfor\e[24m \e[4mperl\e[24m \e[4m5.00403\e[24m \e[4mand\e[24m \e[4mlower\e[24m)
o Net-Telnet-3.03.tar.gz
- # tar xvfz /usr/local/packages/Data-Dumper-2.101.tar.gz
- # cd Data-Dumper-2.101
- # perl Makefile.PL
- # make test
- # make install
- # cd ..
- #
# tar xvfz /usr/local/packages/TimeDate-1.10.tar.gz
# cd TimeDate-1.10
# perl Makefile.PL
# make install
# cd ..
#
- # tar xvfz /usr/local/packages/IO-1.20.tar.gz
- # cd IO-1.20
- # perl Makefile.PL
- # make test
- # make install UNINST=1
- # cd ..
- #
# tar xvfz /usr/local/packages/Net-Telnet-3.03.tar.gz
# cd Net-Telnet-3.02
# perl Makefile.PL
+ Only if you need to do these (because your perl is old):-
+
+
+ #
+ # tar xvfz /usr/local/packages/IO-1.20.tar.gz
+ # cd IO-1.20
+ # perl Makefile.PL
+ # make test
+ # make install UNINST=1
+ # cd ..
+ #
+ # tar xvfz /usr/local/packages/Data-Dumper-2.101.tar.gz
+ # cd Data-Dumper-2.101
+ # perl Makefile.PL
+ # make test
+ # make install
+ # cd ..
+ #
+
+
+
Do not fall into the trap of thinking they're all the same, just
because they nearly are! Pay particular attention to the instructions
of \e[4mIO\e[24m, above.
- # vi /etc/group (or your favorite editor)
+ # vi /etc/group (or your favorite editor)
Using the distributed DXVars.pm as a a template, set your cluster
callsign, sysop callsign and other user info to suit your own
environment.
-
-
-
$mycall = "GB7DJK";
- This is the call sign of your cluster. If you use an SSID then
- include it here also.
+ This is the call sign of your cluster. Here in the UK we have
+ separate callsigns for our cluster nodes. If you can't use a different
+ callsign I suggest you use an SSID of '-2' for the node callsign
+ '$mycall'.
use it though it has to be "made". CD to /spider/src and type \e[4mmake\e[24m.
You should see the output on your screen and hopefully now have a
small C program called \e[4mclient\e[24m. Leave it in this directory.
+
+
+
\e[1m1.6. Starting up for the first time\e[0m
We can now bring spider up for the first time and see if all is well
- shutdown
+ shutdown
o Enter the correct line in /etc/services (root)
+
o Enter the correct line in /etc/inetd.conf (root)
o killall -HUP inetd (root)
There are 2 main node packages in use of which I shall keep to the
original by Tomi Manninen, OH2BNS as this is included in the ax25 rpms
as standard. The other is AWZNode by IZ5AWZ.
-
-
NB: The AX25 stuff in 2.4 kernels appears to have been broken until
2.4.18. I strongly suggest you get at least this kernel.
NOTE:- before we start it is important to realise that every interface
requires a different SSID. You should be able to follow this in the
following examples.
+
+
\e[1m3.5. axports\e[0m
This file sets up the ax25 ports you want to use. An example is below
The file headings are as follows ...
+
portname - The name you will refer to the port by
callsign - This is the callsign that NET/ROM traffic from this
port will use
down this route!
- \e[1m' \e[22m' is the delimiting character for a word or phrase of an
- expect/send line in a chat type script. The words/phrases
- normally come in pairs, either can be empty. Each line reads
- input from the connection until it sees the string (or perl
- regular expression) contained in the left hand string. If the
- left hand string is empty then it doesn't read or wait for
- anything. The comparison is done ignoring case. When the left
- hand string has found what it is looking for (if it is) then the
- right hand string is sent to the connection. This process is
- repeated for every line of chat script.
+ \e[1m' \e[22mline in a chat type script. The words/phrases normally come in
+ pairs, either can be empty. Each line reads input from the
+ connection until it sees the string (or perl regular expression)
+ contained in the left hand string. If the left hand string is
+ empty then it doesn't read or wait for anything. The comparison
+ is done ignoring case. When the left hand string has found what
+ it is looking for (if it is) then the right hand string is sent
+ to the connection. This process is repeated for every line of
+ chat script.
\e[1mclient\e[0m
# you can leave this out if you call this script 'gb7djk'
client gb7djk telnet
+
Both these examples assume that everything is set up properly at the
other end. You will find other examples in the /spider/examples
directory.
projects / spider.git / blobdiff