Hi,
first message to the list, want say hello and want report with a problem I
discovered when I play with the wireguard.
Setup:
Point to point tunnel (ARM-10.x.x.x) (FW) (www) (Server)
Tunnel fine no problem all works as expected.
On the ARM-10.x.x.x runs a service announce kind of service
On 13 Nov 2017 at 20:34, Jason A. Donenfeld wrote:
> I've fixed this all up here:
> https://git.zx2c4.com/WireGuard/commit/?id=e4bf02b833f99f4dcc2ab685d92517ccf8cc4766
>
> I think it _should_ work now. Thanks for the suggestions. I just
> monkey patched the signatures of each of those functions.
Hey Pipacs,
On Mon, Nov 13, 2017 at 2:39 AM, PaX Team wrote:
> at fptr dereference time RAP will still see the type hash mismatch.
> another approach could be to depend on TIMER_DATA_TYPE instead and use
> it in your callback prototypes. as a sidenote, if you want to depend
> on plugin related fe
Hi Roman,
Thanks for the configuration. Could you try this commit, and tell me
if it fixes the problem for you?
https://git.zx2c4.com/WireGuard/commit/?id=921c3eb23009558fdd4a64c36c379b7a8dc6b22f
Regards,
Jason
___
WireGuard mailing list
WireGuard@list
November 13, 2017 12:18:28 AM CET Stephen Major wrote:
>This is a two-fold question:
>
>1) Can Wireguard be used directly with Yubikeys: https://www.yubico.com
>
>2) Can Wireguard be used with a radius server like
>GreenRADIUS:http://www.greenrocketsecurity.com/greenradius/
In case of [1] you c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
You cannot have more than one peer with the same AllowedIPs
entries. This is clearly documented on the "CryptoKey Routing"
section of the homepage. The reason is simple: when sending,
WireGuard would not know to which peer to send the traffic.
- --
