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
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
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
