Not to interrupt, but at least there's a decent reply-to on this mailing list.
Everything is in a bit of a shake-up with CentOS going E.O.L. and Bill Gates
grinning from ear to ear after Microsoft's acquisition of GitHub and IBM's
acquisition of Red Hat.
I could come up with numerous conspiracy
Shorewall (and Shorewall6) has been fantastic to me, as a multi-ISP
user. I'm deeply indebted to Tom for this fantastic tool, and all the
work he put into the documentation especially. Nothing else seems to
come close to ease-of-configuration and maintenance. I'm dreading the
day when Debian
Thank you for your answer Phil.
>I'm not sure what you mean by this, but I personally do not trust ANY
>code written by large language models.
OK you may doubt, naturally.
the best way to evacuate doubt is to try it yourself.
I am not very advanced in this matter , but I can say you that I tried
On 2/6/25 10:28, Sam wrote:
I think the bigger issue is that Shorewall is more of an iptables
configuration tool. And iptables is now deprecated.
Then what is needed is perhaps a project to update shorewall to emit the
CURRENT flavor of Linux firewalling rules. (One that **does not**
depend
On 2/6/25 08:36, Jlem wrote:
Dear Shorewall friends,
I have been using Shorewall for 20 years.
I find it very close to the simple description of network use cases,
ignoring the assembly-like language that can be seen on other products.
Thus we have a very readable and therefore very maintainabl
On 2/6/25 08:36, Jlem wrote:
Dear Shorewall friends,
I have been using Shorewall for 20 years.
I find it very close to the simple description of network use cases,
ignoring the assembly-like language that can be seen on other products.
Thus we have a very readable and therefore very maintainabl
On Thu, 2025-02-06 at 03:46 +0100, Matt Darfeuille wrote:
>
> Monkeypatching..
Could you expand?
Cheers,
b.
___
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
Dear Shorewall friends,
I have been using Shorewall for 20 years.
I find it very close to the simple description of network use cases,
ignoring the assembly-like language that can be seen on other products.
Thus we have a very readable and therefore very maintainable language.
In short, I find it h