From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [IPv6:2001:470:dc45:1000::1]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id DE50B3B29E for ; Tue, 24 Apr 2018 07:54:32 -0400 (EDT) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1524570871; bh=1/o69Vk+/T/viTlhA3Du9o8WXWFmz7N4sEPuvMb8LnA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=gO9iGK0fzTybmLG3ku8Ayez6Acx3aVdrPhG3L1PWDZTIaZVtNDUreJXcufrQjHBzX p94MpkglizATCMmV7GJArIF3G7f68Qha0ABBKxJqYhq0jZyUFOxMejvze9ntyiswGl H9lhpZQ9sv0I+76SvQMgDuDZDRmIckwc2ALvbvHIEbJc9OSrwvApiJ0Xu4fHdb8Yc3 /LuyS02RKwicQKc+ms/QNLTUunC/HDob1hsPoqEIGRX8ZLI3w+MWjNJwhJ0Tq7uyOi IXAWpIMM59ampqox51evXkWACsPhK0HOG1umezs137/AEDYvsf9KpT7nF5hwSlFlPB wkKeoUqOI+gZA== To: Pete Heist , make-wifi-fast@lists.bufferbloat.net In-Reply-To: <66BDCA6E-D7C4-4E76-8591-8FDC35B09EA3@eventide.io> References: <66BDCA6E-D7C4-4E76-8591-8FDC35B09EA3@eventide.io> Date: Tue, 24 Apr 2018 13:54:31 +0200 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <871sf495vs.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] mesh deployment with ath9k driver changes X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 11:54:33 -0000 Pete Heist writes: > I have a 7 node (3 of which are repeaters) mesh deployed at a campground = using Open Mesh=E2=80=99s 6.4 beta (with LEDE and the ath9k changes). I set= up an internal SmokePing instance with each AP as a target, and the first = guests of the season are arriving (school kids, the best testers). The setu= p for our three repeaters is: > > Cabin 12: 110 meters and RSSI -69 to gateway, NLOS through a few leaves > Cabin 20: 65 meters and RSSI -66 to gateway, LOS but maybe some fresnel z= one intrusion from leaves or branches > Cabin 28: 50 meters and RSSI -51 to gateway, clear LOS > > Attached are some PDFs of the current SmokePing results. The school > arrived Monday morning and are mostly clustered around cabins 12 and > 20, with a few around cabin 28, can you tell? :) Mean ping time for > cabin 12 is around 200 ms during =E2=80=9Cactive use=E2=80=9D, with outli= ers above 1 > second, which is higher than expected. I don=E2=80=99t have data collecte= d on > how many active users that is and what they=E2=80=99re doing, but there c= ould > be 40-50 students around the cabin 12 AP, with however many active "as > is typical for kids=E2=80=9D. Hmm, yeah, 200ms seems quite high. Are there excessive collisions and retransmissions? Is the uplink on the same frequency as the clients? > Overall it would be nice to know, in a typical real-world setup, how > much is WiFi latency is due to bufferbloat, and how much to the > physical layer? On ath9k bufferbloat should be more than 10-20ms or so. > Lastly, is there any interest in access to SmokePing results, or other > diagnostics? Things are bound to get interesting as the season > progresses=E2=80=A6 Sure, feel free to keep us updated! :) -Toke