I have a script that I use to auto-configure my MK boxes. I use it with Netinstall, so every time a new box arrives I push it with Netinstall with the latest version of the routeros-mipsbe package. Yesterday i’ve downloaded the routeros-mipsbe 6.15 and tried to Netinstall for RouterOS v6.15 a RB750 using this new package with my script. Unfortunatelly, after rebooting, the script did’nt run. So i’ve tried to access the box using Winbox and I could see that, for some reason, the script was not uploaded rightfully to the equipment. I did the same steps using Netinstall for RouterOS v6.15 but uploaded the routeros-mipsbe6.10 and 6.12. Everything worked fine. I’ve not tried with packs 6.13 and 6.14 because i don’t have them here right now.
Someone have any ideas on what is happening here!?
Seems that removing this line have worked.
What happen with this option? It was removed or changed on 6.15?
The main problem now is related with already installed boxes that where upgraded to the last version 6.15 of RouterOS. Resetting them remotely doesn’t execute the previous script. Because o this I cannot send a remote reset command, anymore. This wasn’t supposed to be a problem until now. This can lead to a huge problems for my business and services that I offer to my customers. I think Mikrotik developers should look at this stuff with some care. A change on the RouterOS like that, that changes the behavior of the boxes can lead some customers to be stucked with old versions of OS. This is not good at all not for them neither for us!
you can install ntp package on the router and your default script will work as before.
In 6.15 SNTP client was changes so that if you set up NTP server, it will switch to unicast mode automatically. If SNTP client is enabled, but no servers set - broadcast mode will be used.