RTL8125 never works well if you consider CPU utilisationRTL8125 2.5GbE Controller works well with 7.15beta8
RTL8125 never works well if you consider CPU utilisationRTL8125 2.5GbE Controller works well with 7.15beta8
QualcommA question - what chips do they use?I don't think MikroTik uses any MediaTek wifi chips?
They can use whatever they want, as long as it gets the job done.FastPath isn't going to cut it in 2024.
They need to use DPDK/VPP for line-rate software dataplane. Maybe XDP for ingress filtering.
Not yet.....So there is now EVPN still?
You and me both !I actually welcome the removal of SMB from the default image. I always considered it quite useless ¯\_(ツ)_/¯
Care to share how much MPLS traffic you have at peak and is it in tile arch?, we have a pilot MPLS implementation base on v6 (mpls atom/pseudowire) in one of our PoP and just running < 500mb at peak
VRF HW forwarding support for CRS3xx/5xx and CCR2116/2216 incoming ?next to loopback interfaces tab, we have also vrf interfaces tab .. ?! what the heck ?
I don't want to get my hopes up. I've only been requesting VTI since 2009....hmm, since we already have Loopback interfaces, maybe "soon" we will also see VTI interfaces :p
Log a ticket with support@mikrotik.comVPLS seems to be broken on 7.13rc.
Interface goes up but router reboot after some minutes (rb4011) or some hours (2216).
With the same config no issue on 7.12...
I am pretty sure it's just a case of "Good things take time" rather than any decision not to support them.but MikroTik decided it was a terrible idea to support these three on the ASICs.
There is no hardware MPLS support in RouterOS v7 at this point.There is hardware offload support for label switching in RouterOS for now.
+1Is it possible MT can make /ip services works in multiple vrf like cisco.
because in v7 /ip service can only choose for 1 vrf only
thx
No, only the CCR2004-1G-12S+2XS
This is for alle CCR2004?
CCR2004-1G-12S+2XS
CCR2004-16G-2S+
Translation = F*** I'm Good, Just Ask Me !Don't you worry, I'll eventually just stop logging in or commenting—My knowledge and expertise are valued elsewhere and certainly Linux based networking, just not MikroTik specific.
I am one of those that is prepared to pay.Many people are willing to pay that cost, though, is the point. A MikroTik box won't cost me $400k.Some of these would come for free as they can be done in software on the existing hardware, but others such as a larger TCAM come at a cost.
What MPLS Hardware functionality was in RouterOS v6 that is not in v7 ?
It would be desirable if mikrotik first restored the same range of functions as in ros 6 and only then implemented new features. I'm mainly waiting for MPLS in HW at least at the same level as in ROS6.
Yet...In MikroTik, neither are offloaded to ASIC.
So sadMPLS FastPath feature Is enabled by default, but only works for switched traffic.
I like the sound of this....We do not have "PER MODEL" packages. Only then we could do this. But change like that would require something like RouterOS v8, where all NPK package system is different, and we can make RouterOS-v8-hAP-ac.npk
I still dont understand the request for some hybrid netwatch + bfd combo.Nice to see you are happy. I would have been happy when they had added a "bfd" type. (I don't see much use for DoS'ing a website from a router...)
They can, and they have indicated that they are doing this currently.I get that but they should be able to rebuild CapsMAN with new libraries that will support this correct?
Completely off-topic, but both features are needed and long overdue.I'd rather like to see IPSEC VTI in ROS. Shouldn't be too much of an issue since it is possible with the Kernel currently used in ROS 7...
I'm showing my age, but the current Capsman is V2That would likely be part of a new CAPsMAN2 that manages them.
What FW provider was this ?Got a reply from a tier1 firewall provider pretty much telling me don't bother order physical hardware this year.
From their smallest smb branch box to their mega iron $100k box no orders will be shipped this year.
Very exciting !We do have plans for true multi platform Winbox. Finally. Let this be a teaser for 2022 No ETA and no promises though.
CCR2116 supports L3 Hardware Offloading. In some cases, it can route packets at close to 10Gbps speed while keeping the CPU idle.
Mikrotik's own proprietary routing engine that they developed in-house.Does anyone know what BGP-Daemon is under the hood?
They are prioritizing it. It's just behind other things like fixing the usability bugs in RouterOS v7.1 and delivering MPLS as well as IPv6 FastPath modules, and for good reason!It is unfortunate that Mikrotik does not prioritize MPLS hardware offload!
In my testing with CRS317 and CRS326 it is stable, just make sure you run RouterOS 7.1 or newer.Is MLAG stable in version 7.1 for use in data centers?
2 x Switch CRS326-24S+2Q+RM configured with one bridge, multiple ports with different PVID and with several ports configured as tagged?
Meanwhile, a brand new MikroTik CCR2116-12G-4S+ supports L3HW in both full routing and FW mode.
Yep, it is a shame, but at the same time understandable.Quite a lot of devices will lack new stack
*) chr - fixed FastPath support for VMXNET3 drivers;
Yes, it is very detailedNice changelog!
Mikrotik support are able to repeat the issue, and have reported that it will be fixed in a coming release.thanks! If it is "just" that I may to try it to replace the active-backup pattern I am using on servers with 2 CRS317. Hopefully it will be fixed soon...
I thought the days of "fixed some stuff" were long behind Mikrotik*) other fixes and improvements;
I would personally hope that Mikrotik implement EVPN+VXLAN as well as EVPN+MPLS as per the RFCHow about EVPN with vxlan? is that going to be added soon too?Since we now have IPv6 VRF support, I do not see the reason why not.
It sure can, but please remember this will only work reliably when it is Mikrotik <---> Mikrotik or Mikrotik <---> Linux with both ends configured for balance-rrMPLS traffic can be load balanced across the members of a bonding interface if you use balance-rr instead of 802.3ad.
First it's kernel and not kernalKERNAL panic after 3 days on rc2. ccr2004. no i won't log a ticket
Speculation is that yes it will come.Do anyone knows if the RB5009 will be getting support for L3hw?
Hi Raimonds,"?" has been replaced by F1
CN9131 or CN9132 is much more likelyWill there be a Marvell Armada 8040 Mikrotik?
My RouterOS v7 test lab consists of 3x RB3011.Rb3011 uias-rm
after 23h, it is frozen
The top3 model number look like bullocks to me. The bottom two look like they could be legit"Extreme Performances" ARM64 Series:
CCR-eOW-12x100G-36x25Gw
CCR-eOW-1x25Gw-2x10G
CCR-eOW-1Gw-1G
ARM64:
ccr2116-12g-4s+ (al64v3)
crs520-4xs-16xq (4x 25gbit + 16x 100gbit)
i'm not the one to stop progress, but can we have a settable option in /console ? like so:As noted by the terminal when You open it up:
Code: Select all/console set help-key=\?
With announcement of RB5009 I hoped better hardware with WIFI will soon follow... but apparently not.
The new ccr2004 is not based on that same chips?
Well it turns out the Armada 7040 based product is the RB5009.I also found traces of Marvell Armada 7040 and Qualcomm IPQ5018 as well as 6018 chipset support, which do not align with any current products
I think @nz_monkey is not MT staffer.
Why do they need to be ?That would break the concept of all ports being processed by a single switch chip.
They can easily add an additional SFP+ with the Marvell 88F8125.I agree that two SFP slots would be more useful for some scenarios, instead of the 2.5GbE.
But if there was a RB5018UG+S+RM ... I'd be in the line for one already ;-)
Bravo!Let's clarify rumors.
Definately not.Apparently I'm being a dumbass again -does ROS 6.47.10 actually support evpn/vxlan....?
:Ocan't wait to see this bad boy: crs520-4xs-16xq
Have you tried RouterOS v7 ? It has newer drivers with multi-queue support.chr with proxmox is a disaster, I've been attempting for a year now lol.
Few things to try;
PCI Passthrough
Try ovs instead of linux bridges
Try vmxnet3 instead of virtio
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.