Re: CentOS improper mount labeling on SELinux enabled systems

2018-06-16 Thread Jason A. Donenfeld
Hi Silvan, Thanks for the report. I've fixed this here: https://git.zx2c4.com/WireGuard/commit/?id=3a6e441000cdf0aaeb6f48135139c48af7319626 Your distro will have to pick up the changes for merging into their wg-quick(8). I've CC'd Joe and Martin, for them to review this. Regards, Jason

CentOS improper mount labeling on SELinux enabled systems

2018-06-16 Thread Silvan Nagl
Hello, herewith I'm requesting a bug fix in the bash script 'wg-quick'. When 'DNS' is set in the interfaces configuration file 'wg-quick' will mount the modified 'resolv.conf' with improper set SELinux labels which leads to services not being able to access the 'resolv.conf' correctly. In my

wireguard-tools : Depends: libc6 (>= 2.25) but 2.24-11+deb9u3 is to be installed

2018-06-16 Thread justaguy
Hi, Wireguard-tools is currently uninstallable on stretch The following packages have unmet dependencies:  wireguard-tools : Depends: libc6 (>= 2.25) but 2.24-11+deb9u3 is to be installed (added to sources by https://www.wireguard.com/install/ ) https://packages.debian.org/stretch/libc6 ___

Re: OpenWRT dynamic IP watchdog

2018-06-16 Thread Aleksandr V. Piskunov
Yes, I've tried 135 first, but during the real usage there were quite a few false alarm situations with watchdog reconnecting at 136..~140 seconds. So.. changed it to 150 secs, which seems to work OK for my conditions. I can try to send a git patch to contrib/examples/reresolve-dns, if rest is OK.

Re: OpenWRT dynamic IP watchdog

2018-06-16 Thread Jason A. Donenfeld
Hi Aleksandr, Nice script. One question: > [ ${idle_seconds} -lt 150 ] && return 0; Is there a reason why you went with 150? My original reresolve-dns.sh went with 135 (REKEY_AFTER_TIME + KEEPALIVE_TIMEOUT + REKEY_TIMEOUT). Did you find 150 matched network conditions better? Regards, Jason __

OpenWRT dynamic IP watchdog

2018-06-16 Thread Aleksandr V. Piskunov
I'm using OpenWRT routers to connect several networks (most behind NAT) to the main one, with a public but dynamic IP. In order to keep WireGuard connections alive in case of sudden endpoint IP change, some kind of monitoring is required, so I adapted https://github.com/WireGuard/WireGuard/blob/mas

Re: Ubuntu Error when trying to launch wireguard

2018-06-16 Thread Greg KH
On Fri, Jun 15, 2018 at 04:27:09PM -0400, Glen Bojsza wrote: > I am trying to run wireguard server on Bionic ARM processor. > > After following the installation instructions and creating my server config > file I get the following error when I run > > root@odroidxu4:~# wg-quick up wg0 > > Warnin