From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E9E94C43603 for ; Fri, 20 Dec 2019 22:07:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C24F32146E for ; Fri, 20 Dec 2019 22:07:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727507AbfLTWG7 convert rfc822-to-8bit (ORCPT ); Fri, 20 Dec 2019 17:06:59 -0500 Received: from c.mail.sonic.net ([64.142.111.80]:52240 "EHLO c.mail.sonic.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727489AbfLTWG7 (ORCPT ); Fri, 20 Dec 2019 17:06:59 -0500 X-Greylist: delayed 619 seconds by postgrey-1.27 at vger.kernel.org; Fri, 20 Dec 2019 17:06:59 EST Received: from [192.168.42.66] (173-228-4-7.dsl.dynamic.fusionbroadband.com [173.228.4.7]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id xBKLuImh004978 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 20 Dec 2019 13:56:20 -0800 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Correct radiotap header for 802.11ad From: Guy Harris In-Reply-To: <4cf0c2a4a2d1cd92dff4f1a791d74523e446cf01.camel@sipsolutions.net> Date: Fri, 20 Dec 2019 13:56:16 -0800 Cc: "radiotap@netbsd.org" , Simon Barber , Richard Sharpe , linux-wireless@vger.kernel.org, Maya Erez , wil6210@qti.qualcomm.com Content-Transfer-Encoding: 8BIT Message-Id: References: <38F46E1D-1C4A-48DC-A906-9522006E8474@alum.mit.edu> <1606812C-649C-4C06-ABE0-AE2F4474BCD0@alum.mit.edu> <1440402013.3735.1.camel@sipsolutions.net> <55DE44EB.6080603@superduper.net> <126B842D-05EA-4510-BC9B-DB1A4AABEC12@alum.mit.edu> <1135A126-6A5A-4C84-A52D-13C0387609CC@alum.mit.edu> <1442507879.2821.9.camel@sipsolutions.net> <4cf0c2a4a2d1cd92dff4f1a791d74523e446cf01.camel@sipsolutions.net> To: Johannes Berg X-Mailer: Apple Mail (2.3445.104.11) X-Sonic-CAuth: UmFuZG9tSVb7wgtVfHcrCfsU7J35lsQEiXr5q3QBNggUhaW39lCqs5yQ8Ab01ERMy+oFdIcBpQ73VHRst3c3k/gyyxsX1kD/ X-Sonic-ID: C;Snb9jHMj6hGWNCGeTRzYKg== M;GAJwjnMj6hGWNCGeTRzYKg== X-Sonic-Spam-Details: 0.0/5.0 by cerberusd Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Dec 11, 2019, at 12:32 AM, Johannes Berg wrote: > On Tue, 2019-12-10 at 15:51 -0800, Guy Harris wrote: >> On Sep 17, 2015, at 9:37 AM, Johannes Berg 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.