From: djk Date: Tue, 13 Jun 2000 10:58:55 +0000 (+0000) Subject: added set/lockout X-Git-Tag: R_1_41~3 X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=commitdiff_plain;h=bff9ecf00b14e7d71d9504088a2fd7b9e5115fe1;hp=f155969d600561b9ef151a7ce2494a0c89aed033;p=spider.git added set/lockout added set/isolate fixed looping bug on ending in C client added VGS's docs --- diff --git a/Changes b/Changes index 5750aa10..77571734 100644 --- a/Changes +++ b/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 diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 599988b8..1e25f894 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -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 [|]^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 diff --git a/cmd/show/isolate.pl b/cmd/show/isolate.pl new file mode 100644 index 00000000..bea994fa --- /dev/null +++ b/cmd/show/isolate.pl @@ -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); diff --git a/cmd/show/lockout.pl b/cmd/show/lockout.pl new file mode 100644 index 00000000..6b7b7d49 --- /dev/null +++ b/cmd/show/lockout.pl @@ -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); + diff --git a/cmd/show/node.pl b/cmd/show/node.pl index e51b97c3..37db1dc8 100644 --- a/cmd/show/node.pl +++ b/cmd/show/node.pl @@ -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); + + + + diff --git a/html/ARCluster_users_2_0_0.htm b/html/ARCluster_users_2_0_0.htm new file mode 100644 index 00000000..f7f89916 --- /dev/null +++ b/html/ARCluster_users_2_0_0.htm @@ -0,0 +1,3592 @@ + + + + + + + + +Introduction + + + + + + + +
+ +

AR-CLUSTER +USER SECTION

+ +

 

+ +

 

+ +

1.0 User Commands

+ +

 

+ +

 

+ +

The +following table shows AR-Cluster commands available for the user. Newer +commands are highlighted in a yellow color.  User +commands can be executed via a Telnet connection, a RF connection or via the +AR-Cluster sysop console. 

+ +

 

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

Command

+ 		+

Description

+
+

ANNOUNCE

+ 		+

Command is used to send + a line of text to all stations.   The + ANNOUNCE command defaults to the local node.  + If you wish to make announcement to a particular node, you can specify + the call of the node on the command.  + If you want to announce to all nodes user the ANNOUNCE/FULL option. + The ANNOUNCE/AREA feature allows you to set up area qualifiers for each + node.  For example, a node could be + listed as being in AUS, CTDXCC, STX, TX, and USA5 (Austin, Central Texas DX + and Contest Club, South Texas, Texas and US 5th call area).   The ANNOUNCE/AREA command is then sent to + qualifying nodes.

+

Syntax: Announce msg

+

             Announce/call msg

+

             Announce/Full msg

+

             Announce/Area msg

+

 

+
+

BYE

+ 		+

Exit the cluster.

+

Syntax: Bye

+
+

CONFERENCE

+ 		+

Enter the conference mode.  Exit the conference mode with a /EXIT.  While in the conference mode DX spots are + send with a *DX

+
+

DB

+ 		+

Command to display the + custom database tables in the system.   + The general command DB will display all available databases.  The command DB/TABLE will show information + from the specific table.

+

Syntax:  DB – Shows available databases

+

            DB/table shows + information from a specific table

+

Example:  DB shows a table is + available called Mic

+

                   DB/MIC shows a list of + help topics from the MIC database.

+

                DB/MIC KEN4 + shows the microphone pin-out for a four pin Kenwood radio.

+
+

DELETE

+

KILL

+ 		+

This command is used to + delete mail messages.

+

If the mail message is a + bulletin mail (addressed to all) and it is being deleted by the station who + originated the mail, then a PC49 command will be deleting the mail on other + nodes in the network.

+

A Delete or Kill without a message number will delete the last read + message.

+

Syntax: DElete message#

+

 

+
+

DIRECTORY

+

DIRECTORY/BULLETINS

+

DIRECTORY/NEW

+

DIRECTORY/OWN

+

DIRECTORY/SUBJECT

+

DIRECTORY/NN

+

 

+

 

+ 		+

The DIRECTORY command is used to display a list + of the current mail messages on the node.  + Messages which have been read are indicated by a hyphen (-) next to + the message number.  A private message + is indicated by a "p".

+

Command: DIr/Bulletins command lists all of the + current bulletins on the system.

+

Command: DIrectory/new command lists all new + personal and bulletin mail since the last DIr command.

+

Command: DIrectory/OWN   Display mail messages which are addressed to or from your + station.

+

Command: Directory/SUbject filter the displayed + records by subject

+

Command: DIrectory/nn    Display the nn most-recent mail messages. 

+

 

+

 

+
+

DX

+ 		+

Command allowing the announcement + of DX spot information. The Credit DX function was intentionally left out of + the product due to sysop request.

+

Syntax: DX frequency + callsign comment

+

The frequency can be + entered in the format 14.1951 or  + 14195.10

+

 

+

 

+
+

HELP

+ 		+

Display help information on a topic.

+

Syntax: Help

+

             Help/Topic

+
+

LIST

+ 		+

Alias for the Directory command.

+
+

QUIT

+ 		+

Exit the cluster.

+

Syntax: Quit

+
+

READ

+ 		+

This command is used to + read mail messages.  A Read command + without a message number will read the last message to your station.

+

Syntax: Read message#

+

 

+
+

REPLY

+

REPLY/RR

+

REPLY/DELETE

+

REPLY/DELETE/RR

+ 		+

The reply command is + used to reply to an email message.   + Command options are to request a return receipt, RR, and to delete the + message we are replying to.

+

Syntax:  Reply nn

+

              Reply/RR nn

+

              Reply/Delete nn

+

              Reply/Delete/RR nn

+

Where nn is the message + number

+
+

RESTART_MESSAGES

+ 		+

Restarts the mail + system. Deletes obsolete files and re-numbers mail messages.

+
+

SEND

+

SEND/PRIVATE

+

SEND/RR

+

SEND/PRIVATE/RR

+

SEND/COPY

+

SP

+ 		+

The SEND command is used + to send a mail message to another station. The system will prompt you for the + destination call and the subject.  + Enter the message line by line.  + The mail send process is terminated with either a ctrl/Z or the text + /EXit.

+

