From: Kevin Chadwick <m8il1ists@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Endpoint default route (Windows)
Date: Fri, 28 Feb 2020 11:46:21 +0000 [thread overview]
Message-ID: <7886753e-c3f6-f94c-6ea4-f767f59af5d6@gmail.com> (raw)
In-Reply-To: <96de0e37-fba0-9187-9bd2-47e5fa469edf@gmail.com>
On 2020-02-27 18:12, Kevin Chadwick wrote:
> I have it working now BTW.
Well it isn't any more. Some kind of ARP issue ignoring replies from the server.
Perhaps having no gateway set would work and allow the entry to be written.
Manual entry didn't seem to work.
Now back to investigating using OpenSSH instead for inuse ports via loopback and
FYI, have found that after uninstalling wireguard and creating an extra loopback
adapter in windows that the new KM-Test loopback device is called wireguard
tunnel device. Running a restore in case anything else has been left behind.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent 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
2020-02-28 11:46 ` Kevin Chadwick [this message]
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=7886753e-c3f6-f94c-6ea4-f767f59af5d6@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).