Dear maintainer,
I tried to set up a wireguard connection on wg0 interface using
NetworkManager for testing purpose and then forgot about that. Let's say
I used 192.168.16.233/32 ip and several routes (ex 10.0.3.0/24 10.0.5.0/24).
Then, using wg-quick, I set up a connection on wg0 with different
Control: retitle 921017 wireguard: wg setconf doesn't always set all allowed-ips
Control: reassign 921017 wireguard-tools
Hi Piotr--
On Mon 2019-09-09 12:40:30 +0200, Piotr Ożarowski wrote:
> yes, I can still replicate it with 0.0.20190905-1 but I do it on stable
> (first Stretch now Buster) with
Hi Daniel,
> I tried to replicate this with exactly the kind of setup you've
> described, but using version 0.0.20190905-1 on amd64 on a
> debian/unstable system. i saw the output was like:
>
> my_public_key=10.8.1.2/32 10.1.0.0/20 10.0.0.0/20 192.168.6.0/24
>
> Can you still replicate
Control: tags 921017 + moreinfo unreproducible
Hi Piotr--
On Thu 2019-01-31 18:15:04 +0100, Piotr Ożarowski wrote:
> I have multiple peers defined in /etc/wireguard/wg0.conf
> but setting AllowedIPs doesn't fully work for some of them
> if I use `wg setconf`… and works perfectly fine if I do this
Package: wireguard
Version: 0.0.20190123-1
Severity: normal
Hi Daniel,
I have multiple peers defined in /etc/wireguard/wg0.conf
but setting AllowedIPs doesn't fully work for some of them
if I use `wg setconf`… and works perfectly fine if I do this
"manually" via `wg set wg0 peer my_public_key all
5 matches
Mail list logo
