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

Add recommendation against 'nobogons'

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1926 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-01-26 19:03:05 +00:00
parent ebb290af4c
commit fceb8cc250
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Shorewall-docs2/Documentation.xml
View File

@ -15,10 +15,10 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>2004-12-31</pubdate> <pubdate>2005-01-26</pubdate>
<copyright> <copyright>
<year>2001-2004</year> <year>2001-2005</year>
<holder>Thomas M. Eastep</holder> <holder>Thomas M. Eastep</holder>
</copyright> </copyright>
@ -638,6 +638,14 @@ dmz DMZ Demilitarized zone</programlisting>
address reserved by the IANA or by other RFCs (other than address reserved by the IANA or by other RFCs (other than
1918) are dropped after being optionally logged. See the 1918) are dropped after being optionally logged. See the
/etc/shorewall/bogons file documentation below.</para> /etc/shorewall/bogons file documentation below.</para>
<para>I personally recommend against using the nobogons
option. The IPV4 address space is being rapidly depleated so
the benefit of blocking traffic from unallocated address
ranges is minimal. Plus the rate at which address blocks are
being assigned causes your /etc/shorewall/bogons file to
become out of date with the result that legitimate traffic
gets blocked.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -4109,4 +4117,4 @@ eth1 -</programlisting>
</revision> </revision>
</revhistory></para> </revhistory></para>
</appendix> </appendix>
</article> </article>