On 11/19/2014 3:12 AM, Philip Le Riche wrote: > Thanks Tom - it sounds like adding something like "required,wait=5" > would at least be a viable work-around.
Yes. > > But reading between the lines, it seems you're saying that I could in > all likelihood sidestep the problem completely, just by specifying > "optional" instead (I presume "required" is the default - the man page > is silent on that.) The default is neither "required" nor "optional". The firewall will start even if the interface doesn't exist, provided that you haven't used a configuration construct that requires the interface to be up in order to start. Is there a discussion somewhere of what > configurations require "required"? > No -- but they are pretty obvious. Given the error message you are seeing, something you are doing requires the IP address of eth0. Some possibilities are: - You are calling find_first_interface_address() in your params file - You have used "ð0" or "%eth0" in one of your files - You have used "detect:" in a rule. - You have entered "detect" in the ADDRESS column in the masq file -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 \________________________________________________
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
