Reword a couple of sentences that I found very confusing. Often this

was due to missing words or sentences that made it very difficult to
understand the text.
This commit is contained in:
Murray Stokely 2001-08-24 07:27:05 +00:00
parent 9adf756449
commit f0042b1654
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10466

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.94 2001/08/22 21:36:25 chern Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.95 2001/08/22 21:40:11 chern Exp $
-->
<chapter id="advanced-networking">
@ -88,7 +88,7 @@
<para>For one machine to be able to find another over a network, there
must be a
mechanism in place to describe how to get from one to the other. This is
called Routing. A <quote>route</quote> is a defined pair of addresses: a
called <firstterm>routing</firstterm>. A <quote>route</quote> is a defined pair of addresses: a
<quote>destination</quote> and a <quote>gateway</quote>. The pair
indicates that if you are trying to get to this
<emphasis>destination</emphasis>, communicate through this
@ -254,8 +254,8 @@ host2.foobar.com link#1 UC 0 0
route (usually the only one present in the system), and is always
marked with a <literal>c</literal> in the flags field. For hosts on a
local area network, this gateway is set to whatever machine has a
direct connection to the outside world (whether via PPP link, or your
hardware device attached to a dedicated data line).</para>
direct connection to the outside world (whether via PPP link,
DSL, cable modem, T1, or another network interface).</para>
<para>If you are configuring the default route for a machine which
itself is functioning as the gateway to the outside world, then the
@ -269,11 +269,12 @@ host2.foobar.com link#1 UC 0 0
[Local2] &lt;--ether--&gt; [Local1] &lt;--PPP--&gt; [ISP-Serv] &lt;--ether--&gt; [T1-GW]
</literallayout>
<para>The hosts <hostid>Local1</hostid> and <hostid>Local2</hostid> are
at your site, with the formed being your PPP connection to your ISP's
Terminal Server. Your ISP has a local network at their site, which
has, among other things, the server where you connect and a hardware
device (T1-GW) attached to the ISP's Internet feed.</para>
<para>The hosts <hostid>Local1</hostid> and
<hostid>Local2</hostid> are at your site.
<hostid>Local1</hostid> is connected to an ISP via a dial up
PPP connection. This PPP server computer is connected through
a local area network to another gateway computer with an
external interface to the ISPs Internet feed.</para>
<para>The default routes for each of your machines will be:</para>
@ -315,7 +316,7 @@ host2.foobar.com link#1 UC 0 0
server.</para>
<para>As a final note, it is common to use the address <hostid
role="ipaddr">...1</hostid> as the gateway address for your local
role="ipaddr">X.X.X.1</hostid> as the gateway address for your local
network. So (using the same example), if your local class-C address
space was <hostid role="ipaddr">10.20.30</hostid> and your ISP was
using <hostid role="ipaddr">10.9.9</hostid> then the default routes
@ -1549,9 +1550,9 @@ hostname myclient.mydomain</programlisting>
<para>As the cost of low end ISDN routers/bridges comes down, it
will likely become a more and more popular choice. An ISDN
router is a small box that plugs directly into your local
Ethernet network(or card), and manages its own connection to
the other bridge/router. It has all the software to do PPP
and other protocols built in.</para>
Ethernet network, and manages its own connection to the other
bridge/router. It has built in software to communicate via
PPP and other popular protocols.</para>
<para>A router will allow you much faster throughput that a
standard TA, since it will be using a full synchronous ISDN
@ -1816,7 +1817,7 @@ ISDN BRI line</literallayout>
and <filename>hosts</filename> files are commonly shared via NIS.
Whenever a process on a client needs information that would
normally be found in these files locally, it makes a query to the
server it is bound to, to get this information.</para>
NIS server that it is bound to instead.</para>
<sect3>
<title>Machine Types</title>