From: Dave Mifsud <dave.mifsud@um.edu.mt>
To: wireguard@lists.zx2c4.com
Subject: Wireguard Windows keeps using lower priority interface (wifi) when a higher priority interface (wired) becomes available
Date: Thu, 19 Oct 2023 09:43:46 +0200 [thread overview]
Message-ID: <CALv0RtmmZyMUGeBjuU+hvDven23Ad6XYWqfL--h+m-sHt-+ZPg@mail.gmail.com> (raw)
We are implementing Wireguard as a VPN solution for our network on
Windows 10/11 clients. One issue we have encountered is that Wireguard
VPN traffic keeps transiting the wifi interface, even when wired
becomes available.
We have tested the same Windows device without Wireguard, and when the
wired connection becomes available, traffic switches to the wired
connection.
Unfortunately users do not realise this, and at times are located in
an area where wifi connectivity is not optimal.
Has anyone come across this issue? Can anything be done, apart from
creating a trigger in windows such that whenever a wired connection
becomes available Wireguard is restarted? We would like to avoid this,
as the solution seems too drastic.
Dave
next reply other threads:[~2023-11-19 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 7:43 Dave Mifsud [this message]
2023-11-19 14:54 ` Daniel Gröber
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=CALv0RtmmZyMUGeBjuU+hvDven23Ad6XYWqfL--h+m-sHt-+ZPg@mail.gmail.com \
--to=dave.mifsud@um.edu.mt \
--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).