-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility Issue Between iptables-nft, nftables and netfilter-mailcow #5847
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I think this issue is still valid and can cause a lot of problems. E.g., in our system, where we are running libvirt/KVM in parallel, libvirt is not able to change the firewall rules and therefore refuses to start. |
i also copy and say i am affected for this imho, having the similar warning |
same here |
Same here. I agree with the suggestions in the OP. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I think the bug report is still valid, isn't it? Still no official answer to now. 🥲 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04.4 LTS
Server/VM specifications:
64GB Ram, 8 cores (Intel(R) Core(TM) i7-7700 CPU)
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
mailcow with docker direct on host, other VMs using KVM
Docker version:
26.0.1
docker-compose version or docker compose version:
v2.16.1
mailcow version:
2024-04
Reverse proxy:
Traefik
Logs of git diff:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: