NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
R8500 is it safe? FW: from 1.0.2.144 to 1.0.2.154
Checking in before i commit anyone update to 1.0.2.154? what device? what version? differences noted?
Thanks!
10 Replies
The release notes show "security fixes".
You can always install it. If it has issues, its easy enough to downgrade to the prior version
https://www.netgear.com/support/product/R8500.aspx
Thank you.
I did read the installation/ release notes. I was looking for someone who may have some experiance with it and read my questions. If you notice I am currently on a version (1.0.2.144) which seems to have some contoversy around it. I know your answer was for those who don't bother to read the release note and then wonder what happened.
To change the subjecth here is a differet question that I may be missing the point on. Why don't (random sampling of four netgear routers. so maybe its just the ones I have been exposed to) they populate (Basic)- Attached Devices with entries from (Advanced/setup/lansetup) Address reservations or query the device for its hostname but why leave them blank when another table has been populated with the IP address, MAC address and hostname why jusy fill in a "--" . Do the devices you have worked on do the same thing?
Thanks
John
Updated from 1.0.2.144 to 1.0.2.154.
No issues at all - did not need to reset to factory defaults first.
25 devices reconnected no issue
However no fix for ready share and usb being recognized after rebooting router. I must pull the usb after a rebbot and re insert it.
So, You do not see issues with DNS? if not, it might be helpful for moderators to know that R8500 does not have the fault. I expect that it does as my router R8300 is almost the same router.
see
I had DNS errors on multiple machines after going to .154. I also had a Windows update at the time so thought it was that. Might be only wired PCs but the TVs, phones and iPads are not so obvious so not sure if the odd connects were the DNS issue. Went back to .144 and so far looking good. I would get Windows Edge error and 1/2 the time it would then go to the site without doing anything.
Dan
