25.7.8 Reporting -> Unbound DNS -> Top blocked domains

[irrenarzt]

First off, thank you for the latest update! It looks like a lot of work went into this one, which we all appreciate.

I have a very minor issue noticed after this update, and want to confirm whether it's an actual bug or if it's a *me* problem. Prior to 25.7.8 if I went to Reporting -> Unbound DNS -> Top blocked domains, it would display the full name of the block list used to block a domain. However, after 25.7.8, mine is displaying an awkward "hgz005" instead of the full name. Anyone else seeing this?

I have unchecked and then reapplied the block lists to see if that would restore it, but it did not.

[Monviech (Cedrik)]

i think the name comes from here

https://github.com/opnsense/core/blob/cf5b944d63a6853fa5d0d2736db154fd6f2ca5f4/src/opnsense/service/templates/OPNsense/Unbound/core/blocklists.conf#L34

If you think theres an issue please open one on github.

[OPNenthu]

Yeah it looks like those dictionary keys have replaced the list names in the reports.  "Steven Black List" is now just "sb" for example.

Side note: even if unrelated to this issue, thank you for bringing the per-network blocklist feature to the community edition!

[Monviech (Cedrik)]

The main reason for that is to give users an alternative to adguard home since the binary of that cannot be built in the opnsense built servers and its operation is located in russia.

Also if people do not install custom code I assume there will be less support noise in general.

But this realisation will need some time to spread, the adguard home suggestion is just too present.

[Patrick M. Hausen]

Doesn't the FreeBSD port download the source from github and compile with golang locally? That should work in poudriere just as well?

[Monviech (Cedrik)]

Im not sure what the exact issue is. I recently built my own lang/go project and also created a port for it. It does download the source from github and build it just fine in the OPNsense build server.

But the OPNsense build server afaik does not use poudriere for building packages.

First glance there isn't too much difference:
https://github.com/opnsense/ports/blob/master/www/adguardhome/Makefile
https://github.com/opnsense/ports/blob/master/opnsense/ndp-proxy-go/Makefile

Maybe @franco reads this and can respond with the real reason why adguard home has issues with the build.

[Patrick M. Hausen]

But the OPNsense build server afaik does not use poudriere for building packages.

It should 😛