Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


arjoll

22 posts

Geek
+1 received by user: 4


#311217 23-Dec-2023 22:29
Send private message

I've got a weird one here. We have an LZ980 OLED, about a year old, which has started having issues with certain apps when connected to the main network. We noticed it with TVNZ+ a few months ago, but now have the same issue with Netflix, ThreeNow and Disney+. Amazon Prime Video, Youtube and Sky Sport Now (the freebie subscription with the set) are fine.

 

What happens is - TVNZ+ will timeout when it normally play an ad, Netflix will stop playback about 2 minutes in to any programme, Disney+ and ThreeNow just time out.

 

I'm running an expired (ssh don't tell my WatchGuard account manager) WatchGuard Firebox T70 with 12.7 firmware, connection is 2degrees gigabit with static IP. The TV is on our home VLAN through a Netgear GS116E "plus" switch. I am not sure if the issue was before I split the home and home office into separate VLANs.

 

The strange thing is that these apps all work without issue if I hotspot on to my phone (Note 20 Ultra), and the TVNZ+ app (haven't tried the others) works fine on my Xbox Series X, which is also on the home VLAN.

 

DNS was 1.1.1.1, have set to 2degrees new forwarders 111.69.69.69 and 111.69.69.68 (the TV only takes one at a time so I've done them one by one) and also set up DNS forwarding on the Firebox to the 2degrees ones and used that. The WatchGuard has a TCP-UDP rule to allow any traffic from the reserved address for the TV, and I've also tried an "any" rule. I have also tried on wireless (Unifi AC Lite) but get the same issue.

 

Packet capture shows that TVNZ is making a bunch of DNS requests and getting what appers to be valid replies. I can't help thinking it is somehow DNS related though, as it's not just making one or two - it makes multiple requests in a row in the Firebox logging, and the capture shows it's making the same request multiple times.

 

Wondering if anyone else has seen a similar issue? I could try a back channel to WatchGuard but really prefer to use those kinds of favour more for client issues, and could try another router but that's an awful lot of messing around with the setup I have with an IKEv2 VPN back to work etc.


Create new topic
arjoll

22 posts

Geek
+1 received by user: 4


  #3176133 29-Dec-2023 13:08
Send private message

Update on this one - it may be the VLAN tagging between router and switch. All of the VLANs were on one router port, with my home office untagged, home and IOT tagged. Moving the TV onto its own port on the router, separate network, resolved the issue. My next step will be to add that port to the home VLAN as untagged and see what happens - because it's working the urgency is no longer there, and the family got to watch random Christmas movies on Disney and Netflix as planned.




BlakJak
1330 posts

Uber Geek
+1 received by user: 735

Trusted

  #3176165 29-Dec-2023 17:29
Send private message

arjoll:

 

Update on this one - it may be the VLAN tagging between router and switch. All of the VLANs were on one router port, with my home office untagged, home and IOT tagged. Moving the TV onto its own port on the router, separate network, resolved the issue. My next step will be to add that port to the home VLAN as untagged and see what happens - because it's working the urgency is no longer there, and the family got to watch random Christmas movies on Disney and Netflix as planned.

 

 

 

 

I'm not sure I understand why you'd leave anything tagged on a port that has a consuming device plugged in.

 

In general you want an access port (single vlan, untagged) facing any consuming device (appliance, computer, etc).  You only want Tagged VLAN's where you need to transport more than one VLAN between devices (say, an IP phone with a pass-through port for a computer, where your phone and your computer need to communicate on different VLAN's.

 

Tagging should only be required on trunk ports between network equipment?





No signature to see here, move along...

arjoll

22 posts

Geek
+1 received by user: 4


  #3176168 29-Dec-2023 17:54
Send private message

BlakJak:

 


I'm not sure I understand why you'd leave anything tagged on a port that has a consuming device plugged in.


In general you want an access port (single vlan, untagged) facing any consuming device (appliance, computer, etc).  You only want Tagged VLAN's where you need to transport more than one VLAN between devices (say, an IP phone with a pass-through port for a computer, where your phone and your computer need to communicate on different VLAN's.


Tagging should only be required on trunk ports between network equipment?


The TV was plugged into a port with nothing tagged on it - the port was untagged on the home network. The only tagged ports were between the Firebox and main switch, and the ports the Unifi APs are on.



BlakJak
1330 posts

Uber Geek
+1 received by user: 735

Trusted

  #3176179 29-Dec-2023 18:24
Send private message

Sounds correct. So I can't imagine why changing anything in that realm should've fixed your problem.





No signature to see here, move along...

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.