From owner-freebsd-wireless@freebsd.org Sun Nov 20 08:14:34 2016 Return-Path: Delivered-To: freebsd-wireless@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 C26A8C4BF90 for ; Sun, 20 Nov 2016 08:14:34 +0000 (UTC) (envelope-from fnoyanisi@yahoo.com) Received: from nm32-vm1.bullet.mail.bf1.yahoo.com (nm32-vm1.bullet.mail.bf1.yahoo.com [72.30.239.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 78A231D59 for ; Sun, 20 Nov 2016 08:14:33 +0000 (UTC) (envelope-from fnoyanisi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1479629524; bh=uCJQn1YcR3yP4f58GkLYVIlclSI3Wm1NDEO3Kkklqfo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=sRYevFS3LyX1TJ7D4+YxCIub/m2xWAgGoI4dSIrF3qgAtGACXBT+VdMIccejVtkqykKBP7AdxtYcusE4TYSMRiiiu97Ttx22WTEiNOEpDh3xl894Sx6oqiG2RP4EGENoIuKJswmxVnHbJ+j11C+6fryqzKuW7YBFqbWiC2i6lmKrqsFV39B7X0DcEA2FOexDhoPxxZpa+FYygIH3krX2GseWmKagGHPIKzMcb8AIt08tWkNYwVSAWkLAiUEXG7ArybCaMZJuZy1EoO9jlMVxQEmhG4Xu3c3iMu037pgx1dr1zdqx6xglbxf4FivXDg76AweMY0zmMNSGEhystNMzPw== Received: from [66.196.81.170] by nm32.bullet.mail.bf1.yahoo.com with NNFMP; 20 Nov 2016 08:12:04 -0000 Received: from [98.139.212.244] by tm16.bullet.mail.bf1.yahoo.com with NNFMP; 20 Nov 2016 08:12:04 -0000 Received: from [127.0.0.1] by omp1053.mail.bf1.yahoo.com with NNFMP; 20 Nov 2016 08:12:04 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 646735.75651.bm@omp1053.mail.bf1.yahoo.com X-YMail-OSG: 6zEuZHcVM1lMzYn6bvcuxamxF_QB.AjkBXK.fJjfXHe0.br9xu7WYBhS.oL7qtI I9TgpNGwck..YsyL4zPhb4vvLbl7BJMX.BX1XY23MpnA99yZ3ZRs9yK0HlErmpDmNnfhaUSyTOdO k5KPd0uLhG70sv2X541Dm0djmO.RproBAnCQUlftobAj.D9dMZ92.HaN6jHyKro7zBG.64TnYR4f V0uZ_70O4feVzSaosKfdPcGLavtwDyMPJ2dHuEvkbqQ7D_7cABfAo_uv1LAIJghqmuCZMFExbK5W lpKgAw1zKywVKYAG6UU9XSufJ_U0jb4QFCPKKyxuI4VQHDDhKjfOdjM5kopKK8EzUWi.c24Ko0vS ulu_RPJ.Ja52nhJn9HjIDzF5Sx3UcCLp0HT.0mfG2FXcH3756OsVux1NDWxfa4CbRlqR2mpt8o6R t4A5n3f2VUNm87S30FUX10ewEAKuP7WGiOYTpxGe7Q7IqrAUwGXAMO7nnMMf63SW_CQZUXtQlkwO MBZLXc8SWKjljMGyS4SY- Received: from jws400095.mail.bf2.yahoo.com by sendmailws163.mail.bf1.yahoo.com; Sun, 20 Nov 2016 08:12:04 +0000; 1479629524.286 Date: Sun, 20 Nov 2016 08:12:04 +0000 (UTC) From: Fehmi Noyan ISI Reply-To: Fehmi Noyan ISI To: Adrian Chadd Cc: Freebsd Wireless Message-ID: <456881900.492024.1479629524039@mail.yahoo.com> In-Reply-To: References: <980351195.1573665.1479336792289.ref@mail.yahoo.com> <980351195.1573665.1479336792289@mail.yahoo.com> <2112311201.1853303.1479370511602@mail.yahoo.com> <1703426610.2431782.1479426526331@mail.yahoo.com> Subject: Re: Using net80211/IEEE80211_C_BITS macro MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 08:14:34 -0000 Thanks Adrian! Checked out revision 308871 and compiled the system from source. Had no issues during the built process. Also, verified the changes in the source tree Script started on Sun Nov 20 20:59:17 2016 root@test:~ # grep IEEE80211_C_BITS /usr/src/sbin/ifconfig/* /usr/src/sbin/ifconfig/ifieee80211.c: printb("drivercaps", dc->dc_drivercaps, IEEE80211_C_BITS); root@test:~ # grep IEEE80211_C_BITS /usr/src/sys/net80211/* /usr/src/sys/net80211/_ieee80211.h:#define IEEE80211_C_BITS \ /usr/src/sys/net80211/ieee80211_ddb.c: db_printf("\tcaps=%b\n", vap->iv_caps, IEEE80211_C_BITS); /usr/src/sys/net80211/ieee80211_ddb.c: db_printf("\tcaps=%b\n", ic->ic_caps, IEEE80211_C_BITS); root@test:~ # exit exit I used a VM (my only laptop has -RELEASE on it :{ , tried some bhyve trick like iwn passthru but did not succeed), hence could not specifically test "ifconfig wlan0 list caps" but since compilation went smooth, I would assume it should be OK. After all, changes do not constitute any new features or functions. Anything on the time frame till we could see this change on -RELEASE branch? Thanks ----- Original Message ----- From: Adrian Chadd To: Fehmi Noyan ISI Cc: Freebsd Wireless Sent: Saturday, November 19, 2016 10:12 AM Subject: Re: Using net80211/IEEE80211_C_BITS macro Hi! Fixed in the latest -head. Two commits - one for net80211, one for ifconfig! -a From owner-freebsd-wireless@freebsd.org Sun Nov 20 18:12:24 2016 Return-Path: Delivered-To: freebsd-wireless@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 D44CDC4C701 for ; Sun, 20 Nov 2016 18:12:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::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 98F7574 for ; Sun, 20 Nov 2016 18:12:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x234.google.com with SMTP id n13so23593374ioe.2 for ; Sun, 20 Nov 2016 10:12:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Y04Co0INmd7p7m6zEhef8mgLGFD8hqirsvvECLJ/gok=; b=q1f/tI2TFDhPFqvJAlHyI4y82ciDjfV9IBMMsdyI1VgsjyChrW1eqC8KWBeKxdkmnk WjjEgS0aH7jrA07/SLdv3dK7Rmdoz6qbp2G8YrkYjyUaB43gjlMZllD7rUVzhqjEr89D eKQ3tVfJQJkF5oAEuiPJxMCo+vqSSweZOxI78N2TDQPdUA3TmQeckPuqko/g4Rx0oc6K LCX7daO7yJmc3iJN74UlPFsY/vw8iD6r+JiS55hqj25oe+cqN6by1jeTSVRyxB0vi4m7 1dkKMTbQeLHGKlevfeWfcEnJxi9hD4zvgAmZITkpRdnPs3jnjfrXah5QGlbE8YB1KK2M 5r8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Y04Co0INmd7p7m6zEhef8mgLGFD8hqirsvvECLJ/gok=; b=PgymsZSaheb1DfCkfxae6FaOeX9qXFqGN9J/4I42pFl+1F3QSNCWpwrnfR8WQ9vc0B TXlM5KcE1546qUxPSkCQsVfv0/QSuyMpTqkQNYDl3JCv8J+iPq2zTfA+UkEW1rjk6WOI dGvK+jDjItwiOWLVxR3Sn5vsTF2c1/eOO+Un8Vd2m3ap+b7sgksb1xtVQprkcYscXgmA wjNJKBIOuZG+pgYNr6zmGXYlSP9yN84NAv9bz5wmcEyxAy7Gy7B4VMASh4Zus/PIPo0W yT93D6W40ASkg8wJPcrJVhABL1Qu2idNiB9+njMMLQ0LLSgxulgUJ6colQN9R64Kfq1R 1sbA== X-Gm-Message-State: AKaTC02w6pxaaV+XqrrJkWY3/Ns29xFdPWpb1VL3bUuEMS05QVnmxS26N4cPGqRQvCRZDJg4BtJENwIM/mwQkg== X-Received: by 10.107.136.86 with SMTP id k83mr7301646iod.99.1479665543943; Sun, 20 Nov 2016 10:12:23 -0800 (PST) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.39.134 with HTTP; Sun, 20 Nov 2016 10:12:22 -0800 (PST) Received: by 10.36.39.134 with HTTP; Sun, 20 Nov 2016 10:12:22 -0800 (PST) In-Reply-To: <456881900.492024.1479629524039@mail.yahoo.com> References: <980351195.1573665.1479336792289.ref@mail.yahoo.com> <980351195.1573665.1479336792289@mail.yahoo.com> <2112311201.1853303.1479370511602@mail.yahoo.com> <1703426610.2431782.1479426526331@mail.yahoo.com> <456881900.492024.1479629524039@mail.yahoo.com> From: Adrian Chadd Date: Sun, 20 Nov 2016 10:12:22 -0800 X-Google-Sender-Auth: -yhjc-3g9_c43zFhqrHQEdtBSqU Message-ID: Subject: Re: Using net80211/IEEE80211_C_BITS macro To: Fehmi Noyan ISI Cc: Freebsd Wireless Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 18:12:24 -0000 I'll try to find someone to back port the wifi bits to stable/11 before they get too problematic. A On Nov 20, 2016 12:12 AM, "Fehmi Noyan ISI" wrote: > Thanks Adrian! > > Checked out revision 308871 and compiled the system from source. Had no > issues during the built process. > > Also, verified the changes in the source tree > > > Script started on Sun Nov 20 20:59:17 2016 > root@test:~ # grep IEEE80211_C_BITS /usr/src/sbin/ifconfig/* > /usr/src/sbin/ifconfig/ifieee80211.c: printb("drivercaps", > dc->dc_drivercaps, IEEE80211_C_BITS); > root@test:~ # grep IEEE80211_C_BITS /usr/src/sys/net80211/* > /usr/src/sys/net80211/_ieee80211.h:#define IEEE80211_C_BITS \ > /usr/src/sys/net80211/ieee80211_ddb.c: db_printf("\tcaps=%b\n", > vap->iv_caps, IEEE80211_C_BITS); > /usr/src/sys/net80211/ieee80211_ddb.c: db_printf("\tcaps=%b\n", > ic->ic_caps, IEEE80211_C_BITS); > root@test:~ # exit > exit > > > I used a VM (my only laptop has -RELEASE on it :{ , tried some bhyve trick > like iwn passthru but did not succeed), hence could not specifically test > "ifconfig wlan0 list caps" but since compilation went smooth, I would > assume it should be OK. After all, changes do not constitute any new > features or functions. > > Anything on the time frame till we could see this change on -RELEASE > branch? > > Thanks > > > ----- Original Message ----- > From: Adrian Chadd > To: Fehmi Noyan ISI > Cc: Freebsd Wireless > Sent: Saturday, November 19, 2016 10:12 AM > Subject: Re: Using net80211/IEEE80211_C_BITS macro > > Hi! > > Fixed in the latest -head. Two commits - one for net80211, one for > ifconfig! > > > > -a > From owner-freebsd-wireless@freebsd.org Sun Nov 20 21:00:58 2016 Return-Path: Delivered-To: freebsd-wireless@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 B8EB4C4CAEE for ; Sun, 20 Nov 2016 21:00:58 +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 AED72236 for ; Sun, 20 Nov 2016 21:00:58 +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 uAKL01sK016611 for ; Sun, 20 Nov 2016 21:00:58 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201611202100.uAKL01sK016611@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-wireless@FreeBSD.org Subject: Problem reports for freebsd-wireless@FreeBSD.org that need special attention Date: Sun, 20 Nov 2016 21:00:58 +0000 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 21:00:58 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 206801 | iwn(4) page fault on netif restart Open | 154598 | [ath] Atheros 5424/2424 can't connect to WPA netw Open | 163312 | [panic] [ath] kernel panic: page fault with ath0 Open | 166190 | [ath] TX hangs and frames stuck in TX queue Open | 166357 | [ath] 802.11n TX stall when the first frame in th Open | 169362 | [ath] AR5416: radar pulse PHY errors sometimes in Open | 169433 | [iwn] iwn(4) doesn't support 6235 chip. Open | 211689 | panic with lagg failover wireless ath and iwm 8 problems total for which you should take action. From owner-freebsd-wireless@freebsd.org Sun Nov 20 22:41:39 2016 Return-Path: Delivered-To: freebsd-wireless@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 D46D7C4CBE2 for ; Sun, 20 Nov 2016 22:41:39 +0000 (UTC) (envelope-from fnoyanisi@yahoo.com) Received: from nm3-vm0.bullet.mail.bf1.yahoo.com (nm3-vm0.bullet.mail.bf1.yahoo.com [98.139.212.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89B691C60 for ; Sun, 20 Nov 2016 22:41:39 +0000 (UTC) (envelope-from fnoyanisi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1479681692; bh=Xv0hEfjPQiEVciTvsex6uSJ2L6eIVLhzSFBGUOOvMNQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=BFSx68RZtLynBEZF+mtJom8aAVblQPf2inbjC/419Ng4VGGfqvw9JAQID34K5KSgANlle12i2CyzsH4BwFe2XWdzFeLli0q7iM9YZoygu/NzmwK7HL/51bbiCHwo4hFzVuVlED6m3YMkHOCSKgx/ckKCGE5iMBVqwTG72SHr49LSNbjM2d2XLSD5tmn+2nyETGZqqfgZHkf+ICe5zT9EoOM4lHaEfT3IdWEgv0QGnDafGUpa/4WALPGxgxKPeLkf9D4Kb70UfywVsbW1RzDsCF9KUR3nozyp5wEXbjK/GHVv+fsq/innmqhuMAFXTrZqJbBTx2T0B4nLHc0FkYhR3Q== Received: from [98.139.215.141] by nm3.bullet.mail.bf1.yahoo.com with NNFMP; 20 Nov 2016 22:41:32 -0000 Received: from [98.139.212.217] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 20 Nov 2016 22:41:32 -0000 Received: from [127.0.0.1] by omp1026.mail.bf1.yahoo.com with NNFMP; 20 Nov 2016 22:41:32 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 199124.53558.bm@omp1026.mail.bf1.yahoo.com X-YMail-OSG: YFsBLsEVM1kBGMmxzD.MQtdEx0UyXbYPNG65DqaE0vzVPq1VeVOTcyHR29FEGaU jE0dY4XFuX04aCc3390gzMIr7J1dwGbEnxzl9jdLZwzt8ODKzMpkQ5wA42wmoTeIDj0RrqBcbzgp Y.Ju2BNCcGX3sYFY0.0V24_bqsmUAbPZjdmYYx2dO2tjjS7LxVlSyxH82S7dBSwKLGGKgDNNVGpp RPIJkxMP3YMDWjf9dWNsw1_FmfH0wgsD.oNZInDaxO6jZcSUDe1wC_csaCs0Sgr4OA5A3RQ52ATf s3GHDJ.1oQIo9zlBWOgDCN23M2XUSwvteynhO2_RiXh.ZYuf9NZ0aWYOnkP5h7S7DwWqPSbuJ2gL .oJ2ULH2kCyu_RLopUDCPx7C7VDgQxbJZdrBJ7n0K7QwArMypb9945jyHd4n_PqGuj3hWSTZMFT4 EqFdoGCDPzKWH4QStyRut1MocDL7fCfKd9FvigDpF0DmFyTtI.BrkpF8pbZnO4qBLVud6e7rruzf vmJzJ3_3dHvfd6Y4opNUsXZM- Received: from jws400060.mail.bf2.yahoo.com by sendmailws136.mail.bf1.yahoo.com; Sun, 20 Nov 2016 22:41:31 +0000; 1479681691.758 Date: Sun, 20 Nov 2016 22:41:18 +0000 (UTC) From: Fehmi Noyan ISI Reply-To: Fehmi Noyan ISI To: Adrian Chadd Cc: Freebsd Wireless Message-ID: <1618804244.754630.1479681678319@mail.yahoo.com> In-Reply-To: References: <980351195.1573665.1479336792289.ref@mail.yahoo.com> <980351195.1573665.1479336792289@mail.yahoo.com> <2112311201.1853303.1479370511602@mail.yahoo.com> <1703426610.2431782.1479426526331@mail.yahoo.com> <456881900.492024.1479629524039@mail.yahoo.com> Subject: Re: Using net80211/IEEE80211_C_BITS macro MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 22:41:39 -0000 Appreciate it! ________________________________ From: Adrian Chadd To: Fehmi Noyan ISI Cc: Freebsd Wireless Sent: Monday, November 21, 2016 7:12 AM Subject: Re: Using net80211/IEEE80211_C_BITS macro I'll try to find someone to back port the wifi bits to stable/11 before they get too problematic. A On Nov 20, 2016 12:12 AM, "Fehmi Noyan ISI" wrote: Thanks Adrian! > >Checked out revision 308871 and compiled the system from source. Had no issues during the built process. > >Also, verified the changes in the source tree > > >Script started on Sun Nov 20 20:59:17 2016 >root@test:~ # grep IEEE80211_C_BITS /usr/src/sbin/ifconfig/* >/usr/src/sbin/ifconfig/ ifieee80211.c: printb("drivercaps", dc->dc_drivercaps, IEEE80211_C_BITS); >root@test:~ # grep IEEE80211_C_BITS /usr/src/sys/net80211/* >/usr/src/sys/net80211/_ ieee80211.h:#define IEEE80211_C_BITS \ >/usr/src/sys/net80211/ ieee80211_ddb.c: db_printf("\tcaps=%b\n", vap->iv_caps, IEEE80211_C_BITS); >/usr/src/sys/net80211/ ieee80211_ddb.c: db_printf("\tcaps=%b\n", ic->ic_caps, IEEE80211_C_BITS); >root@test:~ # exit >exit > > >I used a VM (my only laptop has -RELEASE on it :{ , tried some bhyve trick like iwn passthru but did not succeed), hence could not specifically test "ifconfig wlan0 list caps" but since compilation went smooth, I would assume it should be OK. After all, changes do not constitute any new features or functions. > >Anything on the time frame till we could see this change on -RELEASE branch? > >Thanks > > >----- Original Message ----- >From: Adrian Chadd >To: Fehmi Noyan ISI >Cc: Freebsd Wireless >Sent: Saturday, November 19, 2016 10:12 AM >Subject: Re: Using net80211/IEEE80211_C_BITS macro > >Hi! > >Fixed in the latest -head. Two commits - one for net80211, one for ifconfig! > > > >-a > From owner-freebsd-wireless@freebsd.org Mon Nov 21 22:51:07 2016 Return-Path: Delivered-To: freebsd-wireless@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 2DAA8C4D528 for ; Mon, 21 Nov 2016 22:51:07 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 065321A59 for ; Mon, 21 Nov 2016 22:51:06 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id uALMZLpD027847 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Mon, 21 Nov 2016 14:35:22 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me To: freebsd-wireless From: Yuri Subject: wpa_supplicant + wpa_gui have troubles when many APs have the same name Message-ID: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> Date: Mon, 21 Nov 2016 14:35:20 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2016 22:51:07 -0000 I use wpa_supplicant + wpa_gui and it usually works fine. However, when many APs have the same name it often fails to connect or becomes very clunky. When such network name (with many APs) is left in wpa_supplicant.conf, other networks often fail to connect until the multiple name is removed. Anybody has any insight as of what the problem might be? Yuri From owner-freebsd-wireless@freebsd.org Tue Nov 22 01:53:16 2016 Return-Path: Delivered-To: freebsd-wireless@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 41B5AC4E693 for ; Tue, 22 Nov 2016 01:53:16 +0000 (UTC) (envelope-from fnoyanisi@yahoo.com) Received: from nm13-vm0.bullet.mail.bf1.yahoo.com (nm13-vm0.bullet.mail.bf1.yahoo.com [98.139.213.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF44011BF for ; Tue, 22 Nov 2016 01:53:15 +0000 (UTC) (envelope-from fnoyanisi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1479779594; bh=fEoxUyDYZoN1f7PrYWmfcC+fGVOUmsMEmBnQu4ts/mE=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=ji6eo272I9d7vhJYoVkY4QCYdMYHhLiF6+hiYj/wNX37T4f+1ueoUDijvpvWYijY1+QopClZv37seSj6tzwsvn9wPNgA7bQlnE4n4WkKYZeXXWX9Q9yByhxN9+YesGqPi5hLbBKgGw61IEa6w5X0Jti7eho4r7mRYA/RTkxu2/Uj9rNq/IDXG841QTnHvRE60d0I+wGVQzPonnzt8YPgUKoM5TDiPW6FvVBvSMflB7nlRUMCrb4gS6UDxoIX3rpml2SN/BtEC/oVtnJgH6qliF0HMzBxMXp7RLGZphKRoOHyuI/IpFZt02H5XCOLkz0V3KNiy+0H1dPD2D/YNaQc0w== Received: from [98.139.170.180] by nm13.bullet.mail.bf1.yahoo.com with NNFMP; 22 Nov 2016 01:53:14 -0000 Received: from [98.139.212.236] by tm23.bullet.mail.bf1.yahoo.com with NNFMP; 22 Nov 2016 01:53:14 -0000 Received: from [127.0.0.1] by omp1045.mail.bf1.yahoo.com with NNFMP; 22 Nov 2016 01:53:14 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 158555.99708.bm@omp1045.mail.bf1.yahoo.com X-YMail-OSG: YalJg4YVM1kWFVdac_HeOJeU.PqPE6oQSN5z0.YJ1ORYQXmtQUcXQdzA5TPq177 WBo7WioWQMdLtl6eamDYQdLni9G_xnVxe8OCv4_927qjqYEn6Y52OtJ67xg.Lhi7XNQg4hxsIDI3 Fr06KpAcLS2gYCD24TNHuuZNfgVmI0DSTI4XBTuqPqUzhxJGwqe_G2ouvG854Nfn3hSn8LN4CtIy rQkcSeDfY0FRuuoNmCdB_fs5TX6smGLYcXNodtn6e2VDDSH27J7LsxQLeoxRuYq1COteKTlCInSl 5n0KBx5eD1nzXJ9Lj8NgVqaroFP4_RCRHusBNeLOIehsXFx5th_74abucR3Hb3aIDZxiyFHTNjAP Ph2lyAymUoxK0RRjmC9XKPGR4d0CAr_RAeT.ZvRMueD2wg1ku1paNp0vKYyGGsPIoKc9yeABrWoc LE1IaVUSN6ykqSgKMYQ0hT1EBOTaUXdBr.8IQz1JP80KU0h0tUkdZUwQzwXX6Wt_6N9tMjVK9_SP QtW5PiCokxUuFCKdRzE73LS8e_3XQWkBML9pIo_GX2XrB7oLlU8pcQV8- Received: from jws400081.mail.bf2.yahoo.com by sendmailws162.mail.bf1.yahoo.com; Tue, 22 Nov 2016 01:53:13 +0000; 1479779593.721 Date: Tue, 22 Nov 2016 01:53:06 +0000 (UTC) From: Fehmi Noyan ISI Reply-To: Fehmi Noyan ISI To: Yuri , freebsd-wireless Message-ID: <1983541127.1707358.1479779586520@mail.yahoo.com> In-Reply-To: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> References: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> Subject: Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 01:53:16 -0000 Have you tried adding bssid into wpa_supplicant.conf? https://www.freebsd.org/cgi/man.cgi?wpa_supplicant.conf%285%29 ________________________________ From: Yuri To: freebsd-wireless Sent: Tuesday, November 22, 2016 11:35 AM Subject: wpa_supplicant + wpa_gui have troubles when many APs have the same name I use wpa_supplicant + wpa_gui and it usually works fine. However, when many APs have the same name it often fails to connect or becomes very clunky. When such network name (with many APs) is left in wpa_supplicant.conf, other networks often fail to connect until the multiple name is removed. Anybody has any insight as of what the problem might be? Yuri _______________________________________________ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@freebsd.org Tue Nov 22 01:56:34 2016 Return-Path: Delivered-To: freebsd-wireless@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 4E703C4E829 for ; Tue, 22 Nov 2016 01:56:34 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2564212D2 for ; Tue, 22 Nov 2016 01:56:33 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id uAM1uWwk050135 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 21 Nov 2016 17:56:33 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name To: Fehmi Noyan ISI , freebsd-wireless References: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> <1983541127.1707358.1479779586520@mail.yahoo.com> From: Yuri Message-ID: <3b76a34b-0ac7-dd2e-60f0-e6b0ac811e44@rawbw.com> Date: Mon, 21 Nov 2016 17:56:31 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <1983541127.1707358.1479779586520@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 01:56:34 -0000 On 11/21/2016 17:53, Fehmi Noyan ISI wrote: > Have you tried adding bssid into wpa_supplicant.conf? > > > https://www.freebsd.org/cgi/man.cgi?wpa_supplicant.conf%285%29 With update_config=1 wpa_supplicant does all of this itself based on wpa_gui requests. Yuri From owner-freebsd-wireless@freebsd.org Tue Nov 22 02:01:25 2016 Return-Path: Delivered-To: freebsd-wireless@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 D7A09C4EA55 for ; Tue, 22 Nov 2016 02:01:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 A1EBD1589 for ; Tue, 22 Nov 2016 02:01:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x232.google.com with SMTP id c20so580194itb.0 for ; Mon, 21 Nov 2016 18:01:25 -0800 (PST) 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=2OhpvcWXwl4Ticob1AaP1CFJmyhGgn8g7ekPxzzGGTQ=; b=LKIdksvmJcz9kceEcTwERs0Mp1ijNVGTWyHMVLzo1EAN9qztZkUL6KbBFNqZl04uY3 JvZDI9ldRO41fYgNz/6qe8CcAN1U6qeFW+uNymdhMWqcslYYHW+lkXZ7v6D8cBxgeJ9k fhjRvphlY6QnNLRf2yNu+VMYuy2RzVZDf92ykNhCtxYDs/+eHQjK1llrnwd1VPtlIiDv 1x1yf6dd/XJFTTKpAXRQ7ak1OnPFDx8leNNce51+yYqxljs4XW/KbNpF3oPkZLGuLUf7 BzKuHe0/l6BqvCIq7zbEhH9Wah0eXySzI3JmxsfjMnBjHUuvWPVAFipAmTBKaRbj+cmM kVPA== 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=2OhpvcWXwl4Ticob1AaP1CFJmyhGgn8g7ekPxzzGGTQ=; b=AHUvDP1Kut2rYP5+jFH0b38ExFDFDF6qoW9c2RJ93OMdqnfFRTjR37bHb9t1erx7ML A5tn6/pJ8n2UsICn9PhmNaHAIL4dx0xv96PCjw9xNJ4IQT6pS5gKX/lfidR6EvsiS4Mb vE2TV6tLzdSvfCIVsJJHGXuubIfffaA41UiW1YvEc2U6Mjjnlkt/6puvJRtQ9ynZ50pB 5ZcUE0i8KPH5sODGc8rzYQ3SQ7M3w5k3ud+xpNnDO8iQowCXD0JMxf/dEu/UJ5KfsElr UC/4WHTW3m0FtkrbAR6IJt1Y6vNU8MKT5TBtnVq2j7CcjAKzhs8HheCMISiumdjTbpEM gxqw== X-Gm-Message-State: AKaTC03syV8XKwCm3QXyjL5lkagq4DcgFtv1Enyd2BklQH1l6q2cl8b+mWcRIPjScyWrOwwye7boKljZxM5NOQ== X-Received: by 10.36.91.134 with SMTP id g128mr119430itb.78.1479780085166; Mon, 21 Nov 2016 18:01:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.39.134 with HTTP; Mon, 21 Nov 2016 18:01:24 -0800 (PST) In-Reply-To: <3b76a34b-0ac7-dd2e-60f0-e6b0ac811e44@rawbw.com> References: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> <1983541127.1707358.1479779586520@mail.yahoo.com> <3b76a34b-0ac7-dd2e-60f0-e6b0ac811e44@rawbw.com> From: Adrian Chadd Date: Mon, 21 Nov 2016 18:01:24 -0800 Message-ID: Subject: Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name To: Yuri Cc: Fehmi Noyan ISI , freebsd-wireless Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 02:01:25 -0000 Hi, Is it trying to send out probe requests to ALL of those devices for some reason? How many APs is too many? Maybe I can try duplicating it. -adrian From owner-freebsd-wireless@freebsd.org Tue Nov 22 02:05:15 2016 Return-Path: Delivered-To: freebsd-wireless@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 80AFFC4ED44 for ; Tue, 22 Nov 2016 02:05:15 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6FAE119EA for ; Tue, 22 Nov 2016 02:05:15 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yv.noip.me (c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id uAM25EHN051328 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 21 Nov 2016 18:05:14 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-24-6-186-56.hsd1.ca.comcast.net [24.6.186.56] claimed to be yv.noip.me Subject: Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name To: Adrian Chadd References: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> <1983541127.1707358.1479779586520@mail.yahoo.com> <3b76a34b-0ac7-dd2e-60f0-e6b0ac811e44@rawbw.com> Cc: Fehmi Noyan ISI , freebsd-wireless From: Yuri Message-ID: <7e39e6b6-30a6-9c67-534b-4b8a1b2309e7@rawbw.com> Date: Mon, 21 Nov 2016 18:05:13 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 02:05:15 -0000 On 11/21/2016 18:01, Adrian Chadd wrote: > Hi, > > Is it trying to send out probe requests to ALL of those devices for some reason? > > How many APs is too many? Maybe I can try duplicating it. I didn't debug it. But I observed that the problem occurred in several public places, like airports, conference halls, hotels which attempt to "cover" the space with APs with the same name. Sometimes there were 10-20 APs in sight. Yuri From owner-freebsd-wireless@freebsd.org Tue Nov 22 02:06:25 2016 Return-Path: Delivered-To: freebsd-wireless@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 E5459C4ED96 for ; Tue, 22 Nov 2016 02:06:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 ADB6D1A27 for ; Tue, 22 Nov 2016 02:06:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x232.google.com with SMTP id j65so56438360iof.0 for ; Mon, 21 Nov 2016 18:06:25 -0800 (PST) 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=KlUs5C/JYB3vyIA25EM6HgOWSgeh/5xV7C0c4EGsf2Q=; b=sJDIrYJqstCDPR1sV9Y10rqhs81eIgrYxuAJP/j1M89Azv5KNmRqiQMZWCeSX07HtJ a6NMkmdw3y8H9kNLIn1hSOHPfNL3nz3v0r18oQvO8JGniqx0kH13a5+49LnhD4LuiuDA GBYJccRcHLQrhQYptODX3NMVGNV7YHUj3q2AH9Sb9tsFejFSh0vE0cgvTP4o6gmnvSNL PUUZ9ik6jX3+bIYBtdeUEcHa7MvApaNxvS5R/XZlNp+yfcJoEnWTsqjSrQa/TPurqthG dhECbF7RyVVxOY0Z8zhJiY680v+gTa0dWI6MzyRh3srNgzrxTgu7joncou073B3b6Z0H KGvw== 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=KlUs5C/JYB3vyIA25EM6HgOWSgeh/5xV7C0c4EGsf2Q=; b=Rx86n52lgXkQ2K13Fb70UBjgU85uJelZKc4yoOBy+tDIHsU2ozSReOsDdegUMW8bj/ 5W+CMaX/YNguf4TS4GCC6kp2pK5372FkqV1dE3LiwE65FyalbhTjgKf5tT71N/DJ/Czy sRD4IIhauqFCUxsrtgFNCk0H6yy+WUw3AIc6y2BtD3jCa/HIv1cB2jHFO2b8BYCyzvdJ KBF3YJJoOVhw2GEwTg4RTRvBtBs2M046aIwHEXFntx9+T4XCm9V6ZR6UPGE2rVCy0CDB YYDEFcoTM6gSoIzxx8QO3yjSd8Xbf9W/laNwsYHnjgO0tlIzIdpBSO4vhrn6UK1h5at9 8gFw== X-Gm-Message-State: AKaTC02Z7HlxBgoG+yLraJBi19smqYxQyqYCFOfhbd3qDqRrpL5cDfBFZX8e0CwOzjXw6S+GT4jLyuJ2geoMWw== X-Received: by 10.107.36.144 with SMTP id k138mr14153965iok.177.1479780385199; Mon, 21 Nov 2016 18:06:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.36.39.134 with HTTP; Mon, 21 Nov 2016 18:06:24 -0800 (PST) In-Reply-To: <7e39e6b6-30a6-9c67-534b-4b8a1b2309e7@rawbw.com> References: <264bf419-c97f-a333-167a-5eb13a6bf96a@rawbw.com> <1983541127.1707358.1479779586520@mail.yahoo.com> <3b76a34b-0ac7-dd2e-60f0-e6b0ac811e44@rawbw.com> <7e39e6b6-30a6-9c67-534b-4b8a1b2309e7@rawbw.com> From: Adrian Chadd Date: Mon, 21 Nov 2016 18:06:24 -0800 Message-ID: Subject: Re: wpa_supplicant + wpa_gui have troubles when many APs have the same name To: Yuri Cc: Fehmi Noyan ISI , freebsd-wireless Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 02:06:26 -0000 hi, all on the same band, or on different bands? next time, do this: ifconfig -v wlan0 list scan .. when it's happening. that way I can see how many there are and what they're doing. -a On 21 November 2016 at 18:05, Yuri wrote: > On 11/21/2016 18:01, Adrian Chadd wrote: >> >> Hi, >> >> Is it trying to send out probe requests to ALL of those devices for some >> reason? >> >> How many APs is too many? Maybe I can try duplicating it. > > > I didn't debug it. But I observed that the problem occurred in several > public places, like airports, conference halls, hotels which attempt to > "cover" the space with APs with the same name. Sometimes there were 10-20 > APs in sight. > > Yuri > From owner-freebsd-wireless@freebsd.org Thu Nov 24 02:38:16 2016 Return-Path: Delivered-To: freebsd-wireless@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 732F7C523B5 for ; Thu, 24 Nov 2016 02:38:16 +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 62C628AA for ; Thu, 24 Nov 2016 02:38:16 +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 uAO2cGaU060624 for ; Thu, 24 Nov 2016 02:38:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-wireless@FreeBSD.org Subject: [Bug 214264] iwn regression on 11.0 (Centrino Wireless-N 2230) Date: Thu, 24 Nov 2016 02:38:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: scf@FreeBSD.org 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: In-Reply-To: References: 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-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 02:38:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214264 Sean Farley changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scf@FreeBSD.org --- Comment #1 from Sean Farley --- I was getting the same although WiFi was not working for more than a few seconds. I ran across Bug 214266 which held the solution (for me :)). With lagg, I had the MAC of the wireless NIC set to the same as the wired N= IC.=20 This was causing something to trip. I just needed to change where I set it. From: ifconfig_iwn0=3D"ether aa:bb:cc:dd:ee:ff" ifconfig_wlan0=3D"WPA" To: ifconfig_wlan0=3D"ether aa:bb:cc:dd:ee:ff WPA" Since the actual wireless NIC's are no longer visible except via the wlan interface, ifconfig_iwn0 is no longer valid. I had missed that configurati= on change myself. Hopefully, that is your issue too. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-wireless@freebsd.org Fri Nov 25 19:33:26 2016 Return-Path: Delivered-To: freebsd-wireless@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 1D6C6C54FE5 for ; Fri, 25 Nov 2016 19:33:26 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (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 DED4E3E3 for ; Fri, 25 Nov 2016 19:33:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id j65so138938930iof.0 for ; Fri, 25 Nov 2016 11:33:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to; bh=qcWRY/0PI3AFFEkB3khmVensqF5LRBaTJnUbkHezTXA=; b=Ha/nKGQXJFPuCnfuFmv8yZoZkxj+HZEu7FjjqkD3Ue0WSNJt2yOgvejMaigmbvSyzr 4d1s0F2RVNkZpk8eKiZ/iS8pBpgdEp+V/N3EjvKybSbxxZZJ403uQ7dY6LCCre1etygR 5lvwewgJJltybI2bvemlSCeZyjg2I0VNYaf2WZ0pmS7ynra1uLyVB+OqmM2yWiOe3lXE qfTlDh3my5v1RHmo0tqg3j0u7KbPZ8oQUUACIBa5I542QWdBgBHszkwZd+IoywTP8ibA Aj/70yWZioFkHaXyiWmW5MaBizenosA1toh6bCa/H6O6JIfEgNE1zBJa3xFw63nS69YW nb7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=qcWRY/0PI3AFFEkB3khmVensqF5LRBaTJnUbkHezTXA=; b=k0ieRrwR3aw6GGeTVTHhYg5X+ot50AH3ybVMvjyA53LS7LLcylDfSlfgdLfwcCzk6/ Cj4ziUlYcvkLjR7oS5vo3KnEf/B8iYtab+G3ZB8xQw8ke1zo3o5sG3wblfeWq57WnWDB PW0aW6BBrAXmA8D/NEQt2KDhRPEOILwjobC4cjr2S0Bulkb1Q8MJmF3JOfP/N1uordFF j3PSWPFZF0IwuDZN0qdTT/1FPdjteKFMAHDEp2nnUuGv1Zb7IW5vIFObAHfqpeYdZlPS lwJdvUbsgherCE/pg3t8q0u2yZDK3YHzdOZ1zxVJ5J9yEexVsjq2m8BIPOBWTpRIaq7X xXpQ== X-Gm-Message-State: AKaTC023H0BSA8FxXAwImve1SzQ4MES2W6CTkjue7wJsDD7pOLmZ7TuZ7F91aDo7bbLRXoh4ct2PJxbgjLFs/A== X-Received: by 10.107.136.86 with SMTP id k83mr7813841iod.99.1480102405030; Fri, 25 Nov 2016 11:33:25 -0800 (PST) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.39.134 with HTTP; Fri, 25 Nov 2016 11:33:24 -0800 (PST) From: Adrian Chadd Date: Fri, 25 Nov 2016 11:33:24 -0800 X-Google-Sender-Auth: 5nZ03dggZobHGcGyAyf4Jpe90Lg Message-ID: Subject: radiotap 802.11 change? To: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 19:33:26 -0000 hiya, I've noticed something weird lately - it seems wlan radiotap (both 802.3 and 802.11 radiotap sessions) are now doubling up on RX'ed frames. Has anyone seen this? -adrian From owner-freebsd-wireless@freebsd.org Fri Nov 25 21:47:40 2016 Return-Path: Delivered-To: freebsd-wireless@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 6A90AC5524B for ; Fri, 25 Nov 2016 21:47:40 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 093BF13C; Fri, 25 Nov 2016 21:47:40 +0000 (UTC) (envelope-from s3erios@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id b14so58487664lfg.2; Fri, 25 Nov 2016 13:47:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=nVWZtvidw3UMrERRgybRGdrMHLyb34/Ruh6aObvRDwU=; b=DdR3Wzt4W+RzfFjeNEufyJ2QoK6RXR0kmXFWtDYkjC1KAHhodcOxJSkkxrwPU8o2ko sYxzqQCxDRSJDe9SBx8lr2EnxUeVx5o2fZVmb6A19H/GTboy2w/frSd5XmNZoMgGeXix y2R1WV90lLyYCX2MeDgEYino0O7hQpc0CD4TbXgBCg5BUj8nKBwLukI1TC2TJ0NTTGQt xYjZmbHUBchCH3xjXVE86dL0RghLfTw73bN2kG1mYHj6FqfTUdiCLk/fuFvLDNl21W0W xayJe21TwNlrdlXL6YhjpTcHiSipf7uSQTbciUfeWGhObYcL0F4HbfR2XAXJh816yh+z eiIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to:user-agent; bh=nVWZtvidw3UMrERRgybRGdrMHLyb34/Ruh6aObvRDwU=; b=nKgJ44AOZhR8hEWxoCb7aLEEDCU/20DNp48+DSzq8mspqOMFuZQvW30DmpVuZKbzd+ a3k2OXnQN5/jjurBL8hAIAUCInEUihH1qxrTYf+2OOMHKpMFVLawC9ucksUm9OSx1fm4 mDabzoVKbjfNzibYuow8T2dO3D7ix3/weDSIUTI/flz03NA/QrfO40QGqC75IXGtuCF8 wKq351ozje4AaokMWqEQ1JDW4e4ynqG0FJQNKTsOZrr6pbT/oUP78jNLcMy5V711A/Vc 4x7F1ONnKv9ZLEBCOkGQ4ZzS5BmqNDtL6U3H1gqEd8ogKpVyy3eYDIjIeHHnrgd3f6a6 BZ7A== X-Gm-Message-State: AKaTC00DcWWEiY1Y63Msn9uMNM596W7bx8uvH4yUEhDF5giyq0cDy64ZbPI6ztjleq0J5A== X-Received: by 10.25.201.129 with SMTP id z123mr4180138lff.6.1480110457809; Fri, 25 Nov 2016 13:47:37 -0800 (PST) Received: from localhost (host-176-37-109-22.la.net.ua. [176.37.109.22]) by smtp.gmail.com with ESMTPSA id z2sm9754252lja.10.2016.11.25.13.47.36 (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 25 Nov 2016 13:47:37 -0800 (PST) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Adrian Chadd" Subject: Re: radiotap 802.11 change? References: Date: Fri, 25 Nov 2016 23:47:40 +0200 Cc: "freebsd-wireless@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Andriy Voskoboinyk" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2016 21:47:40 -0000 Fri, 25 Nov 2016 21:33:24 +0200 =D0=B1=D1=83=D0=BB=D0=BE =D0=BD=D0=B0=D0= =BF=D0=B8=D1=81=D0=B0=D0=BD=D0=BE Adrian Chadd = : 12.0-CURRENT (r308862), rtwn(4) (RTL8188CE), wireshark v2.0.5, = non-promiscuous mode: 1) beacon from the AP, 127 bytes: - radiotap header len: 24 bytes (correct); - frame header len: 24 bytes - fixed params: 12 bytes - tagged params: 67 bytes 2) discarded (duplicate) data frame, 1524 bytes: - radiotap header len: 24 bytes - frame header len (+ EIV): 32 bytes - data: 1468 bytes > hiya, > > I've noticed something weird lately - it seems wlan radiotap (both > 802.3 and 802.11 radiotap sessions) are now doubling up on RX'ed > frames. > > Has anyone seen this? > > > -adrian > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to = > "freebsd-wireless-unsubscribe@freebsd.org"