NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Incorrect Update Instructions Nighthawlk
Instructions for firmware updating with browser instead of phone are incorrect. It says to connect the PC to the router with an ethernet cable. When this is done, the login page says it must be con...
Thanks for references. The email from Netgear was
"We've Enhanced Your Product's Security.
Please Update to the Latest Firmware.
Your product has the following updates available:
R6080
Learn how to update here
Latest firmware version: v1.0.0.46
Use the Nighthawk App to update your firmware
App Store
Google Store
If you don't have an iOS or Android capable device, visit this page."
-------------------------
Also a video with instructions
https://click.e.netgear.com/?qs=085694c93a37852e173953e623794457027cbc5db866928f89e530a9118b1914be0fdb61a17c534de2609d3cdfaa667d9a4cc07c93401497
When router.login.com,.net is not available (probably not in DNS), the manual shows the direct IP address numbers to use, typical for such network devices, modems etc. When new firmware is available the initial BASIC mgt screen has an added notice tab to go directly to update without going to Advanced>Administration.
> The manual section on firmware updating does not mention "connect with
> an ethernet cable" as does the article on the website -- just typical
> tech writing detail. Just connect to router.login.net. [...]That's probably because either a wired or wireless connection should
work. A wired connection is always more reliable, and reliability might
matter more when loading firmware than it would normally._Which_ "the article" on _which_ "the website"? (And you complain
about sloppy descriptions from _Netgear_?)> [...] This is not the network login but router management login, with
> default user admin, password "password" for initial setup. [...]I know that. I've read the "Types of Logins" section of the User
Manual. Have you?> When router.login.com,.net is not available (probably not in DNS),
> [...]
There's more than one kind of "not available". One particular such
problem has already been explained.I'm not sure what these rambling comments are intended to contribute.
My firmware is updated so problem solved.