<HTML ><HEAD ><TITLE >Configuring a NET/ROM port</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.63 "><LINK REL="HOME" TITLE="Linux Amateur Radio AX.25 HOWTO" HREF="index.html"><LINK REL="PREVIOUS" TITLE="Configuring an AX.25 interface for TCP/IP" HREF="x1194.html"><LINK REL="NEXT" TITLE="Configuring a NET/ROM interface for TCP/IP" HREF="x1343.html"></HEAD ><BODY CLASS="SECT1" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >Linux Amateur Radio AX.25 HOWTO</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="x1194.html" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="x1343.html" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="AEN1218" >8. Configuring a NET/ROM port</A ></H1 ><P >The NET/ROM protocol relies on, and uses the AX.25 ports you have created. The NET/ROM protocol rides on top of the AX.25 protocol. To configure NET/ROM on an AX.25 interface you must configure two files. One file describes the NET/ROM interfaces, and the other file describes which of the AX.25 ports will carry NET/ROM. You can configure multiple NET/ROM ports, each with its own callsign and alias, the same procedure applies for each.</P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN1221" >8.1. Configuring <TT CLASS="LITERAL" >/etc/ax25/nrports</TT ></A ></H2 ><P >The first is the <TT CLASS="LITERAL" >/etc/ax25/nrports</TT > file. This file describes the NET/ROM ports in much the same way as the <TT CLASS="LITERAL" >/etc/ax25/axports</TT > file describes the AX.25 ports. Each NET/ROM device you wish to create must have an entry in the <TT CLASS="LITERAL" >/etc/ax25/nrports</TT > file. Normally a Linux machine would have only one NET/ROM device configured that would use a number of the AX.25 ports defined. In some situations you might wish a special service such as a BBS to have a separate NET/ROM alias and so you would create more than one.</P ><P >This file is formatted as follows:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >name callsign alias paclen description</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >Where: <P ></P ><DIV CLASS="VARIABLELIST" ><DL ><DT >name</DT ><DD ><P >is the text name that you wish to refer to the port by.</P ></DD ><DT >callsign</DT ><DD ><P >is the callsign that the NET/ROM traffic from this port will use. Note, this is <EM >not</EM > that address that users should connect to to get access to a <EM >node</EM > style interface. (The node program is covered later). This callsign/ssid should be unique and should not appear elsewhere in either of the <TT CLASS="LITERAL" >/etc/ax25/axports</TT > or the <TT CLASS="LITERAL" >/etc/ax25/nrports</TT > files.</P ></DD ><DT >alias</DT ><DD ><P >is the NET/ROM alias this port will have assigned to it.</P ></DD ><DT >paclen</DT ><DD ><P >is the maximum size of NET/ROM frames transmitted by this port.</P ></DD ><DT >description</DT ><DD ><P >is a free text description of the port.</P ></DD ></DL ></DIV ></P ><P >An example would look something like the following:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >netrom VK2KTJ-9 LINUX 236 Linux Switch Port</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >This example creates a NET/ROM port known to the rest of the NET/ROM network as `<TT CLASS="LITERAL" >LINUX:VK2KTJ-9</TT >'.</P ><P >This file is used by programs such as the <EM >call</EM > program.</P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN1264" >8.2. Configuring <TT CLASS="LITERAL" >/etc/ax25/nrbroadcast</TT ></A ></H2 ><P >The second file is the <TT CLASS="LITERAL" >/etc/ax25/nrbroadcast</TT > file. This file may contain a number of entries. There would normally be one entry for each AX.25 port that you wish to allow NET/ROM traffic on.</P ><P >This file is formatted as follows:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >axport min_obs def_qual worst_qual verbose</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >Where: <P ></P ><DIV CLASS="VARIABLELIST" ><DL ><DT >axport</DT ><DD ><P >is the port name obtained from the <TT CLASS="LITERAL" >/etc/ax25/axports</TT > file. If you do not have an entry in <TT CLASS="LITERAL" >/etc/ax25/nrbroadcasts</TT > for a port then this means that no NET/ROM routing will occur and any received NET/ROM broadcasts will be ignored for that port.</P ></DD ><DT >min_obs</DT ><DD ><P >is the minimum obselesence value for the port.</P ></DD ><DT >def_qual</DT ><DD ><P >is the default quality for the port.</P ></DD ><DT >worst_qual</DT ><DD ><P >is the worst quality value for the port, any routes under this quality will be ignored.</P ></DD ><DT >verbose</DT ><DD ><P >is a flag determining whether full NET/ROM routing broadcasts will occur from this port or only a routing broadcast advertising the node itself.</P ></DD ></DL ></DIV ></P ><P >An example would look something like the following:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" >radio 1 200 100 1</PRE ></FONT ></TD ></TR ></TABLE ></P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN1299" >8.3. Creating the NET/ROM Network device</A ></H2 ><P >When you have the two configuration files completed you must create the NET/ROM device in much the same way as you did for the AX.25 devices. This time you use the <EM >nrattach</EM > command. The <EM >nrattach</EM > works in just the same way as the <EM >axattach</EM > command except that it creates NET/ROM network devices called `<TT CLASS="LITERAL" >nr[0-9]</TT >'. Again, the first time you use the <EM >nrattach</EM > command it creates the `<TT CLASS="LITERAL" >nr0</TT >' device, the second time it creates the `<TT CLASS="LITERAL" >nr1</TT >' network devices etc. To create the network device for the NET/ROM port we've defined we would use:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" ># nrattach netrom</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >This command would start the NET/ROM device (<TT CLASS="LITERAL" >nr0</TT >) named <TT CLASS="LITERAL" >netrom</TT > configured with the details specified in the <TT CLASS="LITERAL" >/etc/ax25/nrports</TT > file.</P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN1315" >8.4. Starting the NET/ROM daemon</A ></H2 ><P >The Linux kernel does all of the NET/ROM protocol and switching, but does not manage some functions. The NET/ROM daemon manages the NET/ROM routing tables and generates the NET/ROM routing broadcasts. You start NET/ROM daemon with the command:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" ># /usr/sbin/netromd -i</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >You should soon see the <TT CLASS="LITERAL" >/proc/net/nr_neigh</TT > file filling up with information about your NET/ROM neighbours.</P ><P >Remember to put the <TT CLASS="LITERAL" >/usr/sbin/netromd</TT > command in your <EM >rc</EM > files so that it is started automatically each time you reboot.</P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN1325" >8.5. Configuring NET/ROM routing.</A ></H2 ><P >You may wish to configure static NET/ROM routes for specific hosts. The <EM >nrparms</EM > command enables you to do this. Again, the <EM >man</EM > page offers a complete description, but a simple example might be:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" ># /usr/sbin/nrparms -nodes VK2XLZ-10 + #MINTO 120 5 radio VK2SUT-9</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >This command would set a NET/ROM route to <TT CLASS="LITERAL" >#MINTO:VK2XLZ-10</TT > via a neighbour <TT CLASS="LITERAL" >VK2SUT-9</TT > on my AX.25 port called `<TT CLASS="LITERAL" >radio</TT >'.</P ><P >You can manually create entries for new neighbours using the <EM >nrparms</EM > command as well. For example:</P ><P ><TABLE BORDER="1" BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD ><FONT COLOR="#000000" ><PRE CLASS="SCREEN" ># /usr/sbin/nrparms -routes radio VK2SUT-9 + 120</PRE ></FONT ></TD ></TR ></TABLE ></P ><P >This command would create <TT CLASS="LITERAL" >VK2SUT-9</TT > as a NET/ROM neighbour with a quality of <TT CLASS="LITERAL" >120</TT > and this will be locked and will not be deleted automatically.</P ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="x1194.html" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="x1343.html" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Configuring an AX.25 interface for TCP/IP</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" > </TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Configuring a NET/ROM interface for TCP/IP</TD ></TR ></TABLE ></DIV ></BODY ></HTML >