network: firewall, firewall4, iptables: switch to legacy mode (b9cef980) · Commits · Turris / Turris OS / Turris Build · GitLab

Snippets Groups Projects

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

Verified Commit b9cef980 authored 1 year ago by

Tomas Zak

network: firewall, firewall4, iptables: switch to legacy mode

If firewall ver. 3 is installed, then iptables switched to legacy mode. With
this option we keep compatibility with other packages like mwan3 which reguires
iptables in legacy mode. When switche to firewall ver. 4, iptables is switched
back to nft mode.

parent 9b039514

Branches

Tags

1 merge request!702network: firewall, firewall4, iptables: switch to legacy mode

Pipeline #122870 passed with stages

in 8 minutes and 46 seconds

Hide whitespace changes

Inline Side-by-side

Showing with 159 additions and 0 deletions

Please register or to comment