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 the problem?
yes, I can still replicate it with 0.0.20190905-1 but I do it on stable (first Stretch now Buster) with packages from unstable (without rebuilding them). Every time different peer (I have 11 of them) gets a non complete AllowedIPs so I admit it's hard to reproduce… PS I have another problem that I didn't report yet on one (and only one) of my peers which I don't think is related, but in case it is: from time to time (sometimes few days apart sometimes weeks) wireguard freezes (as in it doesn't accept any in/out connections). Restarting (ip l set dev wg0 down and up again) doesn't help. What helps is to change listening port to something else. This peer has a non-public and dynamic IP (but I have another client using the same provider on my OpenWRT router and it seems to work fine there)