The /PRIVATE qualifier + can be used to send a private message. The /RR qualifier requests a return + receipt, which forces a confirmation when the mail is read.

+

The /Copy is used to + send a copy of a message to another station.

+

A mail message can be + canceled with the Ctrl-Y or a /CAncel command.

+

Syntax: Send 

+

              Send/Private or SP

+

              Send/RR

+

              SEND/COPY Msg# To-Station

+

 

+

A mail message addressed to “ALL” becomes a bulletin mail and is sent + to all nodes connected at the time the mail is entered. 

+

 

+

A mail message addressed to “LOCAL” becomes a bulletin mail but stays + on the node it’s entered on and is not sent through the system.  The “LOCAL” to filed name gets changed to + “ALL”.

+
+

SET/ANNOUNCEMENTS

+

SET/NOANNOUNCEMENTS

+ 		+

Commands to control + whether announcements are sent to your station.

+

Syntax: + SEt/ANNouncements

+

              SEt/NOANNouncements

+

 

+
+

SET/BEEP

+

SET/NOBEEP

+ 		+

Commands to control + whether the bell character is send to the user on each transmission.

+

Syntax: SEt/BEep

+

              SEt/NOBEep

+
+

SET/CALENDAR

+ 		+

Commands used to send + post a event spot to the calendar.  + The regions are defined by the system in the station configuration and + the node configuration.  See + announcement regions fro details.  The + date is set in the format of

+

dd-mmm-yyyy.  The event describes the calendar posting.

+

Syntax: + SEt/CALendar/region/date Event

+

Ex: + Se/CAL/CTDXCC/3-Jul-1999 DX Club meeting

+

 

+
+

SET/DXSqth   SET/NODXSqth

+ 		+

Command to enable or + disable the optional DX spotter’s QTH displayed at the end of the spot.  If the spot originated in the US or + Canada, the state or province of the spotter is posted.  Elsewhere in the world, the CTY prefix of + the spotter is shown.

+
+

SET/DX_ANNOUNCEMENTS

+

SET/NODX_ANNOUNCEMENTS

+ 		+

Commands used to control + whether DX spots are sent to you.

+

Syntax: + SEt/DX_Announcements

+

             SEt/NODX_Announcements

+

 

+
+

SET/FILTER + CTY

+

 

+ 		+

Allows user filtering of + spots returned to his station based on the country of the spotter.  Filtering modes are PASS, REJECT and + OFF.  Country prefixes should match + those on your node (set by the ARRL.CTY file).  Examples:

+

    SET/FILTER CTY/PASS K,VE

+

    SET/FILTER CTY/REJECT JA

+

    SET/FILTER CTY/OFF

+

 

+
+

SET/FILTER + DX

+ 		+

Allows the user to + filter spots based on the country of the spot.  The country prefix (CTY) should match that in the latest + ARRL.CTY file.

+

Filtering modes are + PASS, REJECT and OFF.

+

SET/FILTER DX/PASS K

+

SET/FILTER DX/REJECT K

+

SET/FILTER DX/OFF

+

 

+
+

SET/FILTER + NEEDS

+ 		+

Allows the user to set + his needs.  Needs entries are + overwritten unless the data is proceeded with a "+"  Examples:

+

SET/FILTER NEEDS/CW + R1FJ,VP8/h,JY,ZS8,VU4

+

SET/FILTER NEEDS/SSB + 3D2/r,BV9P,JD/o,JD/m

+

SET/FILTER NEEDS/RTTY + R1MV,SV5,T33,ZK1/n

+

You can also filter + spots by your needs by:

+

SET/FILTER NEEDS/ON

+

SET/FILTER NEEDS/OFF

+

 

+
+

SET/FILTER + BANDPASS

+ 		+

Allows the filtering of + spots by band and mode.

+

Filtering modes are + PASS, REJECT and OFF.

+

SET/FILTER BANDMODE/PASS + 20-CW,20-RTTY

+

SET/FILTER + BANDMODE/REJECT 6-CW,6-SSB

+

 

+
+

SET/FILTER + STATE

+ 		+

Allows user filtering of + spots returned to his station based on the state or province of the + spotter.  Filtering modes are PASS, + REJECT and OFF.  In addition to + specification by state, filters can be set using US call areas of:  K0 thru K9   Examples:

+

    SET/FILTER STATE/PASS TX,AR,OK

+

    SET/FILTER STATE/PASS K1,K2,K3    

+

    SET/FILTER STATE/REJECT K6,K7

+

    SET/FILTER STATE/OFF

+
+

SET/HERE

+

SET/NOHERE

+ 		+

These commands are used + to give some indication to other users when you are available. Displayed + callsigns of users who have done a SET/NOHERE are displayed in parentheses.

+

 Syntax: SEt/Here SEt/NOHere

+

 

+
+

SET/HOMENODE

+ 		+

Command used to specify your "home + node".  Home node is used in mail + forwarding and in talk across limited protocol connections.

+

Syntax:   + SEt/HOMenode call

+

 

+
+

SET/LOCATION

+ 		+

Command allowing you to + specify your latitude and longitude coordinates. Latitude/longitude + information is used  for calculating + beam headings and MUF information

+

 Syntax: SEt/Location lat-deg lat-min N/S + long-deg long-min E/W

+

 

+

 

+

 

+
+

SET/LOGIN_ANN

+

SET/NOLOGIN_ANN

+ 		+

Command to disable login + messages to the user.

+

Syntax:  SET/LOGIN_ANNOUNCEMENTS      

+

             SET/NOLOGIN_ANNOUNCEMENTS

+

 

+
+

SET/NAME

+ 		+

Command used to set you + name in the cluster database.

+

Syntax: SEt/Name name

+

 

+
+

SET/QTH

+ 		+

This command allows you + to set your QTH.

+

Syntax: SEt/Qth location + (city, state)

+

 

+
+

SET/TALK

+

SET/NOTALK

+ 		+

These commands control + whether you want to receive talk messages from other users.

+

Syntax: SEt/TAlk + SEt/NOTAlk

+

 

+
+

SET/WWV_ANNOUNCEMENTS

+

SET/NOWWV_ANNOUNCEMENTS

+ 		+

Commands to control + whether WWV announcements are sent to your station.

+

Syntax: + SEt/WWV_announcements SEt/NOWWV_announcements

