From: Yan Seiner <yan@seiner.com>
To: linux-ppp@vger.kernel.org
Subject: Netflix and pppd
Date: Sun, 06 Dec 2015 16:27:42 +0000 [thread overview]
Message-ID: <566461FE.4090003@seiner.com> (raw)
I've been chasing a weird issue with Netflix and pppd. Basically, the
Netflix apps in my Roku and Samsung TV will not play reliably when using
pppoe. Using tcpdump I can see packets flow, but the app will either
stop at 25% or 99% and eventually time out with the "We're having
trouble playing this title right now".
If I set up my modem to handle the pppoe connection and do double NAT,
it works fine. The problem only comes up when I set up the modem to act
as a dumb modem and use pppd to complete the connection. The problem
only happens when I am running pppd to set up the connection.
Netflix through a browser works fine.
I am running pppd 2.4.7.
Here's what I've done:
Enabled icmp fully (I don't block any icmp messges)
Enabled arp by default
Set up the TV and the Roku to use google DNS instead of dnsmasq DNS
forwarding
Set up dnsmasq to tell dhcp clients to use a shorter packet length
Disabled QOS
Disabled dns-rebind protection.
Snippet of tcpdump when the whirlygig is stuck at 99%
07:42:47.464150 IP samsungtv.lan.41108 >
ipv4_1.lagg0.c023.iad001.ix.nflxvideo.net.www: Flags [.], ack 174241,
win 6200, options [nop,nop,TS val 229009 ecr 175479014], length 0
07:42:47.464577 IP ipv4_1.lagg0.c023.iad001.ix.nflxvideo.net.www >
samsungtv.lan.41108: Flags [.], seq 174241:175681, ack 286, win 2050,
options [nop,nop,TS val 175479056 ecr 228993], length 1440
07:42:47.466836 IP ipv4_1.lagg0.c023.iad001.ix.nflxvideo.net.www >
samsungtv.lan.41108: Flags [.], seq 175681:177121, ack 286, win 2050,
options [nop,nop,TS val 175479056 ecr 228993], length 1440
07:42:47.468982 IP ipv4_1.lagg0.c023.iad001.ix.nflxvideo.net.www >
samsungtv.lan.41108: Flags [.], seq 177121:178561, ack 286, win 2050,
options [nop,nop,TS val 175479056 ecr 228993], length 1440
07:42:47.471442 IP ipv4_1.lagg0.c023.iad001.ix.nflxvideo.net.www >
samsungtv.lan.41108: Flags [.], seq 178561:180001, ack 286, win 2050,
options [nop,nop,TS val 175479056 ecr 228993], length 1440
07:42:47.505174 IP samsungtv.lan.41108 >
ipv4_1.lagg0.c023.iad001.ix.nflxvideo.net.www: Flags [.], ack 180001,
win 5320, options [nop,nop,TS val 229020 ecr 175479056]
next reply other threads:[~2015-12-06 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 16:27 Yan Seiner [this message]
2015-12-06 16:53 ` Netflix and pppd James Carlson
2015-12-07 4:05 ` Michael Richardson
2015-12-07 12:17 ` Yan Seiner
2015-12-07 13:58 ` Michael Richardson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566461FE.4090003@seiner.com \
--to=yan@seiner.com \
--cc=linux-ppp@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.