Thanks for that.To not confuse people, we don't make them learn processor revisions - just choose the product name.
Normis I've just downloaded "all_packages-ns-2.9.51.zip". Unzipped it contains packages like "ntp-2.9.51-ns.npk"look at the package names. they correspond to the CPU type.
Normis, YOU might know that for some arcane reason 'ns' is the code for the processor in the 100/500 series for v2, and 'mipsl' is the code for v3, and 'ccp' appears to be some sort of code for the processor in the 600 series, but YOU live and breath these things, you probably have pictures of these things on the walls of your home surrounded by candles. You've forgotten more about these wretched things than us lesser mortals could possibly want to know.RB600 and 1000 doesn't even support 2.9. You are supposed to download current version, not the old one. Use v3
Yes you do. It's almost idiot proof so there's a sporting chance even I might be able to get that part of it right.PLUS you use the System Selector to get the correct ones.
I've only downloaded one v3 set. I selected RB100 series on the download page. It gave me a set of packages called all_packages-mipsle-3.7.zip. I used it to upgrade an RB133C and it went to pieces - as I've reported in another thread. I had to spend a couple of hours taking it down from the roof, getting access to it and downgrading it back to 2.9.46, with which it's now working perfectly well.you have that for v3 (i already said that).
Unhappily, you see Normis, I don't know what processor these boards have. I don't care what processor these boards have, as long as it does its job. I rely on you guys to do your sums and get it right and provide me with a board that does what you say it will. I don't want to have to learn what all the different CPUs are called that every MT board I use has onboard just so's I can know which of the several sets of packages residing on my HDD is the relevant one for the board I'm trying to upgrade at that moment.when you select a device in the download page, below it's picture - the NAME of the package appears (which actually is the CPU type).
you can tell which devices have the same package name by that method. as you see some have "mipsle", some "mipsbe" and some are "ppc". all devices with PPC can use the same package.
Thank you cmit. I was beginning to think I was the only one who couldn't see the elephant in the room.Normunds,
But there's a simple solution for that: Make folders on your hard disk name something like "RB100_500" and put the files for that architecture in there. Another folder "RB200_x86" for the x86 type files, ...
That's good to know. I did wonder if it was the case but as the only way to find out is to deliberately upload the wrong set of packages to a board and reboot it I thought it might be better to remain in ignorance.The router can't load packages from another routerboard version.
I didn't know this was possible. I've been messing around with ftp for over a year! It's one of the probably very many useful little tricks you can do with Winbox that MT decided not to tell anyone about in their customarily laconic manual entry. Just like the one about using the console as a text messenger they've elected to pull out of their secrets box in the latest newsletter.I open winbox into a CPE unit, open the file list and grab the 4 packages and dump them in the file list.
Well, it happened to me by accident because I also was confused by the serveral different type of packages. But usually I use new updates first on new to be configured unit on my table. So if something goes wrong I can just take another unit when needed. It's not a production unit yet.That's good to know. I did wonder if it was the case but as the only way to find out is to deliberately upload the wrong set of packages to a board and reboot it I thought it might be better to remain in ignorance.The router can't load packages from another routerboard version.
The Mikrotik documentation doesn't mention this.
I didn't know this was possible.I open winbox into a CPE unit, open the file list and grab the 4 packages and dump them in the file list.
Well, that´s how we learn. In my case the auto-update in ros3.x never worked anyway so I do it manually the way I prescibed. A bit of work but its more work to find out why the auto-update doesn't work.I've also been religiously download updates for the RB100 series from the Website, unzipping them, uploading them to a RB500 router by ftp, using auto-update to download them to my 112 and 133 CPEs and rebooting them, wiping the 'RB100' updates from the router, downloading the updates from the RB500 series from the website to a newly-created folder, unzipping them, uploading them to the RB500 by ftp and rebooting it to update it.
I didn't even know there was a ref 3 manual until I read this. I'm on the MT mailing list and receive the newsletter and in my innocence thought MT would actually announce the arrival of a manual for v3 - even as a work in progress - with a fanfare and a bit of crowing about their support for the shiny new products and how good it is, and even provide a link for it so's folk can see what it contains and why it's better than v2-9. Or at the very least might shyly mention it in passing.
the ref manual3.0 does not mention all options of the ros while earlier versions can be found that do. But it doesn't mean therefore these functions are not there any more in the ros3.x!
Well, yes. I suppose I am suggesting that.and what do you suggest, that we put all the router model names in the filename? and how will it work when we have lots more new products?
if the package is the same for like 10 products, what will it be like? routerboard-3.7-rb112-rb133-rb150-rb153-rb500.npk ?routerboard-3.7-RB500.npk
nothing, mipsle packages will work for all mipsle products. i think that's the thing that you don't get it yet. we have 4 package types. x86, mips-le, mips-be and ppc. whenever a new mips-le product will come out, mips-le packages will work with it. what you suggested is even more complicated - make a new package name for this product type. we'll end up with a whole bunch of packagesAs for when you have a lot more products, what are YOU going to do when you have mipsl processors in you RB1200 range and your RB800 range?
routerboard-3.7-rb1xx/5xx.npk ?if the package is the same for like 10 products, what will it be like? routerboard-3.7-rb112-rb133-rb150-rb153-rb500.npk ?
Yes, you're right about what I didn't get. How could I have got it when afaIk this is the first time Mikrotik have explained it?nothing, mipsle packages will work for all mipsle products. i think that's the thing that you don't get it yet. we have 4 package types. x86, mips-le, mips-be and ppc. whenever a new mips-le product will come out, mips-le packages will work with it. what you suggested is even more complicated - make a new package name for this product type. we'll end up with a whole bunch of packagesAs for when you have a lot more products, what are YOU going to do when you have mipsl processors in you RB1200 range and your RB800 range?
I think we've established that.the second post in this thread says that there are many boards which use the same packages.
Dunno. It was off the top of my head that the most recent download I did was 23MB, but on checking see that was Mikrotik-3.4.iso which came in at 24.5MB. I agree that all_packages-mipsle-3.7.zip is a mere 16.3MB. And even with the wonders of ADSL brought to me by wireless through Mikrotik routers, that still takes me a while, and costs me.Why are you downloading 23mb files?
I know that now. But the filename only says it's mipsle. *I* know now it's for the 5xx and the 1xx because I asked a silly question on this forum about RouterOS downloads.The combined package is only around 9mb. Also, why would you have to download the same file twice? If the filename says mipsle, it is for 5xx and 133, etc.... you don't have to download it twice... its the SAME FILE!
But wouldn't it be easier if Mikrotik did what you are I are both now suggesting? That is just have four download buttons and say, "this one is for 1xx, 5xx, crossroads", "this one is for 4xx", etc. Then I can download the mipsle file staight into my '1xx/5xx/crossroads' folder without having to KNOW or worry what processor it has.Do this.... Go through the list... Create the following folders:
1xx,5xx,crossroads -- put mipsle in this folder
4xx ---put mipsbe in this folder
2xx,x86 --- put x86 in this folder
3xx,6xx,1xxx ---put ppc in this folder.
There, now you have all the firmwares you'll need. When a new version comes out, just download ONE of each file and put in the respective folder... no need to download a seperate file for 3xx, 6xx, 1xxx..
Yes it may be a little confusing, but this system makes it pretty easy.
because back then, when 2.9 was released, we only had two routerboard models.won't ask why -ns- on the v2-9 packages is now -mpsle- as I don't want to know
if the names mean nothing to you, you won't need them1. what the mpls.npk package does. Is it essential?
2. what does the calea package do?
3. what does the multicast package do?
click on "content" next to the all-packages download link, and it will show you what's inside.4. does the 'combined packages' package RouterOS-mpsle include all the 'all_packages" packages except Dude and User-Manager? and/or hotspot? Unhappily the "includes optional packages: content" link doesn't work in my browser.
out of hundreds of thousands of people, you are the first5. does anyone else think that a newcomer faced with his first attempt to scale the obfustications of the Mikrotik download page might possibly conceive of the notion that you first have to download and install the new RouterOS package and then add selectable packages like ntp, ppp and wireless to it?
Likely, but then again if I knew what they were maybe I'd think, 'Hey, that's just what I need.'
if the names mean nothing to you, you won't need them
I did actually say that clicking on the "content" next to the all-packages download link doesn't work in my browser - Firefox 18.104.22.168.
click on "content" next to the all-packages download link, and it will show you what's inside.
Perhaps I'm just the first to ask about it, Normis. After all, I did say it was a silly question. But wouldn't it have been nicer to have just answered my silly questions rather than putting me down? After all, the title of this forum is "Beginner Basics".out of hundreds of thousands of people, you are the first
You're absolutely right, it does work. It only works if you click on the 'content' part of it and there's no underlining as there is on the other clickable links nor change of cursor style to indicate that it is a clickable link different from the rest of the line, but once again I've paid the price of not being 100% aux-fait with the way Mikrotik does things.well it does work in my firefox, and all the others around here ...
Are you really saying that 'hundreds of thousands of people' have successfully upgraded Miktotik Routerboards from v2.9 to v3?out of hundreds of thousands of people, you are the first
more or lessAre you really saying that 'hundreds of thousands of people' have successfully upgraded Miktotik Routerboards from v2.9 to v3?
I'd suggest that even if 'hundreds of thousands' of routers have been successfully upgraded this was done by a few professional, full-time network administrators - tho' I'd put my money on most of the hundreds of thousands of Mikrotik routers out there still running an upgraded version of the v2-9 they came with. After all if it's working why risk breaking it with an upgrade that doesn't add anything essential?.... probably more -
In this we agree totally, Normis. Problem is, I AM the system administrator.I wouldn't let anyone except an administrator touch your routers ... it's a security risk after all
Can't a gal be curious?1. what the mpls.npk package does. Is it essential?
2. what does the calea package do?
3. what does the multicast package do?-
if the names mean nothing to you, you won't need them
Yes it is. And wouldn't Googling 'multicast' be an informative exercise!Search is a great invention of the computer age.
Like... yeah man.Peace