---
name: "rsuplnk"
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/rsuplnk"
---

# rsuplnk(8)

User entry into the ROSE network.

## NAME

rsuplnk - User entry into the ROSE network.

## SYNOPSIS

**rsuplnk \[-q\] \<port\>**

## DESCRIPTION

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

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

\#\
 \[KE4GAJ-10\* VIA 144\]\
 NOCALL  \* \* \* \* \* \* L\
 default \* \* \* \* \* \* - root /usr/sbin/rsuplnk rsuplnk rs144\
 \#

There would typically be one **rsuplnk** per user access AX.25 port. The associated program for exiting a ROSE network is **rsdwnlnk.**

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

## OPTIONS

- **-q**

  Suppresses the messages generated by **rsuplnk** when making the connection.

## FILES

/etc/ax25/rsports

## SEE ALSO

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

## AUTHOR

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