Our company integrates RB912uag routerboards into our consumer products. To extend the reset button to the outside of the case, we rely on the solder pads provided on the backside of the RB912's PCB, soldering two wires and running them to a push button located where the user can access it. The prob...

Yes, I too am very reluctant to adopt new RouterOS versions; I only put well-vetted versions into the field because I have been burned in the past by introduced bugs or by inconvenient new features that require difficult adjustments on my part. (With emphasis on progress, insufficient regard is give...

I've repeated the four tests but with RoMON overlaying the existing IP and MNDP traffic -- very interesting: RoMON consistently discovers the nodes that are invisible to MNDP. From this I'm inclined to conclude that we've uncovered a bug in MikroTik Neighbor discovery. (Unless perhaps some additiona...

@pe1chl, I've been reading the wiki about RoMON; I've never used it before. Based on your suggestion, I'm setting this up on my test network to see what it might reveal. (But other than a diagnostic tool, I can't use it in a final solution because these units are all configured and deployed.) I migh...

Yes @sid5632, I agree that it's not necessary to look too far afield; to rule out those conceivable situations that @pe1chl mentions, let me state that I'm relying on MNDP--not LLDP--and that I haven't blocked UDP port 5678 or broadcasts generally. As evidence: discovery frames still make it through...

Lately when using WinBox to discover IP/MAC addresses down multiple, wireless, AP-to-Station links, I have been unable to discover interfaces beyond those that are configured as station. This used to work, but now in RouterOS 6.47, I find that unless a wlan interface is configured as AP, I cannot se...

Has anyone found this to be a problem: I wrote an signal-strength script that I have used for many years. After upgrading from 6.21.1 to 6.36.6 I had to modify it for the new method of controlling the LEDs. (I can’t use the built-in “type=wireless-signal-strength” feature because that has fixed RSSI...

The problem is that the output from this command can't be captured by a script. We used to be able to to this: :local foo [/interface wireless info get wlan1 supported-bands]; :local fooArray [:toarray $foo]; :local supportedband [:pick $fooArray 0 1]; or :foreach b in=$fooArray do={ . . . But I fin...

I'm having problems with this too. For years I've been using NetInstall on several different RB types with no issues. Now however, I have a batch of RB433 boards coming in with ROS 5.26, firmware 3.18, and all of the half-dozen boards I've tested so far have refused to NetInstall as expected. I don'...

This is a critical problem for us. We rely on very elaborate scripts—amassed over years of development—to dovetail with native C++ application software we build for our customers. In many cases, these RouterOS scripts write out text whose purpose is to write out yet more escaped text that gets inter...

But isn't the "firmware" just the bootloader? How can that affect RouterOS? It just permits serial upload of ROS from Netinstall.
If it's bad, we wouldn't be able to Netinstall or at worse, not be able to start RouterOS. Am I misunderstanding what the "firmware" is?

To create a local directory, I've been using this trick for years: /tool fetch address=127.0.0.1 src-path=someDummyFile user=admin password=xxxx \ mode=ftp dst-path=newDirName/newFileName; The fetch command seems to set up the credentials with ppp and then ftp creates the newDirName. Just delete the...