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

Hey Dan, I just submitted a pull request to bump the package and add this conditional: https://github.com/openwrt/packages/pull/3664 Jason ___ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard

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

On Wed, Dec 14, 2016 at 8:48 PM, Dan Lüdtke wrote: > >> Not sure why the dependency is >> hard coded like this; it shouldn't be. > > Even if it wasn't hardcoded, it would be introduced by +kmod-udptunnel6 > anyway. > > Remove both manually if you really need to throw away IP and

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

> Not sure why the dependency is > hard coded like this; it shouldn't be. Even if it wasn't hardcoded, it would be introduced by +kmod-udptunnel6 anyway. Remove both manually if you really need to throw away IP and want to compile legacyIP only. It should work with both, @IP6 and

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

Hi, Is possible to add/modify version to support IPv4 only ? I would like to disable IPv6 and compile LEDE but than wireguard disappear. It is because of flash size 4MB. Thanks, Michal ___ WireGuard mailing list WireGuard@lists.zx2c4.com

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

Live on wireguard.io/install/ now: > commit 6bd5f8cde97456e37415eab80c19d9e8241f7639 > Author: Jason A. Donenfeld > Date: Wed Nov 16 18:44:17 2016 +0100 > > Add openwrt docs > > diff --git a/docs/install.md b/docs/install.md > index 0946182..98579e9 100644 > ---

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

> The config value has to be the same to correlate them. In that case, > you should show an example with multiple peers, so that it's clear > what's happening. It says "Peer configurations are managed via one or more wireguard_ sections." to introduce the example. However, won't hurt to add

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

> On 16 Nov 2016, at 17:56, Jason A. Donenfeld wrote: > > config wireguard_foo > > --> > > config wireguard_peer1 Unfortunately, not. All peers for iface 'foo' will be named wireguard_foo. UCI sections are iterable if they have the same name. wireguard_peer1 could belong

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

Oh, I see, that's not actually a correct suggestion. The config value has to be the same to correlate them. In that case, you should show an example with multiple peers, so that it's clear what's happening. ___ WireGuard mailing list

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

config wireguard_foo --> config wireguard_peer1 ___ WireGuard mailing list WireGuard@lists.zx2c4.com http://lists.zx2c4.com/mailman/listinfo/wireguard

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

> If somebody has time, it would be good to include one or two examples at > the end of the page (otherwise I'll do it at some point). This one OK? https://wiki.lede-project.org/docs/user-guide/tunneling_interface_protocols#static_addressing_of_a_gre_tunnel

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

On Wed, Nov 16, 2016 at 5:15 PM, Baptiste Jonglez wrote: > On Tue, Nov 15, 2016 at 05:01:14PM +0100, Dan Lüdtke wrote: >> thanks for the various feedback, guys! Here is the next round: >> >> https://github.com/openwrt/packages/pull/3514 > > This one is now merged,

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

Hi, thanks for the various feedback, guys! Here is the next round: https://github.com/openwrt/packages/pull/3514 and https://github.com/openwrt/luci/pull/852 Cheers, Dan > On 13 Nov 2016, at 23:52, Dan Lüdtke wrote: > > Hi again, > > here is the pull request for LuCi: >

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

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