Hi,
On 5/23/25 5:57 AM, Johannes Berg wrote:
From a user-experience point of view I think most people watching their
device trying to connect for more than about 20-30 seconds is going to
trigger a "wtf, this is broken" response. And I know if my router was
taking that long to accept connections it would be promptly rebooted.
Its a long way of saying that I think there is some reasonable value here.
We don't just implement wifi for laptops though. I mean we, Intel, do,
but generally the stack gets used elsewhere. The random IOT device out
in my garage? I don't really care where it waits, it only gets a single
BSSID it could ever use.
Yeah the use-case is important. And for mine where connectivity/uptime
is very critical even a 1 second comeback delay is too long and I would
want the device to roam/connect elsewhere, which then leads back to
CMD_ASSOC_COMEBACK.
So no matter what I'll need that event, I was mainly trying to figure
out why the kernel let these excessive wait times happen. I don't have
an answer as to where the cutoff would be though, so I guess I'll drop
it for now.
Thanks,
James
johannes
