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

Wrap lines that were too long.

Browse source 
Only whitespace changes.
This commit is contained in:
Giorgos Keramidas 2001-12-06 21:13:56 +00:00
parent b3347b0fdf
commit f54121bd7f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=11357
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -94,10 +94,10 @@
</varlistentry> </varlistentry>
</variablelist> </variablelist>
<para>There are some other <emphasis>optional</emphasis> items that you can compile <para>There are some other <emphasis>optional</emphasis> items that you
into the kernel for some added security. These are not required in can compile into the kernel for some added security. These are not
order to get firewalling to work, but some more paranoid users may required in order to get firewalling to work, but some more paranoid
want to use them.</para> users may want to use them.</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
@ -107,8 +107,8 @@
<para>This option ignores TCP packets with SYN and FIN. This <para>This option ignores TCP packets with SYN and FIN. This
prevents tools such as nmap etc from identifying the TCP/IP prevents tools such as nmap etc from identifying the TCP/IP
stack of the machine, but breaks support for RFC1644 stack of the machine, but breaks support for RFC1644
extensions. This is <emphasis>not</emphasis> recommended if the machine will be extensions. This is <emphasis>not</emphasis> recommended if the
running a web server.</para> machine will be running a web server.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
</variablelist> </variablelist>
@ -305,8 +305,8 @@ $fwcmd add 65435 deny log ip from any to any</programlisting>
<emphasis>anything</emphasis> being diverted through the <emphasis>anything</emphasis> being diverted through the
<devicename>tun0</devicename> device. As far as it is <devicename>tun0</devicename> device. As far as it is
concerned incoming packets will speak only to the concerned incoming packets will speak only to the
dynamically assigned IP address and <emphasis>not</emphasis> to the internal dynamically assigned IP address and <emphasis>not</emphasis> to
network. Note though that you can add a rule like 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 <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 to any via tun0</literal> which would limit a host on your
internal network from going out via the firewall.</para> internal network from going out via the firewall.</para>