+15Apr01=======================================================================
+1. made some mods to the sgml documentation for 1.47
11Apr01=======================================================================
1. fixed more of the "xxx disappeared from yyy" messages
2. altered the build no logic so that it always checksums the same files
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Installation (Original version by Iain Philipps, G0RDI)</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Installation (Original version by Iain Philipps, G0RDI)</TITLE>
<LINK HREF="adminmanual-2.html" REL=next>
<LINK HREF="adminmanual.html#toc1" REL=contents>
<P>
<P>
<UL>
-<LI> MD5-1.7.tar.gz</LI>
-<LI> Data-Dumper-2.10.tar.gz</LI>
-<LI> TimeDate-1.08.tar.gz</LI>
-<LI> IO-1.20.tar.gz</LI>
+<LI> Data-Dumper-2.101.tar.gz</LI>
+<LI> TimeDate-1.10.tar.gz</LI>
+<LI> IO-1.20.tar.gz (for perl 5.00403 and lower)</LI>
<LI> Net-Telnet-3.02.tar.gz</LI>
<LI> Curses-1.05.tar.gz</LI>
<LI> Time-HiRes-01.20.tar.gz
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Databases</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Databases</TITLE>
<LINK HREF="adminmanual-11.html" REL=next>
<LINK HREF="adminmanual-9.html" REL=previous>
<LINK HREF="adminmanual.html#toc10" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Information, files and useful programs</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Information, files and useful programs</TITLE>
<LINK HREF="adminmanual-12.html" REL=next>
<LINK HREF="adminmanual-10.html" REL=previous>
<LINK HREF="adminmanual.html#toc11" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : CVS</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: CVS</TITLE>
<LINK HREF="adminmanual-13.html" REL=next>
<LINK HREF="adminmanual-11.html" REL=previous>
<LINK HREF="adminmanual.html#toc12" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : The DXSpider command set</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: The DXSpider command set</TITLE>
<LINK HREF="adminmanual-12.html" REL=previous>
<LINK HREF="adminmanual.html#toc13" REL=contents>
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Quick installation guide</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Quick installation guide</TITLE>
<LINK HREF="adminmanual-3.html" REL=next>
<LINK HREF="adminmanual-1.html" REL=previous>
<LINK HREF="adminmanual.html#toc2" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Configuration</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Configuration</TITLE>
<LINK HREF="adminmanual-4.html" REL=next>
<LINK HREF="adminmanual-2.html" REL=previous>
<LINK HREF="adminmanual.html#toc3" REL=contents>
default * * * * * * - sysop /spider/src/client client %s ax25
</PRE>
</CODE></BLOCKQUOTE>
+<P>For most purposes this is not desirable. The only time you probably will need this is
+when you need to allow other cluster nodes that are using SSID's in. In this case it
+owuld probably be better to use the first example and then add a specific line for that
+node like this:
<P>
-<H2><A NAME="ss3.2">3.2 Allowing telnet connects from users</A>
+<BLOCKQUOTE><CODE>
+<PRE>
+GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+default * * * * * * - sysop /spider/src/client client %u ax25
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss3.2">3.2 Allowing telnet connects from users </A>
</H2>
+<P>
+From version 1.47 there is a new (more efficient) way of doing this (see next section) but,
+if you prefer, the method of doing it described here will continue to work just fine.
+<P>
<P>Allowing telnet connections is quite simple. Firstly you need to add a line
in /etc/services to allow connections to a port number, like this ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
-spdlogin 8000/tcp # spider anonymous login port
+spdlogin 7300/tcp # spider anonymous login port
</PRE>
</CODE></BLOCKQUOTE>
<P>Then add a line in /etc/inetd.conf like this ....
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>This needs to be added above the standard services such as ftp, telnet etc.
-Once this is done, you need to restart inetd like this ....
+<P>Once this is done, you need to restart inetd like this ....
<P>
<BLOCKQUOTE><CODE>
<PRE>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-telnet localhost 8000
+telnet localhost 7300
</PRE>
</CODE></BLOCKQUOTE>
<P>
<P>You should now get the login prompt and be able to login as before.
<P>
-<H2><A NAME="ss3.3">3.3 Setting up node connects</A>
+<H2><A NAME="ss3.3">3.3 Setting up telnet connects (from 1.47 onwards)</A>
+</H2>
+
+<P>From version 1.47 you can chose to allow the perl cluster.pl program to
+allow connections direct (i.e. not via the <CODE>/spider/src/client</CODE>
+interface program). If you are using Windows then this is the only method
+available of allowing incoming telnet connections.
+<P>
+<P>To do this you need first to remove any line that you may previously have set
+up in /etc/inetd.conf. Remember to:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+killall -HUP inetd
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>to make the change happen...
+<P>
+<P>Having done that then you need to copy the file
+<CODE>/spider/perl/Listeners.pm</CODE> to <CODE>/spider/local</CODE> and
+then edit it. You will need to uncomment the line containing "0.0.0.0"
+and select the correct port to listen on. So that it looks like this:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+@listen = (
+ ["0.0.0.0", 7300],
+);
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>As standard, the listener will listen on all interfaces simultaniously. If you require more
+control than this, you can specify each interface individually:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+@listen = (
+ ["gb7baa.dxcluster.net", 7300],
+ ["44.131.16.2", 6300],
+);
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>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 which will work.
+<P>
+<P>Restart the cluster.pl program to enable the listener.
+<P>
+<P>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.
+<P>
+<H2><A NAME="ss3.4">3.4 Setting up for AGW Engine (1.47 onwards)</A>
+</H2>
+
+<P>AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine from Linux
+as well as Windows based machines.
+<P>
+<P>In order to enable access to an AGW Engine you need to copy <CODE>/spider/perl/AGWConnect.pm</CODE>
+to <CODE>/spider/local</CODE> and edit it. Specifically you must:-
+<P>
+<UL>
+<LI> set <CODE>$enable</CODE> to 1.</LI>
+<LI> set <CODE>$login</CODE> and <CODE>$passwd</CODE> to the values set up in your AGW installation.
+If you haven't set any there, then you should not touch these values.</LI>
+<LI> You can connect to a remote AGW engine (ie on some other machine) by changing <CODE>$addr</CODE>
+and <CODE>$port</CODE> appropriately.</LI>
+<LI> Restart the cluster.pl program</LI>
+</UL>
+
+<P>
+<P>
+<H2><A NAME="ss3.5">3.5 Setting up node connects</A>
</H2>
<P>In order to allow cluster node connections, spider needs to know that the
this is all that needs to be done. If the connection is to be outgoing then
a connection script needs to be written.
<P>
-<H2><A NAME="ss3.4">3.4 Connection scripts</A>
+<P>Sometimes you make a mistake... Honest, it does happen. If you want to make a node
+back to being a normal user, regardless
+of what type it is, do:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+unset/node gb7baa
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss3.6">3.6 Connection scripts</A>
</H2>
<P>Because DXSpider operates under Linux, connections can be made using just about
<P>The connect scripts consist of lines which start with the following keywords
or symbols:-
<P>
+<DL>
+<P>
+<DT><B>#</B><DD><P>All lines starting with a <CODE>#</CODE> are ignored, as are completely
+blank lines.
+<P>
+<DT><B>timeout</B><DD><P><CODE>timeout</CODE> followed by a number is the number of seconds to wait for a
+command to complete. If there is no timeout specified in the script
+then the default is 60 seconds.
+<P>
+<DT><B>abort</B><DD><P><CODE>abort</CODE> is a regular expression containing one or more strings to look
+for to abort a connection. This is a perl regular expression and is
+executed ignoring case.
+<P>
+<DT><B>connect</B><DD><P><CODE>connect</CODE> followed by ax25, agw (for Windows users) or telnet and some type dependent
+information. In the case of a telnet connection, there can be up to
+two parameters.
+The first is the ip address or hostname of the computer you wish to
+connect to and the second is the port number you want to use (this
+can be left out if it is a normal telnet session).
+In the case of an ax25 session then this would normally be a call to
+ax25_call or netrom_call as in the example above. It is your
+responsibility to get your node and other ax25 parameters to work
+before going down this route!
+<P>
+<DT><B>'</B><DD><P><CODE>'</CODE> 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.
+<P>
+<DT><B>client</B><DD><P><CODE>client</CODE> starts the connection, put the arguments you would want here
+if you were starting the client program manually. You only need this
+if the script has a different name to the callsign you are trying to
+connect to (i.e. you have a script called other which actually
+connects to GB7DJK-1 [instead of a script called gb7djk-1]).
+</DL>
+<P>
+<P>There are many possible ways to configure the script but here are three examples,
+one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip.
+<P>
+<BLOCKQUOTE><CODE>
<PRE>
-
-# All lines starting with a # are ignored, as are completely
- blank lines.
-
-timeout timeout followed by a number is the number of seconds to wait for a
- command to complete. If there is no timeout specified in the script
- then the default is 60 seconds.
-
-abort abort is a regular expression containing one or more strings to look
- for to abort a connection. This is a perl regular expression and is
- executed ignoring case.
-
-connect connect followed by ax25 or telnet and some type dependent
- information. In the case of a telnet connection, there can be up to
- two parameters.
- The first is the ip address or hostname of the computer you wish to
- connect to and the second is the port number you want to use (this
- can be left out if it is a normal telnet session).
- In the case of an ax25 session then this would normally be a call to
- ax25_call or netrom_call as in the example above. It is your
- responsibility to get your node and other ax25 parameters to work
- before going down this route!
-
-' ' 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.
-
-client client starts the connection, put the arguments you would want here
- if you were starting the client program manually. You only need this
- if the script has a different name to the callsign you are trying to
- connect to (i.e. you have a script called other which actually
- connects to GB7DJK-1 [instead of a script called gb7djk-1]).
+timeout 60
+abort (Busy|Sorry|Fail)
+# don't forget to chmod 4775 netrom_call!
+connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+'Connect' ''
+'Connect' 'c np7'
+'Connect' 'c gb7dxm'
+# you can leave this out if you call the script 'gb7dxm'
+client gb7dxm ax25
</PRE>
+</CODE></BLOCKQUOTE>
+<P>
<P>
-<P>There are many possible ways to configure the script but here are two examples,
-one for a NETRom/AX25 connect and one for tcp/ip.
<P>
<BLOCKQUOTE><CODE>
<PRE>
timeout 60
abort (Busy|Sorry|Fail)
-# don't forget to chmod 4775 netrom_call!
-connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+# this does exactly the same as the previous example
+# the '1' is the AGW port number to connect thru for g1tlh
+connect agw 1 g1tlh
'Connect' ''
'Connect' 'c np7'
'Connect' 'c gb7dxm'
<P>Both these examples assume that everything is set up properly at the other end.
You will find other examples in the /spider/examples directory.
<P>
-<H2><A NAME="ss3.5">3.5 Starting the connection</A>
+<H2><A NAME="ss3.7">3.7 Starting the connection</A>
</H2>
<P>You start the connection, from within a sysop enabled cluster login, by typing
</CODE></BLOCKQUOTE>
<P>This will start a connection using the script called <EM>gb7djk-1</EM>. You can
follow the connection by watching the term or console from where you started
-<EM>cluster.pl</EM>. You should see something like this ...
+<EM>cluster.pl</EM>. From version 1.47 onwards, you will need to <CODE>set/debug connect</CODE> first.
+You should see something like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss3.6">3.6 Telnet echo</A>
+<H2><A NAME="ss3.8">3.8 Telnet echo</A>
</H2>
<P>Cluster links in particular suffer greatly from the presence of telnet echo.
<P>
<P>Telnet echo itself should only be a problem if the connection is being made to
the telnet port (23). This port uses special rules that include echo negotiation.
-If the connection is to a different port, such as 8000, this negotiation does
+If the connection is to a different port, such as 7300, this negotiation does
not happen and therefore no echo should be present.
<P>
<P>Sometimes it is not possible to make a direct connection to another node and this
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Automating things</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Automating things</TITLE>
<LINK HREF="adminmanual-5.html" REL=next>
<LINK HREF="adminmanual-3.html" REL=previous>
<LINK HREF="adminmanual.html#toc4" REL=contents>
# check every 10 minutes to see if gb7xxx is connected and if not
# start a connect job going
-0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
+0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
</PRE>
</CODE></BLOCKQUOTE>
<P>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Hop control</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Hop control</TITLE>
<LINK HREF="adminmanual-6.html" REL=next>
<LINK HREF="adminmanual-4.html" REL=previous>
<LINK HREF="adminmanual.html#toc5" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Filtering (Old Style upto v1.44)</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Filtering (Old Style upto v1.44)</TITLE>
<LINK HREF="adminmanual-7.html" REL=next>
<LINK HREF="adminmanual-5.html" REL=previous>
<LINK HREF="adminmanual.html#toc6" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Filtering (New Style v1.45 and later)</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Filtering (New Style v1.45 and later)</TITLE>
<LINK HREF="adminmanual-8.html" REL=next>
<LINK HREF="adminmanual-6.html" REL=previous>
<LINK HREF="adminmanual.html#toc7" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Other filters</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Other filters</TITLE>
<LINK HREF="adminmanual-9.html" REL=next>
<LINK HREF="adminmanual-7.html" REL=previous>
<LINK HREF="adminmanual.html#toc8" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual : Mail</TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual: Mail</TITLE>
<LINK HREF="adminmanual-10.html" REL=next>
<LINK HREF="adminmanual-8.html" REL=previous>
<LINK HREF="adminmanual.html#toc9" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual </TITLE>
+ <TITLE>The DXSpider Installation and Administration Manual</TITLE>
<LINK HREF="adminmanual-1.html" REL=next>
Previous
Contents
<HR>
-<H1>The DXSpider Installation and Administration Manual </H1>
+<H1>The DXSpider Installation and Administration Manual</H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.34 (Revision 1.01) April 2001
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>$Date$ $Revision$
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<UL>
<LI><A HREF="adminmanual-3.html#ss3.1">3.1 Allowing ax25 connects from users</A>
-<LI><A HREF="adminmanual-3.html#ss3.2">3.2 Allowing telnet connects from users</A>
-<LI><A HREF="adminmanual-3.html#ss3.3">3.3 Setting up node connects</A>
-<LI><A HREF="adminmanual-3.html#ss3.4">3.4 Connection scripts</A>
-<LI><A HREF="adminmanual-3.html#ss3.5">3.5 Starting the connection</A>
-<LI><A HREF="adminmanual-3.html#ss3.6">3.6 Telnet echo</A>
+<LI><A HREF="adminmanual-3.html#ss3.2">3.2 Allowing telnet connects from users </A>
+<LI><A HREF="adminmanual-3.html#ss3.3">3.3 Setting up telnet connects (from 1.47 onwards)</A>
+<LI><A HREF="adminmanual-3.html#ss3.4">3.4 Setting up for AGW Engine (1.47 onwards)</A>
+<LI><A HREF="adminmanual-3.html#ss3.5">3.5 Setting up node connects</A>
+<LI><A HREF="adminmanual-3.html#ss3.6">3.6 Connection scripts</A>
+<LI><A HREF="adminmanual-3.html#ss3.7">3.7 Starting the connection</A>
+<LI><A HREF="adminmanual-3.html#ss3.8">3.8 Telnet echo</A>
</UL>
<P>
<H2><A NAME="toc4">4.</A> <A HREF="adminmanual-4.html">Automating things</A></H2>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider FAQ : Installation </TITLE>
+ <TITLE>The DXSpider FAQ: Installation </TITLE>
<LINK HREF="spiderFAQ-2.html" REL=next>
<LINK HREF="spiderFAQ.html#toc1" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider FAQ : Administration</TITLE>
+ <TITLE>The DXSpider FAQ: Administration</TITLE>
<LINK HREF="spiderFAQ-1.html" REL=previous>
<LINK HREF="spiderFAQ.html#toc2" REL=contents>
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider FAQ </TITLE>
+ <TITLE>The DXSpider FAQ</TITLE>
<LINK HREF="spiderFAQ-1.html" REL=next>
Previous
Contents
<HR>
-<H1>The DXSpider FAQ </H1>
+<H1>The DXSpider FAQ</H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 0.5 March 2001
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>$Date$ $Revision$
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<P>
<BLOCKQUOTE><CODE>
<PRE>
-["localhost", 7300],
-["foo.dxcluster.net", 7300],
+["0.0.0.0", 7300],
</PRE>
</CODE></BLOCKQUOTE>
-<P>On my machine, I've simply uncommented the "localhost" entry by
-removing the '#' from the front of the line. I've also
-uncommented the second line, and changed the hostname to point at
-"spud.ath.cx".
+<P>On my machine, I've simply uncommented the "0.0.0.0" entry by
+removing the '#' from the front of the line.
<P>If you don't have a static hostname for your machine, and you
intend to allow folk to connect to your machine across the
internet, then I'd suggest you pay a visit to www.dyndns.org and
may not be connected to anything particularly useful at any given
moment. Contact me by Email if you want me to set up a connection
for you.
-<P><I>Last updated: 05-Mar-01</I>
+<P><I>Last updated: 15-Apr-01</I>
<P>
<HR>
Next
<HR>
<H1>The Installation Guide for DXSpider under Microsoft Windows</H1>
-<H2>Iain Philipps, G0RDI (g0rdi@77hz.com)</H2>Version 1.1 28 March 2001
+<H2>Iain Philipps, G0RDI (g0rdi@77hz.com)</H2>$Date$ $Revision$
<P><HR>
<EM>DX Spider under Microsoft Windows ™</EM>
<HR>
use vars qw(@listen);
@listen = (
-# ["localhost", 7300],
-# ["foo.dxcluster.net", 7300],
+# ["0.0.0.0", 7300],
);
1;
if (ref $pkg) {
$call = $pkg->{call} unless $call;
return undef unless $call;
- confess "changing $pkg->{call} to $call" if exists $pkg->{call} && $call ne $pkg->{call};
+ dbg('connll', "changing $pkg->{call} to $call") if exists $pkg->{call} && $call ne $pkg->{call};
$pkg->{call} = $call;
$ref = $conns{$call} = $pkg;
dbg('connll', "Connection $pkg->{cnum} $call stored");
The DXSpider Installation and Administration Manual
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 1.34 (Revision 1.01) April 2001
+ $Date$ $Revision$
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
3.1 Allowing ax25 connects from users
3.2 Allowing telnet connects from users
- 3.3 Setting up node connects
- 3.4 Connection scripts
- 3.5 Starting the connection
- 3.6 Telnet echo
+ 3.3 Setting up telnet connects (from 1.47 onwards)
+ 3.4 Setting up for AGW Engine (1.47 onwards)
+ 3.5 Setting up node connects
+ 3.6 Connection scripts
+ 3.7 Starting the connection
+ 3.8 Telnet echo
4. Automating things
- +\bo MD5-1.7.tar.gz
+ +\bo Data-Dumper-2.101.tar.gz
- +\bo Data-Dumper-2.10.tar.gz
+ +\bo TimeDate-1.10.tar.gz
- +\bo TimeDate-1.08.tar.gz
-
- +\bo IO-1.20.tar.gz
+ +\bo IO-1.20.tar.gz (for perl 5.00403 and lower)
+\bo Net-Telnet-3.02.tar.gz
+ For most purposes this is not desirable. The only time you probably
+ will need this is when you need to allow other cluster nodes that are
+ using SSID's in. In this case it owuld probably be better to use the
+ first example and then add a specific line for that node like this:
+
+
+
+ GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+
+
+
3\b3.\b.2\b2.\b. A\bAl\bll\blo\bow\bwi\bin\bng\bg t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs f\bfr\bro\bom\bm u\bus\bse\ber\brs\bs
+
+ From version 1.47 there is a new (more efficient) way of doing this
+ (see next section) but, if you prefer, the method of doing it
+ described here will continue to work just fine.
+
+
Allowing telnet connections is quite simple. Firstly you need to add
a line in /etc/services to allow connections to a port number, like
this ....
- spdlogin 8000/tcp # spider anonymous login port
+ spdlogin 7300/tcp # spider anonymous login port
-
-
- This needs to be added above the standard services such as ftp, telnet
- etc. Once this is done, you need to restart inetd like this ....
+ Once this is done, you need to restart inetd like this ....
- ./client login telnet
+ ./client login telnet
- telnet localhost 8000
+ telnet localhost 7300
You should now get the login prompt and be able to login as before.
- 3\b3.\b.3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
+ 3\b3.\b.3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp t\bte\bel\bln\bne\bet\bt c\bco\bon\bnn\bne\bec\bct\bts\bs (\b(f\bfr\bro\bom\bm 1\b1.\b.4\b47\b7 o\bon\bnw\bwa\bar\brd\bds\bs)\b)
+
+ From version 1.47 you can chose to allow the perl cluster.pl program
+ to allow connections direct (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.
+
+
+ To do this you need first to remove any line that you may previously
+ have set up in /etc/inetd.conf. Remember to:-
+
+
+
+ killall -HUP inetd
+
+
+
+
+
+ to make the change happen...
+
+
+ Having done that then you need to copy the file
+ /spider/perl/Listeners.pm to /spider/local and then edit it. You will
+ need to uncomment the line containing "0.0.0.0" and select the correct
+ port to listen on. So that it looks like this:-
+ @listen = (
+ ["0.0.0.0", 7300],
+ );
+
+
+
+
+
+ As standard, the listener will listen on all interfaces
+ simultaniously. If you require more control than this, you can specify
+ each interface individually:-
+
+
+
+ @listen = (
+ ["gb7baa.dxcluster.net", 7300],
+ ["44.131.16.2", 6300],
+ );
+
+
+
+
+
+ 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 which will work.
+
+
+ Restart the cluster.pl program to enable the listener.
+
+
+ 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.
+
+
+ 3\b3.\b.4\b4.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp f\bfo\bor\br A\bAG\bGW\bW E\bEn\bng\bgi\bin\bne\be (\b(1\b1.\b.4\b47\b7 o\bon\bnw\bwa\bar\brd\bds\bs)\b)
+
+ AGW Engine is a Windows based ax25 stack. You can connect to an AGW
+ engine from Linux as well as Windows based machines.
+
+
+ In order to enable access to an AGW Engine you need to copy
+ /spider/perl/AGWConnect.pm to /spider/local and edit it. Specifically
+ you must:-
+
+
+ +\bo set $enable to 1.
+
+ +\bo 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.
+
+ +\bo You can connect to a remote AGW engine (ie on some other machine)
+ by changing $addr and $port appropriately.
+
+ +\bo Restart the cluster.pl program
+
+
+
+
+
+
+
+ 3\b3.\b.5\b5.\b. S\bSe\bet\btt\bti\bin\bng\bg u\bup\bp n\bno\bod\bde\be c\bco\bon\bnn\bne\bec\bct\bts\bs
In order to allow cluster node connections, spider needs to know that
the connecting callsign is a cluster node. This is the case whether
+
The case does not matter as long as you have a version of DXSpider
later than 1.33. Earlier versions required the callsign to be in
upper case.
./client gb7baa
PC38^GB7MBC^~
-
-
-
If the callsign you just set up as a cluster node is for an incoming
connect, this is all that needs to be done. If the connection is to
be outgoing then a connection script needs to be written.
- 3\b3.\b.4\b4.\b. C\bCo\bon\bnn\bne\bec\bct\bti\bio\bon\bn s\bsc\bcr\bri\bip\bpt\bts\bs
-
- Because DXSpider operates under Linux, connections can be made using
- just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
- possible examples. Connect scripts live in the /spider/connect
- directory and are simple ascii files. Writing a script for
- connections is therefore relatively simple.
-
+ Sometimes you make a mistake... Honest, it does happen. If you want
+ to make a node back to being a normal user, regardless of what type it
+ is, do:
- The connect scripts consist of lines which start with the following
- keywords or symbols:-
+ unset/node gb7baa
+ 3\b3.\b.6\b6.\b. C\bCo\bon\bnn\bne\bec\bct\bti\bio\bon\bn s\bsc\bcr\bri\bip\bpt\bts\bs
+ Because DXSpider operates under Linux, connections can be made using
+ just about any protocol; AX25, NETRom, tcp/ip, ROSE etc are all
+ possible examples. Connect scripts live in the /spider/connect
+ directory and are simple ascii files. Writing a script for
+ connections is therefore relatively simple.
+ The connect scripts consist of lines which start with the following
+ keywords or symbols:-
+ #\b# All lines starting with a # are ignored, as are completely blank
+ lines.
+ t\bti\bim\bme\beo\bou\but\bt
+ timeout followed by a number is the number of seconds to wait
+ for a command to complete. If there is no timeout specified in
+ the script then the default is 60 seconds.
+ a\bab\bbo\bor\brt\bt
+ abort is a regular expression containing one or more strings to
+ look for to abort a connection. This is a perl regular
+ expression and is executed ignoring case.
+ c\bco\bon\bnn\bne\bec\bct\bt
+ connect followed by ax25, agw (for Windows users) or telnet and
+ some type dependent information. In the case of a telnet
+ connection, there can be up to two parameters. The first is the
+ ip address or hostname of the computer you wish to connect to
+ and the second is the port number you want to use (this can be
+ left out if it is a normal telnet session). In the case of an
+ ax25 session then this would normally be a call to ax25_call or
+ netrom_call as in the example above. It is your responsibility
+ to get your node and other ax25 parameters to work before going
+ down this route!
+ '\b' 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.
+ c\bcl\bli\bie\ben\bnt\bt
+ client starts the connection, put the arguments you would want
+ here if you were starting the client program manually. You only
+ need this if the script has a different name to the callsign you
+ are trying to connect to (i.e. you have a script called other
+ which actually connects to GB7DJK-1 [instead of a script called
+ gb7djk-1]).
- # All lines starting with a # are ignored, as are completely
- blank lines.
- timeout timeout followed by a number is the number of seconds to wait for a
- command to complete. If there is no timeout specified in the script
- then the default is 60 seconds.
+ There are many possible ways to configure the script but here are
+ three examples, one for a NETRom/AX25 connect, one for AGW engines and
+ one for tcp/ip.
- abort abort is a regular expression containing one or more strings to look
- for to abort a connection. This is a perl regular expression and is
- executed ignoring case.
- connect connect followed by ax25 or telnet and some type dependent
- information. In the case of a telnet connection, there can be up to
- two parameters.
- The first is the ip address or hostname of the computer you wish to
- connect to and the second is the port number you want to use (this
- can be left out if it is a normal telnet session).
- In the case of an ax25 session then this would normally be a call to
- ax25_call or netrom_call as in the example above. It is your
- responsibility to get your node and other ax25 parameters to work
- before going down this route!
- ' 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.
+ timeout 60
+ abort (Busy|Sorry|Fail)
+ # don't forget to chmod 4775 netrom_call!
+ connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+ # you can leave this out if you call the script 'gb7dxm'
+ client gb7dxm ax25
- client client starts the connection, put the arguments you would want here
- if you were starting the client program manually. You only need this
- if the script has a different name to the callsign you are trying to
- connect to (i.e. you have a script called other which actually
- connects to GB7DJK-1 [instead of a script called gb7djk-1]).
- There are many possible ways to configure the script but here are two
- examples, one for a NETRom/AX25 connect and one for tcp/ip.
timeout 60
abort (Busy|Sorry|Fail)
- # don't forget to chmod 4775 netrom_call!
- connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
+ # this does exactly the same as the previous example
+ # the '1' is the AGW port number to connect thru for g1tlh
+ connect agw 1 g1tlh
# you can leave this out if you call the script 'gb7dxm'
client gb7dxm ax25
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.
- 3\b3.\b.5\b5.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bco\bon\bnn\bne\bec\bct\bti\bio\bon\bn
+
+
+ 3\b3.\b.7\b7.\b. S\bSt\bta\bar\brt\bti\bin\bng\bg t\bth\bhe\be c\bco\bon\bnn\bne\bec\bct\bti\bio\bon\bn
You start the connection, from within a sysop enabled cluster login,
by typing in the word _\bc_\bo_\bn_\bn_\be_\bc_\bt followed by a script name like this ....
This will start a connection using the script called _\bg_\bb_\b7_\bd_\bj_\bk_\b-_\b1. You
can follow the connection by watching the term or console from where
- you started _\bc_\bl_\bu_\bs_\bt_\be_\br_\b._\bp_\bl. You should see something like this ...
+ you started _\bc_\bl_\bu_\bs_\bt_\be_\br_\b._\bp_\bl. From version 1.47 onwards, you will need to
+ set/debug connect first. You should see something like this ...
avoid this use the following line ...
+
+
+
+
In a script, this might look like ...
- 3\b3.\b.6\b6.\b. T\bTe\bel\bln\bne\bet\bt e\bec\bch\bho\bo
+ 3\b3.\b.8\b8.\b. T\bTe\bel\bln\bne\bet\bt e\bec\bch\bho\bo
Cluster links in particular suffer greatly from the presence of telnet
echo. This is caused by the telnet negotiation itself and can create
Telnet echo itself should only be a problem if the connection is being
made to the telnet port (23). This port uses special rules that
include echo negotiation. If the connection is to a different port,
- such as 8000, this negotiation does not happen and therefore no echo
+ such as 7300, this negotiation does not happen and therefore no echo
should be present.
# check every 10 minutes to see if gb7xxx is connected and if not
# start a connect job going
- 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
+ 0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
The DXSpider FAQ
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 0.5 March 2001
+ $Date$ $Revision$
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
The Installation Guide for DXSpider under Microsoft Windows
Iain Philipps, G0RDI (g0rdi@77hz.com)
- Version 1.1 28 March 2001
+ $Date$ $Revision$
DX Spider under Microsoft Windows (TM)
______________________________________________________________________
- ["localhost", 7300],
- ["foo.dxcluster.net", 7300],
+ ["0.0.0.0", 7300],
- On my machine, I've simply uncommented the "localhost" entry by
- removing the '#' from the front of the line. I've also uncommented the
- second line, and changed the hostname to point at "spud.ath.cx".
+ On my machine, I've simply uncommented the "0.0.0.0" entry by removing
+ the '#' from the front of the line.
If you don't have a static hostname for your machine, and you intend
to allow folk to connect to your machine across the internet, then I'd
connected to anything particularly useful at any given moment. Contact
me by Email if you want me to set up a connection for you.
- Last updated: 05-Mar-01
+ Last updated: 15-Apr-01
+
+
projects / spider.git / commitdiff