From: Martin <martinmoen@gmail.com>
To: planung@dreamofjapan.de
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: ArchLinux wireguard install
Date: Thu, 30 Jan 2020 07:03:03 +0000 [thread overview]
Message-ID: <CAKiCHuOpy7m9yUwUiE1QBPEDtoM6O_R5grgD9JgLVd-qP3fRHQ@mail.gmail.com> (raw)
In-Reply-To: <6cd7ccf2c193ee3bd1db3d5870f6982084d0d0d6.camel@dreamofjapan.de>
[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]
Take a look at the mullvad program for arch in the AUR.
But I'd also ask in the Networking section on the archlinux forums
regarding the upgrade path for the module and kernel.
https://bbs.archlinux.org/viewforum.php?id=8
On Thu, Jan 30, 2020 at 2:09 AM Frank Tornack <planung@dreamofjapan.de>
wrote:
> hello all,
>
> I apologize in advance for the stupid question, but I am very unsure.
> I received a voucher for a VPN service at a trade fair and would like
> to test it. The service Mullvad VPN uses the technology WireGuard. And
> I use ArchLinux.
>
> My question was created by the ArchLinux Wiki. There it already refers
> to the kernel 5.6, which should support this function without a module.
> Now my question is, is it better to wait for this kernel or just
> install the module? Would it be a problem if I forgot to delete the
> module again? I am using the Network Manager, what do I need to be
> aware of?
>
> Many thanks in advance and thank you for developing this tool.
>
>
> --
> Mit freundlichen Grüßen
> Frank Tornack
>
>
> -----------------------------
> Why don't you pair `em up in threes? -Yogi Berra
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
[-- Attachment #1.2: Type: text/html, Size: 1931 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-30 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 10:13 Frank Tornack
2020-01-30 2:23 ` Dr. Benjamin Flesch
2020-01-30 9:05 ` Jason A. Donenfeld
2020-01-30 7:03 ` Martin [this message]
2020-01-30 7:40 ` Frank Tornack
2020-01-30 7:56 ` Martin
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=CAKiCHuOpy7m9yUwUiE1QBPEDtoM6O_R5grgD9JgLVd-qP3fRHQ@mail.gmail.com \
--to=martinmoen@gmail.com \
--cc=planung@dreamofjapan.de \
--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).