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

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

[Dan Lüdtke]

Hi all,

first step of OpenWRT/LEDE integration is making sure the helper script =
for configuring the interface is installed. The corresponding pull =
request can be found here:
https://github.com/openwrt/packages/pull/3512

Please support this pull request.
Once it is accepted, the GUI (luci) will follow.

Thanks,

Dan=

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

[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 23:35, Dan L=C3=BCdtke <mail@danrl.com> wrote:
>=20
> Hi all,
>=20
> first step of OpenWRT/LEDE integration is making sure the helper =
script for configuring the interface is installed. The corresponding =
pull request can be found here:
> https://github.com/openwrt/packages/pull/3512
>=20
> Please support this pull request.
> Once it is accepted, the GUI (luci) will follow.
>=20
> Thanks,
>=20
> Dan
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/wireguard

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

[Dan Lüdtke]

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=C3=BCdtke <mail@danrl.com> wrote:
>=20
> Hi again,
>=20
> here is the pull request for LuCi:
> https://github.com/openwrt/luci/pull/848
>=20
> Please support this pull request as well.
>=20
> Thanks for all the beta testers and also to Jason and Baptiste for =
their help.
>=20
> It was a great pleasure supporting this project.
>=20
> Cheers,
>=20
> Dan
>=20
>=20
>> On 13 Nov 2016, at 23:35, Dan L=C3=BCdtke <mail@danrl.com> wrote:
>>=20
>> Hi all,
>>=20
>> first step of OpenWRT/LEDE integration is making sure the helper =
script for configuring the interface is installed. The corresponding =
pull request can be found here:
>> https://github.com/openwrt/packages/pull/3512
>>=20
>> Please support this pull request.
>> Once it is accepted, the GUI (luci) will follow.
>>=20
>> Thanks,
>>=20
>> Dan
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> http://lists.zx2c4.com/mailman/listinfo/wireguard
>=20
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/wireguard

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

[Baptiste Jonglez]

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]

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, thanks for the work Dan!

I have documented the various options here:

  https://wiki.lede-project.org/docs/user-guide/tunneling_interface_protocols#protocol_wireguard_wireguard_vpn

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

Baptiste

> > On 13 Nov 2016, at 23:52, Dan Lüdtke <mail@danrl.com> wrote:
> > 
> > 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 23:35, Dan Lüdtke <mail@danrl.com> wrote:
> >> 
> >> Hi all,
> >> 
> >> first step of OpenWRT/LEDE integration is making sure the helper script for configuring the interface is installed. The corresponding pull request can be found here:
> >> https://github.com/openwrt/packages/pull/3512
> >> 
> >> Please support this pull request.
> >> Once it is accepted, the GUI (luci) will follow.
> >> 
> >> Thanks,
> >> 
> >> Dan
> >> _______________________________________________
> >> WireGuard mailing list
> >> WireGuard@lists.zx2c4.com
> >> http://lists.zx2c4.com/mailman/listinfo/wireguard
> > 
> > _______________________________________________
> > WireGuard mailing list
> > WireGuard@lists.zx2c4.com
> > http://lists.zx2c4.com/mailman/listinfo/wireguard
> 
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> http://lists.zx2c4.com/mailman/listinfo/wireguard

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

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

[Kalin KOZHUHAROV]

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

Hmm, something is iffy... I updated my buildroot (./scripts/feeds
update -a) and got the new versions, but it fails to build...

