Page 1 of 1

Torrent

Posted: Wed Feb 11, 2015 4:40 pm
by mars
torrent file for all versions please

Re: RouterOS v6.27 released

Posted: Wed Feb 11, 2015 7:19 pm
by ffernandes
upgraded a few rb's just to see how it goes.....
no torrent to share the love?

Re: RouterOS v6.27 released

Posted: Wed Feb 11, 2015 7:45 pm
by Cha0s
upgraded a few rb's just to see how it goes.....
no torrent to share the love?
http://www.mikrotik.com/download/router ... 27.torrent

Though, there are no seeders to download from yet :(

Re: RouterOS v6.27 released

Posted: Wed Feb 11, 2015 7:55 pm
by ffernandes
THX :DDD
upgraded a few rb's just to see how it goes.....
no torrent to share the love?
http://www.mikrotik.com/download/router ... 27.torrent

Though, there are no seeders to download from yet :(

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 12:35 pm
by Caci99
THX :DDD
upgraded a few rb's just to see how it goes.....
no torrent to share the love?
http://www.mikrotik.com/download/router ... 27.torrent

Though, there are no seeders to download from yet :(
Yes, thanks for the link. But why has Mikrotik removed the all file torrent link?

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 12:59 pm
by normis
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.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:14 pm
by NAB
But why has Mikrotik removed the all file torrent link?
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.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:22 pm
by normis
But why has Mikrotik removed the all file torrent link?
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

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:24 pm
by NAB
How is torrent related to what you asked for?
Because the ALL package was only available by torrent.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:28 pm
by normis
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.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:33 pm
by Caci99
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.
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.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:35 pm
by normis
I already answerd above, but if you need to make an archive of all files, why do you keep downloading manually anyway?

http://download2.mikrotik.com/routeros/LATEST.6

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:55 pm
by NAB
So now you have four clicks instead of one.
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.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 1:57 pm
by normis
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.

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 2:02 pm
by andriys
The biggest problem with torrents is the initial seeding. There exists no stable command line torrent client that we know of.
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?

Re: RouterOS v6.27 released

Posted: Thu Feb 12, 2015 2:24 pm
by NAB
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.
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.".

Re: Torrent

Posted: Thu Feb 12, 2015 2:31 pm
by normis
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.

Re: Torrent

Posted: Thu Feb 12, 2015 2:35 pm
by normis
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

Re: Torrent

Posted: Thu Feb 12, 2015 3:04 pm
by NathanA
I hope somebody finds this useful -
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

Re: Torrent

Posted: Thu Feb 12, 2015 3:06 pm
by normis
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.

Re: Torrent

Posted: Thu Feb 12, 2015 3:14 pm
by NathanA
Anything outside the package (like the cm2) is beta anyway, and is optional.
But the whole point of archiving is to capture *everything* that is being offered, as insurance against that same software becoming unavailable from an official source sometime in the future. If I have a customer set up on CAPsMANv2 (beta) running on 6.25, and everything is working just fine and I don't want to risk an upgrade, I want to be able to have a copy of all of the files that were used to set them up at my disposal in case their hardware takes a dump, needs to be replaced, and I need to re-image a new device for them that is set up *exactly* the same way, "beta" or not. (The "beta" label matters not as long as it works for you...)

Or, *more importantly*, let's say that they are running CAPsMANv2 on 6.27, but I run into a bug, and it is determined to be a regression (it worked in a previous release). If I have archived everything from the past, I can go back into that archive, retrieve an older, working version, and get my customer's problem fixed.

Everybody chiming in here just wants software archiving to be easy, hands-off, and robust.

-- Nathan

Re: Torrent

Posted: Thu Feb 12, 2015 3:14 pm
by Caci99
I have to admit I am bit lost with the scripting and rest. We were supposed to have an easy life, not make it harder. For me it was easy enough to browse on the download page when new version was out, click on torrent link and download. We even used to get email when new version was out, never mind that :). If the link will be back, that is fine, in what ever form you guys plan it.

Re: Torrent

Posted: Thu Feb 12, 2015 3:15 pm
by normis
By the way, torrent did not include those non-standard packages anyway, since torrent creation was done using the same script.

Re: Torrent

Posted: Thu Feb 12, 2015 3:16 pm
by NathanA
By the way, torrent did not include those non-standard packages anyway, since torrent creation was done using the same script.
For the purposes of this discussion, that's actually good to know; thanks.

-- Nathan

Re: Torrent

Posted: Thu Feb 12, 2015 3:20 pm
by NathanA
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.
Another example, though, of when the script needs to be updated: even if file naming in v7 does not change, you have to start checking LATEST.7 instead of LATEST.6. Seems unnecessary to have to change the script for every major version. At the very least, perhaps you could have a plain LATEST without a .6 or .7 suffix that always has the absolute latest version number in it? Then you can point the script at that.

-- Nathan

Re: Torrent

Posted: Thu Feb 12, 2015 4:54 pm
by NAB
By the way, torrent did not include those non-standard packages anyway
Then I don't know what I've been downloading because the torrents I've got for 6.22, 6.23, 6.24 and 6.25 all include cm2 (as well as the netinstall-tile which doesn't appear to be on the download page).

Re: Torrent

Posted: Thu Feb 12, 2015 5:08 pm
by mars
By the way, torrent did not include those non-standard packages anyway
Then I don't know what I've been downloading because the torrents I've got for 6.22, 6.23, 6.24 and 6.25 all include cm2 (as well as the netinstall-tile which doesn't appear to be on the download page).
+1

