Hi again,
I think there is a small mistake in the installation instruction for
Debian, sorry about that: the "Pin-Priority" should be set to 150 instead
of 200.
Long explanation: on jessie, the jessie-backports repository also has a
priority of 200. After enabling unstable with the same
On 08/07/17 03:26, raul wrote:
> 4. The Wireguard server is a single point of failure in a star topology.
> If the server host goes down your network goes down with it. How can we
> add more resilience in a simple way? A backup server in L2 with
> identical keys and a floating internal IP?
I have
Hi,
The current approach is to queue all outgoing packets for an indefinite
amount of time when the peer is not connected or reachable.
I think it does not make much sense, and leads to the kind of issue you
mention here. The initial goal was probably to queue packets just long
enough to be
I can personally see there being use in both the getting sendto errors
but also in simply dropping the packets (depending on the software you
have communicating over wireguard). So rather than change it entirely, I
would suggest making that an option of some sort.
As an aside, a single
Hi,
I am new to wireguard.
I have following queries:
1. I am new to wireguard. How can I contribute to its development. Or
modify code etc.
2. Is it possible to use wireguard beside IP base systems? Like what about
if it will be deployed over zigbee protocol running devices?
3. Is it possible to
