From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 23:34:05 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 13EE8C8 for ; Wed, 20 Aug 2014 23:34:05 +0000 (UTC) Received: from nm14-vm0.bullet.mail.bf1.yahoo.com (nm14-vm0.bullet.mail.bf1.yahoo.com [98.139.213.164]) by mx1.freebsd.org (Postfix) with ESMTP id A316233E3 for ; Wed, 20 Aug 2014 23:34:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s2048; t=1408577637; bh=wn+zq/yUns5CLNYtH7t1IYoEqiTsuMz/XNfPL5I7qZo=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type:From:Subject; b=hBRzfzpkiQnLYis/N0Sp6zzUCKD9a/9HPnGgFoIB/oyb24Wnrz12v/Prbo93+Zv6f8zxUVhg821lnw8DsxoIfU8oVjCXTzseG8JVRArK4Ad9WBJWEKlpA6aoAmKoKrxORX7w869Oir0opnpvS0O29BzS/z9MOTl3YN4tuof91WGVhjt8SLrV6h4oH3GRoMokOSUtsGusjpe0YLg40Zy3/WNHUUlSxS1P/uy6Esg1UwpkFJ6LII5+lY2/p4KUI2FWj4ovEhHjVbcil7e30ywE3aPa20/3e5UMJurFjNCj/eIjkEpkz3Rwh2JRg1DioTPT3SvXjuxlB7bVlEpH6G+oSA== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.ca; b=swtHo38kmJg5pG0VUTVQik2N+3GQYSw7w+xH3+zJc4isaD5BMQrKA1HWILtA1GV2JUgWlbwgFRGYW8OtHl64kvElnbrxT0RzL5TC4L2A6CBSciCbrh8LL2HpSgQVh5BNKSTbMBCyCbh62XCJFOV0Krk2UTjP+7M6wr4bKhQNqjlkcvuDU9WiGTI6sn6yhtAHtrFM49AhRumpORuYy6wOP2YPiaEu2DbyuhYB2gO9W/Otxm2TWoUjHFuHAjxyUDZxhWJ/oRAvQNFkNfwntOLXTaeuaF631SitNByLGoa/ttted5tTznxYy5r07uNs+kiz+YbahDF8YvPmMB5OJL0Eww==; Received: from [98.139.215.140] by nm14.bullet.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 23:33:57 -0000 Received: from [68.142.230.77] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 23:33:57 -0000 Received: from [127.0.0.1] by smtp234.mail.bf1.yahoo.com with NNFMP; 20 Aug 2014 23:33:57 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1408577637; bh=wn+zq/yUns5CLNYtH7t1IYoEqiTsuMz/XNfPL5I7qZo=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:MIME-Version:X-Received:Received:In-Reply-To:References:Date:Message-ID:Subject:From:To:Cc:Content-Type; b=wjYPLprxrt1nnVdv8KNR/CTOseKU+9O7jM7/bB1pIUIR4Mu/WmA1vil2RZxZxoOU+cFDgiP/0zCw+aPN6ezYwGGfAjdgeivzH27iKxtYns8x83mGJV0qFFY0LFfTiXXkwDgS7pFM/cn5blvBFbOg+9SaZjNZf4kV4UKNrDiQl0w= X-Yahoo-Newman-Id: 17487.32792.bm@smtp234.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: pSm.02kVM1nyL9vbsnxQ_bCwgvtcCtabGVjslHCLDwYmss0 1UKIirGh88gVQLJArK0tYdo0TN5zeUDRgKqNqQS8eSRCsfIIM3IGFTs7Hl8y 9Cd5D3_SF2EHbulB0hMhnPFMwbH.J4rPelCQJEBevYGbYpeUc2OPTI2SGdhf fc4xlH2bGh3juU8ZnV7sGY3.BIXppirHTk8.N77gPQbZjvTfVcl9EoYywytX NxNnrR12RmPZajwIwxEgpXQRi7jPaUQXfuHmKBdtqlhWh6FYCQf4BYG3k7G. 5XLQVQYX9K0q0KnVtNdsHTJqsXSvjJFSybJNo3ieWHDTo4uWd_TP8bDwikI7 6RMQK2vr6TP7bDnEQvyHdVOtskTtZLgs28TxcnsWbVxQ_Tt62BCQQEnMR8iX XaTCWZBUy75P7uYUbcv62ITbYznHmCobX406bk77RXCl6GqPR1KWahgc9ige CcFZ9hoL9JtNJyFuDzhWz0NTbhkDCaQDlwmzacpsNcj_PlyohocSCRvpTNmA 6b38bIHo6dH_kYVtsNnsP2ra92K7w8oFDmEdgkMV0 X-Yahoo-SMTP: Xr6qjFWswBAEmd20sAvB4Q3keqXvXsIH9TjJ Received: by mail-la0-f48.google.com with SMTP id gl10so7671309lab.7 for ; Wed, 20 Aug 2014 16:33:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.27.134 with SMTP id t6mr36275060lag.56.1408577633007; Wed, 20 Aug 2014 16:33:53 -0700 (PDT) Received: by 10.112.230.9 with HTTP; Wed, 20 Aug 2014 16:33:52 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 17:33:52 -0600 Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: PseudoCylon To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 Cc: Kevin Lo , "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 20 Aug 2014 23:34:05 -0000 On Wed, Aug 20, 2014 at 1:29 PM, Adrian Chadd wrote: > Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? CCK not sure, OFDM and HT yes. And at wide range of distances. (Tx rates usually hit mcs 12 to 14 with 2s ht20 ap) > > There's a handful of things we can look at to see what's causing it > once some more digging is done. > > (Eg, HT? could be guard interval. OFDM has similar issues, there's > typically ways to configure how much time between each symbol is left > before transmitting the next one. It may not be doing CTS-to-self, or > it may not be advertising the right thing via NAV, or it may be > ignoring CCK, or the receive gain tables are all messed up, etc.) I have looked into stuff I was able to dig out from other src codes, ie protection, ifs, nav, bk slot. (Because I do not have datasheet, every thing is based on my guesses.) One thing I could not figure out is if on-chip memory is properly allocated for rx pkt. (It seems memory can be allocated for different things, ie beacon, enc keys). > > > -a