I am fairly certain that they do NOT use dpdk. If they did, one of your CPU cores would be pegged at 100%I think the Mikrotik fast past is based on dpdk......
I am fairly certain that they do NOT use dpdk. If they did, one of your CPU cores would be pegged at 100%I think the Mikrotik fast past is based on dpdk......
That is my theory too !v6.49beta is out and it fixes 9 issues introduced in v6.48. Haven't tested it properly yet, but it can't be worse than 6.48.... right?
Yes, I believe this fix is for the RB4011 / RB1100AHx4 issues*) arm - improved system stability;
Can you elaborate please? Does this fix the 4011 & 1100AHx4 management lockouts?
All I know is that an EAP245 from TPLINK easily outperforms a capac.
Antenna Type Internal Omni
2.4GHz: 3 × 4dBi
5GHz: 3 × 4dBi
Everyone loves a hard banana ;)Or worse a monkey with a hard banana ;-PP
Thank you for the confirmation Maris.Yes, in ROSv7.
Cool, how much do you want to pay ?Operating at these speeds requires some serious engineering, fully redundant "non stop" fabric, separate control & data-planes (and preferably redundant offcourse)
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
Sad but trueFrankly since 802.11n, but I am curious what exactly they fixed.
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;
Yes we are aware of route selection problems in VRFs, unfortunately you will have to wait for ROS v7 updates.
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)
Hello,
PowerBoxPro metal grounding screw is only connected to SPF and DC negative! It is not connected to metal grounding of LAN ports! Design error?
I certainly hope that is the case, but all the evidence above points to CCR2000 series being an Annapurna Labs based architecture.
The 98DX8208 in the CRS309Do you know for which devices?Marvell have already made custom Prestera DX ASIC's for Mikrotik...
Marvell have already made custom Prestera DX ASIC's for Mikrotik...I only saw the Prestera port extenders matching these speeds.
Either the change log is wrong or the people who wrote it don't know how to properly write what they mean in English.
Great news!!!!We are researching ways how to implement MC-LAG
This x1000IPv6 + routing engine =![]()
* celebrates *Support for more Intel cards should be added in the next v7.0beta build.
Recursive nexthops in v7 works without any scripts.
MU-MIMOwhich features are missing now?
I really hope so!Could the new LtAP be used as GPS-based stratum-1 NTP server?
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.
NV2 and Nstreme are broken on ARM based productsWhat's wrong with ARM? It looks fine on hAP ac2I only need ARM fixed versión![]()
I gave up betting on RouterOS v7 release dates many years ago after incurring significant lossesMe too. I bet Europe MUM![]()
The same as anything to do with routing in RouterOS v6, "Fixed in v7".... Since 2013Hi
Old post, but what was the final outcome of this?
Brad
hahahaha
Which other routers are stackable ?Hi!
I think you first need to learn how to make stackable hardware.
WBR,
Fyodor.
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.
See: https://darbs.mikrotik.com/darbs/
Thanks guys.New beta versions has alignment mode included (it will update information much faster)
to use run from CLI:
/interface w60g align wlan60-1
They will be even more popular with POE out on ether5Most definitely not. But they are very popular devices.
find . -type d \( -name "tile" -o -name "ppc" \) -exec rm -rf {} \;
True, they are missing arm64 folder.Who said any of these pictures are showing the latest folders![]()
Only 4 ?Just waiting for about 4 years ...
+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;
We do not have plans to implement ISIS at least not in near future.
rc45 contains Nv2+ARM fix. It will be released within the next 24 hours.
60Ghz progress is amazing.Nv2 improvments and 60GHZ gears says that there is a new hope![]()
These are my top requests alsoAlso add to firewall address-list from routing filter and isolated VRFs![]()
Thank you MarisTo keep you guys busy with speculations![]()
+1All those photos of you in Hawaii and not one of them showing you in a swimsuit at the beach. For shame
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 am hopeful, But only time will tell.and there will be one made by MT ?
Please see viewtopic.php?f=3&t=129649#p638204Just missing BGP routing in multicore cpu....need this please !!!!
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?
*) wireless - new driver with initial support for 160 and 80+80 MHz channel width;
Hopefully we willWill we see DSL modems soon?
Having no HW support makes it pointless...AFAIK. . yes but via software w/o hardware assistance
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.