Use <emphasis> instead of CAPS to emphasize text.
PR: docs/30785 Submitted by: Giorgos Keramidas <charon@labs.gr>
This commit is contained in:
parent
57228118a4
commit
a470682281
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10814
1 changed files with 4 additions and 4 deletions
|
@ -22,7 +22,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/dialup-firewall/article.sgml,v 1.14 2001/09/02 10:21:15 murray Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/dialup-firewall/article.sgml,v 1.15 2001/09/02 10:37:26 murray Exp $</pubdate>
|
||||
|
||||
<abstract>
|
||||
<para>This article documents how to setup a firewall using a PPP
|
||||
|
@ -94,7 +94,7 @@
|
|||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>There are some other OPTIONAL items that you can compile
|
||||
<para>There are some other <emphasis>optional</emphasis> items that you can compile
|
||||
into the kernel for some added security. These are not required in
|
||||
order to get firewalling to work, but some more paranoid users may
|
||||
want to use them.</para>
|
||||
|
@ -107,7 +107,7 @@
|
|||
<para>This option ignores TCP packets with SYN and FIN. This
|
||||
prevents tools such as nmap etc from identifying the TCP/IP
|
||||
stack of the machine, but breaks support for RFC1644
|
||||
extensions. This is NOT recommended if the machine will be
|
||||
extensions. This is <emphasis>not</emphasis> recommended if the machine will be
|
||||
running a web server.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
@ -299,7 +299,7 @@ $fwcmd add 65435 deny log ip from any to any</programlisting>
|
|||
<emphasis>anything</emphasis> being 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
|
||||
dynamically assigned IP address and <emphasis>not</emphasis> to the internal
|
||||
network. Note though that you can add a rule like
|
||||
<literal>$fwcmd add deny all from 192.168.0.4:255.255.0.0
|
||||
to any via tun0</literal> which would limit a host on your
|
||||
|
|
Loading…
Reference in a new issue