The reload of configuration is some unconfirmed bug, I encountered it as well and I have reported it but AFAIK nothing has been done about it yet.
Just ignore the frequency warning, it is a known bug as well. It appears to be very hard to compile a correct table of default frequencies for all models...
(so some models issue this incorrect warning)
Ah that is interesting, maybe it would solve the issue in my case as well. (was on a RB951G)
It is hard to debug these things because there is no logfile. When I reported the issue it was promised that they would
- writing a log of errors encountered during the import
- continuing the import as long as no disastrous errors occur
As it is now, whenever a minor problem occurs during the import the processing stops right there and you have an incomplete
config that may render the router inaccessible to see what happened. (especially on the low-end models without RS232 port)
@dfxer - Thanks for the tip on the delay in the config file! I have added this to my config file and it was able to import without a problem. You saved me a lot of time troubleshooting this issue, so thanks again for taking time to post how to work around it!
I think it is very unfortunate that:
1. the delay is still necessary. It would seem so trivial to include it in the first-boot procedure but it has not been done even after more than a year...
2. still nothing is done about the error recovery and logging. that would likely be more work.