Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Dr. Benjamin Flesch" <bf@deutsche-cyberberatung.de>
Cc: planung@dreamofjapan.de,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: ArchLinux wireguard install
Date: Thu, 30 Jan 2020 10:05:22 +0100	[thread overview]
Message-ID: <CAHmME9r_GVwOMbuWs9Mxi_5EHw0Gns2MM6kyWESxtO0J0kxebg@mail.gmail.com> (raw)
In-Reply-To: <FC906C5B-26A4-4FED-BB79-49E03704298E@deutsche-cyberberatung.de>


[-- Attachment #1.1: Type: text/plain, Size: 2075 bytes --]

On Thu, Jan 30, 2020, 10:02 Dr. Benjamin Flesch <
bf@deutsche-cyberberatung.de> wrote:

> Hi Frank,
>
> I am also running WireGuard on arch. I think there are two relevant
> packages in AUR right now, one of them is wireguard-dams.
>

The relevant packages are in the actual arch linux package repo. You don't
need anything from AUR to use wireguard on arch linux.



> Just install these packages and don’t bother with NetworkManager - use the
> wg-quick command line tool to spin up the vpn. I have configured it
> persistently in /etc/wireguard/ folder.
>
> I think after the fresh kernel we can just deinstall the AUR packages and
> there won’t be any problem.
>
> Best
> Benjamin
>
> Sent from a mobile device.
>
> > On 30. Jan 2020, at 03:03, 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
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>

[-- Attachment #1.2: Type: text/html, Size: 3281 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:[~2020-01-30  9:05 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 [this message]
2020-01-30  7:03 ` Martin
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=CAHmME9r_GVwOMbuWs9Mxi_5EHw0Gns2MM6kyWESxtO0J0kxebg@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=bf@deutsche-cyberberatung.de \
    --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).