<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<TITLE>Installing Internet</TITLE>

<META NAME="GENERATOR" CONTENT="Internet Assistant for Microsoft Word 2.04z">
</HEAD>
<BODY BGCOLOR="#FFFFFF">
<P>
<A HREF="6_filemap"><IMG SRC="pics/PREV.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="Front"><IMG SRC="pics/FRONT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="TOC"><IMG SRC="pics/CONTS.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="index"><IMG SRC="pics/INDEX.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="8_AppxB"><IMG SRC="pics/NEXT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<P>
<B><FONT SIZE=6>Appendix A: Installing Internet</FONT></B>
<HR>
<P>
In the earlier chapter <A HREF="4_TCPintro">Introduction to TCP/IP</A>
we outlined different ways in which you could set up OmniClient.
You'll have to edit some configuration files to do so. This chapter
tells you how to make those changes and install the software.
It assumes you are using the desktop, and are familiar with simple
use of it. If you have any problems refer to the RISC OS User
Guide supplied with your RISC OS computer.
<H2><A NAME="Config">Config</A>uration files</H2>
<P>
The configuration files that you need to edit are held within
the Internet Application. Rather than refer them all the time
by their lengthy full pathnames, we'll just use the leafname.
The files are supplied on the Network distribution disc as:
<P>
<TABLE >
<TR><TD WIDTH=284><B>Filename</B></TD><TD WIDTH=151><B>Leafname</B>
</TD></TR>
<TR><TD WIDTH=284><TT><FONT FACE="Courier">$.!Internet.files.hosts</FONT></TT> 
</TD><TD WIDTH=151>hosts</TD></TR>
<TR><TD WIDTH=284><TT><FONT FACE="Courier">$.!Internet.files.extensions</FONT></TT> 
</TD><TD WIDTH=151>extensions</TD></TR>
<TR><TD WIDTH=284><TT><FONT FACE="Courier">$.!Internet.files.mimemap</FONT></TT> 
</TD><TD WIDTH=151>mimemap</TD></TR>
<TR><TD WIDTH=284><TT><FONT FACE="Courier">$.!Internet.files.networks</FONT></TT> 
</TD><TD WIDTH=151>networks</TD></TR>
<TR><TD WIDTH=284><TT><FONT FACE="Courier">$.!Internet.files.protocols</FONT></TT> 
</TD><TD WIDTH=151>protocols</TD></TR>
<TR><TD WIDTH=284><TT><FONT FACE="Courier">$.!Internet.files.services</FONT></TT> 
</TD><TD WIDTH=151>services</TD></TR>
</TABLE>
<P>
The hosts, networks, protocols and services are collectively known
as the databases.
<H3>What the files do</H3>
<UL>
<LI>The <TT><FONT FACE="Courier">hosts</FONT></TT>  file gives
the host names and the Internet addresses of all the computers
you wish to refer to by their hostname.
<LI>The <TT><FONT FACE="Courier">extensions</FONT></TT>  file allows
`from' extensions to be added when converting from RISC OS to
Host, and `to' extensions to be removed when converting to RISC
OS from Host.
<LI>The <TT><FONT FACE="Courier">mimemap</FONT></TT>  file maps
the each content type to (a) particular file type(s).
<LI>The <TT><FONT FACE="Courier">networks</FONT></TT> , <TT><FONT FACE="Courier">protocols</FONT></TT> 
and <TT><FONT FACE="Courier">services</FONT></TT>  files contain
databases of network, protocol and service names. These files
are unused by the TCP/IP Protocol Suite (Release 2), and are provided
to support any extra software that uses TCP/IP protocols.
</UL>
<P>
The files specify the default values normally used on all computers
that support the TCP/IP protocols; consequently, you shouldn't
ever need to edit them. If you do, you should see respectively
the UNIX networks, protocols, and services manual pages.
<P>
There are also more configuration files which can be modified
and they are as follows:
<P>
<TABLE >
<TR><TD WIDTH=312><B>Filename</B></TD><TD WIDTH=256><B>Leafname</B>
</TD></TR>
<TR><TD WIDTH=312><TT><FONT FACE="Courier">$.!Boot.Choices.Internet.routes</FONT></TT> 
</TD><TD WIDTH=256>routes</TD></TR>
<TR><TD WIDTH=312><TT><FONT FACE="Courier">$.!Boot.Choices.Internet.startup</FONT></TT> 
</TD><TD WIDTH=256>startup</TD></TR>
<TR><TD WIDTH=312><TT><FONT FACE="Courier">$.!Boot.Choices.Internet.user</FONT></TT> 
</TD><TD WIDTH=256>user</TD></TR>
</TABLE>
<H3>What these files do</H3>
<P>
Any extra *Route commands, apart from the default route that can
be set using !InetConf can be put into the routes file.
<P>
The user file is generated by InetSetup which includes the configurations
set by the user. It shouldn't be edited by hand unless you know
what you're doing.
<P>
Any special configuration options that cannot be set using !InetConf
can be put into the startup file. It is executed immediately after
the automatically generated Startup file.
<H3>InetSetup Configuration </H3>
<P>
InetSetup does most of the configuration of the software. It sets
the principal host name of a computer. It configures each interface
setting their Internet addresses, their netmasks, the driver modules
to be used and establishes the routing information. It also defines
where to find the configuration files for the databases. Finally,
it sets whether or not the station will forward packets between
multiple interfaces, and hence whether it acts as a TCP/IP gateway.
<H2><A NAME="Different">Different</A> ways to configure the software
</H2>
<P>
There are some decisions you have to make on how to configure
the software. This section outlines what those decisions are.
For details of how to configure the choices you make, see <A HREF="#TCP">Installing the TCP/IP Protocol within OmniClient</A>,
and the instructions and examples in the files you'll need to
edit.
<H3>Ways to set the Internet address of each interface</H3>
<P>
You can set the Internet address of each interface in three ways:
<UL>
<LI>you can set it explicitly on the computer to which it's fitted
<LI>you can use the interface name to look up the Internet address
in the hosts database
<LI>you can use the physical address to look up the Internet address
using Reverse ARP exchanges with an ARP server.
</UL>
<H3>Ways to establish <A NAME="routing">routing </A> information
</H3>
<P>
If you are using gateways, you need to ensure that each RISC OS computer knows its location, and the route to subnets other
than the one to which it is connected. There are three ways you
can do this:
<UL>
<LI>Use the *Route command to explicitly define the routing of
each gateway. For example:
</UL>
<P>
<IMG SRC="pics/DIAGRAM" WIDTH=640 HEIGHT=286>
<BR>
<H2>Installing the <A NAME="TCP">TCP</A>/IP Protocol within OmniClient
</H2>
<H3>Backing up the <A NAME="distrib">distrib</A>ution discs</H3>
<P>
In setting up stations you'll need to alter the software<B>. You
must not alter the distribution discs themselves</B>; always work
on copies of them, made either on media that you can access from
other computers (i.e. an Acorn file server) or that you can take
to other computers (i.e. a floppy disc):
<UL>
<LI>If your RISC OS computers can access an Acorn file server,
make a directory on the file server called (say) TCP_IP, and open
its directory display. Put the Network distribution disc in the
floppy drive, open its directory display, select all the files
and drag them to the TCP-_IP directory display. Dismount the floppy
disc. Repeat this process for the Applications distribution disc.
<LI>Alternatively, use the Backup option from the floppy disc
drive's icon bar menu to back up the two distribution discs to
another pair of floppy discs.
</UL>
<H3>Where you can install the software</H3>
<P>
When you actually install the software for a particular station,
you can do so on any media you like, such as a hard disc, floppy
discs or a remote file server. All that is important is that you
preserve the directory structure that is on the distribution discs
- things that are in the same directory must stay together.
<UL>
<LI>If you're installing the software on a hard disc or an Acorn
file server, we suggest you make a directory called (say) TCP_IP
to hold the software. This directory can be anywhere you like
- it needn't be in the root directory.
<LI>You don't have to do this, and may prefer to put the software
in a directory that already contains other applications.
</UL>
<H3>Configuring the software</H3>
<P>
Run !InetSetup and the required configuration changes can simply
be made by following the necessary menus and entering the details
as required:
<UL>
<LI>AUN 
<LI>Access 
<LI>Internet
</UL>
<H3>Edit the Hosts file</H3>
<P>
If you need to edit the hosts file this can be done through the
Internet-Host names option and then double-clicking on the Hosts
file.
<P>
Edit the file so that it contains the Internet addresses and host
names of all the RISC OS computers you wish to refer to by host
name. (If a computer's host name isn't in here you'll instead
have to use its Internet address whenever you want to communicate).
<P>
If you want to add any UNIX hosts to the file, their addresses
and names must match those in your UNIX /etc/hosts files. For
a small number of hosts you'll probably find it best just to print
out and copy a UNIX hosts file. For a larger number of hosts,
you might find it better to copy across your UNIX hosts file later.
<P>
If you need help, see the comments in the supplied hosts file,
and the UNIX hosts manual page.
<P>
After you have finished editing the hosts file and the required
updates have been made you simply save the file so the changes
can take effect.
<H2>Further Reading</H2>
<P>
The following variables are used to configure the software but
are for further reading purposes only:
<P>
<TABLE >
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><B>Variable</B></TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360><B>Notes</B>
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$EaCount</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the number of Ethernet cards present
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$Email</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the email address associated with the machine.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$EtherDevice</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the driver module to be used to interface the TCP/IP software with your Ethernet interface
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$EtherIPAddr</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets whether your station has an Ethernet interface that you wish to configure for use with TCP/IP, and (if so) sets the Internet address, or specifies that it be looked up using Reverse ARP.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$EtherIPMas</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the netmask for an Ethernet interface; the default is correct for most cases.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$EtherType</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the type of Ethernet device used.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$HostName</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets a station's principal hot name
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$IsGateway</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets whether the machine is to forward IP packets, and hence whether it will act as a <A NAME="gateway">gateway</A>.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$LocalAddr</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the local address of the machine.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$LocalDomain</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the local domain of the machine.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$MimeMappings</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the mapping of content types to file types.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$Path</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the pathname of the directory containing the Internet application.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$Resolvers</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the Internet resolver module IP addresses.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$RouteDOptions</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets whether RouteD - the Internet routing module - is run and (if so) with what options.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$Started</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets whether the Internet application has started or not.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">Inet$Startup</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the pathname for the startup file.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">InetDBase$Path</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the pathname of the directory containing the database files.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">InetLogs$Path</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the pathname of a directory containing the logs file.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">InetSetup$Dir</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the directory of the inetsetup file.
</TD></TR>
<TR><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=208><TT><FONT FACE="Courier">InetSpool$Path</FONT></TT> 
</TD><TD ALIGN="LEFT" VALIGN="TOP" WIDTH=360>This sets the pathname of the directory containing the spool file.
</TD></TR>
</TABLE>
<P>
<A HREF="6_filemap"><IMG SRC="pics/PREV.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="Front"><IMG SRC="pics/FRONT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="TOC"><IMG SRC="pics/CONTS.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="index"><IMG SRC="pics/INDEX.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<A HREF="8_AppxB"><IMG SRC="pics/NEXT.GIF" HEIGHT="28" WIDTH="96" BORDER="0"></A>
<P>
</BODY>
</HTML>
