It does allow all packets to go through that have CT state invalid. This means that all packets that do not start a new connection flow (e.g. a TCP SYN), but are also not part of an existing connection flow get allowed through the firewall. The...
Joined journal from boot until network is down and some more informations.
Then I reboot server and disabled offloading with your command on botn nic 2 and 3, but after 8 minutes network goes down again.
Hello, there is a Bugzilla entry [0] for this. As Fabian noted there though, this is a pretty large feature that we cannot commit to or give any ETA for.
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=7410
some logs
2026-10-01T14:03:37.449165+02:00 prabackservername01 kernel: bnxt_en 0000:14:00.0 nic0: NIC Link is servername, 25000 Mbps (NRZ) full dservernamelex, Flow control: none
2026-10-01T14:03:37.449179+02:00 prabackservername01 kernel...
Thanks a lot for the update! Since this is already being worked on, implementing it separately would just mean duplicated effort.
For now, I’ll stick with the small shell script + dialog solution I already have, which basically does the same...
Hi!
One of our team members is already working on a backup job overview. I cannot provide an ETA for the feature right now, but it will come eventually. I'll be sure to forward the list of desired features you provided to the developer who has...
Dann gucken, ob das vms oder docker-Container kann, das wäre dann die beste Variante. Die VM kann sehr schlank sein ( eine vCPU und 512 mb bis 1gb RAM bei 5 gb storage reichen völlig aus) und mit aktivierten unattended-upgrades ( inklusive...
could you (and others affected):
* share the journal from booting up the machine until the issue occurred
* try disabling some offloading functionality: `ethtool -K <nic> rx-gro-hw off lro off`
I have the same (works in -19, stays down in -20), but with the bnxt_en driver for an Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller:
[ 11.380325] bnxt_en 0000:01:00.0 nic6: renamed from enp1s0f0np0
[...
Thanks for confirming! To clarify — when you say it landed in 7.2.x, do you mean upstream Linux 7.2, or is there already a timeline for when a Proxmox kernel build containing this fix (opt-in or otherwise) will be available? I couldn't find an...