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

Update rfc1918 info in FAQ 17

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3202 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-12-28 17:09:19 +00:00
parent 5791bcfc80
commit 3388be2ae2
1 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Shorewall-docs2/FAQ.xml
View File

@ -17,7 +17,7 @@
</author>
</authorgroup>
<pubdate>2005-12-09</pubdate>
<pubdate>2005-12-28</pubdate>
<copyright>
<year>2001-2005</year>
@ -919,6 +919,23 @@ LOGBURST=""</programlisting>
role="bold">logdrop</emphasis> target -- see <filename> <ulink
url="Documentation.htm#rfc1918">/usr/share/shorewall/rfc1918</ulink>
</filename>.</para>
<note>
<para>If you see packets being dropped in the rfc1918 chain and
neither the source nor the destination IP address is reserved by
RFC 1918, that usually means that you have a old
<filename>rfc1918</filename> file in <filename
class="directory">/etc/shorewall</filename> (this problem most
frequently occurs if you are running Debian or one if its
derivatives). The <filename>rfc1918</filename> file used to
include bogons as well as the three ranges reserved by RFC 1918
and it resided in <filename
class="directory">/etc/shorewall</filename>. The file now only
includes the three RFC 1918 ranges and it resides in <filename
class="directory">/usr/share/shorewall</filename>. Remove the
stale <filename>rfc1918</filename> file in <filename
class="directory">/etc/shorewall</filename>. </para>
</note>
</listitem>
</varlistentry>