Restoring settings on same hardware crashes Gargoyle?

[Dr. Crash]

Hi,

I had just installed Gargoyle 1.5.9 on a WDR3600 when I wanted to install it on a different WDR3600. The hardware was identical, with of course different serial numbers but same version etc.

I backed settings up on my Gargoyle router. Then I uploaded Gargoyle 1.5.9 on the other router, rebooted, and went to restore my settings on that new router. At that point the router seemed bricked. I would get an IP in the 169.* net even though my config was 10.0.1.* and Gargoyle's default obviously is 192.168.1.*.

I thankfully managed to get the new router to answer pings using the "reboot and hit the reset button like a maniac" trick, and was then able to telnet, run "firstboot" and get back on my feet. Needless to say, I am now duplicating my configuration by hand...

I can understand why restoring configuration across routers might be bad (though no one would expect it given the lack of warning on the backup/restore page), especially given all the files tarred up in a backup. But across the VERY same hardware? What can be saved there that would make this fail?

I am not really willing to try a backup/restore on the same router to see if that's a bug there... I need that router (I should have gotten too at $39 each maybe... so I could help test), but I can contribute a list of files backed up and if needed my tarball.

P.S.: list of files backed up:


etc/passwd
etc/shadow
etc/config/
etc/config/ddns_gargoyle
etc/config/dhcp
etc/config/dropbear
etc/config/firewall
etc/config/gargoyle
etc/config/httpd_gargoyle
etc/config/nfsd
etc/config/openvpn
etc/config/openvpn_gargoyle
etc/config/p910nd
etc/config/qos_gargoyle
etc/config/samba
etc/config/share_users
etc/config/system
etc/config/tor
etc/config/upnpd
etc/config/vsftpd
etc/config/webmon_gargoyle
etc/config/wol
etc/config/ubootenv
etc/config/network
etc/config/wireless
etc/rc.d/
../init.d/portmap
../init.d/dropbear
../init.d/nfsd
../init.d/network
../init.d/boot
../init.d/umount
../init.d/defconfig
../init.d/boot
../init.d/ubus
../init.d/portmap
../init.d/network
../init.d/share_users
../init.d/time_backup
../init.d/set_kernel_timezone
../init.d/usb
../init.d/sysntpd
../init.d/firewall
../init.d/gargoyle_themes
../init.d/cron
../init.d/dropbear
../init.d/p910nd
../init.d/qos_gargoyle
../init.d/telnet
../init.d/httpd_gargoyle
../init.d/bwmon_gargoyle
../init.d/usb_storage
../init.d/dnsmasq
../init.d/nfsd
../init.d/samba
../init.d/wol
../init.d/tor
../init.d/ddns_gargoyle
../init.d/vsftpd
../init.d/done
../init.d/openvpn
../init.d/led
../init.d/watchdog
../init.d/sysctl
/tmp/TZ
etc/firewall.user
etc/ethers
etc/hosts
etc/crontabs/
etc/crontabs/root
etc/dropbear/
etc/dropbear/dropbear_dss_host_key
etc/dropbear/dropbear_rsa_host_key
tmp/data/
tmp/data/bwmon/
tmp/data/bwmon/qos3-down-dclass_4-hour-24.bw
tmp/data/bwmon/qos2-down-dclass_4-900-24.bw
tmp/data/bwmon/qos1-down-dclass_4-minute-15.bw
tmp/data/bwmon/qos3-down-dclass_3-hour-24.bw
tmp/data/bwmon/qos2-down-dclass_3-900-24.bw
tmp/data/bwmon/qos1-down-dclass_3-minute-15.bw
tmp/data/bwmon/qos3-down-dclass_2-hour-24.bw
tmp/data/bwmon/qos2-down-dclass_2-900-24.bw
tmp/data/bwmon/qos1-down-dclass_2-minute-15.bw
tmp/data/bwmon/qos3-down-dclass_1-hour-24.bw
tmp/data/bwmon/qos2-down-dclass_1-900-24.bw
tmp/data/bwmon/qos1-down-dclass_1-minute-15.bw
tmp/data/bwmon/qos3-up-uclass_4-hour-24.bw
tmp/data/bwmon/qos2-up-uclass_4-900-24.bw
tmp/data/bwmon/qos1-up-uclass_4-minute-15.bw
tmp/data/bwmon/qos3-up-uclass_3-hour-24.bw
tmp/data/bwmon/qos2-up-uclass_3-900-24.bw
tmp/data/bwmon/qos1-up-uclass_3-minute-15.bw
tmp/data/bwmon/qos3-up-uclass_2-hour-24.bw
tmp/data/bwmon/qos2-up-uclass_2-900-24.bw
tmp/data/bwmon/qos1-up-uclass_2-minute-15.bw
tmp/data/bwmon/qos3-up-uclass_1-hour-24.bw
tmp/data/bwmon/qos2-up-uclass_1-900-24.bw
tmp/data/bwmon/qos1-up-uclass_1-minute-15.bw
tmp/data/bwmon/bdist3-upload-hour-24.bw
tmp/data/bwmon/bdist3-download-hour-24.bw
tmp/data/bwmon/total3-upload-180-479.bw
tmp/data/bwmon/total3-download-180-479.bw
tmp/data/bwmon/bdist2-upload-900-24.bw
tmp/data/bwmon/bdist2-download-900-24.bw
tmp/data/bwmon/total2-upload-minute-359.bw
tmp/data/bwmon/total2-download-minute-359.bw
tmp/data/bwmon/bdist1-upload-minute-15.bw
tmp/data/bwmon/bdist1-download-minute-15.bw
tmp/data/bwmon/total1-upload-2-449.bw
tmp/data/bwmon/total1-download-2-449.bw
usr/data/
usr/data/bwmon/
usr/data/bwmon/qos4-up-uclass_2-day-31.bw
usr/data/bwmon/qos4-down-dclass_1-day-31.bw
usr/data/bwmon/bdist5-download-month-12.bw
usr/data/bwmon/qos5-down-dclass_4-month-12.bw
usr/data/bwmon/total5-upload-day-365.bw
usr/data/bwmon/qos4-up-uclass_1-day-31.bw
usr/data/bwmon/bdist5-upload-month-12.bw
usr/data/bwmon/total5-download-day-365.bw
usr/data/bwmon/total4-upload-7200-359.bw
usr/data/bwmon/total4-download-7200-359.bw
usr/data/bwmon/qos5-up-uclass_1-month-12.bw
usr/data/bwmon/bdist4-upload-day-31.bw
usr/data/bwmon/qos5-up-uclass_2-month-12.bw
usr/data/bwmon/qos4-down-dclass_4-day-31.bw
usr/data/bwmon/qos5-down-dclass_1-month-12.bw
usr/data/bwmon/qos4-up-uclass_4-day-31.bw
usr/data/bwmon/qos5-up-uclass_3-month-12.bw
usr/data/bwmon/qos4-down-dclass_3-day-31.bw
usr/data/bwmon/bdist4-download-day-31.bw
usr/data/bwmon/qos5-down-dclass_2-month-12.bw
usr/data/bwmon/qos4-up-uclass_3-day-31.bw
usr/data/bwmon/qos5-up-uclass_4-month-12.bw
usr/data/bwmon/qos4-down-dclass_2-day-31.bw
usr/data/bwmon/qos5-down-dclass_3-month-12.bw
usr/data/quotas/
usr/data/time_backup

