NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HORRIBLE wifi speed but ULTRAFAST via ethernet ports
Issue: Cable modem (SPECTRUM) delivering 350+ Mbps INBOUND with near equal throughput (measured via FAST.COM) to devices via Ethernet ports on two satellites. Wifi throughput, HOWEVER, typically...
Sad that the RBS40V is not 'playing nice'. I have two of them with one RBR50 and one RBS50. "No problem."
The major issue with using a router to extend WiFi service to a device is that routers must be connected using an Ethernet cable. (this would apply to both the Netgear RBR50 and the Linksys router.) If you can run a cable for the router, that same cable would have serviced the camera.
If that camera absolutely requires an Ethernet connection, I would look at an inexpensive WiFi Extender which will connect to the home network over WiFi and provide an Ethernet port for the camera, such as the Netgear EX3700 (under $30 on Amazon).
CrimpOn wrote:If that camera absolutely requires an Ethernet connection, I would look at an inexpensive WiFi Extender which will connect to the home network over WiFi and provide an Ethernet port for the camera, such as the Netgear EX3700 (under $30 on Amazon).
I had one of those at one time but never was satisfied with its performance. Tried to see if I still have it but it isn't in my "spares" box so I must have tossed it.
So I just purchased a "like new" RBS50 off of ebay for $100 that should arrive by the weekend. Hopefully that will put this issue to bed once and for all.
Sounds like a good solution. I have an Orbi satellite in my garage with an 8-port PoE switch connected to it. Got tired of finding electrical outlets for cameras.
CrimpOn wrote:Sounds like a good solution. I have an Orbi satellite in my garage with an 8-port PoE switch connected to it. Got tired of finding electrical outlets for cameras.
Well, nothing would bring the wifi back to where it was yesterday. I did 2 factory resets.One with the pin and one from the Orbi interface and neither restored wifi signals.
I finally decided to use the spare RBR50 instead of selling it. So far I was able to update the firmware and restore the configuration, make adjustments to the access control devices and add the 2 satellites.
It is extremely important to allow the RBS50's time to assimilate into the network individually. For whatever reason, the first RBS50 produced 2 additional mac addresses in addition to the one (9C:C9:EB:2C:77:BF) listed at the top of attached devices. They all listed the same IP address but 3 total unique mac addresses.
I'm posting an image of access control with those 2 additional mac addresses associated with 192.168.7.8
It takes the system about 5 to 10 minutes before those extras listings that appear in access control after adding an RBS50 disappear. Once that happens the mesh provides FAT bandwith for my wifi devices again. Pretty much what the Ethernet ports are providing.
I'm apprehensive of adding another satellite and almost wish I'd just bought a new camera now that everything is smoking fast again. If I add the 3rd RBS50 and everything goes south again I'm going to blow a gasket. 😁I received the new RBS50 and had a bit of trouble adding it via the Orbi app. So I decided to update the firmware manually since I already had 2.7.4.24. However, when I logged directly, it spit out an error that this wasn't the correct firmware etc...
I doubled checked, tried again and ended up using the router interface to automatically download and update.
It rebooted and all 3 satellites show GOOD backhaul and my wifi devices are still consistently pulling down 300+Mbps.
HOORAY!!I sometimes get tangled up by confusing the router firmware file with the satellite firmware file. After all, they differ by only one letter ("r" or "s") Click the wrong one, and "incorrect".
CrimpOn wrote:I sometimes get tangled up by confusing the router firmware file with the satellite firmware file. After all, they differ by only one letter ("r" or "s") Click the wrong one, and "incorrect".
Doh! I resemble that remark. I forgot they were different. If the Orbi interface hadn't worked I would have eventually discovered what I forgot.
😁