torrent file for all versions please
upgraded a few rb’s just to see how it goes…
no torrent to share the love?
http://www.mikrotik.com/download/routeros-ALL-6.27.torrent
Though, there are no seeders to download from yet 
THX 
DD
Yes, thanks for the link. But why has Mikrotik removed the all file torrent link?
Torrents will return after we surgically remove them from the RouterOS release system, and make them entirely separate. The biggest problem with torrents is the initial seeding. There exists no stable command line torrent client that we know of.
Because Mikrotik aren’t end-users and have no idea why end-users may want this feature. I, for one, want a complete archive of every single version, including the Netinstall which is known to work with every single version. If I don’t have these, supporting customers is a real PITA. We operate a “if it ain’t broke, don’t fix it” approach to our customers’ sites - upgrading for security reasons alone. This does mean that we have customers with ROS major versions 3, 4, 5 and 6. This is not a problem as long as we have a complete archive of every single ROS version. If we had faith that new ROS versions had been properly and thoroughly regression tested, we would probably ensure every customer was running the same version, but as it is, we know that there are unstable versions of ROS for different functions and so it would be suicidal for us to run cutting-edge on every customer’s site.
How is torrent related to what you asked for? You can already get any version by changing the URL in the download link. There are all releases of v6, most releases of v5 and even v4.17
Because the ALL package was only available by torrent.
There was no ALL package. The torrent included the same files, grouped in a folder. So now you have four clicks instead of one. If you are creating an archive, why don’t you make a script, that checks http://download2.mikrotik.com/routeros/LATEST.6 for changes and downloads the files ? In this case you will not even care how many links there are.
I don’t quite understand what you have said there 
, but to have a torrent for downloading the all files, like it used to be, is important for some of us. In order to be capable of supporting customers we need to have the files for every hardware platform, mipsbe, ppc, tile … As it stands now, we need to download for each hardware platform one by one, which is not comfortable.
I already answerd above, but if you need to make an archive of all files, why do you keep downloading manually anyway?
I disagree.
Previously it was : click all, click link, click download, click ‘save’ in torrent app. Click to drag and drop to archive.
Now it is : Click ‘mipsbe’, click download combined package link, click download all package link, click download capsman link, Click ‘x86’, click download combined package link, click download all package link, click download capsman link, click download link for ISO, Click ‘ppc’, click download combined package link, click download all package link, click download capsman link, Click ‘mipsle’, click download combined package link, click download all package link, click download capsman link, click download netinstall link. Right click, create new directory, type directory name, click to drag all downloads into directory.
By my reckoning, that’s 5 clicks for the old way and 20 clicks, some typing and a lot more time spent checking that nothing has been missed for the new way.
The old way I can pass on to an office junior to do. The new way needs an understanding of what packages are and what may or may not be missing or required and I have to do it myself to ensure it’s done right.
So four times as many clicks (and a lot more hassle), perhaps, but definitely not only four clicks.
OK, but why do you need to download all the files every time by yourself? Why not make a script do it, and you will no longer need to come to the website to check for any new versions.
Transmission is very stable in my experience - I’ve been using it in daemon mode on my home FreeBSD-based server for years, and it also ships with a command-line client tool you can use to add new torrents to the task queue. Is that what you need?
Because I need to be absolutely sure that I have got everything so the output of a script would have to be double-checked anyway. Also, I have absolutely no idea how to script on Windows boxes.
If I’m committed to spending time on this anyway, then I see little point in writing a script as that time would be wasted.
I am surprised that Mikrotik doesn’t have a reference package for every single version - i.e. an archive which contains everything related to a specific version number.
As for checking the LATEST.6 file, the download would be very easy to script if the index at http://download2.mikrotik.com/routeros/X.XX/ didn’t give permission denied (i.e. just a recursive wget would scrape everything). As it is, my understanding is that you need to know the filenames of all the files you want to download in advance. This doesn’t help if somebody mis-types something or if a new package/file is introduced.
All in all, what amazes me most is the lack of understanding about how end-users run their businesses and what they want to achieve. Several times on this forum, people requesting that things be done in a certain way (and for very good reasons) are told by Mikrotik “You’re doing it wrong”, rather than “You know your business best.”.
If the end user is using the phone to hit nails in the wall, we don’t need to make the phone stronger, we need to simplify the interface and imrove the workflow, so that this is not needed anymore.
Keeping an archive of all versions is fine. Like I said, torrent will return. I am simply explaining how this can be automated, so you don’t have to come and refresh the page every day.
I hope somebody finds this useful - the script checks the latest version, and then downloads it to a folder with the version name. Works also in MacOS if you have wget installed (for example with brew):
#!/bin/bash
version=$(wget http://download2.mikrotik.com/routeros/LATEST.6 -q -O -)
if [ ! -d "$version" ]; then
mkdir $version
cd $version
mkdir routeros
mkdir all_packages
mkdir capsman
cd routeros
for i in "mipsbe" "x86" "powerpc" "mipsle" "tile"
do
#RouterOS packages
wget -q http://download2.mikrotik.com/routeros/$version/routeros-$i-$version.npk
done
cd ..
#All packages
cd all_packages
for i in "mipsbe" "x86" "ppc" "mipsle" "tile"
do
wget -q http://download2.mikrotik.com/routeros/$version/all_packages-$i-$version.zip
done
cd ..
#CAPsMAN
cd capsman
for i in "-mipsbe" "" "-ppc" "-mipsle" "-tile"
do
wget -q http://download2.mikrotik.com/routeros/$version/wireless-cm2-$version$i.npk
done
cd ..
cd ..
echo DONE
else
echo Version $version is already downloaded
fi
Thanks; this is a good start. However, NAB makes a very good point: even if you check LATEST.6, you still have to know the specific names of the files, as well as whether there are any special packages that are separate (like wireless-cm2). If you guys change anything at all – the name or location of the LATEST.x file, the naming scheme of the upgrade package or all-packages zip files, add or remove hardware/CPU architectures, add or remove additional separate, special packages like wireless-cm2, etc. – then the script breaks and has to be updated.
Maybe you don’t need to introduce a torrent again, but simply provide the exact same archive file that you were offering as a torrent for direct download. Alternatively, put files up either on FTP, or provide a directory index for http://download2.mikrotik.com/routeros/ instead of hiding the files and the directory schema from casual browsing. Either of those last 2 suggestions would allow people to write a much more generic and robust script, instead of something fragile that has to constantly be updated and babysat.
– Nathan
Anything is possible, of course, but those files have not changed for many years. Anything outside the package (like the cm2) is beta anyway, and is optional.