From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
wb <webmaster@jbsky.fr>
Subject: Re: [pve-devel] applied: [PATCH firewall] increase default nf_conntrack_max to kernel default
Date: Thu, 8 Jul 2021 09:51:08 +0200 [thread overview]
Message-ID: <8d425e41-53aa-ec3d-5473-da30011ca02e@proxmox.com> (raw)
In-Reply-To: <7c586e5ce8e90aa54f06b138fb4f4c02@mwinf5d29.me-wanadoo.net>
Hello Julien,
On 08.07.21 09:36, wb wrote:
> Hello Thomas,
>
> Currently with Proxmox, I have a Kubernetes node running on LXC. However, I have encountered an issue on the Container Network Interface (CNI) side and in order for it to work, the parameter /proc/sys/net/netfilter/nf_conntrack_max must be raised.
>
> You know that the container settings are managed by the hypervisor. However, something prevents to go above 262144. By searching a bit in your code, I found the limitation in Firewall.pm. I raised this value and the CNI works again.
>
> The last change was in this commit that you made.
> https://lists.proxmox.com/pipermail/pve-devel/2019-October/039748.html
>
> Is it possible to take into consideration the increase of this parameter in your code?
>
FYI, you can already override that setting in the node firewall options in the web-interface,
if set manually that vaile will always be preferred, at least as long the value is bigger than
the default of 262144.
cheers,
Thomas
next prev parent reply other threads:[~2021-07-08 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-08 7:36 wb
2021-07-08 7:51 ` Thomas Lamprecht [this message]
2021-07-08 20:01 ` alexandre derumier
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=8d425e41-53aa-ec3d-5473-da30011ca02e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=webmaster@jbsky.fr \
/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.