NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rhester72
Jul 11, 2017Virtuoso
Firmware V1.12.0.18 Discussion
This does indeed appear to be based on (identical to?) the last private beta V1.12.0.16 and has been released to the public. Hope it helps!
Guest mode AP isolation finally works 100% over IPv4...
- Jul 11, 2017
New Features and Enhancements:
- Supports ReadySHARE Printer for Orbi devices that are equipped with a USB port
- Updated the OrbiOS API to v3.14
Bug Fixes:
- Fixes the iOS disconnection issue.
- Fixes the Dropcam disconnection issue.
- Fixes the convergence issue when an Ethernet connected device moves from one Orbi to another.
- Fixes the issue where the Orbi app can’t find the Orbi router if the router is using IPv6 and is in AP mode.
- Fixes the issue where the Orbi app can’t display more than 20 connected devices.
- Fixes the issue where the installation assistant might not display if the device is connected to the Orbi network wirelessly.
- Fixes the issue where the 2.4 GHz backhaul setting is disabled if the fronthaul MU-MIMO and TxBF is disabled.
- Fixes the issue where IPv6 devices on the guest network can access the Orbi router’s web GUI.
- Includes security fixes for the following security vulnerabilities:
PSV-2016-0133, PSV-2017-0607, PSV-2017-0615, PSV-2017-0736, PSV-2017-2190
Download Link:
RBR50 - http://www.downloads.netgear.com/files/GDC/RBK50/RBR50-V1.12.0.18.zip
RBS50 - http://www.downloads.netgear.com/files/GDC/RBK50/RBS50-V1.12.0.18.zip
martyfp
Aug 23, 2017Luminary
A new beta realse software will not be published, because just recently a new firmware has been published that solved the problem !!
If the new firmware is about to released then the beta program will close and they will stop sending out the beta code. could that be the correct interpretation?
RogerSC
Aug 24, 2017Virtuoso
martyfp wrote:
A new beta realse software will not be published, because just recently a new firmware has been published that solved the problem !!
If the new firmware is about to released then the beta program will close and they will stop sending out the beta code. could that be the correct interpretation?
Yes, if it was a Beta program for a major release. I think that what's happening this time around is that some users that have reported problems are getting Beta test firmware. Not sure how those users are selected, generally, though, if you've reported an issue, and worked with support in supplying the information that they've requested, you're likely to get Beta firmware to see if it resolves the particular problems that you reported. Usually, in that case, each user that receives Beta firmware will be asked not to share it, so unless someone violates that agreement, it will not get shared. I've been through this several times with Netgear, and this process has been used to verify fixes for inclusion in the next release or a later release depending on how many users are affected by the problem and how serious the problem is.
I'm hoping that this is leading to a new firmware version soon, assuming that the Beta test firmware does resolve the problems that users are having.
- gbjacksonAug 25, 2017Apprentice
RogerSC wrote:
martyfp wrote:A new beta realse software will not be published, because just recently a new firmware has been published that solved the problem !!
If the new firmware is about to released then the beta program will close and they will stop sending out the beta code. could that be the correct interpretation?
Yes, if it was a Beta program for a major release. I think that what's happening this time around is that some users that have reported problems are getting Beta test firmware. Not sure how those users are selected, generally, though, if you've reported an issue, and worked with support in supplying the information that they've requested, you're likely to get Beta firmware to see if it resolves the particular problems that you reported. Usually, in that case, each user that receives Beta firmware will be asked not to share it, so unless someone violates that agreement, it will not get shared. I've been through this several times with Netgear, and this process has been used to verify fixes for inclusion in the next release or a later release depending on how many users are affected by the problem and how serious the problem is.
I'm hoping that this is leading to a new firmware version soon, assuming that the Beta test firmware does resolve the problems that users are having.
This is essentially correct. RMA'd one satellite, then could't get the replacement to work, got nowhere with tech support, so wrote a 1 star Amazon review indicating that while I really wanted to like the product, the 1.12 firmware pretty clearly broke it. NetGear got in touch, asked for a bunch of logs (which are hard to find, as they are not accessible through the basic router or satellite interface), lists of connected devices, network info, third party software (inSSIDer) screen shots, etc... Uploaded all of that to them, and a few days later they sent me a demo version 2.0.0.62 of the firmware to try. I'm reluctant to share it, as (i) they know who I am, and (ii) I don't want to be responsible for further screwing up anyone else's system. I have told them that the firmware appears to be working for me (it's now been stable for 3 or 4 days), and asked them for an ETA on a more general release. I have also asked whether a new version would include the ability to disable automatic updates. Netgear support said last night that the ability to disable auto updates would be included in a version of the 2.0 firmware, although it wasn't clear if it was going to be in the first roll out.
To answer someone else's question, I do not have a Samsung device of any sort on my network, so cannot speak to whether the new firmware makes a difference there. All of devices that I do have connected (both wired and wirelessly), however, are working - even the device the controls the temperature of my barbecue grill.
- Dustin278Aug 25, 2017Apprentice
Yes, if it was a Beta program for a major release. I think that what's happening this time around is that some users that have reported problems are getting Beta test firmware. Not sure how those users are selected, generally, though, if you've reported an issue, and worked with support in supplying the information that they've requested, you're likely to get Beta firmware to see if it resolves the particular problems that you reported. Usually, in that case, each user that receives Beta firmware will be asked not to share it, so unless someone violates that agreement, it will not get shared. I've been through this several times with Netgear, and this process has been used to verify fixes for inclusion in the next release or a later release depending on how many users are affected by the problem and how serious the problem is.
I'm hoping that this is leading to a new firmware version soon, assuming that the Beta test firmware does resolve the problems that users are having.
This is essentially correct. RMA'd one satellite, then could't get the replacement to work, got nowhere with tech support, so wrote a 1 star Amazon review indicating that while I really wanted to like the product, the 1.12 firmware pretty clearly broke it. NetGear got in touch, asked for a bunch of logs (which are hard to find, as they are not accessible through the basic router or satellite interface), lists of connected devices, network info, third party software (inSSIDer) screen shots, etc... Uploaded all of that to them, and a few days later they sent me a demo version 2.0.0.62 of the firmware to try. I'm reluctant to share it, as (i) they know who I am, and (ii) I don't want to be responsible for further screwing up anyone else's system. I have told them that the firmware appears to be working for me (it's now been stable for 3 or 4 days), and asked them for an ETA on a more general release. I have also asked whether a new version would include the ability to disable automatic updates. Netgear support said last night that the ability to disable auto updates would be included in a version of the 2.0 firmware, although it wasn't clear if it was going to be in the first roll out.
To answer someone else's question, I do not have a Samsung device of any sort on my network, so cannot speak to whether the new firmware makes a difference there. All of devices that I do have connected (both wired and wirelessly), however, are working - even the device the controls the temperature of my barbecue grill.
I was able to install the Beta firmware last night Beta 2.0.0.62-debug - Did not fix the Wifi issue on my S8 from what I could tell but was only able to try it for less than 10 minutes last night and started to drop connection within 5 minutes so I went back to my Guest network until I have more time to test.. Starting to think this is more of a Samsung/Android thing after googling around..
- Killou92Aug 26, 2017Tutor
I don't see problem of sharing a beta firware thats ridiculous! Can someone upload the firmware on dropbox or something?
Thanks
- Retired_MemberAug 26, 2017When you receive the beta you specifically sign an agreement saying you will not distribute.
- albertsAug 26, 2017Star
I left my experiences with the Orbi on the german amazon site with a 1 star review.
Their answer is pure TECHNICAL FAKE NEWS. Netgear states they have already published the 1.12.0.20 software for the RBK/RBR !!
Thats adding insult to injury when you deal for weeks with support .
++++++++++++++++++++++++++++++++++++++++++++++++++++++
"NETGEAR TEAM
Guten Tag AlbertS,
erst einmal entschuldigen wir uns dafür, dass Sie mit dem Orbi System solche Probleme haben.
Die aktuellste Orbi Firmware in der Version 1.12.0.20 löst die von Ihnen beschriebenen Probleme.
Viele Grüße,
Ihr Netgear Amazon Team2++++++++++++++++++++++++++++++++++++++++++++++++++++++
Translation:
8-22-2017
NETGEAR TEAM
Hello AlbertS,
First of all, we apologize for the trouble with the Orbi System.
The latest Orbi firmware version 1.12.0.20 solves the problems you have described.
Best regards,
Your Netgear Amazon Team - jleecloak1Aug 26, 2017Apprentice
I agree with you on this but it's in their terms.
- NobodyHereAug 26, 2017Initiate
I've gotten no response from Netgear requesting the new firmware. Had two tickets open with them, no offer of any beta or new release software. Returning to costco tday, tired of dealing with them.
- ReplevinAug 26, 2017Star
This is the Netgear strategy (as I see it). Spend no money on software engineers. Spend no money on support. Spend money on people who monitor amazon.
And there are no facts that suggest that the other poster signed some sort of agreement not to distribute the beta (perhaps he/she did, but I don't see it in the post). Once again, general seat of the pants "feelings" don't count much in life.
- Retired_MemberAug 26, 2017
Having received beta firmware for the Orbi, I can confirm you sign an agreement to not distribute.
1.12.0.20 was pushed weeks ago for the 40's not the 50's.
- bsemerickAug 26, 2017Guide
My system updated itself to 1.12.0.18. this is ridiculous. I've never had a router that auto updated.
- RogerSCAug 26, 2017Virtuoso
bsemerick wrote:My system updated itself to 1.12.0.18. this is ridiculous. I've never had a router that auto updated.
The newer "wireless systems" like mesh systems, the orbi, etc. all do this. Standalone wireless routers generally don't. In fact, when you initially configured your router, you agreed that Netgear can upgrade/update your system without your permission. If you don't believe me *smile*, reset your router and satellite, and go through the initial configuration again, you'll see it there.
- Tim-in-CAAug 26, 2017Star
At what version did auto update begin? I'm at 1.3.0.26 and it's working well, however, I'd like to manually update to the version that enabled guest network but don't want to get sucked in to auto updates. Also. If 1.12.0.18 is so problematic for users, why doesn't Netgear pull it from their update servers? I work for a CE brand and we can do that if users experience FW update issues. Netgear appears to be clueless
- scornwellAug 26, 2017Apprentice
Well that lasted a few hours, then Orbi stared dropping the internet connection, now it's back to the same poor speeds.
Time to roll back the firmware again.
- Tim-in-CAAug 28, 2017Star
Tim-in-CA wrote:At what version did auto update begin? I'm at 1.3.0.26 and it's working well, however, I'd like to manually update to the version that enabled guest network but don't want to get sucked in to auto updates. Also. If 1.12.0.18 is so problematic for users, why doesn't Netgear pull it from their update servers? I work for a CE brand and we can do that if users experience FW update issues. Netgear appears to be clueless
Bump ... any feedback to what FW version started auto updates? I'm at 1.3.0.26 and would like to update to the first version that supports Guest Networking, but worried I'll encounter auto upadating to 1.12.0.18
- ArtLeeAug 28, 2017Apprentice
Firmware 1.12 does work for some people, perhaps many people. Hard to tell... I suspect most people who have no problem have no reason to check in here. My Orbi router & satellite have been working just fine for me and my relatively small collection of a dozen or so devices.
- Retired_MemberAug 28, 2017
Yes, it worked for me as well for a couple of weeks, until I rebooted the devices, then it was back to the same behavior as was experienced with 1.11.x.
- n4choAug 28, 2017Apprentice
I thought we were getting a new firmware last week. Has Netgear responded at all about any of this? It is growing rather annoying. Im tempted to jump through the NVRAM clear hoops but would prefer to have the proper firmware release. I see newer 1.12.0.20 builds available for other similar devices but not my RBR50 which I am tempted to return to Costco as I had worse coverage but fewer drops with a multi flavored router DD-WRT WDS setup. I don't have any Netgear contacts like some folks do to ask for Beta firmware so this whole process is annoying.
#frustrating
- Retired_MemberAug 28, 2017
n4cho wrote:I thought we were getting a new firmware last week. Has Netgear responded at all about any of this? It is growing rather annoying. Im tempted to jump through the NVRAM clear hoops but would prefer to have the proper firmware release. I see newer 1.12.0.20 builds available for other similar devices but not my RBR50 which I am tempted to return to Costco as I had worse coverage but fewer drops with a multi flavored router DD-WRT WDS setup. I don't have any Netgear contacts like some folks do to ask for Beta firmware so this whole process is annoying.
#frustrating
Darren will reach out to you, here on this forum, if he wants you to use the Beta. I would recommend returning it if you're within your return window. It's been over a month and a half of this mess and so far, no official word on a fix.
- Tim-in-CAAug 28, 2017Star
@TXGunLover wrote:
n4cho wrote:I thought we were getting a new firmware last week. Has Netgear responded at all about any of this? It is growing rather annoying. Im tempted to jump through the NVRAM clear hoops but would prefer to have the proper firmware release. I see newer 1.12.0.20 builds available for other similar devices but not my RBR50 which I am tempted to return to Costco as I had worse coverage but fewer drops with a multi flavored router DD-WRT WDS setup. I don't have any Netgear contacts like some folks do to ask for Beta firmware so this whole process is annoying.
#frustrating
Darren will reach out to you, here on this forum, if he wants you to use the Beta. I would recommend returning it if you're within your return window. It's been over a month and a half of this mess and so far, no official word on a fix.
Fellow Costco purchaser here as well. I'm not having issues, but am reticent to update to the latest FW for fear of experiencing the myriad of issues reported here. Had mine for a week, but am at much older FW that lacks Guest Networking (and auto-updating :smileyhappy:). One of the primary benefits of purchasing at Costco is that you can return it at ANY time for a full refund. Routers are not part of the 90 day return policy. Had a TP Link Deco system that I bought from Amazon and had to push them to issue a refund as Echo devices were dropping off the network. I’m in a holding pattern on FW updating the Orbi until newer, more stable FW is released.
- n4choAug 28, 2017Apprentice
One of the primary benefits of purchasing at Costco is that you can return it at ANY time for a full refund. Routers are not part of the 90 day return policy.
Exactly why I purchased it there :) I just wish someone at Netgear would say 'hey yeah this is a thing, ETA is x.'
I mean I saw them close the issue for ethernet backhaul with a 'working on it next' sort of comment. Where is that at?
The lack of communication is annoying.
- nxcAug 28, 2017Apprentice
Tim-in-CA wrote:
@TXGunLover wrote:
n4cho wrote:I thought we were getting a new firmware last week. Has Netgear responded at all about any of this? It is growing rather annoying. Im tempted to jump through the NVRAM clear hoops but would prefer to have the proper firmware release. I see newer 1.12.0.20 builds available for other similar devices but not my RBR50 which I am tempted to return to Costco as I had worse coverage but fewer drops with a multi flavored router DD-WRT WDS setup. I don't have any Netgear contacts like some folks do to ask for Beta firmware so this whole process is annoying.
#frustrating
Darren will reach out to you, here on this forum, if he wants you to use the Beta. I would recommend returning it if you're within your return window. It's been over a month and a half of this mess and so far, no official word on a fix.
Fellow Costco purchaser here as well. I'm not having issues, but am reticent to update to the latest FW for fear of experiencing the myriad of issues reported here. Had mine for a week, but am at much older FW that lacks Guest Networking (and auto-updating :smileyhappy:). One of the primary benefits of purchasing at Costco is that you can return it at ANY time for a full refund. Routers are not part of the 90 day return policy. Had a TP Link Deco system that I bought from Amazon and had to push them to issue a refund as Echo devices were dropping off the network. I’m in a holding pattern on FW updating the Orbi until newer, more stable FW is released.
For what it's worth, you can usually roll back without issues if you want to try a newer firmware and run into trouble. One of the reasons I went through the debugging effort to keep running the latest version is to benefit from security fixes that have been pushed. Routers are notoriously wide targets for bad actors, and running old firmwares, however seemingly stable, should not be something we recommend without considering the associated risks. However light they may be in practice. :)
For what it's worth, I've been running v1.12 latest stable for ten days now, with no apparent issues. Everything is fast and stable, wired and wireless, both router and satellite.
Best of luck!
- MyeviltwinAug 28, 2017Initiate
It has been working well for me so far with the 1.12 firmware (knock on wood) but it has only been little more than a week since I got it, so too early to tell.
But reading through all these comments, I'm now worried that it could go down any moment, so keeping my Asus router as a backup at all times.
- nxcAug 28, 2017Apprentice
Myeviltwin wrote:It has been working well for me so far with the 1.12 firmware (knock on wood) but it has only been little more than a week since I got it, so too early to tell.
But reading through all these comments, I'm now worried that it could go down any moment, so keeping my Asus router as a backup at all times.
It's always good to have a backup! While I obviously don't have any inside information, further testing and debugging has me convinced that as long as you never use the speedtest you should be fine.