From: alexandre derumier <aderumier@odiso.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH firewall] increase default nf_conntrack_max to kernel default
Date: Thu, 08 Jul 2021 22:01:40 +0200 [thread overview]
Message-ID: <6fc2fa6ee90a025f240293c520eaf4219ce031f1.camel@odiso.com> (raw)
In-Reply-To: <7c586e5ce8e90aa54f06b138fb4f4c02@mwinf5d29.me-wanadoo.net>
Hi,
you can change it in the proxmox node firewall options.
Le jeudi 08 juillet 2021 à 09:36 +0200, wb a écrit :
> 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?
>
> Waiting for your feedback.
>
> Sincerely.
>
> Julien BLAIS
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
prev parent reply other threads:[~2021-07-08 20:02 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
2021-07-08 20:01 ` alexandre derumier [this message]
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=6fc2fa6ee90a025f240293c520eaf4219ce031f1.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/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.