From: Sahil Gupta <sg5414@rit.edu>
To: 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 17:45:43 -0400 [thread overview]
Message-ID: <CAA8CD9s67yT1esUYwyo5rmsZAKahoXn86AAX8faccgvTcA8_xw@mail.gmail.com> (raw)
In-Reply-To: <CAA8CD9vTW5XJVDjhE=5t6e8midm6LivLYqLHBrT98riTYnP3kQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 303 bytes --]
One more observation here.
In your demo video, listening port number is same.
In my case they are different and so I am using wlp1s0 interface IP as
endpoint IP and its wg listening port number in wg set peer command as
endpoint value.
Please rectify me in case I am doing some mistake here.
[-- Attachment #2: Type: text/html, Size: 369 bytes --]
next prev parent reply other threads:[~2017-07-21 21:26 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 [this message]
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
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=CAA8CD9s67yT1esUYwyo5rmsZAKahoXn86AAX8faccgvTcA8_xw@mail.gmail.com \
--to=sg5414@rit.edu \
--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).