On Mon, Apr 22, 2024 at 04:18:46PM +0200, Mark Kettenis wrote:
> > Date: Mon, 22 Apr 2024 15:39:55 +0200
> > From: Alexander Bluhm
> >
> > Hi,
> >
> > I see a witness lock order reversal warning with soreceive. It
> > happens during NFS regress tests. In /var/log/messages is more
> > context
> Date: Mon, 22 Apr 2024 15:39:55 +0200
> From: Alexander Bluhm
>
> Hi,
>
> I see a witness lock order reversal warning with soreceive. It
> happens during NFS regress tests. In /var/log/messages is more
> context from regress.
>
> Apr 22 03:18:08 ot29 /bsd: uid 0 on
>
Hi,
I see a witness lock order reversal warning with soreceive. It
happens during NFS regress tests. In /var/log/messages is more
context from regress.
Apr 22 03:18:08 ot29 /bsd: uid 0 on
/mnt/regress-ffs/fstest_49fd035b8230791792326afb0604868b: out of inodes
Apr 22 03:18:21 ot29
On Sun, Apr 21, 2024 at 06:31:39PM +0200, Kirill A. Korinsky wrote:
> Greeting,
>
> finally I've catch something. I not sure is it the same error or not, but it
> seems right to share anyway.
>
> It was get from snapshot which was installed about 3 days ago.
>
> Apr 21 10:59:40 matebook /bsd:
On Mon, Apr 22, 2024 at 10:46:50AM +0200, Peter J. Philipp wrote:
> Hi,
>
> I have a shortage of RJ45 adapters so I had to expose one host on wifi, for
> this I set up an access point of type "AVM Fritz!Box 7390" with latest
> firmware
> from last year.
>
> Soon I started facing deauth
Hi,
I have a shortage of RJ45 adapters so I had to expose one host on wifi, for
this I set up an access point of type "AVM Fritz!Box 7390" with latest firmware
from last year.
Soon I started facing deauth attacks from someone within my wifi cell region.
Since the deauthers were spoofing my
