[FS#3520] Firewall rules not applied on boot

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3520 - Firewall rules not applied on boot
User who did this - Jo-Philipp Wich (jow-)

----------
Most likely the both iptables commands trigger kernel module loading in the host kernel and/or trigger the availability of netfilter tables within your container which allows firewall3 to function as expected.

The fw3 executable itself will check if a given table is available through /proc/net/ip_tables_names and /proc/net/ip6_tables_names. If the table is not found in there, it is skipped - which likely leads to the issue you see.

Marking this bug as duplicate of FS#2575 since it appears to be essentially the same issue.

So the underlying problem appears to be that the various container/virtualization environments do not properly populate proc/net/ip{,6}_tables_names until after iptables has been run which somehow directly or indirectly triggers a refresh of these files.
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3520#comment9227

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.