Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Sahil Gupta <sg5414@rit.edu>
To: Eric Light <eric@ericlight.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Not able to ping the host as per demo of wireguard.
Date: Fri, 21 Jul 2017 20:07:47 -0400	[thread overview]
Message-ID: <CAA8CD9vAD2aqjwQ+tpO_T-X_8PsoXLi8Fs7Q=GwT1X++eO_wRQ@mail.gmail.com> (raw)
In-Reply-To: <1500681823.1017135.1048796128.794D7A24@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]

Thanks Eric.
I will do that.
😊

On Fri, Jul 21, 2017 at 8:03 PM, Eric Light <eric@ericlight.com> wrote:

> Yep you can make them permanent.  Create your config in
> /etc/wireguard/wg0.conf.  Then run 'systemctl enable wg-quick@wg0'
>  (assuming you're running systemd).
>
> wg-quick takes care of interface creation, interface and endpoint IP
> addressing, routing, and peer keys; so you just create that file and then
> use 'wg-quick up wg0'.  :)
>
> I wrote a few blog posts on setting up wg to act as a bridge into a remote
> network; you can probably use a lot of the info from there to get you
> started:   https://www.ericlight.com/wireguard-part-one-installation
>
> E
>
> --------------------------------------------
> Q: Why is this email five sentences or less?
> A: http://five.sentenc.es
>
>
>
> On Sat, 22 Jul 2017, at 11:54, Sahil Gupta wrote:
>
> Sorry, my bad.
> I copy paste configuration of Peer A in both Peer A and B in this email.
> I will follow the advise of Jason.
>
> I switched off both Laptops and now wg interface are gone.
> I need to create them again.
> Can we make these interfaces permanent so they will not go upon switching
> off the laptop?
>
> I will mail again if problem still persists.
> Thanks
> Sahil Gupta
>
>
>

[-- Attachment #2: Type: text/html, Size: 2497 bytes --]

  reply	other threads:[~2017-07-21 23:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 21:20 Sahil Gupta
2017-07-21 21:45 ` Sahil Gupta
2017-07-21 22:22   ` Jason A. Donenfeld
2017-07-21 23:33     ` Eric Light
2017-07-21 23:54       ` Sahil Gupta
2017-07-22  0:03         ` Eric Light
2017-07-22  0:07           ` Sahil Gupta [this message]
2017-07-22  0:28             ` Sahil Gupta
2017-07-22  0:30               ` Jason A. Donenfeld

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='CAA8CD9vAD2aqjwQ+tpO_T-X_8PsoXLi8Fs7Q=GwT1X++eO_wRQ@mail.gmail.com' \
    --to=sg5414@rit.edu \
    --cc=eric@ericlight.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).