User Profile
TechandMusic
Newbie Caller
Joined 2 years ago
User Widgets
Contribuciones
Re: Netflix no longer streaming
I no longer have the issue, Netflix is working for me now. They have change the IP for occ-0-7094-90.1.nflxso.net from a T-Mobile owned IP to a Netflix owned IP 198.38.108.x. So the traffic is no longer going to the T-Mobile data centers and instead is sent direct to the Netflix data centers. AS2906 198.38.108.0/24 Netflix Streaming Services Inc. curl -v https://occ-0-7094-90.1.nflxso.net * Trying 198.38.108.76:443... * Connected to occ-0-7094-90.1.nflxso.net (198.38.108.242) port 443 (#0) 11:37:26.467868 IP 192.168.x.x.61346 > 198.38.108.242.443: Flags , seq 2992268027, win 65535 11:37:26.513020 IP 198.38.108.242.443 > 192.168.x.x.61346: Flags [S.], seq 1595082536, ack 2992268028, win 65535 11:37:26.515457 IP 192.168.x.x.61346 > 198.38.108.242.443: Flags [.], ack 1, win 2054 11:37:26.522641 IP 192.168.x.x.61346 > 198.38.108.242.443: Flags [P.], seq 1:337, ack 1, win 2054 I suspect that was a workaround while they figure out the root cause on the T-Mobile hosted Netflix streaming. When I had the issue I changed my DNS resolver to Google, CloudFlare, OpenDNS etc, but as long as occ-0-7094-90.1.nflxso.net resolved to a T-Mobile IP here in the east coast, the issue was there.2Visto0likes0ComentariosRe: Netflix no longer streaming
Here are all the requests that I see in order: android.prod.cloud.netflix.com = Successful connection nrdp60-appboot.netflix.com = Successful connection occ-0-7094-90.1.nflxso.net = Failed SYN packet, no response on T-Mobile IP api-global.netflix.com = Successful connection secure.netflix.com = Successful connection occ-0-7094-90.1.nflxso.net = Failed SYN packet, no response on T-Mobile IP ichnaea.netflix.com = Successful connection Testing to occ-0-7094-90.1.nflxso.net from T-Mobile home gateway: curl -v https://occ-0-7094-90.1.nflxso.net * Trying 208.54.15.202:443... * connect to 208.54.15.202 port 443 failed: Operation timed out Testing toocc-0-7094-90.1.nflxso.net from Comcast IP: curl -v https://occ-0-7094-90.1.nflxso.net * Trying 208.54.15.203:443... * Connected to occ-0-7094-90.1.nflxso.net (208.54.15.203) port 443 (#0) I hope T-Mobile can resolve this ASAP as it has been many days with no progress1Ver0likes0ComentariosRe: Netflix no longer streaming
I have the same issue for a few days now, I have TMHI,FireTV, Google TV and Apple devices all having the same issue. I did some tests and noticed that my devices are doing a DNS lookup for occ-0-7094-90.1.nflxso.net which resolves to 208.54.15.202, 208.54.15.203, 208.54.15.204 and 208.54.15.205. The domain is owned by Netflix and the IPs 208.54.0.0/17 are owned by T-Mobile. I also did a packet capture on my firewall which is connected to the T-Mobile Home Gateway and I can see many connections attempts from my internal network to the T-Mobile IPs but noresponse from them. 23:28:39.597816 IP 192.168.x.x.50974 > 208.54.15.202.443: Flags , seq 1696298149,win 23:28:40.604997 IP 192.168.x.x.50974 > 208.54.15.202.443: Flags , seq 1696298149,win 23:28:41.605026 IP 192.168.x.x.50974 > 208.54.15.202.443: Flags , seq 1696298149,win 23:28:42.606625 IP 192.168.x.x.50974 > 208.54.15.202.443: Flags , seq 1696298149,win If I run the same test using a different ISP, the T-Mobile IP 208.54.15.202 actually responds and completes a 3 way handshake connection. 23:28:07.301342 IP 192.168.x.x.50936 > 208.54.15.202.443: Flags , seq820598644,win 23:28:07.329634 IP 208.54.15.202.443 > 192.168.x.x.50936: Flags [S.], seq 2897770398,ack 23:28:07.331666 IP 192.168.x.x.50936 > 208.54.15.202.443: Flags [.], ack 1,win 23:28:07.350863 IP 192.168.x.x.50936 > 208.54.15.202.443: Flags [P.], seq 1:302,ack So for some reason the T-Mobile IPs are dropping the Netflix stream requests that are coming from their TMHI gateways.1Ver0likes0Comentarios