Re: Why does 'allowed-ips' affect route selection behavior?

2018-04-16 Thread Tim Sedlmeyer
On Sun, Apr 15, 2018 at 6:26 PM, Jason A. Donenfeld wrote: > Hi Patrick, > > I see some others on the wireguard mailing list have replied to a > ghost email. That is, I don't have the original that they're replying > to. Looking into it a bit further, it appears that reasonable

Re: Why does 'allowed-ips' affect route selection behavior?

2018-04-15 Thread Jason A. Donenfeld
Hi Patrick, > I suppose I was a victim of WireGuard's simplicity. I got it up and > running so quickly that I didn't bother to dig into the individual > components more than necessary at first. I ultimately may end up > foregoing wg-quick, but either way I now understand the mechanics to >

Re: Why does 'allowed-ips' affect route selection behavior?

2018-04-15 Thread Patrick O'Sullivan
Hi Jason, First off--thanks for your work on WireGuard and just wanted to mention that your appearance on FLOSS Weekly put my over the edge to try out WireGuard. > You might want to loosen these up a bit. Anyway, I've pulled it out of the > archives for quoting here: You are probably right. My

Re: Why does 'allowed-ips' affect route selection behavior?

2018-04-15 Thread Jason A. Donenfeld
Hi Patrick, I see some others on the wireguard mailing list have replied to a ghost email. That is, I don't have the original that they're replying to. Looking into it a bit further, it appears that reasonable spam filters -- which includes but is not limited to gmail's -- will have your mail

Re: Why does 'allowed-ips' affect route selection behavior?

2018-04-15 Thread mikma . wg
On 04/15/2018 08:49 PM, Patrick O'Sullivan wrote: $ sudo ip route show default via 10.199.199.1 dev wlan0 10.111.111.0/24 dev wg0 proto kernel scope link src 10.111.111.100 10.199.199.0/24 dev wlan0 proto kernel scope link src 10.199.199.131 By this route table, traffic to e.g. 4.2.2.1 should

Re: Why does 'allowed-ips' affect route selection behavior?

2018-04-15 Thread Roman Mamedov
On Sun, 15 Apr 2018 14:49:23 -0400 "Patrick O'Sullivan" wrote: > $ sudo ip route get 4.2.2.1 > 4.2.2.1 dev wg0 table 51820 src 10.111.111.100 ^^^ > cache > Can someone please explain this behavior? Probably will be easier to do if you show

Why does 'allowed-ips' affect route selection behavior?

2018-04-15 Thread Patrick O'Sullivan
Hi Folks, Getting my feet wet with wireguard and enjoying the simplicity and performance thus far. Nonetheless, I have a question about how the normal route selection process is being affected by what's configured for 'allowed-ips'. I set up a peer and configured 'allowed-ips' for 0.0.0.0/0, as