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

Whitespace-only fixes. Modified version of patch from Allan Jude

Browse source 
<freebsd@allanjude.com>.
This commit is contained in:
Warren Block 2014-02-18 00:11:34 +00:00
parent 67eb13536b
commit cc0a9ecafc
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=43973
1 changed files with 121 additions and 37 deletions

158
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
View file

@ -103,9 +103,15 @@
</authorgroup>
</info>
<indexterm><primary>routing</primary></indexterm>
<indexterm><primary>gateway</primary></indexterm>
<indexterm><primary>subnet</primary></indexterm>
<indexterm>
<primary>routing</primary>
</indexterm>
<indexterm>
<primary>gateway</primary>
</indexterm>
<indexterm>
<primary>subnet</primary>
</indexterm>
<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
@ -143,12 +149,18 @@ host2 0:e0:a8:37:8:1e UHLW 0 5 lo0 =&gt;
host2.example.com link#1 UC 0 0
224 link#1 UC 0 0</screen>
<indexterm><primary>default route</primary></indexterm>
<indexterm>
<primary>default route</primary>
</indexterm>
<para>The first two lines specify the default route, described
in more detail in <xref linkend="network-routing-default"/>,
and the <systemitem>localhost</systemitem> route.</para>
<indexterm><primary>loopback device</primary></indexterm>
<indexterm>
<primary>loopback device</primary>
</indexterm>
<para>The interface (<literal>Netif</literal> column) that this
routing table specifies to use for
<literal>localhost</literal> is <filename>lo0</filename>,
@ -160,6 +172,7 @@ host2.example.com link#1 UC 0 0
<primary>Ethernet</primary>
<secondary>MAC address</secondary>
</indexterm>
<para>The addresses beginning with <systemitem
class="etheraddress">0:e0:</systemitem> are Ethernet
hardware addresses, also known as <acronym>MAC</acronym>
@ -175,7 +188,9 @@ host2.example.com link#1 UC 0 0
calculates routes to local hosts based upon a shortest path
determination.</para>
<indexterm><primary>subnet</primary></indexterm>
<indexterm>
<primary>subnet</primary>
</indexterm>
<para>&os; will add subnet routes for the local subnet.
<systemitem class="ipaddress">10.20.30.255</systemitem> is the
@ -271,7 +286,9 @@ host2.example.com link#1 UC 0 0
<sect2 xml:id="network-routing-default">
<title>Default Routes</title>
<indexterm><primary>default route</primary></indexterm>
<indexterm>
<primary>default route</primary>
</indexterm>
<para>When the local system needs to make a connection to a
remote host, it checks the routing table to determine if a
@ -408,7 +425,9 @@ host2.example.com link#1 UC 0 0
<sect2 xml:id="network-dual-homed-hosts">
<title>Dual Homed Hosts</title>
<indexterm><primary>dual homed hosts</primary></indexterm>
<indexterm>
<primary>dual homed hosts</primary>
</indexterm>
<para>A dual-homed system is a host which resides on two
different networks.</para>
@ -436,7 +455,9 @@ host2.example.com link#1 UC 0 0
<sect2 xml:id="network-dedicated-router">
<title>Building a Router</title>
<indexterm><primary>router</primary></indexterm>
<indexterm>
<primary>router</primary>
</indexterm>
<para>A network router is a system that forwards packets from
one interface to another. Internet standards and good
@ -452,9 +473,16 @@ host2.example.com link#1 UC 0 0
<literal>1</literal>. To stop routing, reset this to
<literal>0</literal>.</para>
<indexterm><primary>BGP</primary></indexterm>
<indexterm><primary>RIP</primary></indexterm>
<indexterm><primary>OSPF</primary></indexterm>
<indexterm>
<primary>BGP</primary>
</indexterm>
<indexterm>
<primary>RIP</primary>
</indexterm>
<indexterm>
<primary>OSPF</primary>
</indexterm>
<para>The new router will need routes to know where to send the
traffic. If the network is simple enough, static routes can
be used. &os; comes with the standard BSD routing daemon
@ -649,6 +677,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
<primary>kernel options</primary>
<secondary>MROUTING</secondary>
</indexterm>
<para>&os; natively supports both multicast applications and
multicast routing. Multicast applications do not require any
special configuration of &os;; as applications will generally
@ -688,7 +717,9 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
</authorgroup>
</info>
<indexterm><primary>wireless networking</primary></indexterm>
<indexterm>
<primary>wireless networking</primary>
</indexterm>
<indexterm>
<primary>802.11</primary>
<see>wireless networking</see>
@ -2247,7 +2278,9 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
<title>USB Tethering</title>
</info>
<indexterm><primary>tether</primary></indexterm>
<indexterm>
<primary>tether</primary>
</indexterm>
<para>Many cellphones provide the option to share their data
connection over USB (often called "tethering"). This feature
@ -2287,7 +2320,10 @@ freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS</screen>
</authorgroup>
</info>
<indexterm><primary>Bluetooth</primary></indexterm>
<indexterm>
<primary>Bluetooth</primary>
</indexterm>
<sect2>
<title>Introduction</title>
@ -2359,7 +2395,9 @@ Number of SCO packets: 8</screen>
<title>Host Controller Interface
(<acronym>HCI</acronym>)</title>
<indexterm><primary>HCI</primary></indexterm>
<indexterm>
<primary>HCI</primary>
</indexterm>
<para>The Host Controller Interface (<acronym>HCI</acronym>)
provides a command interface to the baseband controller and
@ -2453,7 +2491,9 @@ Reason: Connection terminated by local host [0x16]</screen>
<title>Logical Link Control and Adaptation Protocol
(<acronym>L2CAP</acronym>)</title>
<indexterm><primary>L2CAP</primary></indexterm>
<indexterm>
<primary>L2CAP</primary>
</indexterm>
<para>The Logical Link Control and Adaptation Protocol
(<acronym>L2CAP</acronym>) provides connection-oriented and
@ -2627,7 +2667,9 @@ hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:
<title>Service Discovery Protocol
(<acronym>SDP</acronym>)</title>
<indexterm><primary>SDP</primary></indexterm>
<indexterm>
<primary>SDP</primary>
</indexterm>
<para>The Service Discovery Protocol (<acronym>SDP</acronym>)
provides the means for client applications to discover the
@ -2811,7 +2853,10 @@ Bluetooth Profile Descriptor List:
<title><acronym>OBEX</acronym> Object Push
(<acronym>OPUSH</acronym>) Profile</title>
<indexterm><primary>OBEX</primary></indexterm>
<indexterm>
<primary>OBEX</primary>
</indexterm>
<para><acronym>OBEX</acronym> is a widely used protocol for
simple file transfers between mobile devices. Its main use
is in infrared communication, where it is used for generic
@ -2939,9 +2984,13 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<sect2>
<title>Introduction</title>
<indexterm><primary><acronym>IP</acronym>
subnet</primary></indexterm>
<indexterm><primary>bridge</primary></indexterm>
<indexterm>
<primary><acronym>IP</acronym> subnet</primary>
</indexterm>
<indexterm>
<primary>bridge</primary>
</indexterm>
<para>It is sometimes useful to divide one physical network,
such as an Ethernet segment, into two separate network
segments without having to create <acronym>IP</acronym>
@ -2981,8 +3030,12 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
<sect3>
<title>Filtering/Traffic Shaping Firewall</title>
<indexterm><primary>firewall</primary></indexterm>
<indexterm><primary>NAT</primary></indexterm>
<indexterm>
<primary>firewall</primary>
</indexterm>
<indexterm>
<primary>NAT</primary>
</indexterm>
<para>A common situation is where firewall functionality is
needed without routing or Network Address Translation
@ -2996,9 +3049,16 @@ rfcomm_sppd[94692]: Starting on /dev/ttyp6...</screen>
on the network. In this situation, using a router-based
firewall is difficult because of subnetting issues.</para>
<indexterm><primary>router</primary></indexterm>
<indexterm><primary><acronym>DSL</acronym></primary></indexterm>
<indexterm><primary><acronym>ISDN</acronym></primary></indexterm>
<indexterm>
<primary>router</primary>
</indexterm>
<indexterm>
<primary><acronym>DSL</acronym></primary>
</indexterm>
<indexterm>
<primary><acronym>ISDN</acronym></primary>
</indexterm>
<para>A bridge-based firewall can be configured and dropped
into the path just downstream of the <acronym>DSL</acronym>
or <acronym>ISDN</acronym> router without any
@ -3119,7 +3179,9 @@ ifconfig_fxp1="up"</programlisting>
<sect2>
<title>Firewalling</title>
<indexterm><primary>firewall</primary></indexterm>
<indexterm>
<primary>firewall</primary>
</indexterm>
<para>When packet filtering is enabled, bridged packets will
pass through the filter inbound on the originating interface
@ -3406,12 +3468,24 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2</screen>
</authorgroup>
</info>
<indexterm><primary>lagg</primary></indexterm>
<indexterm><primary>failover</primary></indexterm>
<indexterm><primary><acronym>FEC</acronym></primary></indexterm>
<indexterm><primary><acronym>LACP</acronym></primary></indexterm>
<indexterm><primary>loadbalance</primary></indexterm>
<indexterm><primary>roundrobin</primary></indexterm>
<indexterm>
<primary>lagg</primary>
</indexterm>
<indexterm>
<primary>failover</primary>
</indexterm>
<indexterm>
<primary><acronym>FEC</acronym></primary>
</indexterm>
<indexterm>
<primary><acronym>LACP</acronym></primary>
</indexterm>
<indexterm>
<primary>loadbalance</primary>
</indexterm>
<indexterm>
<primary>roundrobin</primary>
</indexterm>
<para>&os; provides the &man.lagg.4; interface which can be used
to aggregate multiple network interfaces into one virtual
@ -3752,8 +3826,12 @@ ifconfig_<literal>lagg0</literal>="laggproto failover laggport <replaceable>bge0
</authorgroup>
</info>
<indexterm><primary>diskless workstation</primary></indexterm>
<indexterm><primary>diskless operation</primary></indexterm>
<indexterm>
<primary>diskless workstation</primary>
</indexterm>
<indexterm>
<primary>diskless operation</primary>
</indexterm>
<para>A &os; machine can boot over the network and operate
without a local disk, using file systems mounted from an
@ -4645,6 +4723,7 @@ Received 264951 bytes in 0.1 seconds</screen>
<indexterm>
<primary>&man.natd.8;</primary>
</indexterm>
<para>&os;'s Network Address Translation
(<acronym>NAT</acronym>) daemon, &man.natd.8;, accepts
incoming raw <acronym>IP</acronym> packets, changes the
@ -4661,6 +4740,7 @@ Received 264951 bytes in 0.1 seconds</screen>
<indexterm>
<primary><acronym>NAT</acronym></primary>
</indexterm>
<para>The most common use of <acronym>NAT</acronym> is to
perform what is commonly known as Internet Connection
Sharing.</para>
@ -4766,6 +4846,7 @@ ipdivert_load="YES"</programlisting>
<primary>kernel</primary>
<secondary>configuration</secondary>
</indexterm>
<para>When modules are not an option or if it is preferable to
build all the required features into a custom kernel, the
following options must be in the custom kernel configuration
@ -4931,7 +5012,10 @@ redirect_port tcp 192.168.0.3:80 80</programlisting>
<sect2 xml:id="network-natdaddress-redirection">
<title>Address Redirection</title>
<indexterm><primary>address redirection</primary></indexterm>
<indexterm>
<primary>address redirection</primary>
</indexterm>
<para>Address redirection is useful if more than one
<acronym>IP</acronym> address is available. Each
<acronym>LAN</acronym> client can be assigned its own