From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 25 19:16:13 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50F47106566C; Sun, 25 Mar 2012 19:16:13 +0000 (UTC) (envelope-from lytboris@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id B07748FC14; Sun, 25 Mar 2012 19:16:12 +0000 (UTC) Received: by wibhj6 with SMTP id hj6so2953024wib.13 for ; Sun, 25 Mar 2012 12:16:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9QI/7Raj/SHiiDC1tHhgIxfCddZ9LzzJLAwZK+nQ+7g=; b=s6NwevjbDQjTw2kmhKUSmMauWEd1kkXa4mQB0bbDE7u/E21J9LK0hKuGKe5Wvl8zXD x4EM7mq4j6J1V9DI8BQvT5llHN5HqjJ0BkrkaGLmNjC/kjnBvNLdeR3O5OYLzrV1OHBD A1Z7vxXz6sLEQM1jAu6Y8VyrN0iqoLz8+lX36PIhLSeNa+EuZ7bD4+W4HnnH7zDiZHPk Qc/nRpFAIBnZQWB3y42la0NZt3bM3dfIglTymegcdmAGQ+QxW31lbBclKWLFjuhQXGli BQ7K509Llo7QHE64A0wSPYHTKkzO2f/W0usG7YeHM5GmfTOVrqpwNDGyeP09qeVbh60D FaKw== MIME-Version: 1.0 Received: by 10.216.144.138 with SMTP id n10mr10906465wej.56.1332702966220; Sun, 25 Mar 2012 12:16:06 -0700 (PDT) Received: by 10.223.72.6 with HTTP; Sun, 25 Mar 2012 12:16:06 -0700 (PDT) In-Reply-To: <4f6f67a7.4a0c440a.3941.ffffc865@mx.google.com> References: <4f6f67a7.4a0c440a.3941.ffffc865@mx.google.com> Date: Sun, 25 Mar 2012 23:16:06 +0400 Message-ID: From: Lytochkin Boris To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" Subject: Re: [ath][CURRENT] Triangle-shaped network performance X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Mar 2012 19:16:13 -0000 On Sun, Mar 25, 2012 at 10:44 PM, Adrian Chadd wrote: > Hi, > > The LOR is known. I'd love to fix it but I have other things to do first. > > Try running athstats 1 and watch the rate of errors change over time. Here it is. input output altrate short long xretry crcerr crypt phyerr rssi rate 44332 38318 20 0 14735 1813 1536 0 0 60 MCS11 39 41 0 0 2 0 0 0 0 69 MCS11 32 64 0 0 21 3 0 0 0 53 MCS11 38 66 0 0 4 0 0 0 0 64 MCS11 37 40 0 0 14 2 0 0 0 60 MCS6 28 32 0 0 1 0 0 0 0 56 MCS11 34 46 0 0 1 0 1 0 0 51 MCS0 44 37 0 0 18 3 0 0 0 64 MCS11 32 61 0 0 4 0 0 0 0 62 MCS11 41 60 0 0 20 3 1 0 0 66 MCS11 45 54 0 0 7 0 0 0 0 59 MCS6 43 64 0 0 20 2 0 0 0 65 MCS11 Somewere in the middle triangle-shaped ping reset (timed out and then rolled over) > > Disable HT40 as on ongested channels it's going to behave very oddly. That does not help always. 5 minutes ago I had the same triangles on ~>ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether b0:48:7a:da:0e:59 inet6 fe80::b248:7aff:feda:e59%wlan0 prefixlen 64 tentative scopeid 0x10 inet 192.168.2.1 netmask 0xffffff00 broadcast 192.168.2.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid starlink channel 13 (2472 MHz 11g ht/20) bssid b0:48:7a:da:0e:59 regdomain ETSI country RU indoor ecm authmode WPA privacy MIXED deftxkey 3 AES-CCM 2:128-bit AES-CCM 3:128-bit txpower 50 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 -dfs bintval 1000 (the moment I took athstats snapshot shown in this mail). Some more observations: it can be cured temporarily fetching some data though wireless: first it will start at 10kb/s than in a minute or something triggers and both speed goes up and pings are sane. If transfer is stopped triangles come in 5-10 seconds after transfer abort. Here it is some kind of diagram of such behavior (reproducible), 1 ping per second: Reply from 192.168.1.5: bytes=32 RTT=297ms TTL=64 <-- transfer started, speed 10kb/s Reply from 192.168.1.5: bytes=32 RTT=318ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=340ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=360ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=388ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=410ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=434ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=457ms TTL=64 Timeout. Reply from 192.168.1.5: bytes=32 RTT=35ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=58ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=78ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=101ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=123ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=147ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=173ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=195ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=217ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=237ms TTL=64 Timeout. Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 <-- speed goes to normal Reply from 192.168.1.5: bytes=32 RTT=3ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=2ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=4ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=3ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=2ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=3ms TTL=64 <-- transfer aborted Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=2ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT<1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=1ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=299ms TTL=64 <-- triangles again! Reply from 192.168.1.5: bytes=32 RTT=322ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=345ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=368ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=390ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=413ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=436ms TTL=64 Timeout. Reply from 192.168.1.5: bytes=32 RTT=34ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=57ms TTL=64 Reply from 192.168.1.5: bytes=32 RTT=80ms TTL=64 -- Boris Lytochkin