+

 

+
+

SET/WWX_ANNOUNCEMENTS

+

SET/NOWX_ANNOUNCEMENTS

+ 		+

Commands to control + whether WX announcements are sent to your station.

+

Syntax: + SEt/WX_announcements

+

             SEt/NOWX_announcements

+

 

+
+

SHOW/ANNOUNCE

+ 		+

Displays previously-made announcements.

+

Syntax:   + SHow/ANounce

+

 

+
+

SHOW/ARCHIVE

+ 		+

Displays the files which reside in the ARCHIVE + folder area.

+

Syntax:   + SHow/ARchive

+

 

+
+

SHOW/BUCKMASTER

+

SHOW/BUCK2

+ 		+

The SHOW/BUCKMASTER command can be used to + display call information from the Buckmaster CD.  

+

Syntax:  + SHow/BUCkmaster call

+

         + SHow/BUCK2

+
+

SHOW/BULLETINS

+ 		+

Command: SHOW/BULLETINS   Displays the files which reside in the + BULLETIN folder area.

+

Syntax:   + SHow/Bulletins

+

 

+
+

SHOW/CALENDAR

+ 		+

The SHOW/CALENDAR command is used to view two + months of calendar posts.   If the + date is omitted, the date defaults to the current month.

+

    + Syntax: SHow/CALendar 

+

                + SHow/CALendar  mm-yy

+

      + Ex:      SH/Cal 7-99

+

 

+

 

+
+

SHOW/CLUSTER

+ 		+

Displays the number of nodes in the current + cluster configuration, the number of local users, the total number of users, + and the uptime for the node.  For + nodes running in full protocol, the actual number of reported users are used + in the calculation.  If no users are reported + connected to the node (PC16), the number of users reported in the PC50 user + count is used in the calculation.

+

Syntax:   + SHow/CLuster

+

 

+
+

SHOW/COMMANDS

+ 		+

This command was replaced by the DB command.

+
+

SHOW/CONFIGURATION

+

SH/C/N

+ 		+

Displays the physical configuration of the

+

cluster network.  + The nodes are listed, and the users connected to each node are + displayed.  Specifying a node on the + command lists stations connected to that node.   A optional switch on the end of the command will show only the + node configuration.  SH/C/N

+

Syntax:  + SHow/Configuration

+

             + SHow/Configuration call

+

        

+

 

+

 

+
+

SHOW/DX

+

SHOW/DX/nn

+

SHOW/DX STATS

+

SHOW/DX call

+

SHOW/DX call*

+

SHOW/DX MISSED

+

SHOW/DX + FREQ-FREQ

+

SHOW/DX BAND CALL

+

SHOW/DX BAND CTY

+ 		+

This command is used to view previously logged DX + spots.  Band can be specified in + frequency or wave-length.  If the band + is omitted, all bands are shown.  + Note: if the frequency/band parameter is 10, the logic defaults to + wave-length.  You may also specify the + number of previous entries displayed, e.g. SHOW/DX/15 will show the last 15 + entries.  Omitting this number will + cause the default of 5 entries to be displayed. A call or partial call can + also be specified.  A  shortcut for SH/D is */D.  If room is available in the comment field, + the county prefix, CTY of the spot will also be displayed.  SHow/DX STATS shows the spot stats for + time periods of hours to the last month.  + The SH/DX MISSED command shows the spots reported since your last + logout.

+

 

+

Syntax:   + SHow/Dx show the last 5 spots

+

SHow/Dx/nn     + where nn is the number of entries to be displayed.

+

SHow/Dx 20          20 meter spots only (valid bands: + 160, 80, 40, 30, 20, 17, 15, 12, 10, 6, 2)

+

SHow/Dx 14         20 meter spots only (valid + frequencies: 1, 2, 7, 14, 18, 21, 24, 28, 50)

+

SHow/Dx /15 V73AQ    Show the last 15 spots for V73AQ

+

SHow/Dx /15 V73AQ*    Show the last 15 spots for the Marshall + Islands

+

Show/Dx OH Show spots for calls beginning with OH. 

+

Show/Dx FreqLow-FreqHigh command. Where frequency range is  14.1-14.2 or 7050-7100

+

 

+

New commands allow the + filtering by band and call or band and country.  Examples:

+

SH/DX BAND CALL       SH/DX 12 V73CW

+

SH/DX BAND COUNTRY    SH/DX 12 V73*

+

Note: You do not have to + know the exact country prefix, just enter a valid call from the country + followed by a *

+

 

+
+

SHOW/DX SQL

+ 		+

SQL queries are very + powerful and allows you to build custom commands to query the DX spot + database.   With some simple examples, + is not too hard to pick up.  The new + SH/DX query commands can be ran against any of the fields in the DX spot + database.  Simple query examples are:

+

    sh/dx/10 where dx = 'XZ0A'

+

    sh/dx/50 where freq > 50000.0 and + freq < 54000.0

+

    sh/dx/50 where cty = 'V7'

+

    sh/dx/50 where spotter = 'N5CQ'

+

    sh/dx/50 where FromNode = 'WU3V'

+

    sh/dx/50 where CqZone = '23'

+

    sh/dx/50 where ItuZone = '64'

+

    sh/dx/50 where Band = '12'

+

    sh/dx/50 where Mode = 'CW'

+

    sh/dx/50 where SpotterCty = 'VE'

+

    sh/dx/25 where SpotterSubCty = 'TX'

+

    sh/dx/30 where Comment = 'RTTY'

+

    sh/dx/50 where DateTime > #2/1/00# + AND DateTime < #5/1/00#

+

 

+

You can use the SQL + ORDERBY operator to order the spots by date and time.  The ORDERBY operator followed by DESC will + show the spots in descending order, the most recent spots are shown first.

+

    sh/dx/30 where DX = 'XZ0A' ORDER BY + DateTime DESC

+

 

+

You can also use the + LIKE operator and the wildcard character "*" to do partial + matches.  For example to show spots + with the word "QSL" anywhere in the comment field use the following + query:

+

    sh/dx/50 where comment LIKE '*QSL*'

+

 

+

Compound SQL statements + can be generated by combining two or more operations into one query:

+

    sh/dx/50 where Mode = 'CW' AND Band = + '10' AND spotter = 'N5CQ' ORDERBY DateTime DESC

