subscribe to our Youtube


14455 questions

17168 answers


0 members

We are migrating to our new platform at Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
146 views 0 comments
by anonymous
Hi All:

I am having my guys do the following to prep the routers for deployment:

1. Connect the WAN port to the office lan, laptop to any lan port,

2. Point browser to,

3. login and change the password to XXXXXXXX,

4. Open the CLI,

5. Ping to confirm connectivity via the office LAN,

6. opkg update,

7. opkg install ip-full --force-overwrite

8. opkg install openssh-sftp-server

9. Connect to router using filezilla using sftp,

10. copy up the following files:












Those edited files for each individual site should bring the router up after reboot and it should connect to its proper IPSec tunnel and should just work.

Is there anything I am missing?

Am I over simplifying this?

Are there any of those files that should be left to the local router only?

Can I damage the router by copying up edited version of those files?



1 Answer

0 votes

Seems a massively hard work solution. I have always pre-configured by:

  1. Update firmware to latest OEM image in web interface (from local file, so no internet required)
  2. Restore a settings file with the required settings in it.
  3. After reboot, all settings are applied.
  4. If necessary set a unique per-device password as per your security policy.

If (as you imply) you need every router configuration unique, then the saved settings file is just a tar archive, so you could unpack / modify affected files / repack to generate unique configurations for each router.

Always try to upload configuration to the same firmware version it came from. You can vary, but it gets a lot more complex. When a new firmware comes out, load your base settings archive after update. Check new features you don't need haven't been enabled by default, then re-save the configuration to capture any new settings inserted by the upgrade process. Then use that archive going forwards.

Best answer