On 7/23/10 7:34 AM, Tom Eastep wrote: > The above testing was done with Shorewall 4.4.12 Beta 1 (not yet > released) which ensures that only one event is processed at a time; with > earlier releases, the situation is more chaotic as events are handled in > parallel. > > As a workaround, I'm recommending that you use 'startup=1' in > /etc/default/shorewall* to ensure that the firewall is finally placed in > a 'started' state (assuming that required interfaces are available). >
Beta 1 is now uploaded and contains additional fixes for use with Upstart. The firewall is not guaranteed to be stopped prior to interfaces coming up but the firewall should always end up in the started state after boot (providing that the required interface(s) is (are) available). -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
------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
