holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Admin that PKTTYPE is a no-op

Browse Source
This commit is contained in:
Tom Eastep 2009-09-07 16:44:19 -07:00
parent b2c7b583f5
commit 9a1cb0c6b6
2 changed files with 4 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Documentation_Index.xml
View File

@ -208,8 +208,8 @@
<entry><ulink url="Multiple_Zones.html"><ulink
url="OPENVPN.html">OpenVPN</ulink></ulink></entry>
<entry><ulink url="LennyToSqueeze.html">Upgrade Issues when
upgrading Debian Lenny to Squeeze</ulink></entry>
<entry><ulink url="LennyToSqueeze.html">Upgrading Debian Lenny to
Squeeze - A Shorewall Perspective</ulink></entry>
</row>
<row>

26
manpages/shorewall.conf.xml
View File

@ -1162,30 +1162,8 @@ net all DROP info</programlisting>then the chain name is 'net2all'
role="bold">Yes</emphasis>|<emphasis role="bold">No</emphasis>}</term>
<listitem>
<para>Normally Shorewall attempts to use the iptables packet type
match extension to determine broadcast and multicast packets.</para>
<orderedlist>
<listitem>
<para>This can cause a message to appear during shorewall start
(modprobe: cant locate module ipt_pkttype).</para>
</listitem>
<listitem>
<para>Some users have found problems with the packet match
extension with the result that their firewall log is flooded
with messages relating to broadcast packets.</para>
</listitem>
</orderedlist>
<para></para>
<blockquote>
<para>If you are experiencing either of these problems, setting
PKTTYPE=No will prevent Shorewall from trying to use the packet
type match extension and to use IP address matching to determine
which packets are broadcasts or multicasts.</para>
</blockquote>
<para>This option is included for compatibility with older Shorewall
releases. Its setting has no effect.</para>
</listitem>
</varlistentry>