-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exclude Wi-Fi SSID from the DNS filtering not work #5252
Comments
@Morku Greetings! Can You, please, try the latest nightly version - your problem is still actual on it? If it is, perform further actions:
Also, try to save the settings from correctly working app and import them into other. |
yes, the issue is the same with version nightly 13 (4847). I sent you the Logfile as requested. |
@Morku One more moment - the other device, where bug doesn't occur, has the same Wi-Fi connection? |
Yes, same WiFi connection, same SSID exclude, same homenetwork. I have tested the settings from that working device (also using nightly 13). The issue is the same on my affexted device. There are still DNS requests and my exclusion is ignored. The major difference between both are: 11th Intel-i generation (desktop CPU) with Windows 11 22H2 Build 22621.4317 -> SSID exclusion works fine |
@Morku Try to put the Wi-fi's name in quotation marks (' ' or " ") while adding it to SSID exclusions. |
@KolbasovAnton |
Please answer the following questions for yourself before submitting an issue
AdGuard version
7.19.0 nightly 11 (4845)
Browser version
Firefox
OS version
Windows 11, 24H2 Build 1742
Traffic filtering
Which DNS server do you use?
AdGuard DNS Non-filtering
DNS protocol
DNS-over-HTTPS
Issue Details
Steps to reproduce:
Expected Behavior
The WiFi with the exact same SSID name should not be DNS filtered, like DNS module is disabled.
Actual Behavior
The SSID Exclusion is ignored and DNS module is active.
Screenshots
Screenshot 1
Additional Information
I have another Device, using WiFi that is not affected by the issue. The difference is, that it still use WIndows 11 22H2 and I upgraded to AdGuard 7.19.0 nightly 11 (4845) from AdGuard 7.18.1 (no clean install -> take over the settings).
The text was updated successfully, but these errors were encountered: