ROSE(4) Linux Programmer's Manual ROSE(4)
NAME
AF_ROSE - Rose amateur packet radio protocol family
DESCRIPTION
Rose is a protocol used extensively by radio amateurs. The Linux Rose
protocol family permits access(2,5) to these protocols via the standard net-
working socket(2,7,n) metaphor.
The Rose protocol layer only supports connected mode.
The only mode of operation is connected mode which is the mode used for
a socket(2,7,n) of type SOCK_SEQPACKET (stream sockets are not available in(1,8)
Rose). This requires that the user ensures output data is suitably
packetised, and that input data is read(2,n,1 builtins) a packet at a time(1,2,n) into a
buffer of suitable size.
Rose addresses consist of 10 digits. These are encoded into a sock-
addr_rose structure which is provided to the relevant system calls.
Rose has some unusual properties. Notably in(1,8) a multi-user system an
AX.25 address is often associated with a user, and some users(1,5) may not
have such an association. a set(7,n,1 builtins) of ioctl calls are provided to manage
an association table.
Rose supports the following socket(2,7,n) options for SOL_ROSE. ROSE_T1 is the
T11/T21 timer in(1,8) 1/10ths of a second, ROSE_T2 is the T12/T22 timer in(1,8)
1/10ths of a second. ROSE_T3, is the T13/T23 timer in(1,8) 1/10ths of a sec-
ond. It is possible for an application to request that the Rose layer
return the Rose header as well as the application data, this is done
via the ROSE_HDRINCL socket(2,7,n) option.
SEE ALSO
call(1), socket(2,7,n)(2), setsockopt(2), getsockopt(2), rsports(5), rsctl(8),
rsparms(8).
AUTHOR
Jonathan Naylor G4KLX <g4klx@g4klx.demon.co.uk>
Linux 27 August 1996 ROSE(4)