1 files changed, 58 insertions, 0 deletions
diff --git a/rose/rsdwnlnk.8 b/rose/rsdwnlnk.8
new file mode 100644
index 0000000..f0d4c2d
--- /dev/null
+++ b/rose/rsdwnlnk.8
@@ -0,0 +1,58 @@
+.TH RSDWNLNK 8 "29 April 1997" Linux "Linux Programmer's Manual"
+.SH NAME
+rsdwnlnk \- User exit from the ROSE network.
+.SH SYNOPSIS
+.B rsdwnlnk <port> <call>
+.SH DESCRIPTION
+.LP
+The
+.B rdwnplnk
+program allows a user to leave 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 create 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 ROSE port will come out of the
+associated AX.25 port.
+.LP
+To use
+.B rsdwnlnk
+you need an entry in
+.B ax25d.conf
+to listen for incoming ROSE connections to any callsigns that are not
+matched by the more specific ROSE entries. In the example below, I will be
+listening for ROSE connections on my ROSE port rs144, the exiting AX.25
+connection will be via the associated AX.25 port, 144, using the callsign 
+KE4GAJ-10. Please note that the callsign should be on the same line as the
+rest of the command, it may be wrapped onto the next line on your screen.
+.LP
+#
+.br
+{* VIA rs144}
+.br
+NOCALL  * * * * * * L
+.br
+default * * * * * * - root /usr/sbin/rsdwnlnk rsdwnlnk 144 KE4GAJ-10
+.br
+#
+.LP
+There would typically be one
+.B rsdwnlnk
+per ROSE port. The associated program for entering a ROSE network is
+.B rsuplnk.
+.LP
+All errors generated by
+.B rsdwnlnk
+are written to the system debug log file.
+.SH FILES
+.br
+/etc/ax25/axports
+.SH "SEE ALSO"
+.BR rose (4),
+.BR ax25d.conf (5),
+.BR ax25d (8),
+.BR rsuplnk (8),
+.BR rose_call (8).
+.SH AUTHOR
+Jonathan Naylor G4KLX <g4klx@g4klx.demon.co.uk>