yeah i know (deprication warning).
If you guys dont mind the offtopic question - what are you planning to switch
to after shorewall?
I'll miss shorewall ;) Our customers will too it took us ages to explain to
them how shorewall works. will have to explain something new soon then ;)
On Wed,
On Wed, 28 Feb 2024 19:45:55 +0100
Peter Thurner | Blunix GmbH via Shorewall-users
wrote:
> I am aware of that, however sometimes there isn't really a much
> better way than using dns names. that doesn't just affect shorewall
> but iptables in general of course.
>
> ok but long story short - I
well thats nice. didnt know that!
my case is a bit different but still VERY interesting post!
On Wed, Feb 28, 2024 at 07:36:16PM +0100, Benny Pedersen wrote:
> Peter Thurner | Blunix GmbH via Shorewall-users skrev den 2024-02-28 17:49:
> > Hello shorewall users,
> >
> > is there a way to ignore
I am aware of that, however sometimes there isn't really a much better way than
using dns names. that doesn't just affect shorewall but iptables in general of
course.
ok but long story short - I am aware I'm doing this wrong, and hence there is
no option to ignore failed rules, yes?
I suppose
Peter Thurner | Blunix GmbH via Shorewall-users skrev den 2024-02-28
17:49:
Hello shorewall users,
is there a way to ignore failing rules in shorewall, specifically if
/etc/shorewall/rules contains something like
ACCEPT local pub:this.domain.doesnt.exist.com tcp 443
iptables is not dns
On Wed, 28 Feb 2024 17:49:37 +0100
Peter Thurner | Blunix GmbH via Shorewall-users
wrote:
> Hello shorewall users,
>
> is there a way to ignore failing rules in shorewall, specifically if
> /etc/shorewall/rules contains something like
>
> ACCEPT local pub:this.domain.doesnt.exist.com tcp 443
Hello shorewall users,
is there a way to ignore failing rules in shorewall, specifically if
/etc/shorewall/rules contains something like
ACCEPT local pub:this.domain.doesnt.exist.com tcp 443
?
with kind regards,
Peter Thurner
CEO Blunix GmbH
--
Blunix GmbH
Glogauer Straße 21
10999 Berlin
