On 2/13/11 5:48 AM, Dominic Benson wrote: > > I don't know what the best proper fix would be. If this is an isolated > example of ipv4/ipv6 compatibility trouble, then perhaps the global > address could be supplied from the shorewall/shorewall6 scripts > themselves, per the iptables command. If it isn't, possibly a neater > version of the include path selection I used would be better. If there > is a consensus, I could concoct an appropriate patch.
The attached patch should fix you up. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
diff --git a/Shorewall/Perl/Shorewall/Providers.pm
b/Shorewall/Perl/Shorewall/Providers.pm
index 1085b7e..7240717 100644
--- a/Shorewall/Perl/Shorewall/Providers.pm
+++ b/Shorewall/Perl/Shorewall/Providers.pm
@@ -429,7 +429,7 @@ sub add_a_provider( ) {
if ( $gatewaycase eq 'none' ) {
if ( $local ) {
- emit "run_ip route add local 0.0.0.0/0 dev $physical table
$number";
+ emit 'run_ip route add local ' . ALLIP . " dev $physical table
$number";
} else {
emit "run_ip route add default dev $physical table $number";
}
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
