On Mon, Oct 21, 2024 at 01:44:58PM +0200, Kirill A. Korinsky wrote:
> On Mon, 21 Oct 2024 11:19:48 +0200,
> "Anthony J. Bentley" wrote:
> >
> > Vitaliy Makkoveev writes:
> > > I suspect vio(4).
> >
> > Maybe there are multiple bugs. But as we've discussed before, wg(4) is
> > crashy on em(4) too
On Mon, Oct 21, 2024 at 6:11 AM Martin Pieuchot wrote:
>
> On 21/10/24(Mon) 01:12, William Thebrand wrote:
> > I pull the newest snapshot release every sunday, and run a full upgrade on
> > my system. Which means the OS, packages, and even git based projects I use.
> > Four times in a row, the sys
>Synopsis: Any luser can make a hardlink to a file not owned by them
>Category: system
>Environment:
System : OpenBSD 7.5
Details : OpenBSD 7.5 (GENERIC.MP) #2: Mon Sep 16 07:59:35 MDT 2024
r...@syspatch-75-arm64.openbsd.org:/usr/src/sys/
An anecdotal note:
I've been running Wireguard on multiple firewalls since it was first
built into the kernel. One configuration is a central site that 3
remote sites depend on, on a 24/7 basis. I have had (knock on wood, I
guess) no issues, crashes, etc. whatsoever. And the systems have been
updat
I’ll test your recommendations over the next few days, but I don’t expect
-tcplro to make any difference, as wireguard only uses udp.
For the nic, I can choose between virtio, e1000, and rtl8139, so I’ll be
testing each one individually, both with and without ipv6.
> On 23. Oct 2024, at 10:07, V
> On 23 Oct 2024, at 23:36, Oliver Schweger wrote:
>
> I’ll test your recommendations over the next few days, but I don’t expect
> -tcplro to make any difference, as wireguard only uses udp.
I know, but it was reported that -tcplro helps. So I want to check correlation.
