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

Typo/grammar fixes.

Browse source 
This commit can be safely ignored by translators.
This commit is contained in:
Ceri Davies 2002-05-05 14:09:55 +00:00
parent 0e6ea0f2cb
commit e5221761ac
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12963
1 changed files with 18 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -182,17 +182,17 @@ host2.example.com link#1 UC 0 0
rather than sending it out over the Ethernet interface.</para> rather than sending it out over the Ethernet interface.</para>
<para>The two <literal>host2</literal> lines are an example of what <para>The two <literal>host2</literal> lines are an example of what
happens when we use an &man.ifconfig.8; alias (see the section of Ethernet for happens when we use an &man.ifconfig.8; alias (see the section on Ethernet for
reasons why we would do this). The <literal>=&gt;</literal> symbol reasons why we would do this). The <literal>=&gt;</literal> symbol
after the <devicename>lo0</devicename> interface says that not only after the <devicename>lo0</devicename> interface says that not only
are we using the loopback (since this is address also refers to the are we using the loopback (since this address also refers to the
local host), but specifically it is an alias. Such routes only show local host), but specifically it is an alias. Such routes only show
up on the host that supports the alias; all other hosts on the local up on the host that supports the alias; all other hosts on the local
network will simply have a <literal>link#1</literal> line for network will simply have a <literal>link#1</literal> line for
such.</para> such.</para>
<para>The final line (destination subnet <literal>224</literal>) deals <para>The final line (destination subnet <literal>224</literal>) deals
with MultiCasting, which will be covered in a another section.</para> with MultiCasting, which will be covered in another section.</para>
<para>The other column that we should talk about are the <para>The other column that we should talk about are the
<literal>Flags</literal>. Each route has different attributes that <literal>Flags</literal>. Each route has different attributes that
@ -252,7 +252,7 @@ host2.example.com link#1 UC 0 0
<title>Default Routes</title> <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 remote host, <para>When the local system needs to make a connection to a remote host,
it checks the routing table to determine if a known path exists. If it checks the routing table to determine if a known path exists. If
the remote host falls into a subnet that we know how to reach (Cloned the remote host falls into a subnet that we know how to reach (Cloned
routes), then the system checks to see if it can connect along that routes), then the system checks to see if it can connect along that
@ -396,7 +396,7 @@ host2.example.com link#1 UC 0 0
<programlisting>gateway_enable=YES # Set to YES if this host will be a gateway</programlisting> <programlisting>gateway_enable=YES # Set to YES if this host will be a gateway</programlisting>
<para>This option will put the &man.sysctl.8; variable <para>This option will set the &man.sysctl.8; variable
<filename>net.inet.ip.forwarding</filename> to <filename>net.inet.ip.forwarding</filename> to
<literal>1</literal>. If you should need to stop routing <literal>1</literal>. If you should need to stop routing
temporarily, you can reset this to 0 temporarily.</para> temporarily, you can reset this to 0 temporarily.</para>
@ -452,7 +452,7 @@ host2.example.com link#1 UC 0 0
</indexterm> </indexterm>
<para>Sometimes, there is a problem with routing propagation, and some <para>Sometimes, there is a problem with routing propagation, and some
sites are unable to connect to you. Perhaps the most useful command sites are unable to connect to you. Perhaps the most useful command
for trying to figure out where a routing is breaking down is the for trying to figure out where routing is breaking down is the
&man.traceroute.8; command. It is equally useful if you cannot seem &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> fails).</para>
@ -616,7 +616,7 @@ host2.example.com link#1 UC 0 0
<para>to <filename>/etc/sysctl.conf</filename> to enable the bridge at <para>to <filename>/etc/sysctl.conf</filename> to enable the bridge at
runtime. If you want the bridged packets to be filtered by &man.ipfw.8;, runtime. If you want the bridged packets to be filtered by &man.ipfw.8;,
you should also add:</para> you should add:</para>
<programlisting>net.link.ether.bridge_ipfw=1</programlisting> <programlisting>net.link.ether.bridge_ipfw=1</programlisting>
@ -1798,7 +1798,7 @@ Exports list on foobar:
linkend="ppp">PPP</link> option, not the user-land <link linkend="ppp">PPP</link> option, not the user-land <link
linkend="userppp">iijPPP</link>.</para> linkend="userppp">iijPPP</link>.</para>
<para>The following TA's are know to work with FreeBSD.</para> <para>The following TA's are known to work with FreeBSD.</para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
@ -1814,7 +1814,7 @@ Exports list on foobar:
sure their product can accept most of the standard modem AT command sure their product can accept most of the standard modem AT command
set.</para> set.</para>
<para>The real problem with external TA's is like modems you need a good <para>The real problem with external TA's is that, like modems, you need a good
serial card in your computer.</para> serial card in your computer.</para>
<para>You should read the <ulink <para>You should read the <ulink
@ -1866,7 +1866,7 @@ Exports list on foobar:
bridge/router. It has built in software to communicate via bridge/router. It has built in software to communicate via
PPP and other popular protocols.</para> PPP and other popular protocols.</para>
<para>A router will allow you much faster throughput that a <para>A router will allow you much faster throughput than a
standard TA, since it will be using a full synchronous ISDN standard TA, since it will be using a full synchronous ISDN
connection.</para> connection.</para>
@ -1961,7 +1961,7 @@ ISDN BRI line</literallayout>
have two serial ports. Do not confuse this with channel bonding, MPP, have two serial ports. Do not confuse this with channel bonding, MPP,
etc.</para> etc.</para>
<para>This can be very useful feature if, for example, you have an <para>This can be a very useful feature if, for example, you have an
dedicated ISDN connection at your office and would like to dedicated ISDN connection at your office and would like to
tap into it, but do not want to get another ISDN line at work. A router tap into it, but do not want to get another ISDN line at work. A router
at the office location can manage a dedicated B channel connection at the office location can manage a dedicated B channel connection
@ -2043,7 +2043,7 @@ ISDN BRI line</literallayout>
<para>There are several terms and several important user processes <para>There are several terms and several important user processes
that you will come across when that you will come across when
attempting to implement NIS on FreeBSD, whether you are trying to attempting to implement NIS on FreeBSD, whether you are trying to
create an NIS server or act an NIS client:</para> create an NIS server or act as an NIS client:</para>
<indexterm> <indexterm>
<primary><application>portmap</application></primary> <primary><application>portmap</application></primary>
@ -2370,7 +2370,7 @@ ISDN BRI line</literallayout>
<para>Now, all you have to do is to run the command <para>Now, all you have to do is to run the command
<command>/etc/netstart</command> as superuser. It will <command>/etc/netstart</command> as superuser. It will
setup everything for you, using the values you defined in set up everything for you, using the values you defined in
<filename>/etc/rc.conf</filename>.</para> <filename>/etc/rc.conf</filename>.</para>
</sect4> </sect4>
@ -2955,7 +2955,7 @@ INTERNS (,able,test-domain) (,baker,test-domain)</programlisting>
<listitem> <listitem>
<para>The NIS domain for the account. You can import <para>The NIS domain for the account. You can import
accounts from other NIS domains into your netgroup if you accounts from other NIS domains into your netgroup if you
are one of unlucky fellows with more than one NIS are one of the unlucky fellows with more than one NIS
domain.</para> domain.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
@ -3170,7 +3170,7 @@ TWO (,hotel,test-domain)
will automatically have access to the boxes.</para> will automatically have access to the boxes.</para>
<para>One last word of caution: It may not always be advisable <para>One last word of caution: It may not always be advisable
to use machine-based netgroups. If you are deploying a couple to use machine-based netgroups. If you are deploying a couple of
dozen or even hundreds of identical machines for student labs, dozen or even hundreds of identical machines for student labs,
you should use role-based netgroups instead of machine-based you should use role-based netgroups instead of machine-based
netgroups to keep the size of the NIS map within reasonable netgroups to keep the size of the NIS map within reasonable
@ -3248,7 +3248,7 @@ TWO (,hotel,test-domain)
generally a good idea to force the servers to bind to themselves generally a good idea to force the servers to bind to themselves
rather than allowing them to broadcast bind requests and possibly rather than allowing them to broadcast bind requests and possibly
become bound to each other. Strange failure modes can result if become bound to each other. Strange failure modes can result if
one server goes down and others are dependent upon on it. one server goes down and others are dependent upon it.
Eventually all the clients will time out and attempt to bind to Eventually all the clients will time out and attempt to bind to
other servers, but the delay involved can be considerable and the other servers, but the delay involved can be considerable and the
failure mode is still present since the servers might bind to each failure mode is still present since the servers might bind to each
@ -4275,7 +4275,7 @@ www IN CNAME @
<varlistentry> <varlistentry>
<term>MX</term> <term>MX</term>
<listitem><para>mail exchange</para></listitem> <listitem><para>mail exchanger</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
@ -4971,7 +4971,7 @@ driftfile /var/db/ntp.drift</programlisting>
<note> <note>
<para>Some Internet access providers block low-numbered ports, <para>Some Internet access providers block low-numbered ports,
preventing NTP from from functioning since replies never preventing NTP from functioning since replies never
reach your machine.</para> reach your machine.</para>
</note> </note>
</sect2> </sect2>