1AXDIGI(8) Linux Programmer's Manual AXDIGI(8)
2
3
4
6 axdigi - axdigi file.
7
9 axdigi This executable should be loaded in your startup script with the
10 command: /usr/local/sbin/axdigi (or path to where you installed it).
11 This file enables cross-port digipeating within your linux's ax25
12 stack.
13
14 Special Conditions: axdigi In order to digipeat, you or the user *must*
15 know your SSID associated with the ifconfig <interface> that is the
16 direct link to the outbound path they wish to digi to. axdigi will han‐
17 dle the appropriate digipeat accordingly. If you have multiple ax25
18 interfaces, you should somehow list them for the users in the axports
19 description so they will see them when doing an "Interface" command
20 while on URONode. If the user wishes to log off URONode and digi
21 through, then they must use the interface's SSID associated with the
22 OUTBOUND path to their destination.
23
24 commands are:
25
26 C <destination> via <your interface-SSID>
27 If the user heard station A1BCD-7 on your ax0 interface,
28 and that interface's SSID is: W1XYZ-9 (NOT the FlexID of
29 URONode!) then the user would enter: c a1bcd-7 via
30 w1xyz-9 even if their inbound interface might be ax1 and
31 it's ifconfig shows your SSID as w1xyz-10!
32
33 Detailed information
34 If you have 3 ax25 interfaces ifconfigured as: ax0 -
35 w1xyz-9 ax1 - w1xyz-10 ax2 - w1xyz-11
36
37 User k2lmn would enter your node via ax2 and they wish to
38 digi to a1bcd-7 which is heard on ax0 they would simply
39 enter: c a1bcd-7 via w1xyz-9 to connect. Axdigi handles
40 the crossport functions. If they tried: c a1bcd-7 via
41 w1xyz-11 the connect would fail because it would attempt
42 to digi OUT on your ax2 interface. This may get tricky so
43 expect a need to educate your users on this. Unfortu‐
44 nately, linux lacks native cross-port digipeating at this
45 time so this is a work-around.
46
48 /usr/local/sbin/axdigi
49
51 axports(5), ax25(4).
52
53
54
55Linux 28 April 2013 AXDIGI(8)