From owner-freebsd-current@freebsd.org  Sun Jun  3 17:44:08 2018
Return-Path: <owner-freebsd-current@freebsd.org>
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 419C3FE4B00
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun,  3 Jun 2018 17:44:08 +0000 (UTC)
 (envelope-from cmt@burggraben.net)
Received: from smtp.burggraben.net (smtp.burggraben.net
 [IPv6:2a01:4f8:140:50a2::3:1])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id D0C937149B
 for <freebsd-current@freebsd.org>; Sun,  3 Jun 2018 17:44:07 +0000 (UTC)
 (envelope-from cmt@burggraben.net)
Received: from localhost (localhost [127.0.0.1])
 by smtp.burggraben.net (Postfix) with ESMTP id C85376002F3
 for <freebsd-current@freebsd.org>; Sun,  3 Jun 2018 19:44:06 +0200 (CEST)
X-Spam-Scanned: by amavisd-new at exwg.net
Received: from smtp.burggraben.net ([127.0.0.1])
 by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 9V5vN9Eyjitm for <freebsd-current@freebsd.org>;
 Sun,  3 Jun 2018 19:44:01 +0200 (CEST)
Received: from squirrel.exwg.net (unknown [145.253.109.162])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "squirrel.exwg.net",
 Issuer "Christoph Moench-Tegeder" (verified OK))
 by smtp.burggraben.net (Postfix) with ESMTPS
 for <freebsd-current@freebsd.org>; Sun,  3 Jun 2018 19:44:01 +0200 (CEST)
Received: by squirrel.exwg.net (Postfix, from userid 1000)
 id 6D3D12C29E3; Sun,  3 Jun 2018 19:44:01 +0200 (CEST)
Date: Sun, 3 Jun 2018 19:44:01 +0200
From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: freebsd-current@freebsd.org
Subject: Re: Can't seem to use 5GHz APs with Intel wireless
Message-ID: <20180603174401.rbxa3fcnuoprogow@squirrel.exwg.net>
References: <20180601091031.72u7tqfkatsl3guh@kazhap>
 <20180601223711.GA93642@elch.exwg.net>
 <20180603145342.qziiv7awhr4cvs73@kazhap>
 <CA+tpaK37cYp2kQOUJOMicgZNPJtobgCweEGutgt9n2r+Q=JMnA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CA+tpaK37cYp2kQOUJOMicgZNPJtobgCweEGutgt9n2r+Q=JMnA@mail.gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Jun 2018 17:44:08 -0000

## Adam (amvandemore@gmail.com):

> > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some
> > 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.

Regards,
Christoph

--