On R, 2020-08-21 at 10:04 -0400, Andrew Roth wrote:
> I did see wgnlpy [2], but don't think it is a fit since it relies on
> Netlink (Linux kernel interface), so it's not cross-platform
Some time ago I played around with netlink and using it to configure
WireGuard interfaces[1]. But it looks like
On E, 2020-06-29 at 14:15 +0200, Toke Høiland-Jørgensen wrote:
> In general I'd say that deviating from the RFC needs a good reason.
> Expanding the number of bits we can use for the identifier may be a
> good reason to expand the LL interface ID width (although I'm not
> actually too worried
On L, 2020-06-27 at 17:43 -0400, Reid Rankin wrote:
> Luckily, Blake2s is a simple and elegant algorithm, and in an effort
> to get some working code out there I've [implemented][1] it in ~100
> lines of Bash script.
It turns out that Python includes blake2s implementation that seems to
work with
On K, 2020-05-27 at 11:01 +0200, nicolas prochazka wrote:
> How can i know that a packet come from peer X ?
You can check which peers allowed ips list covers the received packets
source ip
> Is is possible to mark packet not a level interface (wg0) but at peer
> level ?
Its probably possible to
On P, 2020-04-05 at 19:43 -0400, Reid Rankin wrote:
> However, I've taken it one step further, by using
> cryptographically-generated addresses; each peer automatically gets
> fe80:(truncated hash of pubkey)/128 stuck in its allowed IP list.
> (I'm considering harmonizing this address generation
On P, 2020-03-15 at 14:16 +0100, J.R. Oldroyd wrote:
> New here. Apologies if I am re-hashing something discussed before.
> I did read back a few months of this list and didn't see any relevant
> discussion.
Quite a lot of information can also be obtained via Linux Wireguard
module. wg(8) man
On E, 2020-02-17 at 15:47 +1100, Matthew Oliver wrote:
> Someone asked about this in the IRC channel, so quickly wrote up a
> patch to add it. No pressure if you do/don't want to merge it :)
If you have wireguard-tools package installed then it should be
possible to use the incldued wg-json
> Hi!
>
> I'm new to WireGuard and a formerly user with some experiences
on
> OpenVPN with complex setups but sometimes (I believe) a tools must
be
> changed ;-)
>
> Now my environment will be migrated to WireGuard and
I have wrote a
> little shell script to get a status page for my
peerings.
>
