Skip to content
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

Open
4 tasks done
Morku opened this issue Oct 7, 2024 · 7 comments
Open
4 tasks done

Exclude Wi-Fi SSID from the DNS filtering not work #5252

Morku opened this issue Oct 7, 2024 · 7 comments

Comments

@Morku
Copy link

Morku commented Oct 7, 2024

Please answer the following questions for yourself before submitting an issue

  • Filters were updated before reproducing an issue
  • I checked the knowledge base and found no answer
  • I checked to make sure that this issue has not already been filed

AdGuard version

7.19.0 nightly 11 (4845)

Browser version

Firefox

OS version

Windows 11, 24H2 Build 1742

Traffic filtering

  • yes, I do

Which DNS server do you use?

AdGuard DNS Non-filtering

DNS protocol

DNS-over-HTTPS

Issue Details

Steps to reproduce:

  1. I clean installed Windows 11, 24H2
  2. Clean installed AdGuard 7.19.0 nightly 11 (no upgrade, first install)
  3. Entered SSID name of WiFi in SSID exclude list
  4. Clicked Save and Rebooted to take changes affect
  5. Opened filtering log and notice that DNS is protocolled and filtered anyway

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

wlan ssid

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).

@KolbasovAnton
Copy link

@Morku Greetings! Can You, please, try the latest nightly version - your problem is still actual on it? If it is, perform further actions:

  1. Collect the debug log as it's explained here.
  2. Remember the exact time when the issue was reproduced.
  3. Send the archive to [email protected]:
    - include [windows] keyword and 5252 in the subject of your email
    - specify the exact time when the issue occurred.

Also, try to save the settings from correctly working app and import them into other.

@Morku
Copy link
Author

Morku commented Oct 16, 2024

Hi @KolbasovAnton

yes, the issue is the same with version nightly 13 (4847). I sent you the Logfile as requested.

@KolbasovAnton
Copy link

@Morku One more moment - the other device, where bug doesn't occur, has the same Wi-Fi connection?

@Morku
Copy link
Author

Morku commented Oct 16, 2024

@KolbasovAnton

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
1st Intel-i generation (mobile CPU) with Windows 11 24H2 Build 26100.2033 -> SSID exlusion not work (have sent the logfile)

@KolbasovAnton
Copy link

@Morku Try to put the Wi-fi's name in quotation marks (' ' or " ") while adding it to SSID exclusions.

@Morku
Copy link
Author

Morku commented Oct 17, 2024

@KolbasovAnton
I tried 'Besucht uns, aber bringt Kuchen!' and "Besucht uns, aber bringt Kuchen!", saved and rebooted in between.
The issue remain.

@Morku
Copy link
Author

Morku commented Nov 2, 2024

Today I have setup my other WiFi device (11th Intel-i generation) with a clean install Windows 11 24H2 Build 26100.2033.

Now this device is affected, too and SSID exclusion is ignored. I see DNS request in filtering log, but SSID exclusion is setup.

The lowest common denominator is now Windows 11 24H2. Something have changed from Windows 11 22H2 to 24H2. Please check with the new feature release of Windows 11.

I hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants