Ax25 server software

There is a difference in the libarier. After a break I start again. A fresh install Raspbian Buster with desktop and recommended software there are a few packages missing : autogen autoconf libtool Script is succesfull eeindigd: Now it is time to compile and install AX. If this is a first install of AX. You must be logged in to post a comment. This site uses Akismet to reduce spam. Learn how your comment data is processed. Skip to content Menu Secondary menu. This example is a standalone C program that will listen for a connection request on the radio interface, exchange data, then close the connection.

It then terminates. Again this is hard-coded to run on VK7NTK-2 , because that is the callsign used when choosing the interface to which to bind. Like the client there are three steps that must be performed to accept a connection. As before the first is to create an AX. This is the radio that will be listening for connections. The third step is to call accept.

This will wait for an incoming connection. Then I can simply use read and write to exchange data. It looks like this on the server:. It looks like this on the client using axcall :. Ham Radio operators review new sites every day since , for potential inclusion in the Directory, and to evaluate the best place to list them.

Packet Radio Software for packet radio use. Operating Modes Operating Aids. CB Radio Antique Radio. Home : Software : Packet. Packet and Digital. Packet Radio. The access methods allowed are: method description ampr User is telnet connected from an amprnet address This allows you to determine what AX.

The third field contains the port name if you are using this facility. This is useful only for AX. This might be useful to help protect specially configured users who have high authority levels. If the fourth field is set then its value will be the password that will be accepted. The permissions field is coded as a bit field, with each facility having a bit value which if set allows the option to be used and if not set prevents the facility being used. The list of controllable facilities and their corresponding bit values are: value description 1 Login allowed.

To code the permissions value for a rule, simply take each of the permissions you want that user to have and add their values together. The resulting number is what you place in field five. A sample nodes. Configuring node to run from ax25d The node program would normally be run by the ax25d program. In my configuration I wanted users to have a choice of either connecting to the node or connecting to other services.

For example, given the ax25d configuration presented above, I want to configure node so that all users who connect to VK2KTJ-1 are given the node. Configuring node to run from inetd If you want users to be able to telnet a port on your machine and obtain access to the node you can go this fairly easily.

The first thing to decide is what port users should connect to. In this example I've arbitrarily chosen port , though Tomi gives details on how you could replace the normal telnet daemon with the node in his documentation. You need to modify two files. Configuring axspawn. The axspawn program is a simple program that allows AX.

It may be invoked from the ax25d program as described above in a manner similar to the node program. The default is to not wait. Any individual host configurations that follow this line will have the axspawn program run when they connect. This is usually ax25 or guest. Configuring the pms The pms program is an implementation of a simple personal message system.

It was originally written by Alan Cox. At present it is still very simple, supporting only the ability to send mail to the owner of the system and to obtain some limited system information but Dave is working to expand its capability to make it more useful.

After that is done there are a couple of simple files that you should create that give users some information about the system and then you need to add appropriate entries into the ax25d. The file is a simple text file, any text you include in this file will be sent to users. Associate AX. When a connected user sends mail to an AX.

This is described in a section of its own. Adding the pms to your ax25d. There is one small thing you need to think about though. Dave has added command line arguments to the PMS to allow it to handle a number of different text end-of-line conventions. So, for example, if you wanted to add an entry that meant that the default action for a connection received on an AX. Check the man page for what you should specify for other connection methods.

Test the PMS. You can do all the things connected users can. Additionally you might try getting some other node to connect to you to confirm that your ax25d. They are very simple programs designed to be called from ax25d to automate network connections to remote hosts.

They may of course be called from a number of other places such as shell scripts or other daemons such as the node program. They are like a very simple call program. They don't do any meddling with the data at all, so the end of line handling you'll have to worry about yourself. Let's start with an example of how you might use them.

Imagine you have a small network at home and that you have one linux machine acting as your Linux radio gateway and another machine, lets say a BPQ node connected to it via an ethernet connection.

Normally if you wanted radio users to be able to connect to the BPQ node they would either have to digipeat through your linux node, or connect to the node program on your linux node and then connect from it. There are all sorts of other possible configurations that you might try. One amateur has used this utility to make connections to a remote BBS easier.

Normally the users would have to manually enter a long connection string to make the call so he created an entry that made the BBS appear as though it were on the local network by having his ax25d proxy the connection to the remote machine. The Linux Rose implementation does not support this capability in the kernel, but there are two application programs called rsuplnk and rsdwnlnk which perform this function.

