NVRAM [Release] NVRAM Save/Restore Utility

[Torson]

HND migration restore RT-AX56U -> RT-AC86U on 384.16 Beta 2.

Used latest available NSRU version (03/27/2020). The migration seems to have worked to some extent (VPN clients work, DHCP reservation work, wireless all working etc.) However, I'm unable to logon to my router - none of the passwords that I use/d work.

I've seen a recent entry where someone had the same issue - unable to logon to the router after restore. As I mentioned, all seems fully functional, but I need access to the router ASAP. Thank you!

 

[RMerlin]

I've seen a recent entry where someone had the same issue - unable to logon to the router after restore.

Some router models encrypt the content of http_passwd, so you can't just copy it between all models.

 

[Torson]

Thank you for the information. What's the solution?

 

[Xentrk]

HND migration restore RT-AX56U -> RT-AC86U on 384.16 Beta 2.

Used latest available NSRU version (03/27/2020). The migration seems to have worked to some extent (VPN clients work, DHCP reservation work, wireless all working etc.) However, I'm unable to logon to my router - none of the passwords that I use/d work.

I've seen a recent entry where someone had the same issue - unable to logon to the router after restore. As I mentioned, all seems fully functional, but I need access to the router ASAP. Thank you!

Can you SSH into the router? Maybe you can set the http_passwd and http_username nvram values.

nvram set http_username="username"
nvram set http_passwd="passwd"
nvram commit

If you can access the USB, you can search or grep the nvram restore script that got created for http_passwd and http_username= to see if they are encrypted or plain text.

 

[maghuro]

Yesterday I made the first backup using this fantastic tool.
Just one question, what in the name of God is Facebook Wifi?

 

[here1310]

@Torson:
1. make a factory reset (reset button)
2. Set a new username / password
3. Activate jffs / ssh
4. Connect via WinSCP and on the usb stick in the nsru / backup
Edit files nvram-restore-xxxxxxxx.sh
delete "" http_passwd "and" "http_username"
5. do a restore now
good luck..

 

[Torson]

@Xentrk - on the Ax56U username is in clear text and the password is encrypted. Cannot SSH into the router - same login issue.
@here1310 - I'll give it a try and report back here.
Thank you all...

 

[Torson]

HND migration restore RT-AX56U -> RT-AC86U on 384.16 Beta 2 ...continued

@here1310 - your suggestion worked! Thanks.

Basically the migration was as documented. I ended up with a fully restored and functional AC86U including the UI and functionality for the AC66U_B1 AiMesh node.
The OpenVPN server came up properly, all OpenVPN Clients connected, wireless fully functional (same channels on both bands as on the original AX56U,) all DHCP reservations, ports open, all settings required by unbound in place, QoS etc. all working.

Basically the only thing that was not started (although it was properly configured) was the IPSec Server.

@Xentrk, the only suggestion would be to add instructions to comment out the username and password lines in the restore file (for the models that encrypt passwords ?,) and after reboot to use the ones entered during the initial network configuration.

 

[here1310]

Excellent!
Did you also connect an Aimesh node to the router?
I'm still looking for the necessary NVRAM parameters ...
These settings are no longer available during a migration restore ...
Could you test a migration restore on your router instead of a restore?
Complement:
I can only test from non-HND to HND (ac88u to ax88u or ac86u)
it would be helpful!


..we are at home and cannot infect ourselves or infect others! Stay ALL HEALTHY !!

 

[Torson]

@here1310 - my start point was the AX56U router with an AC66U_B1 as AiMesh node. I ran a migration save on the AX56U + hnd-migr script followed by a restore on the AC86U (as described in https://github.com/Xentrk/nvram-save-restore-utility#nvram-hnd-migrsh-usage-notes) + your suggested workaround for the encrypted password issue. It all restored alright as I previously described.

I can certainly try a migration save on the AC86U and restore back on the AX56U, just can't see the practicality of it (except when or if the better router breaks and there's no equivalent or better replacement on hand...)

 

[RMerlin]

