Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Eric Light <eric@ericlight.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Not able to ping the host as per demo of wireguard.
Date: Sat, 22 Jul 2017 11:33:58 +1200	[thread overview]
Message-ID: <1500680038.1009000.1048775720.4A6974DA@webmail.messagingengine.com> (raw)
In-Reply-To: <CAHmME9pQR3hmHJjV-wUah2wqYGKqSw+HipuQH6F92hVgD4FBrg@mail.gmail.com>

Hi Sahil,

Both of your wg0 interfaces are set to 10.0.0.1/24, but both of your
AllowedIPs are set to 10.0.0.2/32 -- so neither of them are routing to
the other.  For me, I'd set AllowedIPs to 10.0.0.1/24 on both laptops,
so they can each talk to  10.0.0.x.

Also, your Endpoints are both set to 192.168.2.170, but neither of your
wlp1s0 interfaces are set to this IP address... this means they're each
throwing their wg packets to some unknown third device.

And then there's the Listening Port thing that Jason already
mentioned... If computer A is listening on 12345, computer B must be
talking to 12345 as well.

Hope this helps
E

--------------------------------------------
Q: Why is this email five sentences or less?
A: http://five.sentenc.es

On Sat, 22 Jul 2017, at 10:22, Jason A. Donenfeld wrote:
> You need to set the correct listening port. If you want to use port
> 51820, set it as such:
> 
> $ wg set wg0 listen-port 51820
> 
> Then adjust your endpoint to 'endpoint 1.2.3.4:51820'.
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2017-07-21 23:14 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 [this message]
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=1500680038.1009000.1048775720.4A6974DA@webmail.messagingengine.com \
    --to=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).