Hi all,
So - I don't know if it's me being *thick* or wg-quick isn't supposed to do
this, but:
I have a wireguard config on my Macbook with addresses 10.3.0.5/31 &
fd10::10:3:41/127, other endpoint is .4 and :40.
Running wg-quick up wg-x works fine - pinging the v4 of the other side
doesn't
> > On 16.05.2018 09:10, Stefan Tatschner wrote:
> > How can I debug this further?
>
> Check the output of "ip rule".
As a user I can't read anything useful out of this, since I don't known how
wireguard android sets its fwmarks, etc. But here it is:
lux:/ # ip rule
0: from all lookup local
On 16.05.2018 09:10, Stefan Tatschner wrote:
> How can I debug this further?
Check the output of "ip rule".
--
-- Matthias Urlichs
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
Hi Jason,
thanks for your hard work!
On Wed, 2018-05-16 at 00:54 +0200, Jason A. Donenfeld wrote:
> [NEW] WireGuard for Android
> ---
> You can download the app from the Play Store or from F-Droid. It supports
> adding wg-quick(8)-style .conf files or .zips of them. The ap
Hi Tim,
On Wed, May 16, 2018 at 2:24 AM, Jason A. Donenfeld wrote:
> # TODO: this should use scutil and be slightly more clever. But for now
> # so horrible to deal with here, we'll simply wait for irate users to
> If you'd like to contribute a patch to do this properly, please don't
> h
On Wed, May 16, 2018 at 1:09 AM, Tim Sedlmeyer wrote:
> MacOS users should be aware that if you have manually assigned DNS servers
> the current wg-quick implementation will remove them and not restore them.
Wow, that was fast. Indeed, from the source [1], see comment:
set_dns() {
# TODO: th
MacOS users should be aware that if you have manually assigned DNS servers
the current wg-quick implementation will remove them and not restore them.
On Tue, May 15, 2018, 6:54 PM Jason A. Donenfeld wrote:
> Hey folks,
>
> We're gradually adding more platforms capable of running WireGuard, thank