Currently, the AX models are the ones with NVRAM_ENCRYPT enabled (AX88, AX56 and AX58).

You can't just set httpd_passwd to a new one, you'll need to have an encrypted string to put in there. And since the encryption function is closed source, I don't know how one might be able to generate his own.

At a quick glance, I think httpd has a special case for when httpd_passwd is set to the default password. So, try setting it to "admin", it might then let you connect over http, and define a new, encrypted password.

 

[Torson]

I just rem'ed out that whole httpd_passwd line. After the migration and reboot it allowed me to login with the password I set during network configuration (after the factory reset and before starting the migration restore.) The httpd_username is not an issue since it's clear text.

 

[Xentrk]

Yesterday I made the first backup using this fantastic tool.
Just one question, what in the name of God is Facebook Wifi?

Facebook WiFi is a legacy feature that Asus no longer supports. I need to check to see if John's Fork still supports it. If not, I will remove it in the next update.

 

[Xentrk]

HND migration restore RT-AX56U -> RT-AC86U on 384.16 Beta 2 ...continued

@here1310 - your suggestion worked! Thanks.

Basically the migration was as documented. I ended up with a fully restored and functional AC86U including the UI and functionality for the AC66U_B1 AiMesh node.
The OpenVPN server came up properly, all OpenVPN Clients connected, wireless fully functional (same channels on both bands as on the original AX56U,) all DHCP reservations, ports open, all settings required by unbound in place, QoS etc. all working.

Basically the only thing that was not started (although it was properly configured) was the IPSec Server.

@Xentrk, the only suggestion would be to add instructions to comment out the username and password lines in the restore file (for the models that encrypt passwords ?,) and after reboot to use the ones entered during the initial network configuration.

I will push an update to prevent the userid and password from being saved/restored. One has to set up a username and password after a factory reset or logon using a valid username/password to restore. That should prevent future problems.

 

[Xentrk]

Update: nvram-merlin.ini

Issue reported by @Torson - the AX models have NVRAM_ENCRYPT enabled (AX88, AX56 and AX58) impacting the ability to properly save/restore the http_passwd nvram parm.

The nvram parms http_username and http_passwd have been commented out to prevent processing in the nvram-merlin.ini file and may eventually be removed. One has to set up a username and password after a factory reset or logon using an existing username/password to perform the restore anyway. So the nvarm values are good candidates for exception processing.

Facebook WiFi is a legacy feature that Asus no longer supports. Reference removed from nvram-merlin.ini.

 

[ICDeadPpl]

Update: nvram-merlin.ini

Issue reported by @Torson - the AX models have NVRAM_ENCRYPT enabled (AX88, AX56 and AX58) impacting the ability to properly save/restore the http_passwd nvram parm.

The nvram parms http_username and http_passwd have been commented out to prevent processing in the nvram-merlin.ini file and may eventually be removed. One has to set up a username and password after a factory reset or logon using an existing username/password to perform the restore anyway. So the nvarm values are good candidates for exception processing.

Facebook WiFi is a legacy feature that Asus no longer supports. Reference removed from nvram-merlin.ini.

http_username and http_passwd are still in the nvram-sample.ini file.

 

[Xentrk]

http_username and http_passwd are still in the nvram-sample.ini file.

Thank you. I just pushed an update to also comment out http_username and http_passwd in nvram-sample.ini.

[System - Basic]
time_zone_dst
time_zone
time_zone_dstoff
#http_passwd
http_clientlist
#http_username
@jffs2_on
<snip>

 

[XIII]

How long does it take for amtm to process these?

it says all scripts are up to date (no minor changes either)

 

[TechTinkerer]

How long does it take for amtm to process these?

it says all scripts are up to date (no minor changes either)

Hi, you need to check for updates within the script then it will download the changed files.

@Xentrk can you add an option within your script to view backups and be able to delete ones if not needed please?

 

[XIII]

Hi, you need to check for updates within the script then it will download the changed files.

Oh, right.

I keep forgetting that this is less integrated than other scripts...