The new unbound reporting is pretty cool

[tuto2]

2. No for me, all local even with 'All' set as the option for display. Possibly it may be how I have Unbound setup.

How is Unbound configured? Forwarding, special advanced options, DoT etc.

The total result set of the "live" view is limited to a 1000 entries for performance reasons. It might be that localhost is taking them all up. If there are specific clients you wish to view you can also click on a client in the "overview" page in the client graph and it will present you with a view of this clients' activity within that specific time period.

[aimdev]

DOT

Thanks for the advice.

[SpinningRust]

Unbound reporting is really cool. I'm a new user to OPNsense this month and am loving this new feature. One very minor suggestion would be to change the background font for the details tab to work better with the dark mode themes (like cicada or vicuna). I usually have to change to the default OPNsense theme to read that tab. Otherwise, fantastic work!

[Fright]

@SpinningRust
https://github.com/opnsense/plugins/issues/3290

[SpinningRust]

Wonderful, I'm glad it has been put into the backlog.

[dumbo]

Hi,

is this only a "design" glitch, or why does it block the A records but not the HTTPS records?

metrics.icloud.com A record blocked
metrics.icloud.com HTTPS record NOT blocked

[slackadelic]

Like the others I love the new reporting, however, with this new implementation with the python module that handles the DNSBL, what's the work around to allow bypassing the DNSBL?

It used to be using tags or views, but those won't apply now that the dnsbl file is in .json format.

[Fright]

@dumbo
not sure about the 'glitch'
HTTPS RR is pretty new. for now dnsbl is applied to A/AAA/CNAME records

[tuto2]

Hi,

is this only a "design" glitch, or why does it block the A records but not the HTTPS records?

metrics.icloud.com A record blocked
metrics.icloud.com HTTPS record NOT blocked

https://forum.opnsense.org/index.php?topic=32127.msg155508#msg155508

[tuto2]

Like the others I love the new reporting, however, with this new implementation with the python module that handles the DNSBL, what's the work around to allow bypassing the DNSBL?

It used to be using tags or views, but those won't apply now that the dnsbl file is in .json format.

If you're referring to single domains, you can use the "whitelist domains" field.

If you're referring to networks, not really possible.

[Fright]

@tuto2
im afraid https rr could provide ip via hints ..
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-01#section-6.4

[tuto2]

@tuto2
im afraid https rr could provide ip via hints ..
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-https-01#section-6.4

Ok, if we're going to add HTTPS as a record type to block, would you mind helping by testing this locally? I'll put up a patch tomorrow.

[Fright]

@tuto2
sure )

[tuto2]

@tuto2
sure )

@Fright Can you test with

Code: [Select]

# opnsense-patch e0469001a?

[dumbo]

@Fright Can you test with

Code: [Select]

# opnsense-patch e0469001a?

Is this the patch with also blocking HTTPS requests?