You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2018. It is now read-only.
I am running into a problem where "aireplay-ng -9" is not seeing some APs in 5 GHz band.
These APs are visible when running airodump-ng.
Looking at the code of grab_essid, the first thing it does is look for a "DSSS Parameter Set" IE (IE ID, AKA tagtype, 3), and bails if it doesn't find it. So, any AP that doesn't include it in Beacon or Probe Response will be ignored.
However, by my reading of the standard, that IE is not required when using OFDM in the 5 GHz band. So this seems like a bug.
The text was updated successfully, but these errors were encountered:
I am running into a problem where "aireplay-ng -9" is not seeing some APs in 5 GHz band.
These APs are visible when running airodump-ng.
Looking at the code of grab_essid, the first thing it does is look for a "DSSS Parameter Set" IE (IE ID, AKA tagtype, 3), and bails if it doesn't find it. So, any AP that doesn't include it in Beacon or Probe Response will be ignored.
However, by my reading of the standard, that IE is not required when using OFDM in the 5 GHz band. So this seems like a bug.
The text was updated successfully, but these errors were encountered: