![]() All because I tried to test what you were nicely telling me all along. So now, of all my routers, this one router has a different password. Unbeknownst to me, the new firmware _allowed_ the old password but the new firmware doesn't allow you to _set_ an old password after a factory reset. Yesterday I set the router to factory defaults When I finally logged in with Iron, I set the same old password At some point yesterday, I flashed to the latest router firmware Many times I logged in - and the old 8-character password worked Notice what happened, which is a _direct_ result of me resetting to factory defaults? Now I can't use the same password I've used on my other routers! Oh no! You can't do that! It _must_ now be a 10-character password, along with a whole bunch of other upper/lower case requirements. ![]() I'll just use the same 8-character password it took yesterday before I had upgraded the firmware with tftp clients. Only later, when the same kind of thing happened when I unchecked the router settings to broadcast the SSID did I then realize (by using Iron) that it was a hidden "OK" button that was preventing the next step.Īll that is well and good, but what happened when I reset the router back to factory defaults just now is that it requested a new password. What I think happened, and I just tested it again, much to my regret, is the login to works fine, but the _next_ page (for whatever reason) requires the http(s) instead.Īt that point, I suspect, some kind of Firefox protection (which I probably instituted long ago, I'm not going to deny I mess with the settings), prevented that _second_ page from doing whatever it wanted to do. It's only slowly dawning upon me what actually transpired yesterday. This important observation escaped me, until I re-tested things today. In fact, EVERY FIRST LOGIN to that unsecured IP address worked perfectly! (It's only what happened _after_ that login, where failures occurred.) That is, the login to actually works perfectly fine! In actuality, the sequence of events in Firefox was 49 happens before 48. The significance didn't occur to me until I pondered what you are saying. In the end, I was able to flash the latest firmware from what appears to be from (R7000-V1.0.11.100_10.2.100.chk) to what is now version R7000-V1.0.11.136_10.2.120.chk from what appears to be based on these two reference urls I found in the Netgear download support site.įormatting link Notice that screenshot was taken at 8:51am yesterday. But I don't know for sure why SRWARe Iron worked with but Firefox would never let me log in when I used a url. I suspect it was something similar that prevented me from logging in also. It could be my Firefox settings though, but what happened was a dialog box asking for an "OK" popped up in SRWare Iron, but not in Firefox. It's definitely a problem with Firefox though as there was ANOTHER problem which only showed up with Firefox, which was that I couldn't hit the "Apply" button whenever I changed some settings in Firfox, and yet I could hit that same "Apply" button when I switched to SRWare Iron to do it. The solution should have come to me sooner, which was to use SRWare Iron (I didn't try any other browser than Iron so others may have worked also). I had two main problems, one of which is the router stopped accepting the login/password for reasons unknown to me and the second was that as a result of that first problem (which had nothing to do with Firefox), I did a (whole bunch of) factory resets to try to log into the router, but that's when the Firefox wouldn't let me log in and wouldn't let me choose to not worry about the lack of a bona fide certificate either. I solved it but I can't really say what specific action solved it because almost everything made no sense because it all "should" have been working.
0 Comments
Leave a Reply. |