- 4.2 Allowing telnet connects from users
- 4.3 Setting up telnet connects (from 1.47 onwards)
+ 4.2 Setting up telnet connects (from 1.47 onwards)
+ 4.3 Allowing telnet connects from users (before version 1.47 or for special purposes)
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
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.
+
+ On most modern distributions most (if not all) the modules you will
+ need are either included or can be loaded automatically. Please
+ consult your distro's instructions for loading new programs and look
+ for modules that usually start with the string "perl-". For instance:-
+
+
+ o Mandrake: urpmi perl-TimeDate perl-Digest-SHA1 perl-Curses perl-
+ Net-Telnet
+
+ o Redhat/Fedora: up2date perl-TimeDate perl-Digest-SHA1 perl-Curses
+ perl-Net-Telnet
+
+ o SuSE: use yast
+
+ o Debian: use apt-get
+
+
+ Some distros are now packaging perl-DB_File separately as well, so you
+ may have to add that to the list above.
+
+
Copy the CPAN modules listed above to a convenient place on your
computer. One good place would be /usr/local/packages, and the
instructions which follow will assume that that's where you have put
Copy the CPAN modules listed above to a convenient place on your
computer. One good place would be /usr/local/packages, and the
instructions which follow will assume that that's where you have put
\e[1m1.3. Installing the software\e[0m
Now to unpack the DX Spider distribution, set symbolic links and group
\e[1m1.3. Installing the software\e[0m
Now to unpack the DX Spider distribution, set symbolic links and group
- 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.
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
\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
This should log you into the cluster as the sysop under the alias
callsign we set earlier. In this case the callsign is G0VGS. The
cluster callsign is set in the DXVars.pm file in /spider/local. In
This should log you into the cluster as the sysop under the alias
callsign we set earlier. In this case the callsign is G0VGS. The
cluster callsign is set in the DXVars.pm file in /spider/local. In
more comprehensive and an interesting configuration program is also
available called ax25-config which may help you to configure things.
more comprehensive and an interesting configuration program is also
available called ax25-config which may help you to configure things.
The following files are extracts from the working files at GB7MBC and
are in daily use. However, there are many ways that you can configure
the ax25 utils, this is just the one I use, it does not mean it is
The following files are extracts from the working files at GB7MBC and
are in daily use. However, there are many ways that you can configure
the ax25 utils, this is just the one I use, it does not mean it is
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.
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.
- #portname callsign alias paclen description
- netrom gb7mbc-8 BARE 236 Node Netrom Port
- netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
+ #portname callsign alias paclen description
+ netrom gb7mbc-8 BARE 236 Node Netrom Port
+ netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
+ >From version 1.47 you can choose to allow the perl cluster.pl program
+ to allow connections directly (i.e. not via the /spider/src/client
+ interface program). If you are using Windows then this is the only
+ method available of allowing incoming telnet connections.
- Now login as \e[4msysop\e[24m and cd spider/src. You can test that spider is
- accepting telnet logins by issuing the following command ....
+ As standard, the listener will listen on all interfaces
+ simultaneously. If you require more control than this, you can
+ specify each interface individually:-
- You should get a login prompt and on issuing a callsign, you will be
- given access to the cluster. Note, you will not get a password login.
- There seems no good reason for a password prompt to be given so it is
- not asked for.
+ This will only be successful if the IP addresses on each interface are
+ static. If you are using some kind of dynamic IP addressing then the
+ 'default' method is the only one that will work.
+ One important difference with the internal listener is that no echoing
+ is done by the cluster program. Users will need to set 'local-echo' on
+ in their telnet clients if it isn't set automatically (as per the
+ standards). Needless to say this will probably only apply to Windows
+ users.
- You should now get the login prompt and be able to login as before.
+ >From version 1.47 there is a new (more efficient) way of doing this
+ (see previous section) but, if you prefer, the method of doing it
+ described here will continue to work just fine.
- >From version 1.47 you can choose to allow the perl cluster.pl program
- to allow connections directly (i.e. not via the /spider/src/client
- interface program). If you are using Windows then this is the only
- method available of allowing incoming telnet connections.
+ spdlogin 8000/tcp # spider anonymous login port
- @listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
- );
+
+ You should get a login prompt and on issuing a callsign, you will be
+ given access to the cluster. Note, you will not get a password login.
+ There seems no good reason for a password prompt to be given so it is
+ not asked for.
- One important difference with the internal listener is that no echoing
- is done by the cluster program. Users will need to set 'local-echo' on
- in their telnet clients if it isn't set automatically (as per the
- standards). Needless to say this will probably only apply to Windows
- users.
+
+ You should now get the login prompt and be able to login as before.
+
In order to enable access to an AGW Engine you need to copy
\e[4m/spider/perl/AGWConnect.pm\e[24m to \e[4m/spider/local\e[24m and edit it. Specifically
you must:-
In order to enable access to an AGW Engine you need to copy
\e[4m/spider/perl/AGWConnect.pm\e[24m to \e[4m/spider/local\e[24m and edit it. Specifically
you must:-
o set $enable to 1.
o set $login and $passwd to the values set up in your AGW
installation. If you haven't set any there, then you should not
touch these values.
o set $enable to 1.
o set $login and $passwd to the values set up in your AGW
installation. If you haven't set any there, then you should not
touch these values.
o You can connect to a remote AGW engine (ie on some other machine)
by changing $addr and $port appropriately.
o You can connect to a remote AGW engine (ie on some other machine)
by changing $addr and $port appropriately.
- timeout 15
- connect telnet dirkl.tobit.co.uk
- # tell GB7DJK-1 that it is connected to GB7DJK
- # you can leave this out if you call this script 'gb7djk'
- client gb7djk telnet
+ timeout 15
+ connect telnet dirkl.tobit.co.uk
+ # tell GB7DJK-1 that it is connected to GB7DJK
+ # 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
Both these examples assume that everything is set up properly at the
other end. You will find other examples in the /spider/examples
This means if a node is unreachable, it will continue sending logins
and logouts to users even though it is not actually connecting. To
avoid this use the following line ...
This means if a node is unreachable, it will continue sending logins
and logouts to users even though it is not actually connecting. To
avoid this use the following line ...
This is not only a way to start the cluster automatically, it also
works as a watchdog, checking the sanity of DXSpider and respawning it
should it crash for any reason. Before doing the following, shutdown
This is not only a way to start the cluster automatically, it also
works as a watchdog, checking the sanity of DXSpider and respawning it
should it crash for any reason. Before doing the following, shutdown
As root type the command \e[4mtelinit\e[24m \e[4mq\e[24m. DXSpider should start up
immediately. You will see the output on tty7 and if you login as
\e[4msysop\e[24m you should find everything running nicely.
As root type the command \e[4mtelinit\e[24m \e[4mq\e[24m. DXSpider should start up
immediately. You will see the output on tty7 and if you login as
\e[4msysop\e[24m you should find everything running nicely.
any platform that has reasonably complete support for Perl. Is there
someone out there with both an enquiring mind and (say) a Macintosh,
for instance?
any platform that has reasonably complete support for Perl. Is there
someone out there with both an enquiring mind and (say) a Macintosh,
for instance?
Please bear in mind, though, that my instructions relate solely to how
to get this going under a Microsoft Windows environment, and I have
zero intention of trying to make them say otherwise.
Please bear in mind, though, that my instructions relate solely to how
to get this going under a Microsoft Windows environment, and I have
zero intention of trying to make them say otherwise.
noticable difficulty.) You can get this from:
http://www.activestate.com/Products/ActivePerl/Download.html
noticable difficulty.) You can get this from:
http://www.activestate.com/Products/ActivePerl/Download.html
The link takes you to an initial page of System Requirements and
Software Prerequisites. If you do not have it already installed, you
can download and install the Windows Installer 2.0 for a Win98
The link takes you to an initial page of System Requirements and
Software Prerequisites. If you do not have it already installed, you
can download and install the Windows Installer 2.0 for a Win98
- D:\ppm>ppm install Data-Dumper.ppd
- Installing package 'Data-Dumper.ppd'
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
- Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
- Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
- Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
- Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
- D:\ppm>
+ D:\ppm>ppm install Data-Dumper.ppd
+ Installing package 'Data-Dumper.ppd'
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
+ Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
+ Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
+ Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
+ Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
+ D:\ppm>
The only difference between "CVSlatest.tgz" and the latest "official"
release version is that it is more up to date. \e[1mDo not confuse the\e[0m
\e[1m"CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -\e[0m
The only difference between "CVSlatest.tgz" and the latest "official"
release version is that it is more up to date. \e[1mDo not confuse the\e[0m
\e[1m"CVSlatest.tgz" file with "Downloading from Sourceforge with CVS" -\e[0m
o $mylocator - The Maidenhead (or QRA) locator of the station
You really also ought to update the $myqth and $myemail variables. And
o $mylocator - The Maidenhead (or QRA) locator of the station
You really also ought to update the $myqth and $myemail variables. And
somesuch), then you need to have the machine listening at least to
"127.0.0.1" ("0.0.0.0" means \e[1mall \e[22mIP addresses).
somesuch), then you need to have the machine listening at least to
"127.0.0.1" ("0.0.0.0" means \e[1mall \e[22mIP addresses).
\e[1m6.2. The AGW packet engine\e[0m
On the assumption that you'll be using the SV2AGW Packet Engine to
\e[1m6.2. The AGW packet engine\e[0m
On the assumption that you'll be using the SV2AGW Packet Engine to
If all goes according to plan, you will see no output from this
program, and after a brief wait, your DOS prompt will be returned.
If all goes according to plan, you will see no output from this
program, and after a brief wait, your DOS prompt will be returned.
On getting the \e[1mlogin: \e[22mprompt, enter your sysop callsign (the one you
put in DXVars.pm as $myalias).
On getting the \e[1mlogin: \e[22mprompt, enter your sysop callsign (the one you
put in DXVars.pm as $myalias).
I would recommend \e[1mstrongly \e[22mthat you obtain a better telnet client than
that which comes with windows (I use PuTTY).
I would recommend \e[1mstrongly \e[22mthat you obtain a better telnet client than
that which comes with windows (I use PuTTY).
- 0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')
+ 0,10,20,30,40,50 * * * * start_connect('gb7xxx') unless connected('gb7xxx')
going to connect to. This will now check every 10 minutes to see if
gb7xxx is connected, if it is then nothing will be done. If it is
not, then a connect attempt will be started.
going to connect to. This will now check every 10 minutes to see if
gb7xxx is connected, if it is then nothing will be done. If it is
not, then a connect attempt will be started.
There are probably lots of other things you could use this crontab
file for. If you want to know more about it, look at the DXSpider
website at the cron page where it is explained more fully.
There are probably lots of other things you could use this crontab
file for. If you want to know more about it, look at the DXSpider
website at the cron page where it is explained more fully.