It has been discovered that when using the recommended upgrade sequence to Shorewall 4.0.0 using RPMs, Shorewall is not started at the next reboot. After you upgrade, be sure to use your distribution''s services configuration tool to insure that Shorewall is configured to start. For most distributions using RPMs, the following command is sufficient: chkconfig --add shorewall -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- 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/