+

    sh/dx/50 where dx = 'FO0AAA' AND + DateTime > #2/1/00# AND DateTime < #5/1/00#

+

    sh/dx/50 where dx = 'FO0AAA' AND comment + LIKE '*QSL*' ORDERBY DateTime DESC

+

 

+
+

SHOW/FILTER NEEDS

+ 		+

The SHOW/FILTER NEEDS + command will display the country needs saved on the node.

+
+

SHOW/FDX

+ 		+

Formatted DX command.  The + SHOW/FDX command is identical to the SHOW/DX command except that the output + of the command is formatted in the original node real-time node broadcast + format.  This command allows you to + display spots in a format that popular contesting program expect.  See Show/DX for command syntax.

+

 

+

 

+
+

SHOW/FITU

+ 		+

The SHOW/FITu command is identical to + the SHOW/ITU command except that the output of the command is formatted in + the original node real-time broadcast format.  This command allows you to display spots in a format that + popular contesting program expect.  + See Show/ITu for command syntax.

+
+

SHOW/FZONE

+ 		+

The SHOW/FZOne command is identical + to the SHOW/ZOne command except that the output of the command is formatted + in the original node real-time broadcast format.  This command allows you to display spots in a format that + popular contesting program expect.  + See Show/ZOne for command syntax.

+
+

SHOW/FILES

+ 		+

Displays the files which reside in the general + FILES folder area.

+

Syntax:   + SHow/FILes

+

 

+
+

SHOW/GRID

+ 		+

Displays the MaidenHead Grid Locator for a + station.

+

Syntax:   + SHow/Grid callsign 

+

 

+
+

SHOW/HAM

+ 		+

Alias for SH/BUCK

+
+

SHOW/HEADING

+ 		+

Displays the heading and distance to the call + specified on the command. The heading calculations use your + latitude/longitude information if you have specified it with the SET/LOCATION + command.  Otherwise, it will use the + location of the node.

+

 

+

If the destination call + is found in the UserInfo, database, with a valid latitude/longitude the + heading and distance to that call will be displayed.  If the destination call is not found in the + UserInfo database, then the prefix of the country is determined and the + heading and distance to the country is displayed.  The user does not have to know the exact prefix of the country + thus V7, V73, V73AQ all work.

+

Syntax:   + SHow/Heading call

+

 

+

Details:

+

If the TOCALL and the + FROM CALL both have LAT/LON's entered into the database, the distance and + bearing is calculated and reads as follows:

+

Station: K5HOG  360 deg.  + 68 mi.  42 km. from user WA5IED

+

 

+

If the FROM CALL does + not have a LAT/LON in the database, the location of the  node is used instead as:

+

Station: K5HOG  360 deg.  + 68 mi.  42 km. from node AB5K

+

 

+

If the TOCALL does not + have a LAT/LON in the database, the location of the country is used as:

+

Country: V7 = Marshall + Islands  280 deg.  6206 mi.  + 3856 km. from user K5HOG 

+

 

+

 

+
+

SHOW/HOME

+ 		+

Shows the home node for + the selected call.

+

Syntax:  SH/HOME CALL

+
+

SHOW/ITU

+ 		+

This command is used to + view previously logged DX spots by ITU zone. Omitting the nn number will + cause the default of 5 entries to be displayed.

+

This command is similar + to the SH/DX command except the command shows the most recent spots in a + designated ITU zone.

+

Syntax:   SHow/ITu/nn  ItuZone#

+

 

+

 

+
+

SHOW/LOCATION

+ 		+

Displays the latitude/longitude information, + which has been previously been entered by with the SET/LOCATION command. 

+

Syntax:   + SHow/LOCation call

+

 

+
+

SHOW/LOG

+ 		+

The SH/LOG command + displays the log data for the station showing dates and times when the + station logged onto and logged out of the cluster.

+

Syntax:   SHow/LOG call 

+
+

SHOW/MUF

+ 		+

Displays maximum useable + frequency (MUF) calculations for the country specified on the command. The + origination point is your station if you have previously specified it with + the SET/LOCATION command; otherwise, the latitude/ longitude of the node.  You do not have to know the exact CTY + prefix, just enter a call and AR-Cluster will calculate the country prefix.

+

Syntax: SHow/Muf call

+

 

+
+
SHOW/NEED
+ 		+

Displays the needs + database for the specified user or country prefix. You may also specify a + mode qualifer to just show needs for that mode.

+

Syntax:   SHow/NEed call

+

               SHow/NEed prefix*  (* takes the call and gives the prefix)

+

               SHow/NEed/mode  call   + where mode is CW, SSB, or RTTY

+

Examples:  SH/NEed AB5K, SH/NE/RTTY WU3V, SH/NE + V73A*, SHow/need/CW V73*

+
+

SHOW/NODES

+ 		+

Displays a list of direct nodes and a list of each indirect node + connected via that node.

+

Syntax: Show/Nodes

+
+

SHOW/PREFIX

+ 		+

The Show/Prefix command + will calculate the prefix of the passed call and display the prefix and + country information. Such as the country name, and CQ/ITU zones.

+

Syntax: SHow/Prefix call +

+

Example: + SHOW/PREFIX  V73A

+

 

+
+

SHOW/QSL

+

 

+ 		+

The SHOW/QSL is used to show QSL manager + information from the AR-Cluster database.  + The stock database contains almost 180,000 lines of QSL manager + information.

+

Syntax: SHow/QSL call

+
+

SHOW/STATION

+ 		+

Displays known information for the specified + station such as name, home node, location, latitude/longitude and last + connect date/time.  The distance and + heading to the station is also shown.

+

Syntax:   + SHow/STation call

+

 

+
+

SHOW/SUN

+ 		+

Displays the sunrise and sunset for the specified country.  If the exact country prefix is not known, + enter a valid call for the country and the Cty prefix will be automatically + determined.  A show/sun without any + callsign defaults to the sun data for the user’s location.  SH/SUN also works on US call areas of K0 through K9, resulting in the sunrise/sunset + being shown for each state

+

Syntax:  Show/Sun prefix or call +

+

 

+
+

SHOW/TALK

+ 		+

Displays the last talk messages to your station.

+

