From: Sahil Gupta <sg5414@rit.edu>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Not able to ping the host as per demo of wireguard.
Date: Fri, 21 Jul 2017 17:20:01 -0400 [thread overview]
Message-ID: <CAA8CD9vTW5XJVDjhE=5t6e8midm6LivLYqLHBrT98riTYnP3kQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3566 bytes --]
Hi all,
I am trying demo of Wireguard as shown in this link:
https://www.wireguard.com/talks/talk-demo-screencast.mp4
I am having two laptops connected to same wifi.
Operating system is ubuntu.
I have followed exact same steps as shown in demo but unable to ping the
send laptop.
It is not even recognizing the laptop.
Only difference from video is I don't have eth0 interface but wlp6so
wireless interface.
I am sending both ip addr and wg command results of both.
Please guide what is going wrong with ping command.
Laptop 1(Peer A):
"
root@sahilgupta221-900X3B-900X4B:/home/sahilgupta221# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether e8:03:9a:9a:3b:90 brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 88:53:2e:c7:78:f1 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.211/22 brd 192.168.3.255 scope global dynamic wlp1s0
valid_lft 2130sec preferred_lft 2130sec
inet6 fe80::82c0:7df3:3700:b941/64 scope link
valid_lft forever preferred_lft forever
4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state
UNKNOWN group default qlen 1
link/none
inet 10.0.0.1/24 scope global wg0
valid_lft forever preferred_lft forever
root@sahilgupta221-900X3B-900X4B:/home/sahilgupta221# wg
interface: wg0
public key: N5XYKCRQvs7mMd1QQiPuNcAmchvB4u1oc3N+RNjWeSs=
private key: (hidden)
listening port: 40668
peer: XtGALYDx+tE9dHBftR26vUkjZ6bHzRZscaaM++NSGk4=
endpoint: 192.168.2.170:59257
allowed ips: 10.0.0.2/32
transfer: 0 B received, 3.04 KiB sent
root@sahilgupta221-900X3B-900X4B:/home/sahilgupta221#
"
Laptop 2(Peer B):
"
root@sahilgupta221-900X3B-900X4B:/home/sahilgupta221# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether e8:03:9a:9a:3b:90 brd ff:ff:ff:ff:ff:ff
3: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 88:53:2e:c7:78:f1 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.211/22 brd 192.168.3.255 scope global dynamic wlp1s0
valid_lft 2130sec preferred_lft 2130sec
inet6 fe80::82c0:7df3:3700:b941/64 scope link
valid_lft forever preferred_lft forever
4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state
UNKNOWN group default qlen 1
link/none
inet 10.0.0.1/24 scope global wg0
valid_lft forever preferred_lft forever
root@sahilgupta221-900X3B-900X4B:/home/sahilgupta221# wg
interface: wg0
public key: N5XYKCRQvs7mMd1QQiPuNcAmchvB4u1oc3N+RNjWeSs=
private key: (hidden)
listening port: 40668
peer: XtGALYDx+tE9dHBftR26vUkjZ6bHzRZscaaM++NSGk4=
endpoint: 192.168.2.170:59257
allowed ips: 10.0.0.2/32
transfer: 0 B received, 3.04 KiB sent
root@sahilgupta221-900X3B-900X4B:/home/sahilgupta221#
"
Waiting for reply.
Regards
Sahil Gupta
[-- Attachment #2: Type: text/html, Size: 6733 bytes --]
next reply other threads:[~2017-07-21 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 21:20 Sahil Gupta [this message]
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
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='CAA8CD9vTW5XJVDjhE=5t6e8midm6LivLYqLHBrT98riTYnP3kQ@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).