Here is the relevant log (from `make -j1 V=3Ds`) :
...
make[3]: Leaving directory '/srv/OpenWRT/openwrt/package/libs/libmnl'
make[3]: Entering directory
'/srv/OpenWRT/openwrt/package/network/utils/resolveip'
rm -rf /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-a=
r71xx/tmp-resolveip
mkdir -p /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root=
-ar71xx/stamp
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/t=
mp-resolveip
install -d -m0755
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/t=
mp-resolveip/usr/bin
install -m0755 /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/=
resolveip/resolveip
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/t=
mp-resolveip/usr/bin/
SHELL=3D flock /srv/OpenWRT/openwrt/tmp/.root-copy.flock -c 'cp -fpR
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/t=
mp-resolveip/.
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/'
rm -rf /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-a=
r71xx/tmp-resolveip
touch /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar=
71xx/stamp/.resolveip_installed
if [ -f /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkgin=
fo/resolveip.default.install.clean
]; then rm -f /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15=
/pkginfo/resolveip.default.install
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkginfo/resol=
veip.default.install.clean;
fi; echo "resolveip" >>
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkginfo/resol=
veip.default.install
make[3]: Leaving directory
'/srv/OpenWRT/openwrt/package/network/utils/resolveip'
make[3]: Entering directory '/srv/OpenWRT/openwrt/feeds/packages/net/wiregu=
ard'
mkdir -p /srv/OpenWRT/openwrt/bin/ar71xx/packages
/srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-exper=
imental-0.0.20161110/ipkg-ar71xx/wireguard-tools/CONTROL
/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkginfo
install -d -m0755
/srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-exper=
imental-0.0.20161110/ipkg-ar71xx/wireguard-tools/usr/bin/
install -m0755 /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/=
WireGuard-experimental-0.0.20161110/src/tools/wg
/srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-exper=
imental-0.0.20161110/ipkg-ar71xx/wireguard-tools/usr/bin/
install -m0755 ./files/wireguard.sh
/srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-exper=
imental-0.0.20161110/ipkg-ar71xx/wireguard-tools/lib/netifd/proto/
install: target
'/srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-expe=
rimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/lib/netifd/proto/'
is not a directory: No such file or directory
Makefile:106: recipe for target
'/srv/OpenWRT/openwrt/bin/ar71xx/packages/packages/wireguard-tools_0.0.2016=
1110-2_ar71xx.ipk'
failed
make[3]: *** [/srv/OpenWRT/openwrt/bin/ar71xx/packages/packages/wireguard-t=
ools_0.0.20161110-2_ar71xx.ipk]
Error 1
make[3]: Leaving directory '/srv/OpenWRT/openwrt/feeds/packages/net/wiregua=
rd'
package/Makefile:196: recipe for target
'package/feeds/packages/wireguard/compile' failed
make[2]: *** [package/feeds/packages/wireguard/compile] Error 2
make[2]: Leaving directory '/srv/OpenWRT/openwrt'
package/Makefile:193: recipe for target
'/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/stamp/.packa=
ge_compile'
failed
make[1]: *** [/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15=
/stamp/.package_compile]
Error 2
make[1]: Leaving directory '/srv/OpenWRT/openwrt'
/srv/OpenWRT/openwrt/include/toplevel.mk:192: recipe for target 'world' fai=
led
make: *** [world] Error 2

$ ll /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-=
experimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/
total 8
4 drwxr-xr-x 2 kalin users 4096 Nov 16 17:26 CONTROL
4 drwxr-xr-x 3 kalin users 4096 Nov 16 17:26 usr

Hmm, "No such file or directory" ? Somewhere mkdir -p is needed?


It used to work 4 days ago, I successfully built/tested/still running:
kmod-wireguard 4.4.14+0.0.20161105-1
wireguard-tools 0.0.20161105-1

I'll try a clean recompile of everything now...

Kalin.

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

[Dan Luedtke]

Hmm, could it be missing a line like

$(INSTALL_DIR) $(1)/lib/netifd/proto/

In the Makefile? Not sure why we would need to create it, shouldn't it be th=
ere?

Kalin, could you try again with the installdir line?

