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

Reverse the way the mss= works

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1706 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2004-10-20 15:28:47 +00:00
parent ccf56bcf74
commit 532a2d0990
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Shorewall2/firewall
View File

@ -1768,10 +1768,10 @@ setup_ipsec() {
for z in $zones; do for z in $zones; do
case $2 in case $2 in
_in) _in)
set_mss1 ${z}2${zone} $1 set_mss1 ${zone}2${z} $1
;; ;;
_out) _out)
set_mss1 ${zone}2${z} $1 set_mss1 ${z}2${zone} $1
;; ;;
*) *)
set_mss1 ${z}2${zone} $1 set_mss1 ${z}2${zone} $1

5
Shorewall2/releasenotes.txt
View File

@ -89,6 +89,11 @@ Problems corrected since 2.1.11
Shorewall will now issue an error message and terminate during Shorewall will now issue an error message and terminate during
"shorewall [re]start" or "shorewall check". "shorewall [re]start" or "shorewall check".
2) If a configuration has two or more "complex" zones (zones having
IPSEC hosts or zones having more than one subnet on an interface)
then an incorrect ruleset is generated. This problem was introduced
in 2.1.11.
----------------------------------------------------------------------- -----------------------------------------------------------------------
Issues when migrating from Shorewall 2.0 to Shorewall 2.1: Issues when migrating from Shorewall 2.0 to Shorewall 2.1: