Dash Four wrote:
>
> Dash Four wrote:
>>
>>> Yes. But the actual set of rules will be:
>>>
>>> -A INPUT -j accountin
>>> -A accounting -I eth0 -j eth0_in
>>> -A eth0_in -m nfacct --nfacct-name eth0_in
>>>
>> Interesting, I think I found another bug:
>>
>> accounting
>> ~~~~~~~~~~
>> test
>> INPUT test
>>
>> produces ... well, all hell brakes loose - I get over 30 lines of
>> internal shorewall errors...
> OK, I was able to reproduce this and find what is causing it - one of
> the most bizarre errors I've seen. Here goes:
> 1. cd /etc/shorewall
> 2. shorewall compile firewall (this MUST succeed with no errors!)
> 3. edit "accounting" and add:
> firewall
> INPUT firewall
> 4. save & exit, then repeat step 2. I am getting this:
>
> String found where operator expected at (eval 22) line 45, near "n
> "$g_timestamp""
> (Do you need to predeclare n?)
> String found where operator expected at (eval 22) line 46, near "echo
> "${timestamp}$@""
> (Do you need to predeclare echo?)
> Bareword found where operator expected at (eval 22) line 51, near
> ""$(date +'%b %_d %T') "
> echo"
> (Missing operator before echo?)
> String found where operator expected at (eval 22) line 51, near "echo
> "${timestamp}$@""
> (Do you need to predeclare echo?)
> Bareword found where operator expected at (eval 22) line 52, near
> "$STARTUP_LOG
> fi"
> (Missing operator before fi?)
> String found where operator expected at (eval 22) line 61, near "n
> "$g_timestamp""
> (Do you need to predeclare n?)
> String found where operator expected at (eval 22) line 62, near "echo
> "${timestamp}$@""
> (Do you need to predeclare echo?)
> Bareword found where operator expected at (eval 22) line 67, near
> ""$(date +'%b %_d %T') "
> echo"
> (Missing operator before echo?)
> String found where operator expected at (eval 22) line 67, near "echo
> "${timestamp}$@""
> (Do you need to predeclare echo?)
> Bareword found where operator expected at (eval 22) line 68, near
> "$STARTUP_LOG
> fi"
> (Missing operator before fi?)
> String found where operator expected at (eval 22) line 77, near "n
> "$g_timestamp""
> ERROR: Couldn't parse /etc/shorewall/firewall: syntax error at (eval
> 22) line 40, near ") # $* = Message
> {"
> Global symbol "$VERBOSITY" requires explicit package name at (eval 22)
> line 44, <$currentfile> line 1.
> Global symbol "$LOG_VERBOSITY" requires explicit package name at (eval
> 22) line 49, <$currentfile> line 1.
> syntax error at (eval 22) line 51, near ""$(date +'%b %_d %T') "
> echo "
> Global symbol "$STARTUP_LOG" requires explicit package name at (eval
> 22) line 52, <$currentfile> line 1.
> Global symbol "$VERBOSITY" requires explicit package name at (eval 22)
> line 60, <$currentfile> line 1.
> Global symbol "$LOG_VERBOSITY" requires explicit package name at (eval
> 22) line 65, <$currentfile> line 1.
> syntax error at (eval 22) line 67, near ""$(date +'%b %_d %T') "
> echo "
> Global symbol "$STARTUP_LOG" requires explicit package name at (eval
> 22) line 68, <$currentfile> line 1.
> Global symbol "$VERBOSITY" requires explicit package name at (eval 22)
> line 76, <$currentfile> line 1.
> (eval 22) has too many errors.
> /etc/shorewall/accounting (line 1)
The above error is still present in this Beta!
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Shorewall-devel mailing list
Shorewall-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
