1AX25D.CONF(5) Linux Programmer's Manual AX25D.CONF(5)
2
6 ax25d.conf - ax25d configuration file.
7
9 Ax25d.conf controls the functioning of ax25d. Its purpose is to spec‐
10 ify on which ports to listen on, which applications are available, and
11 to whom they are available to. The configuration file is common to both
12 AX.25, NET/ROM and Rose and their is similarity between the two parts
13 of the file.
14 The general layout for an entry for a given port is as follows:
16 interface control
18 callsign entry 1
19 .
20 .
21 callsign entry n
22 The interface control line determines which port and callsigns apply to
24 the following callsign entry lines, until the next interface control is
25 read. There are four different variants of the interface control line:
26 1. [AX.25 Port Name]
28 2. [Callsign VIA AX.25 Port Name]
29 3. <NET/ROM Port Name>
30 4. {Callsign VIA Rose Port Name}
31 Version 1 allows the following callsign entry lines to listen on the
33 AX.25 port specified by the AX.25 port name using the default callsign
34 of that AX.25 port.
35 Version 2 allows the following callsign entry lines to listen on the
37 AX.25 port specified by the AX.25 port name using the callsign speci‐
38 fied instead of the default callsign of that AX.25 port. Specifying a
39 * for the AX.25 port name allows the following callsign entries to be
40 valid for all the operating AX.25 ports using the callsign specified.
41 VIA can be abbreviated to just V. If the callsign has an asterisk
42 appended to it then the system will be listening on the port with the
43 callsign, but as a pseudo-digipeater instead of being the normal desti‐
44 nation callsign.
45 Version 3 allows the following callsign entry lines to listen on the
47 NET/ROM port specified by the NET/ROM port name using the default call‐
48 sign of that NET/ROM port.
49 Version 4 allows the following callsign entry lines to listen on the
51 Rose port using the specified Rose port name using the callsign speci‐
52 fied as the service access point (SAP). A * may be specified for a
53 callsign to allow matching to any incoming Call Requests with any SAP.
54 The callsign entry lines have a similar layout for both AX.25, NET/ROM
56 and Rose, the layout is:
57 peer window t1 t2 t3 idle n2 mode uid exec args...
59 All values must be entered for all entries even when they are not used
61 (ie window for NET/ROM, just enter a * instead), The meanings of each
62 of the fields is given below. All timings apart from the idle value are
63 given in seconds, the idle values is given in minutes.
64 peer This specifies the callsign of the remote end of the
66 connection that should have the following parameters
67 and executable set up for them. The syntax of the peer
68 argument is explained below.
69 window This sets the the value of the window size, if a value
71 of * is entered in this field then the default value
72 for the port is taken from the “parameters” entry (see
73 below) or lacking such an entry, the kernel default
74 value is used. This entry is used by AX.25 but not by
75 NET/ROM or Rose.
76 t1 This sets the the value of the T1 timer, if a value of
78 * is entered in this field then the default value for
79 the port is taken from the “parameters” entry (see
80 below) or lacking such an entry, the kernel default
81 value is used. This entry is used by both AX.25 and
82 NET/ROM but not by Rose.
83 t2 This sets the the value of the T2 timer, if a value of
85 * is entered in this field then the default value for
86 the port is taken from the “parameters” entry (see
87 below) or lacking such an entry, the kernel default
88 value is used. This entry is used by both AX.25 and
89 NET/ROM but not by Rose.
90 t3 This sets the the value of the T3 timer, if a value of
92 * is entered in this field then the default value for
93 the port is taken from the “parameters” entry (see
94 below) or lacking such an entry, the kernel default
95 value is used. This entry is used by AX.25 but not by
96 NET/ROM or Rose.
97 idle This sets the the value of the idle timer, if a value
99 of * is entered in this field then the default value
100 for the port is taken from the “parameters” entry (see
101 below) or lacking such an entry, the kernel default
102 value is used.
103 n2 This sets the the value of the N2 counter, if a value
105 of * is entered in this field then the default value
106 for the port is taken from the “parameters” entry (see
107 below) or lacking such an entry, the kernel default
108 value is used. This entry is used by both AX.25 and
109 NET/ROM but not by Rose.
110 mode This is a set of flags that control the various prop‐
112 erties associated with the incoming connection. The
113 flags are single letters, may be in either upper or
114 lower case, and there may not be any spaces between
115 them. If no flags are to be specified either a 0, - or
116 a * must be entered instead. The valid mode flag let‐
117 ters are:
118 D Do not allow connections that have passed via any
120 digipeaters. AX.25 only.
121 L Do not allow this station to connect, they are
123 Locked out.
124 N Check that the NET/ROM neighbour is allowed, cur‐
126 rently unused.
127 Q Do not make an entry into the log file for this
129 connection.
130 V Validate the callsign of the incoming connection,
132 currently unused.
133 uid This is the userid that the following command should
135 run under when executing.
136 exec This is the executable that should be executed when an
138 incoming connection matches the criteria of both the
139 interface control and the callsign entry .
140 args... These are the optional arguments that are passed to
142 the executable. All of the arguments are passed liter‐
143 ally apart from the following:
144 %d The name of the port that the connection is on.
146 %U The username (callsign) of the remote station in
148 upper case without the SSID.
149 %u The username (callsign) of the remote station in
151 lower case without the SSID.
152 %S The username (callsign) of the remote station in
154 upper case with the SSID.
155 %s The username (callsign) of the remote station in
157 lower case with the SSID.
158 %P The nodename of the remote station in upper case
160 without the SSID. This is only valid under
161 NET/ROM and Rose, under AX.25 a % is substituted
162 instead.
163 %p The nodename of the remote station in lower case
165 without the SSID. This is only valid under
166 NET/ROM and Rose, under AX.25 a % is substituted
167 instead.
168 %R The nodename of the remote station in upper case
170 with the SSID. This is only valid under NET/ROM
171 and Rose, under AX.25 a % is substituted instead.
172 %r The nodename of the remote station in lower case
174 with the SSID. This is only valid under NET/ROM
175 and Rose, under AX.25 a % is substituted instead.
176 %% A %.
178 The peer argument is dependant upon whether AX.25, NET/ROM or Rose is
180 being used. There are five formats of this argument:
181 1. default
183 2. parameters
184 3. callsign
185 4. callsign@node
186 5. @node
187 The first version is used by AX.25, NET/ROM and Rose to specify that
189 all callsigns on a given port are to be matched. The default line is
190 usually the last of the callsign entry lines, so that more specific
191 entries may have the chance to be matched first.
192 The second version is not a callsign entry that is used by any incoming
194 connections. It is a means to specify default values for parameters
195 such as Window, T1, T2, T3, Idle and N2. It is used for both AX.25,
196 NET/ROM and Rose.
197 The third version is used by both AX.25, NET/ROM and Rose to specify
199 the callsign of the remote station to match the callsign entry line. If
200 no SSID is specified then the callsign will be matched with any that
201 has the same callsign and any SSID. Specifying an SSID causes the call‐
202 sign to be matched exactly. In the case of NET/ROM and Rose this entry
203 does not specify which node the originating callsign comes from.
204 The fourth version is used by NET/ROM and Rose to specify the callsign
206 of the remote station and the remote node to match the callsign entry
207 line. If no SSID is specified in the callsign section then the callsign
208 will be matched with any that has the same callsign and any SSID. Spec‐
209 ifying an SSID causes the callsign to be matched exactly.
210 The fifth version is used by NET/ROM and Rose to specify only the
212 address of the remote node to match the callsign entry line. This entry
213 will mean that all remote users at the given node will match the entry.
214 Comments may be embedded in the configuration file by placing a # in
216 the first column.
217 ax25d can now honour AX.25 TCP/IP mode-VC connections in a special way.
219 Therefore, a new port specific option "parameters_extAX25" is avail‐
220 able, with the following options, which are seperated by space.
221 parameters_extAX25
223 VC-debug
224 VC-reject-login|VC-wait-login|VC-login-ok
225 VC-disc-on-linkfailure-msg, VC-send-failure-msg, VC-log-connec‐
226 tions
227 Recommended settings in ax25d.conf:
228 parameters_extAX25 VC-wait-login VC-disc-on-linkfailure-msg VC-
229 log-connections
230 or
231 parameters_extAX25 VC-reject-login VC-send-failure-msg VC-log-
232 connections
233
236 /etc/ax25/ax25d.conf
237
239 ax25(4), netrom(4), rose(4), axports(5), nrports(5), rsports(5),
240 ax25d(8).
241Linux 17 January 1997 AX25D.CONF(5)