Update via terminal when no internet access

RouterOS Beginner Basics
1

Hello,

STXsq 5 ac
6.4.6

I can ONLY access router via winbot using MAC addresses. Sometimes I also see an entry with a 0.0.0.0 ip address. Rebooting accomplished nothing, meaning the device is not getting assigned any address in the 196.168.88.x range. So no ip’s are being assigned thus can’t do anything regarding automatic downloads from internet to upgrade or fix.

I have downloaded the configuration file from NYC mesh for this device. I have downloaded the firmware for this device. The winbot gui does not seem to work - it shows firmware and scripts uploaded but I believe they are not being actually installed. How do I know this? Because I also uploaded the previous rev. of OSrouter thinking hey, let me downgrade the OS maybe that’s the problem. But after uploading the previous rev. and rebooting, the device still shows 6.4.6 and the identity does not reflect the identity in the script only the “identity” MikroTic.

I have heard that the gui doesn’t work, so I’m writing to ask what are the terminal commands that will

  1. upload the firmware from my computer and,
  2. upload the nyc mesh script from my computer and,
  3. command line that will verify if these commands worked.

Google searches only return results that would work under the assumption that the device still has internet access.

Thank you!

2

You can’t downgrade the OS just by uploading an older version and rebooting without performing the explicit downgrade command, otherwise RouterOS will detect the older version, ignore it, and discard the files.

As far as the script not working, any error in the script will cause it to be aborted, sometimes even before it starts. Often (but not always) there is a message in the log to tell you there was an error in the script.

The only way to be sure what is happening on an untested initialization script is to reset the configuration with no default configuration, then import the script by hand with verbose. If the script does any manipulation of the interface you’re using (like bridging it), you may lose connectivity before the script finishes; often you can rearrange the script to do that as one of the very last things and avoid that problem.

3

Thank you for the useful information. It turns out that upgrading to 6.46.2 somehow broke the router and downgrading to 6.44.6 brought everything back. I’m still troubleshooting why upgrading the router would have done this.