Date: Wed, 8 Apr 2026 17:21:49 -0400 From: "J.R. Oldroyd" <fbsd@opal.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: iwx VHT unknown rate (type 3) Message-ID: <20260408172133.3169e967@opal.com> In-Reply-To: <CAJ-VmokcsS8FGu1L6gbH1ZRik7KruAGHzjKh=noX1Nz2q-pMfw@mail.gmail.com> References: <20260408165253.2ec624bd@opal.com> <CAJ-VmokcsS8FGu1L6gbH1ZRik7KruAGHzjKh=noX1Nz2q-pMfw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Wed, 8 Apr 2026 14:02:59 -0700 Adrian Chadd <adrian@freebsd.org> wrote: > > Yup, it's a known issue, it should only happen during initial > negotiation when it's sending the early dhcp exchange and those frames > are marked as "please tell me what happened with them." > Later frames are handled completely in firmware and we don't get or > need per-frame completion information. > > I'll go sit down and finish cleaning that up shortly. It's harmless, > just a reminder that the code path needs converting to the newer world > order. > > > > -a > Thanks Adrian. Actually it's happening regularly during the day. Laptop is about 2m from the A/P with a clear line of sight so there shouldn't be any disconnects/reconnects. That said, the i/f is under a lagg with an Ethernet which is master at the moment so the wlan disconnects may be related to that. -jrhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20260408172133.3169e967>