Vieri Di Paola wrote:
> As already stated by others I'm also deeply grateful for what
> Shorewall has done for me.
> It sure makes iptables look easy... but I think it's great that it
> also takes care of tc, route tables, route rules, etc.
> So it's much more than a "firewall”.
Indeed, and at o
As already stated by others I'm also deeply grateful for what
Shorewall has done for me.
It sure makes iptables look easy... but I think it's great that it
also takes care of tc, route tables, route rules, etc.
So it's much more than a "firewall".
Incidentally, I'm seeing these errors more often l
On 2/13/25 16:18, Simon wrote:
Tom Eastep wrote:
I now spent my time doing a bit of traveling, walking my dog, and riding my
bicycle - I am commited to continuing to ride through next year when I turn 80
years old :-).
Sounds like you are still quite fit and enjoying retirement - long may
Tom Eastep wrote:
> I now spent my time doing a bit of traveling, walking my dog, and riding my
> bicycle - I am commited to continuing to ride through next year when I turn
> 80 years old :-).
Sounds like you are still quite fit and enjoying retirement - long may that
continue.
And I’ll sec
On Tue, 11 Feb 2025 01:35:09 -0500
Winston Sorfleet wrote:
> Good resource Wayne. Can you (or Tuomi) comment on how mature
> foomuuri is for multi-ISP? Here is my usecase:
Plese, use foomuuri support channel for related questions.
https://github.com/FoobarOy/foomuuri/discussions
--
Tuomo So
Good resource Wayne. Can you (or Tuomi) comment on how mature foomuuri
is for multi-ISP? Here is my usecase:
1. ISP 1 is slow static IPv4 on PPPoE. IPv6/56 available via dhcp6 but
not enabled due to my not being able to get it working along with IPv6
on ISP 2 with Shorewall6 (incoming packe
On 2/10/25 06:29, Tuomo Soini via Shorewall-users wrote:
Foomuuri is not systemd specific. It is something like one hour work to
make foomuuri work with OpenRC/sysv/whatever + cron, if somebody wants
that. You only need to create init scripts to start the services, and
convert timer+service combi
On Thu, 6 Feb 2025 12:57:05 -0500
Phil Stracchino wrote:
> 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
> t
* On 2025 08 Feb 10:24 -0600, Wayne Shumaker wrote:
> I have now converted to foomuuri and find it was relatively painless,
> including ulogd2 logging. I also found adding blocklists fairly
> convenient with automatic daily updates.
>
> https://blog.frehi.be/2024/11/30/protecting-your-server-from-
On 2/8/25 12:58, Benny Pedersen wrote:
Wayne Shumaker skrev den 2025-02-08 16:56:
At 2/6/2025 02:25 PM, Winston wrote:
Shorewall (and Shorewall6) has been fantastic to me, as a multi-ISP
user.
if that debian maintaince stops, one can still find older slackware that
still works, just remember
Wayne Shumaker skrev den 2025-02-08 16:56:
At 2/6/2025 02:25 PM, Winston wrote:
Shorewall (and Shorewall6) has been fantastic to me, as a multi-ISP
user.
if that debian maintaince stops, one can still find older slackware that
still works, just remember to not keep using precompiled problems
At 2/6/2025 02:25 PM, Winston wrote:
>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 maint
Definitely appreciate everything you've done, and even your continuing
contribution here on this list. Shorewall isn't obsolete yet, for
sure. Hoping that Tuomo's project continues to mature and likely I will
go in that direction when the time comes, but until then... thanks!
Enjoy your dog,
On 2/7/25 19:56, Tom Eastep wrote:
On 2/6/25 1:25 PM, Winston Sorfleet wrote:
Tom, if you're reading this, can
I ask - are you still running your own systems, and what you expect to
be shifting to yourself?
Winston,
At the time that I stepped down from Shorewall, I terminated my
commercial
Well, Tom, enjoy your time, because you deserve it.
You helped me out often over the years, and I still run Shorewall, and it's
still doing a great job.
Nigel.
On Fri, Feb 7, 2025 at 5:57 PM Tom Eastep wrote:
> On 2/6/25 1:25 PM, Winston Sorfleet wrote:
> > Tom, if you're reading this, can
>
On 2/6/25 1:25 PM, Winston Sorfleet wrote:
Tom, if you're reading this, can
I ask - are you still running your own systems, and what you expect to
be shifting to yourself?
Winston,
At the time that I stepped down from Shorewall, I terminated my
commercial internet service. I still run shore
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
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
23 matches
Mail list logo
