From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 19C5E21F340 for ; Sat, 7 Feb 2015 18:35:35 -0800 (PST) Received: by mail-ob0-f176.google.com with SMTP id wo20so19921018obc.7 for ; Sat, 07 Feb 2015 18:35:34 -0800 (PST) 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:content-transfer-encoding; bh=6Lsbfm10CiuB5eJCUakih2T3QljuF/IOAZVXGf47r6w=; b=MdS8GZn2Q5+HuiIth7uN9V8xYz+Z+OAjW2gpf0nHUH1ABIi1T2zklWssBKTIpDXxHd SIuFrtELiLbBzgxLktro1gU+Zn4cDyb+ZW7vtwJhwosPLQs3c4/JFN5JJc5ndxH68gwO 3su9ku38qXDfT6ph4h1v8e23lrnBi2+BsZiaLpPwEVGOKPg+LfFyCqGlIK+BuR6q8e3h 94Bq0loGWiZ/lRKqeCcbo1Qo5hD/LPuNyJhZQ54z7WK8O+6e9GQDi6gxuevr7nkrR+B1 mTYtQTqy4/FYSGBSD5EWJibtX2KVfqcX/P+W72h9n0vj55UxcnkqyD1nMMNAMpgtru0c QkJQ== MIME-Version: 1.0 X-Received: by 10.202.204.203 with SMTP id c194mr11405oig.81.1423362934655; Sat, 07 Feb 2015 18:35:34 -0800 (PST) Received: by 10.202.51.66 with HTTP; Sat, 7 Feb 2015 18:35:34 -0800 (PST) In-Reply-To: References: Date: Sun, 8 Feb 2015 15:35:34 +1300 Message-ID: From: Dave Taht To: David Lang Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] what stats do people want from conference wifi? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2015 02:36:04 -0000 I am very interested in per sta stats - rc_stats - captured fairly frequently - timestamped and kept on per mac order.. cat /sys/kernel/debug/ieee80211/phy*/netdev:*/stations/*/rc_stats you might also get a good grip on simultaneous users and on user migration by using this. also I have found the xmit stat to be useful. On Sun, Feb 8, 2015 at 3:02 PM, David Lang wrote: > In the next few days I'm going to be building the openwrt images to use a= t > the SCaLE conference. I will have ~50 APs deployed supporting ~3k attende= es. > This will be running on WNDR3700v2 and WNDR3800 APs. Since I am compiling > the firmware myself, I can add in patches to gather and log stats for thi= ngs > that are not normally reported > > The wireless network architecture is: > > separate ESSIDs for 2.4 vs 5. > each band gets bridged to a different VLAN > the APs are configured not to forward broadcast traffic from one wireless > client to another on the same AP (although broadcast traffic from one AP > probably goes out others after hitting the wire now that I think about it= ) > I have all logs from the APs sent to a central logserver > I have use rrdtool to catpture normal bandwith/cpu/etc stats > I also have rrdtool capture how many clients are connected to each ESSID > every minute. > > > What else can I gather related to the wifi? > > I think it would be useful if we could gather info along the lines of > > amount of airtime used > > how much latency is added to packets while waiting to transmit because it= 's > hearing something else transmit? > > amount of unused airtime available > > average effective bit rate > > percentage of time spent doing broadcasts (things required to operate at = the > lowest bit rate) > > > > > Part of the reason that I compile my own firmware images is that I > completely disable connection tracking in the kernel (because clients may > move from one AP to another in the middle of a connection it's a waste of > cpu and memory to track), and as a result of these optimizations, there i= s > actually quite a bit of CPU available. The boxes almost never hit 20% cpu > utilization, so there's quite a bit available to gather other stats. > > some of the stats I gather are in messages spit out by the kernel, others > from scrips running on the box querying things in /proc or /sys, and othe= rs > from watching logs and summarizing them once a minute. I even have a proc= ess > that goes threough all the connection logs for the duration of the show a= nd > graph how many unique MAC addresses we've seen and a breakdown into the > different vendor prefixes. If there's a way to get the data, I can suppor= t > it. > > If there are fq_codel stats that people would find interesting in this > environment, I can gather those as well (both on the APs and on the Debia= n > based firewall/gateway) > > David Lang > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel --=20 Dave T=C3=A4ht thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks