From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (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 117D23B2A4 for ; Sat, 30 Jun 2018 15:15:11 -0400 (EDT) Received: by mail-oi0-x229.google.com with SMTP id i12-v6so6957406oik.2 for ; Sat, 30 Jun 2018 12:15:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=IX5pZsGvuU5TA0eEBt8nF12nM2w0lv81nLfHWxFLNUA=; b=cJoBhG36H9SXozGNHhZFeS4FcMEoC06pkLOrD6fHr7FZJg8xqP4YA9LvGOrWHZmkFB EVyM+s7bkPbdfxd4WrGTw/aTXGjN9wc7JzXUPzUJL7g1lRU92OAX2kjA003OhlLmt9U5 Z3AR2lkQ+QgwRNVbcUdA0o7OBNAEAxdGVAC4rlQXOS4Phv3zGXCUTtoqEeuNsXtxu16a Yo8adwLNT/8YcqfzSUwzIpu0fxvaUL0rJE89pdpKXiNqZ+3reSET6zfX2JhzGyWvUvpk Izhi8aD4Xmzb+kW7NZ9Q+tOsffV/4Tmr8c6lsywQUXpD9ZiIl/G+QQCNu+ZV9WS+hzTs +VaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=IX5pZsGvuU5TA0eEBt8nF12nM2w0lv81nLfHWxFLNUA=; b=EIY6TpUnhMvYe50vcvmX2xmZ4MJGX4slyLEGhG2YrgRXKr+Rm5FTVrIYpSomxJ1x3I mW0CHEkWBNBUuOrduwy0IiZOT14hrRtA2XLgLoszWM90EkY2dnczaJT+5p6fumFsdJUk TApBum3x/HEEufwTyWIlylrDozRNZZlwiSWVFzhZjD8kNvI1Hksqn+vhfOjSbn0rpZyY w1qEMvv7+q+PEw4u++nj5drfZZ2EN9oAU3nEw1EGlgj6JorlHlMU3WkUH2hjv1Fx/UMb 8eUBXaukphMptGb4VF36fh28N59bkb0oYMLIh9iS2MQjSi3OY0BKyl9nulp0IfGj7hVN NTfA== X-Gm-Message-State: APt69E0HfZAgZqLrHxokI8zXtd9gx4IpplmEnCdlrnfBkQyhSjxWd/7g jW3oHeotbdAVEBfeLAtjEACLdWLCPrMIGwcyxFg= X-Google-Smtp-Source: AAOMgpfd7t7L71g2maGZlHwfXyf1NucXbsYLvDR6hM1wer5ScLFrDYi8OOgtWkIz2f8nsLRAQe+xMzCltVN1cPZm+hM= X-Received: by 2002:aca:efd7:: with SMTP id n206-v6mr48513oih.70.1530386110257; Sat, 30 Jun 2018 12:15:10 -0700 (PDT) MIME-Version: 1.0 Sender: bkil.hu@gmail.com Received: by 2002:a9d:1d28:0:0:0:0:0 with HTTP; Sat, 30 Jun 2018 12:14:49 -0700 (PDT) In-Reply-To: <8A44F1D4-1EB8-4D46-85F9-00C7307FF2D4@heistp.net> References: <9E7E043B-2373-46ED-B122-38A287422999@eventide.io> <87d0wu7rbg.fsf@toke.dk> <8A44F1D4-1EB8-4D46-85F9-00C7307FF2D4@heistp.net> From: bkil Date: Sat, 30 Jun 2018 21:14:49 +0200 X-Google-Sender-Auth: Zndv3JG48AEH_9PHcX5KJC0ELxk Message-ID: To: Pete Heist Cc: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , make-wifi-fast@lists.bufferbloat.net 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: Sat, 30 Jun 2018 19:15:11 -0000 Dear Pete, We understand that you are reluctant to share full radiotap wlan traces due to privacy reasons and collecting them would strain your infrastructure still a bit more. As a compromise, let me suggest a lightweight alternative. You can set up to only collect trimmed frame metadata on your AP's of interest, ie., cabin 20 & 24 and the gateway running on the same channel. You can aggregate a full day's worth of data or just the interesting hours at a central location using a PC or NAS. Then you can export only a few key data fields to CSV to carefully mask out any remaining ID and data parts. After compressing such an export with xz, it should have a manageable size. I've made a few small scripts to do such an export and to illustrate how to run the central collection & the agents on your AP's in a quick and dirty way. Feel free to improve and share your findings. https://github.com/bkil/lede-pcap-investigation I'm sure many of us would like to have a look into such real life data, because your high density single radio setup sounds really interesting from a contention standpoint. Although I've tested it on both Atheros and Intel traces, you should probably preserve the original pcap's as well until we verify that all needed fields had been successfully exported. Also feel free to adjust the snap length if needed. After you have collected the data, please also attach a recent SmokePing screenshot so we can correlate the two. Although we can probably give more informed advice based on the traces, as a stop gap measure until you finish cabling, you may consider traffic shaping of the clients to improve QoS. For example, you may put a hard bandwidth cap on each client (or only those coming from an AP in question), prioritize HTTP & VoIP traffic and reduce P2P traffic, depending on what is the biggest data hog. Also, could you by any chance set up monitoring of some addition metrics, like CPU usage, I/O wait, load average and memory usage on your nodes? N.b.: It's a pity that networking trace anonymization tools aren't up to the challenge. Simple MAC randomization or hashing with data omission would be just fine for such a use case. https://sharkfestus.wireshark.org/sharkfest.11/presentations/A-11_Bongertz-= Trace_File_Anonymization.pdf http://www.caida.org/tools/taxonomy/anontaxonomy.xml https://wiki.wireshark.org/Tools#Capture_file_anonymization https://cseweb.ucsd.edu/~snoeren/papers/slomo-nsdi13.pdf Regards On Wed, Jun 13, 2018 at 6:01 PM, Pete Heist wrote: > > On Jun 13, 2018, at 3:24 PM, Toke H=C3=B8iland-J=C3=B8rgensen wrote: > > Pete Heist writes: > > I=E2=80=99m still waiting for the digging / cabling project to happen, wh= ich > > > How to improve WiFi? Run cables! :D > > > Yes, and pave the earth right over=E2=80=A6 :) > > Seriously, watching this network evolve over the years has been a 6 year > lesson in incremental progress, something like: > > 1) 4Mbit ADSL + 802.11g > 2) 4Mbit ADSL/fq_codel + 802.11g > 3) 4Mbit ADSL/fq_codel + 802.11n > 4) 40Mbit via P2P WiFi + 802.11n > 5) 40Mbit via P2P WiFi + 802.11n 2x2 > 6) 40Mbit via P2P WiFi + 802.11n 2x2 / make-wifi-fast ath9k driver > > This is not an enterprise, so we=E2=80=99ve never invested in high-end ha= rdware, but > perhaps life would have been better along the way if the entire WiFi > industry had focused not on maximum single device throughput but on > resolving contention, increasing responsiveness and providing fairness > between multiple users. But then we can=E2=80=99t put =E2=80=9C300 Mbps= =E2=80=9D on the box! > > I do appreciate your ath9k driver work for moving beyond that kind of > thinking, I just need to see if I can fix the other stuff getting in its > way=E2=80=A6 :) > > _______________________________________________ > Make-wifi-fast mailing list > Make-wifi-fast@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/make-wifi-fast