Fix 'bridge' compilation error

This commit is contained in:
Tom Eastep 2009-11-21 15:37:22 -08:00
parent 446dff6ec5
commit 51b905eed4
4 changed files with 17 additions and 1 deletions

View File

@ -2316,7 +2316,7 @@ EOF
}
} else {
for my $interface ( all_bridges ) {
emit "do_iptables -A FORWARD -p 58 " . match_source_interface( $interface ) . match_dest_interface( $interface ) . "-j ACCEPT";
emit "do_iptables -A FORWARD -p 58 " . match_source_dev( $interface ) . match_dest_dev( $interface ) . "-j ACCEPT";
}
if ( $config{IP_FORWARDING} eq 'on' ) {

View File

@ -2,6 +2,8 @@ Changes in Shorewall 4.4.4.1
1) Fix 15-port change.
2) Fix handling of interfaces with the 'bridge' option.
Changes in Shorewall 4.4.4
1) Change STARTUP_LOG and LOG_VERBOSITY in default shorewall6.conf.

View File

@ -3,3 +3,11 @@
more than 15 ports are listed, an error is generated.
This problem is corrected in Shorewall 4.4.4.1.
2) If any interfaces have the 'bridge' option specified, compilation
fails with the error:
Undefined subroutine &Shorewall::Rules::match_source_interface called
at /usr/share/shorewall/Shorewall/Rules.pm line 2319.
This problem is corrected in Shorewall 4.4.4.1.

View File

@ -181,6 +181,12 @@ Shorewall 4.4.4 Patch Release 1
/etc/shorewall/routestopped was incomplete. The result was that if
more than 15 ports are listed, an error was generated.
2) If any interfaces have the 'bridge' option specified, compilation
fails with the error:
Undefined subroutine &Shorewall::Rules::match_source_interface called
at /usr/share/shorewall/Shorewall/Rules.pm line 2319.
----------------------------------------------------------------------------
P R O B L E M S C O R R E C T E D I N 4 . 4 . 4
----------------------------------------------------------------------------