-
Notifications
You must be signed in to change notification settings - Fork 84
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
NAT not working under higher load #890
Comments
Can you provide the full |
of course, here you go
I'm a bit unsure about the nft chains, so here's the iptables format
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Debian 12 netavark 1.4.0-3 podman 4.3.1+ds1-8+b1 aardvark 1.4.0-3
I experience issues with NAT not being done, in my case only for one source address. My traffic is 99% IPv6.
I run an rsyslog container. The syslog clients send the traffic to the podman host on port 514 UDP.
With tcpdump I see that the traffic hits the host and is then DNATed to the IP of the container
One syslog client is much more active than others as it's a firewall that sends all rejected/dropped packet logs to the rsyslog container. Those packets are not NATed thus never arriving at the container.
I'm not certain that it's due to the fact that the traffic from this source is higher but it's my best guess.
This is the network my guests use:
Here's an excerpt of the nft ruleset:
The text was updated successfully, but these errors were encountered: