Here is the manual in english. It is not complete but is provided so others can help with added features or corrections to my work. Some day I will run it through LaTeX and make it pretty... ----------------------------------------------------------------------- DXNET Manual 27 Oct 1997 K5DI Modified to reflect the latest changes based on information about version Dx980516 on June 20, 1998 INTRODUCTION: This manual covers the installation, setup and use of the DX Cluster software called DXNET obtained from http//www.f6fbb.org originally as an Alfa release. The installation is very simple. The setup is simple but time consuming. Using it is very simple! Once you get connected to the DX Cluster Network you sit back and enjoy. The current Alfa version that I am running has the basic Cluster features of send/receive DX spots, Announcements local and Cluster wide, and talk. It also has a WWV spot data base and it has a local packet bulletin board data base. It makes a useful DX Cluster for my city. INSTALLATION: When you have down-loaded the file put it in your /usr/local directory. It is a .tgz file that will make a /dxnet directory off /usr/local. Use: tar xvfz dx971025.tgz (be sure to use the proper file name) This will place all the files you need in a directory tree. Get to your /dxnet directory and with an editor bring up the file dxnet.sh. Edit the file until it looks like this: #!/bin/sh BASEDIR=/usr/local/dxnet echo "Add -v option for the verbose mode" echo "Changing directory to $BASEDIR" cd $BASEDIR .. .. Here is the directory tree you made with tar. It is not complete as shown but shows what you need now: Directory dxnet: dxnet Main program dxnet.sh [-v] Shell script to run the program (endless loop) Directory dxnet/language: Danish.hlp.example* english.txt* luxembou.hlp.example* danish.hlp.example* english.txt.example* luxembou.txt.example* danish.txt.example* french.hlp.example* russian.hlp.example* english.hlp* french.mot.example* russian.txt.example* english.hlp.example* french.txt.example* span_sa.hlp.example* english.mot* german.hlp.example* span_sa.txt.example* english.mot.example* german.txt.example* Directory dxnet/script: f6krq_ax.fwd.example f6krq_rs.fwd.example* wu3v.fwd f6krq_nr.fwd.example* wa5pie.fwd Directory dxnet/system: bin/ dxtodo.dat language.dat.example* dxnet.cfg dxtodo.dat.example local.dat.example* dxnet.cfg.example language.dat* Directory dxnet/system/bin: announce.bin dx.bin maxusers.bin.example announce.bin.example dx.bin.example users.bin dirmes.bin hops.bin users.bin.example dirmes.bin.example hops.bin.example wwv.bin dirmes.old.example maxusers.bin STARTUP: CD to your ~system/ directory and with your editor open a new file dxnet.cfg. In this file put 2 lines the first being set/call k5di-5 and the second set/node +wa5pie. Of course use your call for your cluster and your adjacent clusters call-sign. Be sure to put a + in front of the set/node call-sign. Now put some more lines in dxnet.cfg that explain what you have set up on your computer. I have the ax25-util set up and have 2 ax.25 ports named ax0 and ax1, and a netrom port I call netrom. These names are from the /etc/ax25/axports and nrports files. To get DxNet to use these ports add the line: set/port ax0 ax1 netrom When DxNet is started it reads dxnet.cfg and if you start it with dxnet.sh -v you will see the data from dxnet.cfg being read into the main program. If there is a problem you will see it. Now make a dxtodo.dat file with your editor and put the following line as the first line: ???5 c wa5pie (use the call of your adjacent cluster. Under no condition make this call longer than 8 characters)! Save this file. Now change to the /usr/local/dxnet/script directory. There are several examples of what to do Here is my file for getting to wa5pie which works fine. The file name is wa5pie.fwd: WA5PIE .C netrom elpdx +to ----------------------- Since the netrom node ELPDX exists on my ax25 system I just call that node using netrom. .C netrom elpdx does this. The +to tells me that when I see it the connection was successful. Look at the examples for more complex conditions. Now your ready to try out your DxNet. I wrote a simple bash file to start the program. This way I don't need to remember how to start it. The file "startdx" looks like this: #! /bin/sh # Starts DxNet /usr/local/dxnet/dxnet.sh -v Of course you need to make this file executable and do that with chmod 755 startdx. OPERATION: Watch your eterm window that you started Dxnet in. You should see your system connect to the node you put in to dxnet.cfg and the dx spots and other information begin to flow. This window to your system can be used by you the sysop to enter set/xxxx commands and messages. You can read messages to you or to anyone using this window. Of course you see the DX spots coming in. Type sh/users and it will show you who is using your local Cluster. Packet BBS: There is a local mailbox that is working just fine. As of this version forwarding of messages to distant nodes is not finished. There are plans to finish this part of the system in the near future. To send a message to a user of your cluster, use the command s w5raf and you will be asked for a title and then you can finish the message. The message is placed in the ~mail/ directory as a file. The title of the message is held in the binary file ~bin/dirmes.bin. So to read the entire message you need to use: r 3 assuming the message is message 3. COMMANDS: SET/BLACK Stops call-signs connecting to cluster example: set/black +NOCALL +N5BKL SHow/Announce Announcement list SHow/CLuster Short cluster configuration SHow/Configuration Cluster configuration SHow/DX Dx spot list SHow/LANGuage Language list SHow/Users Local cluster configuration SET/Here You're here SET/HOME Set your home cluster SET/LANGuage Set the language SET/LOCAtor Set your locator SET/NAME Set your first name SET/NOHere You're away SET/QTH Set your QTH Announce Send a local announcement Announce/Full Send a cluster-wide announcement Bye Quit DX Send DX Information See an information message about the server Talk Send a talk to an user SH/DX This command shows the list of the last dx spots. As you use the software a number of data files will be made in the /usr/local/dxnet/system/bin directory. They are where the announcement and Dx-spot data and user data are stored. The messages are stored in the ~mail/ directory and all these files will grow with time. There is a program for DOS to kill these files but none in the Linux version. It is up to you to set something up. I use cron to do timed things on this computer so it is no problem, yet. Joe editor in Unix end at 1445 31 Oct 97 end at 1225 21 Jun 98