This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
No issues. The only problem I had in the beginning was when I tried to have an Ethernet Backhaul. I plugged the Satelitte in to a Switch that is in the Office the other end of the house (Fibre and Coms cupboard is in the centre of the house, Orbi Router is there) other WIFI access points I had in the Comms area the WIFI was some patchy down near the office that is why I thought I would go for a MESH system (rather than multiple APs).
Once I got the Ethernet Backhaul sorted by having the LAN cable between the comms room and the office into Orbi Satelitte then my switch to one o the spare ports and I have had no drop offs, Never needed to reboot either the Orbi Router or Satelitte and it has been stable for over 2 weeks now. (It was stable before with the WIFI backhaul)
Just one question it does seem that the Orbi Satelittle has a Decent Wireless Connection back to the Router, Connecting at 1700Mbps. Is the Ethernet (Gbps) Actually slower? And better to stay with the WIFI Backhaul and drop the LAN link between the 2 rooms? Or since the number of devices run from the office the ethernet backhaul is better (2x NAS, 1x Printer, 1x iMac, Then another bedroom next door for Apple TV and PS4)
Could always go back to LAN direct to the switch and just have the Satelitte as standalone with Wifi backhaul
The wireless backhaul throughput will always be less than Ethernet.
1. Wireless throughput is, at best, 50%-60% of the link rate, due to protocol overhead. So, divide the 1700 Mbps by at least one half.
2. In practice you will not get a 1700 Mbps link rate, because you will have walls between router and satellite. I've measured no more than 575 Mbps throughput across my Orbi backhaul.
3. Ethernet throughput is always ~940 Mbps.
4. Wireless is a shared medium. If you have more than one satellite, they must share the backhaul throughput. With Ethernet, each satellite gets a dedicated 940 Mbps back to the router.
5. Ethernet has lower latency and is more stable over time. Wireless is subject to interference that you cannot control.
The wireless backhaul throughput will always be less than Ethernet.
1. Wireless throughput is, at best, 50%-60% of the link rate, due to protocol overhead. So, divide the 1700 Mbps by at least one half.
2. In practice you will not get a 1700 Mbps link rate, because you will have walls between router and satellite. I've measured no more than 575 Mbps throughput across my Orbi backhaul.
3. Ethernet throughput is always ~940 Mbps.
4. Wireless is a shared medium. If you have more than one satellite, they must share the backhaul throughput. With Ethernet, each satellite gets a dedicated 940 Mbps back to the router.
5. Ethernet has lower latency and is more stable over time. Wireless is subject to interference that you cannot control.
No issues. The only problem I had in the beginning was when I tried to have an Ethernet Backhaul. I plugged the Satelitte in to a Switch that is in the Office the other end of the house (Fibre and Coms cupboard is in the centre of the house, Orbi Router is there) other WIFI access points I had in the Comms area the WIFI was some patchy down near the office that is why I thought I would go for a MESH system (rather than multiple APs).
Once I got the Ethernet Backhaul sorted by having the LAN cable between the comms room and the office into Orbi Satelitte then my switch to one o the spare ports and I have had no drop offs, Never needed to reboot either the Orbi Router or Satelitte and it has been stable for over 2 weeks now. (It was stable before with the WIFI backhaul)
Just one question it does seem that the Orbi Satelittle has a Decent Wireless Connection back to the Router, Connecting at 1700Mbps. Is the Ethernet (Gbps) Actually slower? And better to stay with the WIFI Backhaul and drop the LAN link between the 2 rooms? Or since the number of devices run from the office the ethernet backhaul is better (2x NAS, 1x Printer, 1x iMac, Then another bedroom next door for Apple TV and PS4)
Could always go back to LAN direct to the switch and just have the Satelitte as standalone with Wifi backhaul
The wireless backhaul throughput will always be less than Ethernet.
1. Wireless throughput is, at best, 50%-60% of the link rate, due to protocol overhead. So, divide the 1700 Mbps by at least one half.
2. In practice you will not get a 1700 Mbps link rate, because you will have walls between router and satellite. I've measured no more than 575 Mbps throughput across my Orbi backhaul.
3. Ethernet throughput is always ~940 Mbps.
4. Wireless is a shared medium. If you have more than one satellite, they must share the backhaul throughput. With Ethernet, each satellite gets a dedicated 940 Mbps back to the router.
5. Ethernet has lower latency and is more stable over time. Wireless is subject to interference that you cannot control.
That was my thoughts as well.
That is always what I have believed, that is why I wanted the Ethernet Backhaul
But recently I heard a so called "expert" say different, at the time I thought he was full of crap as a few things didnt sound right. But it put some doubt in place.
OK, you'll be find. I put that satellite down behind where your two 8 port switches are on my system. Working well for me on un-managed switches. Just making sure what you had. Been issues with Orbi and Managed switches. You'll be good.
1) Is the Vodafone Hub in bridge mode? Also what is the model number of the Vodafone Hub?
2) Without an understanding of traffic flow and load, it is difficult to make an accurate assessment. However it looks like the Orbi Satellite is going to be overloaded by the devices on the two 8-port switches and the Wi-Fi devices.
3) Also note you have no QoS.
1) It is the Vodafone Ultra Hub.
And it is in Router Mode. I have the Orbi as a static IP and in DMZ Then all my devices behind that. 2) How will the Satellite be over loaded? It has been running fine for over 2 weeks like this.
3) How can you tell I have no QoS just by looking at my network map?
