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

Fix spelling mistakes picked up by igor.

Browse source 
Approved by:	bcr (mentor)
Differential Revision:	https://reviews.freebsd.org/D8428
This commit is contained in:
Sevan Janiyan 2016-11-03 19:48:36 +00:00
parent 25a1d3d7bd
commit 9b207cb155
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=49640
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -3231,7 +3231,7 @@ bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1
address is seen on a different interface. This gives address is seen on a different interface. This gives
the benefit of static address entries without the need the benefit of static address entries without the need
to pre-populate the forwarding table. Clients learned to pre-populate the forwarding table. Clients learned
on a particular segment of the bridge can not roam to on a particular segment of the bridge cannot roam to
another segment.</para> another segment.</para>
<para>An example of using sticky addresses is to combine <para>An example of using sticky addresses is to combine
@ -3251,7 +3251,7 @@ bridge0: flags=8843&lt;UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST&gt; metric 0 mtu 1
<para>In this example, both clients see <systemitem <para>In this example, both clients see <systemitem
class="ipaddress">192.168.0.1</systemitem> as their class="ipaddress">192.168.0.1</systemitem> as their
default gateway. Since the bridge cache is sticky, one default gateway. Since the bridge cache is sticky, one
host can not spoof the <acronym>MAC</acronym> address of host cannot spoof the <acronym>MAC</acronym> address of
the other customer in order to intercept their the other customer in order to intercept their
traffic.</para> traffic.</para>