os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

The author of this section was slightly confused about the terminology

Browse source 
used to describe network topology.  Change instances of '10 base T' to
'10 base 2' and adjust sentence structure when describing a bus-based
topology.

While I'm here, consistently use 'LAN' instead of 'lan' for local area
networks.
This commit is contained in:
Murray Stokely 2001-06-24 03:22:48 +00:00
parent 506d3469cb
commit ca002b6606
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=9686
1 changed files with 38 additions and 34 deletions
Download patch file Download diff file Expand all files Collapse all files

72
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.46 2001/06/23 22:46:15 murray Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.47 2001/06/24 03:06:38 murray Exp $
-->
<chapter id="advanced-networking">
@ -1073,8 +1073,6 @@ hostname myclient.mydomain</programlisting>
<sect1 id="isdn">
<title>ISDN</title>
<para><emphasis>Last modified by &a.wlloyd;</emphasis>.</para>
<para>A good resource for information on ISDN technology and hardware is
<ulink url="http://alumni.caltech.edu/~dank/isdn/">Dan Kegel's ISDN
Page</ulink>.</para>
@ -1221,51 +1219,56 @@ hostname myclient.mydomain</programlisting>
router, and with a simple 386 FreeBSD box driving it, probably more
flexible.</para>
<para>The choice of sync/TA v.s. stand-alone router is largely a religious
issue. There has been some discussion of this in the mailing lists.
I suggest you search the <ulink
url="http://www.FreeBSD.org/search.html">archives</ulink> for the
complete discussion.</para>
<para>The choice of sync/TA v.s. stand-alone router is largely a
religious issue. There has been some discussion of this in
the mailing lists. I suggest you search the <ulink
url="http://www.FreeBSD.org/search.html">archives</ulink> for
the complete discussion.</para>
</sect2>
<sect2>
<title>Stand-alone ISDN Bridges/Routers</title>
<para>ISDN bridges or routers are not at all specific to FreeBSD or any
other operating system. For a more complete description of routing
and bridging technology, please refer to a Networking reference
book.</para>
<para>ISDN bridges or routers are not at all specific to FreeBSD
or any other operating system. For a more complete
description of routing and bridging technology, please refer
to a Networking reference book.</para>
<para>In the context of this page, the terms router and bridge will
be used interchangeably.</para>
<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>
<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>
<para>A router will allow you much faster throughput that a standard TA,
since it will be using a full synchronous ISDN connection.</para>
<para>A router will allow you much faster throughput that a
standard TA, since it will be using a full synchronous ISDN
connection.</para>
<para>The main problem with ISDN routers and bridges is that
interoperability between manufacturers can still be a problem. If you
are planning to connect to an Internet provider, you should
discuss your needs with them.</para>
interoperability between manufacturers can still be a problem.
If you are planning to connect to an Internet provider, you
should discuss your needs with them.</para>
<para>If you are planning to connect two lan segments together, ie: home
lan to the office lan, this is the simplest lowest maintenance
solution. Since you are buying the equipment for both sides of the
connection you can be assured that the link will work.</para>
<para>If you are planning to connect two LAN segments together,
ie: home LAN to the office LAN, this is the simplest lowest
maintenance solution. Since you are buying the equipment for
both sides of the connection you can be assured that the link
will work.</para>
<para>For example to connect a home computer or branch office network to
a head office network the following setup could be used.</para>
<para>For example to connect a home computer or branch office
network to a head office network the following setup could be
used.</para>
<example>
<title>Branch office or Home network</title>
<para>Network is 10 Base T Ethernet. Connect router to network cable
with AUI/10BT transceiver, if necessary.</para>
<para>Network uses a bus based topology with 10 base 2
Ethernet ("thinnet"). Connect router to network cable with
AUI/10BT transceiver, if necessary.</para>
<mediaobject>
<imageobject>
@ -1285,7 +1288,7 @@ ISDN BRI line</literallayout>
</textobject>
<textobject>
<phrase>10 Base T Ethernet</phrase>
<phrase>10 Base 2 Ethernet</phrase>
</textobject>
</mediaobject>
@ -1295,9 +1298,10 @@ ISDN BRI line</literallayout>
</example>
<example>
<title>Head office or other lan</title>
<title>Head office or other LAN</title>
<para>Network is Twisted Pair Ethernet.</para>
<para>Network uses a star topology with 10 base T Ethernet
("Twisted Pair").</para>
<mediaobject>
<imageobject>
@ -2966,7 +2970,7 @@ dhcp_flags=""</programlisting>
<sect3>
<title><filename>/etc/namedb/named.conf</filename></title>
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.46 2001/06/23 22:46:15 murray Exp $
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.47 2001/06/24 03:06:38 murray Exp $
//
// Refer to the named(8) man page for details. If you are ever going
// to setup a primary server, make sure you've understood the hairy