Normally you would configure this entry to be the default behaviour for incoming Rose connections. For example you might have Rose listeners operating for destinations like NODE-0 or HEARD-0 that you wish to handle locally, but for all other destination calls you may want to pass them to the rsdwnlink command and assume they are AX. This configuration would allow an AX. There are a number of situations where it is highly desirable to associate a callsign with a linux user account.

One example might be where a number of amateur radio operators share the same linux machine and wish to use their own callsign when making calls. Another is the case of PMS users wanting to talk to a particular user on your machine.

We've mentioned it once already in the PMS section, but I'm spelling it out here to be sure you don't miss it. You make the association with the axparms command. An example looks like: axparms -assoc vk2ktj terry This command associates that AX. So, for example, any mail for vk2ktj on the pms will be sent to Linux account terry. Remember to put these associations into your rc file so that they are available each time your reboot. Note you should never associate a callsign with the root account as this can cause configuration problems in other programs.

These files are normally used by the AX52 utilities, but they are plainly formatted so you may be interested in reading them. The format is fairly easily understood so I don't think much explanation will be necessary. These can can AX. These might be listening for a connection, or active sessions.

Probably the biggest advantage of using the kernel based implementations of the amateur packet radio protocols is the ease with which you can develop applications and programs to use them.

While the subject of Unix Network Programming is outside the scope of this document I will describe the elementary details of how you can make use of the AX. The address families. Network programming for AX. The major differences being the address families used, and the address structures that need to be mangled into place. The address family names for AX.

The header files. Simple top level skeletons would look something like the following: For AX. Callsign mangling and examples. You can write your own of course if you wish. The source code for them is included in the AX25 utilities package. If you spend a little time working with those you will soon see that ninety percent of the work is involved in just getting ready to open the socket.

Actually making the connection is easy, the preparation takes time. The example are simple enough to not be very confusing. If you have any questions, you should feel to direct them to the linux-hams mailing list and someone there will be sure to help you. Following are examples of the most common types of configurations.

These are guides only as there are as many ways of configuring your network as there are networks to configure, but they may give you a start. This is the type of configuration I use at home. I arranged to have a suitable block of addresses allocated to me that I could capture in a single route for convenience and I use these on my Ethernet LAN. Your local IP coordinator will assist you in doing this if you want to try it as well.

The following configuration is the actual one for my linux router on my network at home:. Network I needn't have done so, I could have easily used IPIP encapsulated gateway configuration.

The new tunnel driver supports multiple encapsulated routes and makes the older ipip daemon obsolete. A typical configuration would look similar to the following. This is why it now supports multiple routes per interface. In this example both the sl0 and the tunl0 devices have been configured with the IP address of the radio port.

This is done so that the remote gateway sees the correct address from your gateway in encapsulated datagrams sent to it. This is included below. The source file must be in the NOS route command format.

Setting this parameter to an appropriate value improves the performance of your radio link. The new tunnel-munge script:! Usage: Gateway file on stdin, Linux route format file on stdout. Failure to do so will cause serious routing loops. Make sure this is correct for your system.

Encapsulation of AX. Mike Westerhof wrote an implementation of an AX. The axutils package includes a marginally enhanced version of it for Linux. To distinguish IP datagrams containing AX. This process is described in RFC The ax25ipd program included in the axutils package presents itself as a program supporting a KISS interface across which you pass AX.

AXIP configuration options. The ax25ipd program has two major modes of operation. In "tnc" mode the daemon is treated as though it were a kiss TNC, you pass KISS encapsulated frames to it and it will transmit them, this is the usual configuration. In "digipeater" mode, you treat the daemon as though it were an AX.

There are subtle differences between these modes. In the configuration file you configure "routes" or mappings between destination AX. Each route has options which will be explained later. Other options that are configured here are the tty that the ax25ipd daemon will open and its speed usually one end of a pipe what callsign you want to use in "digipeater" mode beacon interval and text whether you want to encapsulate the AX. If you selected tnc mode, the callsign is currently optional, but this may change in the future!

Any of the addresses listed will be forwarded to any of the routes flagged as broadcast capable routes. Some notes about the routes and route flags The "route" command is where you specify where you want your AX. When the ax25ipd daemon receives a packet from its interface, it compares the destination callsign with each of the callsigns in its routing table.

If if finds a match then the ax. There are two flags you can add to any of the route commands in the ax25ipd. The two flags are: b traffic with a destination address matching any of those on the list defined by the "broadcast" keyword should be transmitted via this route. The broadcast flag is very useful, as it enables informations that is normally destined for all stations to a number of AXIP destinations.