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

Improve bridging instructions in config file comments

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3090 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-11-28 15:26:06 +00:00
parent 7bd385d2ce
commit 577389464f
4 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/changelog.txt
View File

@ -2,6 +2,8 @@ Changes in 3.0.3
1) Implement "shorewall show macros" 1) Implement "shorewall show macros"
2) Comments regarding bridge configuration were improved.
Changes in 3.0.2 Changes in 3.0.2
1) Typos in the Samples corrected. 1) Typos in the Samples corrected.

4
Shorewall/hosts
View File

@ -41,7 +41,9 @@
# optionally followed by a colon (":") and a # optionally followed by a colon (":") and a
# host or network IP or a range. # host or network IP or a range.
# See http://www.shorewall.net/Bridge.html # See http://www.shorewall.net/Bridge.html
# for details. # for details. Specifying a physical port
# name requires that you have BRIDGING=Yes in
# /etc/shorewall/shorewall.conf.
# e) The name of an ipset (preceded by "+"). # e) The name of an ipset (preceded by "+").
# #
# Examples: # Examples:

10
Shorewall/releasenotes.txt
View File

@ -2,7 +2,9 @@ Shorewall 3.0.3
Problems Corrected in 3.0.3 Problems Corrected in 3.0.3
None. 1) The comments in the /etc/shorewall/shorewall.conf and
/etc/shorewall/hosts files have been changed to clarify when
BRIDGING=Yes is required when dealing with bridges.
New Features in 3.0.3 New Features in 3.0.3
@ -83,7 +85,7 @@ New Features in 3.0.1
ACCEPT net loc:192.168.1.5 tcp http ACCEPT net loc:192.168.1.5 tcp http
Migration Considerations: Migration Considerations for Users upgrade from Shorewall 2.2 or 2.4.
1) The "monitor" command has been eliminated. 1) The "monitor" command has been eliminated.
@ -593,7 +595,9 @@ New Features in Shorewall 3.0.*
21) The output of "shorewall dump" now includes a capabilities report 21) The output of "shorewall dump" now includes a capabilities report
such as the one produced by "shorewall show capabilities". such as the one produced by "shorewall show capabilities".
22) The "plain" zone type has been replaced by "ipv4". The types 22) Note: This change is only important for users who ran Shorewall 2.5.x.
The "plain" zone type has been replaced by "ipv4". The types
"IPv4" and "IPV4" are synonyms for "ipv4". In addition, "IPSEC", "IPv4" and "IPV4" are synonyms for "ipv4". In addition, "IPSEC",
"ipsec4" and "IPSEC4" are recognized synonyms for "ipsec". "ipsec4" and "IPSEC4" are recognized synonyms for "ipsec".

2
Shorewall/shorewall.conf
View File

@ -652,7 +652,7 @@ DISABLE_IPV6=Yes
# #
# BRIDGING # BRIDGING
# #
# If you wish to control traffic through a bridge (see http://bridge.sf.net), # If you wish to restrict connections through a bridge (see http://bridge.sf.net),
# then set BRIDGING=Yes. Your kernel must have the physdev match option # then set BRIDGING=Yes. Your kernel must have the physdev match option
# enabled; that option is available at the above URL for 2.4 kernels and # enabled; that option is available at the above URL for 2.4 kernels and
# is included as a standard part of the 2.6 series kernels. If not # is included as a standard part of the 2.6 series kernels. If not