I've got the simplest possible .rsc file for testing with:
(As a side note: turns out that sometime since the 6.40.2 setting /interface wireless security-profile is now a requirement for a netinstalled router to boot. Thanks for documenting that, Mikrotik! I only wasted about five hours figuring that out by trial and error)
Code: Select all
/interface wireless security-profiles set [ find default=yes ] supplicant-identity=MikroTik /ip address add address=10.0.0.1/30 interface=ether2 network=10.0.0.0
Anyway, process/symptoms as follows:
- Use netinstall to install 6.42.6 with above .rsc as installation script
- Router reboots, ~50 secs later it responds on 10.0.0.1
- Power cycle router, again ~50 seconds later it starts responding again
- Repeat last step several times to be sure
- Factory reset router using the button on the back (held on power up until usr led starts flashing, then let go)
- Router is now a brick. Not even the Mikrotik standard config. Seems to not even boot (but there is no way to tell because no serial port)
Only way to get it back to life is to netinstall again.
For those that have not played with Netinstall, the point of it is that it can set the factory default settings to be custom so when a router goes out to the end user they can factory reset it themselves to get back to a customised known state.
Mikrotik can you comment, please. Is this a known issue? Any roadmap for it to be fixed? If not, how far do I need to roll back in ROS versions to avoid the problem?