Hello,
It would be useful to have a named wg_endpoint type in the embeddable wg
library. It's added by the attached patch.
/Mikael
>From 62b35cb221af7208399fced86660585080c688f5 Mon Sep 17 00:00:00 2001
From: Mikael Magnusson
Date: Sat, 7 Nov 2020 13:32:56 +0100
Subject: [PATCH]
On 2021-03-01 21:09, i iordanov wrote:
Hi Frank,
On Mon, Mar 1, 2021 at 9:42 AM Frank Carmickle wrote:
Maybe it's a bug and not a feature? It seems to me that you would have no way
of setting the MTU on the inner tunnel.
That's true - other than inefficient packet fragmentation, is there
On 2020-06-14 20:19, Sergey Ivanov wrote:
Hi,
I have a question about wg0 on OpenWRT not forwarding packets from one
client to another. I have a laptop at home in my home LAN, and a
computer at work in a very restricted LAN. They can not see one
another. I spent a lot of time trying to get them
Hello,
I have an improvement to IpcGetOperation in wireguard-go.
uapi: IpcGetOperation: return peers in sorted order
Sort peers based on the public key.
The pros of using a sorted peer list is that the order doesn't change in
each ipc operation, or execution of the "wg showconf" command. Which
On 2019-09-30 09:52, Nico Schottelius wrote:
At lookup time this works already. The problem is, if the underlying
network topology changes and you need to reconnect via IPv4, when you
had IPv6 underlying before.
It doesn't work for me at least not with the Android app. I have a DNS
name with
Hello list,
I'm experiencing crashes in wg_allowedips_insert_v4 and
wg_allowedips_insert_v6 in the wireguard kernel module. It happens both
with the current snapshot (0.0.20190227-wg1~bionic) and the current git
master (65e1f283). It seems to be caused by commit 20a230b3 (allowedips:
On 2019-03-26 15:17, Julian Orth wrote:
Hello list,
I'm currently using WireGuard on Android for two purposes:
1. Routing all traffic via a commercial VPN provider to protect myself on
open wireless networks.
2. Connecting to my home network.
Unfortunately WireGuard on Android does not
On 04/15/2018 08:49 PM, Patrick O'Sullivan wrote:
$ sudo ip route show
default via 10.199.199.1 dev wlan0
10.111.111.0/24 dev wg0 proto kernel scope link src 10.111.111.100
10.199.199.0/24 dev wlan0 proto kernel scope link src 10.199.199.131
By this route table, traffic to e.g. 4.2.2.1 should
On 04/12/2018 01:42 PM, Christophe-Marie Duquesne wrote:
Long story short, you need a proper central server that will find the
next ip address, or you need to stick to ipv6 (and in that case the
address space makes it pointless to do that check).
I think one option is to use the
