On 04/10/2012 04:26 AM, Steven Jan Springl wrote:
>
>
> Confirmed, OPTIMIZE_ACCOUNTING now works.
>
> I have finished my testing of RC2.
Thank you, Steven
-Tom
--
Tom Eastep\ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screami
> >
> >Steven,
> >
> >Please try this patch instead.
>
> Patch attached this time.
>
> -Tom
> You do not need a parachute to skydive. You only need a parachute to
> skydive twice.
Tom
Confirmed, OPTIMIZE_ACCOUNTING now works.
I have finished my testing of RC2.
Steven.
---
On 4/9/12 6:06 PM, "Tom Eastep" wrote:
>On 4/9/12 5:03 PM, "Tom Eastep" wrote:
>
>>On 4/9/12 4:32 PM, "Tom Eastep" wrote:
>>
>>>On 4/9/12 3:14 PM, "Steven Jan Springl"
>>>wrote:
>>>
Tom
In the attached config. accounting entry:
RPFILTER:COUNT - - eth0
generate
On 4/9/12 5:03 PM, "Tom Eastep" wrote:
>On 4/9/12 4:32 PM, "Tom Eastep" wrote:
>
>>On 4/9/12 3:14 PM, "Steven Jan Springl" wrote:
>>
>>>Tom
>>>
>>>In the attached config. accounting entry:
>>>
>>>RPFILTER:COUNT - - eth0
>>>
>>>generates the following iptables rule:
>>>
>>>-A INPUT -o eth0 -j
On 4/9/12 4:32 PM, "Tom Eastep" wrote:
>On 4/9/12 3:14 PM, "Steven Jan Springl" wrote:
>
>>Tom
>>
>>In the attached config. accounting entry:
>>
>>RPFILTER:COUNT - - eth0
>>
>>generates the following iptables rule:
>>
>>-A INPUT -o eth0 -j RPFILTER
>>
>>which produces the following error mess
On Tuesday 10 Apr 2012 00:32:08 Tom Eastep wrote:
> On 4/9/12 3:14 PM, "Steven Jan Springl" wrote:
> >Tom
> >
> >In the attached config. accounting entry:
> >
> >RPFILTER:COUNT - - eth0
> >
> >generates the following iptables rule:
> >
> >-A INPUT -o eth0 -j RPFILTER
> >
> >which produces the f
On 4/9/12 3:14 PM, "Steven Jan Springl" wrote:
>Tom
>
>In the attached config. accounting entry:
>
>RPFILTER:COUNT - - eth0
>
>generates the following iptables rule:
>
>-A INPUT -o eth0 -j RPFILTER
>
>which produces the following error message:
>
>iptables-restore v1.4.13: Can't use -o with IN
Tom
In the attached config. accounting entry:
RPFILTER:COUNT - - eth0
generates the following iptables rule:
-A INPUT -o eth0 -j RPFILTER
which produces the following error message:
iptables-restore v1.4.13: Can't use -o with INPUT
Additionally accounting entry:
RPFILTER:COUNT - eth0
On 04/09/2012 02:48 PM, Steven Jan Springl wrote:
>
> Confirmed, the patch fixes the issue and my last reported issue also.
>
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
Washi
On Monday 09 Apr 2012 22:40:30 Tom Eastep wrote:
> On 04/09/2012 01:56 PM, Tom Eastep wrote:
> > The fix may have a defect -- I'm seeing differences in the generated
> > ruleset while running regression tests.
>
> Steven,
>
> The problem turned out to be 'first-entry' processing. That was
> happe
On 04/09/2012 02:33 PM, Steven Jan Springl wrote:
>
> I can confirm the patch resolves the issue. However it does cause a futher
> problem. Rule:
>
> {ACTION=DROP SOURCE=fw DEST=lan PROTO=udp} #
>
> produces the following error message:
>
> ERROR: Unknown ACTION ({ACTION=DROP) : /etc/shore
On 04/09/2012 01:56 PM, Tom Eastep wrote:
>
> The fix may have a defect -- I'm seeing differences in the generated
> ruleset while running regression tests.
>
Steven,
The problem turned out to be 'first-entry' processing. That was
happening before the first non-omitted non-commentary entry in
On Monday 09 Apr 2012 21:56:57 Tom Eastep wrote:
> On 04/09/2012 12:55 PM, Tom Eastep wrote:
> > On 04/09/2012 12:35 PM, Steven Jan Springl wrote:
> >> On Monday 09 Apr 2012 19:09:28 Tom Eastep wrote:
> >>> On 04/09/2012 10:13 AM, Tom Eastep wrote:
> On 04/09/2012 06:56 AM, Steven Jan Springl
On 04/09/2012 12:55 PM, Tom Eastep wrote:
> On 04/09/2012 12:35 PM, Steven Jan Springl wrote:
>> On Monday 09 Apr 2012 19:09:28 Tom Eastep wrote:
>>> On 04/09/2012 10:13 AM, Tom Eastep wrote:
On 04/09/2012 06:56 AM, Steven Jan Springl wrote:
> Rule:
>
> SHELL echo "#DROP fw wan
On 04/09/2012 12:35 PM, Steven Jan Springl wrote:
> On Monday 09 Apr 2012 19:09:28 Tom Eastep wrote:
>> On 04/09/2012 10:13 AM, Tom Eastep wrote:
>>> On 04/09/2012 06:56 AM, Steven Jan Springl wrote:
Rule:
SHELL echo "#DROP fw wan tcp 80"
produces the following error
On Monday 09 Apr 2012 19:09:28 Tom Eastep wrote:
> On 04/09/2012 10:13 AM, Tom Eastep wrote:
> > On 04/09/2012 06:56 AM, Steven Jan Springl wrote:
> >> Rule:
> >>
> >> SHELL echo "#DROP fw wan tcp 80"
> >>
> >> produces the following error messages:
> >>
> >> /bin/sh: Syntax error: Untermi
On 04/09/2012 10:13 AM, Tom Eastep wrote:
> On 04/09/2012 06:56 AM, Steven Jan Springl wrote:
>
>> Rule:
>>
>> SHELL echo "#DROP fw wan tcp 80"
>>
>> produces the following error messages:
>>
>> /bin/sh: Syntax error: Unterminated quoted string
>> ERROR: SHELL Script failed : /etc/shorewallT
On Monday 09 Apr 2012 18:13:48 Tom Eastep wrote:
> On 04/09/2012 06:56 AM, Steven Jan Springl wrote:
> > Rule:
> >
> > SHELL echo "#DROP fw wan tcp 80"
> >
> > produces the following error messages:
> >
> > /bin/sh: Syntax error: Unterminated quoted string
> > ERROR: SHELL Script failed :
On 04/09/2012 06:56 AM, Steven Jan Springl wrote:
> Rule:
>
> SHELL echo "#DROP fw wan tcp 80"
>
> produces the following error messages:
>
> /bin/sh: Syntax error: Unterminated quoted string
> ERROR: SHELL Script failed : /etc/shorewallT8/rules (line 15)
Steven,
Doesn't this happen on
Tom
Rule:
SHELL echo "#DROP fw wan tcp 80"
produces the following error messages:
/bin/sh: Syntax error: Unterminated quoted string
ERROR: SHELL Script failed : /etc/shorewallT8/rules (line 15)
Steven.
--
For De
On 4/8/12 2:50 PM, "Steven Jan Springl" wrote:
>
>Confirmed, the patch fixes the issue.
Thanks, Steven
-Tom
You do not need a parachute to skydive. You only need a parachute to
skydive twice.
--
For Developers, A Lo
On Sunday 08 Apr 2012 19:20:15 Tom Eastep wrote:
> On 4/8/12 9:28 AM, "Steven Jan Springl" wrote:
> >BEGIN SHELL
> >echo "DROP fw lan tcp 80"
> >echo "DROP fw lan tcp 81,82"
> >END SHELL
> >
> >The following error message is produced:
> >
> >ERROR: Invalid/Unknown tcp
On 4/8/12 9:28 AM, "Steven Jan Springl" wrote:
>
>BEGIN SHELL
>echo "DROP fw lan tcp 80"
>echo "DROP fw lan tcp 81,82"
>END SHELL
>
>The following error message is produced:
>
>ERROR: Invalid/Unknown tcp port/service (80echo) :
>SHELL@/etc/shorewallC1/rules:16 (l
Tom
I have applied both patches.
The original issue has been fixed.
--
When the rules file contains:
BEGIN SHELL
echo "DROP fw lan tcp 80"
echo "DROP fw lan tcp 81,82"
END SHELL
The following error
On 04/08/2012 05:58 AM, Steven Jan Springl wrote:
> The attached minimal config. produces the following error messages:
>
> /bin/sh: Syntax error: Unterminated quoted string
>ERROR: SHELL Script failed : /etc/shorewallC1/rules (line 15)
>
> This worked with RC1 and previous releases.
Steven
On 04/08/2012 05:58 AM, Steven Jan Springl wrote:
> The attached minimal config. produces the following error messages:
>
> /bin/sh: Syntax error: Unterminated quoted string
>ERROR: SHELL Script failed : /etc/shorewallC1/rules (line 15)
>
> This worked with RC1 and previous releases.
The at
Tom
The attached minimal config. produces the following error messages:
/bin/sh: Syntax error: Unterminated quoted string
ERROR: SHELL Script failed : /etc/shorewallC1/rules (line 15)
This worked with RC1 and previous releases.
Steven.
shorewallC1.tar.gz
Description: application/compressed
RC 2 is ready for testing.
Problems corrected:
1) The 4.5.1 Shorewall Lite and Shorewall6 Lite installers install the
wrong SysV init script on Debian and derivatives. That has been
corrected.
2) The getparams program now reads the installed shorewallrc file
rather than ~/.shorewal
28 matches
Mail list logo
