From: Eric Dumazet <eric.dumazet@gmail.com>
To: Vasily Averin <vvs@openvz.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>,
edumazet@google.com
Cc: netfilter-devel@vger.kernel.org, kernel@openvz.org
Subject: Re: troubles caused by conntrack overlimit in init_netns
Date: Sat, 2 Apr 2022 10:12:18 -0700 [thread overview]
Message-ID: <80f0f13f-d671-20fb-ffe6-5903f653c9ed@gmail.com> (raw)
In-Reply-To: <de70cc55-6c11-d772-8b08-e8994fd934a0@openvz.org>
On 4/2/22 03:33, Vasily Averin wrote:
> Pablo, Florian,
>
> There is an old issue with conntrack limit on multi-netns (read container) nodes.
>
> Any connection to containers hosted on the node creates a conntrack in init_netns.
> If the number of conntrack in init_netns reaches the limit, the whole node becomes
> unavailable.
Can you describe network topology ?
Are you using macvlan, ipvlan, or something else ?
> To avoid it OpenVz had special patches disabled conntracks on init_ns on openvz nodes,
> but this automatically limits the functionality of host's firewall.
>
> This has been our specific pain for many years, however, containers are now
> being used much more widely than before, and the severity of the described problem
> is growing more and more.
>
> Do you know perhaps some alternative solution?
>
> Thank you,
> Vasily Averin
next prev parent reply other threads:[~2022-04-02 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 10:33 troubles caused by conntrack overlimit in init_netns Vasily Averin
2022-04-02 11:11 ` Florian Westphal
2022-04-02 13:00 ` Nikita Yushchenko
2022-04-04 7:59 ` Vasily Averin
2022-04-02 17:12 ` Eric Dumazet [this message]
2022-04-02 18:32 ` Vasily Averin
2022-04-02 18:50 ` Eric Dumazet
2022-04-02 19:52 ` Vasily Averin
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=80f0f13f-d671-20fb-ffe6-5903f653c9ed@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kernel@openvz.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vvs@openvz.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).