All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reindl Harald <h.reindl@thelounge.net>
To: Phil Sutter <phil@nwl.cc>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Arturo Borrero Gonzalez <arturo@netfilter.org>,
	netfilter-devel@vger.kernel.org, kadlec@netfilter.org
Subject: Re: [iptables PATCH] iptables-nft: fix basechain policy configuration
Date: Fri, 9 Oct 2020 12:07:57 +0200	[thread overview]
Message-ID: <0669e18b-661b-efec-fe15-e540290c3219@thelounge.net> (raw)
In-Reply-To: <20201009093705.GF13016@orbyte.nwl.cc>



Am 09.10.20 um 11:37 schrieb Phil Sutter:
> I guess fundamentally this is due to legacy design which keeps builtin
> chains in place at all times. We could copy that in iptables-nft, but I
> like the current design where we just delete the whole table and start
> from scratch.
> 
> Florian made a related remark a while ago about flushing chains with
> DROP policy: He claims it is almost always a mistake and we should reset
> the policy to ACCEPT in order to avoid people from locking themselves
> out. I second that idea, but am not sure if such a change is tolerable
> at all.
bad idea!

nothing is locking you out just because of a short drop phase, at least 
not over the past 12 years, that's what tcp retransmits are for

when you once accept i have someone which should never have been 
accepted in the conntracking - sorry - but when i say drop i literally 
mean drop at any point in time

  reply	other threads:[~2020-10-09 10:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 11:44 [iptables PATCH] iptables-nft: fix basechain policy configuration Arturo Borrero Gonzalez
2020-10-02 12:07 ` Phil Sutter
2020-10-02 12:15   ` Pablo Neira Ayuso
2020-10-02 12:28     ` Phil Sutter
2020-10-02 12:47       ` Pablo Neira Ayuso
2020-10-02 13:31         ` Phil Sutter
2020-10-02 14:39           ` Pablo Neira Ayuso
2020-10-08 17:31 ` Pablo Neira Ayuso
2020-10-09  8:29   ` Phil Sutter
2020-10-09  8:50     ` Pablo Neira Ayuso
2020-10-09  9:37       ` Phil Sutter
2020-10-09 10:07         ` Reindl Harald [this message]
2020-10-09 10:14           ` Phil Sutter
2020-10-09 10:28             ` Reindl Harald
2020-10-09 10:37         ` Jozsef Kadlecsik
2020-10-09 12:04           ` Phil Sutter
2020-10-09 19:05             ` Jozsef Kadlecsik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0669e18b-661b-efec-fe15-e540290c3219@thelounge.net \
    --to=h.reindl@thelounge.net \
    --cc=arturo@netfilter.org \
    --cc=kadlec@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.