You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running podman with netavark and aardvark on Debian 12 Bookworm.
Before starting to use Podman I had been using plain nftables to regulate traffic flow.
Now using podman netavark regulates rules. As a result my host is fully open to the whole internet.
What is best practice to address this issue? I'm aware that most users use some kind of wrapper like firewalld or ufw.
I would be willing to use such a tool, if it integrates into the ecosystem of netavark.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm running podman with netavark and aardvark on Debian 12 Bookworm.
Before starting to use Podman I had been using plain nftables to regulate traffic flow.
Now using podman netavark regulates rules. As a result my host is fully open to the whole internet.
What is best practice to address this issue? I'm aware that most users use some kind of wrapper like firewalld or ufw.
I would be willing to use such a tool, if it integrates into the ecosystem of netavark.
This docker howto addresses my issue but I don't want to use docker.
https://docs.docker.com/network/packet-filtering-firewalls/
Beta Was this translation helpful? Give feedback.
All reactions