Hi,
> [...]
>
> Sorry, but I don't agree with the following reasons. Let me briefly explain
> why.
>
> All files under '/usr/share/firewall4/includes.d' are uci files. I can see
> all relevant options.
One problem with your suggested implementation is that you introduce a generic
directory
Hi,
Sorry for the late reply
instead of introducing uci includes that configure nft includes, why
not
encode the chain/position etc. values directly into the path/filename
and
directly include the file if it exists at the expected location?
I was just wondering why not use the new feature
Hi,
instead of introducing uci includes that configure nft includes, why not
encode the chain/position etc. values directly into the path/filename and
directly include the file if it exists at the expected location?
A potential pattern could be
