From owner-freebsd-wireless@FreeBSD.ORG Thu Jun 18 13:12:01 2015 Return-Path: Delivered-To: freebsd-wireless@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94594868 for ; Thu, 18 Jun 2015 13:12:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (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 5D9EF9C5 for ; Thu, 18 Jun 2015 13:12:01 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igblz2 with SMTP id lz2so59117993igb.1 for ; Thu, 18 Jun 2015 06:12:00 -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:content-transfer-encoding; bh=1omzmqq76U7qq52mBvbGkmaum+Odys40QOB0SyzXWIo=; b=YNaWqIUkdiprjfRaXqtMN7IyHdqzLqwST8QqZed452Vpk9pm5wgll3jGCPIjxboCnq lAvRaWb7TEUhFxjA9hbodJrGMj9Yn+fQXmhf5f+9PhJL+SZf1U5buz24sQ1fziiSiG8K SQnskZtRBU8IDImU+pB4gUSoyS//kS0tujlfS/mGMIG19N2CEldVy8pBxAjqPtk0JJh6 +60Ms9prZ5yg1hAMl64Dn25i/8EMaUet1AvLL2QU5Ru6KLlmypzYl+Bw/ecMyws9W55g Iqa/kIFFYkCocGvu+Oaue/mLELLsO/iDf4dXOuiv2JZwUnsx06bBUPCRm52JSOOnbM6e e4MQ== MIME-Version: 1.0 X-Received: by 10.42.176.8 with SMTP id bc8mr5725872icb.22.1434633120674; Thu, 18 Jun 2015 06:12:00 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Thu, 18 Jun 2015 06:12:00 -0700 (PDT) In-Reply-To: <716422696.1187863.1434616682661.JavaMail.yahoo@mail.yahoo.com> References: <716422696.1187863.1434616682661.JavaMail.yahoo@mail.yahoo.com> Date: Thu, 18 Jun 2015 06:12:00 -0700 X-Google-Sender-Auth: 91s4LbtMYle1E7X79GxNf-6Msmo Message-ID: Subject: Re: trouble connecting to wifi From: Adrian Chadd To: zsolty szasz Cc: "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.20 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, 18 Jun 2015 13:12:01 -0000 On 18 June 2015 at 01:38, zsolty szasz via freebsd-wireless wrote: > Hi, > > I am using pfsense 2.2.2 at home. I have a computer dedicated to be a hom= e router which contains a PCI slot wireless adapter with Atheros 9227 chips= et. The model of the wireless adapter is TP-Link TL-WN51ND and it has two a= ntennas. This comply with IEEE 802.11n, and provides wireless speed up to 3= 00Mbps according to the manufacturer. > This adapter was recognized well by pfsense and I have setup with ease in= "N" using channel 3 - I live in a crowded neighborhood and I saw that nobo= dy is using channel 3. With this settings the wifi is working fine one or t= wo days but after that I have to do something like "ifconfig ath0 down | if= config ath0 up" to work again a couple of days more. The issue is that from= my laptop or phones I can see my wifi but I cant connect. I also receive a= lot of "ath0 stuck beacon resetting" messages in pfsense. For a couple of = weeks I changed back to "G" mode to see if its stable and its working perfe= ctly stable with no ath0 stuck beacon messages at all! > I really would like to use in "N" because of greater download speeds but = I'm lazy to go every time in front of the router and type ifconfig ath0 dow= n/up every time. So please advise me what can I do, or check or setup. > Kind regards, Hi, So: * Set dev.ath.0.hal.force_full_reset=3D1 ; see if that helps * Since 11n is not working but 11g does, it may be something to do with using 11n features. 11n is always /configured/ in the NIC. So, try doing this: # ifconfig wlan0 -ampdutx .. to disable AMPDU transmit. See if that makes it behave differently. -adrian