Certain upstream switch to `firewall4` aka `nftables` instead of `iptables`
See original GitHub issueHi all, especially @openwrt/luci-admin,
for the next OpenWrt release firewall4
is considered as a replacement of the current iptables
based firewall
package. While the configuration stays within /etc/config/firewall
, packages using iptables
directly may see trouble.
This is a heads up for everyone maintaining such packages but also please post packages here that would be affected so a smother migration is possible.
Heads up for packages.git: https://github.com/openwrt/packages/issues/16818 Heads up for routing.git: https://github.com/openwrt/routing/issues/731
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Certain upstream switch to `firewall4` aka `nftables` instead of ...
Hi all, especially @openwrt/packages-write, for the next OpenWrt release firewall4 is considered as a replacement of the current iptables ...
Read more >Firewall4 / NFtables Tips and Tricks - OpenWrt Forum
Certain upstream switch to `firewall4 ` aka `nftables` instead of `iptables`. opened 05:49AM - 06 Oct 21 UTC. aparcar. help wanted.
Read more >Moving from iptables to nftables
This page gives information on moving/migrating from the old iptables/xtables (legacy) world to the new nftables framework.
Read more >Updated OpenWrt/muvirt/kernels + SFP info for LuCI
... with iptables rather than nftables (see openwrt/packages: Certain upstream switch to firewall4 aka nftables instead of iptables ).
Read more >Chapter 47. Getting started with nftables Red Hat Enterprise ...
If your firewall configuration still uses iptables rules, you can migrate your iptables rules to nftables . 47.1.1. When to use firewalld, nftables,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think that that Status->Firewall menu item and page is still totally iptables based after 48599d8d1d, right?
https://github.com/openwrt/luci/blob/master/modules/luci-mod-status/htdocs/luci-static/resources/view/status/iptables.js
Oh, it was never closed: https://github.com/openwrt/luci/pull/5839