Syntax:  SHow/TAlk/nn where nn + is the number of talk messages to display.

+

Example: SH/TA/15,   SH/TA 

+

 

+

 

+
+

SHOW/TIME

+

SHOW/TIME + COUNTRY

+ 		+

Displays the current + time if no country is presented.  If a + country is included the local time in the country is displayed.   Note:  its not possible + to resolve the correct local time from all countries due to their size.  I.E.  + US, VE etc.

+

Syntax: SHow/Time

+

 

+
+
SHOW/TIP
+ 		+

The SH/TIP command + displays a random tip to the user. 

+
+
SHOW/TRAFFIC
+ 		+

Command to show the + packet traffic through the node.  + Shows the node time up and inbound and outbound packets and number of + bytes handled.

+
+
SHOW/USERS
+ 		+

Displays what stations + are currently connected to the node. A call which is displayed in parentheses + () signifies that user has done a SET/NOHERE command.  An asterisk by the call signifies that the + station is in Conference Mode.

+

Syntax: SHow/Users

+

 

+
+

SHOW/VERSION

+ 		+

Displays the version of + the AR-Cluster software. Syntax: SHow/Version

+

 

+
+

SHOW/WWV

+ 		+

Displays the most-recent WWV propagation reports + logged into the system.

+

Syntax:   + SHow/WWv  Displays 5 entries

+

        + SHow/WWv/nn   Displays nn + entries

+

 

+
+

SHOW/WX

+ 		+

Displays previously weather spot announcements.

+

Syntax:   + SHow/WX 

+

 

+

 

+
+

SHOW/WXSTATION

+ 		+

Displays current weather data from an optional + weather station.  The wind chill will + be displayed if it is less that 4 degrees lower that the current + temperature.  Optional values for + humidity, barometric pressure and rainfall will be shown if available from + your weather station.

+

Syntax:   + SHow/WXStation  call

+

 

+

Example output:

+

WX for Bee Cave, TX:  Temp(F) + 81  Wind 180 at 12 MPH

+
+

SHOW/ZONE

+ 		+

This command is used to + view previously logged DX spots by CQ zone. Omitting the nn number will cause + the default of 5 entries to be displayed.

+

This command is similar + to the SH/DX command except the command shows the most recent spots in a + designated CQ zone.

+

Syntax:   SHow/ZOne/nn  CQZone#

+

 

+

 

+
+

TALK

+ 		+

The TALK command is used + to talk to various stations which are connected to the cluster.  Talk commands can be one-liners such as Talk + WU3V followed by a message, or you can enter the talk mode by typing Talk + WU3V.  While in the talk mode, + anything typed on the keyboard will be transmitted to the talk station.  A ctrl/Z will only terminate your side of + the talk. If the talk message is directed to a station that is node connected + but that station has a listed home node and the home node is connected, the + talk message will be send to the home node for distribution.  This allows talk across limited protocol + connections.

+

Syntax: Talk call    or Talk call message

+

 

+

A special flag character “>”can be used to communicate with stations + across a limited protocol (-EXT) connection.   The “>” character directs the talk command to a specific + node, from there, the node takes care of distributing the message to the + correct station.

+

Talk Call > NODE Message

+

 

+
+

TALK/TIMESTAMP

+ 		+

This command sends a one + line talk message to the station with a timestamp.

+

Syntax: Talk/Timestamp + call message

+

 

+
+

TYPE/ARCHIVE

+

TYPE/BULLETINS

+

TYPE/FILES

+ 		+

This command is used to display a file, in one of + the following folder areas: ARCHIVE, BULLETINS or FILES.  The files which are available may be shown + by doing a SHOW/FILES, SHOW/BULLETIN, or SHOW/ARCHIVE. 

+

Syntax:   + TYpe/area filename

+

 

+

 

+
+

WWV

+ 		+

The WWV command allows + you to announce and log WWV propagation information.  Previously-logged WWV information can be + displayed  using the  SHOW/WWV command.

+

Syntax: WWv + SF=xxx,A=xx,K=xx,forecast

+

 

+
+

WX

+

WX/FULL

+ 		+

The WX command allows + you to announce weather conditions to the cluster. WX commands default to the + local cluster.  WX/FULL sends the + weather announcement to the full cluster.

+

Syntax: WX information + WX/FULL information

+

 

+
+ +

 

+ +

 

+ +

 

+ +

2.0 +FILTERS

+ +

The cluster has a set of +generic filters, which are used to set up the region of spot coverage for the whole +node.  The user can also apply +additional filters to further narrow the area of coverage.

+ +

 

+ +

2.0.1 Cluster Filters

+ +

Users should be +aware of the filtering settings on the node and how node filters may effect his +operations.  The following table +summarizes DX filtering operations, which may be applied to an AR-Cluster node. 

+ +

 

+ +

 

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

DX Filters

+ 		+

Description

+ 		+

Node Setting

+
+

Anti-Loop

+ 		+

Spots with a exact match are deleted

+ 		+

Always On

+
+

Spot Lockout

+ 		+

List of bad calls to reject:  + TEST, FR0G, etc.

+ 		+

Active

+
+

Spotter CTY and State

+ 		+

Spotter CTY and State filters can be activated by the sysop to limit + the spot coverage area presented to users on the node.  User filters can be activated to further + limit the spot coverage area.

+ 		+

None

+
+

Spot Age

+ 		+

Reject spots over xx minutes old

+ 		+

Off

+
+

Spotter CTY

+ 		+

Pass/Reject based on spotter country

+ 		+

Off

+
+

Node CTY

+ 		+

Pass/Reject based on spotter node country

+ 		+

Off

+
+

Band-Time Reject

+ 		+

Reject spots per Band and Time of Day.  + i.e. 80m-12Z, 80m-13z

+ 		+

None

+
+

Comment

+ 		+

Reject spots containing specific spot grabber flags in the comment + field

+ 		+

Off

+
+

OH2AQ

+ 		+

Reject spots coming from a OH2AQ spot grabber

+ 		+

Off

+
+

Close Dupe

+ 		+

Reject spots with the same call spotted within the last x minutes + within a frequency of y Hz.

+ 		+

Off

+
+

Self Spot

+ 		+

Do not allow a user to spot himself

+ 		+

Off

+
+ +

 

+ +

2.0.1 Spotter CTY/STATE Filters

+ +

The SET/FILTER CTY/STATE command allows users to +configuration their own filters based on the country and the state of the +spotter.  Examples are:

+ +

 

+ +

Send +spots originating in the USA, Mexico and Canada:

+ +

SET/FILTER CTY/PASS K,XE,VE

+ +

SET/FILTER STATE/OFF

+ +

 

+ +

Send +US spots originating in Texas, Oklahoma and Arkansas:

+ +

            SET/FILTER +CTY/PASS K

+ +

SET/FILTER STATE/PASS TX,OK,AR

+ +

 

+ +

Send +spots originating in the 4th and 5th call areas:

+ +

SET/FILTER CTY/PASS K

+ +

SET/FILTER STATE/PASS K4,K5

+ +

 

+ +

Send +all US spots except for the California and the US 7th call area

+ +

SET/FILTER CTY/PASS K

+ +

SET/FILTER STATE/REJECT K6,K7

+ +

 

+ +

Show +spots originating anywhere in the world:

+ +

SET/FILTER CTY/OFF

+ +

SET/FILTER STATE/OFF

+ +

 

+ +

You can examine +you current CTY/State filters with the following commands:

+ +

SHOW/FILTER +CTY

+ +

SHOW/FILTER +STATE

+ +

 

+ +

2.0.2 BandMode Filters

+ +

User BandMode +filters allow filtering of spots by the band and mode. Valid bands are 160, 80, +40, 30, 20, 17, 15, 12, 10, 6, 2, 1, 70, VHF, UHF, and MW.  Valid modes are CW, RTTY, and SSB.  The user should be aware that the mode +frequency allocations are set by the sysop and sometimes overlap.  For example in a CW contest, often CW spots +come into the system in the RTTY part of the band.  Thus narrowing Bandmode filters to only display CW QSO’s will +filter any CW spots in the RTTY part of the band.  This is one of the most use commands as HFers typically want to +reject spots above 30 MHz and UHF/VHFers want to reject spots below 30 MHz.  Examples of Bandmode filters are:

+ +

 

+ +

Send +only 20 meter spots

+ +

SET/FILTER +BANDMODE/PASS 20-CW,20-RTTY,20-SSB

+ +

         

+ +

Send +only 20 meter and 40 meter CW spots

+ +

SET/FILTER +BANDMODE/PASS 20-CW,40-CW

+ +

 

+ +

Send +everything but 6 meter spots

+ +

SET/FILTER +BANDMODE/REJECT 6-CW,6-SSB,6-FM

+ +

 

+ +

Send +everything but VHF, UHF and Microwave spots

+ +

SET/FILTER +BANDMODE/REJECT VHF,UHF,MW

+ +

 

+ +

Show +only VHF, UHF and Microwave spots

+ +

SET/FILTER +BANDMODE/PASS VHF,UHF,MW

+ +

 

+ +

Show +all spots, turn off BandMode filters

+ +

SET/FILTER +BANDMODE/OFF

+ +

 

+ +

You can examine +you current CTY/State filters with the following commands:

+ +

SHOW/FILTER +BANDMODE

+ +

 

+ +

2.0.2 Needs Filters

+ +

Needs filters +are used to set the various country needs of the user.  If the first character in the data is a +"+", the data is appended to the needs list, otherwise the existing +needs list is overwritten.  Country +prefixes are taken from the ARRL CTY list.

+ +

 

+ +

User +needs can be set on each of the three operating modes of CW, SSB and RTTY. Needs entries +are overwritten unless the data is proceeded with a "+" as shown in +the CW example below.  User country needs are set as follows:

+ +

SET/FILTER +NEEDS/SSB 3D2/r,3Y/b,BV9P,JD/o,JD/m

+ +

SET/FILTER +NEEDS/RTTY R1MV,SV5,T33,ZK1/n

+ +

SET/FILTER +NEEDS/CW R1MV,SV5,T33,ZK1/n

+ +

SET/FILTER +NEEDS/CW +R1FJ,VP8/h,JY,ZS8,VU4,VU7

+ +

 

+ +

You can +activate and deactivate the filtering of spots by need by using the following +commands:

+ +

SET/FILTER +NEEDS/ON

+ +

SET/FILTER +NEEDS/OFF

+ +

 

+ +

You can examine +you current CTY/State filters with the following commands:

+ +

SHOW/FILTER +NEEDS

+ +

 

+ +

You can also +query the needs database looking at needs of other stations or a specific country +prefix. You may also specify a mode qualifier (CW, SSB, RTTY) to just show +needs for that mode. Examples are: 

+ +

 

+ +

Show the needs of another station.

+ +

SH/Need AB5K

+ +

 

+ +

Show the needs on a specific mode for +another station.

+ +

SH/Need/SSB +AB5K

+ +

 

+ +

Show all stations needing the Marshal +Islands (V73)

+ +

SHow/NEed V7*

+ +

 

+ +

The “*” at the +end of the call tells ARC to look up the prefix from the call and use the +prefix in displaying the needs.

+ +

 

+ +

2.0.3 Country Filters

+ +

Users can also +filter spots based on the country of the spot.   Examples are:

+ +

Show all spots +except for US spots

+ +

SET/FILTER +DX/REJECT K

+ +

 

+ +

Show all spots +except for US, Mexico and Canada

+ +

SET/FILTER +DX/REJECT K,XE,VE

+ +

 

+ +

Show only US, +Mexico and Canada spots

+ +

SET/FILTER +DX/PASS K,XE,VE

+ +

 

+ +

Show all spots +regardless of their country (DX CTY filter off)

+ +

SET/FILTER +DX/OFF

+ +

 

+ +

You can examine +you current CTY/State filters with the following commands:

+ +

SHOW/FILTER DX

+ +

 

+ +

 

+ +

3.0 +Other Commands

+ +

 

+ +

Upload/User command - The Upload/User allow the user to execute a +pre-set number of commands when the user logs into the system.  The Upload/User commands are sent to the +node via email.  The user creates an +email message addressed to the node (or nodes) he connects to with a subject of +"Upload/User" and a body containing a list of commands he wants +executed when logging into the system.  +Upon receipt of the email, the AR-Cluster node parses the mail message +and enters the commands into the database.  +The next time the user logs into the system, the commands will be +executed.  SSID’s are ignored for this +command.  Sending an empty +"Upload/User" mail message will any clear previous +"Upload/User" commands.

