From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 276AB3B2A0 for ; Mon, 31 Oct 2016 13:18:55 -0400 (EDT) Received: by mail-wm0-x233.google.com with SMTP id a197so33031278wmd.0 for ; Mon, 31 Oct 2016 10:18:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:subject:message-id:date:to:mime-version; bh=0APRZSbMgZMBH0xbArvBh2aS9QORx8QzUY55SgdqsfY=; b=bnIl0qQesp3nwUjc8r+iF3k39PvajVQkCX+pdRSwbpNjE0vwlg740HvbK0rX3qLqz2 zAuXAI8TeD27eHGdmZXPF/Rb8WOdIQeFLKk4LVCDzn26axVuc6M4GYgyyb8TUc3reT0W gnZz4LnBGYwRAxhrIsoJCrveipjXuz9D4j1ILRLe6De8up8+D17haVuI4yMzQXAf5ceW Kt4FEL4OyK0tSK8dMUGOVgppodI+t72nqDl1Q4tOCGjrKA/M5xtWD/rPFfDF7sdtWmMg JHvS2PigFRhFAE5keGSro7XWOtCPA4zTAnscOjE3nHBsKaJJbD8GjN4w+S/tZScca1VF mpBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:message-id:date:to:mime-version; bh=0APRZSbMgZMBH0xbArvBh2aS9QORx8QzUY55SgdqsfY=; b=c582FFBPtSpGWWw8zRDrG44j5Mk5AtByPmJFot3x0L6Q47C2aj8ndOvOTPUILAiT/u IX3fu6+mIN2P7AanVoHiPIZya6TbkPUxf/EVCxA3OtPf4yrL29LlnkcldtEtVMsso/hu JvJIHIAeX/PrY4N+A1U6mgD1P+GQswl+lfgeY36TqNoD+uGp7S3H7tMCkaNMzlkHWT7H UuaRZ3iE8s/3Xr2F+Dl0R8oyrzDY8ooGnpwkQo5Om+VSXF0q7wqHH6PDq1xUW1YpT7Qe rG/UFxRz8iS9Zej9pFaYvOA2NU8n8atb9wJkNsqjxFZ/66F2BR+pBXK4zrBhNsVIVtqK QpJA== X-Gm-Message-State: ABUngvenEmYgFEKDzdw7FRVfrgiUWsJ/b8B1sygpbqZQxM+pB+BlwBrTpJAp5DP6npwm5g== X-Received: by 10.194.59.98 with SMTP id y2mr3189092wjq.166.1477934333635; Mon, 31 Oct 2016 10:18:53 -0700 (PDT) Received: from [10.72.0.20] (h-1169.lbcfree.net. [185.99.119.68]) by smtp.gmail.com with ESMTPSA id 132sm25822902wmn.16.2016.10.31.10.18.52 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 31 Oct 2016 10:18:52 -0700 (PDT) From: Pete Heist Content-Type: multipart/alternative; boundary="Apple-Mail=_8E5AA987-862F-4D4E-B885-EFC96F5A4E89" Message-Id: Date: Mon, 31 Oct 2016 18:18:51 +0100 To: make-wifi-fast@lists.bufferbloat.net Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Subject: [Make-wifi-fast] Testing airtime fairness and other "make wifi fast" project code 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: Mon, 31 Oct 2016 17:18:55 -0000 --Apple-Mail=_8E5AA987-862F-4D4E-B885-EFC96F5A4E89 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Question: What kind of testing is most needed or useful for the airtime = fairness code and related work in the make WiFi fast project? And, is it = best to post any results to this mailing list? Test Environment: I=E2=80=99ve got a single spare OM2Pv1 AP with the = head of LEDE as of today installed (r2032). I=E2=80=99ve got two MacBook = Pros available as clients. I could do some flent or iperf3 runs, or = other testing. Background: I=E2=80=99m evaluating LEDE to improve the WiFi setup at an = outdoor camp, both the WiFi LAN and point-to-point WiFi Internet uplink. = So the testing I=E2=80=99m doing is also for us, to see if any = improvements can be made. For the LAN, we=E2=80=99re currently running Open Mesh firmware on a 7 = node mesh network (4 gateways and 3 repeaters, a mixture of OM2Pv2 and = OM2P-HS APs). The goal is to try to improve roaming, reduce latency and = provide airtime fairness, as clients connect at a mixture of data rates. = With up to 150 clients connected (10-15 people doing =E2=80=9Csomething=E2= =80=9D, at times), things can be rather =E2=80=9Cactive=E2=80=9D, as it = were. Latency can suffer. For the WAN, our WISP uses Routerboard 911-5HnD's for the point-to-point = devices (Atheros AR9300 chipset, running RouterOS 6.34.6, probably Linux = kernel 3.3.5). I=E2=80=99m not sure I=E2=80=99ll be able to change that, = so I don=E2=80=99t think I can run any =E2=80=9Cmake wifi fast" code = here today, unless a backport is done to this rather prehistoric kernel = version. Our Internet connection is advertised as "40 Mbps symmetric = with 1:3 aggregration=E2=80=9D, but after real world testing what that = really means for us is 8 - 25 Mbps symmetric, depending on the time of = day. With this kind of variable data rate, it doesn=E2=80=99t make much = sense to do rate limiting, so I don=E2=80=99t see how we can run = HTB+fq_codel in the same way we did with our old ADSL connection. But = I=E2=80=99m holding out hope that one day we=E2=80=99ll get queue = management this good in the WiFi driver itself, somehow. PS- I was sorry to miss the recent OpenWRT summit in Berlin, for the = Speeding up WiFi presentation, but the conference filled up before I = could register. I=E2=80=99m glad this great session was made available = online = (https://youtu.be/fFFpo_2xlfU?list=3DPL3bvPCw5QCLJ0xR1oXui6M7QBh6UElgvn = ).= Nice work!= --Apple-Mail=_8E5AA987-862F-4D4E-B885-EFC96F5A4E89 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
Question: What kind of = testing is most needed or useful for the airtime fairness code and = related work in the make WiFi fast project? And, is it best to post any = results to this mailing list?

