From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (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 37AD83B29E for ; Sun, 20 May 2018 14:56:12 -0400 (EDT) Received: by mail-wr0-x230.google.com with SMTP id w18-v6so10130507wrn.6 for ; Sun, 20 May 2018 11:56:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eventide.io; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jKPMUDPqJYvBYE9GUnOTH9cijatJcvwhSUCB+Pxn77I=; b=Co3UuH+G0DmM2SazBa4aLEUwXjOuqknpqm/oyzrlgsIGRLkZEVPyrz8kUzAaG7EYqd sW5BHmDQeCtW9W+phdP706DaHjA63YeK2i0qcRYf/745SH1Lx0W/ozN3+d6xVNQnWo95 R/sOiQiZYPwPPexgLpXX+eOBzc5e6/ZhuJVm9+cZDbclRzKm4pM93dcfAPY+VFXihkWG jUo1gXy2QYBfvgiBp1fodTLBObfT62m1Iq4dMTLXh+iY6AIP5MOMpeLQ+cheN4frbsWt QkxRckYTiglUtk29CmA2C0foy8AqHbX3ohbu7h8cO7YX7R4p/qtEMc+fq1+mviMmhk3/ Lzhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=jKPMUDPqJYvBYE9GUnOTH9cijatJcvwhSUCB+Pxn77I=; b=XMpBzRnujPZW13VK7yMWYfb78eh62nMnaMEci9NqBA2rmJbB+w/xgXxQ9x+t3CjqZ6 L4qxgzFxbB3MljjPqyAKtKUUZWOXhrwugSHAOOYjN2zubnwhuIqQo0YWoOUgGvhLJj5L 3XBOJm8gROMmS4BOHrfHjdBsw7rdjAHcQD4A5AYXfhYw/742SvifIktkpLKYCSgTU4en 0VtSKcFaSY48qQD52hpyL2aJvD/cwkYzsjCypfpzAn4pAloDiG8lkv4uwmd2znKgrTOf FioVIn89a75U/vRKVu2Q0iAjlKwb2yiPUERT1lTl1VM9fo4NitF84wXw39ISy4ApQqD6 +9mA== X-Gm-Message-State: ALKqPwcyaN9jALFfNNYQeFOg/icauB2oFKiC39SEHuMzD/BBDIqLGQI+ pu4vZ2nBuRjLMsu4bUZx52BbvQ== X-Google-Smtp-Source: AB8JxZp7nbocnJ64GlMMVhhM0D6Dyi7OgKKxT64qHzs8XDtLS05SWjlNBoEi5zhCV7Gtt/6RZyMJIw== X-Received: by 2002:adf:a0b8:: with SMTP id m53-v6mr13404582wrm.269.1526842570955; Sun, 20 May 2018 11:56:10 -0700 (PDT) Received: from tron.luk.eventide.io (h-1169.lbcfree.net. [185.193.85.130]) by smtp.gmail.com with ESMTPSA id t14-v6sm10391017wrm.82.2018.05.20.11.56.10 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 20 May 2018 11:56:10 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: Pete Heist In-Reply-To: Date: Sun, 20 May 2018 20:56:08 +0200 Cc: make-wifi-fast@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: <3859F229-D698-44D2-906A-2C6527000013@eventide.io> References: To: bkil X-Mailer: Apple Mail (2.3124) 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: Sun, 20 May 2018 18:56:12 -0000 Hi, thanks for the tips=E2=80=A6most everything seems to be already set = similarly in Open Mesh=E2=80=99s config except: - the disabling of lower rates- interesting idea and maybe the most = consequential, I=E2=80=99ll see if I can do this in one of OM=E2=80=99s = custom.sh scripts, otherwise it=E2=80=99s easy to do in plain OpenWrt - client isolation isn=E2=80=99t supported when bridging to a VLAN, = which I=E2=80=99m doing at the moment It=E2=80=99s taking some convincing, but I have a rough plan to dig a = minimal trench for a new cabled gateway to split cabins 12 and 20, which = is the primary issue. If ground isn=E2=80=99t broken soon, it might be = me at the shovel. :) Most definitely I=E2=80=99ll report back as I want = to do some more testing on the ath9k changes, once this physical issue = is taken care of... > On May 19, 2018, at 6:03 PM, bkil wrote: >=20 > In reply to this thread: > = https://lists.bufferbloat.net/pipermail/make-wifi-fast/2018-April/001787.h= tml >=20 > Sorry for the late response, although I can see from yesterday's > SmokePing plots that the issue still prevails. >=20 > 1. > You should definitely not allow rates as low as 1Mb/s considering: > * plots of signal vs. rate, > * topology of closely packed cabins; > * mostly static, noise-free camp ground. >=20 > Almost all of your clients were able to link with >20Mb/s even at > 70-80dBm. Those below were probably just idling. I'd limit the network > to 802.11g/n-only, and would even consider disabling all rates below > 12Mb/s. >=20 > This should help both in working around imperfect schedulers and > clients roaming. >=20 > You could double check the coverage afterwards with a simple site > survey. You may also test whether disassoc_low_ack makes things more > stable around the edge. >=20 > Despite the recently introduced air fairness patches, most other > points are still valid from these earlier articles due to pathological > schedulers: > http://divdyn.com/disable-lower-legacy-data-rates/ > = https://blogs.cisco.com/wireless/wi-fi-taxes-digging-into-the-802-11b-pena= lty > = https://www.networkworld.com/article/2230601/cisco-subnet/dropping-legacy-= 802-11-support-from-your-infrastructure--part-2-.html >=20 > Disabling 802.11/b modulation also brings the added benefit of > occupying less bandwidth (16.5-20 OFDM vs. 22 Barker/CCK), enabling > the previously mentioned channel spacing of 1-5-9-13. >=20 > = https://wifinigel.blogspot.hu/2013/02/adjacent-channel-interference.html >=20 > 2. > Enable client isolation to mitigate broadcast storms. >=20 > 3. > If you still couldn't split the two cells that work on the same > channel, at least try to reduce their TX power to reduce their range > of interference. This may or may not improve things overall due to > hidden nodes, though. >=20 > We'd definitely love to hear from you whether any of these worked or > made things worse. Happy camping!