General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kenneth Porter <shiva@sewingwitch.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Xfinity Flex streaming box starves on cake?
Date: Fri, 04 Dec 2020 11:26:27 -0800	[thread overview]
Message-ID: <6096417F0109590F3C6DD6A1@[172.27.17.193]> (raw)

I suspect that my Xfinity Flex box has too small an internal buffer and is 
starving when fed by my cake-enabled OpenWrt router.

For the last few weeks, I've been streaming Amazon Prime Video shows and 
movies and the box tends to go to black screen after 5-10 minutes of 
viewing, followed by a jump to the Flex main menu (which selects which 
streaming service to view). I thought perhaps the box was overheating or 
that there was a bug in the Amazon app that caused it to crash to the home 
screen. This week the same thing happened when I watched a show on HBO Max.

On a hunch, I disabled SQM on the router and was able to watch an hour of 
TV with no interruption, using a different service on successive nights. My 
next test will be to re-enable SQM and try viewing to see if I get a black 
screen and crash to home screen again.

Sometimes instead of a black screen I get a "problem with connection" 
message. So my theory is that the Flex box has too little buffer to handle 
hiccups in the feed, and is depending on a deep buffer in the Xfinity 
modem. Except that I have the modem set to bridge mode so I can disable its 
DHCP server and let my LAN server handle DHCP and DNS and other services.

My SQM config follows:

config queue 'eth1'
        option itarget 'auto'
        option etarget 'auto'
        option linklayer 'none'
        option interface 'eth1.2'
        option debug_logging '0'
        option verbosity '5'
        option qdisc 'cake'
        option qdisc_advanced '1'
        option squash_dscp '1'
        option squash_ingress '1'
        option qdisc_really_really_advanced '1'
        option script 'layer_cake.qos'
        option iqdisc_opts 'docsis wash besteffort nat ingress'
        option eqdisc_opts 'docsis ack-filter nat'
        option ingress_ecn 'NOECN'
        option egress_ecn 'NOECN'
        option download '170000'
        option upload '9000'
        option enabled '1'



             reply	other threads:[~2020-12-04 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 19:26 Kenneth Porter [this message]
2020-12-06 12:15 ` Toke Høiland-Jørgensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='6096417F0109590F3C6DD6A1@[172.27.17.193]' \
    --to=shiva@sewingwitch.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox