[thirdparty/cups.git] / doc / help / network.html

<HTML>
<!-- SECTION: Getting Started -->
<HEAD>
	<TITLE>Using Network Printers</TITLE>
</HEAD>
<BODY>

<H2 CLASS="title"><A NAME="URI">Network Printer URIs</A></H2>

<P>Once you have set the IP address you can access the printer or
print server using the <CODE>ipp</CODE>, <CODE>lpd</CODE>, or
<CODE>socket</CODE> backends. The following is a list of common
network interfaces and printer servers and the settings you
should use with CUPS:</P>

<DIV CLASS="table"><TABLE SUMMARY="Common Device URIs">
<CAPTION>Table 1: Common Device URIs</CAPTION>
<THEAD>
<TR>
	<TH>Model/Manufacturer</TH>
	<TH>Device URI(s)</TH>
</TR>
</THEAD>
<TBODY>
<TR>
	<TD>Apple LaserWriter</TD>
	<TD>lpd://<I>address</I>/PASSTHRU</TD>
</TR>
<TR>
	<TD>Axis w/o IPP<BR>
	Axis OfficeBasic<BR>
	<A HREF="#AXIS">(see directions)</A></TD>
	<TD>socket://<I>address</I>:9100<BR>
	socket://<I>address</I>:9101<BR>
	socket://<I>address</I>:9102</TD>
</TR>
<TR>
	<TD>Axis w/IPP</TD>
	<TD>ipp://<I>address</I>/LPT1<BR>
	ipp://<I>address</I>/LPT2<BR>
	ipp://<I>address</I>/COM1</TD>
</TR>
<TR>
	<TD>Castelle LANpress<SUP>TM</SUP></TD>
	<TD>lpd://<I>address</I>/pr1<BR>
	lpd://<I>address</I>/pr2<BR>
	lpd://<I>address</I>/pr3</TD>
</TR>
<TR>
	<TD>DPI NETPrint</TD>
	<TD>lpd://<I>address</I>/pr1<BR>
	lpd://<I>address</I>/pr2<BR>
	lpd://<I>address</I>/pr3</TD>
</TR>
<TR>
	<TD>DLink DP-301P+</TD>
	<TD>socket://<I>address</I></TD>
</TR>
<TR>
	<TD>EFI&reg; Fiery&reg; RIP</TD>
	<TD>lpd://<I>address</I>/print</TD>
</TR>
<TR>
	<TD>EPSON&reg; Multiprotocol Ethernet Interface Board</TD>
	<TD>socket://<I>address</I></TD>
</TR>
<TR>
	<TD>Extended System ExtendNET</TD>
	<TD>lpd://<I>address</I>/pr1<BR>
	lpd://<I>address</I>/pr2<BR>
	lpd://<I>address</I>/pr3</TD>
</TR>
<TR>
	<TD>Hewlett Packard JetDirect w/o IPP</TD>
	<TD>socket://<I>address</I>:9100<BR>
	socket://<I>address</I>:9101<BR>
	socket://<I>address</I>:9102</TD>
</TR>
<TR>
	<TD>Hewlett Packard JetDirect w/IPP</TD>
	<TD>ipp://<I>address</I>/ipp<BR>
	ipp://<I>address</I>/ipp/port1<BR>
	ipp://<I>address</I>/ipp/port2<BR>
	ipp://<I>address</I>/ipp/port3</TD>
</TR>
<TR>
	<TD>Intel&reg; NetportExpress XL, PRO/100</TD>
	<TD>lpd://<I>address</I>/LPT1_PASSTHRU<BR>
	lpd://<I>address</I>/LPT2_PASSTHRU<BR>
	lpd://<I>address</I>/COM1_PASSTHRU</TD>
</TR>
<TR>
	<TD>Lexmark<SUP>TM</SUP> MarkNet</TD>
	<TD>lpd://<I>address</I>/ps</TD>
</TR>
<TR>
	<TD>Linksys EtherFast&reg;<BR>
	<A HREF="#LINKSYS">(see directions)</A></TD>
	<TD>socket://<I>address</I>:4010<BR>
	socket://<I>address</I>:4020<BR>
	socket://<I>address</I>:4030</TD>
</TR>
<TR>
	<TD>Linksys PSUS4</TD>
	<TD>lpd://<I>address</I>/lp</TD>
</TR>
<TR>
	<TD>Kodak&reg;</TD>
	<TD>lpd://<I>address</I>/ps</TD>
</TR>
<TR>
	<TD>QMS&reg; CrownNet<SUP>TM</SUP></TD>
	<TD>lpd://<I>address</I>/ps</TD>
</TR>
<TR>
	<TD>Tektronix&reg; PhaserShare<SUP>TM</SUP></TD>
	<TD>socket://<I>address</I>:9100</TD>
</TR>
<TR>
	<TD>XEROX&reg; 4512 NIC</TD>
	<TD>lpd://<I>address</I>/PORT1</TD>
</TR>
<TR>
	<TD>XEROX&reg; XNIC</TD>
	<TD>lpd://<I>address</I>/PASSTHRU</TD>
</TR>
<TR>
	<TD>XEROX&reg; (most others)</TD>
	<TD>socket://<I>address</I>:5503</TD>
</TR>
</TBODY>
</TABLE></DIV>

<H2 CLASS="title"><A NAME="ADDRESS">Getting the IP Address</A></H2>

<P>When you first install a network printer or print server on
your LAN, you need to set the Internet Protocol ("IP") address.
On most higher-end "workgroup" printers, you can set the address
through the printer control panel. However, in most cases you
will want to assign the addresses remotely from your workstation.
This makes administration a bit easier and avoids assigning
duplicate addresses accidentally.</P>

<P>To setup your printer or print server for remote address
assignment, you'll need the Ethernet Media Access Control ("MAC")
address, also sometimes called a node address, and the IP address
you want to use for the device. The Ethernet MAC address can
often be found on the printer test page or bottom of the print
server.</P>

<H3>Configuring the IP Address Using ARP</H3>

<P>The easiest way to set the IP address of a network device is
to use the <CODE>arp(8)</CODE> command.  The <CODE>arp</CODE>
sends an Address Resolution Protocol ("ARP") packet to the
specified Ethernet MAC address, setting the network device's IP
address:</P>

<PRE CLASS="command">
<KBD>arp -s ip-address ethernet-address</KBD>
<KBD>arp -s host.domain.com 08:00:69:00:12:34</KBD>
<KBD>arp -s 192.0.2.2 08:00:69:00:12:34</KBD>
</PRE>

<H3>Configuring the IP Address Using RARP</H3>

<P>The most flexible way to remotely assign IP addresses under
UNIX is through the Reverse Address Resolution Protocol ("RARP").
RARP allows a network device to request an IP address using its
Ethernet MAC address, and one or more RARP servers on the network
will respond with an ARP packet with the IP address the device
can use.</P>

<P>RARP should be used when you have to manage many printers or
print servers, or when you have a network device that does not
remember its IP address after a power cycle. If you just have a
single printer or print server, the <CODE>arp</CODE> command is
the way to go.</P>

<P>Some UNIX operating systems use a program called
<CODE>rarpd(8)</CODE> to manage RARP. Others, like Linux, support
this protocol in the kernel. For systems that provide the
<CODE>rarpd</CODE> program you will need to start it before RARP
lookups will work:</P>

<PRE CLASS="command">
<KBD>rarpd</KBD>
</PRE>

<P>Under IRIX you can enable this functionality by default
using:</P>

<PRE CLASS="command">
<KBD>chkconfig rarpd on</KBD>
</PRE>

<P>Both the <CODE>rarpd</CODE> program and kernel RARP support
read a list of Ethernet and IP addresses from the file
<VAR>/etc/ethers</VAR>. Each line contains the Ethernet address
(colon delimited) followed by an IP address or hostname like:</P>

<PRE CLASS="command">
08:00:69:00:12:34 myprinter.mydomain.com
08:00:69:00:12:34 192.0.2.2
</PRE>

<P>Add a line to this file and cycle the power on the printer or
print server to set its address.</P>

<H3>Configuring the IP Address Using BOOTP</H3>

<P>The BOOTP protocol is used when you need to provide additional
information such as the location of a configuration file to the
network interface. Using the standard <CODE>bootpd(8)</CODE>
program supplied with UNIX you simply need to add a line to the
<VAR>/etc/bootptab</VAR> file; for IRIX:</P>

<PRE CLASS="command">
myprinter 08:00:69:00:12:34 192.0.2.2 <VAR>myprinter.boot</VAR>
</PRE>

<P>Newer versions of <CODE>bootpd</CODE> use a different
format:</P>

<PRE CLASS="command">
myprinter:ha=080069001234:ip=192.0.2.2:<VAR>t144=myprinter.boot</VAR>
</PRE>

<P>The <VAR>myprinter.boot</VAR> file resides in the
<VAR>/usr/local/boot</VAR> directory by default. If you do not
need to provide a boot file you may leave the last part of the
line blank.</P>

<BLOCKQUOTE><B>Note:</B>

<P>Some versions of UNIX do not enable the BOOTP service by
default. The <VAR>/etc/inetd.conf</VAR> usually contains a line
for the BOOTP service that can be uncommented if needed.</P>

</BLOCKQUOTE>

<H2 CLASS="title"><A NAME="VERIFY">Verifying the Printer Connection</A></H2>

<P>To test that the IP address has been successfully assigned and
that the printer is properly connected to your LAN, type:</P>

<PRE CLASS="command">
<KBD>ping ip-address</KBD>
</PRE>

<P>If the connection is working properly you will see something
like:</P>

<PRE CLASS="command">
<KBD>ping myprinter</KBD>
PING myprinter (192.0.2.2): 56 data bytes
64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms
64 bytes from 192.0.2.2: icmp_seq=1 ttl=15 time=3 ms
64 bytes from 192.0.2.2: icmp_seq=2 ttl=15 time=3 ms
64 bytes from 192.0.2.2: icmp_seq=3 ttl=15 time=3 ms
</PRE>

<P>If not, verify that the printer or print server is connected
to the LAN, it is powered on, the LAN cabling is good, and the IP
address is set correctly. You can usually see the current IP
address and network status by printing a configuration or test
page on the device.</P>

<H2 CLASS="title"><A NAME="AXIS">Configuring Axis Print Servers</A></H2>

<P>The Axis print servers can be configured using ARP, RARP, or
BOOTP. However, on models that do not provide IPP support an
additional step must be performed to configure the TCP/IP portion
of the print server for use with CUPS.</P>

<P>Each print server contains a configuration file named
<VAR>config</VAR> that contains a list of network parameters used
by the server. To modify this file you must first download it
from the print server using the <CODE>ftp(1)</CODE> program:</P>

<PRE CLASS="command">
<KBD>ftp ip-address</KBD>
Connected to ip-address.
220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
ftp> <KBD>user root</KBD>
331 User name ok, need password
Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
230 User logged in
ftp> <KBD>get config</KBD>
local: config remote: config
200 PORT command successful.
150 Opening data connection for config (192,0,2,2),
(mode ascii).
226 Transfer complete.
##### bytes received in #.## seconds (##### Kbytes/s)
ftp> <KBD>quit</KBD>
221 Goodbye.
</PRE>

<P>Next, edit the file with your favorite text editor and locate
the lines beginning with:</P>

<PRE CLASS="command">
RTN_OPT.     : YES
RTEL_PR1.    : 0
RTEL_PR2.    : 0
RTEL_PR3.    : 0
RTEL_PR4.    : 0
RTEL_PR5.    : 0
RTEL_PR6.    : 0
RTEL_PR7.    : 0
RTEL_PR8.    : 0
</PRE>

<P>Change the <CODE>RTN_OPT</CODE> line to read:</P>

<PRE CLASS="command">
RTN_OPT.     : <KBD>NO</KBD>
</PRE>

<P>This disables the Reverse TELNET protocol and enables the
standard TELNET protocol on the print server. Next, assign a port
number for each parallel and serial port on the server as
follows:</P>

<PRE CLASS="command">
RTEL_PR1.    : <KBD>9100</KBD>
RTEL_PR2.    : <KBD>9101</KBD>
RTEL_PR3.    : <KBD>9102</KBD>
RTEL_PR4.    : <KBD>9103</KBD>
RTEL_PR5.    : <KBD>9104</KBD>
RTEL_PR6.    : <KBD>9105</KBD>
RTEL_PR7.    : <KBD>9106</KBD>
RTEL_PR8.    : <KBD>9107</KBD>
</PRE>

<P>This essentially makes the Axis print server look like a
Hewlett Packard JetDirect EX print server. Save the file and then
upload the new <VAR>config</VAR> file using the <CODE>ftp</CODE>
command:</P>

<PRE CLASS="command">
<KBD>ftp ip-address</KBD>
Connected to ip-address.
220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
ftp> <KBD>user root</KBD>
331 User name ok, need password
Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
230 User logged in
ftp> <KBD>put config CONFIG</KBD>
local: config remote: CONFIG
200 PORT command successful.
150 Opening data connection for config (192,0,2,2), (mode ascii).
226 Transfer complete.
##### bytes received in #.## seconds (##### Kbytes/s)
ftp> <KBD>get hardreset</KBD>
local: hardreset remote: hardreset
200 PORT command successful.
421 Axis NPS ### hard reset, closing connection.
ftp> <KBD>quit</KBD>
221 Goodbye.
</PRE>

<P>Your Axis print server is now ready for use!</P>

<H2 CLASS="title"><A NAME="LINKSYS">Configuring Linksys Print Servers</A></H2>

<P>The Linksys print servers can be configured using ARP, RARP,
or BOOTP. Like older Axis print servers, an additional step must
be performed to configure the TCP/IP portion of the print server
for use with CUPS.</P>

<P>Each print server contains a configuration file named
<VAR>CONFIG</VAR> that contains a list of network parameters used
by the server. To modify this file you must first download it
from the print server using the <CODE>ftp(1)</CODE> program:</P>

<PRE CLASS="command">
<KBD>ftp -n ip-address</KBD>
Connected to ip-address.
220 Print Server Ready.
Remote system type is Print.
ftp> <KBD>get CONFIG</KBD>
local: CONFIG remote: CONFIG
200 Command OK.
150 Open ASCII Mode Connection.
WARNING! 68 bare linefeeds received in ASCII mode
File may not have transferred correctly.
226 Transfer complete.
##### bytes received in #.## seconds (##### Kbytes/s)
ftp> <KBD>quit</KBD>
221 Goodbye.
</PRE>

<P>Next, edit the file with your favorite text editor and locate
the lines beginning with:</P>

<PRE CLASS="command">
0100 L1_PROUT:P1
0120 L2_PROUT:P1
0140 L3_PROUT:P1
</PRE>

<P>Change the port number for each parallel and serial port on
the server as follows:</P>

<PRE CLASS="command">
0100 L1_PROUT:<KBD>P1</KBD>
0120 L2_PROUT:<KBD>P2</KBD>
0140 L3_PROUT:<KBD>P3</KBD>
</PRE>

<P>This maps each virtual printer with a physical port. Save the
file and then upload the new <VAR>CONFIG</VAR> file using the
<CODE>ftp</CODE> command:</P>

<PRE CLASS="command">
<KBD>ftp -n ip-address</KBD>
Connected to ip-address.
220 Print Server Ready.
Remote system type is Print.
ftp> <KBD>put CONFIG</KBD>
local: CONFIG remote: CONFIG
200 Command OK.
150 Open ASCII Mode Connection.
226 Transfer complete.
##### bytes received in #.## seconds (##### Kbytes/s)
ftp> <KBD>quit</KBD>
221 Goodbye.
</PRE>

<P>Your Linksys print server is now ready for use!</P>

</BODY>
</HTML>
Commit	Line	Data
ef416fc2	1	<HTML>
	2	<!-- SECTION: Getting Started -->
	3	<HEAD>
	4	<TITLE>Using Network Printers</TITLE>
	5	</HEAD>
	6	<BODY>
	7
	8	<H2 CLASS="title"><A NAME="URI">Network Printer URIs</A></H2>
	9
	10	<P>Once you have set the IP address you can access the printer or
	11	print server using the <CODE>ipp</CODE>, <CODE>lpd</CODE>, or
	12	<CODE>socket</CODE> backends. The following is a list of common
	13	network interfaces and printer servers and the settings you
	14	should use with CUPS:</P>
	15
480ef0fe	16	<DIV CLASS="table"><TABLE SUMMARY="Common Device URIs">
	17	<CAPTION>Table 1: Common Device URIs</CAPTION>
	18	<THEAD>
	19	<TR>
ef416fc2	20	<TH>Model/Manufacturer</TH>
	21	<TH>Device URI(s)</TH>
	22	</TR>
480ef0fe	23	</THEAD>
	24	<TBODY>
	25	<TR>
ef416fc2	26	<TD>Apple LaserWriter</TD>
	27	<TD>lpd://<I>address</I>/PASSTHRU</TD>
	28	</TR>
480ef0fe	29	<TR>
ef416fc2	30	<TD>Axis w/o IPP<BR>
	31	Axis OfficeBasic<BR>
	32	<A HREF="#AXIS">(see directions)</A></TD>
	33	<TD>socket://<I>address</I>:9100<BR>
	34	socket://<I>address</I>:9101<BR>
	35	socket://<I>address</I>:9102</TD>
	36	</TR>
480ef0fe	37	<TR>
ef416fc2	38	<TD>Axis w/IPP</TD>
	39	<TD>ipp://<I>address</I>/LPT1<BR>
	40	ipp://<I>address</I>/LPT2<BR>
	41	ipp://<I>address</I>/COM1</TD>
	42	</TR>
480ef0fe	43	<TR>
ef416fc2	44	<TD>Castelle LANpress<SUP>TM</SUP></TD>
	45	<TD>lpd://<I>address</I>/pr1<BR>
	46	lpd://<I>address</I>/pr2<BR>
	47	lpd://<I>address</I>/pr3</TD>
	48	</TR>
480ef0fe	49	<TR>
ef416fc2	50	<TD>DPI NETPrint</TD>
	51	<TD>lpd://<I>address</I>/pr1<BR>
	52	lpd://<I>address</I>/pr2<BR>
	53	lpd://<I>address</I>/pr3</TD>
	54	</TR>
480ef0fe	55	<TR>
ef416fc2	56	<TD>DLink DP-301P+</TD>
	57	<TD>socket://<I>address</I></TD>
	58	</TR>
480ef0fe	59	<TR>
ef416fc2	60	<TD>EFI® Fiery® RIP</TD>
	61	<TD>lpd://<I>address</I>/print</TD>
	62	</TR>
480ef0fe	63	<TR>
ef416fc2	64	<TD>EPSON® Multiprotocol Ethernet Interface Board</TD>
	65	<TD>socket://<I>address</I></TD>
	66	</TR>
480ef0fe	67	<TR>
ef416fc2	68	<TD>Extended System ExtendNET</TD>
	69	<TD>lpd://<I>address</I>/pr1<BR>
	70	lpd://<I>address</I>/pr2<BR>
	71	lpd://<I>address</I>/pr3</TD>
	72	</TR>
480ef0fe	73	<TR>
ef416fc2	74	<TD>Hewlett Packard JetDirect w/o IPP</TD>
	75	<TD>socket://<I>address</I>:9100<BR>
	76	socket://<I>address</I>:9101<BR>
	77	socket://<I>address</I>:9102</TD>
	78	</TR>
480ef0fe	79	<TR>
ef416fc2	80	<TD>Hewlett Packard JetDirect w/IPP</TD>
	81	<TD>ipp://<I>address</I>/ipp<BR>
	82	ipp://<I>address</I>/ipp/port1<BR>
	83	ipp://<I>address</I>/ipp/port2<BR>
	84	ipp://<I>address</I>/ipp/port3</TD>
	85	</TR>
480ef0fe	86	<TR>
e1d6a774	87	<TD>Intel® NetportExpress XL, PRO/100</TD>
ef416fc2	88	<TD>lpd://<I>address</I>/LPT1_PASSTHRU<BR>
	89	lpd://<I>address</I>/LPT2_PASSTHRU<BR>
	90	lpd://<I>address</I>/COM1_PASSTHRU</TD>
	91	</TR>
480ef0fe	92	<TR>
ef416fc2	93	<TD>Lexmark<SUP>TM</SUP> MarkNet</TD>
	94	<TD>lpd://<I>address</I>/ps</TD>
	95	</TR>
480ef0fe	96	<TR>
ef416fc2	97	<TD>Linksys EtherFast®<BR>
	98	<A HREF="#LINKSYS">(see directions)</A></TD>
	99	<TD>socket://<I>address</I>:4010<BR>
	100	socket://<I>address</I>:4020<BR>
	101	socket://<I>address</I>:4030</TD>
	102	</TR>
480ef0fe	103	<TR>
ef416fc2	104	<TD>Linksys PSUS4</TD>
	105	<TD>lpd://<I>address</I>/lp</TD>
	106	</TR>
480ef0fe	107	<TR>
ef416fc2	108	<TD>Kodak®</TD>
	109	<TD>lpd://<I>address</I>/ps</TD>
	110	</TR>
480ef0fe	111	<TR>
ef416fc2	112	<TD>QMS® CrownNet<SUP>TM</SUP></TD>
	113	<TD>lpd://<I>address</I>/ps</TD>
	114	</TR>
480ef0fe	115	<TR>
ef416fc2	116	<TD>Tektronix® PhaserShare<SUP>TM</SUP></TD>
	117	<TD>socket://<I>address</I>:9100</TD>
	118	</TR>
