From owner-freebsd-amd64@freebsd.org  Fri Oct 14 10:01:08 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71DDDC0F848
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Fri, 14 Oct 2016 10:01:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 61C69AB5
 for <freebsd-amd64@FreeBSD.org>; Fri, 14 Oct 2016 10:01:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EA162k075616
 for <freebsd-amd64@FreeBSD.org>; Fri, 14 Oct 2016 10:01:08 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 213456] Problem with iwn firmware on 11-RELEASE
Date: Fri, 14 Oct 2016 10:01:07 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: wireless
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: vbotka@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-wireless@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-213456-6-Ia89S34F0h@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213456-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-213456-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2016 10:01:08 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213456

Vladimir Botka <vbotka@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vbotka@gmail.com

--- Comment #5 from Vladimir Botka <vbotka@gmail.com> ---
Hello! FWIW. Let me share my experience with 6205 in Linux.

1) If there is too many APs arround (~30) the driver doesn't connect. In th=
is
case it was worth to try and configure wpa_supplicant with:
    ap_scan=3D0
and limit the scanning for specific SSID
    scan_freq=3D <list of the frequencies>

2) Disabling fast re-authentication sometimes helped to stop dropping WPA-E=
AP.
    fast_reauth=3D0

I have no 6205 in FreeBSD box atm. Sorry. HTH, Cheers,

-vlado

--=20
You are receiving this mail because:
You are on the CC list for the bug.=