NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi and ATT Uverse IPTV
Today I reconfigured my network to move all remaining traffic onto the Orbi, including IPTV. For those outside the US, one of the vendors that sells IPTV service is ATT and their product is called U...
Yes of course, my comment was a bit facetious and tongue -in-cheek.
I'll probably move a few things around to remove the constraint. The main reason for the comment was that I endeavor to wire connect as many streaming devices as I can.
As for the concern about too many devices on the satellite, is there some hardware or other technical reason I'm unaware of?
I'll probably move a few things around to remove the constraint. The main reason for the comment was that I endeavor to wire connect as many streaming devices as I can.
As for the concern about too many devices on the satellite, is there some hardware or other technical reason I'm unaware of?
Bandwidth on certain devices can be taxing and some router just have a limitation on how much bandwidth they can process all at once. Each device connected to a router has the main connection, however apps and such on each device can open many connections which adds up.
FURRYe38 wrote:
Dandwidth on certain devices can be taxing and some router just have a limiation on how much bandwidth they can process all at once. Each device connected to a router has the main connection, however apps and such on each device can open many connections which adds up.
If the point was about the RBK50 in general, I'm good. But as far as the RBS50 is concerned, that monster wireless backhaul is for all intents and purposes transparent and should make all the connected clients stand on equal footing.
Yes, it should be good. So adding a switch behind the RBS should work as well.
The following is a bug report. Firmware level tested was v60.
The timeshift commands to the ISB7005 set-top box do not work when the receiver is Ethernet connected to the RBS50. I moved the receiver back onto the VAP2500 WAP connected to the RBR50 and the timeshift controls work properly. It appears the RBS50 may not fully support IGMPv3 protocols or some defect exists.
What happens if you disable IGMP proxy on the RBR? Someone reported that disabling this on the RBR helped with the TV service get thru to the set top boxes over Orbi.
- That’s table stakes for IPTV to work at all.
So yes, that’s already unchecked. Possible that the IPTV just may not work at all thru Orbi. Or needs to be all connected with there required HW. I know that DISH wireless Joeys have to be connected to there own wireless AP and not external wifi such as Orbi.
Anything is possible I suppose. But it was working. In fact it could be the upstream servers themselves as I've seen one other report like mine from a veteran user.
I did a full reboot last night and the only thing I stopped short of was factory reset of the gateway and the RBR50. I do think v60 has issues though.
And as for why I'm not using the native hardware support, it's because without running everything off the same network, I cannot use the remote control function over wifi built into the Uverse app. This has become more important to me to use over the standard IR remote. I'm at a point now I wish TVs and settop boxes would do away completely with IR and use either wifi of bluetooth to perform the remote command functions.
Well something to try as last resort with a reset.
IR has it's place in some areas. I know for DISH they dual band remotes so IR and UHF. I use IR repeaters were needed for my use.
The Uverse app thing, that would be there area of development and would check on its requirements for use with 3rd party wifi outside of there required HW.
If it has been working up to v60 then possible something on there side recently broke. Wouldn't be always something with Orbi. :smileywink:I'd still like to either be able to report a bug for Orbi or at least get confirmation from Netgear that the RBS50 provides full support for IGMPv3.
As for Uverse itself, I don't need help with it from this community. I'm not sure how my messages are being misinterpreted but I'll try to do better to clarify my posts.
To the extend standards and specifications are beng implemented in the product, I do expect them to work no matter how obscure the usecase may be.
Cheers
Would be best place to let NG know:
https://www.netgear.com/mynetgear/registration/login.aspx
Might ask a forum moderator about IGMPv3. I presume it doesn't. And may not until Orbi AX arrives. Who knows.
Good Luck.
Is a thread like this okay and perhaps explicity tagging one of the moderators to respond? I'm not well versed on how to engage moderators here.
Did you ever get any information on this?
I see IGMPv3 in the UI of the RBR.
gr8sho wrote:Hello Blanca. Can you have a look at this thread please and in particular the question about requesting confirmation for support of IGMPv3 being extended to the RBS50 and it's attached clients.
Thank you!
- Hello. Haven't seen a reply.
Yes, for the RBR50, but the RBS50 I'm uncertain about. In other words, does IGMPv3 support carry across wireless backhaul to its wired clients. I would presume yes, however with Orbi, could be anything. :smileyfrustrated:
Have you tried wired backhaul with the RBS?
gr8sho wrote:
Hello. Haven't seen a reply.
Yes, for the RBR50, but the RBS50 I'm uncertain about. In other words, does IGMPv3 support carry across wireless backhaul to its wired clients.- That’s not practical unfortunately.
If Netgear provides an official response and also needs or wants to do a deeper dive into the configuration, I’m willing to help where I can. I do in fact have interest in having a wired IPTV settop client connected to a satellite to simplify the overall network topology. Something to open a support ticket and see if you can send them the debug logs...
gr8sho wrote:
That’s not practical unfortunately.
If Netgear provides an official response and also needs or wants to do a deeper dive into the configuration, I’m willing to help where I can. I do in fact have interest in having a wired IPTV settop client connected to a satellite to simplify the overall network topology.- Right, and again, focus on the satellite, as the base works fine.
If talking to engineering, confirming support and validation testing is good enough.
Thanks so much for taking interest. Hello, While I haven't heard back on this topic, nor have I seen mention of it in the patch notes, I decided to reconnect my ISB7005 back to the RBS50. So far it seems to be holding up well. I would of course feel better knowing something was done to improve this area of IGMP support in the satellite.
What was the version of FW prior to what you have loaded now?
Nothing in the release notes?
FURRYe38 wrote:
What was the version of FW prior to what you have loaded now?
Nothing in the release notes?
I've stepped through most of them, but the better question is what was the last version I tested this on, and I'm thinking .44, but not 100% sure.
As to the release notes question, I hadn't spotted anything that seemed connected to the reported issue.Might ask Blanca_O to see if she can pull some infomation. I guess if v30 is working when it didn't work before. Anything could have snuck in.
gr8sho wrote:FURRYe38 wrote:
What was the version of FW prior to what you have loaded now?
Nothing in the release notes?
I've stepped through most of them, but the better question is what was the last version I tested this on, and I'm thinking .44, but not 100% sure.
As to the release notes question, I hadn't spotted anything that seemed connected to the reported issue.
