NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New to Orbi - RBK50 / RBR50 V2 - rebooting often
Hi All
new to orbi and coming from a d7000
Have the RBK50 kit. Live in New Zealand.
Have set up the router, did a factory restore and installed 2.5.1.8 firmware.
Ran the unit without the satellite at all. so we are talking a stand alone rbr50 essentially.
Went through and set up my device allowed DHCP starting at 192.168.1.10, set some reserved addresses for house alarm, printer, nas etc ( all in the .2 - .9 range ) also set up other items to have some specific reserved addresses higher up..
Had to do a manul configuration to work with our fibre provider, PPPOE
Have Enabled vlan bridge by tag group with ID 10. All required for spark in NZ.
Device connects fine, as do all the wireless and wired devices.
On 2.5.1.8 i found the router would reboot often im talking every 5 - 20 minutes, i then manually upgraded to 2.5.1.16 as that wasnt showing as an option, same problem, rolled back to 2.3.5.30 ( based on reading here ) had a stable connection for about 8 hours, now the device was showing a firmware upgrade to 2.5.1.16, so i did that using the auto update, seemed to work better however rebooting started again after 1 hour, ended up rolling back to 2.3.5.30 which is where i currently sit,
The device has rebooted after 3 hours this time, and right now has been running for 3. i did change the 2.4ghz band to site on 6 rather than auto as i read there were issues with that?
my device is also showing it wants me to upgrade to 2.5.1.16 which for now im not doing.
So ive read a bit about the device rebooting. this is a V2 model, could that come with issues? when its running it runs fine, speed and coverage is good, id be very happy with it, but when its rebooting often its infuriating..
could anyone tell me if setting up reserved addresses is a problem for this unit? im not a router expert, i have a mix of devices which dont use dhcp and for these devices i notice that they dont appear in my attached devices unless i reserver the same IP for them? for the rest i normally allow DHCP assignment, and just reserve the address for that mac address.
The logs are all but useless as they just show that the device has re initialised and the uptime is reset, i know there is a debug.htm page and wondering if i need to be capturing logs in there to determine whats going on? Does netgear look at those , could they help.
So really just looking for some help to stop rebooting. im guessing its down to a device trying to connect and crashing it some how..
hope you can help or provide some next steps i can review.
THank you
40 Replies
Hi
Yeah cant say i agree sorry, there is no real need to upgrade, i already tried .16 and had issues.. what my system thinks it wants and what works are two different things :)
GregCook wrote:Hi
Yeah cant say i agree sorry, there is no real need to upgrade, i already tried .16 and had issues.. what my system thinks it wants and what works are two different things :)
I think you're missing my point.................which is stop doing manual updates. The only reason I mentioned the upgrade at this point is that I've read of some success with the other version. Your only other option (other than sit there and suffer) would be to revert back to a previous stable version.
Good luck
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-router
Any Wifi Neighbors near by? If so, how many?Try enabling Beamforming and MIMO(MIMO may or maynot be needed) and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Armor, Circle, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Set Short preamble instead of Long preamble modes. Save settings and reboot the router and satellite(s).Above suggestions working:
https://community.netgear.com/t5/Orbi/Throttling-Devices-RBK53/m-p/1858561/highlight/true#M81925
https://community.netgear.com/t5/Orbi/Orbi-Satellite-Drop-Connection-time-to-time/m-p/1890341/highlight/true#M88026You can try Voxels FW for Orbi:
https://community.netgear.com/t5/Orbi/Voxels-FW-available-for-50-series-Orbi-only-available/m-p/1883615#
You can revert back to stock FW if it doesn't work out for you.For doing any FW updates, I recommend avoiding the auto update FW section of the router. Many posters have had problems with this feature and is not stable to use. Seems to break systems or causes problems more than anything else.
First manually download the RBS and RBR FW files from here.
http://kb.netgear.com/en_US/000061838/
Unpack the FW from the .zip files.
Use a wired PC for this process. Safari(Mac), IE11, Firefox or Opera browsers are recommended.
Log into the RBSs web page and send the FW file there first.
Then send the RBR FW file lastly.
Factory reset the RBS and RBR and setup from scratch. After makeing sure the system works after setting up, be sure to make a backup configuration to file for safe keeping. This saves time if a reset is needed again.
GregCook wrote:Hi All
new to orbi and coming from a d7000
Have the RBK50 kit. Live in New Zealand.
Have set up the router, did a factory restore and installed 2.5.1.8 firmware.
Ran the unit without the satellite at all. so we are talking a stand alone rbr50 essentially.
Went through and set up my device allowed DHCP starting at 192.168.1.10, set some reserved addresses for house alarm, printer, nas etc ( all in the .2 - .9 range ) also set up other items to have some specific reserved addresses higher up..
Had to do a manul configuration to work with our fibre provider, PPPOE
Have Enabled vlan bridge by tag group with ID 10. All required for spark in NZ.
Device connects fine, as do all the wireless and wired devices.
On 2.5.1.8 i found the router would reboot often im talking every 5 - 20 minutes, i then manually upgraded to 2.5.1.16 as that wasnt showing as an option, same problem, rolled back to 2.3.5.30 ( based on reading here ) had a stable connection for about 8 hours, now the device was showing a firmware upgrade to 2.5.1.16, so i did that using the auto update, seemed to work better however rebooting started again after 1 hour, ended up rolling back to 2.3.5.30 which is where i currently sit,
The device has rebooted after 3 hours this time, and right now has been running for 3. i did change the 2.4ghz band to site on 6 rather than auto as i read there were issues with that?
my device is also showing it wants me to upgrade to 2.5.1.16 which for now im not doing.
So ive read a bit about the device rebooting. this is a V2 model, could that come with issues? when its running it runs fine, speed and coverage is good, id be very happy with it, but when its rebooting often its infuriating..
could anyone tell me if setting up reserved addresses is a problem for this unit? im not a router expert, i have a mix of devices which dont use dhcp and for these devices i notice that they dont appear in my attached devices unless i reserver the same IP for them? for the rest i normally allow DHCP assignment, and just reserve the address for that mac address.
The logs are all but useless as they just show that the device has re initialised and the uptime is reset, i know there is a debug.htm page and wondering if i need to be capturing logs in there to determine whats going on? Does netgear look at those , could they help.
So really just looking for some help to stop rebooting. im guessing its down to a device trying to connect and crashing it some how..
hope you can help or provide some next steps i can review.
THank you
- Thank you. This is the first sensible reply. I’ll report back on the details you asked for. In terms of locations the devices are about 30 feet. But You’ll also notice I said this was happening without satellites connected or turned on. So the distance shouldn’t be a factor .
More details to comeKeep us posted.
GregCook wrote:
Thank you. This is the first sensible reply. I’ll report back on the details you asked for. In terms of locations the devices are about 30 feet. But You’ll also notice I said this was happening without satellites connected or turned on. So the distance shouldn’t be a factor .
More details to come
