1AX25RTD.CONF(5)            Linux Programmer's Manual           AX25RTD.CONF(5)
2
3
4

NAME

6       ax25rtd.conf - ax25 routing daemon configuration file
7

SYNOPSIS

9       /etc/ax25/ax25rtd.conf
10

DESCRIPTION

12       The  file /etc/ax25/ax25rtd.conf is the configuration file for ax25rtd.
13       The parameters of the options shown here are the default values  except
14       the ones marked with (example)
15
16       ax25-maxroutes 4096
17
18       ip-maxroutes   4096
19              The  maximum  size  of  the  three  lists / caches. On overflow,
20              ax25rtd will substitute the oldest entry with the new one.
21
22       iproute2-table radio
23
24              name ("radio") of the kernel routing table. This is an  advanced
25              routing  feature. If you do not need it, just leave this setting
26              as is.
27
28              The current implementation  depends on iproute2 (anyone like  to
29              code it directly?).
30
31              If not set or empty, routes are set in the normal, default, man‐
32              ner.  Please configure /etc/iproute2/rt_protos with
33
34                44      ax25rtd
35
36              and /etc/iproute2/rt_tables with
37
38                210     radio
39
40              where "radio" is the name of the table, (for  the  configuration
41              example above).
42
43              This option is disabled by default.
44
45       ip-encaps-dev ipax0
46              This option was for a patched kernel of the 2.2.x series. Multi‐
47              ble interfaces were aggregated to one interface when sending  IP
48              frames. This option is disabled by default.
49
50       [1k2]
51              This  marks the beginning of per-port definitions. Note that you
52              have to use port names as defined in axports(5)  here,  anywhere
53              else you may use the port or the device name.
54
55       ax25-learn-routes no
56              Set  this to "yes", ax25rtd will add the routing information for
57              every heard frame (with complete digipeater path) to the  kernel
58              AX.25  routing table. Note that ax25rtd's internal cache will be
59              updated anyway, regardless of this option.
60
61       ax25-learn-only-mine no
62              If you set it to "yes", only frames that are  sent  to  (1)  the
63              interface  callsign, (2) any of the listeners on this device, or
64              (3) the callsigns specified by ax25-more-mycalls will be used to
65              update  the  internal cache and (depending on ax25-learn-routes)
66              the kernel routing table.
67
68       ax25-add-path db0ach     (example)
69              This is useful on DAMA digipeaters. In this case, the DAMA  mas‐
70              ter  has  to  be used for _every_ AX.25 connection, thus ax25rtd
71              will add this digipeater(s) to every target we learn that has no
72              digipeater path (yet). "db0ach" is just an example here.
73
74       ax25-more-mycalls dl1bke dl1bke-8  (example)
75              You  can  specify  more  calls as calls here that belong to this
76              interface... "dl1bke" and "dl1bke-8" are examples.
77
78       ip-learn-routes no
79              If set to "yes", ax25rtd will modify the IP routing table if  it
80              receives an IP frame (directed to us). This is dangerous!
81
82              It  should not screw up your routing table, though. Ax25rtd rec‐
83              ognizes the netmask of the device and will adjust the route only
84              if  it  fits  the netmask and the old route points to one of the
85              devices ax25rtd knows about (hence an AX.25 device).
86
87              The problems begin if you have more than one port and a user  is
88              able to hear your outgoing traffic on at least two of them.  Due
89              to technical reasons ax25rtd adjusts the route _after_ the  ker‐
90              nel  has sent the reply to the received TCP frame already.  This
91              has technical reasons.
92
93              If the remote does the same both are switching between  the  two
94              ports.
95
96              Don't use this feature unless you know what you are doing.
97
98              It  _should_  be  safe  do  enable  this  on  one-port machines,
99              although I strongly recommend to set a  network  route  instead,
100              i.e.:
101
102                      route add -net 44.0.0.0 scc3
103
104              Note  that  ax25rtd's  internal  cache  will  be updated anyway,
105              regardless of this option.
106
107       irtt <irtt>
108              If ip-learn-routes is  enabled  this  will  assign  newly  added
109              routes an initial round trip time (IRTT) for TCP. <irtt> is mea‐
110              sured in msec, hence
111
112                      irtt 10000
113
114              sets the irtt to 10 seconds. A value of 0 disables this  feature
115              (default).
116
117       ip-adjust-mode no
118              If  you  set  this  option  to  "yes" ax25rtd will change the IP
119              encapsulation mode according to the last received IP frame.
120
121              The problem with this option is that the kernel  AX.25  sends  a
122              received  IP  frame to the IP layer regardless if it was sent in
123              UI frame encapsulation  "mode  datagram  (dg)"  or  in  I  frame
124              encaps,  hence  in  an  AX.25  connection, "mode virtual connect
125              (vc)". The Linux  kernel  will  respond  to  this  frame  before
126              ax25rtd  can adjust the mode. If the remote does the same... You
127              get the picture.
128
129              Don't use this feature unless you know what you are doing.
130
131       arp-add   no
132              This option, if set to "yes",  changes  the  ARP  table  to  the
133              source  callsign  of  the received frame. It should be harmless,
134              just has the the effect that if it is a new entry, the Linux ARP
135              code will send one ARP request before ax25rtd has adjust the ARP
136              table. If there was already an existing ARP entry  for  this  IP
137              route,  one  IP  datagram  will  be sent to the old address. Not
138              really a problem, I hope.
139

SEE ALSO

141       ax25rtd(8), ax25rtctl(8).
142

AUTHORS

144       Joerg Reuter <jreuter@poboxes.com>
145       Llaus Kudielka OE1KIB
146
147
148
149Linux                          11 November 2003                AX25RTD.CONF(5)
Impressum