From owner-freebsd-net@freebsd.org Mon Aug 22 22:36:52 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 69A9DBC201F for ; Mon, 22 Aug 2016 22:36:52 +0000 (UTC) (envelope-from kob6558@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 42DD11DF3 for ; Mon, 22 Aug 2016 22:36:52 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3E7D5BC201D; Mon, 22 Aug 2016 22:36:52 +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 3E123BC201C for ; Mon, 22 Aug 2016 22:36:52 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 F011B1DEC; Mon, 22 Aug 2016 22:36:51 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-it0-x234.google.com with SMTP id x131so114882851ite.0; Mon, 22 Aug 2016 15:36:51 -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=AIyO31EDrdqDAbgwrNW7f0Cg7WQBpdYwzglnv9XohEk=; b=qBYqFZsDQKAaZIk+njqjMT79rVlYS5eEENywamsMvU0M4FnOUlNHEXnHa2yEnZNCKl kzPWqCIys699Eb3ru75eqJlEGbodnDKQOKwom4vTgck3/IzmPnyKLrguVa/kshzS/kNY dQmTffMNtNoRjLBihPVM2aCHPBZv4+Sd2WjvNeSuWt8GRImIrYCuZoT7LxWQWAVC+UJR WSDivO4zkBPPJ4vlWMFwfGysarAnarTBQZxiEs0mBZJV9WYN/CQyBTU72WQx+dN6WIGE FpMxCzEy0+EkfKQI5aRbyIgqFxj0//5NMuc7bBWNI5UnmTX5MD3cjKclOJsBlusVvgVY PG5w== 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=AIyO31EDrdqDAbgwrNW7f0Cg7WQBpdYwzglnv9XohEk=; b=FJA9yCBIH2lsVMAxrglt3I87dZsWJpjgENMXxXAnaC24qebPwUUjiRrNLSpUQ7mgSk JnYA4upJgARPAUh5ZtyQx2h2+8/h2YZDGHIyKjo6FA+AkTCWwHeAfJcfUATWwJReZtzX T3jw22AITN4RRU4gGIgJZF8g9xgzCl4NgmRZ8TNy8bjF2y8luhfs09TsDiPxCFrkIoxk qvQidMPHvSEdCH4ZPxzAr6HiUCZsO2KrQUcCUKq5gp4AV5M+IM3bRlt22wh2fffr4Nkl sTig9vjmx8qFGYPmPtSpt2l4Xo/6pu07Y0zMG2tqXnaR2U0fia8eyrbkKuPsT3k6eJHh 58LQ== X-Gm-Message-State: AEkoousWPO7PIpHcyNYYmvPP6PeUFcNQQNSj63xEoGRJ7zDqJbcZe2GAHpTdkRnI0VPgNE2eKzcjN/mRZHU5/w== X-Received: by 10.36.39.195 with SMTP id g186mr21610276ita.53.1471905411421; Mon, 22 Aug 2016 15:36:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.119.144 with HTTP; Mon, 22 Aug 2016 15:36:50 -0700 (PDT) In-Reply-To: References: From: Kevin Oberman Date: Mon, 22 Aug 2016 15:36:50 -0700 Message-ID: Subject: Re: iwn(4) association issues in 11-Stable (and maybe RC) To: =?UTF-8?Q?Vin=C3=ADcius_Zavam?= Cc: Adrian Chadd , Andriy Voskoboinyk , FreeBSD Net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 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: Mon, 22 Aug 2016 22:36:52 -0000 On Mon, Aug 22, 2016 at 12:21 PM, Vin=C3=ADcius Zavam < egypcio@googlemail.com> wrote: > > > 2016-08-20 23:07 GMT-03:00 Adrian Chadd : > >> 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 L= ED >> > 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 >> > > since freebsd 11.0-current I am using my TP x201's wifi stuff w/o any > trouble. now it's running 12 with the very same comfort. it has an iwn... > 6200, I think. // but I did see people trying to use a 2230, and getting > nothing from it. > > > -- > Vin=C3=ADcius Zavam > keybase.io/egypcio/key.asc > I can now say that it IS dependent on the AP. On my home unit, it often associates on the first try and ALMOST always on the second. With the hotspot on my Galaxy S5 phone, it almost never associates on the first try and usually takes three or four tries, but I keep seeing "link state changed to UP" messages followed by "link state changed to DOWN". Over s single second I logged an UP followed by in a row followed by three cycles of UP and DOWN in one second and an UP that actually was UP. the next boot I got 4 UP/DOWN cycles (no double UP) but it gave up at this point. Then I did a "netif restart wlan0" and ti came up. Next boot had 8 UP/DOWN, but never actually appeared to associate. I am not seeing symptoms of the wpa_supplicant issue. The sample I included in the original message had the only repeat wpa_supplicant message. It is certainly not behaving like it did the last time I saw the that issue. None of these problems were seen with 10.3. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com