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

Fix title capitalization, abbreviations, spelling, and a missing </para>

Browse source 
tag.

Approved by:	gjb (mentor)
This commit is contained in:
Warren Block 2012-01-24 15:56:06 +00:00
parent 2525bfe454
commit 703fd01a72
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=38300
1 changed files with 26 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -180,7 +180,7 @@ host2.example.com link#1 UC 0 0
<para>Both of these groups (local network hosts and local subnets) have
their routes automatically configured by a daemon called
<application>routed</application>. If this is not run, then only
routes which are statically defined (i.e. entered explicitly) will
routes which are statically defined (i.e., entered explicitly) will
exist.</para>
<para>The <literal>host1</literal> line refers to our host, which it
@ -627,7 +627,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
sites are unable to connect to you. Perhaps the most useful command
for trying to figure out where routing is breaking down is the
&man.traceroute.8; command. It is equally useful if you cannot seem
to make a connection to a remote machine (i.e. &man.ping.8;
to make a connection to a remote machine (i.e., &man.ping.8;
fails).</para>
<para>The &man.traceroute.8; command is run with the name of the remote
@ -1660,7 +1660,7 @@ wlan0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; mtu 1500
<callout arearefs="co-peap-cacert">
<para>The <literal>ca_cert</literal> field indicates
the pathname of the CA certificate file. This file
is needed to verify the server certificat.</para>
is needed to verify the server certificate.</para>
</callout>
<callout arearefs="co-peap-pha1">
@ -1911,7 +1911,7 @@ ifconfig_wlan0="inet <replaceable>192.168.0.1</replaceable> netmask <replaceable
</sect3>
<sect3>
<title>Host-based Access Point without Authentication or
<title>Host-based Access Point Without Authentication or
Encryption</title>
<para>Although it is not recommended to run an AP without any
@ -2147,7 +2147,7 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
</sect2>
<sect2>
<title>Using both wired and wireless connection</title>
<title>Using Both Wired and Wireless Connection</title>
<para>Wired connection provides better performance and reliability,
while wireless connection provides flexibility and mobility,
@ -2256,7 +2256,7 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
Networks are usually formed ad-hoc from portable devices such as
cellular phones, handhelds and laptops. Unlike the other popular
wireless technology, Wi-Fi, Bluetooth offers higher level service
profiles, e.g. FTP-like file servers, file pushing, voice transport,
profiles, e.g., FTP-like file servers, file pushing, voice transport,
serial line emulation, and more.</para>
<para>The Bluetooth stack in &os; is implemented using the Netgraph
@ -2322,7 +2322,7 @@ Number of SCO packets: 8</screen>
control registers. This interface provides a uniform method of accessing
the Bluetooth baseband capabilities. HCI layer on the Host exchanges
data and commands with the HCI firmware on the Bluetooth hardware.
The Host Controller Transport Layer (i.e. physical bus) driver provides
The Host Controller Transport Layer (i.e., physical bus) driver provides
both HCI layers with the ability to exchange information with each
other.</para>
@ -2771,7 +2771,7 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<title>Troubleshooting</title>
<sect3>
<title>A remote device cannot connect</title>
<title>A Remote Device Cannot Connect</title>
<para>Some older Bluetooth devices do not support role switching.
By default, when &os; is accepting a new connection, it tries to
perform a role switch and become master. Devices, which do not
@ -2786,7 +2786,7 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
</sect3>
<sect3>
<title>Something is going wrong, can I see what exactly is happening?</title>
<title>Something is Going Wrong, Can I See What Exactly is Happening?</title>
<para>Yes, you can. Use the third-party package
<application>hcidump</application>, which is available as
<filename role="package">comms/hcidump</filename> port.
@ -3152,7 +3152,7 @@ bridge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1
</sect3>
<sect3>
<title>Address limits</title>
<title>Address Limits</title>
<para>The number of unique source MAC addresses behind an
interface can be limited. Once the limit is reached packets
@ -3356,7 +3356,7 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
<title>Examples</title>
<example id="networking-lacp-aggregation-cisco">
<title>LACP aggregation with a &cisco; Switch</title>
<title>LACP Aggregation with a &cisco; Switch</title>
<para>This example connects two interfaces on a &os; machine to the
switch as a single load balanced and fault tolerant link. More interfaces
@ -3439,7 +3439,7 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto lacp lag
</programlisting>
</example>
<example id="networking-lagg-failover">
<title>Failover mode</title>
<title>Failover Mode</title>
<para>Failover mode can be used to switch over to a secondary interface if
the link is lost on the master interface. Bring the underlying
@ -3484,7 +3484,7 @@ ifconfig_<literal>lagg<replaceable>0</replaceable></literal>="laggproto failover
</programlisting>
</example>
<example id="networking-lagg-wired-and-wireless">
<title>Failover mode between wired and wireless interfaces</title>
<title>Failover Mode Between Wired and Wireless Interfaces</title>
<para>For laptop users, it is usually desirable to make wireless as a
secondary interface, which is to be used when the wired connection
@ -3934,7 +3934,7 @@ margaux:ha=0123456789ab:tc=.def100
role="package">net/etherboot</filename> package or port.</para>
<para>You can change the <application>Etherboot</application>
configuration (i.e. to use <acronym>TFTP</acronym> instead of
configuration (i.e., to use <acronym>TFTP</acronym> instead of
<acronym>NFS</acronym>) by editing the <filename>Config</filename>
file in the <application>Etherboot</application> source
directory.</para>
@ -4001,7 +4001,7 @@ margaux:ha=0123456789ab:tc=.def100
<procedure>
<step>
<para>Create a directory from which <application>tftpd</application>
will serve the files, e.g. <filename>/tftpboot</filename>.</para>
will serve the files, e.g., <filename>/tftpboot</filename>.</para>
</step>
<step>
@ -4127,7 +4127,7 @@ options BOOTP_NFSROOT # NFS mount root file system using BOOTP info
<filename>dhcpd.conf</filename>.</para>
<sect4>
<title>Using <command>make world</command> to populate root</title>
<title>Using <command>make world</command> to Populate Root</title>
<para>This method is quick and
will install a complete virgin system (not only the root file system)
@ -4223,7 +4223,7 @@ cd /usr/src/etc; make distribution</programlisting>
</author>
</authorgroup>
</sect1info>
<title>PXE Booting with an NFS root file system</title>
<title>PXE Booting with an NFS Root File System</title>
<para>The &intel; Preboot eXecution Environment (<acronym>PXE</acronym>)
allows booting the operating system over the network.
@ -4248,7 +4248,7 @@ cd /usr/src/etc; make distribution</programlisting>
the &os; booting process.</para>
<sect2>
<title>Setting Up the <command>chroot</command> Environment for the NFS Root File system</title>
<title>Setting Up the <command>chroot</command> Environment for the NFS Root File System</title>
<procedure>
<step>
@ -4349,7 +4349,7 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
<screen>&prompt.root; <userinput>chroot ${NFSROOTDIR}</userinput>
&prompt.root; <userinput>passwd</userinput></screen>
<para>This will set the root password for client machines
which are <acronym>PXE</acronym> booting.
which are <acronym>PXE</acronym> booting.</para>
</step>
<step>
@ -4375,7 +4375,7 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
</sect2>
<sect2>
<title>Configuring Memory File Systems used by <filename>/etc/rc.initdiskless</filename></title>
<title>Configuring Memory File Systems Used by <filename>/etc/rc.initdiskless</filename></title>
<para>If you boot from an NFS root volume,
<filename>/etc/rc</filename>
@ -4453,7 +4453,7 @@ subnet 192.168.0.0 netmask 255.255.255.0 {
</sect2>
<sect2>
<title>Configuring the PXE client and Debugging Connection Problems</title>
<title>Configuring the PXE Client and Debugging Connection Problems</title>
<procedure>
<step>
@ -5522,7 +5522,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
by multicast addresses in IPv6.</para></note>
<table frame="none">
<title>Reserved IPv6 addresses</title>
<title>Reserved IPv6 Addresses</title>
<tgroup cols="4">
<thead>
@ -5696,7 +5696,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
</sect2>
<sect2>
<title>Applying the needed changes to <filename>/etc/rc.conf</filename></title>
<title>Applying the Needed Changes to <filename>/etc/rc.conf</filename></title>
<sect3>
<title>IPv6 Client Settings</title>
@ -5814,7 +5814,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
<title>Asynchronous Transfer Mode (ATM)</title>
<sect2>
<title>Configuring classical IP over ATM (PVCs)</title>
<title>Configuring Classical IP over ATM (PVCs)</title>
<para>Classical IP over ATM (<acronym>CLIP</acronym>) is the
simplest method to use Asynchronous Transfer Mode (ATM)
@ -5824,7 +5824,7 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
on PVCs.</para>
<sect3>
<title>Fully meshed configurations</title>
<title>Fully Meshed Configurations</title>
<para>The first method to set up a <acronym>CLIP</acronym> with
PVCs is to connect each machine to each other machine in the
@ -6082,7 +6082,7 @@ route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"</programlisting>
used to distinguish the host on the network.</para>
<sect2>
<title>Using CARP For Server Availability (CARP)</title>
<title>Using CARP for Server Availability (CARP)</title>
<para>One use of <acronym>CARP</acronym>, as noted above, is for
server availability. This example will provide failover support