From: Joseph Jeffers <monprin@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Ubuntu PPA Package Bug
Date: Mon, 15 Apr 2019 22:09:37 -0400 [thread overview]
Message-ID: <CANL8rF+LbByc14jB-+HGG=TbiRYufCG_Ggw0h9ezvti5ueVFsw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1416 bytes --]
Hello mailing list,
I am building a server utilizing wireguard and network namespaces, and
since the most recent update I seem to have developed an issue where
wireguard on Ubuntu no longer seems to be able to reach the internet
despite following the instructions verbatim. It does however seem to work
on Debian.
To test this I wrote a script that sets up the interface and tests it side
by side with the default network interface. It also tests the network
namespace method as well. It conforms as close as possible to your
instructions. I am using Mullvad as the server to connect to. To get clean
tests, I spun up two clean VMs on Digital Ocean, one Debian and one Ubuntu,
did any available updates, followed the install instruction on the page,
and ran the script. The script and the results are in this Gist:
https://gist.github.com/monprin/c9352f32a6e7e02561a571f27d7ce274
I also tried to test this on Fedora 29 in the same manner, but something
more major went wrong with the install from Copr.
Any guidance on any workarounds for this would be greatly appreciated since
the old build no longer seem to appear in the PPA. I would be happy to help
in any way I can in trying to troubleshoot this, but I wasn't able to dig
into the code as is it is pretty far from my high level python wheelhouse.
Thanks for all your work on Wireguard, I am loving it!
--
*Joseph Ray Jeffers*
Email: monprin@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 1837 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-05-06 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANL8rF+LbByc14jB-+HGG=TbiRYufCG_Ggw0h9ezvti5ueVFsw@mail.gmail.com' \
--to=monprin@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).