Messages

1

23.1 Legacy Series / Re: After upgrade speeds less then halved

« on: May 06, 2023, 01:31:15 pm »

Hi there,

Check out this link and read the section about opnsense-revert:

https://docs.opnsense.org/manual/opnsense_tools.html

Cheers!

2

23.1 Legacy Series / Re: DNS issues since 23.1.6

« on: May 01, 2023, 05:35:01 pm »

Below I posted an issue that I ran into today, but it just disappeared as mysteriously as it occurred. I have no idea what to make of this, as I did absolutely nothing that could have triggered the problem or its solution. I'm just glad it's solved for now.

I'll leave my post here anyway just in case it happens again or sb else experiences something similar.

======
My original post:

I'm puzzled ... everything has been working well on 23.1.6 and I haven't touched anything in the settings (OPNSense or AdGuard) since over a week, but some time last night AdGuardHome all of a sudden stopped processing DNS requests.

AdGuard runs on port 53, Unbound on port 5353

AdGuard's query log is empty, and indeed nothing gets blocked.
DNS requests do get resolved, except for my internal network addresses.
When I redirect all DNS queries directly to 127.0.0.1:5353, then the internal addresses are getting resolved by Unbound, but obviously this bypasses AdGuard altogether.
When I redirect everything to port 127.0.0.1:53, then AdGuard resolves the requests but my devices don't have internet connection.

I then re-installed AdGuard as well as the AdGuard plugin (didn't use it before), checked the box that AdGuard runs on port 53, but the behaviour I described above hasn't changed.

3

23.1 Legacy Series / Re: DNS issues since 23.1.6

« on: April 22, 2023, 02:24:10 pm »

As the DNS issue seems to manifest in different ways, I figured I post my settings here — it’s really nothing unusual, but maybe this helps in some cases.

Unbound listening port is set to 5353,
AdGuard listens to port 53 and upstream DNS server in AdGuard is set as 127.0.0.1:5353
DNS port forwarding rule: Protocol TCP/UDP, destination LAN net:5353, redirect to 127.0.0.1:5353

As I wrote in a previous post, I also had the DNS issue after updating to 23.1.6, but in my case the port forwarding rule was broken. Once I realized it and entered the exact settings that I had before the update, everything worked fine.

By the way, restoring a saved configuration and reverting back to 23.1.5 both didn’t help, which was odd. I really had to enter the old settings manually to make it work.

4

23.1 Legacy Series / Re: No internet access since 23.1.6 - caused by adguard

« on: April 21, 2023, 08:38:36 am »

Hi all, in my case Adguard Home works fine.

Right after updating to 23.1.6. all my devices lost internet access. Reverting to 23.1.5 didn’t solve the problem.

I investigated the issue and found that for whatever reason my DNS port forwarding rules had been changed. I changed them back to what they were before, updated back to 23.1.6 and that seemed to fix it.