From: Kat Liny <billowtongroup@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Disconnection Bug on Win 11 with Intel adapter
Date: Wed, 23 Aug 2023 00:26:31 +0700 [thread overview]
Message-ID: <CAMFOZ_+iR0J5q5RUKvZ8Gtk3Q3bVcAs=GpB9YWxjCUTs5cN4oQ@mail.gmail.com> (raw)
There appears to be a bug that causes the network adapter "Intel(R)
Wi-Fi 6E AX211 160MHz" on Windows 11 (with all current updates) to
disconnect and re-connect to the WiFi network a few times AFTER
disconnecting a WireGuard client profile. If the WireGuardTunnel
service can be either set to automatic startup or be started later
after Windows loads. The WireGuard connection will remain stable and
connected until the WireGuardTunnel service is stopped, that is when
the connection issues begin, the Internet will be lost for about 20
seconds each time, sometimes more, then reconnects (and usually last
5-15 minutes while the adapter disconnects and reconnects to the
normal network). The issue could be lasting longer than that, I did
not have the patience after each test with reboot.
Have tried:
-Disabling windows firewall and windows defender
-Disable/enable the Intel network adapter quickly after disabling the
WireGuard tunnel service.
-Changing many of the adapter settings.
After each test, I rebooted.
It seems only a reboot solves the issue, and the intermittent
disconnection issue will start again after connecting/disconnecting
the WireGuard profile.
If the WireGuardTunnel service is kept to Disabled status and I never
try to connect to a WireGuard client config during the test, then the
disconnection issue does not happen.
In the Event Viewer logs, it shows this a few times, only during the
issue which seems related:
-----
The description for Event ID 7021 from source Netwtw12 cannot be
found. Either the component that raises this event is not installed on
your local computer or the installation is corrupted. You can install
or repair the component on the local computer.
----
Tested using the WireGuard installer wireguard-amd64-0.5.3.msi. There
are no other security/networking products on the machine that could be
conflicting.
reply other threads:[~2023-08-23 16:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMFOZ_+iR0J5q5RUKvZ8Gtk3Q3bVcAs=GpB9YWxjCUTs5cN4oQ@mail.gmail.com' \
--to=billowtongroup@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).