Hi all,
I had Dude v3.1 running, but when right clicking on a device to upgrade routeros, only versions 3.20 and older would show. I had newer .npk’s in the files list, so I decided to upgrade the dude to v3.4. Now when I right click on a device and on the upgrade arrow, NO packages show, all of my packages are in the files list. I even removed and re uploaded them. Still no routeros packages show from the dude. Has anyone seen this yet?
I just wanted to say problem solved on this one. I didnt do anything except wait, I waited like 8 hrs and it started working all of a sudden, now when I right click a mikrotik device and click on upgrade it shows all npk versions including the newest 4.2.
What exactly is the secret of upgrading routers remotely from the Dude?
I’m running Dude 3.4 on a x86 with (licenced) RouterOS 3.16. I uploaded the v3.30 mipsle packages to the Dude files page and there they all are, but when I try to upgrade a Xroads running 3.24 - nothing happens.
If I set the Xroads to auto-upgrade from the x86 with its IP, user and password it finds no packages to upload, and using Winbox to look at the x86 it only shows 3.30 mipsbe packages in the files list.
If I select the device in Dude and hit the upgrade button - nothing. The RouterOS tab in the Dude relating to the device can list its current packages.
I haven’t tried the Dude ‘force-upgrade’ command, as that sounds like a recipe to break things.
So can you point all your machines to the Dude to auto-upgrade? And if so what do you point them at if not the machine the Dude is running on? But if you use the Dude to upgrade, how? Is it another of those arcane Mikrotik rituals involving virgins, moonlight and over-ripe tomatoes you only learn about at MUMs?