Re: Torrent

Posted: Fri Feb 13, 2015 9:21 am
by normis
My script includes CM2, I was not talking about that package, just any extra packages in general

Re: Torrent HTTP seed (Web seed)

Posted: Thu Mar 19, 2015 11:04 pm
by mmv
One idea. To seed torrent not necessary to have torrent daemon at all!
Need only declare HTTP seed (Web seed) at creation Torrent file and make seed from http URL.

Possible it simpler to integrate in build system.

Re: Torrent

Posted: Thu Apr 23, 2015 12:39 am
by 111111
It will be nice to share all history of mikrotik software
I like this MIRROR

Re: Torrent

Posted: Thu Apr 23, 2015 7:12 am
by lambert
normis, I modified your script slightly. It should work on *BSD and Mac OS X/Darwin without having to install extra software and everywhere else with wget.

Tested on FreeBSD and MacOS X.
#!/usr/bin/env sh

ARCH=$(uname -s)

case $ARCH in
FreeBSD) 	GETIT="fetch -q";
		OUT="-o -";
		;;
*BSD|Darwin)	GETIT="ftp"; # ftp(1) doesn't have -q, but without a term is quiet
		OUT="-o -";
		;;
*) 		WGET=$(which wget);
		if [ ! -z $WGET ]; then
		  GETIT="$WGET -q";
		  OUT="-O -";
		else
		  echo "No download program we know how to use found on this platform";
		fi ;;
esac;

