<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Configuration</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.49: Setting up the AX25 Utilities</TITLE>
<LINK HREF="installation-4.html" REL=next>
<LINK HREF="installation-2.html" REL=previous>
<LINK HREF="installation.html#toc3" REL=contents>
<A HREF="installation-2.html">Previous</A>
<A HREF="installation.html#toc3">Contents</A>
<HR>
-<H2><A NAME="s3">3. Configuration</A></H2>
+<H2><A NAME="s3">3. Setting up the AX25 Utilities</A></H2>
-<H2><A NAME="ss3.1">3.1 Allowing ax25 connects from users</A>
+<P>The aim of this section is not to fully cover the installation
+and configuration of all the possible ax25 modules. I will
+attempt to cover a simple installation and configure 2 serial
+ports as if they had TNC's on them. I will also show what
+additional configuration the DXSpider program requires.
+<P>
+<P>Please bear in mind that I am basing this section on a RedHat
+7.1 distribution, if you are using SuSe or any other distibution
+then your mileage may vary. I will be happy to make any changes
+and additions if you email me any errors or distribution specific
+requirements.
+<P>
+<P>You would probably benefit from reading the
+<A HREF="http://www.fokus.gmd.de/linux/HOWTO/html_single/AX25-HOWTO.html#AEN151">AX25-HOWTO</A> which is much more
+comprehensive and an interesting configuration program is also available
+called
+<A HREF="http://1409.org/projects/index.html">ax25-config</A> which
+may help you to configure things.
+<P>
+<P>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 necessarily
+the best or for that matter, the right way!
+<P>
+<H2><A NAME="ss3.1">3.1 Getting Started</A>
</H2>
-<P>As stated previously, the aim of this document is not to tell you how to
-configure Linux or the ax25 utilities. However, you do need to add a line
-in your ax25d.conf to allow connections to DXSpider for your users. For
-each interface that you wish to allow connections on, use the following format ...
+<P>There are 2 things you need to do initially. You need to get the
+3 files required for the ax25 installation and you need to make
+some changes to the kernel configuration.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-default * * * * * * - sysop /spider/src/client client %u ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>or, if you wish your users to be able to use SSID's on their callsigns ..
+<P>The first thing is to get the versions of the ax25 utils that match
+your kernel. You may also wish to get a node package of some kind.
+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
+<A HREF="ftp://ftp.funet.fi/pub/ham/packet/linux/awznode/">AWZNode</A> by IZ5AWZ.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-default * * * * * * - sysop /spider/src/client client %s ax25
-</PRE>
-</CODE></BLOCKQUOTE>
+<P>For 2.4 kernels you need these files...
<P>
-<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 would probably be better to use the first example and
-then add a specific line for that node like this:
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
-default * * * * * * - sysop /spider/src/client client %u ax25
-</PRE>
-</CODE></BLOCKQUOTE>
+<UL>
+<LI>
+<A HREF="ftp://ftp.rpmfind.net/linux/redhat/7.1/en/powertools/i386/RedHat/RPMS/libax25-0.0.7-7.i386.rpm">libax25-0.0.7-7.i386.rpm</A></LI>
+<LI>
+<A HREF="ftp://ftp.rpmfind.net/linux/redhat/7.1/en/powertools/i386/RedHat/RPMS/ax25-tools-0.0.6-13.i386.rpm">ax25-tools-0.0.6-13.i386.rpm</A></LI>
+<LI>
+<A HREF="ftp://ftp.rpmfind.net/linux/redhat/7.1/en/powertools/i386/RedHat/RPMS/ax25-apps-0.0.4-9.i386.rpm">ax25-apps-0.0.4-9.i386.rpm</A></LI>
+</UL>
<P>
-<H2><A NAME="ss3.2">3.2 Allowing telnet connects from users </A>
+<H2><A NAME="ss3.2">3.2 The kernel</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>First you need to add Amateur Radio Support to your kernel. This is
+a main menu item and should be easily found. Within this header you
+will find lots of options. For our purposes you need to enable
+Amateur Radio AX.25 Level 2 Protocol, NET/ROM and the Serial Port
+KISS Driver. For the purposes of this document I will work under the
+assumption that you include them in the kernel fully, ie not as modules.
+If you need to look at compiling your kernel for ax25 more fully, I would
+refer to the excellent
+<A HREF="http://www.fokus.gmd.de/linux/HOWTO/html_single/AX25-HOWTO.html#AEN151">AX25-HOWTO</A><P>
+<P>I should say at this stage that NET/ROM is not mandatory. If you do not use it
+simply ignore any instruction concerning it.
+<P>
+<P>Now recompile your kernel in the normal way and reboot your system.
+<P>
+<H2><A NAME="ss3.3">3.3 Installing the RPM's</A>
+</H2>
+
+<P>Now install the RPM's you downloaded, libax25 first, then ax25-tools,
+then ax25-apps.
<P>
<BLOCKQUOTE><CODE>
<PRE>
-spdlogin 8000/tcp # spider anonymous login port
+rpm -ivh libax25-0.0.7-7.i386.rpm
+rpm -ivh ax25-tool-0.0.6-13.i386.rpm
+rpm -ivh ax25-apps-0.0.4-9.i386.rpm
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>Then add a line in /etc/inetd.conf like this ....
+<H2><A NAME="ss3.4">3.4 Configuration</A>
+</H2>
+
+<P>You will find the configuration files in /etc/ax25. These consist of
+several files ...
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
-</PRE>
-</CODE></BLOCKQUOTE>
+<UL>
+<LI>axports</LI>
+<LI>nrports</LI>
+<LI>nrbroadcast</LI>
+<LI>ax25d.conf</LI>
+<LI>node.conf</LI>
+</UL>
<P>
-<P>Once this is done, you need to restart inetd like this ....
+<P>These are the main files. You will find other files but they do not
+have any use unless you are wanting to use that particular protocol,
+Rose or axip for example.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-killall -HUP inetd
-</PRE>
-</CODE></BLOCKQUOTE>
+<P>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.
<P>
-<P>Now login as <EM>sysop</EM> and cd spider/src. You can test that spider
-is accepting telnet logins by issuing the following command ....
+<H2><A NAME="ss3.5">3.5 axports</A>
+</H2>
+
+<P>This file sets up the ax25 ports you want to use. An example is below
+for a standard TNC2 ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client login telnet
+#portname callsign baudrate paclen window description
+ 2m gb7mbc-2 19200 256 2 2m port on 144.900MHz
+ 4m gb7mbc-4 19200 256 2 4m port on 70.325MHz
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>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.
+<P>Note that the portnames have to be unique.
<P>
-<P>Assuming all is well, then try a telnet from your linux console ....
+<P>The file headings are as follows ...
<P>
-<BLOCKQUOTE><CODE>
<PRE>
-telnet localhost 8000
+portname - The name you will refer to the port by
+callsign - The ax25 callsign you want to assign to the port
+baudrate - The speed you communicate between TNC and computer
+paclen - The maximum packet length for ax25 connections
+window - The ax25 window parameter. This is like 'maxframe'
+description - A textual description of the port
</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 telnet connects (from 1.47 onwards)</A>
+<H2><A NAME="ss3.6">3.6 nrports</A>
</H2>
-<P>From version 1.47 you can choose to allow the perl cluster.pl program to
-allow connections directly (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>This file sets up the netrom ports you want to use. An example is below
+and includes a port for both cluster and node. You will see why we need
+2 ports later ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-killall -HUP inetd
+#portname callsign alias paclen description
+ netrom gb7mbc-8 BARE 236 Node Netrom Port
+ netrom2 gb7mbc-9 MBCDX 236 Cluster Netrom Port
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>to make the change happen...
+<P>Note that the portnames have to be unique.
<P>
-<P>Having done that, you need to copy the file
-<EM>/spider/perl/Listeners.pm</EM> to <EM>/spider/local</EM> 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>The file headings are as follows ...
<P>
-<BLOCKQUOTE><CODE>
<PRE>
-@listen = (
- ["0.0.0.0", 8000],
-);
+portname - The name you will refer to the port by
+callsign - This is the callsign that NET/ROM traffic from this
+ port will use
+alias - The NET/ROM alias this port will be assigned
+paclen - The maximum size of NET/ROM frames transmitted
+description - A textual description of the port
</PRE>
-</CODE></BLOCKQUOTE>
<P>
-<P>As standard, the listener will listen on all interfaces simultaneously.
-If you require more control than this, you can specify each interface
-individually:-
+<H2><A NAME="ss3.7">3.7 nrbroadcast</A>
+</H2>
+
+<P>This file sets up the netrom broadcast qualities. An example is below ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-@listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
-);
+#axport min_obs def_qual worst_qual verbose
+ 4m 5 10 100 1
</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 that 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
-<EM>/spider/perl/AGWConnect.pm</EM> to <EM>/spider/local</EM> 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>The file headings are as follows ...
<P>
+<PRE>
+axport - The port name in axports that you wish to broadcast
+ NET/ROM on.
+min_obs - The minimum obsolescence value for the port
+def_qual - The default quality for the port
+worst_qual - The worst quality for the port. Any routes under
+ this quality will be ignored
+verbose - This flag determines whether you will only broadcast
+ your own node (0) or all known nodes (1)
+</PRE>
<P>
-<H2><A NAME="ss3.5">3.5 Setting up node connects</A>
+<H2><A NAME="ss3.8">3.8 ax25d.conf</A>
</H2>
-<P>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 connect
-is incoming or outgoing. In spider this is a simple task and can be done in
-runtime.
-<P>
-<P>Later versions of Spider can distinguish different software and treat them
-differently. For example, the WCY beacon cannot be handles by AK1A type
-nodes as AK1A does not know what to do with PC73. There are 4 different
-types of node at present and although they may not have any major
-differences at the moment, it allows for compatibility. The 4 types are ...
+<P>This file controls any incoming ax25 and NET/ROM connections and steers
+them to the relevant program. There are lots of configuration options
+you can set here, however they are well covered in the AX25-HOWTO. For
+our purposes I will show a typical set of parameters. An example is
+below ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-set/node (AK1A type)
-set/spider
-set/dxnet
-set/clx
+[gb7mbc-0 via 2m]
+parameters 2 1 6 900 * 15 0
+NOCALL * * * * * * L
+default * * * * * * - sysop /spider/src/client client %u ax25
+
+[gb7mbc-1 via 2m]
+parameters 2 1 6 900 * 15 0
+NOCALL * * * * * * L
+default * * * * * * 0 root /usr/sbin/node node
+
+[gb7mbc-0 via 4m]
+parameters 2 1 6 900 * 15 0
+NOCALL * * * * * * L
+default * * * * * * - sysop /spider/src/client client %u ax25
+
+[gb7mbc-1 via 4m]
+parameters 2 1 6 900 * 15 0
+NOCALL * * * * * * L
+default * * * * * * 0 root /usr/sbin/node node
+
+<netrom2>
+parameters 1 10 * * * 3 *
+NOCALL * * * * * * L
+default * * * * * * - sysop /spider/src/client client %u ax25
+
+<netrom>
+parameters 1 10 * * * 3 *
+NOCALL * * * * * * L
+default * * * * * * 0 root /usr/sbin/node node
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>For now, we will assume that the cluster we are going to connect to is an
-AK1A type node.
+<P>There are a few things to take note of here. Firstly, all ax25
+sections are wrapped in [ ] and all NET/ROM sections are wrapped in
+< >. Secondly you should be able to see that anyone who forgets to
+set their callsign in a TNC and tries to connect with the standard
+NOCALL set into their TNC will not connect, the 'L' means 'lockout'.
+Lastly and importantly, notice the order of the sections. They are
+all done in interface order.
<P>
-<P>Start up the cluster as you did before and login as the sysop with client.
-The cluster node I am wanting to make a connection to is GB7BAA but you would
-obviously use whatever callsign you required. At the prompt type ...
+<P>You should be able to see that the normal line for access to the
+cluster is like this ..
<P>
<BLOCKQUOTE><CODE>
<PRE>
-set/node gb7baa
+default * * * * * * - sysop /spider/src/client client %u ax25
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>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.
-<P>
-<P>That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop, cd to spider/src and issue the command ...
+<P>however, if you wish your users to be able to use SSID's on their callsigns ..
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client gb7baa (using the callsign you set as a node)
+default * * * * * * - sysop /spider/src/client client %s ax25
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>You should get an initialisation string from DXSpider like this ...
+<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 would probably be better to use the first example and
+then add a specific line for that node like this:
<P>
<BLOCKQUOTE><CODE>
<PRE>
-./client gb7baa
-PC38^GB7MBC^~
+GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+default * * * * * * - sysop /spider/src/client client %u ax25
</PRE>
</CODE></BLOCKQUOTE>
-<P>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.
<P>
-<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:
+<H2><A NAME="ss3.9">3.9 node.conf</A>
+</H2>
+
+<P>For those of you that wish to run the node, you need to set up the
+node.conf file. There are a couple of additional files, node.perms is
+very similar to the way ftp permissions are set up in NOS systems and
+node.motd is the message anyone logging into the node will get.
+The node.conf file sets all the parameters of the node as you would
+expect. An example is below ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-unset/node gb7baa
+# /etc/ax25/node.conf - LinuxNode configuration file
+#
+# see node.conf(5)
+
+# Idle timeout (seconds).
+#
+IdleTimeout 1800
+
+# Timeout when gatewaying (seconds).
+#
+ConnTimeout 40000
+
+# Visible hostname. Will be shown at telnet login.
+#
+HostName gb7mbc.ampr.org
+
+# ReConnect flag.
+#
+ReConnect off
+
+# "Local" network.
+#
+#LocalNet 44.139.8.48/32
+
+# Command aliases. See node.conf(5) for the meaning of the uppercase
+# letters in the name of the alias.
+#
+##Alias CAllbook 'telnet %{2:44.17.0.53} 1235 %1 s'
+#Alias CONVers 'telnet %{2:oh2ti} 3600 "/n %u %{1:139}\n/w *"'
+#Alias CLuster 'c hkiclh'
+Alias CONV "telnet lurpac 3600"
+Alias BBS "c 70cm gb7crv"
+Alias DXC "telnet localhost 9000"
+Alias MUD "telnet homer 4000"
+##Alias TEMP "finger temp@mary.g6phf"
+##Alias TNOS "c ip1 gb7mbc-5"
+##Alias TUtor "telnet gb7mbc 3599"
+
+# Hidden ports.
+#
+#HiddenPorts 2
+
+# External commands. See node.conf(5) for the meaning of the uppercase
+# letters in the name of the extcmd.
+#
+# Flags: 1 Run command through pipe
+# 2 Reconnected flag
+#
+#ExtCmd TPM 3 nobody /usr/bin/finger finger tpm
+#ExtCmd ECho 1 nobody /bin/echo echo \%U \%u \%S \%s \%P \%p \%R \%r \%T \%t \%\% \%0 \%{1:foobar} \%{2} \%3 \%4 \%5
+
+# Node ID.
+#
+NodeId "\nBARE:GB7MBC-1"
+#NodeId \033[01;31m***\033[0m
+
+# Netrom port name. This port is used for outgoing netrom connects.
+#
+NrPort netrom
+
+# Logging level
+#
+LogLevel 3
+
+# The escape character (CTRL-T)
+#
+EscapeChar ^T
+
+# Resolve ip numbers to addresses?
+#
+ResolveAddrs off
+
+# Node prompt.
+#
+#NodePrompt "\n"
+#NodePrompt "%s@%h \%i> "
+NodePrompt "\nBARE:GB7MBC-1 \%i > "
+#NodePrompt "\a\033[36m%U\033[0m de \033[01;32m#LNODE\033[0m:\033[01;33mOH2BNS-10\033[0m> "
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss3.6">3.6 Connection scripts</A>
+<P>This should be fairly obvious I hope.
+<P>
+<H2><A NAME="ss3.10">3.10 Getting it all running</A>
</H2>
-<P>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.
-<P>
-<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>
-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>Ok, now we have all the relevant files configured, the next step is to get
+it all running.
<P>
+<P>The first thing to do is attach the TNC's. Your TNC's should be in KISS mode
+and connected to the serial ports involved.
<P>
+<P>You now use the 'kissattach' command to connect the TNC's to the system like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-timeout 60
-abort (Busy|Sorry|Fail)
-# 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'
-# you can leave this out if you call the script 'gb7dxm'
-client gb7dxm ax25
+kissattach /dev/ttyS0 2m 44.131.96.199
+kissattach /dev/ttyS1 4m 44.131.96.199
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>
+<P>Assuming that 44.131.96.199 is your IP address. The devices ttyS0 and ttyS1 are com1 and
+com2 respectively. Now we can set some parameters ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-timeout 15
-connect telnet dirkl.tobit.co.uk
-'login' 'gb7djk'
-'word' 'gb7djk'
-# tell GB7DJK-1 that it is connected to GB7DJK
-# you can leave this out if you call this script 'gb7djk'
-client gb7djk telnet
+kissparms -p 2m -t 150 -l 150 -s 50 -r 50
+kissparms -p 4m -t 150 -l 150 -s 50 -r 50
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<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>The command 'man kissparms' will give you the explanation of the switches.
<P>
-<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
-in the word <EM>connect</EM> followed by a script name like this ....
+<P>Now we need to attach the NET/ROM ports in the same way ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
-connection to GB7DJK-1 started
-G0VGS de GB7MBC 13-Dec-1998 2043Z >
+nrattach netrom
+nrattach netrom2
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<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>. From version 1.47 onwards, you will need to <CODE>set/debug connect</CODE> first.
-You should see something like this ...
+<P>All of the above can be put in a file and called from /etc/rc.d/rc.local. Put all
+the above commands in a file called rc.ax25 and put a line in rc.local to call it.
+<P>
+<P>Now you can start the daemons that set everything in motion ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-<- D G1TLH connect gb7djk-1
--> D G1TLH connection to GB7DJK-1 started
--> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
-timeout set to 15
-CONNECT sort: telnet command: dirkl.tobit.co.uk
-CHAT "login" -> "gb7djk"
-received "
-Red Hat Linux release 5.1 (Manhattan)
-Kernel 2.0.35 on an i586
-"
-received "login: "
-sent "gb7djk"
-CHAT "word" -> "gb7djk"
-received "gb7djk"
-received "Password: "
-sent "gb7djk"
-Connected to GB7DJK-1, starting normal protocol
-<- O GB7DJK-1 telnet
--> B GB7DJK-1 0
-GB7DJK-1 channel func state 0 -> init
-<- D GB7DJK-1
-<- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
-<- D GB7DJK-1 PC38^GB7DJK-1^~
-<- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
-0 00:00^5447^~
- etc
+ax25d
+netromd -i
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>With later versions of Spider there is a set/login command for users. This
-tells them when a user or node logs in or out. If you do not add a line to
-your scripts after the final line (or before the client line which should always
-be last if needed) then the login/logout information will be sent to users
-<I>before</I> the login actually completes. 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 ...
+<P>All should now be running. All that remains is to get the node working for telnet
+connections. If nothing else, this will allow you to connect to the node yourself
+to check on connection status etc. There are 2 files that need to be edited.
+<P>
+<P>First edit /etc/services and add
<P>
<BLOCKQUOTE><CODE>
<PRE>
-'connect' ''
+node 3000/tcp #OH2BNS's Node Software
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>In a script, this might look like ...
+<P>Assuming you want it to run on port 3000
+<P>
+<P>Now cd /etc/xinetd.d and edit a new file called node. It should look like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-timeout 35
-abort (Busy|Sorry|Fail)
-connect telnet mary 3000
-'ogin:' 'gb7mbc'
-'>' 'telnet 44.131.93.96 7305'
-'connect' ''
+# default: on
+# unencrypted username/password pairs for authentication.
+service node
+{
+ socket_type = stream
+ wait = no
+ user = root
+ server = /usr/sbin/node
+ log_on_failure += USERID
+ disable = yes
+}
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<H2><A NAME="ss3.8">3.8 Telnet echo</A>
-</H2>
-
-<P>Cluster links in particular suffer greatly from the presence of telnet echo.
-This is caused by the telnet negotiation itself and can create at worst severe
-loops. At best it creates unnecessary bandwidth and large logfiles! There are
-things that can be done to limit this problem but will not always work dependent
-on the route taken to connect.
-<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 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
-can cause problems. There is a way of trying to suppress the telnet echo but
-this will not always work, unfortunately it is difficult to be more specific.
-Here is an example of what I mean ...
+<P>You now need to restart the xinetd daemon. First find out what the PID is
+like so ..
<P>
<BLOCKQUOTE><CODE>
<PRE>
-timeout 35
-abort (Busy|Sorry|Fail)
-connect telnet mary.lancs.ac.uk
-'ogin:' 'gb7mbc'
-'word:' 'mypasswd'
-'\$' 'stty -echo raw'
-'\$' 'telnet 44.131.93.96'
-'connect' ''
+ps auxw |grep xinetd
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>So, the first connection is made by Spider. This is fine as Spider uses the
-Net_Telnet script from within perl. This actually uses TCP rather than TELNET
-so no negotiation will be done on the first connection. Once connected to
-mary.lancs.ac.uk, the command is sent to suppress echo. Now a telnet is made
-to a cluster node that is accepting connections on port 23. The problem with
-this link is that the negotiation is made by the remote machine, therefore you
-have no control over it. The chances are that this link will create echo and
-there will be no way you can stop it.
-<P>
-<P>
-<H2><A NAME="ss3.9">3.9 Autostarting the cluster</A>
-</H2>
-
-<P>Ok, you should now have DXSpider running nicely and allowing connects by cluster
-nodes or users. However, it has to be shutdown and restarted manually. It
-would be much easier to have it start automatically.
-<P>
-<P>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 the cluster as you did earlier.
-<P>
-<P>Login as root and bring up the /etc/inittab file in your favourite editor. Add
-the following lines to the file near the end ...
+<P>You will get a reply something like this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-##Start DXSpider on bootup and respawn it should it crash
-DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+root 592 0.0 0.1 2256 620 ? S Feb07 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>This line works fine for RedHat distributions. It is also fine for SuSE up to
-7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ...
+<P>The PID or Process ID is 592 in this case so now we can issue the command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+kill -HUP 592
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>The line required for Slackware distributions is slightly different. My thanks to
-Aurelio, PA3EZL for this information.
+<P>All should now be operational and you should be able to log into the node by
+using a telnet session to the relevant port, like so ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+telnet localhost 3000
</PRE>
</CODE></BLOCKQUOTE>
<P>
-<P>This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
-it should it crash for any reason.
-<P>
-<P>As root type the command <EM>telinit q</EM>. DXSpider should start up
-immediately. You will see the output on tty7 and if you login as <EM>sysop</EM>
-you should find everything running nicely.
+<P>If that works, you are just about there. you should (assuming you have radios connected
+to the TNC's) be able to connect out to other stations and receive incoming ax25 and
+netrom connections.
<P>
<HR>
<A HREF="installation-4.html">Next</A>
projects / spider.git / blobdiff