> On 16 Nov 2016, at 09:48, Kalin KOZHUHAROV <me.kalin@gmail.com> wrote:
>=20
> On Wed, Nov 16, 2016 at 5:15 PM, Baptiste Jonglez
> <baptiste@bitsofnetworks.org> wrote:
>> On Tue, Nov 15, 2016 at 05:01:14PM +0100, Dan L=C3=BCdtke wrote:
>>> thanks for the various feedback, guys! Here is the next round:
>>>=20
>>> https://github.com/openwrt/packages/pull/3514
>>=20
>> This one is now merged, thanks for the work Dan!
>>=20
>=20
> Hmm, something is iffy... I updated my buildroot (./scripts/feeds
> update -a) and got the new versions, but it fails to build...
>=20
> Here is the relevant log (from `make -j1 V=3Ds`) :
> ...
> make[3]: Leaving directory '/srv/OpenWRT/openwrt/package/libs/libmnl'
> make[3]: Entering directory
> '/srv/OpenWRT/openwrt/package/network/utils/resolveip'
> rm -rf /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-=
ar71xx/tmp-resolveip
> mkdir -p /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/roo=
t-ar71xx/stamp
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/=
tmp-resolveip
> install -d -m0755
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/=
tmp-resolveip/usr/bin
> install -m0755 /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15=
/resolveip/resolveip
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/=
tmp-resolveip/usr/bin/
> SHELL=3D flock /srv/OpenWRT/openwrt/tmp/.root-copy.flock -c 'cp -fpR
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/=
tmp-resolveip/.
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-ar71xx/=
'
> rm -rf /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-=
ar71xx/tmp-resolveip
> touch /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/root-a=
r71xx/stamp/.resolveip_installed
> if [ -f /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkgi=
nfo/resolveip.default.install.clean
> ]; then rm -f /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.1=
5/pkginfo/resolveip.default.install
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkginfo/reso=
lveip.default.install.clean;
> fi; echo "resolveip" >>
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkginfo/reso=
lveip.default.install
> make[3]: Leaving directory
> '/srv/OpenWRT/openwrt/package/network/utils/resolveip'
> make[3]: Entering directory '/srv/OpenWRT/openwrt/feeds/packages/net/wireg=
uard'
> mkdir -p /srv/OpenWRT/openwrt/bin/ar71xx/packages
> /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-expe=
rimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/CONTROL
> /srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/pkginfo
> install -d -m0755
> /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-expe=
rimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/usr/bin/
> install -m0755 /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15=
/WireGuard-experimental-0.0.20161110/src/tools/wg
> /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-expe=
rimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/usr/bin/
> install -m0755 ./files/wireguard.sh
> /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-expe=
rimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/lib/netifd/proto/
> install: target
> '/srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard-exp=
erimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/lib/netifd/proto/'
> is not a directory: No such file or directory
> Makefile:106: recipe for target
> '/srv/OpenWRT/openwrt/bin/ar71xx/packages/packages/wireguard-tools_0.0.201=
61110-2_ar71xx.ipk'
> failed
> make[3]: *** [/srv/OpenWRT/openwrt/bin/ar71xx/packages/packages/wireguard-=
tools_0.0.20161110-2_ar71xx.ipk]
> Error 1
> make[3]: Leaving directory '/srv/OpenWRT/openwrt/feeds/packages/net/wiregu=
ard'
> package/Makefile:196: recipe for target
> 'package/feeds/packages/wireguard/compile' failed
> make[2]: *** [package/feeds/packages/wireguard/compile] Error 2
> make[2]: Leaving directory '/srv/OpenWRT/openwrt'
> package/Makefile:193: recipe for target
> '/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.15/stamp/.pack=
age_compile'
> failed
> make[1]: *** [/srv/OpenWRT/openwrt/staging_dir/target-mips_34kc_musl-1.1.1=
5/stamp/.package_compile]
> Error 2
> make[1]: Leaving directory '/srv/OpenWRT/openwrt'
> /srv/OpenWRT/openwrt/include/toplevel.mk:192: recipe for target 'world' fa=
iled
> make: *** [world] Error 2
>=20
> $ ll /srv/OpenWRT/openwrt/build_dir/target-mips_34kc_musl-1.1.15/WireGuard=
-experimental-0.0.20161110/ipkg-ar71xx/wireguard-tools/
> total 8
> 4 drwxr-xr-x 2 kalin users 4096 Nov 16 17:26 CONTROL
> 4 drwxr-xr-x 3 kalin users 4096 Nov 16 17:26 usr
>=20
> Hmm, "No such file or directory" ? Somewhere mkdir -p is needed?
>=20
>=20
> It used to work 4 days ago, I successfully built/tested/still running:
> kmod-wireguard 4.4.14+0.0.20161105-1
> wireguard-tools 0.0.20161105-1
>=20
> I'll try a clean recompile of everything now...
>=20
> Kalin.

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

[Kalin KOZHUHAROV]

On Wed, Nov 16, 2016 at 6:34 PM, Dan Luedtke <mail@danrl.com> wrote:
> Hmm, could it be missing a line like
>
> $(INSTALL_DIR) $(1)/lib/netifd/proto/
>
> In the Makefile? Not sure why we would need to create it, shouldn't it be=
 there?
>
> Kalin, could you try again with the installdir line?
>
Currently the Makefile had this in:

define Package/wireguard-tools/install
    $(INSTALL_DIR) $(1)/usr/bin/
    $(INSTALL_BIN) $(PKG_BUILD_DIR)/src/tools/wg $(1)/usr/bin/
    $(INSTALL_BIN) ./files/wireguard.sh $(1)/lib/netifd/proto/
endef

I patched it:
--- a/srv/OpenWRT/openwrt/feeds/packages/net/wireguard/Makefile
2016-11-16 18:45:57.733060093 +0900
+++ b/srv/OpenWRT/openwrt/feeds/packages/net/wireguard/Makefile
2016-11-16 18:46:07.716948224 +0900
@@ -83,6 +83,7 @@
 define Package/wireguard-tools/install
     $(INSTALL_DIR) $(1)/usr/bin/
     $(INSTALL_BIN) $(PKG_BUILD_DIR)/src/tools/wg $(1)/usr/bin/
+    $(INSTALL_DIR) $(1)/lib/netifd/proto/
     $(INSTALL_BIN) ./files/wireguard.sh $(1)/lib/netifd/proto/
 endef

And it seems to work now. I guess this looks as expected:
./build_dir/target-mips_34kc_musl-1.1.15/WireGuard-experimental-0.0.2016111=
0/ipkg-ar71xx/wireguard-tools/
=E2=94=9C=E2=94=80=E2=94=80 CONTROL
=E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 control
=E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 postinst
=E2=94=82   =E2=94=94=E2=94=80=E2=94=80 prerm
=E2=94=9C=E2=94=80=E2=94=80 lib
=E2=94=82   =E2=94=94=E2=94=80=E2=94=80 netifd
=E2=94=82       =E2=94=94=E2=94=80=E2=94=80 proto
=E2=94=82           =E2=94=94=E2=94=80=E2=94=80 wireguard.sh
=E2=94=94=E2=94=80=E2=94=80 usr
    =E2=94=94=E2=94=80=E2=94=80 bin
        =E2=94=94=E2=94=80=E2=94=80 wg

(still compiling the rest)

Kalin.

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

[Dan Lüdtke]

Hi Kalin,


yes, this looks fine. Thanks for reporting.

I created an issue and submitted a fixing pull request. As soon as it is =
merged the builds should be fine again.

I will set up a new build machine that builds from scratch to avoid =
similar mistakes in the future.

Cheers,

Dan

> On 16 Nov 2016, at 10:50, Kalin KOZHUHAROV <me.kalin@gmail.com> wrote:
>=20
> And it seems to work now. I guess this looks as expected:
> =
./build_dir/target-mips_34kc_musl-1.1.15/WireGuard-experimental-0.0.201611=
10/ipkg-ar71xx/wireguard-tools/
> =E2=94=9C=E2=94=80=E2=94=80 CONTROL
> =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 control
> =E2=94=82   =E2=94=9C=E2=94=80=E2=94=80 postinst
> =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 prerm
> =E2=94=9C=E2=94=80=E2=94=80 lib
> =E2=94=82   =E2=94=94=E2=94=80=E2=94=80 netifd
> =E2=94=82       =E2=94=94=E2=94=80=E2=94=80 proto
> =E2=94=82           =E2=94=94=E2=94=80=E2=94=80 wireguard.sh
> =E2=94=94=E2=94=80=E2=94=80 usr
>    =E2=94=94=E2=94=80=E2=94=80 bin
>        =E2=94=94=E2=94=80=E2=94=80 wg

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

[Dan Lüdtke]

> 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_protocol=
s#static_addressing_of_a_gre_tunnel

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

[Jason A. Donenfeld]

config wireguard_foo

-->

config wireguard_peer1

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

[Jason A. Donenfeld]

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.

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

[Dan Lüdtke]

> 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_<ifname> sections." to introduce the example. However, won't =
hurt to add another peer for clarification.

Consider it done :)

DUMP:

