[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 - Dan Goodliffe (rascalDan)

----------
Continued to dig around with various bits of tweaks and logging etc.

I think I finally bottomed the issue, but I'm not sure of the cause.

I've worked around it by adding


        iptables -L
        iptables -t nat -L


to /etc/init.d/firewall's boot() function before it calls start().

On the face of it, it made no sense. But then I figure this is what was I witnessing with the issue where sometimes restarting the firewall service worked and sometimes it didn't. If I've visited the firewall status page (which presumably invokes iptables or otherwise queries the iptable status for display purposes) that's enough to provide the same poke as calling iptables from the init script.

I think this is a variation of [[https://forum.openwrt.org/t/iptables-are-empty-at-boot-or-on-reload/47421/2]] but that was supposably fixed in v19... maybe it isn't.
----------

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

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.