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

Remove some contractions.

Browse source
This commit is contained in:
Marc Fonvieille 2003-02-28 21:13:53 +00:00
parent 487715cb27
commit 9f2712705b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=16148
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
en_US.ISO8859-1/articles/filtering-bridges/article.sgml
View file

@ -46,7 +46,7 @@
that filters incoming and outgoing traffic from and towards Internet,
but a packet filtering solution based on router may not be applicable,
either due to subnetting issues, the router is owned by the connectivity
supplier (<acronym>ISP</acronym>), or because it doesn't support such
supplier (<acronym>ISP</acronym>), or because it does not support such
functionalities. In these scenarios the use of a filtering bridge is
highly advised.</para>
@ -244,7 +244,7 @@ firewall_logging="YES"</programlisting>
<para>Let's look at an example setup. Note first that at the top of
<filename>/etc/rc.firewall</filename> there are already standard rules
for the loopback interface <devicename>lo0</devicename>, so we shouldn't
for the loopback interface <devicename>lo0</devicename>, so we should not
have to care for them anymore. Custom rules should be put in a separate
file (say <filename>/etc/rc.firewall.local</filename>) and loaded at
system startup, by modifying the row of
@ -276,7 +276,7 @@ add drop all from 172.16.0.0/12 to any in via fxp0
add drop all from 192.168.0.0/16 to any in via fxp0
# Allow the bridge machine to say anything it wants
# (if the machine is IP-less don't include these rows)
# (if the machine is IP-less do not include these rows)
add pass tcp from 1.2.3.4 to any setup keep-state
add pass udp from 1.2.3.4 to any keep-state
add pass ip from 1.2.3.4 to any