Or you can have nice readable export which you can inspect before you apply config to new router, but it's missing important things.
We have a few routers running in different networks, we didn't buy them in bulk and are all different.
After a day of messing around I've got the two Omni's talking to each other and I can ping through both of them.
When I load the backup file, the correct IP comes in, but the wireless settings are wrong, the SSID is from a very old configuration, the wireless is disabled and the bridge settings are off too.
The problem you're facing could be the fact that those devices have wireless interfaces, whose driver takes a little to load when booting.
But I can reset configuration on the original Omni (A), and import the same backup file back into (A) and all of the parameters load fine.
So in other words, you can have unreadable binary backup, which is not meant for transfering config elsewhere, but it will probably work, even though it can mess up some things.
When both are on and talking, the Omni that is set up as a station bridge gets its bridge port set to Backup Port.
Probably there are some configuration items in the rsc file which are already existing on the device where the import is done.
Values in this field link to pages explaining in detail what is unsupported and why, what the concequences are and what you can do about it.
Also, it'd be awesome if you guys could rework the backup function so that it isn't make and model limited.
Now, I understand that this isn't so simple so for the time being I'll settle for a reply to the following.
DHCP server where IP pool settings are some rows below, so import can't assign this pool to DHCP server.
When copying and pastingover a terminal the wireless driver has aready been loaded, that's why the import loads fine.
