[WireGuard] Debugging AllowedIps

2016-11-13 Thread John Huttley
Hi Team, I've had success with AllowedIPs = 0.0.0.0/0 but not otherwise. Is there a way of get some debug output on this? Regards, John ___ WireGuard mailing list WireGuard@lists.zx2c4.com http://lists.zx2c4.com/mailman/listinfo/wireguard

[WireGuard] [PATCH v3] ip6_output: ensure flow saddr actually belongs to device

2016-11-13 Thread Jason A. Donenfeld
This puts the IPv6 routing functions in parity with the IPv4 routing functions. Namely, we now check in v6 that if a flowi6 requests an saddr, the returned dst actually corresponds to a net device that has that saddr. This mirrors the v4 logic with __ip_dev_find in __ip_route_output_key_hash. In

Re: [WireGuard] Wireguard in OpenWRT/LEDE: FYI: Pull Request

2016-11-13 Thread Dan Lüdtke
Hi again, here is the pull request for LuCi: https://github.com/openwrt/luci/pull/848 Please support this pull request as well. Thanks for all the beta testers and also to Jason and Baptiste for their help. It was a great pleasure supporting this project. Cheers, Dan > On 13 Nov 2016, at

Re: [WireGuard] [PATCH v2] ip6_output: ensure flow saddr actually belongs to device

2016-11-13 Thread David Ahern
On 11/13/16 12:02 PM, Jason A. Donenfeld wrote: > This puts the IPv6 routing functions in parity with the IPv4 routing > functions. Namely, we now check in v6 that if a flowi6 requests an > saddr, the returned dst actually corresponds to a net device that has > that saddr. This mirrors the v4

[WireGuard] [PATCH v2] ip6_output: ensure flow saddr actually belongs to device

2016-11-13 Thread Jason A. Donenfeld
This puts the IPv6 routing functions in parity with the IPv4 routing functions. Namely, we now check in v6 that if a flowi6 requests an saddr, the returned dst actually corresponds to a net device that has that saddr. This mirrors the v4 logic with __ip_dev_find in __ip_route_output_key_hash. In