> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 03/08/2017 11:14 AM, Simon Matter wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
>>> On 03/07/2017 11:33 PM, Simon Matter wrote:
Hi Tom and all,
Since upgrading from shorewall-5.1.1 to shorewall-5.1.2.1 I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/08/2017 11:14 AM, Simon Matter wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> On 03/07/2017 11:33 PM, Simon Matter wrote:
>>> Hi Tom and all,
>>>
>>> Since upgrading from shorewall-5.1.1 to shorewall-5.1.2.1 I
>>> have a new
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 03/07/2017 11:33 PM, Simon Matter wrote:
>> Hi Tom and all,
>>
>> Since upgrading from shorewall-5.1.1 to shorewall-5.1.2.1 I have a
>> new problem with longstanding TCP connections being killed during
>> "shorewall reload".
>>
>> This has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following fix was inadvertently omitted from 5.1.2.2:
8) When running the 'update' command where:
- A tcfile exists
- There is a writable mangle file on the CONFIG_PATH (not in
$SHAREDIR/configfiles/)
the update will not wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/07/2017 11:33 PM, Simon Matter wrote:
> Hi Tom and all,
>
> Since upgrading from shorewall-5.1.1 to shorewall-5.1.2.1 I have a
> new problem with longstanding TCP connections being killed during
> "shorewall reload".
>
> This has never happen
> Hi Tom and all,
>
> Since upgrading from shorewall-5.1.1 to shorewall-5.1.2.1 I have a new
> problem with longstanding TCP connections being killed during "shorewall
> reload".
Just in case it help I've attached a diff of the compiled firewall script.
Simon
firewall.diff
Description: Binary da
