From: Grant Haywood <mrgranthaywood@gmail.com>
To: Allen Walker <eawalker@protonmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Using OPENVPN Client (UDP port 1194) on top of wireguard - packets corrupt
Date: Wed, 23 Jan 2019 22:14:18 -0700 [thread overview]
Message-ID: <CAPayrd5bfuDmL+FvVxzONyKBB4UU-h0zzCOpMgdrG=+VVJA26g@mail.gmail.com> (raw)
In-Reply-To: <c_FUpjUVAFaFWrfz97DeqRpOcM3uLdpa3ylizfNa3ceIzcB5qpDmKvKXb4VD7jfPsTUt17ji91aVxBqHXDdu0IBC4Y1xCZZXMPCyrj6GneM=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]
I do this all the time, not with windows and not on a router, but openvpn
over wg has never really been a problem for me
On Wed, Jan 23, 2019 at 9:01 PM Allen Walker <eawalker@protonmail.com>
wrote:
> My router is set to route everything thru my wireguard vpn. My windows
> machine (a lan client) can run openvpn client but there are issues as
> when I copy large files, specifically mp4s via scp or ftp, the files are
> inevitably corrupted. My guess is that the clients OPENVPN UDP packets
> are getting invariably corrupted when going thru the router and
> wireguard (my router routes are configured via wg-quick). Any ideas on
> how to prevent such packet corruption from the clients openvpn connection?
>
> Thanks
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 1383 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-01-24 5:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 21:38 Allen Walker
2019-01-24 5:14 ` Grant Haywood [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='CAPayrd5bfuDmL+FvVxzONyKBB4UU-h0zzCOpMgdrG=+VVJA26g@mail.gmail.com' \
--to=mrgranthaywood@gmail.com \
--cc=eawalker@protonmail.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).