Re: Cannot ping peer 1 from peer 2

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

Re: Android app and command line

Hello, On 03/12/18 20:51, Jacob Schooley wrote: > There is an option in the Android app to enable wg and wg-quick, which will be > extremely useful to me as most of my VPN stuff is taken care of with Tasker. > There are two major bugs with this however. Thanks for the report! > One is that the

Re: Cannot ping peer 1 from peer 2

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

Cannot ping peer 1 from peer 2

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

Re: Allowed IPs Toggling

> WireGuard *does* support overlapping ranges of AllowedIPs on different peers. It > doesn't support having *identical* ranges of AllowedIPs on different peers, > which was the situation here. (You're correct, there's no concept of a metric.) Oh good - looks like I just misunderstood your

Re: Allowed IPs Toggling

Hello, On 03/15/18 13:39, Steve Gilberd wrote: >> Allowed IPs is like a routing table; you can't have two routes for the same > set of IPs > > If this is the case, then wireguard does not have proper routing support. > > Normally, routing tables allow both multiple and overlapping routes

Re: Allowed IPs Toggling

> Allowed IPs is like a routing table; you can't have two routes for the same set of IPs If this is the case, then wireguard does not have proper routing support. Normally, routing tables allow both multiple and overlapping routes present. When making routing decisions, the most-specific route

Re: Multiple peers

Hi Gianluca, you may want to read also this example I explained in Ninux mailing list https://www.mail-archive.com/wireless@ml.ninux.org/msg20983.html Best regards ___ WireGuard mailing list WireGuard@lists.zx2c4.com

Re: Lineage OS (Android) Support

Hello, On 03/13/18 06:15, Paul wrote: > On So, Mär 11, 2018 at 7:42 PM, Paul wrote: >> Hi all, >> >> I'm new to the list and hope this wasn't discussed in length here before. If >> so, please give me a direction, I couldn't find anything related. >> >> For the last days I

Re: Allowed IPs Toggling

Hello, On 03/15/18 10:31, Gianluca Gabrielli wrote: > I was setting two peers on the server, but every time I re-add one of these > two the other one is shown with (none) on "allowed ips" field. Of course that > blocks communications with that peer. If I try to re-add it, then the other > peer

Re: Multiple peers

Thanks to both of you guys, really helpful! Especially **Network Namespace** is a great feature that I didn't know before. Cheers, Gianluca ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard