"In the near future, the network will be upgraded to a 100 Gbps data transfer rate, using MikroTik devices that will be released soon."
😲 😲 😲
Yes, it does..
On another topic, does anyone know if v7.1 has a working i40e driver? I was thinking of buying an Intel card for use with SR-IOV.
I too want to know this. At first glance the new implementation seems like a step backwards from v6.
Also how do you do passive interface as the default? It used to be possible to add interface=all and set passive=yes. Does that still work to make passive the default?
Thank you MarisSome basic stuff to start with ROSv7 routing config:
https://help.mikrotik.com/docs/display/ ... g+Examples
/routing bgp template add address-families=ip as=65533 instance=default multihop=yes name=as65533-ipv4 routing-table=main /routing bgp connection add connect=yes listen=yes local.role=ebgp remote.address=10.69.1.254 .as=65001 template=as65533-ipv4
It is maturing like a fine wine.Are we close to Beta6? Seems like a longer than usual run between Beta releases.THere are several problems with routing marks in beta5. Wait until beta6 is released.
*) improved large table loading speed in RouterOS v7;
I cannot agree more !smb on a security device is just crazy. It should be entirely removed from RouterOS. That's what nas devices are made for, firewalled behind the router.
I think that this will require a new SoC that outputs less heat. The hAP AC and cAP AC run really hot, adding more PoE circuitry will just make it worse.And at least one pass-through poe-out port please.
- HAP AC2 with 802.3af poe-input support (as cap ac does)
I certainly hope that is the case, but all the evidence above points to CCR2000 series being an Annapurna Labs based architecture.Anyone think this is related?
https://www.servethehome.com/new-marvel ... x-5g-socs/
Either the change log is wrong or the people who wrote it don't know how to properly write what they mean in English.
I 100% agreeThe big issue I see for some of those switches by the time they are released QSFP might be a dead standard more or less.
Starting to get hard to find modules , as everybody and their mother has now focused on getting into the QSFP28 and SFP28 space.
This is my expectation as well.I think there's a high risk that some architectures/platforms will be stuck on ROS v6 for flash-size and toolchain reasons. v7 will probably be ARM and x86_64 only, and will probably lack some features thats simply not portable (I guess MPLS- and tunnel stuff).
Most high performance packet forwarding is done in user space!
One of the selling points is performance. Especially on embedded devices userspace is not okay.
It's only one month until the EU MUM. Maybe they will announce some 802.11ax gear.You can buy 802.11ax routers on the shelf in retail stores already, yet zero communication from Mikrotik about their timeline... this is rather worrying.
I gave up betting on RouterOS v7 release dates many years ago after incurring significant lossesMe too. I bet Europe MUM
Which other routers are stackable ?Hi!
I think you first need to learn how to make stackable hardware.
Mikrotik have had that same ad up for the last 10 years...Maybe. And maybe there are few programmers...Maybe the devs are on holiday.
+1I think Mikrotik should just make a version with the 98DX3336 and 128MB storage and call it a router if they want.
*) rb3011 - implemented multiple engine IPsec hardware acceleration support;
rc45 contains Nv2+ARM fix. It will be released within the next 24 hours.
RouterOS is still missing LLDP-MED which allows the router/switch to signal to VoIP phones which vlan they need to use. This is one of the main reasons for using LLDP, and is a standard feature on switches.Please clarify "not doing anything"? LLDP initial support was added in 2016-Sep-30
60Ghz progress is amazing.Nv2 improvments and 60GHZ gears says that there is a new hope
That is not the problem.I am still not sure why Mikrotik didn't go with IP Infusion....
It is just that with Mikrotik's increasing popularity, hackers are now targeting RouterOS. Exploits exist on all equipment, just look at Cisco and Fortinet if you want an example...The security issues are happening too frequent on MikroTik recently...
I agree Mikrotik should move as much as possible to ARM.I think the real answer has to be yes.
If I were Mikrotik, I would move to ARM by now.
And thats what they will do.
I agree this will be a great seller.This product seems more balanced than hAP ac. So i think it will be a new bestseller from mikrotik.
5 years and counting for meI think the same. For the last few years
- ROS7 will be ready in a year I think.
Mikrotik announced the new products at the Philippines MUM, so Meconet are not doing anything wrong.Damn that german shop should be banned for that one
I don't disagree.They better start with ROS7 in this year, ARM Products only badly supported, and Wave 2 Chipsets are buggy with ROS6
Can you give me an example of a package that is not multicore capable ?most Packages are not multicore capable
At a guess, its based on xt_tls which can support wildcards, see https://github.com/Lochnair/xt_tlsSweet. No more Layer 7 for HTTPS blocking*) firewall - added "tls-host" firewall matcher (CLI only);
How it works? Which packet matches? Does it support wildcards?
Wave2 you say... You mean like this:
stop right there. this stuff above literally translates to wave2, right?
v7 is a mythIt probably would require the new routing engine in v7, so whenever that happens is the earliest we can expect FlowSpec.
I still want it ASAP, though.
Hi Uldis, it is Layer3 with CAPsMAN forwarding.How are you connecting the CAP to the CAPsMAN? Are you using Local-forwarding or CAPsMAN forwarding? Are you using VLAN in our setup?
Great write up, thank you doneware !here you can find photos and a small post on the CRS326 and the marvell SOCs used in it.
https://tikguy.wordpress.com/2017/08/17 ... -24g-2srm/