Messages

Honestly man whoever signed off on this needs to be fired. This is utterly ridiculous for this level of names and words and layout being clipped

Man, Linux sucks so bad lmao

Hello there, very frustrated with OPNsense and Unbound at the moment

What *should* be a simple task of editing /var/unbound/unbound.conf and changing the do-ip6: yes line to no, is proving impossible as it keeps being overwritten

First of all, all prior references to setting custom changes in Unbound are described in the past as Services > Unbound > General or Advanced containing some mythical text box area for Custom Options, which would make a whole lot of sense -- but what makes no sense, is that this has been removed for some reason in latest OPNsense, as I cannot find it anywhere

Then, I found topics saying to use /usr/local/etc/unbound.opnsense.d/ which contains other .conf files

So, I created no_ipv6.conf and it contains simply

server:
     do-ip6: no

and then restarted the Unbound via the GUI

Lo and behold, /var/unbound/unbound.conf is STILL showing do-ip6: yes


Any help would be greatly appreciated, as I am wondering if the reason Query Forwarding stops working is related to this.  Someone else said they had the exact same problem and solved it here: https://github.com/opnsense/core/issues/7639#issuecomment-2325683371

Essentially, Unbound and OPNsense have a problem where Query Forwarding simply stops working and it breaks web browsing connectivity with no rhyme or reason at times, also fails to resolve items when dig can do it just fine

Hi there, I followed this guide: https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html and it works great, thanks for that.

But, I have one tunnel out of my 5 established tunnels at ProtonVPN that I want specifically use ProtonVPN's DNS server (Specified as 10.2.0.1 as per their provided wireguard config file) instead of using 192.168.1.2, my home self-hosted AdGuard DNS server, which DHCP defaults to.

It must be more complicated than simply changing /etc/resolv.conf from 192.168.1.2 which was already there, to 10.2.0.1 which I tried.  It doesn't work, nothing resolves.  And furthermore, 10.2.0.1 is not even pingable

So then I figured maybe I have to go into OPNsense, to VPN > WireGuard > Instances > Proton_SE (my tunnel)
toggled, advanced options to uncover the DNS Server: field which was blank by default, and entered 10.2.0.1 into there, and STILL nothing

So what is the story here?

Where do we specify the DNS server for this one tunnel? I'm really hoping it's as simple as filling the value into a field and doesn't require a ton of custom rules.  Why does that DNS Server box even exist otherwise?

Thank you in advance!