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

* Add id="" attributes to some sect3 elements that didn't have any.

Browse source 
* Move a few <indexterm> elements before the paragraph that mentions
  them.  I'm not sure if this has any effect on the index link
  location, but we usually write index terms before the relevant
  paragraph.
This commit is contained in:
Giorgos Keramidas 2008-12-10 17:38:07 +00:00
parent e77076083e
commit 6a337ea69f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=33404
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -383,8 +383,9 @@ host2.example.com link#1 UC 0 0
routing tables, consult &man.route.8; manual page.</para>
</sect2>
<sect2>
<sect2 id="network-dual-homed-hosts">
<title>Dual Homed Hosts</title>
<indexterm><primary>dual homed hosts</primary></indexterm>
<para>There is one other type of configuration that we should cover, and
that is a host that sits on two different networks. Technically, any
@ -433,6 +434,9 @@ host2.example.com link#1 UC 0 0
<literal>1</literal>. If you should need to stop routing
temporarily, you can reset this to <literal>0</literal> temporarily.</para>
<indexterm><primary>BGP</primary></indexterm>
<indexterm><primary>RIP</primary></indexterm>
<indexterm><primary>OSPF</primary></indexterm>
<para>Your new router will need routes to know where to send the
traffic. If your network is simple enough you can use static
routes. FreeBSD also comes with the standard BSD routing
@ -442,13 +446,9 @@ host2.example.com link#1 UC 0 0
<filename role="package">net/zebra</filename> package.
Commercial products such as <application>&gated;</application> are also available for more
complex network routing solutions.</para>
<indexterm><primary>BGP</primary></indexterm>
<indexterm><primary>RIP</primary></indexterm>
<indexterm><primary>OSPF</primary></indexterm>
</sect2>
<sect2>
<sect2 id="network-static-routes">
<sect2info>
<authorgroup>
<author>
@ -583,7 +583,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
</sect3>
</sect2>
<sect2>
<sect2 id="network-routing-propagation">
<title>Routing Propagation</title>
<indexterm><primary>routing propagation</primary></indexterm>
<para>We have already talked about how we define our routes to the
@ -614,7 +614,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
propagation.</para>
</sect2>
<sect2>
<sect2 id="network-routing-troubleshooting">
<title>Troubleshooting</title>
<indexterm>
<primary><command>traceroute</command></primary>
@ -635,7 +635,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
&man.traceroute.8;.</para>
</sect2>
<sect2>
<sect2 id="network-routing-multicast">
<title>Multicast Routing</title>
<indexterm>
<primary>multicast routing</primary>