From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 7AC6B3CB48 for ; Fri, 12 Jan 2018 07:33:28 -0500 (EST) 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=1515760406; bh=2273Srnb5fwX5wlbNZqKuUqtT2VltbxpBsz9tpE7LW0=; h=From:To:Subject:Date:From; b=CDIdkZucsOu3gX3ZdI/HcO0hLDaMyztGhkQmUjECzHGtj/zTfqG6QGzIV0Gi6jZwi Oy3tK8M+T4BNtu05Zn2WJyaORmUuo5ruBZg+vr4AeP81aWHWhbSXyqyQj79o3Ymlc+ RJOQUfkekfA6mPK7MQb3GQRUp/TmRDBWFKzAoHmR45xmtsrtvWmxWgpGtoYCGj0M8O 7sTo6CN9wpSl3hd2ozJs9Qb3fmfR3hHL8RIBgU6FLulL1UdBQnHYU8jDP2LRh0gSXW 4NvxNaQHTvmBSAzGNMFT0l8F3izJTpDsu05tZFsoEoSDukEgPt2U//6QFg4kqu4KIK vwEDzb6UNPjeQ== To: make-wifi-fast@lists.bufferbloat.net Date: Fri, 12 Jan 2018 13:33:25 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87o9lzqmsq.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: [Make-wifi-fast] Estimating WiFi congestion using different-prio pings 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: Fri, 12 Jan 2018 12:33:28 -0000 Some people over at Skype have implemented a technique for a client to estimate congestion at the WiFi AP by pinging the AP at VO and BE priority and measuring the difference in response times. Pretty neat, except that it would presumably break if the AP was FQ-CoDel-enabled... Paper here, including a description of the bandwidth estimation stuff they apply to Skype based on the information: https://dl.acm.org/citation.cfm?doid=3143361.3143390 -Toke