[DoesItMatter]

I deleted your other threads because it looked like you duplicate
posted the same information/issue.

As for backing up and restoring to same hardware - not advisable!

The MAC addresses are different.

This can cause a LOT of issues when restoring to same hardware

Only restore to the device that the backup was created for.

[Cachorro]

I have a working setup of Gargoyle on TP WDR1043, and want to restore to new hardware to replace it with. The new router I got is a TP-WDR3600.
So I saved a backup of my 1043 and dumped it on my 3600. The router boots up fine as far as the status light is concerned (slow blinking, then solid system LED), but the router does not work. That is, it is not available on the IP I know it should be on (if I set my PC IP address via static), and DHCP does not assing my computer an address.

Is it possible to do this? Can I restore, then boot in failsafe mode and modify some files to get it working?

I could start from a fresh config and set it up from scratch, but that is so much to setup ... and would be much better not to be typing for an hour and possibly even mis something...

Thanks.

[BashfulBladder]

Do not restore from Device A to entirely different Device B. There are lots of settings that are device specific.

You only solution is to get into failsafe & erase ALL the changes.

If you were a shell wiz, you could extract the backup on your computer, stop services, copy files into place & start services. That would probably take a good long while too.

Why this is posting on a thread titled 'same hardware' is beyond me, but we all wipe a little differently I suppose.