480ef0fe	119	<TR>
ef416fc2	120	<TD>XEROX® 4512 NIC</TD>
	121	<TD>lpd://<I>address</I>/PORT1</TD>
	122	</TR>
480ef0fe	123	<TR>
ef416fc2	124	<TD>XEROX® XNIC</TD>
	125	<TD>lpd://<I>address</I>/PASSTHRU</TD>
	126	</TR>
480ef0fe	127	<TR>
ef416fc2	128	<TD>XEROX® (most others)</TD>
	129	<TD>socket://<I>address</I>:5503</TD>
	130	</TR>
480ef0fe	131	</TBODY>
ef416fc2	132	</TABLE></DIV>
	133
	134	<H2 CLASS="title"><A NAME="ADDRESS">Getting the IP Address</A></H2>
	135
	136	<P>When you first install a network printer or print server on
	137	your LAN, you need to set the Internet Protocol ("IP") address.
	138	On most higher-end "workgroup" printers, you can set the address
	139	through the printer control panel. However, in most cases you
	140	will want to assign the addresses remotely from your workstation.
	141	This makes administration a bit easier and avoids assigning
	142	duplicate addresses accidentally.</P>
	143
	144	<P>To setup your printer or print server for remote address
	145	assignment, you'll need the Ethernet Media Access Control ("MAC")
	146	address, also sometimes called a node address, and the IP address
	147	you want to use for the device. The Ethernet MAC address can
	148	often be found on the printer test page or bottom of the print
	149	server.</P>
	150
	151	<H3>Configuring the IP Address Using ARP</H3>
	152
	153	<P>The easiest way to set the IP address of a network device is
	154	to use the <CODE>arp(8)</CODE> command. The <CODE>arp</CODE>
	155	sends an Address Resolution Protocol ("ARP") packet to the
	156	specified Ethernet MAC address, setting the network device's IP
	157	address:</P>
	158
	159	<PRE CLASS="command">
	160	<KBD>arp -s ip-address ethernet-address</KBD>
	161	<KBD>arp -s host.domain.com 08:00:69:00:12:34</KBD>
	162	<KBD>arp -s 192.0.2.2 08:00:69:00:12:34</KBD>
	163	</PRE>
	164
	165	<H3>Configuring the IP Address Using RARP</H3>
	166
	167	<P>The most flexible way to remotely assign IP addresses under
	168	UNIX is through the Reverse Address Resolution Protocol ("RARP").
	169	RARP allows a network device to request an IP address using its
	170	Ethernet MAC address, and one or more RARP servers on the network
	171	will respond with an ARP packet with the IP address the device
	172	can use.</P>
	173
	174	<P>RARP should be used when you have to manage many printers or
	175	print servers, or when you have a network device that does not
	176	remember its IP address after a power cycle. If you just have a
	177	single printer or print server, the <CODE>arp</CODE> command is
	178	the way to go.</P>
	179
	180	<P>Some UNIX operating systems use a program called
	181	<CODE>rarpd(8)</CODE> to manage RARP. Others, like Linux, support
	182	this protocol in the kernel. For systems that provide the
	183	<CODE>rarpd</CODE> program you will need to start it before RARP
	184	lookups will work:</P>
	185
	186	<PRE CLASS="command">
	187	<KBD>rarpd</KBD>
	188	</PRE>
	189
	190	<P>Under IRIX you can enable this functionality by default
	191	using:</P>
	192
	193	<PRE CLASS="command">
	194	<KBD>chkconfig rarpd on</KBD>
	195	</PRE>