+ +

 

+ +

 

+ +

 

+ +

3.1  AR-Technology Web Site

+ +

For +more information about AR-Cluster and our latest Dxing and contesting +solutions, visit the AR-Technology web site at:

+ +

http:\\ +149.74.21.166

+ +

 

+ +

 

+ +

 

+ +

 

+ +

 

+ +
+ + + + diff --git a/html/adminmanual-1.html b/html/adminmanual-1.html new file mode 100644 index 00000000..e85ba645 --- /dev/null +++ b/html/adminmanual-1.html @@ -0,0 +1,211 @@ + + + + + The DXSpider Administration Manual : Installation (Original version by Iain Phillips, G0RDI) + + + + + +Next +Previous +Contents +
+

1. Installation (Original version by Iain Phillips, G0RDI)

+ +

Last modified: November 1999 by Ian Maude, G0VGS +

+

1.1 Introduction +

+ +

This section describes the installation of DX Spider v1.35 on a +RedHat 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 +DXSpider website. +

+

I am assuming a general knowledge of Linux and its commands. You should know how to use tar and how to edit files using your favourite editor. +

+

The crucial ingredient for all of this is +Perl 5.004.Now I know Perl 5.005 is out and this will almost certainly work with it, but +RedHat 5.1 comes with 5.004. Be Warned, earlier versions of +RedHat do not come with 5.004 as standard, you need to +upgrade

+

In addition to the standard Red Hat distribution you will require the following +CPAN modules: - +

+

+

    +
  • MD5-1.7.tar.gz
    • +
  • Data-Dumper-2.10.tar.gz
    • +
  • FreezeThaw-0.3.tar.gz
    • +
  • MLDBM-2.00.ar.gz
    • +
  • TimeDate-1.8.tar.gz
    • +
  • IO-1.20.tar.tgz
    • +
  • Net-Telnet-3.01.tar.gz +
    • +
+

+

+

Do get the latest versions of these packages and install them but use the above list as the earliest versions usable. +

+

1.2 Preparation +

+ +

I will assume that you have already downloaded the latest tarball of the DXSpider software and are ready to install it. +

+

Login as root and create a user to run the cluster under. UNDER NO CIRCUMSTANCES USE ROOT AS THIS USER!. I am going to use the name sysop. 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. +

+

+

+
+# adduser -m sysop
+
+
+

+

Now set a password for the user ... +

+

+
+# passwd sysop
+# New UNIX password:
+# Retype new UNIX password:
+passwd: all authentication tokens updated successfully
+
+
+

+

1.3 Installing the software +

+ +

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. +

+

+
+# cd ~sysop
+# tar xvfz spider-1.35.tar.gz
+# ln -s ~sysop/spider /spider
+# groupadd -g 251 spider       (or another number)
+
+
+

If you do not have the command groupadd available to you simply add a line in /etc/group by hand. +

+

+
+# vi /etc/group                (or your favorite editor)
+
+
+

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 +

spider:x:251:sysop,g0vgs,root +

+

The next step is to set the permissions on the Spider directory tree and files .... +

+

+
+# chown -R sysop.spider spider
+# find . -type d -exec chmod 2775 {} \;
+# find . -type f -exec chmod 775 {} \;
+
+
+

+

This last step allows various users of the group spider 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. +

+

Finally, you need to fix the permissions on the ax25_call and netrom_call programs. Check where they are with the locate command and alter the permissions with the chmod command like this .. +

+

+
+# chown root ax25_call netrom_call
+# chmod 4775 ax25_call netrom_call
+
+
+

+

1.4 Setting callsigns etc +

+ +

Now login to your machine as the user you created earlier. In my case that user is called sysop. Once logged in, issue the following commands .... +

+

+
+$ cd /spider
+$ mkdir local
+$ mkdir local_cmd
+$ cp perl/DXVars.pm local
+$ cd local
+$ vi DXVars.pm (or your favourite editor)
+
+
+

+

Using the distributed DXVars.pm as a a template, set your cluster callsign, sysop callsign and other user info to suit your own environment. 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 .... +

$myemail = "ianmaude\@btinternet.com"; +

+

There appears to be an extraeneous slash in there. However this has to be there for the file to work so leave it in. +

+

PLEASE USE CAPITAL LETTERS FOR CALLSIGNS +

+

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! +

+

Save the new file and change directory to ../perl .... +

+

+
+$ cd ../perl
+
+
+

+

Now type the following command which creates the basic user file with you as the sysop. +

+

+
+$ create_sysop.pl
+
+
+

+

1.5 Starting up for the first time +

+ +

We can now bring spider up for the first time and see if all is well or not! It should look something like this ... +

+

+
+$ 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 ...
+
+
+

+

If all is well then login on another term or console as sysop and cd to /spider/perl. Now issue the following command ... +

+

+
+$ client.pl
+
+
+

+

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 .... +

+

+
+G0VGS de GB7MBC 19-Nov-1999 2150Z >
+
+
+

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 .... +

+

+
+shutdown
+
+
+

+

and both the cluster and the client should return to Linux prompts. +

+

+Next +Previous +Contents + + diff --git a/html/adminmanual-2.html b/html/adminmanual-2.html new file mode 100644 index 00000000..3f4a7a3f --- /dev/null +++ b/html/adminmanual-2.html @@ -0,0 +1,282 @@ + + + + + The DXSpider Administration Manual : Configuration + + + + + +Next +Previous +Contents +
+

2. Configuration

+ +

2.1 Allowing ax25 connects from users +

+ +

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 ... +

+

+
+default  * * * * * *  - sysop /spider/perl/client.pl client.pl %u ax25
+
+
+

+

2.2 Allowing telnet connects from users +

+ +

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
+
+
+

Then add a line in /etc/inetd.conf like this .... +

+

+
+spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/perl/client.pl login telnet
+
+
+

+

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 .... +

+

+
+killall -HUP inetd
+
+
+

+

+

Now login as sysop and cd spider/perl. You can test that spider is accepting telnet logins by issuing the following command .... +

+

+
+client.pl login telnet
+
+
+

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. +

+