Create a WireGuard tunnel interface named ''foo'' that connects to one =
peer (VPN server at vpn.example.com) and allows another peer (e.g. road =
warrior) to connect.
Peer configurations are managed via one or more ''wireguard_<ifname>'' =
sections.

<code>
config interface 'foo'
	option proto 'wireguard'
	option private_key =
'qLvQnx5CpXPDo6oplzdIvXLNqkbgpXip3Yv4ouHWZ0Q=3D'
	option preshared_key =
'M1IbkkDVwXsQbFbURiMXiVe/iUCjC5TKHCmemVs+oLQ=3D'

config wireguard_foo
	option public_key '9mD+mTiOp7SGIkB4t3ZfWAcfp5iA/WwQRdVypKKwrjY=3D'=

	option route_allowed_ips '1'
	list allowed_ips 'fd00:13:37::/48'
	option endpoint_host 'vpn.example.com'
	option persistent_keepalive '25'

config wireguard_foo
	option public_key '4mLeSytW6/y4UcOT6rNorw1Ae9nXSxhXUjxsdzMWkUA=3D'=

	list allowed_ips 'fd00:13:37:ffff::23'
</code>

To use static addresses on a WireGuard interface, create a static =
address configuration on top of the interface.

<code>
config interface 'bar'
	option proto 'static'
	option ifname 'foo'
	option ip6addr 'fd00:13:37::2/64'
</code>=

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

[Jason A. Donenfeld]

Live on wireguard.io/install/ now:

> commit 6bd5f8cde97456e37415eab80c19d9e8241f7639
> Author: Jason A. Donenfeld <Jason@zx2c4.com>
> 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
> --- a/docs/install.md
> +++ b/docs/install.md
> @@ -46,11 +46,11 @@ As WireGuard nears closer to release time, distribution support will be much wid
>      boot.extraModulePackages = [ cfg.boot.kernelPackages.wireguard ];
>      environment.systemPackages = [ pkgs.wireguard ];
>
> -#### OpenWRT <small>[trunk &ndash; [module &amp; tools](https://github.com/openwrt/packages/blob/master/net/wireguard/Makefile)]</small>
> +#### OpenWRT &amp; LEDE <small>[trunk &ndash; [module &amp; tools](https://github.com/openwrt/packages/blob/master/net/wireguard/Makefile)]</small>
>
>      # opkg install kmod-wireguard wireguard-tools
>
> -Note that the OpenWRT package does not yet enable multi-core crypto, but their developers are working on it.
> +Further installation and configuration instructions may be found on the [wiki](https://wiki.lede-project.org/docs/user-guide/tunneling_interface_protocols).
>
>  #### <i class="fa fa-apple"></i> Mac OS X <small>[homebrew &ndash; [tools](http://braumeister.org/formula/wireguard-tools)]</small>
>

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

[Dan Lüdtke]

> On 16 Nov 2016, at 17:56, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>=20
> config wireguard_foo
>=20
> -->
>=20
> 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 to any wg interface. We would need a =
further option to relate it to the corresponding interface. It would be =
more complicated.=

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

[Michal Kowalski]

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 

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

[Jason A. Donenfeld]

On Mon, Dec 12, 2016 at 1:03 PM, Michal Kowalski <kofec@wp.pl> wrote:
> 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.

Yes. WireGuard supports this already. You just need to remove the v6
deps from the LEDE wireguard makefile. Not sure why the dependency is
hard coded like this; it shouldn't be.

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

[Dan Lüdtke]

> 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 =
kmod-udptunnel6 removed.=20=

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

[Jason A. Donenfeld]

On Wed, Dec 14, 2016 at 8:48 PM, Dan L=C3=BCdtke <mail@danrl.com> 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 a=
nyway.
>
> Remove both manually if you really need to throw away IP and want to comp=
ile legacyIP only. It should work with both, @IP6 and kmod-udptunnel6 remov=
ed.

kmod-udptunnel6 is only required if IPv6 is turned on.

At least in menuconfig, it's easy to describe conditional dependencies
like this one. Can the OpenWRT makefile thinger do it too? Baptiste?

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

[Jason A. Donenfeld]

Hey Dan,

I just submitted a pull request to bump the package and add this
conditional: https://github.com/openwrt/packages/pull/3664

Jason