alexboroda, I would suggest that you try resetting without the .rsc file and without any default configuration. After reboot, log into the unit and then manually copy your .rsc file into the terminal window. This will most likely point out a CLI error (usually caused by the newer firmware version having different syntax for one or more commands) that is preventing the .rsc file from running after reset.
In my experience, “run after reset” .rsc will roll back if there are any failures during the application process – it won’t generally leave a “partial config” with just the commands that worked.
mars, download page works fine, there is no problem to get package from it.
Do you have any problems with download page? http://www.mikrotik.com/download
alexboroda, thank you for the report. We will see what we can do!
jdog, mail support with detailed problem description and attached support output file. As more detailed report you will include, as easier for us will be to help you. We are sorry for any incovenience caused.
First of all, you can not take one export, and simple reload it back after reset…
You must check it on one just netinstalled board, line by line, till you find all the errors.
When on the script are presents errors, routeros stop running the file (BAD from my point of view, I’m expect the skip of error to next instruction, not stop it all…).
From example, you must remove all this line from the script:
set [ find default=yes ] supplicant-identity=MikroTik
... eap-methods="" ...
... supplicant-identity="" ...
/queue type
set 2 kind=pfifo
set 9 pfifo-limit=100
/system logging action
set 3 remote=0.0.0.0
/ip ipsec policy
add template=yes
/system leds
set 0 interface=wlan1
/system routerboard settings
set cpu-frequency=600MHz
P.S.:
Do not put wlan1 on “wds bridge”, if thw wlan1 are on bridge or ap-bridge mode with WDS with default bridge on “wds bridge”…
Thanks for all the feedback. The special package for enabling protected routerboot is available upon request, email support to get it. This is to avoid people accidentally installing it together with all the other packages.
Doh searched on other forum posts and in the first time i was thinking that the problem is from my email server, but if i downgrade to 6.25 it;s working as expected only on 6.26 i have this problem
what was not working? device didn’t boot? did you manually run the routerboot upgrade? they are not done at the same time, so most likely v6.26 worked fine, if you were able to run the routerboot upgrade, yes?
More information please.
What models? What previous firmware? What winbox version? What routerboard firmware version?
Can you access now? What was the fix? Did you send MT a support file?
I won’t be upgrading until health information is fixed. We need this without exception.