subject:"Cannot ping peer 1 from peer 2"

Re: Cannot ping peer 1 from peer 2

2018-04-13 Thread Jason A. Donenfeld

You may need to run as root:

sysctl net.ipv4.ip_forward=1

You also may want a -o wg0 rule on the FORWARD table, if you don't
also have an established/related rule there.
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: Cannot ping peer 1 from peer 2

2018-03-15 Thread Vikas

Thank you.

On peer 2 making Address = 10.100.1.2/24 allows peer2 to ping peer1.

But peer2 is not able to use peer1 as a router.

>From peer 2 when I do a traceroute the packets are not being forwarded by 
>peer1:

root@ubuntu:/gt/runenv/config/wireguard/client# traceroute 4.4.4.4
traceroute to 4.4.4.4 (4.4.4.4), 30 hops max, 60 byte packets
 1  10.100.1.1 (10.100.1.1)  4.206 ms  4.197 ms  4.189 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *

To make sure there is no confusion.

Here are the current settings I am using: https://thepasteb.in/p/y8hzcR2w7xDM0S2

What am I doing wrong?



--
VK


On Thu, Mar 15, 2018 at 7:07 PM, Vikas  wrote:
> Here is the config on peer 1 (Vmware VM running ubuntu 16.04):
> =
>
> vk@ubuntu /g/r/c/w/server> ifconfig ens33
> ens33 Link encap:Ethernet  HWaddr 00:0c:29:c8:6c:d5
>   inet addr:10.0.1.77  Bcast:10.0.1.255  Mask:255.255.255.0
>   inet6 addr: fe80::5b06:24b6:c9e4:954e/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:327949 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:87146 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:351155285 (351.1 MB)  TX bytes:12179516 (12.1 MB)
>
>
> vk@ubuntu /g/r/c/w/server> more etc-wireguard-wg0.conf
> [Interface]
> Address = 10.100.1.1/24
> ListenPort = 51820
> PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A
> POSTROUTING -o ens33 -j MASQUERADE
> PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D
> POSTROUTING -o ens33 -j MASQUERADE
> PrivateKey = CPQLRq40QGY3+8yn2LlYb1x3zU/3/Ki+A4QjVYgbakY=
> SaveConfig = true
>
> [Peer]
> PublicKey = uL8bs5596DJO7BMnrIVG5btvr4LTzlbx1ovwHe59NBc=
> AllowedIPs = 10.100.1.2/32
>
>
> vk@ubuntu /g/r/c/w/server> ifconfig wg0
> wg0   Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>   inet addr:10.100.1.1  P-t-P:10.100.1.1  Mask:255.255.255.0
>   UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:459 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
>
> Here is the config on peer 2  (Vmware VM running ubuntu 18.04):
> ==
>
> root@ubuntu /g/r/c/w/client# ifconfig ens33
> ens33: flags=4163  mtu 1500
> inet 10.0.1.71  netmask 255.255.255.0  broadcast 10.0.1.255
> inet6 fe80::c4d7:35d6:306b:fc91  prefixlen 64  scopeid 0x20
> ether 00:0c:29:b6:bb:18  txqueuelen 1000  (Ethernet)
> RX packets 532611  bytes 765847699 (765.8 MB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 71767  bytes 5458394 (5.4 MB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> root@ubuntu /g/r/c/w/client# more etc-wireguard-wg0.conf
> [Interface]
> Address = 10.100.1.2
> PrivateKey = AMZXJ1vBx6OOnZlbnYHuShTBAPuOzwCgweG73BS/4WY=
>
> [Peer]
> PublicKey = KNuvytvYu9NktxybaOHsCF11q96IGfc+dT/Dv8L6KB0=
> AllowedIPs = 0.0.0.0/0
> Endpoint = 10.0.1.77:51280
>
>
> root@ubuntu /g/r/c/w/client# ifconfig wg0
> wg0: flags=209  mtu 1420
> inet 10.100.1.2  netmask 255.255.255.255  destination 10.100.1.2
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> txqueuelen 1000  (UNSPEC)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 10  bytes 1480 (1.4 KB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> root@ubuntu /g/r/c/w/client# ping 10.0.1.77
> PING 10.0.1.77 (10.0.1.77) 56(84) bytes of data.
> 64 bytes from 10.0.1.77: icmp_seq=1 ttl=64 time=0.464 ms
> 64 bytes from 10.0.1.77: icmp_seq=2 ttl=64 time=0.715 ms
>
>
> root@ubuntu /g/r/c/w/client# ping 10.100.1.1
> PING 10.100.1.1 (10.100.1.1) 56(84) bytes of data.
> ^C
> --- 10.100.1.1 ping statistics ---
> 3 packets transmitted, 0 received, 100% packet loss, time 2033ms
>
>
> What am I doing wrong?
>
> --
> VK
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: Cannot ping peer 1 from peer 2

2018-03-15 Thread Tim Sedlmeyer

The ip address for the wg0 interface on peer 2 is set to 10.100.1.2/32
so peer2 has no route to reach 10.100.1.1. You either need to set a
route to 10.100.1.1 on peer 2 or change the address on peer 2 so the
subnet it is in includes 10.100.1.1. For example 10.100.1.2/24.

On Thu, Mar 15, 2018 at 10:07 PM, Vikas  wrote:
> Here is the config on peer 1 (Vmware VM running ubuntu 16.04):
> =
>
> vk@ubuntu /g/r/c/w/server> ifconfig ens33
> ens33 Link encap:Ethernet  HWaddr 00:0c:29:c8:6c:d5
>   inet addr:10.0.1.77  Bcast:10.0.1.255  Mask:255.255.255.0
>   inet6 addr: fe80::5b06:24b6:c9e4:954e/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:327949 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:87146 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:351155285 (351.1 MB)  TX bytes:12179516 (12.1 MB)
>
>
> vk@ubuntu /g/r/c/w/server> more etc-wireguard-wg0.conf
> [Interface]
> Address = 10.100.1.1/24
> ListenPort = 51820
> PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A
> POSTROUTING -o ens33 -j MASQUERADE
> PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D
> POSTROUTING -o ens33 -j MASQUERADE
> PrivateKey = CPQLRq40QGY3+8yn2LlYb1x3zU/3/Ki+A4QjVYgbakY=
> SaveConfig = true
>
> [Peer]
> PublicKey = uL8bs5596DJO7BMnrIVG5btvr4LTzlbx1ovwHe59NBc=
> AllowedIPs = 10.100.1.2/32
>
>
> vk@ubuntu /g/r/c/w/server> ifconfig wg0
> wg0   Link encap:UNSPEC  HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>   inet addr:10.100.1.1  P-t-P:10.100.1.1  Mask:255.255.255.0
>   UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:459 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
>
> Here is the config on peer 2  (Vmware VM running ubuntu 18.04):
> ==
>
> root@ubuntu /g/r/c/w/client# ifconfig ens33
> ens33: flags=4163  mtu 1500
> inet 10.0.1.71  netmask 255.255.255.0  broadcast 10.0.1.255
> inet6 fe80::c4d7:35d6:306b:fc91  prefixlen 64  scopeid 0x20
> ether 00:0c:29:b6:bb:18  txqueuelen 1000  (Ethernet)
> RX packets 532611  bytes 765847699 (765.8 MB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 71767  bytes 5458394 (5.4 MB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> root@ubuntu /g/r/c/w/client# more etc-wireguard-wg0.conf
> [Interface]
> Address = 10.100.1.2
> PrivateKey = AMZXJ1vBx6OOnZlbnYHuShTBAPuOzwCgweG73BS/4WY=
>
> [Peer]
> PublicKey = KNuvytvYu9NktxybaOHsCF11q96IGfc+dT/Dv8L6KB0=
> AllowedIPs = 0.0.0.0/0
> Endpoint = 10.0.1.77:51280
>
>
> root@ubuntu /g/r/c/w/client# ifconfig wg0
> wg0: flags=209  mtu 1420
> inet 10.100.1.2  netmask 255.255.255.255  destination 10.100.1.2
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> txqueuelen 1000  (UNSPEC)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 10  bytes 1480 (1.4 KB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
>
> root@ubuntu /g/r/c/w/client# ping 10.0.1.77
> PING 10.0.1.77 (10.0.1.77) 56(84) bytes of data.
> 64 bytes from 10.0.1.77: icmp_seq=1 ttl=64 time=0.464 ms
> 64 bytes from 10.0.1.77: icmp_seq=2 ttl=64 time=0.715 ms
>
>
> root@ubuntu /g/r/c/w/client# ping 10.100.1.1
> PING 10.100.1.1 (10.100.1.1) 56(84) bytes of data.
> ^C
> --- 10.100.1.1 ping statistics ---
> 3 packets transmitted, 0 received, 100% packet loss, time 2033ms
>
>
> What am I doing wrong?
>
> --
> VK
> ___
> 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

Cannot ping peer 1 from peer 2

2018-03-15 Thread Vikas

Here is the config on peer 1 (Vmware VM running ubuntu 16.04):
=

vk@ubuntu /g/r/c/w/server> ifconfig ens33
ens33 Link encap:Ethernet  HWaddr 00:0c:29:c8:6c:d5
  inet addr:10.0.1.77  Bcast:10.0.1.255  Mask:255.255.255.0
  inet6 addr: fe80::5b06:24b6:c9e4:954e/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:327949 errors:0 dropped:0 overruns:0 frame:0
  TX packets:87146 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:351155285 (351.1 MB)  TX bytes:12179516 (12.1 MB)


vk@ubuntu /g/r/c/w/server> more etc-wireguard-wg0.conf
[Interface]
Address = 10.100.1.1/24
ListenPort = 51820
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A
POSTROUTING -o ens33 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D
POSTROUTING -o ens33 -j MASQUERADE
PrivateKey = CPQLRq40QGY3+8yn2LlYb1x3zU/3/Ki+A4QjVYgbakY=
SaveConfig = true

[Peer]
PublicKey = uL8bs5596DJO7BMnrIVG5btvr4LTzlbx1ovwHe59NBc=
AllowedIPs = 10.100.1.2/32


vk@ubuntu /g/r/c/w/server> ifconfig wg0
wg0   Link encap:UNSPEC  HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
  inet addr:10.100.1.1  P-t-P:10.100.1.1  Mask:255.255.255.0
  UP POINTOPOINT RUNNING NOARP  MTU:1420  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:459 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



Here is the config on peer 2  (Vmware VM running ubuntu 18.04):
==

root@ubuntu /g/r/c/w/client# ifconfig ens33
ens33: flags=4163  mtu 1500
inet 10.0.1.71  netmask 255.255.255.0  broadcast 10.0.1.255
inet6 fe80::c4d7:35d6:306b:fc91  prefixlen 64  scopeid 0x20
ether 00:0c:29:b6:bb:18  txqueuelen 1000  (Ethernet)
RX packets 532611  bytes 765847699 (765.8 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 71767  bytes 5458394 (5.4 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


root@ubuntu /g/r/c/w/client# more etc-wireguard-wg0.conf
[Interface]
Address = 10.100.1.2
PrivateKey = AMZXJ1vBx6OOnZlbnYHuShTBAPuOzwCgweG73BS/4WY=

[Peer]
PublicKey = KNuvytvYu9NktxybaOHsCF11q96IGfc+dT/Dv8L6KB0=
AllowedIPs = 0.0.0.0/0
Endpoint = 10.0.1.77:51280


root@ubuntu /g/r/c/w/client# ifconfig wg0
wg0: flags=209  mtu 1420
inet 10.100.1.2  netmask 255.255.255.255  destination 10.100.1.2
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
txqueuelen 1000  (UNSPEC)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 10  bytes 1480 (1.4 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


root@ubuntu /g/r/c/w/client# ping 10.0.1.77
PING 10.0.1.77 (10.0.1.77) 56(84) bytes of data.
64 bytes from 10.0.1.77: icmp_seq=1 ttl=64 time=0.464 ms
64 bytes from 10.0.1.77: icmp_seq=2 ttl=64 time=0.715 ms


root@ubuntu /g/r/c/w/client# ping 10.100.1.1
PING 10.100.1.1 (10.100.1.1) 56(84) bytes of data.
^C
--- 10.100.1.1 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2033ms


What am I doing wrong?

--
VK
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: Cannot ping peer 1 from peer 2

Re: Cannot ping peer 1 from peer 2

Re: Cannot ping peer 1 from peer 2

Cannot ping peer 1 from peer 2

4 matches

Site Navigation

Mail list logo

Footer information