From owner-freebsd-net@freebsd.org Sun Aug 21 02:07:17 2016 Return-Path: Delivered-To: freebsd-net@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 89422BB93E1 for ; Sun, 21 Aug 2016 02:07:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 68D521356 for ; Sun, 21 Aug 2016 02:07:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 68266BB93E0; Sun, 21 Aug 2016 02:07:17 +0000 (UTC) Delivered-To: net@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 67CC8BB93DF for ; Sun, 21 Aug 2016 02:07:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3264B1355; Sun, 21 Aug 2016 02:07:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id n128so55724274ith.1; Sat, 20 Aug 2016 19:07:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/IVu4qRZHPxaz8x4qdN+YRBDj5SbTHehcy69NJKbXMo=; b=J7gZMKjpg2WVA3pxQxFlslL8MU5VAvzaD75gs8UhAT4nbldK6qhPztNuduYSaAhhvT I7TiUcD6iKdSFKPkF+PCllEB6kYiLu6o8glW2Zs6c1ZoG36lx5AtzYKj0QWZXj5PHMn4 om5sFRvhCrNqkPj2mPKi9sMUwhNHJrrKKuaBXjfG51gw31UTKm66ds1zzQQZ+Rsi4HEK QM65ur9yso6f6iCJGk47LQM2PN5qgZ1R/1WdojiYSKkDncdgsvNwUHzOrTYaW2AGuclP KNimb50GVC+0U3jIKrwlvWz4IR304d7huksGeA57s33jKBqzeLh9EnZ0MtB71YaEmFSj 4L3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/IVu4qRZHPxaz8x4qdN+YRBDj5SbTHehcy69NJKbXMo=; b=EEgA3eSCv+RN09g8aKLeF79xjVWTXJnRBNghBFzS85JhhnDqVROemgqeWV8c8+ILBu P2vmiVgxutTNn8YI6xeOqnus1z4mJ74RRumOngyfBD8ae4GKEzpBJDzXo2s5ySetUWn7 XNPuocqPDL/kNbc4/pyvEcm12W8dUgSxp2qhXOWIqQLv/z1Dy8Izo8nTpEL0iHZ3nofu DLD6yMY6MEk0+sEOrGTYcIGakulyIOI5Zq8dEsstwBtXky8xKiPXRO7KTUUWeYlZ2cZu uPfyVsTWpvX6m3dTnZU2dukoniQpuatvrQj1eJvcIVUqe7ECEeUGtxKFNTua3x13dUWx CDdg== X-Gm-Message-State: AEkoouuOxFlUn3/YkofUW4277AEZgDWz4Op1+sQS1jYhj3xjxJQHyG8yiFYTtIAQyt9csAka+/m6dzYZoD1Qxw== X-Received: by 10.36.124.141 with SMTP id a135mr13314648itd.25.1471745236554; Sat, 20 Aug 2016 19:07:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.141.129 with HTTP; Sat, 20 Aug 2016 19:07:15 -0700 (PDT) In-Reply-To: References: From: Adrian Chadd Date: Sat, 20 Aug 2016 19:07:15 -0700 Message-ID: Subject: Re: iwn(4) association issues in 11-Stable (and maybe RC) To: Kevin Oberman Cc: FreeBSD Net , Andriy Voskoboinyk Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2016 02:07:17 -0000 On 20 August 2016 at 19:02, Kevin Oberman wrote: > On Aug 20, 2016 6:29 PM, "Adrian Chadd" wrote: >> >> Hi, >> >> There have been some changes to the scan code and iwn scan timeout code. >> Andriy may have some ideas. >> >> Thanks! >> >> A > > One more note. There are multiple "link up" messages in the log. The LED > never stopped the flashing which indicates that it is not associated. If I > did "ifconfig wlan0 list aps", my hot spot was listed, but a simple > "ifconfig wlan0" never showed an association. Usually a few "netif restart"s > will get it to work, but sometimes it seems hopeless. It seems worse when my > phone is the hot spot than with my home router. I've not seen this happen with any of the iwn hardware that I have, but wifi is odd like that. it looks like wpa_supplicant is started twice. Is that happening? That (sigh) still may be making things unhappy. -adrian