62 lines
2.6 KiB
HTML
62 lines
2.6 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
|
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>Interface Configuration for IP</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node66.html">The Loopback Interface</A>
|
|
<B>Up:</B> <A HREF="node58.html">Configuring TCP/IP Networking</A>
|
|
<B> Previous:</B> <A HREF="node64.html">Writing hosts and networks </A>
|
|
<BR> <P>
|
|
<H1><A NAME="SECTION007700000">Interface Configuration for IP</A></H1>
|
|
After setting up your hardware as explained in the previous chapter, you
|
|
have to make these devices known to the kernel networking software. A
|
|
couple of commands are used to configure the network interfaces, and
|
|
initialize the routing table. These tasks are usually performed from the
|
|
rc.inet1 script each time the system is booted. The basic tools for
|
|
this are called <A HREF="node73.html">ifconfig</A> (where ``if'' stands for interface), and
|
|
route.
|
|
<P>
|
|
ifconfig is used to make an interface accessible to the kernel
|
|
networking layer. This involves the assignment of an IP-address and other
|
|
parameters, and activating the interface, also known as ``taking up.''
|
|
Being active here means that the kernel will send and receive IP-datagrams
|
|
through the interface. The simplest way to invoking it is
|
|
<Pre>
|
|
ifconfig interface ip-address
|
|
|
|
</Pre>
|
|
which assigns ip-address to interface and activates it.
|
|
All other parameters are set to default values. For instance, the
|
|
default subnet mask is derived from the network class of the IP-address,
|
|
such as 255.255.0.0 for a class-B address. ifconfig is
|
|
described in detail at the end of this chapter.
|
|
<P>
|
|
route allows you to add or remove routes from the kernel routing
|
|
table. It can be invoked as
|
|
<Pre>
|
|
route [add|del] target
|
|
</Pre>
|
|
where the add and del arguments determine whether
|
|
to add or delete the route to target.
|
|
|
|
<HR>
|
|
<UL>
|
|
<LI> <A HREF="node66.html#SECTION007710000">The Loopback Interface</A>
|
|
<LI> <A HREF="node67.html#SECTION007720000">Ethernet Interfaces</A>
|
|
<LI> <A HREF="node68.html#SECTION007730000">Routing through a Gateway</A>
|
|
<LI> <A HREF="node69.html#SECTION007740000">Configuring a Gateway</A>
|
|
<LI> <A HREF="node70.html#SECTION007750000">The PLIP Interface</A>
|
|
<LI> <A HREF="node71.html#SECTION007760000">The SLIP and PPP Interface</A>
|
|
<LI> <A HREF="node72.html#SECTION007770000">The Dummy Interface</A>
|
|
</UL>
|
|
<BR> <HR>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|