From owner-freebsd-wireless@FreeBSD.ORG Sat Jun 20 15:00:43 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 451B3A80 for ; Sat, 20 Jun 2015 15:00:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (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 0E5AE262 for ; Sat, 20 Jun 2015 15:00:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iecrd14 with SMTP id rd14so91247689iec.3 for ; Sat, 20 Jun 2015 08:00:42 -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:content-type; bh=QvCpIHt5LdDZwXX62vK+n53HUQWsOec0L6riUeSBtFc=; b=iruCqPgFKjQyrsqoLPX1KLVj5pXKbajSdf7FSB5uFkUFd6IZJ+p9KNt2QR6vjGxgux qE8b/mClSMdnR6N3UVTtguAh3/T76G2ESX1UsajIFjqb8AvodNewXwBBFPTNFgmlfIX8 Kgyp157Xw2MMgoP5xLD0gYKamD1kefp+Vn1IvD3/+0InVIVmAcBd/vv9L57TiRQXrgm8 c6m1kLSorI2bo17/m1LgvmDPhP/hGKYH+jCTA7VLcRu3wFJ6sdYIvqyplgNWRKWssTNh Hzz5z3FvrP4gZoLIC8nXiUD64oG6gBwLfY6ST58qkUmdygI4uU7zUOSSTeQ6xd1dJn8H Ia5w== MIME-Version: 1.0 X-Received: by 10.107.164.70 with SMTP id n67mr28791875ioe.8.1434812442318; Sat, 20 Jun 2015 08:00:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.38.133 with HTTP; Sat, 20 Jun 2015 08:00:42 -0700 (PDT) In-Reply-To: <55846575.8000501@yahoo.com> References: <716422696.1187863.1434616682661.JavaMail.yahoo@mail.yahoo.com> <55846575.8000501@yahoo.com> Date: Sat, 20 Jun 2015 11:00:42 -0400 X-Google-Sender-Auth: zOHjksZff6TdyxH_6pZITBo8e2o Message-ID: Subject: Re: trouble connecting to wifi From: Adrian Chadd To: Zsolt SZASZ , "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Sat, 20 Jun 2015 15:00:43 -0000 Hi, yes - this'll hurt performance, but I'm more interested in whether disabling ampdutx affects performance/stability. If disabling AMPDU TX (but leaving AMPDU RX enabled) reduces the instability/stuck beacons then I have more useful information. -adrian On 19 June 2015 at 14:54, Zsolt SZASZ wrote: > Hi, > > * dev.ath.0.hal.force_full_reset=1 <- its already setup, this is nothing to > do with the ability to connect with my devices to the wifi, but it helps me > to have a smoother download - without this I have interruptions (spikes) > when I download - so its a good thing. > > Then I tried: > # ifconfig ath0_wlan0 -ampdutx but it hurts my download speeds. Without this > I achieve download speeds like 15-17MB/sec but when this is active I've got > only 3MB/sec. Also, I don't know if my wifi is stable with this setting on, > I need more days to check :) > > > > On 6/18/2015 4:12 PM, Adrian Chadd wrote: >> >> 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 >>> home router which contains a PCI slot wireless adapter with Atheros 9227 >>> chipset. The model of the wireless adapter is TP-Link TL-WN51ND and it has >>> two antennas. This comply with IEEE 802.11n, and provides wireless speed up >>> to 300Mbps 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 nobody >>> is using channel 3. With this settings the wifi is working fine one or two >>> days but after that I have to do something like "ifconfig ath0 down | >>> ifconfig 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 perfectly 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 >>> down/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=1 ; 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 > >