Stop whining about DHCP vs. nobogons

git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1507 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-07-29 21:21:15 +00:00
parent 6304de1731
commit 8507d941e5
3 changed files with 11 additions and 1 deletions

View File

@ -22,6 +22,7 @@
# #
############################################################################### ###############################################################################
#SUBNET TARGET #SUBNET TARGET
0.0.0.0 RETURN # Stop the DHCP whining
255.255.255.255 RETURN # We need to allow limited broadcast 255.255.255.255 RETURN # We need to allow limited broadcast
169.254.0.0/16 DROP # DHCP autoconfig 169.254.0.0/16 DROP # DHCP autoconfig
192.0.2.0/24 logdrop # Example addresses (RFC 3330) 192.0.2.0/24 logdrop # Example addresses (RFC 3330)

View File

@ -42,3 +42,5 @@ Changes in 2.0.7
3) Enhance IP/Routing output in "shorewall status". 3) Enhance IP/Routing output in "shorewall status".
4) Correct handling of multiple 'blacklist' interfaces. 4) Correct handling of multiple 'blacklist' interfaces.
5) Add "0.0.0.0 RETURN" to nobogons.

View File

@ -51,6 +51,13 @@ Problems Corrected in version 2.0.7
2) Multiple interfaces with the 'blacklist' option no longer result in 2) Multiple interfaces with the 'blacklist' option no longer result in
an error message at startup. an error message at startup.
3) The following has been added to /etc/shorewall/bogons:
0.0.0.0 RETURN
This prevents the 'nobogons' option from logging DHCP 'DISCOVER'
broadcasts.
New Features in version 2.0.7 New Features in version 2.0.7
1) To improve supportability, the "shorewall status" command now 1) To improve supportability, the "shorewall status" command now