CaptnDanLKW
Senior Member
I am looking to block outbound 443/UDP traffic from my Roku TV.
RT-AC86U, HW Accel Enabled. No Skynet, diversion, etc. (as my sig says)
My Roku TV has a DHCP lease reservation of 192.168.1.56
I am blocking traffic using this Network Services Filter with these settings.
A) Is this the correct method?
iptables shows this:
xxxxn@RTAC86U:/tmp/home/root# iptables -L |grep -i JVC
DROP udp -- JVCRoku55. anywhere udp spt:https
B) Is there a way to log actions taken here if the rules match? Logged to /opt/var/log/firewall.log (scribe/syslog-ng location)
Background. Many different branded 4k RokuTVs have an odd issue with The Youtube app, where 2160p60 content wont keep up and keeps buffering, regardless of wired/wireless or ISP speeds.
I found a (recent) post in the roku community forums that says it has something to do with negotiation the QUIC protocol, and if you block it, it will fall back to TCP and should fix this quirk.
This has NOT fixed it for me, so I wanted to verify my setting was proper per the instructions AND get a log message that the router saw and dropped it.
Thanks all!
RT-AC86U, HW Accel Enabled. No Skynet, diversion, etc. (as my sig says)
My Roku TV has a DHCP lease reservation of 192.168.1.56
I am blocking traffic using this Network Services Filter with these settings.
A) Is this the correct method?
iptables shows this:
xxxxn@RTAC86U:/tmp/home/root# iptables -L |grep -i JVC
DROP udp -- JVCRoku55. anywhere udp spt:https
B) Is there a way to log actions taken here if the rules match? Logged to /opt/var/log/firewall.log (scribe/syslog-ng location)
Background. Many different branded 4k RokuTVs have an odd issue with The Youtube app, where 2160p60 content wont keep up and keeps buffering, regardless of wired/wireless or ISP speeds.
I found a (recent) post in the roku community forums that says it has something to do with negotiation the QUIC protocol, and if you block it, it will fall back to TCP and should fix this quirk.
This has NOT fixed it for me, so I wanted to verify my setting was proper per the instructions AND get a log message that the router saw and dropped it.
Thanks all!