Re: [Shorewall-users] Shorewall in (highly?) "compartmentalized" deployments: our case-history [Was: Shorewall 5.2.3]

2019-02-25 Thread ObNox
On 24/02/2019 09:33, Damiano Verzulli wrote: In our main location we are running two shorewall boxes, each one connected to an 802.1q trunk, firewalling traffic between related VLANs. In detail, currently: - mixer: 27 zones, related to 27 VLANs - equalizer: 56 zones, related to 56 VLANs [...]

Re: [Shorewall-users] The Next Chapter for Shorewall

2019-02-25 Thread Fog_Watch
On Mon, 25 Feb 2019 09:09:44 -0500 Roberto C. Sánchez wrote: > Our intent is to > continue to grow the community which Tom has so painstakingly built > over the years. Outstanding news. ___ Shorewall-users mailing list

Re: [Shorewall-users] The Next Chapter for Shorewall

2019-02-25 Thread Phil Stracchino
On 2/25/19 9:09 AM, Roberto C. Sánchez wrote: > While Shorewall as a software product can certainly be described as > mature, firewalling in Linux continues to evolve and there is no > technical reason why Shorewall cannot continue to evolve along with it. > To that end, Tom has identified a small

Re: [Shorewall-users] The Next Chapter for Shorewall

2019-02-25 Thread Sam
On 2/25/19 8:09 AM, Roberto C. Sánchez wrote: Shorewall Community ... You are likely aware that Tom Eastep, founder and principal developer of Shorewall, recently announced his effective retirement from the Shorewall project after nearly 50 years working in technology and nearly 20 years since

[Shorewall-users] The Next Chapter for Shorewall

2019-02-25 Thread Roberto C . Sánchez
Shorewall Community ... You are likely aware that Tom Eastep, founder and principal developer of Shorewall, recently announced his effective retirement from the Shorewall project after nearly 50 years working in technology and nearly 20 years since he started the project. While Shorewall as a

Re: [Shorewall-users] locking processes left behind

2019-02-25 Thread Brian J. Murrell
On Wed, 2018-08-01 at 14:27 -0700, Tom Eastep wrote: > So, getting back to this... > Any results with this patch? I would like to include this fix in > 5.2.0.5. On the shorewall (i.e. not the "lite") machine, I have 5.2.0.5 installed that includes this patch. On the "lite" machine I have