Normis,

You should pull the above package from the US mirror as it fails to install on any of our RB1000U and it has a different SHA1SUM to that of the same package from your Latvian mirror; observe:

[tez@tetris routeros]$ wget "http://download.mikrotik.com/routeros-powerpc-4.7.npk"
--2010-04-21 20:13:49-- http://download.mikrotik.com/routeros-powerpc-4.7.npk
Resolving download.mikrotik.com... 174.36.189.128, 66.228.113.58
Connecting to download.mikrotik.com|174.36.189.128|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11589985 (11M) [application/octet-stream]
Saving to: `routeros-powerpc-4.7.npk'

100%[======================================>] 11,589,985 565K/s in 63s

2010-04-21 20:14:54 (180 KB/s) - `routeros-powerpc-4.7.npk' saved [11589985/11589985]

[tez@tetris routeros]$ sha1sum -b routeros-powerpc-4.7.npk
2dad08d252c54ea12ea70bbd8ee5cd440df09122 *routeros-powerpc-4.7.npk
[tez@tetris routeros]$ rm -f routeros-powerpc-4.7.npk
[tez@tetris routeros]$ wget "http://www.mikrotik.com/download/router ... pc-4.7.npk"
--2010-04-21 20:15:48-- http://www.mikrotik.com/download/router ... pc-4.7.npk
Resolving http://www.mikrotik.com... 159.148.147.196
Connecting to http://www.mikrotik.com|159.148.147.196|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11589985 (11M) [application/octet-stream]
Saving to: `routeros-powerpc-4.7.npk'

100%[======================================>] 11,589,985 60.1K/s in 3m 10s

2010-04-21 20:18:59 (59.4 KB/s) - `routeros-powerpc-4.7.npk' saved [11589985/11589985]

[tez@tetris routeros]$ sha1sum -b routeros-powerpc-4.7.npk
cd3eeb14db2ef5d2f101fd7e851cd7ab6d9e3bee *routeros-powerpc-4.7.npk

As expected, the package from the Latvian mirror (http://www.mikrotik.com) works absolutely fine.

Please feel free to delete this thread once you have confirmed and replaced the package.

P.S. Any news on availability dates for the RB1100 ?

Regards,
Terry Froy
Spilsby Internet Solutions

netinstall-4.7.zip is also corrupt from http://download.mikrotik.com/netinstall-4.7.zip

Downloading it from http://www.mikrotik.com/download/netinstall-4.7.zip works just fine.

it's not corrupt, we verified it by downloading from different locations. you probably have a broken download cached in your proxy or browser cache.

I tried upgrade 450G:
1) downloaded from USA mirror:
system,error broken package routeros-mipsbe-4.7.npk
2) downloaded from Latvia mirror is OK:
jan/02/1970 02:00:32 system,info verified routeros-mipsbe-4.7.npk
jan/02/1970 02:00:36 system,info installed routeros-mipsbe-4.7

it's not corrupt, we verified it by downloading from different locations. you probably have a broken download cached in your proxy or browser cache.

Normis,

wget doesn't have a cache - hence why I demonstrated the problem using wget.

There is no proxy between my personal machine and the Internet - only thing besides Layer-2 switches between ourselves and our upstream routers is made by MikroTik

None of which have any proxying/caching turned on.

As a favour, could MikroTik please post checksums for all published files in a textfile that is in turn, PGP-signed by a MikroTik PGP key ?

This is similar to what most Linux distros do - at least that way, we will know if the files themselves are corrupt before we try and upload them to our devices.

This isn't the first time this has happened to us; the RouterOS 4.6 combined package for PPC was also corrupt when we initially tried to download it on release day but that had the same problem, although I believe you acknowledged that the files were corrupt on all mirrors - we got around it by using the separate .npk files and uploading those individually.

What mechanism do you use to get files to your mirrors anyway - rsync over SSH ?

I did notice that MikroTik doesn't have a United Kingdom mirror, if you want one, please PM me.

Regards,
Terry Froy
Spilsby Internet Solutions

These download problems from this mirror first started showing up with 4.6. Everything worked before then. I've heard of multiple reports of this issue from different clients scattered around the US. What could have changed on our end to cause this to start happening so consistently? What do we need to look at to fix this?