Seth Woolley's Man Viewer

netrom(4) - AF_NETROM - NET/ROM amateur packet radio protocol family - man 4 netrom

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

NETROM(4)                  Linux Programmer's Manual                 NETROM(4)



NAME
       AF_NETROM - NET/ROM amateur packet radio protocol family

DESCRIPTION
       NET/ROM  is  a  protocol  used extensively by radio amateurs. The Linux
       NET/ROM protocol family permits access(2,5) to these protocols via the stan-
       dard networking socket(2,7,n) metaphor.

       The NET/ROM protocol layer only supports connected mode. IP traffic may
       be stacked on top of NET/ROM frames using a non-standard  extension  to
       the NET/ROM protocol.

       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)
       NET/ROM).   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.

       NET/ROM addresses consist of 6 ascii(1,7) characters and a number called the
       SSID. These are encoded into a sockaddr_ax25 structure  which  is  pro-
       vided to the relevant system calls.

       NET/ROM  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.

       NET/ROM supports the following socket(2,7,n) options for SOL_NETROM. NETROM_T1
       is  the  T1  timer in(1,8) 1/10ths of a second, NETROM_T2 is the T2 timer in(1,8)
       1/10ths of a second. NETROM_N2, the retry counter is also configurable.
       There  is  no 'infinite retry' option supported however. It is possible
       for an application to request that the NET/ROM layer return the NET/ROM
       header  as  well  as  the  application  data,  this  is  done  via  the
       NETROM_HDRINCL socket(2,7,n) option.

SEE ALSO
       call(1),  socket(2,7,n)(2),  setsockopt(2),   getsockopt(2),   nrbroadcast(5),
       nrports(5), netromd(8), noderest(8), nodesave(8), nrctl(8), nrparms(8).


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



Linux                            25 July 1996                        NETROM(4)

References for this manual (incoming links)