İlker Aktuna (Koç.net) wrote: > So you are 100% sure that it's not caused by Shorewall or > misconfiguration of it ?
Given that Shorewall is nothing but a configuration tool, problems where the firewall works for a while then stops working can't possibly be traced to Shorewall. Once 'shorewall start' has completed, there is no Shorewall code left running in your system at all. Unless you are using CONNLIMIT, there isn't any way that I know of that Shorewall could be mis-configured such that your problem could be resolved by 'conntrack -F'. -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: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
