NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but ...
IF the satellite wired back haul is working directly conntect to the router with just a LAN cable in between for this test, it should work at its remote location. Only items that would impact this is faulty cabling in between, connectors, or managed switches. Need to rule out each one and try to narrow down where the Satellite is failing when it's placed in his desured remote location...
If you get it working in the temp location directly to the router for wired back haul, then power OFF, place in remote location and power ON, it should connect in the same wired back haul and not need any reconfiguration. Should just work if the cabing and connections are good in between.
Happen to have a long lan cable that you can temporarily run between the router and remote location?
I can tell you that wired back haul is working in this FW version.
turns2stone wrote:
FURRYe38 wrote:Not really, you maybe already hitting the limits of your wifi devices. Just because they can connect at 866Mb doesn't mean the data can flow that fast as well. Doesn't work like that. Connection rates differ from data flow rates. The Connection rates are just connection rate speeds between the devices and wireless AP/router only. Mfrs have different designes and depending on chips used and implemented, data rates will differ and some are limited by the chips they use or implement. Honestly, is 866Mb data rate really needed on a phone, stop and think, what are you doing one thing at a time on ap phone that would need that kind of bandwidth? FB? text? voice? Nothing on a phone needs that kind of data rate. Streaming compressed video even doesn't need that kind of data rate. Theres many connection however on phones, apps and browsers and all this combine needs some bandwidth. That were the connection rate comes in. Wider connetion rate, more app, video and browser data can share the pipe.
My current v2.1.3.x FW has working wired back haul. Zero issues so far.
All fair points and I understand about theoretical maximums and other factors. I guess I'm more interested in getting wired backhaul to work because I spend a fair amount of effort putting an Ethernet drop to my satellite locations. Also, I'm just trying to achieve the most consistent performance possible, which I assume Ethernet backhaul would provide.
Considering that I can get a satellite to connect via Ethernet backhaul when directly connected to the LAN ports on the RBR50, do you have any final tips for getting it to work before I give up for a while? I've tried establishing the connection directly to the RBR50, then powering off the RBS50 and moving to its real home, but no luck. I've tried (I think) every combination of power cycling the RBS50 with/without the Ethernet cable plugged in.
FURRYe38 wrote:IF the satellite wired back haul is working directly conntect to the router with just a LAN cable in between for this test, it should work at its remote location. Only items that would impact this is faulty cabling in between, connectors, or managed switches. Need to rule out each one and try to narrow down where the Satellite is failing when it's placed in his desured remote location...
If you get it working in the temp location directly to the router for wired back haul, then power OFF, place in remote location and power ON, it should connect in the same wired back haul and not need any reconfiguration. Should just work if the cabing and connections are good in between.
Happen to have a long lan cable that you can temporarily run between the router and remote location?
I can tell you that wired back haul is working in this FW version.
I agree that it *should* work, when I power off the satellite and move it to it's regular location and reconnect Ethernet. Not sure what a long LAN cable to the regular would accomplish? I realize you got it working, and appreciate the help. But based on how just plugging in a LAN cable to a satellite can bring down the whole network, I don't think wired backhaul is very stable at this point.
How long did you wait before checking the network. 5 minutes should be long enough.
Reason for trying a long cable is to see if remote location with long cable works vs your installed cable infrastructure.
If the Satellite is working directly, then not in it's remote location, this means something in between is a cause or causing the satellite not to work right or mis operate. This points to a cabling problem between the remote location and router.
turns2stone wrote:
FURRYe38 wrote:IF the satellite wired back haul is working directly conntect to the router with just a LAN cable in between for this test, it should work at its remote location. Only items that would impact this is faulty cabling in between, connectors, or managed switches. Need to rule out each one and try to narrow down where the Satellite is failing when it's placed in his desured remote location...
If you get it working in the temp location directly to the router for wired back haul, then power OFF, place in remote location and power ON, it should connect in the same wired back haul and not need any reconfiguration. Should just work if the cabing and connections are good in between.
Happen to have a long lan cable that you can temporarily run between the router and remote location?
I can tell you that wired back haul is working in this FW version.
I agree that it *should* work, when I power off the satellite and move it to it's regular location and reconnect Ethernet. Not sure what a long LAN cable to the regular would accomplish? I realize you got it working, and appreciate the help. But based on how just plugging in a LAN cable to a satellite can bring down the whole network, I don't think wired backhaul is very stable at this point.
FURRYe38 wrote:How long did you wait before checking the network. 5 minutes should be long enough.
Reason for trying a long cable is to see if remote location with long cable works vs your installed cable infrastructure.
If the Satellite is working directly, then not in it's remote location, this means something in between is a cause or causing the satellite not to work right or mis operate. This points to a cabling problem between the remote location and router.
I waited at least 30 minutes. I guess I still don't understand the long cable suggestion. If it works via a "short" cable, of course it's going to work if I use a 50ft cable and just move the satellite to another room away from the router.
I still hesitate to believe it's a cable issue. I've tried wired backhaul in 3 different rooms, with two different satellites. Other network devices negotiate full duplex 1000Mbp/s when connected to the same LAN jack that I'm attempting to use with the Orbi satellites. I've tried a variety of patch cables, all "new" quality Cat6 cables from Belkin, etc.
Also, I forgot to mention.. direct connection of the satellite to to the router does not work 100% of the time. Maybe 50%? Which again is why I think there is something inherent to the firmware that chokes on Ethernet backhaul based on certain circumstances.
5 minutes is all thats needed after conneting the cable to the satellit. If its longer and your not seeing the BLUE LED at the top, then something is wrong.
Long cable should simulate whats in the walls and such. I'm trying to establish with your satellite that it if it works short cable in temp location, it will work in remote location with longer cable. If so then this isn't a satellite or FW issue, this is a in wall infrastructure issue that needs to be reviewed. Cable continuity and connections should be tested and checked fully.
I don't recommend anything Belkin...your choice though. I get most of my cabling from either DeepSurplus or MonoPrice.