???As you are using OpenWRT code as a basis
RouterOS is special linux based operating system, and definietly not OpenWRT. It uses own linux kernel (with external kernel modules) and BusyBox compilation. Rest of applications is written or modified (including GPL licensed applications, ie. kvm or racoon) by MikroTik.Can you clarify this ? Is router OS only Linux based, is it OpenWRT based, or is it fully proprietary ?
There are many things we are working on, they all have high priorityMikrotik should be able to implement missing IPv6 and Ethernet bridging functions (PBB)
What's new in 3.10: *) added Multilink PPP to PPPoE client - just specify multiple interfaces to enable it;I've found strange as well that PPP multilink is still not implemented.
Wouldn't it be nice if MikroTik could comply with the requirements of GPLv2 license? This one in particular:RouterOS is special linux based operating system, and definietly not OpenWRT. It uses own linux kernel (with external kernel modules) and BusyBox compilation. Rest of applications is written or modified (including GPL licensed applications, ie. kvm or racoon) by MikroTik.
There is no mention about GPL parts of the firmware in the RB-450G documentation whatsoever, and also no information about where and how to obtain the source code. And I don't mean the external kernel modules here, I just want to be able to tweak the rest of the kernel (which is GPLv2 licensed code for your information) and use it with the binary drivers from MikroTik.3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
I'm sorry, I haven't actually used it yet. I did not buy this hardware for using RouterOS on it. Will try to check this information and return back later. Thanks for your reply and clarification, that's what support forums exist for, and I'm glad that I joined here Nevertheless I still think that your pdf documentation could be improved a lot.if you had actually used RouterOS before posting this nonsense
You can look for the PDF links here: http://www.routerboard.com/index.php?showProduct=52we don't have PDF documentation.
To get a CD with the corresponding source code for the GPL-covered
programs in this distribution, wire transfer $45 to MikroTikls SIA,
Pernavas 46, Riga, LV-1009, Latvia. Please contact MikroTikls SIA for
our current account information and wire transfer instructions. Offer
valid for three years from the date of distribution of this software.
This CD will only include the source code of the following programs
and any non-proprietary programs distributed according to license
requirements. This CD will not include MikroTikls proprietary SOFTWARE.
what's the problem with those documents?You can look for the PDF links here: http://www.routerboard.com/index.php?showProduct=52
You should study more about GPL. This is a valid method. If you want the kernel changes for making your own openwrt, you can simply email support and ask for the kernel patch, instead of complaining on the community forum, where nobody can help you.Hmm, is it a bad joke?
Bizzarely, some of us could help ....complaining on the community forum, where nobody can help you.
The Drivers aren't too hard to do.In the end I just want to have a kernel which can load the needed proprietary drivers from NAND and boot linux rootfs from microsd card.
Yes, it is.Is it too much ?
The GPL permits charging a reasonable amount for the physical distribution. Likewise, if you distribute binaries as Mikrotik does, it must be accompanied by an offer valied for three years to obtain machine-readable source code for a charge "no more than your cost of physically performing source distribution..." -- And MikroTik does exactly this.Hmm, is it a bad joke? MikroTik guys seem to be playing retards who are stuck in the last century without any means of having better and less expensive distribution channels. Is this price even somehow justified? I just can't believe that buying a blank CD, spending a few minutes for writing it, and shipping could cost anywhere like $45.
You may charge a fee for the physical act of transferring a copy...
The $45 in question is not unreasonable. The cost to Mikrotik in employee time to process a source code request, make a machine-readable copy, and the cost to then send the copy quite easily fits the fee they charge.3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
...
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; ...
You are absolutely wrong, most people just want to hack projects. Only a minority try to sell opensource firmware. You can take other known firmware sources as examples. It happens, I can't deny it, but it's definitely not the common usage of firmware source.In the end, the Toolchain is only really useful to people who want to build their own firmware(s) to either use for direct Profit, or to sell for indirect Profit.
Thanks for digging up the zombie thread from 2010, but the RB450 can run OpenWRT as I read in their community forum http://wiki.openwrt.org/toh/start#mikrotikYou are absolutely wrong, most people just want to hack projects. Only a minority try to sell opensource firmware. You can take other known firmware sources as examples. It happens, I can't deny it, but it's definitely not the common usage of firmware source.In the end, the Toolchain is only really useful to people who want to build their own firmware(s) to either use for direct Profit, or to sell for indirect Profit.
And most importantly, It really only will be of benefit to the sale of routers.
if the rb450G could boot openwrt, I would buy two more this moment. Actually I would also purchase a router board model with wireless.
We FLOSS people don't do things just for features, or raw ability. Its the openness and the flexibility, which appeals most.
truthfully this is a pretty large market, with nobody catering to it. The FLOSS people want a DIY ARM base router, that can boot a generic distribution. They also tend to be the people less likely to use support resources. As long as things are open, the community almost does the rest. Basically being opensource friendly always means, "we provided the tool chain + any documents openly, we don't 'officially' support anything that comes from this."
there does exist other router options, but they are all x86. They are not real DIY embedded routers. x86 also uses a ton of power, even ATOM.