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

Add more descriptive markup (<command>, <devicename>, etc..)

Browse source 
PR:		docs/29744
Submitted by:	ncalvo <ncalvo@es.freebsd.org>
This commit is contained in:
Murray Stokely 2001-09-02 10:21:15 +00:00
parent 961dc11c17
commit 504bff39b8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10535
1 changed files with 11 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
en_US.ISO8859-1/articles/dialup-firewall/article.sgml
View file

@ -22,7 +22,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD$</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/dialup-firewall/article.sgml,v 1.13 2001/08/31 18:06:40 dd Exp $</pubdate>
<abstract>
<para>This article documents how to setup a firewall using a PPP
@ -173,7 +173,7 @@ ppp_profile="<replaceable>profile</replaceable>"</programlisting>
order of allow first and then deny. The premise is that you add the
rules for your allows, and then everything else is denied. :)</para>
<para>Now, let's make the dir /etc/firewall. Change into the directory and
<para>Now, let's make the dir <filename class="directory">/etc/firewall</filename>. Change into the directory and
edit the file <filename>fwrules</filename> as we specified in
<filename>rc.conf</filename>. Please note that you can change this
filename to anything you wish. This guide just gives an example of a
@ -245,17 +245,18 @@ $fwcmd add 65435 deny log ip from any to any</programlisting>
<qandaset>
<qandaentry>
<question>
<para>Why are you using natd and ipfw when you could be using
the built in ppp-filters?</para>
<para>Why are you using &man.natd.8; and &man.ipfw.8; when
you could be using the built in &man.ppp.8;
filters?</para>
</question>
<answer>
<para>I'll have to be honest and say there's no definitive reason
why I use ipfw and natd instead of the built in ppp filters. From
why I use <command>ipfw</command> and <command>natd</command> instead of the built in <command>ppp</command> filters. From
the discussions I've had with people the consensus seems to be
that while ipfw is certainly more powerful and more configurable
than the ppp filters, what it makes up for in functionality it
loses in being easy to customise. One of the reasons I use it is
that while <command>ipfw</command> is certainly more powerful and more configurable
than the <command>ppp</command> filters, what it makes up for in functionality it
loses in being easy to customize. One of the reasons I use it is
because I prefer firewalling to be done at a kernel level rather
than by a userland program.</para>
</answer>
@ -287,9 +288,9 @@ $fwcmd add 65435 deny log ip from any to any</programlisting>
</question>
<answer>
<para>The simple answer is no. The reason for this is that natd is
<para>The simple answer is no. The reason for this is that <command>natd</command> is
doing address translation for <emphasis>anything</emphasis> being
diverted through the tun0 device. As far as it's concerned
diverted through the <devicename>tun0</devicename> device. As far as it's concerned
incoming packets will speak only to the dynamically assigned IP
address and NOT to the internal network. Note though that you can
add a rule like <literal>$fwcmd add deny all from