I fully agree! I think that when an existing feature requires a new device-mode setting after an upgrade, the corresponding device-mode should be automatically set as part of the upgrade.
Only on new devices or after reset-to-defaults, a new device-mode regime should become active by default.
[quote=pe1chl post_id=1100735 time=1727799467 user_id=80589]
So it seems that when you try to setup partitions while not having that device-mode option set, it just corrupts the device?
That is even worse than being unable to switch partitions after upgrade…
[/quote]
That be my take. I only went down the rabbit hole since the RB1100 had a physical serial port. Clearly it shouldn’t end up in a bootloop.
Normally if something is blocked by device-mode, it does not show up in UI/CLI - so there that initial problem here IMO.
Why there is no device-mode called “this-is-my-router-and-I-want-everything-to-be-enabled-always-and-forever”?
The knee-jerk reaction of most SoHo, and supermarket IT people would be to set this, defeating it's purpose
That said, there must be a better way than forcing a truck-roll for people managing thousands of devices, especially when involving partitions/downgrade
those are recovery features by their very nature, and messing with them has a wide range of ramifications
Very off-topic, but can you share why would you need to hit those PSU’s with traffic-gen?
Emulating some kind of magic-packet maybe?
Also, i can definitelly see why they hid traffic-gen behind a config-wall, as it’s essenially a wirespeed DDOS generator, and should not be trusted to the average home user
I have installed this new beta to check some fixes, but after downgrading back to 7.16 I started to receive an error in the log each 5 seconds. I don’t remember exact error text, but it was something like “the router can’t save changes because of problem in file system”. And it was impossible to reboot. Only netinstall helped.
Documentation of device-mode has been updated with more info. If anyone has any doubts or questions, please post them here and we will answer them in the documentation
Thanks for adding the “feature clarification table”. ![]()
Yes, this exactly. We are using traffic gen to detect presence and current config of a device, to avoid bridging and using proprietary windows app.
[quote=infabo post_id=1100759 time=1727808393 user_id=177714]
Coordinated button press is not the only option. Power cycle / remove power from device is an alternative.
Deploy your devices from now on with some remote-controlled powerplug and you’re good to go. future proof kind of…
…what if these remote-controlled powerplugs are online and somehow easily accessible (backdoor, unsecured, auth bypass, etc.) by “evil people” as well? Ransomware gangs triggering power plugs to unlock ROS device mode…![]()
![]()
![]()
![]()
![]()
![]()
[/quote]
Yeah, sure; we’ve also started in a garage; luckily, today we are way past that. If device requires any power-cycling to keep working, it’s replaced as failed. If it’s “normal behavior”, then it’s decommissioned and vendor is banned. I sincerely hope you were just making a joke about adding point of failures to “always on” setups. MikroTik devices are quite robust and, with exception of first batch(es) of CRS317 switches, I don’t remember any cases that would consistently require power interventions ![]()
I don’t know what you understood. In simple words: any change you make to device-mode settings can be either commited/confirmed by pusing reset-button or a cold reboot. Cold reboot stands for “take away power and restore power”, “unplug power cable, re-attach power cable”, or any other action that takes away energy from the device. I hope this is clear now. My - rather a sarkastic comment - had nothing to do with “stability”, “reliability”, or with “failures” or any regular behaviours of devices.
The device-mode can be changed by the user, but remote access to the device is not enough to change it. After changing the device-mode, you need to confirm it, by pressing a button on the device itself, or perform a “cold reboot” - that is, unplug the power.
I hope this is clear now.
I do understand why Mikrotik wants to lock down some device functionality, it makes perfect sense in regards of security.
On the other side I think the current situation (7.17beta2) with device-mode is not acceptable either. (I think I was the first to complain in this thread.) Visiting thousands of devices physically is just a huge issue.
So how about adding a kind of “grace period” for post-7.16 updates? The newly introduced device modes could be activated without physical interaction for a period of something like 24 hours after that update. If no action is taken in that time the modes become locked, just as they are now. Does that help most of us?
I don’t know what you understood. In simple words: any change you make to device-mode settings can be either commited/confirmed by pusing reset-button or a cold reboot.
Well, I should mention that I was quite surprised the first time when I confirmed a device mode change with pressing the reset button that the device actually cold booted…
I assumed that the reset button was just a soft input button, not hardwired to CPU reset, because you can also configure a script that will be run after pressing it for a short time. And of course there is all those different operations when pressing it for shorter or longer time during powerup.
So when I changed device-mode and pressed reset to confirm, I expected that it would print “OK! you have pressed reset!” and make the change, not to do a cold boot.
When a reboot would be required, I would have expected a warm boot (like /system reboot from commandline)…
The message shown on CLI is quite clear and does not leave room for interpretations:
update: please activate by turning power off or pressing reset or mode button in 4m27s
So how about adding a kind of “grace period” for post-7.16 updates? The newly introduced device modes could be activated without physical interaction for a period of something like 24 hours after that update. If no action is taken in that time the modes become locked, just as they are now. Does that help most of us?
That would be one solution.
Another one would be to auto-set all “newly added device-mode properties” to “yes” whenever RouterOS is upgraded.
One can argue “then it would not be very effective for its original purpose”, but we already have the situation where all existing devices are in enterprise/advanced mode and will not (I HOPE NOT!) switch to the new default device mode for 7.17 on that device.
(when I read the help page I conclude that all devices now running 7.16 will be in “advanced” mode after upgrade to 7.17)
The message shown on CLI is quite clear and does not leave room for interpretations:
update: please activate by turning power off or pressing reset or mode button in 4m27s
Maybe for you? For me that is not clear. When I press reset or mode button, it will activate the setting. But will it also reboot???
It does not tell that.
Maybe it even depends: pressing reset will reboot it, pressing mode button will not. Who knows?
(I was not able to test that because the devices I tested it on have no mode button)
We have added to the manual some more info about device mode, including that it will reboot in any case.
The console message will also be amended in future betas.
Well, I should mention that I was quite surprised the first time when I confirmed a device mode change with pressing the reset button that the device actually cold booted…
Device mode gets set into routerboot (could be it’s even baked into permanent storage just like the rest of routerboot contents) and I’d guess that as with every other change in routerboot, device has to be reset.
As to hard/soft reset … it’s hard to self-inflict hard reset on RB devices since they don’t have necessary (power management) hardware. So it was probably a (normal?) reboot.
Maybe for you? For me that is not clear. When I press reset or mode button, it will activate the setting. But will it also reboot???
It does not tell that.
Point taken. I don’t know either what happens on button press. That’s a bad thing I have to admit. Last time I changed device-mode was to enable “container” flag - but pressing the reset-button did not confirm it. Don’t know why it did not work. So I had to do the other thing: “turning power off”.
Pressing the button will initiate a reboot when device-mode command is issued before this.