Hi, I have 2 WRT54GS v1.1 and I was hoping to backup/restore one config to the other Router so I can play around with variosu firmware, and have an instant backup if things go pear shaped. However it says ""cannot restore on a different router", when I try this. Is there any work around, is this at all possible? I'm loathe to re-enter everything again. Cheers k.
There have been a few threads on this in the past, including one in which two members of the forum somehow forced a restore of another router's config onto one and subsequently bricked it. Do a search for more info., as it came up again just a week or two ago.
afaik details of mac IDs are held on the config and this may trash another router. WRT configs are for individual routers and do not have the same feature/config set as an Cisco IOS config that can be carried over to another similar router
Hmm... bummer. I'm not that keen on trashing either router. Thanks, I guess I was mistaken, thought I'd be able to do this easily... k.
You can save the web-pages of each page in the router.... this is not a great solution but at least helps with copy-pasting complex info such as static-dhcp mac addresses etc... though you'll still have to copy-paste each individual item. It's still a pain, I know... I wish there was some better solution.
I was the one that bricked the router :redface: Of all the methods and suggestions so far the most promising to me seems to be to to alter the HTTP-ID so that prevously saved web pages from e.g. 192.168.1.1 can be used to 'save" back to the same IP address - but which is now a different router. Any modders have any ideas how to do this, or if they think it's possible?
wouldn't changing the router's mac address work? this would allow for a backup router to be prepped and ready to go in the event of a failure.
if I recall correctly the restore program have a force switch just make sure you backup your config first and use the same type of hardware for both routers. I think there was a script to replicate the configuration from one router to another. this have been discussed before, here is the previous thread I can't seem to find the script that cleaned up the configuration - maybe someone here can help you with that. this is what is known that should be deleted/cleaned from the .cfg file for a painless restore: eou_device_id: An alphanumeric string of length 6. Use not known. eou_private_key: A very long hexadecimal string. Use not known. eou_public_key: Another very long hexadecimal string of unknown purpose. et0macaddr: The hardware address of the LAN, as assigned by the manufacturer. http_id: TID followed by 16 hexadecimal digits. Used by the http daemon to ensure that responses it receives are from pages it was sent. Initialized using a random value from /dev/urandom. lan_hwaddr: Actual LAN hardware address. Either et0macaddr or assigned by the user. lan_ipaddr: The user-assigned LAN IP address. router_name: User assigned name for the router. sdram_ncdl: Purpose unknown. Had values 0xFE0008 and 0xFF0009. The router seems to set this to 0 at times of great confusion, but I can't find what it means. sshd_hostkey: Host key generated by the ssh daemon. It appears that setting this to the empty string will cause the ssh daemon to generate a new host key at startup wan_hostname: User assigned host name wan_hwaddr: Current WAN hardware address (may be user assigned) wl0_hwaddr: Current wireless hardware address (may be user assigned) the .cfg file type is simply a tar.gz file so you can uncompress is change what you need and then re-compress it. :grin:
