From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 2B5CD3CB3F for ; Tue, 3 Sep 2019 20:03:19 -0400 (EDT) Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-01v.sys.comcast.net with ESMTP id 5IeyiwzJ5a4RT5IlaiWdww; Wed, 04 Sep 2019 00:03:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20180828_2048; t=1567555398; bh=TNOTpRPBUDhC1d/lPgg5G2UFE2YSAoFnUslFjWUihbQ=; h=Received:Received:Received:Date:From:To:Subject:Message-ID: MIME-Version:Content-Type; b=qE3FNnFhG5ZDI7UU5SeXti6mYgwrU9stDJtqUzQ6/BPdmZTIUqKnqzPlHX4kqd8Le i4AGmJFfhHtaqFKym7ePKGjlsMAFtwRSYxYvjnI9Dk+TmJZyWwcyo/BDqgywMt5ztl Xui6IP2zUkbIFB0uslfZ8h8cfvVzJmkXOr0X3OaXvScRDBElETCOCCX9SVW8tp1f9p tO5N6aQIRnwzpolz+EJC5MwtMXjA3rKlEcxDId0Kqvnwbp3TzcUvRjEZajfXx7P3bg 9kQzAL8om1sO4vjCDBeNro+m+qtmYyHi4Mi4Fmpwm6nbgctfqyGs8FMoRqPJG3iiiG 1Xbgp/wOtN9oQ== Received: from home.sewingwitch.com ([IPv6:2601:644:1:6c10::3f1]) by resomta-po-04v.sys.comcast.net with ESMTPA id 5IlYiyglL89lp5IlZiPKJS; Wed, 04 Sep 2019 00:03:18 +0000 X-Xfinity-VMeta: sc=0;st=legit Received: from [10.96.7.39] ([10.96.7.39]) (authenticated bits=0) by home.sewingwitch.com (8.14.7/8.14.7) with ESMTP id x8403E1j017889 for ; Tue, 3 Sep 2019 17:03:14 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 home.sewingwitch.com x8403E1j017889 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sewingwitch.com; s=default; t=1567555394; bh=TNOTpRPBUDhC1d/lPgg5G2UFE2YSAoFnUslFjWUihbQ=; h=Date:From:To:Subject:In-Reply-To:References:From; b=1DNrdCByVDYUWfidaH3E122rnSjK0NFsEAE9cVvQSHONzfn4OLnBeZXp/bjn0TbwP uHm+VOuxLVQfIWStsal8vWAESolw3YU34NQ8W5N9aOcARgotEGVox1GZt7AjR8P0Sw bEsP11Vx0aKh8SwlxvZ8TpUXS/mRqD8F3c4INA48= Date: Tue, 03 Sep 2019 17:03:13 -0700 From: Kenneth Porter To: bloat Message-ID: In-Reply-To: References: <614481A6-1C07-4C6A-AB86-10A6DEF1B5D2@gmail.com> X-Mailer: Mulberry/4.1.0a3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=1129 X-Scanned-By: MIMEDefang 2.84 on 10.96.0.132 Subject: Re: [Bloat] Rigorous Coffee Shop Bloat Testing X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2019 00:03:19 -0000 --On Tuesday, September 03, 2019 11:29 AM -0700 Dave Taht wrote: > In many cases they share the wifi with their credit card reader and > when I say that fixing bufferbloat helps, > their eyes light up. That was a specific problem that at least one had > - demonstrable - I saw it take forever > to clear a transaction (and the bloat was 2+ seconds long at the time > - NOT triggered by me) once... he had a synology router, and "applying > QoS" "just worked", and we did other things like reposition the > antenna, also. got me lunch > that did and he punched a whole bunch of holes in my "repeat business" > card.... My favorite cafe owner would just look like a deer in the headlights over this. She doesn't do online at all and just provides the wifi for customers. I'm not sure who set it up for her. Her CC reader is dial-up. I'm pretty new myself to hacking a consumer router so I don't know what's even possible. Likely her router doesn't even have any settings to deal with bloat. What can you do without risking breaking things and ending up with an angry owner?