SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

BotDetect - Real-Time Bot Detection API
 
 

MAN page from Mandrake Other ax25-utils-2.1.42a-3.i386.rpm

AX25D.CONF

Section: Linux Programmer's Manual (5)
Updated: 17 January 1997
Index 

NAME

ax25d.conf - ax25d configuration file. 

DESCRIPTION

Ax25d.confcontrols the functioning ofax25d.Its purpose is to specify on which ports to listen on, which applicationsare available, and to whom they are available to. The configuration file iscommon to both AX.25, NET/ROM and Rose and their is similarity between thetwo parts of the file.

The general layout for an entry for a given port is as follows:

interface control
callsign entry 1

 .

 .
callsign entry n

Theinterface controlline determines which port and callsigns apply to the followingcallsign entrylines, until the nextinterface controlis read. There are four different variants of theinterface controlline:

1. [AX.25 Port Name]
2. [Callsign VIA AX.25 Port Name]
3. <NET/ROM Port Name>
4. {Callsign VIA Rose Port Name}

Version 1 allows the followingcallsign entrylines to listen on the AX.25 port specified by the AX.25 port name using thedefault callsign of that AX.25 port.

Version 2 allows the followingcallsign entrylines to listen on the AX.25 port specified by the AX.25 port name using thecallsign specified instead of the default callsign of that AX.25 port.Specifying a * for the AX.25 port name allows the followingcallsign entriesto be valid for all the operating AX.25 ports using the callsign specified. VIAcan be abbreviated to just V. If the callsign has an asterisk appended to itthen the system will be listening on the port with the callsign, but as apseudo-digipeater instead of being the normal destination callsign.

Version 3 allows the followingcallsign entrylines to listen on the NET/ROM port specified by the NET/ROM port name usingthe default callsign of that NET/ROM port.

Version 4 allows the followingcallsign entrylines to listen on the Rose port using the specified Rose port name usingthe callsign specified as the service access point (SAP). A * may bespecified for a callsign to allow matching to any incoming Call Requestswith any SAP.

Thecallsign entrylines have a similar layout for both AX.25, NET/ROM and Rose, the layout is:

peer window t1 t2 t3 idle n2 mode uid exec args...

All values must be entered for all entries even when they are not used (iewindow for NET/ROM, just enter a * instead), The meanings of each of thefields is given below. All timings apart from the idle value are given inseconds, the idle values is given in minutes.

peer
This specifies the callsign of the remote end of the connection that shouldhave the following parameters and executable set up for them. The syntax ofthe peer argument is explained below.
window
This sets the the value of the window size, if a value of * is entered in thisfield then the default value for the port is taken from the "parameters"entry (see below) or lacking such an entry, the kernel default value is used.This entry is used by AX.25 but not by NET/ROM or Rose.
t1
This sets the the value of the T1 timer, if a value of * is entered in thisfield then the default value for the port is taken from the "parameters"entry (see below) or lacking such an entry, the kernel default value is used.This entry is used by both AX.25 and NET/ROM but not by Rose.
t2
This sets the the value of the T2 timer, if a value of * is entered in thisfield then the default value for the port is taken from the "parameters"entry (see below) or lacking such an entry, the kernel default value is used.This entry is used by both AX.25 and NET/ROM but not by Rose.
t3
This sets the the value of the T3 timer, if a value of * is entered in thisfield then the default value for the port is taken from the "parameters"entry (see below) or lacking such an entry, the kernel default value is used.This entry is used by AX.25 but not by NET/ROM or Rose.
idle
This sets the the value of the idle timer, if a value of * is entered inthis field then the default value for the port is taken from the"parameters" entry (see below) or lacking such an entry, the kerneldefault value is used.
n2
This sets the the value of the N2 counter, if a value of * is entered in thisfield then the default value for the port is taken from the "parameters"entry (see below) or lacking such an entry, the kernel default value is used.This entry is used by both AX.25 and NET/ROM but not by Rose.
mode
This is a set of flags that control the various properties associated withthe incoming connection. The flags are single letters, may be in eitherupper or lower case, and there may not be any spaces between them. If noflags are to be specified either a 0, - or a * must be entered instead. Thevalid mode flag letters are:
D
Do not allow connections that have passed via any digi-peaters. AX.25 only.
L
Do not allow this station to connect, they are Locked out.
N
Check that the NET/ROM neighbour is allowed, currently unused.
Q
Do not make an entry into the log file for this connection.
V
Validate the callsign of the incoming connection, currently unused.
uid
This is the userid that the following command should run under whenexecuting.
exec
This is the executable that should be executed when an incoming connectionmatches the criteria of both theinterface controland thecallsign entry.
args...
These are the optional arguments that are passed to the executable. All ofthe arguments are passed literally apart from the following:
%d
The name of the port that the connection is on.
%U
The username (callsign) of the remote station in upper case without the SSID.
%u
The username (callsign) of the remote station in lower case without the SSID.
%S
The username (callsign) of the remote station in upper case with the SSID.
%s
The username (callsign) of the remote station in lower case with the SSID.
%P
The nodename of the remote station in upper case without the SSID.This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead.
%p
The nodename of the remote station in lower case without the SSID.This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead.
%R
The nodename of the remote station in upper case with the SSID.This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead.
%r
The nodename of the remote station in lower case with the SSID.This is only valid under NET/ROM and Rose, under AX.25 a % is substituted instead.
%%
A %.

Thepeerargument is dependant upon whether AX.25, NET/ROM or Rose is being used. There arefive formats of this argument:

1. default
2. parameters
3. callsign
4. callsignAATTnode
5. @node

The first version is used by AX.25, NET/ROM and Rose to specify that all callsignson a given port are to be matched. The default line is usually the last of thecallsign entrylines, so that more specific entries may have the chance to be matchedfirst.

The second version is not acallsign entrythat is used by any incoming connections. It is a means to specify defaultvalues for parameters such as Window, T1, T2, T3, Idle and N2. It is used forboth AX.25, NET/ROM and Rose.

The third version is used by both AX.25, NET/ROM and Rose to specify the callsign ofthe remote station to match thecallsign entryline. If no SSID is specified then the callsign will be matched with anythat has the same callsign and any SSID. Specifying an SSID causes thecallsign to be matched exactly. In the case of NET/ROM and Rose this entry does notspecify which node the originating callsign comes from.

The fourth version is used by NET/ROM and Rose to specify the callsign of the remotestation and the remote node to match thecallsign entryline. If no SSID is specified in the callsign section then the callsign willbe matched with any that has the same callsign and any SSID. Specifying anSSID causes the callsign to be matched exactly.

The fifth version is used by NET/ROM and Rose to specify only the address of theremote node to match thecallsign entryline. This entry will mean that all remote users at the given node willmatch the entry.

Comments may be embedded in the configuration file by placing a # in thefirst column. 

FILES

/etc/ax25/ax25d.conf 

SEE ALSO

ax25(4),netrom(4),rose(4),axports(5),nrports(5),rsports(5),ax25d(8).


 

Index

NAME
DESCRIPTION
FILES
SEE ALSO

This document was created byman2html,using the manual pages.
 
ICM Bot detect detector