On Dec 2, 2011, at 6:31 AM, Tom Eastep wrote: > On Fri, 2011-12-02 at 10:01 +0100, Peter Mumenthaler wrote: >> Hello, >> >> We have a problem since upraded shorewall from shorewall-4.0.15-1 to >> shorewall-4.4.23.3-1 running on Centos 6.1. >> >> The problem is that our own defined params file in >> /etc/shorewall/puppet/params seems not to be read. Thus shorewall >> complains about shell variables not being defined. This is strange >> because all other files in /etc/shorewall/puppet (blacklist hosts >> interfaces masq nat policy providers proxyarp rfc1918 >> routestopped rules zones) seem to be read, though. >> >> We defined in /etc/shorewall/shorewall.conf and >> /usr/share/shorewall/configfile/shorewall.conf the CONFIG_PATH variable >> as follows: >> >> CONFIG_PATH=/etc/shorewall/puppet:/etc/shorewall:/usr/share/shorewall > > As a workaround, you can move that line toward the top of the file, > before any reference to a variable in params. I'll work on a fix.
As I devised a fix for this problem, I realized that the above advice doesn't solve the problem. At any rate, the defect is corrected in Shorewall 4.4.26 which was released yesterday. -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 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
