NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DrillSGT
Jan 29, 2023Tutor
RBR20 blocking *something* with Amazon Firestick 4k
I have seen a few older posts sort of around this topic, but nothing exactly the same. New Fire TV Stick 4K connected to RBR20/RBS20 network seems to have extremely slow network connection for s...
- Feb 05, 2023
For the benefit of others, here is an update on the resolution to the problem. In the end, this is not an Orbi problem, but one take-away relevant to Orbi is the use of the http://orbilogin.net/debug.htm page.
NETGEAR support instructed me to capture WAN/LAN traffic using the built-in http://orbilogin.net/debug.htm page and email it to them. This is a great tool and what I was hoping for. I don't know why it's not documented in the User Manual.
They also requested that I put the router back to factory default and report back to them. Resetting made no difference, but I took that opportunity to use a different wifi SSID and isolate all the other wired/wireless items on the network. I found the cause of the issue was related to having a TP-Link TL-R600VPN device connected in the wired network. This device is being used just as a LAN switch (no WAN connected, DHCP disabled). Here's where you can use that capture from the /debug page and really go to work! I captured traffic both with and without that TP-Link switch in the network.
I saw in the failure logs that there is a lot of IPv6 communication from the FireStick, and seemingly a fallback to IPv4 at some point, but very slowly and it doesn't really recover. Including some link-local ICMPv6 neighbor solicitation/advertisements between the TP-Link and the FireStick, which I did not see in the success logs.
The success case logs showed all IPv4 communication from the FireStick, and of course no ICMPv6 exchanges.
Then I found a setting in TP-Link TL-R600 in the IPTV section that had IGMP proxy enabled (default maybe? I don't think I've ever even looked at that). I disabled that, and I believe that solves the problem.
I did not go back and capture new success traces to see if it is all IPv4 or if it is IPv6 working better. I understand that IGMP can affect exchange of IPv6 info info but my understanding of what exactly is happening is a bit shaky. I also can't explain why the Firestick had issues with some apps, while other apps were fine and all other devices on my network were fine - including an AppleTV running exactly the same apps that fail on the Firestick. I assume it comes down how the devices/apps are using IPv6, but since it is working now, I'm not looking any deeper at this point.
Thanks to all for the input and help.
CrimpOn
Jan 29, 2023Guru - Experienced User
DrillSGT wrote:
I don't really see much of anything in the Orbi WebGUI in terms of available diagnostic tools and logs, so I am stuck where to go next, and hoping somebody here has had a similar experience or has some ideas.
This is perhaps the one area where the Orbi 'app' is superior to the Orbi web interface. Whereas the web interface Attached Devices shows how the device is connected (2.4G vs. 5G) and to which Orbi unit, the app Connected Devices panel shows a list of devices that are currently connected in three groups: 2.4G, 5G, and Wired with a symbol indicating the strength of the connection. Selecting the device brings up a panel with the "Link Rate" of the connection.
The troubleshooting steps appear to be "spot on". Updating the firmware was a smart move because one of the first things people suggest is, "update the firmware".
If performance was consistently terrible, I would look at "does it get a good WiFi signal?" TV's are full of metal and something plugged into an HDMI port might not "see" the WiFi. The network analysis (analiti) and good performance on some apps seems to rule that out.
As you indicate, this does not make sense.