Shorewall 4.4.26 Beta 2 is now available for testing.
Problems Corrected:
1) Previously, Shorewall did not detect the ULOG and NFLOG
capabilities. This lead to run-time failures during
''start'' and
''restart'' as well as confusing error messages during
compilation
when ULOG or NFLOG was used when the LOG target was not available.
ULOG and NFLOG are now detected capabilities so, if you use a
capabilities file, you will need to regenerate it in order to use
these log levels.
Thank you for testing,
-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 \________________________________________________
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
Tom In the attached config. rule: act1:warn! all all tcp 90 produces the following error message: ERROR: Invalid log level (warn!) : /etc/shorewallT8/rules (line 13) Steven. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
On Nov 15, 2011, at 3:36 PM, Steven Jan Springl wrote:> In the attached config. rule: > > act1:warn! all all tcp 90 > > produces the following error message: > > ERROR: Invalid log level (warn!) : /etc/shorewallT8/rules (line 13) >The attached patch corrects this issue. Thanks, Steven -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 \________________________________________________ ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
On Wednesday 16 Nov 2011 00:44:18 Tom Eastep wrote:> On Nov 15, 2011, at 3:36 PM, Steven Jan Springl wrote: > > In the attached config. rule: > > > > act1:warn! all all tcp 90 > > > > produces the following error message: > > > > ERROR: Invalid log level (warn!) : /etc/shorewallT8/rules (line 13) > > The attached patch corrects this issue. > > Thanks, Steven > > -TomTom Confirmed, the patch corrects the issue. Thanks. Steven. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
On Wed, 2011-11-16 at 01:07 +0000, Steven Jan Springl wrote:> > Confirmed, the patch corrects the issue. Thanks. >Thanks, Steven -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 \________________________________________________ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
Tom Shorewall rule: LOG:LOGMARK(info) all all tcp 90 produces the following error message: ERROR: Invalid log level (LOGMARK(INFO)) : /etc/shorewallT8/rules (line 13) Steven. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Nov 16, 2011, at 3:23 PM, Steven Jan Springl wrote:> Shorewall rule: > > LOG:LOGMARK(info) all all tcp 90 > > produces the following error message: > > ERROR: Invalid log level (LOGMARK(INFO)) : /etc/shorewallT8/rules (line 13)Steven, The attached patch seems to resolve the issue. Thanks, -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 \________________________________________________ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Thursday 17 Nov 2011 04:38:31 Tom Eastep wrote:> On Nov 16, 2011, at 3:23 PM, Steven Jan Springl wrote: > > Shorewall rule: > > > > LOG:LOGMARK(info) all all tcp 90 > > > > produces the following error message: > > > > ERROR: Invalid log level (LOGMARK(INFO)) : /etc/shorewallT8/rules (line > > 13) > > Steven, > > The attached patch seems to resolve the issue. > > Thanks, > -TomTom Confirmed, the patch fixes the issue. Thanks. Steven. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
Tom Issuing the following command against the attached config: shorewall update -b /etc/shorewallT8 produces the following error message: ERROR: Internal error in Shorewall::Misc::remove_blacklist at /usr/share/shorewall/Shorewall/Misc.pm line 359 Steven. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Nov 17, 2011, at 3:12 PM, Steven Jan Springl wrote:> Issuing the following command against the attached config: > > shorewall update -b /etc/shorewallT8 > > produces the following error message: > > ERROR: Internal error in Shorewall::Misc::remove_blacklist at > /usr/share/shorewall/Shorewall/Misc.pm line 359Steven, This patch seems to work around the problem. Thanks, -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 \________________________________________________ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Nov 17, 2011, at 4:56 PM, Tom Eastep wrote:> > Steven, > > This patch seems to work around the problem. > > Thanks, > -TomPatch was corrupted. Here''s the correct patch. -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 \________________________________________________ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Friday 18 Nov 2011 14:25:50 Tom Eastep wrote:> Patch was corrupted. Here''s the correct patch. > > -TomTom The patch fixes the issue, however I now get the following error message when issuing command ''shorewall update -b /etc/shorewallT8'': ERROR: Unknown ACTION (blacklog) : /etc/shorewallT8/blrules (line 15) I have attached a copy of the config. after ''shorewall update'' command has been run. Steven. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Nov 18, 2011, at 2:35 PM, Steven Jan Springl wrote:> The patch fixes the issue, however I now get the following error message > when issuing command ''shorewall update -b /etc/shorewallT8'': > > ERROR: Unknown ACTION (blacklog) : /etc/shorewallT8/blrules (line 15) > > I have attached a copy of the config. after ''shorewall update'' command has been > run.Steven, The attached patch corrects this next issue but the original config was invalid -- the blacklist file contained a reference to br0 which does not appear in the interfaces 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 \________________________________________________ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Saturday 19 Nov 2011 00:44:40 Tom Eastep wrote:> On Nov 18, 2011, at 2:35 PM, Steven Jan Springl wrote: > > The patch fixes the issue, however I now get the following error message > > when issuing command ''shorewall update -b /etc/shorewallT8'': > > > > ERROR: Unknown ACTION (blacklog) : /etc/shorewallT8/blrules (line 15) > > > > I have attached a copy of the config. after ''shorewall update'' command > > has been run. > > Steven, > > The attached patch corrects this next issue but the original config was > invalid -- the blacklist file contained a reference to br0 which does not > appear in the interfaces file. > > -TomTom Confirmed, the patch fixes the issue. The blacklist keyword is not being removed from the zones file. Steven. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d
On Sat, 2011-11-19 at 01:52 +0000, Steven Jan Springl wrote:> > Confirmed, the patch fixes the issue. > > The blacklist keyword is not being removed from the zones file. >Steven, I''ve decided to change my approach slightly -- I''ll be releasing Beta 3 later today. Thanks, -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 \________________________________________________ ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d