From: Florian Westphal <fw@strlen.de>
To: Martin Zaharinov <micron10@gmail.com>
Cc: Florian Westphal <fw@strlen.de>,
pablo@netfilter.org, Paolo Abeni <pabeni@redhat.com>,
netfilter-devel@vger.kernel.org,
netfilter <netfilter@vger.kernel.org>
Subject: Re: Kernel 6.0.0 bug pptp not work
Date: Thu, 6 Oct 2022 15:43:40 +0200 [thread overview]
Message-ID: <20221006134340.GA31481@breakpoint.cc> (raw)
In-Reply-To: <0DF040F3-ACC8-447E-99DA-BB77FEE03C7E@gmail.com>
Martin Zaharinov <micron10@gmail.com> wrote:
> Huh
> Very strange in kernel 6.0.0 i not found : net.netfilter.nf_conntrack_helper
>
>
> in old kernel 5.19.14 in sysctl -a | grep net.netfilter.nf_conntrack_helper
>
> net.netfilter.nf_conntrack_helper = 1
Yes, so this is expected -- 6.0.0 should behave like 5.19.14 with
net.netfilter.nf_conntrack_helper=0.
You need something like:
table inet foo {
ct helper pptp {
type "pptp" protocol tcp
l3proto ip
}
chain prerouting {
type filter hook prerouting priority filter; policy accept;
tcp dport 1723 ct helper set "pptp"
}
}
... so that the helper will start processing traffic on the pptp control port.
You might want to refine the rule a big, e.g.
'iifname ppp*' or similar, to restrict/limit the helper to those clients that need
it.
next prev parent reply other threads:[~2022-10-06 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 23:34 Kernel 6.0.0 bug pptp not work Martin Zaharinov
2022-10-05 23:41 ` Martin Zaharinov
2022-10-06 11:01 ` Pablo Neira Ayuso
2022-10-06 11:18 ` Florian Westphal
2022-10-06 12:46 ` Martin Zaharinov
2022-10-06 12:57 ` Martin Zaharinov
2022-10-06 13:04 ` Pablo Neira Ayuso
2022-10-06 13:06 ` Martin Zaharinov
2022-10-06 12:57 ` Pablo Neira Ayuso
2022-10-06 13:43 ` Florian Westphal [this message]
2022-10-06 14:16 ` Martin Zaharinov
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=20221006134340.GA31481@breakpoint.cc \
--to=fw@strlen.de \
--cc=micron10@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.