News for hackers. Stuff that matters.
Re:Diagnosing an Unusual WiFi Issue by dehrmann on Friday January 03, 2025 @12:46PM (#42587778)
> Scanning for nearby WiFi access points with excessive frequency might be a dumb idea for other reasons (e.g. power consumption) but it should not interrupt the functionality of the current network connection.

Scanning works by tuning the radio to listen for a beacon sent by the AP every ~100ms on every channel (there are 11 2.4 GHz and ~22 5 GHz channels in the US). Since you're not transmitting, it should be low-power, but you have to tune the radio to each channel, so you can't communicate with your AP.

Re:Diagnosing an Unusual WiFi Issue by dlenski on Friday January 03, 2025 @01:54PM (#42588416)
> Scanning works by tuning the radio to listen for a beacon sent by the AP every ~100ms on every channel (there are 11 2.4 GHz and ~22 5 GHz channels in the US).

Yes, but good drivers can mitigate the latency hit by not scanning all the channels at once. https://blogs.gnome.org/dcbw/2016/05/16/networkmanager-and-w....

> Since you're not transmitting, it should be low-power,

Depending on the hardware/firmware quality, tuning to each channel can use a lot of energy. As for "not transmitting," this is true for passive scanning (generally preferable) but not for active scanning.

> but you have to tune the radio to each channel, so you can't communicate with your AP.

Right, but _if the OS and drivers are written properly_ (on both the client device as well as the AP ) they'll buffer unsent packets… the high latency during the channel changes is unavoidable, but the dropped packets and broken TCP streams are NOT.

Re:Diagnosing an Unusual WiFi Issue by vel0city on Friday January 03, 2025 @02:15PM (#42588596)
From your quote:

> With a good driver scanning takes only a few seconds

A few seconds of not transmitting or receiving packets. This is in line with people having sudden several hundred millisecond ping spikes.

A few seconds of no real traffic is absolutely noticeable impact for constant, latency sensitive traffic.

Re:Diagnosing an Unusual WiFi Issue by dlenski on Friday January 03, 2025 @02:51PM (#42588876)
> From your quote: > > With a good driver scanning takes only a few seconds

You omitted the immediately following text: "*and the driver breaks the scan into chunks*, returning to the associated access point’s channel periodically to handle pending traffic."

A good driver will return to the AP's channel _during the scan_ so that there is never more than (say) 100 ms of latency even while the scan is ongoing.