Files are hosted on Amazon S3. It doesn’t support serving torrent of a folder. We could only provide torrent of a ZIP file of all the files, but that is not what you want, probably. Example:
http://mikrotikdownload.s3.amazonaws.com/routeros/6.35rc12.zip?torrent
Even that is better than nothing.
HTTP download from S3 is not nothing 
OK, anyone else? If ZIP via Torrent is fine, we could start doing that.
Presonally I don’t care if it’s zip or a folder or torrent.
I care to be able to download the full release containing everything (as the old .torrent used to) so that I have all archs offline.
I manage many Mikrotik installations on a non-internet network(s) so I need to have all files offline to easily upload them when upgrading.
Downloading them one by one as you essentially forced us when you stopped the .torrent file is not helpful or productive (at least in my case).
Zip is great for me also. Is there a rss feed I can put in my torrent downloader to get the files right when they are published?
To my great surprise, upgrading to 6.35rc12 (testing) void the problem as far as I can see. Hope to see 6.35 release soon.
Could you please make a choose that Istanbul in Asia or Europe region before the next update?
It would be fine even if you distribute ZIP via plain http. Torrent was useful to me just because it allowed to download all the files at once.
the file is in all of these regions, download will start from the closest one to you.
United States
Atlanta, GA
Ashburn, VA (3)
Chicago, IL
Dallas/Fort Worth, TX (2)
Hayward, CA
Jacksonville, FL
Los Angeles, CA (2)
Miami, FL
New York, NY (3)
Newark, NJ
Palo Alto, CA
San Jose, CA
Seattle, WA
South Bend, IN
St. Louis, MO
Europe
Amsterdam, The Netherlands (2)
Dublin, Ireland
Frankfurt, Germany (3)
London, England (3)
Madrid, Spain
Marseille, France
Milan, Italy
Paris, France (2)
Stockholm, Sweden
Warsaw, PolandAsia
Chennai, India
Hong Kong (2)
Mumbai, India
Manila, the Philippines
Osaka, Japan
Seoul, Korea (2)
Singapore (2)
Taipei, Taiwan
Tokyo, Japan (2)Australia
Melbourne, Australia
Sydney, AustraliaSouth America
São Paulo, Brazil
Rio de Janeiro, Brazil
Amazon Cloudfront is not present in Istanbul
++ Exactly!
Same link:
http://mikrotikdownload.s3.amazonaws.com/routeros/6.35rc12.zip?torrent
Just remove ?torrent:
http://mikrotikdownload.s3.amazonaws.com/routeros/6.35rc12.zip
Beg me a pardon, I wonder if anyone care for bugs in 6.34.2 or this is just a way of distribution buggy version topic?
http://mikrotikdownload.s3.amazonaws.com/routeros/6.34.2.zip
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>EE531A7AF04C691C</RequestId><HostId>ZgDad9tZ2OAXthP+vHdM58Q0Ez8otLabmExNiAS/QZjBBItrFHyRpM9+W2uK0tT9DqNgdNiMcC4=</HostId></Error>
Just publish the proper links on the downloads page.
We shouldn’t have to guess them each time 
It is only starting mentioned RC version. Next releases only. Old releases not published as ZIP. They will be on download page
Oh sorry. I didn’t read all page. I mean, there is two selection Asia/Istanbul and Europe/Istanbul in clock time zone settings .
Hi the export file seen wrong on my CCR1009.
ver 6.34.2
/interface ethernet
set [ find default-name=ether5 ] l2mtu=1588 name=ether1-gateway
set [ find default-name=ether6 ] l2mtu=1588 name=ether2-master-local speed=
1Gbps
set [ find default-name=ether7 ] l2mtu=1588 master-port=ether2-master-local
name=ether3-NAS
set [ find default-name=ether8 ] l2mtu=1588 master-port=ether2-master-local
name=ether4-ap speed=1Gbps
set [ find default-name=ether1 ] l2mtu=1590 name=ether5
set [ find default-name=ether2 ] l2mtu=1590 name=ether6-mp
set [ find default-name=ether3 ] advertise=
10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full l2mtu=1590
name=ether7-dns320
set [ find default-name=ether4 ] l2mtu=1590 name=ether8-mio
set [ find default-name=sfp-sfpplus1 ] auto-negotiation=no l2mtu=1590 speed=
1Gbps
set [ find default-name=sfp1 ] l2mtu=1590 rx-flow-control=on tx-flow-control=
on
older version.
/interface ethernet
set [ find default-name=ether1 ] l2mtu=1588 name=ether1-gateway
set [ find default-name=ether2 ] l2mtu=1588 name=ether2-master-local speed=
1Gbps
set [ find default-name=ether3 ] l2mtu=1588 master-port=ether2-master-local
name=ether3-NAS
set [ find default-name=ether4 ] l2mtu=1588 master-port=ether2-master-local
name=ether4-ap speed=1Gbps
set [ find default-name=ether5 ] l2mtu=1590
set [ find default-name=ether6 ] l2mtu=1590 name=ether6-mp
set [ find default-name=ether7 ] advertise=
10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full l2mtu=1590
name=ether7-dns320
set [ find default-name=ether8 ] l2mtu=1590 name=ether8-mio
set [ find default-name=sfp-sfpplus1 ] auto-negotiation=no l2mtu=1590 speed=
1Gbps
set [ find default-name=sfp1 ] l2mtu=1590 rx-flow-control=on tx-flow-control=
on
Looks like noone here care for bugs, just for new version package availability.
The only way to get rid is to downgrade.
Following up on this, I still get this really annoying error every minute!
It floods my logs making them useless!
I got some screenshots with ipsec debug enabled in case someone can help.
ipsec_error_850Gx2.png
ipsec_error_x86.png
The messages above keep on looping over and over and every minute I get the error mentioned on my previous post.
I’ve tried many things (except reinstall which is not an option at this time) and nothing seems to fix this annoying issue.
It just keeps on trying to reconnect (or whatever it’s trying to do) on an already connected and working peer.
It seems that every time Mikrotik changes something related to IPsec all hell breaks lose! 
We do care about bugs very much! I am not so sure about Mikrotik though
A friendly and constructive advice:
Then send the bugs TO Mikrotik! Email: support@mikrotik.com 
This is a userforum, so you can not expect Mikroitk to answer you here, its just a bonus if they do!
Sure sometimes if we post a problem or possible bug on forum, we might get an answer straight away from MT staff or other users BECAUSE someone already sent in an support request to MT about the bug/issue and they are therefor aware of it and maybe already working a solution.
BUT bitching about not getting an answer from Mikrotik on forum does not help either you, Mikrotik or other users on the fourm!
Instead first send your SUPPOUT file right away, and a good description of the problem, and preferably how MT can reproduce it and send this to: support@mikrotik.com .
Then you will get a ticketnumber, and MT support will have a look at your problem and relay it to developers if there is a confirmed bug!
And you will get answer from MT if they do or dont manage to replicate the problem!
THEN you can ALSO post here on the forums if you want to make other users aware of the possible bug, and maybe get input back from other users who might have the same problems, or maybe even someone has found a workaround or other remedy for this bug that can help.
And as mentioned if you get a BONUS, MT will also put a reply on the forum about the issue if they found the problem and/or a solution to it!
This way ALL users of the forum can use it to mutual benefit of all, instead of wasting time on reading a lot of posts complaining about not getting an answer from MT about a bug on the forums!
And just to make myself clear, I am NOT saying you should not search or post questions/reports about bugs on forums before you send the support request to MT!
What I AM saying is that you can not EXPECT to find an answer on forums from MT/Other users before you do!