diff --git a/debian/README.source b/debian/README.source new file mode 100644 index 0000000..1a89a3d --- /dev/null +++ b/debian/README.source @@ -0,0 +1,2 @@ +Manpages from upstream have been patched out due to being supplied as +gzipped files. They have been unzipped and moved to debian/manpages. diff --git a/debian/manpages/axdigi.8 b/debian/manpages/axdigi.8 new file mode 100644 index 0000000..f764c6e --- /dev/null +++ b/debian/manpages/axdigi.8 @@ -0,0 +1,52 @@ +.TH AXDIGI 8 "28 April 2013" Linux "Linux Programmer's Manual" +.SH NAME +axdigi \- axdigi file. +.SH DESCRIPTION +.LP +.B axdigi +This executable should be loaded in your startup script with the command: +/usr/local/sbin/axdigi (or path to where you installed it). This file enables +cross-port digipeating within your linux's ax25 stack. +.LP +Special Conditions: +.B axdigi +In order to digipeat, you or the user *must* know your SSID associated +with the ifconfig that is the direct link to the outbound +path they wish to digi to. axdigi will handle the appropriate digipeat +accordingly. If you have multiple ax25 interfaces, you should somehow +list them for the users in the axports description so they will see +them when doing an "Interface" command while on URONode. If the user +wishes to log off URONode and digi through, then they must use the +interface's SSID associated with the OUTBOUND path to their destination. +.sp +commands are: +.TP 14 +.B C via +If the user heard station A1BCD-7 on your ax0 interface, and that +interface's SSID is: W1XYZ-9 (NOT the FlexID of URONode!) then the user +would enter: +c a1bcd-7 via w1xyz-9 +even if their inbound interface might be ax1 and it's ifconfig shows +your SSID as w1xyz-10! +.TP 14 +.B Detailed information +If you have 3 ax25 interfaces ifconfigured as: +ax0 - w1xyz-9 +ax1 - w1xyz-10 +ax2 - w1xyz-11 + +User k2lmn would enter your node via ax2 and they wish to digi to +a1bcd-7 which is heard on ax0 they would simply enter: +c a1bcd-7 via w1xyz-9 to connect. Axdigi handles the crossport +functions. If they tried: +c a1bcd-7 via w1xyz-11 +the connect would fail because it would attempt to digi OUT on your +ax2 interface. This may get tricky so expect a need to educate your +users on this. Unfortunately, linux lacks native cross-port digipeating +at this time so this is a work-around. +.SH FILES +.LP +/usr/local/sbin/axdigi +.SH "SEE ALSO" +.BR axports (5), +.BR ax25 (4). diff --git a/debian/manpages/flexd.conf.5 b/debian/manpages/flexd.conf.5 new file mode 100644 index 0000000..60c50cb --- /dev/null +++ b/debian/manpages/flexd.conf.5 @@ -0,0 +1,51 @@ +.TH FLEXD.CONF 5 "28 April 2013" Linux "Linux Programmer's Manual" +.SH NAME +flexd.conf \- flexd configuration file. +.SH DESCRIPTION +.LP +.B flexd.conf +file is read by flexd at program startup and is used to modify the +behaviour of the robot. +.LP +The lines within +.B flexd.conf +must either be a comment line, which starts with a # in the first column, or +one of the commands listed below. Commands and arguments are delimited +by white space. Arguments can contain white space if they are enclosed +in double quotes. Also C-style escapes (\\n, \\x0A, \\012 etc.) are parsed +within double quotes. +.sp +Available configuration commands are: +.TP 14 +.B MyCall +Sets up the callsign AND ssid you wish to use to connect to your flexnet +neighbor for destinations import. Do NOT use an ssid of your ax25 interface +which you'll be polling from as you may create a loop between your system +and the flexnet neighbor. +An example: MyCall kb1uuu-13 +.TP 14 +.B PollInterval