On Dec 11, 2019, at 12:32 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2019-12-10 at 15:51 -0800, Guy Harris wrote: >> On Sep 17, 2015, at 9:37 AM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > > Reviving an old thread :-) Yes - it came up with the Wireshark bug in question. >> But a presumably-Linux system does appear to use it; see Wireshark bug >> >> https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16272 >> >> For now, I'll throw a hack into Wireshark to treat a signal >= 60 GHz >> as meaning 11ad, > > I don't think that's quite right - you'll need to do something like >= > 56 GHz. Yes - there's a macro in Wireshark to test whether a frequency is in the 11ad range; it was testing for frequencies between 57 and 66 GHz. I changed the code to use that. I also changed it to test for 57 to 71 GHz; apparently, some regulatory domains have added (US) or may add (Canada, EU) more frequencies to the range allowed.
