extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-08-17 12:16:58 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update for Shorewall 2.2.0

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1747 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep
2004-11-10 21:11:00 +00:00
parent 2322635ac4
commit f0887d47ac
6 changed files with 171 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
Samples/two-interfaces/interfaces
View File

@ -1,5 +1,5 @@
#
# Shorewall 2.0 -- Sample Interface File For Two Interfaces
# Shorewall 2.2 -- Sample Interface File For Two Interfaces
#
# /etc/shorewall/interfaces
#
@ -80,6 +80,14 @@
# Check packets arriving on this interface
# against the /etc/shorewall/blacklist
# file.
# logmartians
# Turn on kernel martian logging (logging
# of packets with impossible source
# addresses. It is suggested that if you
# set routefilter on an interface that
# you also set logmartians. This option
# may also be enabled globally in the
# /etc/shorewall/shorewall.conf file.
# maclist
# Connection requests from this interface
# are compared against the contents of
@ -109,10 +117,19 @@
# which are not part of an established connection
# will be accepted from this interface, even if
# NEWNOTSYN=No has been specified in
# /etc/shorewall/shorewall.conf.
# /etc/shorewall/shorewall.conf. In other
# words, packets coming in on this interface
# are processed as if NEWNOTSYN=Yes had been
# specified in /etc/shorewall/shorewall.conf.
#
# This option has no effect if NEWNOTSYN=Yes.
#
# It is the opinion of the author that
# NEWNOTSYN=No creates more problems than
# it solves and I recommend against using
# that setting in shorewall.conf (hence
# making the use of the 'newnotsyn'
# interface option unnecessary).
# routeback
# If specified, indicates that Shorewall
# should include rules that allow filtering