1
General Discussion / Re: anyone know why enabling IPv6 on the LAN breaks Disney+, Netflix & Amazon Music
« on: March 03, 2023, 04:46:21 am »
0/10 and 3/20.
Thanks for your help!
Thanks for your help!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
General Discussion / Re: anyone know why enabling IPv6 on the LAN breaks Disney+, Netflix & Amazon Music
« on: March 02, 2023, 05:52:38 pm »
Thanks franco, apparently my WANs IPv6 connection that should work...doesn't!. Disabling IPv6 support on the LAN and removing the IPv6 WAN support eliminates that issue.
...Now that's sorted, why? Why would it work for 18 to 24 hours and then just...not?
...Now that's sorted, why? Why would it work for 18 to 24 hours and then just...not?
3
General Discussion / anyone know why enabling IPv6 on the LAN breaks Disney+, Netflix & Amazon Music
« on: February 24, 2023, 06:16:59 pm »
Been on OPNsense for about two months, pfSense, debian BYO, IPcop, IPfire,etc...for almost 2 decades now.
One thing I can't figure out, and it's reproducible to me (but I can never find corresponding log issues or other indications)...but if I enable IPv6 on my LAN, streaming services will work for about a day - and then they will start to fail w/o an error on the firewall end. No errors in the logs, diagnostics don't appear to show anything, just a silent death...
This is purpose-built edge device, ECC ram, fully BSD-Supported NICs, the works...so i'm fairly confident it's not some intermittent hardware issue. I've wirecaptured plenty of logs for the offending devices (Amazon Fire TVs of almost every generation) and on the IPv4 side everything looks good. No TTL issues, no dropped packets, no routing issues, nothing abnormal. On IPv6, it works...until it doesn't. Usually between 18 & 24 hours. A reboot makes it work again.
This problem really became noticable on the pfSense install that I ran for 5 years, and I never mentally tied it in to the IPv6 services on the LAN. When I migrated over the OPNSense, and really did it right with supported hardware, etc, I thought it was odd that the same problem I chased on pfSense resurfaced.
I don't need IPv6 on the LAN right now, but what am I missing?
One thing I can't figure out, and it's reproducible to me (but I can never find corresponding log issues or other indications)...but if I enable IPv6 on my LAN, streaming services will work for about a day - and then they will start to fail w/o an error on the firewall end. No errors in the logs, diagnostics don't appear to show anything, just a silent death...
This is purpose-built edge device, ECC ram, fully BSD-Supported NICs, the works...so i'm fairly confident it's not some intermittent hardware issue. I've wirecaptured plenty of logs for the offending devices (Amazon Fire TVs of almost every generation) and on the IPv4 side everything looks good. No TTL issues, no dropped packets, no routing issues, nothing abnormal. On IPv6, it works...until it doesn't. Usually between 18 & 24 hours. A reboot makes it work again.
This problem really became noticable on the pfSense install that I ran for 5 years, and I never mentally tied it in to the IPv6 services on the LAN. When I migrated over the OPNSense, and really did it right with supported hardware, etc, I thought it was odd that the same problem I chased on pfSense resurfaced.
I don't need IPv6 on the LAN right now, but what am I missing?
Pages: [1]