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

Fix another add_rule() that should have been an add_jump().

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-04-15 10:03:46 -07:00
parent 2b7cbe25e6
commit a7ec75d084
3 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/Perl/Shorewall/Tc.pm
View File

@ -1374,7 +1374,7 @@ sub setup_tc() {
# This is overloading TRACK_PROVIDERS a bit but sending tracked packets through PREROUTING is a PITA for users # This is overloading TRACK_PROVIDERS a bit but sending tracked packets through PREROUTING is a PITA for users
# #
for my $interface ( @routemarked_interfaces ) { for my $interface ( @routemarked_interfaces ) {
add_rule $mangle_table->{PREROUTING} , match_source_dev( $interface ) . "-j tcpre"; add_jump $mangle_table->{PREROUTING} , 'tcpre', 1, match_source_dev( $interface );
} }
} }
} }

2
Shorewall/changelog.txt
View File

@ -2,6 +2,8 @@ Changes in Shorewall 4.4.8.3
1) Make wildcard interfaces play well with optimize 4. 1) Make wildcard interfaces play well with optimize 4.
2) Fix another add_rule() that should have been an add_jump().
Changes in Shorewall 4.4.8.2 Changes in Shorewall 4.4.8.2
1) Fix OPTIMIZE 4 bug. 1) Fix OPTIMIZE 4 bug.

4
Shorewall/releasenotes.txt
View File

@ -224,6 +224,10 @@ I I I. P R O B L E M S C O R R E C T E D I N T H I S R E L E A S E
ending in '+' has been corrected. The most likely symptom of this ending in '+' has been corrected. The most likely symptom of this
problem would be iptables-restore failure. problem would be iptables-restore failure.
2) A second problem with optimize 4 has been corrected. This one
manifested as invalid iptables-restore input involving the 'tcpre'
mangle chain.
4.4.8.2 4.4.8.2
1) With optimize 4, if an unnecessary NONAT rule was included in 1) With optimize 4, if an unnecessary NONAT rule was included in