Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Kevin Chadwick <m8il1ists@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Endpoint default route (Windows)
Date: Thu, 27 Feb 2020 18:12:56 +0000	[thread overview]
Message-ID: <96de0e37-fba0-9187-9bd2-47e5fa469edf@gmail.com> (raw)

I assume this is by design for portability, however it had me scratching my head
as to why there was no UDP traffic being sent to the servers IP (endpoint in
client config).

I ended up with two default routes by accident on Windows, so perhaps something
screwed up there but it appears that without a default route, wireguard will not
even attempt communication with the endpoint IP, even if you untick the kill
switch and can ping. Is that correct/intended?

I have it working now BTW.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2020-02-29 11:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 18:12 Kevin Chadwick [this message]
2020-02-28 11:46 ` Kevin Chadwick

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=96de0e37-fba0-9187-9bd2-47e5fa469edf@gmail.com \
    --to=m8il1ists@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).