196
197	<P>Both the <CODE>rarpd</CODE> program and kernel RARP support
198	read a list of Ethernet and IP addresses from the file
199	<VAR>/etc/ethers</VAR>. Each line contains the Ethernet address
200	(colon delimited) followed by an IP address or hostname like:</P>
201
202	<PRE CLASS="command">
203	08:00:69:00:12:34 myprinter.mydomain.com
204	08:00:69:00:12:34 192.0.2.2
205	</PRE>
206
207	<P>Add a line to this file and cycle the power on the printer or
208	print server to set its address.</P>
209
210	<H3>Configuring the IP Address Using BOOTP</H3>
211
212	<P>The BOOTP protocol is used when you need to provide additional
213	information such as the location of a configuration file to the
214	network interface. Using the standard <CODE>bootpd(8)</CODE>
215	program supplied with UNIX you simply need to add a line to the
216	<VAR>/etc/bootptab</VAR> file; for IRIX:</P>
217
218	<PRE CLASS="command">
219	myprinter 08:00:69:00:12:34 192.0.2.2 <VAR>myprinter.boot</VAR>
220	</PRE>
221
222	<P>Newer versions of <CODE>bootpd</CODE> use a different
223	format:</P>
224
225	<PRE CLASS="command">
226	myprinter:ha=080069001234:ip=192.0.2.2:<VAR>t144=myprinter.boot</VAR>
227	</PRE>
228
229	<P>The <VAR>myprinter.boot</VAR> file resides in the
230	<VAR>/usr/local/boot</VAR> directory by default. If you do not
231	need to provide a boot file you may leave the last part of the
232	line blank.</P>
233
234	<BLOCKQUOTE><B>Note:</B>
235
236	<P>Some versions of UNIX do not enable the BOOTP service by
237	default. The <VAR>/etc/inetd.conf</VAR> usually contains a line
238	for the BOOTP service that can be uncommented if needed.</P>
239
240	</BLOCKQUOTE>
241
242	<H2 CLASS="title"><A NAME="VERIFY">Verifying the Printer Connection</A></H2>
243
244	<P>To test that the IP address has been successfully assigned and
245	that the printer is properly connected to your LAN, type:</P>
246
247	<PRE CLASS="command">
248	<KBD>ping ip-address</KBD>
249	</PRE>
250
251	<P>If the connection is working properly you will see something
252	like:</P>
253
254	<PRE CLASS="command">
255	<KBD>ping myprinter</KBD>
256	PING myprinter (192.0.2.2): 56 data bytes
257	64 bytes from 192.0.2.2: icmp_seq=0 ttl=15 time=5 ms
258	64 bytes from 192.0.2.2: icmp_seq=1 ttl=15 time=3 ms
259	64 bytes from 192.0.2.2: icmp_seq=2 ttl=15 time=3 ms
260	64 bytes from 192.0.2.2: icmp_seq=3 ttl=15 time=3 ms
261	</PRE>
262
263	<P>If not, verify that the printer or print server is connected
264	to the LAN, it is powered on, the LAN cabling is good, and the IP
265	address is set correctly. You can usually see the current IP
266	address and network status by printing a configuration or test
267	page on the device.</P>
268
269	<H2 CLASS="title"><A NAME="AXIS">Configuring Axis Print Servers</A></H2>
270
271	<P>The Axis print servers can be configured using ARP, RARP, or
272	BOOTP. However, on models that do not provide IPP support an
273	additional step must be performed to configure the TCP/IP portion
274	of the print server for use with CUPS.</P>
275
276	<P>Each print server contains a configuration file named
277	<VAR>config</VAR> that contains a list of network parameters used
278	by the server. To modify this file you must first download it
279	from the print server using the <CODE>ftp(1)</CODE> program:</P>
280
281	<PRE CLASS="command">
282	<KBD>ftp ip-address</KBD>
283	Connected to ip-address.
284	220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
285	ftp> <KBD>user root</KBD>
286	331 User name ok, need password
287	Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
288	230 User logged in
289	ftp> <KBD>get config</KBD>
290	local: config remote: config
291	200 PORT command successful.
292	150 Opening data connection for config (192,0,2,2),
293	(mode ascii).
294	226 Transfer complete.
295	##### bytes received in #.## seconds (##### Kbytes/s)
296	ftp> <KBD>quit</KBD>
297	221 Goodbye.
298	</PRE>
299
300	<P>Next, edit the file with your favorite text editor and locate
301	the lines beginning with:</P>
302
303	<PRE CLASS="command">
304	RTN_OPT. : YES
305	RTEL_PR1. : 0
306	RTEL_PR2. : 0
307	RTEL_PR3. : 0
308	RTEL_PR4. : 0
309	RTEL_PR5. : 0
310	RTEL_PR6. : 0
311	RTEL_PR7. : 0
312	RTEL_PR8. : 0
313	</PRE>
314
315	<P>Change the <CODE>RTN_OPT</CODE> line to read:</P>
316
317	<PRE CLASS="command">
318	RTN_OPT. : <KBD>NO</KBD>
319	</PRE>
320
321	<P>This disables the Reverse TELNET protocol and enables the
322	standard TELNET protocol on the print server. Next, assign a port
323	number for each parallel and serial port on the server as
324	follows:</P>
325
326	<PRE CLASS="command">
327	RTEL_PR1. : <KBD>9100</KBD>
328	RTEL_PR2. : <KBD>9101</KBD>
329	RTEL_PR3. : <KBD>9102</KBD>
330	RTEL_PR4. : <KBD>9103</KBD>
331	RTEL_PR5. : <KBD>9104</KBD>
332	RTEL_PR6. : <KBD>9105</KBD>
333	RTEL_PR7. : <KBD>9106</KBD>
334	RTEL_PR8. : <KBD>9107</KBD>
335	</PRE>
336
337	<P>This essentially makes the Axis print server look like a
338	Hewlett Packard JetDirect EX print server. Save the file and then
339	upload the new <VAR>config</VAR> file using the <CODE>ftp</CODE>
340	command:</P>
341
342	<PRE CLASS="command">
343	<KBD>ftp ip-address</KBD>
344	Connected to ip-address.
345	220 Axis NPS ### FTP Printer Server V#.## MON DD YEAR ready.
346	ftp> <KBD>user root</KBD>
347	331 User name ok, need password
348	Password: <KBD>pass</KBD> <I>(this is not echoed)</I>
349	230 User logged in
350	ftp> <KBD>put config CONFIG</KBD>
351	local: config remote: CONFIG
352	200 PORT command successful.
353	150 Opening data connection for config (192,0,2,2), (mode ascii).
354	226 Transfer complete.
355	##### bytes received in #.## seconds (##### Kbytes/s)
356	ftp> <KBD>get hardreset</KBD>
357	local: hardreset remote: hardreset
358	200 PORT command successful.
359	421 Axis NPS ### hard reset, closing connection.
360	ftp> <KBD>quit</KBD>
361	221 Goodbye.
362	</PRE>
363
364	<P>Your Axis print server is now ready for use!</P>
365
366	<H2 CLASS="title"><A NAME="LINKSYS">Configuring Linksys Print Servers</A></H2>
367
368	<P>The Linksys print servers can be configured using ARP, RARP,
369	or BOOTP. Like older Axis print servers, an additional step must
370	be performed to configure the TCP/IP portion of the print server
371	for use with CUPS.</P>
372
373	<P>Each print server contains a configuration file named
374	<VAR>CONFIG</VAR> that contains a list of network parameters used
375	by the server. To modify this file you must first download it
376	from the print server using the <CODE>ftp(1)</CODE> program:</P>
377
378	<PRE CLASS="command">
379	<KBD>ftp -n ip-address</KBD>
380	Connected to ip-address.
381	220 Print Server Ready.
382	Remote system type is Print.
383	ftp> <KBD>get CONFIG</KBD>
384	local: CONFIG remote: CONFIG
385	200 Command OK.
386	150 Open ASCII Mode Connection.
387	WARNING! 68 bare linefeeds received in ASCII mode
388	File may not have transferred correctly.
389	226 Transfer complete.
390	##### bytes received in #.## seconds (##### Kbytes/s)
391	ftp> <KBD>quit</KBD>
392	221 Goodbye.
393	</PRE>
394
395	<P>Next, edit the file with your favorite text editor and locate
396	the lines beginning with:</P>
397
398	<PRE CLASS="command">
399	0100 L1_PROUT:P1
400	0120 L2_PROUT:P1
401	0140 L3_PROUT:P1
402	</PRE>
403
404	<P>Change the port number for each parallel and serial port on
405	the server as follows:</P>
406
407	<PRE CLASS="command">
408	0100 L1_PROUT:<KBD>P1</KBD>
409	0120 L2_PROUT:<KBD>P2</KBD>
410	0140 L3_PROUT:<KBD>P3</KBD>
411	</PRE>
412
413	<P>This maps each virtual printer with a physical port. Save the
414	file and then upload the new <VAR>CONFIG</VAR> file using the
415	<CODE>ftp</CODE> command:</P>
416
417	<PRE CLASS="command">
418	<KBD>ftp -n ip-address</KBD>
419	Connected to ip-address.
420	220 Print Server Ready.
421	Remote system type is Print.
422	ftp> <KBD>put CONFIG</KBD>
423	local: CONFIG remote: CONFIG
424	200 Command OK.
425	150 Open ASCII Mode Connection.
426	226 Transfer complete.
427	##### bytes received in #.## seconds (##### Kbytes/s)
428	ftp> <KBD>quit</KBD>
429	221 Goodbye.
430	</PRE>
431
432	<P>Your Linksys print server is now ready for use!</P>
433
ef416fc2	434	</BODY>
ef416fc2	435	</HTML>