From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 960EE3B29E for ; Sun, 6 Dec 2020 07:15:27 -0500 (EST) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1607256926; bh=kdQquL/+yfYVBqgZ2vyHINkt2dc/BRxEs98Aj9A57D8=; h=From:To:Subject:In-Reply-To:References:Date:From; b=jJvPyrrAltW5IjcIy8+efe0jaWUEmmRMe8eGJddnFDc1uh8MoEF/i0S4qmRwQe0G5 I09/dMI+azuJTKuqBEQoD7lAA0avLsyukxPFM3mP77BxRjdBlljiRMzslGp3uCVBTn D3hiOl7hZkwpvwGyL+foBSlEK3+HHccr4CXLyTfQZkf78HhZBRkezeBXXzuzUW0EIf +rX+XCUMrJ6voNt637bpxG2xd42QgiSeLXI8l4loVnM+RybWq7GWsCUqYYJ9nh7g+J hEtNG5+44vw9suLV9TjmTv97ZZwaKGPuDGJnQW1gqFjNcFAbpUauxFzOXx7z/iGLB5 5r6mAzfGE6O3A== To: Kenneth Porter , bloat In-Reply-To: <6096417F0109590F3C6DD6A1@[172.27.17.193]> References: <6096417F0109590F3C6DD6A1@[172.27.17.193]> Date: Sun, 06 Dec 2020 13:15:25 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87eek36sgy.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Bloat] Xfinity Flex streaming box starves on cake? 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: Sun, 06 Dec 2020 12:15:27 -0000 Kenneth Porter writes: > I suspect that my Xfinity Flex box has too small an internal buffer and is > starving when fed by my cake-enabled OpenWrt router. >From your config you have around 10x the downstream bandwidth you need for streaming, so unless you are really hitting your connection hard with other things I would not expect packets to buffer in the modem/router at all while you're streaming. So if this really is caused by sqm-scripts (which I think you should do a few more tests to definitely confirm), I would think it more likely it was due to some other weird interaction. Streaming box expecting a certain DSCP marking? Server choking on ACK stream due to filtering? Hard to say... A packet dump of the stream going to the box while the black screen happens may be illuminating, but could be hard to pull off if it's not reliably reproducible... -Toke