Torrent
Posted: Wed Feb 11, 2015 4:40 pm
torrent file for all versions please
http://www.mikrotik.com/download/router ... 27.torrentupgraded a few rb's just to see how it goes.....
no torrent to share the love?
http://www.mikrotik.com/download/router ... 27.torrentupgraded a few rb's just to see how it goes.....
no torrent to share the love?
Though, there are no seeders to download from yet
Yes, thanks for the link. But why has Mikrotik removed the all file torrent link?THX DDhttp://www.mikrotik.com/download/router ... 27.torrentupgraded a few rb's just to see how it goes.....
no torrent to share the love?
Though, there are no seeders to download from yet
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.But why has Mikrotik removed the all file torrent link?
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.17Because 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.But why has Mikrotik removed the all file torrent link?
Because the ALL package was only available by torrent.How is torrent related to what you asked for?
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.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 disagree.So now you have four clicks instead of one.
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?The biggest problem with torrents is the initial seeding. There exists no stable command line torrent client that we know of.
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.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.
#!/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.I hope somebody finds this useful -
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...)Anything outside the package (like the cm2) is beta anyway, and is optional.
For the purposes of this discussion, that's actually good to know; thanks.By the way, torrent did not include those non-standard packages anyway, since torrent creation was done using the same script.
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.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.
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).By the way, torrent did not include those non-standard packages anyway
+1Then 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).By the way, torrent did not include those non-standard packages anyway
#!/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
#!/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
./get_routeros.sh
./get_routeros.sh 6.34rc23
#!/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)"
how bout transmission for example?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.
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 uploadedThere is little benefit but a lot of maintenance. S3 + Cloudfront gives better speed and does not rely on the upload speed of volunteer seeders.
Now is possible to download HTML cluttered changelog fromFilled 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.
cd $DOWNLOADROOT/$version
( curl https://mikrotik.com/download/changelogs/current-release-tree || DOWNLOADERROR=$? ) |
pandoc --from=html --to=plain --no-wrap > CHANGELOG