From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 20 19:29:29 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 4627BAC5; Wed, 20 Aug 2014 19:29:29 +0000 (UTC) Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA5F13CB0; Wed, 20 Aug 2014 19:29:28 +0000 (UTC) Received: by mail-qc0-f179.google.com with SMTP id m20so8347507qcx.10 for ; Wed, 20 Aug 2014 12:29:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nlQ+5Df5ANHHwon8UQNIgklkQDck2rOhaRKPNLt7hKU=; b=Ds1ZkGgDXH9LMo+uWMR3kQiZyBBtMN/KTi264GIlS9i6eyi8sFozNz4KAyPNrDuF0q teKCOKLbcMDfLlbqu54IgC5yyukuLD5WVD6J6iSt8l6jpSCl4U692PipuZmsf9OhqeMD WqFUYG1rN4owSeSi83nPaj+R5LZhzsBMPfMzwDw2kxKeuxTrWHjeEbvteC8pmxFTB43K 1fTF3nu8OidC7YMWT89wMYeJDrgL8goKWvb6bwnj7QUbFJnCDwYsN223q4HAu1EAnc83 DAo/w1LH6EzXGBoUaGjjmGXZnHfWZb3udIRwvotf81GQEy1728HATZsSbp2UZnMrPE94 8l6g== MIME-Version: 1.0 X-Received: by 10.224.75.73 with SMTP id x9mr43697927qaj.63.1408562967804; Wed, 20 Aug 2014 12:29:27 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.39.139 with HTTP; Wed, 20 Aug 2014 12:29:27 -0700 (PDT) In-Reply-To: References: Date: Wed, 20 Aug 2014 12:29:27 -0700 X-Google-Sender-Auth: dbJH5Sc362_1lGJvg5mTktnb6Go Message-ID: Subject: Re: FreeBSD current RT3071 can't connect to 5G network From: Adrian Chadd To: PseudoCylon 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 19:29:29 -0000 Are you seeing RX CRC errors for all rates? CCK? OFDM? HT? At all distances? 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.) -a