RBR50 - Have You Installed V2.7.2.104

---

CrimpOn wrote:

I'm now at 13 days with no problems.  Sort of wish I had taken the time to do a complete "config from scratch" rather than save config, Factory Reset, and reload config.  Who knows what "cobwebs" remain? 

---

I believe the failure rate is higher for those who upgraded as soon as it became available as advertised by a certain guru 

---

pdeethardt wrote:

---

vajim wrote:

---

pdeethardt wrote:

I installed it via the web update interface, and no issues so far with a 12 day uptime.

---

Thanks 

 

that's about 5 weeks after it first became available 

 

possibly time for netgear to fix any previous issues 

---

Could be since we can't see the actual build number. I was running 2.7.2.102 for some time prior to updating to .104 (my router automatically updated to that version at some point), but due to issues I had updating to version 2.5.1.16 I didn't want to upgrade to .104 until my work schedule allowed me time to troubleshoot and so forth if the upgrade went awry.

 

I did notice a substantial increase in my Wi-Fi speeds after I got my system fully updated to .102 (the satellite didn't automatically update; only the router), and I've seen no change in that after the .104 update.

---

Tell us more about how your router automatically updated as you state above

---

vajim wrote:

Hopefully we'll hear more about the auto update 

---

I was poking around in the app one day, and I happened to notice in the details section for my RBR50 the firmware was now version 2.7.2.102. I had not applied any updates myself using any of the methods, and when I checked the debug info on the RBR50 I saw it had an uptime of around 9 days. I then checked my RBS50, and it was still running 2.5.1.16 and had an 80-ish day uptime. This led to me asking in another thread how the automatic update process from Netgear actually works, and why only the RBR50 had been updated.