Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[bobg52]

Prior to upgrading to 1.37NA on my DIR-655 I saved a copy of the gateway_settings.gws file on a local drive using Firefox 31.  Following the upgrade all of my previous settings were wiped out.  I figured no problem, just restore the saved config file.  Unfortunately this resulted in the following message, RESTORE OUT OF VALID RANGE.  Thinking the uograde was the source of the problem I downgraded back to 1.35NA. Again I tried to restore the config file however the result of a restore configuration was the same as with 1.37NA.  Thinking the file might have been corrupted I used a previously backed up config file that was saved using IE11 approximately 1 year ago with still the same outcome.  I then did an internet search and found a couple of threads on this forum about this topic.  One of them discussed http vs https. I tried both alternatives with the same result.  The other post talked about a possible corrupted file which degenerated into some insulting replies. Anyway, this may seem like a lot of concern for some but I have owned this router for about 4 years and have made numerous tweaks and changes as I have added new hardware and software to my network.  Any help in resolving this problem would be greatly appreciated.

[FurryNutz]

Link>Welcome!

• Was a Factory Reset performed before and after any firmware updates then set up from scratch?

FW Update Process

What version of FW was loaded before you upgraded? FW? If you came from 1.1x or 1.2x, then it's recommended to clean install FW and set up from scratch when applying 1.3x FW as some features and options may have changed between the versions.

Please use the FW update process to find information and application of FW updates for safely applying FW.

[bobg52]

Thank you for your reply and input.  In answer to your questions; no Factory Reset was performed and I was upgrading from 1.35NA to 1.37NA.  I reviewed the FW update process posted on this forum and didn't note any ideas that might solve my problem but after making my post I started scanning all of the posts on  the DIR-655 forum looking for any reference that might relate to my problem.  During this review I found a post from LarryNOTtheCableGuy dated 1/12/14.  I quote as follows:

"LarryNOTtheCableGuy link=topic=57338.msg224600#msg224600 date=1389589878
I had the same problem when I updated my DIR-655 A4 from 1.35NA to 1.37NA. The first time around I must have gotten lucky, because the router eventually accepted the file after repeated tries. Subsequently I had to go back to 1.35NA in order to troubleshoot a network problem I hadn't noticed until after the update. I eventually determined that it had nothing to do with the firmware update. When I updated the router to 1.37NA the second time, I ran into the same problem. However, for some reason I looked at the router log right after the file had been rejected, and it actually said why (imagine that). It turned out that one of the reserved IP addresses was in use by (i.e., had been assigned to) the computer I was using to do the firmware update. As soon as I configured the computer with an IP static address that wasn't reserved, the router accepted the configuration file. Your problem may be something different, but at least the log might point you in the right direction. Good luck.

Larry ...."

With this information I went to my router logs and found the same message as Larry.  In my case the offending IP address was one that had been reserved for my network printer however it showed an odd MAC address, 00:00:00:00:00:00.  I revoked the IP address and to my surprise the configuration file restored successfully!  The suspect IP address on my network was 192.168.0.199.  I don't know if this was the one Larry encountered but it might be one that the router must have access to perform the file upload.  To possibly guide other users to this solution when performing a search on this forum I have included the complete text of the error message from the router below.

I hope this might be of some value to others.

Bob



RESTORE OUT OF VALID RANGE

The restored configuration file is not correct. You may have restored a settings file that contains one or more values
that are out of the valid range permitted for this release.

Try the restore again with a valid restore configuration file.

[FurryNutz]

Sounds Good. Thanks for the information. I'll put this in the FW update process as well for future use.

Enjoy. 

[LarryNOTtheCableGuy]

It's been quite a while since I had this problem, but it's very likely that the "troublesome" IP address was in fact 192.168.0.199. I doubt that there's anything special about this IP address, other than the fact that it's the first one automatically assigned by the router, if the router is setup with the default DHCP IP Address Range of 192.168.0.100 to 192.168.0.199 (If I remember correctly, earlier hardware versions of the DIR-655 started at the other end of the range, i.e., assigned 192.168.0.100 first).

In my case I have a number of devices (e.g., printers, camaras, NAS devices, etc.) hardwired to my router and have reserved IP addresses for them at the top of the list. I normally connect my laptop via wi-fi, so I've reserved an IP address for it farther down the list (e.g., 192.168.0.188). So when I was changing the firmware version of the router, it's configuration would have been wiped, and with the laptop hardwired to the router (wi-fi not setup at this point), the router would have assigned it the first one in the range (i.e., 192.168.0.199). Thus the reported conflict when the configuration file was loaded (which would have contained 192.168.0.188 as the IP address for the laptop).

As I said earlier, I'm amazed that the router actually checks.

[FurryNutz]

Another thing I was thinking about. When working with the FW and saved config files, you might want to disconnect ALL devices and power them off accept for one wired PC and just the router. Do the FW updates and re-apply the saved config file before turning ON and reconnecting devices. I've used .199 address as a reserved address for my Xbox and have never had any issues with that address.

Glad it working now for you. Enjoy.