From owner-freebsd-current@freebsd.org Sun Jun 3 18:13:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD9AAFE814A for ; Sun, 3 Jun 2018 18:13:46 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C33672C08 for ; Sun, 3 Jun 2018 18:13:46 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id PXQwfMqY6SzNNPXQyfWUL5; Sun, 03 Jun 2018 12:08:53 -0600 X-Authority-Analysis: v=2.3 cv=KuxjJ1eN c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=7mUfYlMuFuIA:10 a=kgfhYre9AAAA:8 a=pGLkceISAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=hqx1a1BDsZXljwEO1yYA:9 a=CjuIK1q_8ugA:10 a=o4YRySerR8EA:10 a=FOgIJflhCR-CFpFWLMjf:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=cEB5NwCL2tbdTkCdtNfK:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id A3DB7270A; Sun, 3 Jun 2018 11:08:50 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w53I8oEc074731; Sun, 3 Jun 2018 11:08:50 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w53I8okL074728; Sun, 3 Jun 2018 11:08:50 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201806031808.w53I8okL074728@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Christoph Moench-Tegeder cc: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless In-Reply-To: Message from Christoph Moench-Tegeder of "Sun, 03 Jun 2018 19:44:01 +0200." <20180603174401.rbxa3fcnuoprogow@squirrel.exwg.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 03 Jun 2018 11:08:50 -0700 X-CMAE-Envelope: MS4wfI8ALj1VwtofzY/h0Yj70DJZI2RRUxKKDwkd8hjh+0w+TwdqJYag8ZN5NaNBiG8pdCWk+0JpMrelo6Mg86WHy2a61KO9PDjcb7Gub4+7mBHea7t5hikz Nj04BF7QK+rGRLdqQ/OJBSveTpGZkX6j0EVxUsCeZ8ZzORVP8LVWzVJ65ivLDhtZDoB30nGW9YCEY06CrA9WOXF80wpl4qFw9hWWFNI5nyGqQAkOrP8TqPe0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 18:13:47 -0000 In message <20180603174401.rbxa3fcnuoprogow@squirrel.exwg.net>, Christoph Moenc h-Tegeder writes: > ## Adam (amvandemore@gmail.com): > > > > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least som > e > > > I tested) > > > > I don't believe the iwn driver is capable of 5gz. At least mine doesn't > > work on CURRENT. > > The iwn driver has code for 5GHz (I've no idea if that's complete). > But looking at that reminded me: there are many "iwn" devices, including > some having "BGN" appended to their names - I'd guess those devices > don't support 5GHz aka 11a mode. My iwn device (iwn0: ) supports 5 GHz. I just disabled my 2.4 GHz APs and reassociated: wlan0: flags=8843 metric 0 mtu 1500 ether nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11na status: associated ssid XXXXXXXX-5G channel 153 (5765 MHz 11a ht/40-) bssid regdomain FCC country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 23 bmiss 120 mcastrate 6 mgmtrate 6 scanvalid 16959 ampdulimit 64k ampdudensity 8 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL groups: wlan Some devices do and others don't. For example, I have an ath card for this same laptop (I swapped out my iwn card for an ath card for a short while) that supports station mode (BTW iwn firmware doesn't), discovering my ath device firmware does not support 5 GHz. I suspect that some iwn devices may be similarly "crippled", though the driver supports 5 GHz the firmware does not. My point is it's not a binary issue. You may need to Google your particular card to determine if the manufacturer has implemented the feature or not. I did for my ath card discovering not all implementations are equal. I wouldn't be surprised this might be true of iwn as well. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few.