---
name: "rsdwnlnk"
section: "8"
platform: "linux"
package: "ax25-tools"
version: "0.0.10-rc5+git20230513+d3e6d4f-3"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/rsdwnlnk"
---

# rsdwnlnk(8)

User exit from the ROSE network.

## NAME

rsdwnlnk - User exit from the ROSE network.

## SYNOPSIS

**rsdwnlnk \<port\> \<call\>**

## DESCRIPTION

The **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 **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.

To use **rsdwnlnk** you need an entry in **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.

\#\
 {\* VIA rs144}\
 NOCALL  \* \* \* \* \* \* L\
 default \* \* \* \* \* \* - root /usr/sbin/rsdwnlnk rsdwnlnk 144 KE4GAJ-10\
 \#

There would typically be one **rsdwnlnk** per ROSE port. The associated program for entering a ROSE network is **rsuplnk.**

All errors generated by **rsdwnlnk** are written to the system debug log file.

## FILES

/etc/ax25/axports

## SEE ALSO

[**rose**(4)](/rose/4.md), [**ax25d.conf**(5)](/ax25d.conf/5.md), [**ax25d**(8)](/ax25d/8.md), [**rsuplnk**(8)](/rsuplnk/8.md), [**rose\_call**(8)](/rose_call/8.md).

## AUTHOR

Jonathan Naylor G4KLX \<g4klx@g4klx.demon.co.uk\>