-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firewall ipset GUI #6187
Firewall ipset GUI #6187
Conversation
Great work! Two remarks:
|
Thanks for the feedback! Largely done. I'm still concerned about the boot hang, however. People who use a file list are still vulnerable to a boot hang if the firewall bump does not make it into 22.03.3 (and must BTW: How does one submit PRs for fw4 project? As a patch on the dev mailing list? Unless there is a reason that the comment field needs to be a |
The boot fix was added a few days after the 22.03.2 release already, it will definitely be part of 22.03.3 |
last push changed 'enabled' into checkboxes outside of modal, and put it to the last column on right, more in line to be consistent with other dialogues. |
LGTM |
The comment option for ipset definitions is incorrectly declared as bool and not actually used anywhere in the nftables output rendering. Solve this issue by changing it to the proper "string" type and expose the user configured comment as "comment" property in the generated nftables output. Also add some initial test coverage for ipset declarations to better spot such inconsistencies in the future. Ref: openwrt/luci#6187 (comment) Reported-by: Paul Dee <itsascambutmailmeanyway@gmail.com> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small remark
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
Hi @jow- any final comments? |
The 1:
|
Done |
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/snats.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/forwards.js
Show resolved
Hide resolved
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/rules.js
Outdated
Show resolved
Hide resolved
Resolved. |
applications/luci-app-firewall/htdocs/luci-static/resources/view/firewall/ipsets.js
Outdated
Show resolved
Hide resolved
Enable it and place it between snats and custom tabs Tested on 22.03.2, 22.03.3 Signed-off-by: Paul Dee <itsascambutmailmeanyway@gmail.com>
Signed-off-by: Paul Dee <itsascambutmailmeanyway@gmail.com>
Signed-off-by: Paul Dee <itsascambutmailmeanyway@gmail.com>
Signed-off-by: Paul Dee <itsascambutmailmeanyway@gmail.com>
Resolved. |
@jow- apparently you already picked these into master. I guess I can close this? I was confused as to why my rebase was coming up empty 😉 |
Needs some feedback before commit.
Variously tested on 22.03.2. This is unlikely to land in 22.03.2, unless someone specially pulls/builds with this PR, so we can probably remove the loadfile GUI warning. See also this which seems related.
We could probably drop the
if...else
blocks that check for fw4 if there are no cases where units would run e.g. fw3 in builds from now onward.Edit: displays string for firewall version (4 or not 4).