Test Environment: = I=E2=80=99ve got a single spare OM2Pv1 AP with the head of LEDE as of = today installed (r2032). I=E2=80=99ve got two MacBook Pros available as = clients. I could do some flent or iperf3 runs, or other = testing.

Background: I=E2=80=99m evaluating LEDE to improve = the WiFi setup at an outdoor camp, both the WiFi LAN and point-to-point = WiFi Internet uplink. So the testing I=E2=80=99m doing is also for us, = to see if any improvements can be made.

For the LAN, we=E2=80=99re currently = running Open Mesh firmware on a 7 node mesh network (4 gateways and 3 = repeaters, a mixture of OM2Pv2 and OM2P-HS APs).  The goal is to = try to improve roaming, reduce latency and provide airtime fairness, as = clients connect at a mixture of data rates. With up to 150 clients = connected (10-15 people doing =E2=80=9Csomething=E2=80=9D, at times), = things can be rather =E2=80=9Cactive=E2=80=9D, as it were. Latency can = suffer.

For = the WAN, our WISP uses Routerboard 911-5HnD's for the point-to-point = devices (Atheros AR9300 chipset, running RouterOS 6.34.6, probably Linux = kernel 3.3.5). I=E2=80=99m not sure I=E2=80=99ll be able to change that, = so I don=E2=80=99t think I can run any =E2=80=9Cmake wifi fast" code = here today, unless a backport is done to this rather prehistoric kernel = version. Our Internet connection is advertised as "40 Mbps symmetric = with 1:3 aggregration=E2=80=9D, but after real world testing what that = really means for us is 8 - 25 Mbps symmetric, depending on the time of = day. With this kind of variable data rate, it doesn=E2=80=99t make much = sense to do rate limiting, so I don=E2=80=99t see how we can run = HTB+fq_codel in the same way we did with our old ADSL connection. But = I=E2=80=99m holding out hope that one day we=E2=80=99ll get queue = management this good in the WiFi driver itself, somehow.

PS- I was sorry to miss = the recent OpenWRT summit in Berlin, for the Speeding up WiFi = presentation, but the conference filled up before I could register. = I=E2=80=99m glad this great session was made available online (https://youtu.be/fFFpo_2xlfU?list=3DPL3bvPCw5QCLJ0xR1oXui6M7QBh= 6UElgvn). Nice work!
= --Apple-Mail=_8E5AA987-862F-4D4E-B885-EFC96F5A4E89--