I think it can also help users like me who are a bit bottlenecked by PPPoE clients (since the load will be distributed, leaving more headroom for the PPPoE client).
Actually many of the chips used in MikroTik routers would be able to hardware-offload PPPoE but for some reason RouterOS still doesn’t support it. The consumer routers distributed by ISPs with their subscriptions, which use the same chips, often do. And perform a lot better.
I'm guessing I'm opening another topic 
The most I was able to push before CPU hit 100%
was 350
I could even reach 900-ish with wap ax, using internal iperf server.
Unfortunately that device has been send into the trenches, so i don't have it at hand anymore ( read: it was first tested in home lab, then put in production).
2 Likes
At least, please check and review this issue to see if further optimization is possible. If it can't be optimized further, document it, because my other router (different brand) runs VRF routing (BGP VPNv4) with 2 million routes in VRF without issues, NMS runs smoothly. Many people use SNMP for monitoring, I think. Oh, and my NMS doesn't monitor routing details specifically.
I don't see any problem with wAP ax throughput. I tested it in my office and I get full speed my ISP provides me. (1000/500 and realistic speeds are 931/485 and wAP ax gives me about 924/450)
well
looks like every version
LTS, RC, Beta have same SNMP problem
MIKROTIK-MIB::mtxrScriptRunOutput\[1\] = No Such Object available on this agent at this OID
Mikrotik ? could it be fixed ?
I standing with pe1chl’s opinions, polling routing table through SNMP is besides being outdated, it's also a torture, for the admin and router also. There are more modern and less painful solutions. We must move forward with the times, not cling to the past at all costs, in all cases, and hammering vendors with our nonsenses.
Running the script if you use OID works just fine. However, yes - if you use "mtxrScriptRunOutput" from MIB then it indeed does not work. We will fix this as soon as possible.
2 Likes
I don't have a specific need to monitor the routing table in detail using SNMP, and I've also tried disabling the SNMP routing monitoring function but it's not found. This kind of error doesn't appear on similar PE devices still running v6. Could you please share in this forum, what do you mean by "There are more modern and less painful solutions"?
Maybe when you were not monitoring the routing table, you should not include that info in your posting, and omit the info about what you were actually monitoring, because here on the forum we cannot read your mind.
Just a quick note, when I updated to 7.21_RC6 my Roberts radio does not connect any more.
So this is on a slave which happens to be a guest radio. If I enable wpa-psk sha2 it starts working
this is repeatable from the security setting menu. So my normal setting is this
add authentication-types=wpa2-psk disabled=no encryption=ccmp management-protection=allowed name=sec3 wps=disable
to get the radio up and running again I have to do this...
add authentication-types=wpa2-psk,wpa2-psk-sha2 disabled=no encryption=ccmp management-protection=allowed name=sec3 wps=disable
ie enable wpa2-psk-sha2
Edit: Yes I know it's more than likely my cruddy old Radio!
Any ETA for stable?
Ive just tried again using 7.21rc6 and i can now easily push 700mbps on 80mhz. In both directions!
Im actually kinda impressed
Thanks for making me try this again.
Now it’s time to retest my ax2’s as i also have some really terrible results with those. ^^
It’s under System → Resources; Winbox and Webfig it shows Hardware, CPU, IRQ, and RPS. On CLI I think it’s under IRQ.
Not quite 800 on my ax2
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams
[ 5] 0.00-10.00 sec 238 MBytes 200 Mbits/sec 0.000 ms 0/172655 (0%) sender
[ 5] 0.00-10.00 sec 237 MBytes 199 Mbits/sec 0.076 ms 703/172655 (0.41%) receiver
[ 7] 0.00-10.00 sec 238 MBytes 200 Mbits/sec 0.000 ms 0/172654 (0%) sender
[ 7] 0.00-10.00 sec 238 MBytes 199 Mbits/sec 0.068 ms 597/172654 (0.35%) receiver
[ 9] 0.00-10.00 sec 238 MBytes 200 Mbits/sec 0.000 ms 0/172655 (0%) sender
[ 9] 0.00-10.00 sec 237 MBytes 199 Mbits/sec 0.073 ms 1012/172655 (0.59%) receiver
[ 11] 0.00-10.00 sec 238 MBytes 200 Mbits/sec 0.000 ms 0/172655 (0%) sender
[ 11] 0.00-10.00 sec 237 MBytes 199 Mbits/sec 0.074 ms 845/172655 (0.49%) receiver
[SUM] 0.00-10.00 sec 954 MBytes 800 Mbits/sec 0.000 ms 0/690619 (0%) sender
[SUM] 0.00-10.00 sec 949 MBytes 796 Mbits/sec 0.073 ms 3157/690619 (0.46%) receiver
Version 7.21 has been released: