1 files changed, 63 insertions, 0 deletions
diff --git a/rose/rsuplnk.8 b/rose/rsuplnk.8
new file mode 100644
index 0000000..b9a65f1
--- /dev/null
+++ b/rose/rsuplnk.8
@@ -0,0 +1,63 @@
+.TH RSUPLNK 8 "29 April 1997" Linux "Linux Programmer's Manual"
+.SH NAME
+rsuplnk \- User entry into the ROSE network.
+.SH SYNOPSIS
+.B rsuplnk [-q] <port>
+.SH DESCRIPTION
+.LP
+The
+.B rsuplnk
+program allows a user to gain entry into the ROSE network using the standard
+pseudo-digipeating method. Recent Linux kernels are aware of this form
+of operation and the
+.B ax25d
+program can listen for such connections. The normal mode of operation of a
+ROSE switch is to have one ROSE address (ie port) per physical AX.25 port.
+Therefore ROSE users coming in on a given AX.25 port will appear as if they
+come from the associated ROSE port. This is the reason for the need for a
+ROSE port as an argument.
+.LP
+To use
+.B rsuplnk
+you need an entry in
+.B ax25d.conf
+to listen for incoming connections. In the example below, I will be
+listening for ROSE connections on my AX.25 port 144 using the callsign
+KE4GAJ-10 and the ROSE port associated with the AX.25 port is rs144.
+.LP
+#
+.br
+[KE4GAJ-10* VIA 144]
+.br
+NOCALL  * * * * * * L
+.br
+default * * * * * * - root /usr/sbin/rsuplnk rsuplnk rs144
+.br
+#
+.LP
+There would typically be one
+.B rsuplnk
+per user access AX.25 port. The associated program for exiting a ROSE
+network is
+.B rsdwnlnk.
+.LP
+All errors generated by
+.B rsuplnk
+are written to the system debug log file.
+.SH OPTIONS
+.TP 8
+.BI \-q
+Supresses the messages generated by
+.B rsuplnk
+when making the connection.
+.SH FILES
+.br
+/etc/ax25/rsports
+.SH "SEE ALSO"
+.BR rose (4),
+.BR ax25d.conf (5),
+.BR ax25d (8),
+.BR rsdwnlnk (8),
+.BR rose_call (8).
+.SH AUTHOR
+Jonathan Naylor G4KLX <g4klx@g4klx.demon.co.uk>