Messages

Hey folks,

I'm currently replacing my Pi-hole with the Unbound plugin in OPNsense. That works well so far.
My girlfriend had access to our Pi-hole before, so, to immitate the former state I wanted to create a OPNsense user for her with only access to Unbound's "blocklists" page (/ui/unbound/dnsbl/index). But this currently is not possible, since there's no default ruleset, that provides this functionality. Almost all pages have their own rule, except "blocklists".

There're now two possibilities, at least from my point of view:

• A blocklist permission is added to OPNsense and deployed in an upcoming patch.
• I add this permission by my own.

I attempted to try the second variant, with the help of https://forum.opnsense.org/index.php?topic=3431.0, but it doesn't matter if I add my own ACL.xml in its own folder or edit Unbound's ACL.xml: After that the OPNsense Web UI is failing to load and I need to undo my changes.
What am I potentially missing?

Creating a parent interface also worked for me. Thank you spark5 and hmronline.

But I'm still a bit puzzled, why it's now relevant, when it wasn't before...

Hello folks,

I found out to have exactly the same issue like the thread creator after upgrading from 21ish to 22.1 with a similar setup (OPNsense in a Proxmox VM).
I also reverted the upgrade with a rollback of a full VM backup.

Let me know, how I can help with additional information.

- Stumie