Srinivasa Hebbar wrote: >> > I am using shorewall 3.4.4 at the moment. Will this technique future > compatible with shorewall perl (4.0+)? > My concern is I may end up in trouble if shorewall started using different > function (other than is_interface_usable) to detect interface status in > future versions. I tested with my own version of is_interface_usable and > which works for the current version of shorewall I am using. (3.4.4).
Not much chance of this changing but for Shorewall-perl 4.0.3, there will be
an 'isuasable' extension script. Here's an example:
# Ping a gateway through the passed interface
case $1 in
eth0)
ping -c 4 -I eth0 206.124.146.254 > /dev/null 2>&1
return
;;
eth1)
ping -c 4 -I eth1 192.168.12.254 > /dev/null 2>&1
return
;;
*)
return 1
;;
esac
>
> I feel the plugin approach will be very helpful for multiple wan links with
> static IPs.
Of course -- but then you don't have to document it or answer silly
questions about it.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ [EMAIL PROTECTED]
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Shorewall-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-devel
