Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 32 subscribers
  • Views 35322 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Netflix 4K and v17

RobertDavis

Ugh! Been having problems on my LG OLED Netflix app. 1080p worked fine but when I viewed 4K it would get about 15+ mins into a show and then start giving an error.  If you tried to resume it would play about 3 secs and error again.  FINALLY traced it to v17 (MR2 or MR3).  I had Web Filter: Allow All.  As soon as I changed to to None it worked fine.  Tried the Netflix exception and still had the problem. I had been running v16.05 until v17 MR2 came out and had no problems. Weird.



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    I solved it as follows:

    1. Create/enhance the Netflix FQDN Group with the following FQDNs:

    *.nflximg.com
    *.nflxvideo.com
    *.nflxso.com
    *.netflix.com
    *.nflxext.com
    *.nflximg.net
    *.nflxso.net
    *.nflxvideo.net

    2. Create a dedicated FW rule for NetFlix FQDN Group and your TV:

    Services: HTTP & HTTPS

    Web Malware: everything disabled

    IPS: can be enabled

    Web Policy: None

     

    And now the very important hint if it is still not working: Simply retry to play the video after 1-2 minutes if it was not working at first. This is some kind of a bug with the FQDNs, I've opened a thread for this here: First FQDN host resolution happens to late when used in FW rule

    Best Regards

    Dom Nik

     

  • 0 in reply to Dom Nik

    The other thing that we have discovered is that you need to make sure that your TV and your XG are using the same DNS server.  Some ISPs have co-located Netflix streaming boxes so that if you do DNS via the ISP DNS you go to one set of servers and if you do DNS via something else (eg Google, OpenDNS) you get a different set of servers.

  • 0 in reply to Michael Dunn

    Michael Dunn said:

    The other thing that we have discovered is that you need to make sure that your TV and your XG are using the same DNS server.  Some ISPs have co-located Netflix streaming boxes so that if you do DNS via the ISP DNS you go to one set of servers and if you do DNS via something else (eg Google, OpenDNS) you get a different set of servers.

    Micheal,

    Thank you for brining that up.  I've run into that issue too.  Some smart TVs won't "smartly" use your gateway DNS nor let your change its DNS.

  • 0 in reply to David Birdsall

    Most likely they are doing DHCP and getting the DNS settings from DHCP.  So if they getting their address from the XG I think they should be using the XG as their DNS server and everything is good.  If they are using your home ADSL router's DHCP then they are going to use that as the DNS server, which then will go up however your modem is configured.  At which point you should make sure that you modem and XG are configured the same.  The worst may be things like PVRs and Set Top boxes provided by the telco/cableco.  Since they are only ever intended to work on their network, they could potentially be configured to use some specific DNS server or even worse (ignore DNS and use a completely different mechanism to determine what servers to connect to).

  • 0 in reply to Michael Dunn

    I haven't had time to play with it since I posted so haven't been able to do more testing.  As noted the error was ONLY with 4K programs.  I could watch HD (1080p) all day with no problems.  My first quick thought is that Netflix keeps chunks on different servers (for caching) and my show switched to a different server to finish.  That is just a guess.

    The LG is DHCP handled by the XG firewall and uses my ISP DNS.

    I might try to force a Google DNS when I test again. I will also try the specific exclusions listed.  The built-in v17 Netflix exclusion had no affect.

  • 0 in reply to Michael Dunn

    Michael Dunn said:

    Most likely they are doing DHCP and getting the DNS settings from DHCP.  So if they getting their address from the XG I think they should be using the XG as their DNS server and everything is good. 

    I know for a fact that roku has hard coded google 8.8.8.8/8.8.4.4 dns servers. That is why every beta I ask for the ability to DNAT (which is available in SG) any dns traffic to anywhere back to XG for certain devices. Every device including most IoTs and phones also try to connect to NTP servers all day long all over the place but that is separate discussion although it still comes under my DNAT feature request.

    In any case always nice to hear your input Michael.

  • 0 in reply to Michael Dunn

    Michael,

    I fully understand this issue. I was saying thank you for bringing it up because I forgot to mention it to Robert Davis.

    I have run into this issue on earlier generations of smart TVs built for home users who did not have home networking, because they used cellular internet or were not "connected" at all.  Once they got a smart TV an internet service was now required to be installed or the streaming came through MoCA.

    I haven't seen this in 4k models because I'm sure that, by default, they get their instruction from the network router that most homes have now.

Reply
  • 0 in reply to Michael Dunn

    Michael,

    I fully understand this issue. I was saying thank you for bringing it up because I forgot to mention it to Robert Davis.

    I have run into this issue on earlier generations of smart TVs built for home users who did not have home networking, because they used cellular internet or were not "connected" at all.  Once they got a smart TV an internet service was now required to be installed or the streaming came through MoCA.

    I haven't seen this in 4k models because I'm sure that, by default, they get their instruction from the network router that most homes have now.

Children
No Data