old-www/LDP/nag2/x-087-2-issues.interfaces.html

189 lines
3.5 KiB
HTML

<HTML
><HEAD
><TITLE
>Networking Interfaces</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"><LINK
REL="HOME"
TITLE="Linux Network Administrators Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Issues of TCP/IP Networking"
HREF="x-087-2-issues.html"><LINK
REL="PREVIOUS"
TITLE="Issues of TCP/IP Networking"
HREF="x-087-2-issues.html"><LINK
REL="NEXT"
TITLE="IP Addresses"
HREF="x-087-2-issues.ip-addresses.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 Network Administrators Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="x-087-2-issues.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 2. Issues of TCP/IP Networking</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x-087-2-issues.ip-addresses.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="X-087-2-ISSUES.INTERFACES"
>2.1. Networking Interfaces</A
></H1
><P
>To hide the diversity of equipment that may be used in a networking
environment, TCP/IP defines an abstract <I
CLASS="EMPHASIS"
>interface</I
>
through which the hardware is accessed. This interface offers a set of
operations that is the same for all types of hardware and basically deals
with sending and receiving packets.</P
><P
>For each peripheral networking device, a corresponding interface has
to be present in the kernel. For example, Ethernet interfaces in Linux
are called by such names as <TT
CLASS="FILENAME"
>eth0</TT
> and
<TT
CLASS="FILENAME"
>eth1</TT
>; PPP (discussed in <A
HREF="x-087-2-ppp.html"
>Chapter 8</A
>&#8201;) interfaces are named <TT
CLASS="FILENAME"
>ppp0</TT
>
and <TT
CLASS="FILENAME"
>ppp1</TT
>; and FDDI interfaces are given names
like <TT
CLASS="FILENAME"
>fddi0</TT
> and <TT
CLASS="FILENAME"
>fddi1</TT
>. These
interface names are used for configuration purposes when you want to
specify a particular physical device in a configuration command, and
they have no meaning beyond this use.</P
><P
>Before being used by TCP/IP networking, an interface must be assigned
an IP address that serves as its identification when communicating
with the rest of the world. This address is different from the
interface name mentioned previously; if you compare an interface to a
door, the address is like the nameplate pinned on it.</P
><P
>&#13;Other device parameters may be set, like the maximum size of datagrams
that can be processed by a particular piece of hardware, which is referred
to as <I
CLASS="EMPHASIS"
>Maximum Transfer Unit</I
> (MTU). Other attributes
will be introduced later. Fortunately, most attributes have sensible defaults.</P
></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="x-087-2-issues.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="x-087-2-issues.ip-addresses.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Issues of TCP/IP Networking</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="x-087-2-issues.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>IP Addresses</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>