I find it ridiculous that you all have to jump over hoops and waste a lot of time fixing Netgear's problem. One of my satellites is literally fried and Netgear isn't doing anything about it.
You have to turn off all of the features they offer just to make it reliable? C'mon.
I find it ridiculous that you all have to jump over hoops and waste a lot of time fixing Netgear's problem. One of my satellites is literally fried and Netgear isn't doing anything about it.
You have to turn off all of the features they offer just to make it reliable? C'mon.
If you wanna keep the 2.4hgz at 25% it might be worth trying third satellite. When your iPhone is totally dropping WiFi it means either WiFi assist is knocking it off if you have it on or you are out of range where it can’t see your router. So in your case you may need to put one satellite in the other corner to get the nearby coverage. I have 2 satellites one in each corner and the router in the front room.
I have reached out to Netgear via email, twitter, and here on the board with no response.
My "dead" satellite is just that. Dead. No light other than green LED on the back (the working satellite has a white LED on). It won't show up wired or wireless. I have soft and hard-cycled/reset it a dozen times or more now.
I replied before, WiFi Assist was a good hypothesis, but given that it’s only used 216KB of data, it’s not that.
Even if it were WiFi Assist, it wouldn’t be a signal issue. I’ve tested my 5Ghz signal thoroughly and it’s very strong. This is the thing I love about the Orbi. No signal issues.
The only thing it could be is iOS detecting a lack of internet access through the WiFi fabric. Which I know isn’t it either, as long as the 216KB is accurate, that’s vanishingly small for the amount of internet activity I’ve done after being disconnected from WiFi.
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
I have reached out to Netgear via email, twitter, and here on the board with no response.
My "dead" satellite is just that. Dead. No light other than green LED on the back (the working satellite has a white LED on). It won't show up wired or wireless. I have soft and hard-cycled/reset it a dozen times or more now.
I replied before, WiFi Assist was a good hypothesis, but given that it’s only used 216KB of data, it’s not that.
Even if it were WiFi Assist, it wouldn’t be a signal issue. I’ve tested my 5Ghz signal thoroughly and it’s very strong. This is the thing I love about the Orbi. No signal issues.
The only thing it could be is iOS detecting a lack of internet access through the WiFi fabric. Which I know isn’t it either, as long as the 216KB is accurate, that’s vanishingly small for the amount of internet activity I’ve done after being disconnected from WiFi.
Out of curiosity... have you tried going into WiFi settings on your phone and "Forget This Network", power cycle phone and then connecting back to the network again?
The reason I am saying you might want to try third satellite is because on phones the 5ghz signal is small terms sucks. You might be testing with devices that have more power where Iphone is failing to make up the difference. I honestly don’t have this issue and I have 3 iPhones and 2 iPads. My WiFi only drops when the router is shut off or not broadcasting. Other than that I haven’t had these issues since I added the 3rd satellite. I was fine with two but the way my house is it has to go through many walls to hit my back yard. Now I have coverage front yard and back yard and all over the house.
Update on the Rainmachine...I added it to a static IP and rebooted the router (remotely)..it is now assigned the static IP and I can only again connect via the Rainmachine app. We will see if the issue crops up in a day or two like it did before with a static IP.
Hopefully Netgear is reading this so they can fix these beta firmware issues. Other than that one device it seems to be working well for me.
Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Now that my Rainmachine is flaking out again my router log is filled with these messages again and again and again:
[DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:25:07 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:25:04 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:25:01 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:58 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:55 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:52 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:49 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:46 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:43 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:40
Rainmachine? The only reason I ask is that when I do a MAC address vendor lookup the MAC you listed, it comes back as "
TP-LINK TECHNOLOGIES CO.,LTD. "
TP-link may very well make the wireless module for Rainmachine but I am just curious.
Now that my Rainmachine is flaking out again my router log is filled with these messages again and again and again:
[DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:25:07 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:25:04 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:25:01 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:58 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:55 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:52 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:49 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:46 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:43 [DHCP IP: 192.168.1.105] to MAC address 98:de:d0:12:26:00, Tuesday, March 27, 2018 14:24:40
Rainmachine? The only reason I ask is that when I do a MAC address vendor lookup the MAC you listed, it comes back as "
TP-LINK TECHNOLOGIES CO.,LTD. "
TP-link may very well make the wireless module for Rainmachine but I am just curious.
Yup, the Rainmachine uses just a usb plug in wifi adapter that they supply...it looks a bit silly but it works. Never had a problem until this firmware. Hopefully a static IP will fix it.
I'm now at 4 days and a couple of hours since loading the beta firmware. Was stable before though. All good so far and one thing I've noticed that seems to have improved is roaming from router to satellite and back again. Before it seemed to hang on to a slower connection. Always at near max speed now.
This may be a good recommendation on beta firmware, but NG - and any other company - can't afford to put out firmware updates that require a factory reset. 98% of folks - the non-tech geeks that aren't on this forum like us 🙂 - will not spring for it, and shouldn't. Not saying you are wrong; it's a good recommednation. But again, for most household users, a full factory reset should would be unacceptable...
This may be a good recommendation on beta firmware, but NG - and any other company - can't afford to put out firmware updates that require a factory reset. 98% of folks - the non-tech geeks that aren't on this forum like us 🙂 - will not spring for it, and shouldn't. Not saying you are wrong; it's a good recommednation. But again, for most household users, a full factory reset should would be unacceptable...
Model: RBK53| Orbi Router + 2 Satellites Orbi WiFi System
I am on 2.1.2.18 - will try the new beta this week as well and report back (also one of the few that has not had any issues with the current 2.1.2, and never went backwards)
I for one see no need to scrap later releases. I have had excellent results from the 2.1 firmware. I am currently running an RBR 50 and RBS 50 on the 2.1.3 beta and an RBS40 on the 2.1.2.18. The RBS50 is connected by Wi-Fi backhaul and Ethernet for the 40. All is working fantastically with SweetSpots speeds above 800 throughout the house. I have all the options set apart from daisy chaining and I get great hand offs as I roam round the house. For the record I didn’t factory reset and the only snag I have had is my RBS50 connected to the RBS40 upon restarting after upgrade despite being closer to the router; hence I unselected daisy chaining.
I see no reason to scrap either. This beta and also the .18 builds ran fine for me and I have had no issues. So, scrapping a lot of work because of a pocket of user issues will just probably break things for those of us that are working. Not trying to down play the problems some users are having, but digging in and figuring out what makes the users who are having problems different is the way to solve this.
I would also be curious if electrical issues in a home can cause some of the user problems and reboots... inconsistent power can cause a lot of odd problems. Just a small power blip could be enough to cause a router to reboot or reset. I have all mine on small UPS boxes so if the power were to go out or flicker (which happens in CT from time to time in the winter or during heavy winds), that I don't have to worry about any of my network components going up or down or rebooting. Well... and if the power goes out for a few minutes and my whole house UPS isn't fired up yet... internet is still up and I don't have anyone complaining about no wifi. Heh.
Well, I had some issues getting the ethernet backhaul working, but doing the satellite only reset fixed that issue. However, today, out of the blue, I had issues crop up: First, one of my satellites just dropped off. Didn't show up in config any longer, and wouldn't connect. Tried doing a reboot, no luck, reset, no luck. Had to unplug ethernet backhaul, reconnect from scratch as a wireless backhaul. Once this came up, it dumped the network, causing all devices to lose connectivity (much like plugging in the ethernet backhaul did before) only no ethernet connected. Powered off the satellite, no luck, router still borked. Powered off the router, then back on again. Router came back up, but now my 2nd satellite is gone. Nothing in config at all, and in fact it's now showing an orbi73 SSID, so it had complete reset itself. I did a manual satellite add and it connected back in. Now, I'm back up on router + 2 satellites, but all on wireless backhaul.
Yes, when in a normal circumstance and using official non beta FW, factory resets shouldn't be needed. Only needed as a troubleshooting step. I presume NG intend is to ensure user configurations are kept and persistent thru FW upgrades. However, for these Beta builds and since users have seen so many different experiences, it's best to help narrow down some issues and give the beta FW a good chance of getting set up and installed. A factory reset on the entire system and set up from scratch is highly recommended at this stage and when using Beta FW. Seen many users still complain about a problem after updating FW and they didn't do a reset. After a reset and setup again, problem went away. Also helps weed out bad-configurations as well. So for now, lets factory reset if your using the Beta FW. Lets give the system the best chance to be some solid and working well.
This may be a good recommendation on beta firmware, but NG - and any other company - can't afford to put out firmware updates that require a factory reset. 98% of folks - the non-tech geeks that aren't on this forum like us 🙂 - will not spring for it, and shouldn't. Not saying you are wrong; it's a good recommednation. But again, for most household users, a full factory reset should would be unacceptable...
Seems that v2.1.3.4 is the most stable out of anything so far. I presume once this has been tested fully, NG may push to this to auto FW updates depending if they need to make any other FW changes before then.
Well, I had some issues getting the ethernet backhaul working, but doing the satellite only reset fixed that issue. However, today, out of the blue, I had issues crop up: First, one of my satellites just dropped off. Didn't show up in config any longer, and wouldn't connect. Tried doing a reboot, no luck, reset, no luck. Had to unplug ethernet backhaul, reconnect from scratch as a wireless backhaul. Once this came up, it dumped the network, causing all devices to lose connectivity (much like plugging in the ethernet backhaul did before) only no ethernet connected. Powered off the satellite, no luck, router still borked. Powered off the router, then back on again. Router came back up, but now my 2nd satellite is gone. Nothing in config at all, and in fact it's now showing an orbi73 SSID, so it had complete reset itself. I did a manual satellite add and it connected back in. Now, I'm back up on router + 2 satellites, but all on wireless backhaul.
I upgraded to beta and factory reset the satellites, but didn't factory reset the router. If I need to factory reset the router to make this work, then it's not a valid image in my opinion and I'll move on to another product; I have too many devices on my network and don't use 10. addressing so a factory reset is VERY time consuming to restore.
I waited more than 15 minutes, all with complete network failure by the way, and still no luck. As I mentioned in the message, the router didn't even show the satellites as devices any longer, then weren't 'disconnected' they were gone completely.
