security related stuff is an exception.

https://help.mikrotik.com/docs/display/ROS/Device-mode

You're just trolling right now, right?

Device mode does not target any explicit vulnerability. It is a security measure. Just read the wiki article about what device mode does and look for meris botnet here in the forum. It may answer your questions.

I worry Mikrotik knows about new vulnerability and device-lock is some fix for it. And, they don't want to say what the vulnerability is yet.

i was using accept in dst address in NAT for local ip tv to make ip tv see all users ip address after update to 6.48.6 i cant open ip tv downgade fix it or remove accept rule and use !dst address in Masquerade rule, what makes this happen ?

6.48.6 broke all PPP only for me? Сyclic PPP reconnections (client or server - it doesn't matter).
downgrade to 6.48.5 - fixed problem

And by all PPP you mean L2TP, SSTP, OVPN, PPTP, PPPoE or actually PPP that runs over serial connection?

Thank You Mikrotik staff for releasing routeros in long-term branch that makes my life so much more interesting.

Thank You Mikrotik staff for releasing routeros in long-term branch that makes my life so much more interesting.

And you did test the software on equal routers with same config and software version at a local site before you did the upgrade?
And you did also upgrade at the same time as software was released?
And you did read all message on the forum, the first day?

If not, this is much your fault.

RouterOS is a complex router with lots of function. I know may big company that has released software that has give breakdown of bigger network. To just mention one, Cisco. No one can garanti that all possible has been tested and all bugs are removed.

So wait some time before upgrade, read forum and do a test before upgrade lots of routers.

The question is what was the CAUSE that anything prior to 6.41.4 was bricked.

The question is what was the CAUSE that anything prior to 6.41.4 was bricked.

Why did you not upgrade before? 6.41.4 was released more than 3 1/2 year ago.
You have missed out lots of security fixes.

Something strange with multicast

once again, I admit it was my fault. to much faith. i'm with mikrotik since routerOS 2.9.27 or so. So I had many many situations up to now, with buggy routerOS. I Should have learn it.
So last time after many succesfull hand made upgrades decided to do it on mass. Stupid I was.
And since that time mikrotik long-term release refers for me to "dont try it on production. EVER"

Yes ofcourse Mikrotik is no top-shelf company but could at least do that SIMPLE test if release is upgradable from every earlier ROS, at least from the same generation.
but hey! let our customers be again betatesters in a hardway.

thank You mikrotik again, unforgettable moments, very close to my cusotemers, during last two weeks. especially important during another wave of covid.

6.48.6 broke all PPP only for me? Сyclic PPP reconnections (client or server - it doesn't matter).
downgrade to 6.48.5 - fixed problem

When will RouterOS v6 reach end of life?

I worry Mikrotik knows about new vulnerability and device-lock is some fix for it. And, they don't want to say what the vulnerability is yet.

IF (and that's a big IF) this would be the case, don't you think they FIRST would make sure to have the fix in place BEFORE making public what the problem is ?
Logical sequence of communicating.

Not saying there IS a vulnerability at play here. But it does make perfect sense to provide the fix first.

IF (and that's a big IF) this would be the case, don't you think they FIRST would make sure to have the fix in place BEFORE making public what the problem is ?
Logical sequence of communicating.

Not saying there IS a vulnerability at play here. But it does make perfect sense to provide the fix first.

Your guess should be correct.

Your guess should be correct.

I also had very good luck with long-term 6.47.10, and then seemingly rush out a "long term" without promoting a "stable". Mikroitk doesn't seem big on disclosure, so that was my worry.

Apparently FTP and SMB effected by a DoS vector in 6.47.10. See https://www.cvedetails.com/vulnerabilit ... rotik.html with details here https://github.com/colorlight/mikrotik_ ... o_vulns.md

If suspicious configuration is detected, the suspicious configuration will be disabled and the flagged parameter will be set to "yes". The device has now a Flagged state and enforces certain limitations.

To exit the flagged state, you must perform the command "/system/device-mode/update flagged=no". The system will ask to either press a button, or issue a hard reboot (cut power physically or do a hard reboot of the virtual machine).

Seems like you're running a command without fully understanding its parameters?

Seems like you're running a command without fully understanding its parameters?

forum was not my 1st choice,because of the "kind" comment above. :)

So your idea is to have somebody else read the docs for you?

Back to the problem you're having: as device mode is pretty new functionality, it might have some bug. So perhaps you should try the other possibility (press the button). And be sure to do it within indicated time interval (5 minutes). If that doesn't work, then register trouble ticket with Mikrotik support.

Disabling PoE does not comply with "cold reboot" ?

/system device-mode update mode=home scheduler=yes romon=yes bandwidth-test=yes flagged=yes

or am i missing something? AP boots back info enterprise mode....

• Cut off DC power

• Press the rest button

• Cut off DC power

@mkx

are you guessing or have you checked already? i got v6.48.6 and it's not there , then why im asking here

i got that, and wehre is "locking mechanism"?
that has been here since device-mode pops up

I worry Mikrotik knows about new vulnerability and device-lock is some fix for it. And, they don't want to say what the vulnerability is yet.

Those devices don't have Wave2 wireless chips.

v6 has it reached the end?

Bonding is done on CPU, not on bridge, is not hardware-offloaded.
You can see the H, when supported and enabled, only on hardware ports, and also not all switch models support more than one bridge on hardware offload.
I not remember all models at memory, check the docs.

bonding1 belongs to bridge1.

Now contrast the RB5009, where you're back to 1 bridge, since everything's now on a single switch chip.

I was upgrading from 6.11 to 6.48.6.

Ok this day is too late but tomorrow will be test from netinstall.

The last RouterOS v6 (long-term) was released nearly a year ago. Is Mikrotik going to release a newer RouterOS v6 (long-term) version?

What's new in 6.48.6 (2021-Dec-03 12:15):

Are there any noteworthy bugs in latest v6 versions?

Are there any noteworthy bugs in latest v6 versions?

Apparently it's vulnerable to CVE-2022-45315

It's possible for an authenticated user to achieve code execution.

good version

It could have been longer if Russia had not destroyed our energy.

... RouterOS enables this [SNMP?] by default ...

The last RouterOS v6 (long-term) was released nearly a year ago. Is Mikrotik going to release a newer RouterOS v6 (long-term) version?
Zero-Day Initiative:
SUCCESS - DEVCORE becomes the first team ever to successfully execute two different Stack-based buffer overflow attacks against a Mikrotik router and a Canon printer in the brand new SOHO SMASHUP category. They earn a cool $100K cash and 10 Master of Pwn points.
https://www.zerodayinitiative.com/blog/ ... ne-results
Does anybody know about this Stack-based buffer overflow attacks against a Mikrotik router?

Example code

{
:local test1 do={:put "test1"}
:local test2 do={:put "test2"}
:local test3 do={:put "test3"}
:local test4 do={:put "test4"}
:local test5 do={:put "test5"}
[]
[]
}

I see censorship is starting to work on this forum and inconvenient facts are pushed to other threads.