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
{{ message }}
This repository was archived by the owner on Nov 2, 2024. It is now read-only.
It took me some time to figure out why the firewall configuration on some containers were not taking effect on iptables.
Turns out the firewall rule configuration has no effect if the firewall is not enabled on the virtual NIC level too.
Enabling the firewall on the NIC level by default is harmless, as it does not enable any firewall rules out of the box.
Then, my suggestion is to enable the firewall by default on every VM virtual network interface by adding ,firewall=1 to PCT_OPTIONS:
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
Uh oh!
There was an error while loading. Please reload this page.
-
It took me some time to figure out why the firewall configuration on some containers were not taking effect on iptables.
Turns out the firewall rule configuration has no effect if the firewall is not enabled on the virtual NIC level too.
Enabling the firewall on the NIC level by default is harmless, as it does not enable any firewall rules out of the box.
Then, my suggestion is to enable the firewall by default on every VM virtual network interface by adding
,firewall=1
toPCT_OPTIONS
:Beta Was this translation helpful? Give feedback.
All reactions