Which feature are you waiting for in v7?
Sometimes requests for new features are turned down because they would require a new kernel, and v7 would include the new kernel.Some of the requested features haven't been made, so there is no difference if you are waiting for them in v6, v7 or whatever version.
Let's just say you are waiting for a specific feature, not a version. The v7 doesn't automagically come with all the missing features.
Some of the requested features haven't been made, so there is no difference if you are waiting for them in v6, v7 or whatever version.
Let's just say you are waiting for a specific feature, not a version. The v7 doesn't automagically come with all the missing features.
I agree!BGP4-MIB support on SNMP would be great too...
Mikrotik trying to support all the 3rd Party LTE modules will be a never ending game of cat and mouse.One of the main things for me - and I'm sure I'm not the only one - is the total lack of support for the newer Sierra Wireless MC74xx models. I've got emails dating back 3 years from MikroTik telling me "v7 will support it".
+1, BUT: the routing engine is the most important part on a router.Normis is right. A huge number of the "v7" features have been added to RouterOS v6. Mikrotik have done an outstanding job of backporting features.
The missing features and unresolved bugs are mostly related to the "new routing" engine that has been long promised, or rely on a newer Linux Kernel.
And that IPv6 is so unimportant that it does not even need kid-control!Unfortunately, it seems mikrotik thinks kid-control is more important than routing.
It's a bit of everything, but nothing right.Is it Wireless/WISP?
Is it Datacenter/Enterprise?
Is it SOHO/SMB?
MikroTik making their own LTE cards will have the same issue supporting all countries and bands. SW already do a great job of this - why not just support ONE of the major brands (SW)?Mikrotik trying to support all the 3rd Party LTE modules will be a never ending game of cat and mouse.One of the main things for me - and I'm sure I'm not the only one - is the total lack of support for the newer Sierra Wireless MC74xx models. I've got emails dating back 3 years from MikroTik telling me "v7 will support it".
I think Mikrotik should focus on building up their own portfolio of LTE products, this way customers will be able to buy a product they know will work reliably and be supported by Mikrotik. It also means that Mikrotik can add features like LTE Pass-Through, and update the LTE module's firmware from within RouterOS. It will result in a much better user experience for all of us.
Is it about parent=global or Simple Queues?how about a 2500$ cloud core than can queue more than the $350 version? HTB is limited to single CPU / interface and that just kills it for us.
That is just an entirely different market. When you require that, you know where to go and what you are going to spend.v7 should come with dedicated packet forwarding chips and ASIC/FPGA hardware for offloading the services such as Queues,firewall etc in the new products.
For ex, most basic Cisco ASR hardware handles 24 000 PPPoE Sessions in a single box compared to a CCR1036 which is aprx 2000 sessions.
There are limits which can be done in software and I think RouterOS pretty much done it all. It is time to focus on dedicared hardware.
Apparently yes.hasn't support for TILE been dropped in recent Linux Kernel versions?
Isolated VRF'sSteve is right. There is barely anything left in v7 that we haven't backported.
So now that tile is removed from the linux kernel, where does that leave the CCR.RouterOS does not use any TILE code from the Linux kernel. This news has no effect on RouterOS.
Read the above: at the same place where it always has been.So now that tile is removed from the linux kernel, where does that leave the CCR.RouterOS does not use any TILE code from the Linux kernel. This news has no effect on RouterOS.
Please enable openvpn udp support and also ability to manually enter ip for ovpn tunnel in pop profile that can be used for bgp next hop resolution.These two bugs are stopping me from using mikrotik for my DN42 network.Steve is right. There is barely anything left in v7 that we haven't backported.
Please enable openvpn udp support and also ability to manually enter ip for ovpn tunnel in pop profile that can be used for bgp next hop resolution.These two bugs are stopping me from using mikrotik for my DN42 network.Steve is right. There is barely anything left in v7 that we haven't backported.
viewtopic.php?p=617477#p617477@normis When are we getting UDP for OpenVPN? It was promised for v7: viewtopic.php?f=1&t=77898&start=150#p527829
Hi NormisSteve is right. There is barely anything left in v7 that we haven't backported.
Please could you explain how is this possible? It's hard to undertand your comment, Linux kernel works around system architecture, x86, arm, riscv, https://github.com/torvalds/linux/tree/master/arch. If the RouterBoard is Tile, how the kernel works without using any TILE code?RouterOS does not use any TILE code from the Linux kernel. This news has no effect on RouterOS.