From: Florian Westphal <fw@strlen.de>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Florian Westphal <fw@strlen.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: b118509076b3 (probably) breaks my firewall
Date: Thu, 8 Sep 2022 23:48:59 +0200 [thread overview]
Message-ID: <20220908214859.GD16543@breakpoint.cc> (raw)
In-Reply-To: <78611fbd-434e-c948-5677-a0bdb66f31a5@googlemail.com>
Chris Clayton <chris2553@googlemail.com> wrote:
[ CC Pablo ]
> On 08/09/2022 20:19, Florian Westphal wrote:
> > Chris Clayton <chris2553@googlemail.com> wrote:
> >> Just a heads up and a question...
> >>
> >> I've pulled the latest and greatest from Linus' tree and built and installed the kernel. git describe gives
> >> v6.0-rc4-126-g26b1224903b3.
> >>
> >> I find that my firewall is broken because /proc/sys/net/netfilter/nf_conntrack_helper no longer exists. It existed on an
> >> -rc4 kernel. Are changes like this supposed to be introduced at this stage of the -rc cycle?
> >
> > The problem is that the default-autoassign (nf_conntrack_helper=1) has
> > side effects that most people are not aware of.
> >
> > The bug that propmpted this toggle from getting axed was that the irc (dcc) helper allowed
> > a remote client to create a port forwarding to the local client.
>
>
> Ok, but I still think it's not the sort of change that should be introduced at this stage of the -rc cycle.
> The other problem is that the documentation (Documentation/networking/nf_conntrack-sysctl.rst) hasn't been updated. So I
> know my firewall is broken but there's nothing I can find that tells me how to fix it.
Pablo, I don't think revert+move the 'next' will avoid this kinds of
problems, but at least the nf_conntrack-sysctl.rst should be amended to
reflect that this was removed.
I'd keep it though because people that see an error wrt. this might be
looking at nf_conntrack-sysctl.rst.
Maybe just a link to
https://home.regit.org/netfilter-en/secure-use-of-helpers/?
What do you think?
next prev parent reply other threads:[~2022-09-08 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 19:13 b118509076b3 (probably) breaks my firewall Chris Clayton
2022-09-08 19:19 ` Florian Westphal
2022-09-08 21:22 ` Chris Clayton
2022-09-08 21:48 ` Florian Westphal [this message]
2022-09-09 10:19 ` Pablo Neira Ayuso
2022-09-09 18:21 ` Chris Clayton
2022-09-09 18:31 ` Chris Clayton
2022-09-10 2:02 ` removing conntrack helper toggle to enable auto-assignment [was Re: b118509076b3 (probably) breaks my firewall] Pablo Neira Ayuso
2022-09-10 3:49 ` Willy Tarreau
2022-09-19 19:40 ` Jakub Kicinski
2022-09-19 20:23 ` Florian Westphal
2022-09-19 20:57 ` Jakub Kicinski
2022-09-19 21:27 ` Florian Westphal
2022-09-20 6:49 ` Chris Clayton
2022-09-20 9:01 ` Thorsten Leemhuis
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=20220908214859.GD16543@breakpoint.cc \
--to=fw@strlen.de \
--cc=chris2553@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).