Hi Frank,
On Sat, Apr 17, 2021 at 9:23 AM Frank Behrens wrote:
>
>
> Am 17.04.2021 um 17:00 schrieb Jason A. Donenfeld:
> > Does this actually fix or change anything? Don't new sockets have
> > fib==0 right out of the gate already?
>
> New sockets inherit the fib from the current process. If you
Hi Jason!
Am 13.04.2021 um 04:57 schrieb Jason A. Donenfeld:
Can you let me know if this fixes the issue?
https://git.zx2c4.com/wireguard-freebsd/commit/?id=cdb18ebf44a5babb57cddccd6b33e9f19cfdf365
It looks better, but a little too much optimized. ;-)
The fix is in
Hi Frank,
On 4/17/21, Frank Behrens wrote:
> Hi Jason!
>
> Am 13.04.2021 um 04:57 schrieb Jason A. Donenfeld:
>> Can you let me know if this fixes the issue?
>>
>> https://git.zx2c4.com/wireguard-freebsd/commit/?id=cdb18ebf44a5babb57cddccd6b33e9f19cfdf365
>
> It looks better, but a little too
Am 17.04.2021 um 17:00 schrieb Jason A. Donenfeld:
Does this actually fix or change anything? Don't new sockets have
fib==0 right out of the gate already?
New sockets inherit the fib from the current process. If you create
the wg interface from a process with different fib, that fib will