Assuming all is well, then try a telnet from your linux console .... +

+

+
+telnet localhost 8000
+
+
+

+

You should now get the login prompt and be able to login as before. +

+

2.3 Setting up node connects +

+ +

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. +

+

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 ... +

+

+
+set/node gb7baa
+
+
+

+

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. +

+

That is now set, it is as simple as that. To prove it, login on yet another console as sysop and issue the command ... +

+

+
+client.pl gb7baa (using the callsign you set as a node)
+
+
+

+

You should get an initialisation string from DXSpider like this ... +

+

+
+client.pl 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. +

+

Connection scripts

+ +

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:- +

+

+

+        
+#               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]).
+
+

+

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
+        'Connect' ''
+        'Connect' 'c np7'
+        'Connect' 'c gb7dxm'
+        'Connect' ''
+        # you can leave this out if you call the script 'gb7dxm'
+        client gb7dxm ax25
+
+
+

+

+

+

+
+        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
+
+
+

+

Both these examples assume that everything is set up properly at the other end. You will find other examples in the /spider/examples directory. +

+

Starting the connection

+ +

You start the connection, from within a sysop enabled cluster login, by typing in the word connect followed by a script name like this .... +

+

+
+G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
+connection to GB7DJK-1 started
+G0VGS de GB7MBC 13-Dec-1998 2043Z >
+
+
+

This will start a connection using the script called gb7djk-1. You can follow the connection by watching the term or console from where you started cluster.pl. You should see something like this ... +

+

+
+<- 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
+
+
+

+

2.4 Automating things +

+ +

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. +

+

Autostarting the cluster

+ +

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. +

+

Login as root and bring up the /etc/inittab file in your favourite editor. Add the following lines to the file near the end ... +

+

+
+##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
+
+
+

+

This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart it should it crash for any reason. +

+

As root type the command telinit q. DXSpider should start up immediately. You will see the output on tty7 and if you login as sysop you should find everything running nicely. +

+

So far so good, now to automate script connections... +

+

The crontab file

+ +

Login as sysop 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) +

+

+
+# 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')
+
+
+

+

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. +

+

There are probably lots of other things you could use this crontab file for. If you want to know more about it, look at the +DXSpider website at the cron page where it is explained more fully. +

+

+Next +Previous +Contents + + diff --git a/html/adminmanual-3.html b/html/adminmanual-3.html new file mode 100644 index 00000000..638a2680 --- /dev/null +++ b/html/adminmanual-3.html @@ -0,0 +1,112 @@ + + + + + The DXSpider Administration Manual : Hop control and filtering + + + + +Next +Previous +Contents +
+

3. Hop control and filtering

+ +

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). +

+

3.1 Basic hop control +

+ +

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 ... +

+

+
+# 
+# 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,
+                   },
+};
+
+
+

+

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. +

+

You can alter this file at any time, including whilst the cluster is running. If you alter the file during runtime, the command load/hops will bring your changes into effect. +

+

3.2 Isolating networks +

+ +

It is possible to isolate networks from each other on a "gateway" node using the +set/isolate <node call> command. +

+

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. +

+

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. +

+

+

+Next +Previous +Contents + + diff --git a/html/adminmanual.html b/html/adminmanual.html new file mode 100644 index 00000000..efd5f158 --- /dev/null +++ b/html/adminmanual.html @@ -0,0 +1,52 @@ + + + + + The DXSpider Administration Manual + + + + + +Next +Previous +Contents +
+

The DXSpider Administration Manual

+ +

Ian Maude, G0VGS, (ian@lurpac.lancs.ac.uk)

Version 0.1 November 1999 +

+A reference for SysOps of the DXSpider DXCluster program. +
+

+

1. Installation (Original version by Iain Phillips, G0RDI)

+ + +

+

2. Configuration

+ + +

+

3. Hop control and filtering

+ + +
+Next +Previous +Contents + + diff --git a/html/sysop_t.html b/html/sysop_t.html new file mode 100644 index 00000000..2b473564 --- /dev/null +++ b/html/sysop_t.html @@ -0,0 +1,41 @@ + + + + Sysop Command Reference + + + + + + +
+

Sysop Command Reference

+
+ + + +
Dirk Koopman G1TLH
+

+ + +Last modified: Wed Nov 17 17:36:58 GMT 1999 + +

Introduction

+ +

This is the list of sysop commands currently available within the DX Spider DX Cluster system.

+

It is automatically generated from the system help files.

+ +

The Commands

+ + + + +

 

+

+

+ + Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved
+ + $Id$ + + diff --git a/html/user_en_t.html~ b/html/user_en_t.html~ new file mode 100644 index 00000000..e2689401 --- /dev/null +++ b/html/user_en_t.html~ @@ -0,0 +1,41 @@ + + + + User Command Reference + + + + + + +
+

User Command Reference

+
+ + + +
Dirk Koopman G1TLH
+

+ + +Last modified: Wed Nov 17 16:27:21 GMT 1999 + +

Introduction

+ +

This is the list of user commands currently available within the DX Spider DX Cluster system.

+

It is automatically generated from the system help files.

+ +

The Commands

+ + + + +

 

+

+

+ + Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved
+ + $Id$ + + diff --git a/html/user_t.html~ b/html/user_t.html~ new file mode 100644 index 00000000..71858ffe --- /dev/null +++ b/html/user_t.html~ @@ -0,0 +1,62 @@ + + + + Local extensions + + + + + + +
+

Local extensions

+
+ + + +
Dirk Koopman G1TLH
+

+ + +Last modified: Mon Dec 28 22:43:23 GMT 1998 + +

Introduction

+ + The DXSpider system is designed to be extensible, to facilitate experimentation and + self-training in both Amateur Radio and Programming. + +

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. + +

What is it?

+ + The mechanism I have chosen to allow people to do their own thing, is a perl .pm file called + Local.pm. 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. + +

Where is it?

+ + The template is /spider/perl/Local.pm. This file should be + copied into /spider/local and then modified to your taste. + +

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! + +

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! + + +

 

+

+

+ + Copyright © 1998 by Dirk Koopman G1TLH. All Rights Reserved
+ + $Id$ + + diff --git a/src/client.c b/src/client.c index 98f5a668..382c852b 100644 --- a/src/client.c +++ b/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];