version=$($GETIT $OUT http://download2.mikrotik.com/routeros/LATEST.6 )
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
      $GETIT http://download2.mikrotik.com/routeros/$version/routeros-$i-$version.npk >> /dev/null
    done
  cd ..
  #All packages
  cd all_packages
  for i in "mipsbe" "x86" "ppc" "mipsle" "tile"
  do
    $GETIT http://download2.mikrotik.com/routeros/$version/all_packages-$i-$version.zip >> /dev/null
  done
  cd ..
  #CAPsMAN
  cd capsman
  for i in "-mipsbe" "" "-ppc" "-mipsle" "-tile"
  do
    $GETIT http://download2.mikrotik.com/routeros/$version/wireless-cm2-$version$i.npk >> /dev/null
  done
  cd ..
  cd ..
  echo DONE
else
  echo Version $version is already downloaded
fi

Re: Torrent

Posted: Sat Jun 06, 2015 12:15 am
by mmv
I great script. But one more question.
Where located changelog, to download it together with packages?

Re: Torrent

Posted: Mon Aug 24, 2015 11:22 pm
by gmsmstr
I like torrents, don't use a script, would be nice to have a RSS feed for torrents then just point our torrent app and let it eat when a new version comes out. .BTW, looks like no full seeds for 6.31 :(

Re: Torrent

Posted: Wed Sep 02, 2015 12:48 am
by mmv
Download script stop working after 6.31, because of trailing space in LATEST.6
Fixed by trimming
#!/bin/bash
WGETOPT="-q"

trim()
{
    local trimmed=$1
    trimmed=${trimmed%% }
    trimmed=${trimmed## }

    echo "$trimmed"
}

version=$(trim $(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 $WGETOPT 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 $WGETOPT 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 $WGETOPT http://download2.mikrotik.com/routeros/$version/wireless-cm2-$version$i.npk
done
cd ..
cd ..
echo DONE
else
echo Version $version is already downloaded
fi

Re: Torrent

Posted: Sat Dec 26, 2015 12:46 pm
by NEJI
Got lazy and updated one of the scripts here. This script will collect files for all listed "instruction sets" as well as the CHR images.

Usage:
To get the "current" release. Note that you can have a daily cronjob running to get the latest files
./get_routeros.sh


Get a specific release. This is so that you can get the latest RC release.
./get_routeros.sh 6.34rc23
Notes on usage:
Before running, make sure the the directory supplied for the "ros_dir" variable does exist or at least change it to where you want your files to be downloaded to.

Filled under "would be nice";
If someone can explain or show me how to get the "changelog" per release type then I can update this script to get that information as well.
The same can be mentioned for the MD5 checksums. Maybe even add code to check and confirm that the integrity of the file is correct.
#!/bin/bash 
ros_dir="/data/routeros"
http_base_url="http://download2.mikrotik.com/routeros"
START=$(date +%s)
cd $ros_dir || exit
if [ -z "$1" ]
    then
        echo "Getting the latest release"
        version=$(wget $http_base_url/LATEST.6 -q -O - | awk '{print $1}')
else 
    echo "Release parameter has been supplied. Using that in order to download specific ROS release"
    version=$1
fi

if [ ! -d "$version" ]; then
    echo "Release $version has not been downloaded as yet."
    echo "Creating directories for $version..."
    mkdir "$version"
    cd "$version" || exit
    mkdir routeros
    mkdir netinstall
    mkdir all_packages
    mkdir capsman
    mkdir chr
    #RouterOS main - Start	
    cd routeros || exit
    echo "Getting basic upgrade package(s)..."
    for i in "mipsbe" "smips" "arm" "x86" "powerpc" "mipsle" "tile"
        do
        #RouterOS packages
        echo "-> $i"
        wget -q "$http_base_url/$version/routeros-$i-$version.npk"
    done
    cd - || exit
    #RouterOS main - End
    #RouterOS netinstall - Start
    cd netinstall || exit
    echo "Getting netinstall..."
    for i in "mipsbe" "smips" "arm" "x86" "powerpc" "mipsle" "tile"
        do
        #RouterOS netinstall
        echo "-> $i"
        wget -q "$http_base_url/$version/netinstall-$version-$i.zip"
    done
    cd - || exit
    #RouterOS netinstall - End
    #All packages - Start
    cd all_packages || exit
    echo "Getting all package(s)..."    
    for i in "mipsbe" "smips" "arm" "x86" "powerpc" "mipsle" "tile"
        do
        echo "-> $i"
        wget -q "$http_base_url/$version/all_packages-$i-$version.zip"
    done
    cd - || exit
    #All packages - End
    #CAPsMAN - Start
    cd capsman || exit
    echo "Getting CAPsMAN package(s)..."
    for i in "-mipsbe" "-smips" "-arm" "-x86" "-powerpc" "-mipsle" "-tile"
        do
        echo "-> $i"
        wget -q "$http_base_url/$version/wireless-cm2-$version$i.npk"
    done
    cd - || exit
    #CAPsMAN - End
    #All Cloud Hosted Router - Start
    cd chr || exit
    echo "Getting Cloud Hosted Router images..."
    for i in "vmdk" "vhdx" "vdi" "img.zip"
        do
        echo "-> $i"
        wget -q "$http_base_url/$version/chr-$version.$i"
    done        
    cd "$ros_dir" || exit
    #All Cloud Hosted Router - End	
    echo "Finished downloading files for release $version"
else
    echo "Release $version has already been downloaded"
fi
END=$(date +%s)
DIFF=$(( END - START ))
echo "Execution time: $DIFF second(s)"

Re: RouterOS v6.27 released

Posted: Mon Dec 28, 2015 9:21 pm
by Zorro
omgosh, i do really Miss downloading AND seeding RouterOS :/ always wonder bout initial reasons for removing them :(
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.
how bout transmission for example?
the most functional torrent client(or server ;)among "low-overhead" ones.
and yes, its had relatively small size.
other things are - several times bigger, sadly. and/or depend on libraries/sources of comparably sizes, which nullify benefits/point to use them in many applications.

Re: Torrent

Posted: Tue Dec 29, 2015 9:44 am
by normis
There is little benefit but a lot of maintenance. S3 + Cloudfront gives better speed and does not rely on the upload speed of volunteer seeders.

Re: Torrent

Posted: Tue Dec 29, 2015 10:09 pm
by Zorro
depend appoach. as for S3/amazon/akamai/azure/hp/rest - its completely lack Control/security of Service Level, quite expoitable/abusable by number of entities, interested in. generally relying in any kind of 3rd-parties quite irresponsible and can lead to number of unwanted consequences for both companies and individuals, trying. its /sometimes/cheaper and sometimes simpler, but drawbacks outweight in my eyes.
as for torrents, compared - they had NO overhead. MT - may even not need to had tracker(but they may publish to number of popular FOSS trackers if they wish), just publish appropriate magent links to content and DHT network do the rest, thanks to seeders contribution. after they initially feed by content, of course.

Re: Torrent

Posted: Tue Mar 08, 2016 11:03 pm
by mmv
May be release system support more undocumented URLs like http://download2.mikrotik.com/routeros/LATEST.6 ?
URL with filelist of released files allow to simplify and stabilize download script.

Re: Torrent

Posted: Wed Mar 09, 2016 11:51 am
by chechito
There is little benefit but a lot of maintenance. S3 + Cloudfront gives better speed and does not rely on the upload speed of volunteer seeders.
im agree the only way torrent works reliably is on private trackers where users are obligated to seed the torrent until the downloaded is equal to uploaded

Re: Torrent

Posted: Wed Mar 09, 2016 12:11 pm
by Caci99
Guys, this topic has got away from its main subject.
The whole point of this topic is to have the ability to download all files of all architectures (mipsbe, tile, ppc, etc.). This is what is asked about a year ago. Whether it is a torrent or a file from http makes little difference. Some of us have to work with different routerboards and assist different customers so we do need those files, there is no point in arguing why don't you download what you need, because we need them all.
It is comfortable and not time consuming to download all of them at the same time, instead of going from http download page and select to download one by one.

Posted: Wed Mar 09, 2016 6:33 pm
by jarda
That's the point.

Re: Torrent

Posted: Thu Jul 13, 2017 9:58 pm
by mmv
Filled under "would be nice";
If someone can explain or show me how to get the "changelog" per release type then I can update this script to get that information as well.
Now is possible to download HTML cluttered changelog from
https://mikrotik.com/download/changelog ... lease-tree
https://mikrotik.com/download/changelog ... lease-tree
https://mikrotik.com/download/changelog ... lease-tree

I convert it to plain text by pandoc.
cd $DOWNLOADROOT/$version
( curl https://mikrotik.com/download/changelogs/current-release-tree  || DOWNLOADERROR=$? ) |
pandoc --from=html --to=plain --no-wrap > CHANGELOG

Re: Torrent

Posted: Fri Apr 13, 2018 12:00 pm
by NEJI
I've rewritten "get_routeros.sh" that I previously posted.

New code is at https://github.com/jawug/ros-getter/blo ... -getter.sh
It works for versions from when capsman was dropped as a package.

Use at own risk.