mirror of
git://scm.dxcluster.org/scm/spider
synced 2024-09-21 07:47:10 +00:00
added set/lockout
added set/isolate fixed looping bug on ending in C client added VGS's docs
This commit is contained in:
djk
parent
f155969d60
commit
bff9ecf00b
4
Changes
4
Changes
@ -1,3 +1,5 @@
|
||||
13Jun00=======================================================================
|
||||
1. fixed looping bug in C client on ending.
|
||||
12Jun00=======================================================================
|
||||
1. Added RCMD for clx
|
||||
2. Added WCY processing
|
||||
@ -5,6 +7,8 @@
|
||||
4. Store echo settings
|
||||
5. Store pagelth settings
|
||||
6. sort out source of DXVars for callbot.pl
|
||||
7. added sh/isolate
|
||||
8. added sh/lockout
|
||||
11Jun00=======================================================================
|
||||
1. removed extraneous DXDebug from DXUtil
|
||||
2. added help for set/echo
|
||||
|
||||
@ -646,6 +646,10 @@ string to see a selection of files in a filearea eg:-
|
||||
|
||||
See also TYPE - to see the contents of a file.
|
||||
|
||||
=== 1^SHOW/ISOLATE^Show list of ISOLATED nodes
|
||||
|
||||
=== 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
|
||||
|
||||
=== 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
|
||||
Show the Moon rise and set times for a (list of) prefixes or callsigns,
|
||||
together with the azimuth and elevation of the sun currently at those
|
||||
|
||||
16
cmd/show/isolate.pl
Normal file
16
cmd/show/isolate.pl
Normal file
@ -0,0 +1,16 @@
|
||||
#
|
||||
# show/isolate
|
||||
#
|
||||
# show all excluded users
|
||||
#
|
||||
# Copyright (c) 2000 Dirk Koopman G1TLH
|
||||
#
|
||||
# $Id$
|
||||
#
|
||||
|
||||
my ($self, $line) = @_;
|
||||
return (1, $self->msg('e5')) unless $self->priv >= 1;
|
||||
|
||||
# search thru the user for nodes
|
||||
my @out = sort map { my $ref; (($ref = DXUser->get_current($_)) && $ref->isolate) ? $_ : () } DXUser::get_all_calls;
|
||||
return (1, @out);
|
||||
17
cmd/show/lockout.pl
Normal file
17
cmd/show/lockout.pl
Normal file
@ -0,0 +1,17 @@
|
||||
#
|
||||
# show/lockout
|
||||
#
|
||||
# show all excluded users
|
||||
#
|
||||
# Copyright (c) 2000 Dirk Koopman G1TLH
|
||||
#
|
||||
# $Id$
|
||||
#
|
||||
|
||||
my ($self, $line) = @_;
|
||||
return (1, $self->msg('e5')) unless $self->priv >= 9;
|
||||
|
||||
# search thru the user for nodes
|
||||
my @out = sort map { my $ref; (($ref = DXUser->get_current($_)) && $ref->lockout) ? $_ : () } DXUser::get_all_calls;
|
||||
return (1, @out);
|
||||
|
||||
@ -34,11 +34,13 @@ foreach $call (@call) {
|
||||
my $pcall = sprintf "%-11s", $call;
|
||||
push @out, $self->msg('snode1') unless @out > 0;
|
||||
if ($uref) {
|
||||
$sort = "Spider" if $uref->sort eq 'S';
|
||||
$sort = "AK1A " if $uref->sort eq 'A';
|
||||
$sort = "clx " if $uref->sort eq 'C';
|
||||
$sort = "Fred " if $uref->sort eq 'U';
|
||||
$sort = "BBS " if $uref->sort eq 'B';
|
||||
$sort = "Spider" if $uref->is_spider;
|
||||
$sort = "AK1A " if $uref->is_ak1a;
|
||||
$sort = "Clx " if $uref->is_clx;
|
||||
$sort = "User " if $uref->is_user;
|
||||
$sort = "BBS " if $uref->is_bbs;
|
||||
$sort = "DXNet " if $uref->is_dxnet;
|
||||
$sort = "ARClus" if $uref->is_arcluster;
|
||||
} else {
|
||||
push @out, $self->msg('snode3', $call);
|
||||
next;
|
||||
@ -59,3 +61,7 @@ foreach $call (@call) {
|
||||
}
|
||||
|
||||
return (1, @out);
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
3592
html/ARCluster_users_2_0_0.htm
Normal file
3592
html/ARCluster_users_2_0_0.htm
Normal file
File diff suppressed because it is too large
Load Diff
211
html/adminmanual-1.html
Normal file
211
html/adminmanual-1.html
Normal file
@ -0,0 +1,211 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||||
<TITLE>The DXSpider Administration Manual : Installation (Original version by Iain Phillips, G0RDI)</TITLE>
|
||||
<LINK HREF="adminmanual-2.html" REL=next>
|
||||
|
||||
<LINK HREF="adminmanual.html#toc1" REL=contents>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<A HREF="adminmanual-2.html">Next</A>
|
||||
Previous
|
||||
<A HREF="adminmanual.html#toc1">Contents</A>
|
||||
<HR>
|
||||
<H2><A NAME="s1">1. Installation (Original version by Iain Phillips, G0RDI)</A></H2>
|
||||
|
||||
<P>Last modified: November 1999 by Ian Maude, G0VGS
|
||||
<P>
|
||||
<H2><A NAME="ss1.1">1.1 Introduction</A>
|
||||
</H2>
|
||||
|
||||
<P>This section describes the installation of DX Spider v1.35 on a
|
||||
<A HREF="http://www.redhat.com">RedHat</A> Linux Distribution. I do not intend to try and cover the installation of Linux or the setup of the AX25 utilities. If you need help on this then read Iains original HOWTO on the
|
||||
<A HREF="http://www.dxcluster.org">DXSpider</A> website.
|
||||
<P>
|
||||
<P>I am assuming a general knowledge of Linux and its commands. You should know how to use <EM>tar</EM> and how to edit files using your favourite editor.
|
||||
<P>
|
||||
<P>The crucial ingredient for all of this is
|
||||
<A HREF="http://www.perl.org">Perl 5.004</A>.Now I know Perl 5.005 is out and this will almost certainly work with it, but
|
||||
<A HREF="http://www.redhat.com">RedHat 5.1</A> comes with 5.004. <EM>Be Warned</EM>, earlier versions of
|
||||
<A HREF="http://www.redhat.com">RedHat</A> <B>do not</B> come with 5.004 as standard, you need to
|
||||
<A HREF="ftp://upgrade.redhat.com">upgrade</A><P>
|
||||
<P>In addition to the standard Red Hat distribution you will require the following
|
||||
<A HREF="http://www.cpan.org/CPAN.html">CPAN</A> modules: -
|
||||
<P>
|
||||
<P>
|
||||
<UL>
|
||||
<LI> MD5-1.7.tar.gz</LI>
|
||||
<LI> Data-Dumper-2.10.tar.gz</LI>
|
||||
<LI> FreezeThaw-0.3.tar.gz</LI>
|
||||
<LI> MLDBM-2.00.ar.gz</LI>
|
||||
<LI> TimeDate-1.8.tar.gz</LI>
|
||||
<LI> IO-1.20.tar.tgz</LI>
|
||||
<LI> Net-Telnet-3.01.tar.gz
|
||||
</LI>
|
||||
</UL>
|
||||
<P>
|
||||
<P>
|
||||
<P><EM>Do</EM> get the latest versions of these packages and install them but use the above list as the earliest versions usable.
|
||||
<P>
|
||||
<H2><A NAME="ss1.2">1.2 Preparation</A>
|
||||
</H2>
|
||||
|
||||
<P>I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it.
|
||||
<P>
|
||||
<P>Login as root and create a user to run the cluster under. <B><I>UNDER NO CIRCUMSTANCES USE ROOT AS THIS USER!</I></B>. I am going to use the name <EM>sysop</EM>. You can call it anything you wish. Depending on your security requirements you may wish to use an existing user, however this is your own choice.
|
||||
<P>
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# adduser -m sysop
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>Now set a password for the user ...
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# passwd sysop
|
||||
# New UNIX password:
|
||||
# Retype new UNIX password:
|
||||
passwd: all authentication tokens updated successfully
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<H2><A NAME="ss1.3">1.3 Installing the software</A>
|
||||
</H2>
|
||||
|
||||
<P>Now to unpack the DX Spider distribution, set symbolic links and group permissions. This example assumes you are using version 1.35 but of course you would substitute the correct version number. Copy the tarball to /home/sysop and do the following.
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# cd ~sysop
|
||||
# tar xvfz spider-1.35.tar.gz
|
||||
# ln -s ~sysop/spider /spider
|
||||
# groupadd -g 251 spider (or another number)
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>If you do not have the command <EM>groupadd</EM> available to you simply add a line in /etc/group by hand.
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# vi /etc/group (or your favorite editor)
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>You also need to add some others to the group, including your own callsign (this will be used as an alias) and root. The finished line in /etc/group should look something like this
|
||||
<P><CODE>spider:x:251:sysop,g0vgs,root</CODE>
|
||||
<P>
|
||||
<P>The next step is to set the permissions on the Spider directory tree and files ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# chown -R sysop.spider spider
|
||||
# find . -type d -exec chmod 2775 {} \;
|
||||
# find . -type f -exec chmod 775 {} \;
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>This last step allows various users of the group <EM>spider</EM> to have write access to all the directories. This is not really needed just yet but will be useful when web interfaces start to appear.
|
||||
<P>
|
||||
<P>Finally, you need to fix the permissions on the ax25_call and netrom_call programs. Check where they are with the <EM>locate</EM> command and alter the permissions with the <EM>chmod</EM> command like this ..
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# chown root ax25_call netrom_call
|
||||
# chmod 4775 ax25_call netrom_call
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<H2><A NAME="ss1.4">1.4 Setting callsigns etc</A>
|
||||
</H2>
|
||||
|
||||
<P>Now login to your machine as the user you created earlier. In my case that user is called <EM>sysop</EM>. Once logged in, issue the following commands ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
$ cd /spider
|
||||
$ mkdir local
|
||||
$ mkdir local_cmd
|
||||
$ cp perl/DXVars.pm local
|
||||
$ cd local
|
||||
$ vi DXVars.pm (or your favourite editor)
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to suit your own environment. Note that this a perl file which will be parsed and executed as part of the cluster. If you get it wrong then perl will complain when you start the cluster process. It is important only to alter the text of any section. Some of the lines look a little odd. Take this line for example ....
|
||||
<P><CODE>$myemail = "ianmaude\@btinternet.com";</CODE>
|
||||
<P>
|
||||
<P>There appears to be an extraeneous slash in there. However this has to be there for the file to work so leave it in.
|
||||
<P>
|
||||
<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
|
||||
<P>
|
||||
<P>DON'T alter the DXVars.pm (or any other file) in /spider/perl, they are overwritten with every release. Any files or commands you place in /spider/local or /spider/local_cmd will automagically be used in preference to the ones in /spider/perl EVEN whilst the cluster is running!
|
||||
<P>
|
||||
<P>Save the new file and change directory to ../perl ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
$ cd ../perl
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>Now type the following command which creates the basic user file with you as the sysop.
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
$ create_sysop.pl
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<H2><A NAME="ss1.5">1.5 Starting up for the first time</A>
|
||||
</H2>
|
||||
|
||||
<P>We can now bring spider up for the first time and see if all is well or not! It should look something like this ...
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
$ cluster.pl
|
||||
DXSpider DX Cluster Version 1.35
|
||||
Copyright (c) 1998 Dirk Koopman G1TLH
|
||||
loading prefixes ...
|
||||
loading band data ...
|
||||
loading user file system ...
|
||||
starting listener ...
|
||||
reading existing message headers
|
||||
reading cron jobs
|
||||
orft we jolly well go ...
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>If all is well then login on another term or console as sysop and cd to /spider/perl. Now issue the following command ...
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
$ client.pl
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>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 case we will assume that this was set as GB7MBC. You should therefore see this when you login ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
G0VGS de GB7MBC 19-Nov-1999 2150Z >
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>If you do, congratulations! If not, look over the instructions again, you have probably missed something out. You can shut spider down again with the command ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
shutdown
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>and both the cluster and the client should return to Linux prompts.
|
||||
<P>
|
||||
<HR>
|
||||
<A HREF="adminmanual-2.html">Next</A>
|
||||
Previous
|
||||
<A HREF="adminmanual.html#toc1">Contents</A>
|
||||
</BODY>
|
||||
</HTML>
|
||||
282
html/adminmanual-2.html
Normal file
282
html/adminmanual-2.html
Normal file
@ -0,0 +1,282 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||||
<TITLE>The DXSpider Administration Manual : Configuration</TITLE>
|
||||
<LINK HREF="adminmanual-3.html" REL=next>
|
||||
<LINK HREF="adminmanual-1.html" REL=previous>
|
||||
<LINK HREF="adminmanual.html#toc2" REL=contents>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<A HREF="adminmanual-3.html">Next</A>
|
||||
<A HREF="adminmanual-1.html">Previous</A>
|
||||
<A HREF="adminmanual.html#toc2">Contents</A>
|
||||
<HR>
|
||||
<H2><A NAME="s2">2. Configuration</A></H2>
|
||||
|
||||
<H2><A NAME="ss2.1">2.1 Allowing ax25 connects from users</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>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
default * * * * * * - sysop /spider/perl/client.pl client.pl %u ax25
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<H2><A NAME="ss2.2">2.2 Allowing telnet connects from users</A>
|
||||
</H2>
|
||||
|
||||
<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
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>Then add a line in /etc/inetd.conf like this ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/perl/client.pl login telnet
|
||||
</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>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
killall -HUP inetd
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>
|
||||
<P>Now login as <EM>sysop</EM> and cd spider/perl. You can test that spider is accepting telnet logins by issuing the following command ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
client.pl login telnet
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<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>
|
||||
<P>Assuming all is well, then try a telnet from your linux console ....
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
telnet localhost 8000
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>You should now get the login prompt and be able to login as before.
|
||||
<P>
|
||||
<H2><A NAME="ss2.3">2.3 Setting up node connects</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>Start up the cluster as you did before and login as the sysop with client.pl.
|
||||
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>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
set/node gb7baa
|
||||
</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 and issue the command ...
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
client.pl gb7baa (using the callsign you set as a node)
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>You should get an initialisation string from DXSpider like this ...
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
client.pl gb7baa
|
||||
PC38^GB7MBC^~
|
||||
</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>
|
||||
<H3>Connection scripts</H3>
|
||||
|
||||
<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>
|
||||
<P>
|
||||
<PRE>
|
||||
|
||||
# All lines starting with a # are ignored, as are wholly 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]).
|
||||
</PRE>
|
||||
<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
|
||||
'Connect' ''
|
||||
'Connect' 'c np7'
|
||||
'Connect' 'c gb7dxm'
|
||||
'Connect' ''
|
||||
# you can leave this out if you call the script 'gb7dxm'
|
||||
client gb7dxm ax25
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>
|
||||
<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
|
||||
</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>
|
||||
<H3>Starting the connection</H3>
|
||||
|
||||
<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>
|
||||
<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 >
|
||||
</PRE>
|
||||
</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 ...
|
||||
<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
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<H2><A NAME="ss2.4">2.4 Automating things</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 and if connection scripts fail they have to be started again manually too, not much use if you are not at the console!
|
||||
So, in this section we will automate both. Firstly starting the cluster.
|
||||
<P>
|
||||
<H3>Autostarting the cluster</H3>
|
||||
|
||||
<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>
|
||||
<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
|
||||
</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>
|
||||
<P>So far so good, now to automate script connections...
|
||||
<P>
|
||||
<H3>The crontab file</H3>
|
||||
|
||||
<P>Login as <EM>sysop</EM> and create a file in /spider/local_cmd called crontab. Edit it with your favourite editor and add a line like this (I have included a comment)
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
# 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')
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>The callsign involved will be the callsign of the cluster node you are 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.
|
||||
<P>
|
||||
<P>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
|
||||
<A HREF="http://www.dxcluster.org/cron.html">DXSpider</A> website at the cron page where it is explained more fully.
|
||||
<P>
|
||||
<HR>
|
||||
<A HREF="adminmanual-3.html">Next</A>
|
||||
<A HREF="adminmanual-1.html">Previous</A>
|
||||
<A HREF="adminmanual.html#toc2">Contents</A>
|
||||
</BODY>
|
||||
</HTML>
|
||||
112
html/adminmanual-3.html
Normal file
112
html/adminmanual-3.html
Normal file
@ -0,0 +1,112 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||||
<TITLE>The DXSpider Administration Manual : Hop control and filtering</TITLE>
|
||||
<LINK HREF="adminmanual-2.html" REL=previous>
|
||||
<LINK HREF="adminmanual.html#toc3" REL=contents>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
Next
|
||||
<A HREF="adminmanual-2.html">Previous</A>
|
||||
<A HREF="adminmanual.html#toc3">Contents</A>
|
||||
<HR>
|
||||
<H2><A NAME="s3">3. Hop control and filtering</A></H2>
|
||||
|
||||
<P>Starting with version 1.13 there is simple hop control available on a per
|
||||
node basis. Also it is possible to isolate a network completely so that you
|
||||
get all the benefits of being on that network, but can't pass on information
|
||||
from it to any other networks you may be connected to (or vice versa).
|
||||
<P>
|
||||
<H2><A NAME="ss3.1">3.1 Basic hop control</A>
|
||||
</H2>
|
||||
|
||||
<P>In /spider/data you will find a file called hop_table.pl. This is the file that controls your hop count settings. It has a set of default hops on the various PC frames and also a set for each node you want to alter the hops for. You may be happy with the default settings of course, but this powerful tool can help to protect and improve the network. The file will look something like this ...
|
||||
<P>
|
||||
<BLOCKQUOTE><CODE>
|
||||
<PRE>
|
||||
#
|
||||
# hop table construction
|
||||
#
|
||||
|
||||
package DXProt;
|
||||
|
||||
# default hopcount to use
|
||||
$def_hopcount = 5;
|
||||
|
||||
# some variable hop counts based on message type
|
||||
%hopcount =
|
||||
|
||||
11 => 10,
|
||||
16 => 10,
|
||||
17 => 10,
|
||||
19 => 10,
|
||||
21 => 10,
|
||||
);
|
||||
|
||||
|
||||
# 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,
|
||||
},
|
||||
};
|
||||
</PRE>
|
||||
</CODE></BLOCKQUOTE>
|
||||
<P>
|
||||
<P>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.
|
||||
<P>
|
||||
<P>You can alter this file at any time, including whilst the cluster is running. If you alter the file during runtime, the command <EM>load/hops</EM> will bring your changes into effect.
|
||||
<P>
|
||||
<H2><A NAME="ss3.2">3.2 Isolating networks</A>
|
||||
</H2>
|
||||
|
||||
<P>It is possible to isolate networks from each other on a "gateway" node using the
|
||||
<EM>set/isolate <node call></EM> command.
|
||||
<P>
|
||||
<P>The effect of this is to partition an isolated network completely from another
|
||||
nodes 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.
|
||||
<P>
|
||||
<P>The only limitation currently is that non-private messages cannot be passed down
|
||||
isolated links regardless of whether they are generated locally. This will change
|
||||
when the bulletin routing facility is added.
|
||||
<P>
|
||||
<P>
|
||||
<HR>
|
||||
Next
|
||||
<A HREF="adminmanual-2.html">Previous</A>
|
||||
<A HREF="adminmanual.html#toc3">Contents</A>
|
||||
</BODY>
|
||||
</HTML>
|
||||
52
html/adminmanual.html
Normal file
52
html/adminmanual.html
Normal file
@ -0,0 +1,52 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||||
<TITLE>The DXSpider Administration Manual </TITLE>
|
||||
<LINK HREF="adminmanual-1.html" REL=next>
|
||||
|
||||
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<A HREF="adminmanual-1.html">Next</A>
|
||||
Previous
|
||||
Contents
|
||||
<HR>
|
||||
<H1>The DXSpider Administration Manual </H1>
|
||||
|
||||
<H2>Ian Maude, G0VGS, (ian@lurpac.lancs.ac.uk)</H2>Version 0.1 November 1999
|
||||
<P><HR>
|
||||
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
|
||||
<HR>
|
||||
<P>
|
||||
<H2><A NAME="toc1">1.</A> <A HREF="adminmanual-1.html">Installation (Original version by Iain Phillips, G0RDI)</A></H2>
|
||||
|
||||
<UL>
|
||||
<LI><A HREF="adminmanual-1.html#ss1.1">1.1 Introduction</A>
|
||||
<LI><A HREF="adminmanual-1.html#ss1.2">1.2 Preparation</A>
|
||||
<LI><A HREF="adminmanual-1.html#ss1.3">1.3 Installing the software</A>
|
||||
<LI><A HREF="adminmanual-1.html#ss1.4">1.4 Setting callsigns etc</A>
|
||||
<LI><A HREF="adminmanual-1.html#ss1.5">1.5 Starting up for the first time</A>
|
||||
</UL>
|
||||
<P>
|
||||
<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">Configuration</A></H2>
|
||||
|
||||
<UL>
|
||||
<LI><A HREF="adminmanual-2.html#ss2.1">2.1 Allowing ax25 connects from users</A>
|
||||
<LI><A HREF="adminmanual-2.html#ss2.2">2.2 Allowing telnet connects from users</A>
|
||||
<LI><A HREF="adminmanual-2.html#ss2.3">2.3 Setting up node connects</A>
|
||||
<LI><A HREF="adminmanual-2.html#ss2.4">2.4 Automating things</A>
|
||||
</UL>
|
||||
<P>
|
||||
<H2><A NAME="toc3">3.</A> <A HREF="adminmanual-3.html">Hop control and filtering</A></H2>
|
||||
|
||||
<UL>
|
||||
<LI><A HREF="adminmanual-3.html#ss3.1">3.1 Basic hop control</A>
|
||||
<LI><A HREF="adminmanual-3.html#ss3.2">3.2 Isolating networks</A>
|
||||
</UL>
|
||||
<HR>
|
||||
<A HREF="adminmanual-1.html">Next</A>
|
||||
Previous
|
||||
Contents
|
||||
</BODY>
|
||||
</HTML>
|
||||
41
html/sysop_t.html
Normal file
41
html/sysop_t.html
Normal file
@ -0,0 +1,41 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>Sysop Command Reference</title>
|
||||
<meta name="Keywords" content="DX Cluster, DXSpider, Spider, Packet Cluster, DXCluster, Pavillion Software, AK1A, AX25, AX.25, WWV, Packet Radio, Amateur Radio, Propagation, DX, DXing, G1TLH, GB7TLH, Dirk Koopman, Mailing list, Linux, RedHat, PERL">
|
||||
<meta name="Description" content="Software and systems for realtime digital communications between amateur radio stations for the provision of information on propagation conditions and stations operating">
|
||||
<meta name="Author" content="Dirk Koopman G1TLH">
|
||||
</head>
|
||||
<body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
|
||||
<FONT COLOR="#606060">
|
||||
<hr>
|
||||
<h2>Sysop Command Reference</h2>
|
||||
<hr>
|
||||
</font>
|
||||
|
||||
|
||||
<address><a href="mailto:djk@tobit.co.uk">Dirk Koopman G1TLH</a></address>
|
||||
<p>
|
||||
<!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
|
||||
<!-- hhmts start -->
|
||||
Last modified: Wed Nov 17 17:36:58 GMT 1999
|
||||
<!-- hhmts end -->
|
||||
<h4>Introduction</h4>
|
||||
|
||||
<p>This is the list of sysop commands currently available within the DX Spider DX Cluster system.</p>
|
||||
<p>It is automatically generated from the system help files.</p>
|
||||
|
||||
<h4>The Commands</h4>
|
||||
|
||||
<data>
|
||||
|
||||
<!-- Standard Footer!! -->
|
||||
<p> </p>
|
||||
<p>
|
||||
<FONT COLOR="#606060"><hr></font>
|
||||
<font color="#FF0000" size=-2>
|
||||
Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved<br>
|
||||
</font>
|
||||
<font color="#000000" size=-2>$Id$</font>
|
||||
</body>
|
||||
</html>
|
||||
41
html/user_en_t.html~
Normal file
41
html/user_en_t.html~
Normal file
@ -0,0 +1,41 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>User Command Reference</title>
|
||||
<meta name="Keywords" content="DX Cluster, DXSpider, Spider, Packet Cluster, DXCluster, Pavillion Software, AK1A, AX25, AX.25, WWV, Packet Radio, Amateur Radio, Propagation, DX, DXing, G1TLH, GB7TLH, Dirk Koopman, Mailing list, Linux, RedHat, PERL">
|
||||
<meta name="Description" content="Software and systems for realtime digital communications between amateur radio stations for the provision of information on propagation conditions and stations operating">
|
||||
<meta name="Author" content="Dirk Koopman G1TLH">
|
||||
</head>
|
||||
<body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
|
||||
<FONT COLOR="#606060">
|
||||
<hr>
|
||||
<h2>User Command Reference</h2>
|
||||
<hr>
|
||||
</font>
|
||||
|
||||
|
||||
<address><a href="mailto:djk@tobit.co.uk">Dirk Koopman G1TLH</a></address>
|
||||
<p>
|
||||
<!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
|
||||
<!-- hhmts start -->
|
||||
Last modified: Wed Nov 17 16:27:21 GMT 1999
|
||||
<!-- hhmts end -->
|
||||
<h4>Introduction</h4>
|
||||
|
||||
<p>This is the list of user commands currently available within the DX Spider DX Cluster system.</p>
|
||||
<p>It is automatically generated from the system help files.</p>
|
||||
|
||||
<h4>The Commands</h4>
|
||||
|
||||
<data>
|
||||
|
||||
<!-- Standard Footer!! -->
|
||||
<p> </p>
|
||||
<p>
|
||||
<FONT COLOR="#606060"><hr></font>
|
||||
<font color="#FF0000" size=-2>
|
||||
Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved<br>
|
||||
</font>
|
||||
<font color="#000000" size=-2>$Id$</font>
|
||||
</body>
|
||||
</html>
|
||||
62
html/user_t.html~
Normal file
62
html/user_t.html~
Normal file
@ -0,0 +1,62 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>Local extensions</title>
|
||||
<meta name="Keywords" content="DX Cluster, DXSpider, Spider, Packet Cluster, DXCluster, Pavillion Software, AK1A, AX25, AX.25, WWV, Packet Radio, Amateur Radio, Propagation, DX, DXing, G1TLH, GB7TLH, Dirk Koopman, Mailing list, Linux, RedHat, PERL">
|
||||
<meta name="Description" content="Software and systems for realtime digital communications between amateur radio stations for the provision of information on propagation conditions and stations operating">
|
||||
<meta name="Author" content="Dirk Koopman G1TLH">
|
||||
</head>
|
||||
<body TEXT="#000000" LINK="#0000ff" VLINK="#800080" BGCOLOR="#FFFFFF">
|
||||
<FONT COLOR="#606060">
|
||||
<hr>
|
||||
<h2>Local extensions</h2>
|
||||
<hr>
|
||||
</font>
|
||||
|
||||
|
||||
<address><a href="mailto:djk@tobit.co.uk">Dirk Koopman G1TLH</a></address>
|
||||
<p>
|
||||
<!-- Created: Sun Dec 13 20:25:14 GMT 1998 -->
|
||||
<!-- hhmts start -->
|
||||
Last modified: Mon Dec 28 22:43:23 GMT 1998
|
||||
<!-- hhmts end -->
|
||||
<h4>Introduction</h4>
|
||||
|
||||
The DXSpider system is designed to be extensible, to facilitate experimentation and
|
||||
self-training in both Amateur Radio and Programming.
|
||||
|
||||
<p>Having said all of that it is also designed so that it should be relatively easy to solve
|
||||
some real world problems that we have in the DX Cluster network as well as allow the implementation
|
||||
and testing of new protocols relatively safely.
|
||||
|
||||
<h4>What is it?</h4>
|
||||
|
||||
The mechanism I have chosen to allow people to do their own thing, is a perl <tt>.pm</tt> file called
|
||||
<b>Local.pm</b>. It is simply a perl package with its own address space, which has a number of defined
|
||||
subroutines called from certain places in the daemon code. I have provided a "blank" version for you
|
||||
to modify.
|
||||
|
||||
<h4>Where is it?</h4>
|
||||
|
||||
The template is <b>/spider/perl/Local.pm</b>. This file should be
|
||||
copied into <b>/spider/local</b> and then modified to your taste.
|
||||
|
||||
<p>At the moment, the template's format and standard functions are
|
||||
not really finalised, but I won't take away the functions that are
|
||||
currently there and I won't rename them. I reserve the right to
|
||||
add to them!
|
||||
|
||||
<p>As and when I get a clearer idea of what people might wish to do with
|
||||
it and how, I will add to the documentation on this page. So for now:
|
||||
this is it!
|
||||
|
||||
<!-- Standard Footer!! -->
|
||||
<p> </p>
|
||||
<p>
|
||||
<FONT COLOR="#606060"><hr></font>
|
||||
<font color="#FF0000" size=-2>
|
||||
Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved<br>
|
||||
</font>
|
||||
<font color="#000000" size=-2>$Id$</font>
|
||||
</body>
|
||||
</html>
|
||||
14
src/client.c
14
src/client.c
@ -90,6 +90,8 @@ char *root = "/spider"; /* root of data tree, can be overridden by DXSPI
|
||||
int timeout = 60; /* default timeout for logins and things */
|
||||
int paclen = DEFPACLEN; /* default buffer size for outgoing packets */
|
||||
int tabsize = 8; /* default tabsize for text messages */
|
||||
char *connsort = "local"; /* the connection variety */
|
||||
|
||||
|
||||
myregex_t iscallreg[] = { /* regexes to determine whether this is a reasonable callsign */
|
||||
{
|
||||
@ -289,7 +291,7 @@ int fcb_handler(sel_t *sp, int in, int out, int err)
|
||||
unsigned char c;
|
||||
|
||||
/* input modes */
|
||||
if (in) {
|
||||
if (ending == 0 && in) {
|
||||
char *p, buf[MAXBUFL];
|
||||
int r;
|
||||
|
||||
@ -507,11 +509,11 @@ lend:;
|
||||
*/
|
||||
void setmode(char *m)
|
||||
{
|
||||
char *connsort = strlower(m);
|
||||
if (eq(connsort, "telnet") || eq(connsort, "local") || eq(connsort, "nlonly") {
|
||||
connsort = strlower(m);
|
||||
if (eq(connsort, "telnet") || eq(connsort, "local") || eq(connsort, "nlonly")) {
|
||||
nl = '\n';
|
||||
echo = 1;
|
||||
mode = eq(connsort, "nlonly") 2 : 1;
|
||||
mode = eq(connsort, "nlonly") ? 2 : 1;
|
||||
} else if (eq(connsort, "ax25")) {
|
||||
nl = '\r';
|
||||
echo = 0;
|
||||
@ -577,7 +579,7 @@ lerr:
|
||||
}
|
||||
|
||||
/* this is kludgy, but hey so is the rest of this! */
|
||||
if (!eq(connsort, "ax25") && paclen == DEFPACLEN) {
|
||||
if (mode != 0 && paclen == DEFPACLEN) {
|
||||
paclen = MAXPACLEN;
|
||||
}
|
||||
}
|
||||
@ -770,8 +772,6 @@ main(int argc, char *argv[])
|
||||
|
||||
/* is this a login? */
|
||||
if (eq(call, "LOGIN") || eq(call, "login")) {
|
||||
chgstate(LOGIN);
|
||||
} else if (eq(
|
||||
|
||||
char buf[MAXPACLEN+1];
|
||||
char callsign[MAXCALLSIGN+1];
|
||||
|
||||
Loading…
Reference in New Issue
Block a user