Endpoint default route (Windows)

Endpoint default route (Windows)

[Kevin Chadwick]

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

Re: Endpoint default route (Windows)

[Kevin Chadwick]

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