*) updated drivers and kernel (to linux-2.6.38.2);
*) improved interface management (scales well for up to thousands of interfaces and more);
*) improved queue management (/queue simple and /queue tree) - easily handles tens
of thousands of queues;
*) improved overall router performance when simple queues are used -
at least double the performance of v5, even bigger improvements on multicore systems;
*) very small overhead for packets that miss simple queues,
but simple queues are present in the system;
*) pcq queue is NAT aware (just like “/queue simple” and “/ip traffic-flow”;
*) in “/ip firewall mangle” can specify “new-priority=from-dscp-high-3-bits”;
*) new default queue types: pcq-download-default and pcq-upload-default;
*) simple queues have separate priority setting for download/upload/total;
*) slave flag shows up for interfaces that are in bridge,bonding or switch group;
*) global-in, global-out, global-total parent in /queue tree is
replaced with global that is equivalent to global-total in v5;
*) simple queues happen in different place - at the very end of
postrouting and local-in chains;
*) simple queues target-addresses and interface parameters are joined into one
target parameter, now supports multiple interfaces match for one queue;
*) simple queues dst-address parameter is changed to dst and now supports
destination interface matching;
*) dns cache logs requests to topics “dns” and “packet”;
v6.0beta1 includes many changes, we suggest it for testing environment until you are confident that it works with necessary configuration.
Please, submit all reports to support@mikrotik.com (include suppout.rif file).
you have to choose - ether you allow traffic to bypass CPU completely (by switching it to other port) or you wanna work with packets in CPU - there is no middle way.
One-way throughput is at half of v5 router with nstreme enabled and 5GHz-40 MHz mode, and station in 5GHz-Turbo with nstreme cannot connect to bridge. Changing sides solves problem. Significally less cpu usage (about 60% difference)…
paoloaga, you are right, thank you very much for the report! Connection-state matcher in IPv6 firewall is the reason for reboot, other IPv6 firewall rules work fine.
We will fix the particular problem in the next 6.0 version.
[admin@MikroTik] /ip route vrf> /ipv6 route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable
# DST-ADDRESS GATEWAY DISTANCE
0 ADC 2001:db8:ffff:ffff::/64 ether5-slave-local 0
[admin@MikroTik] /ip route vrf> print
Flags: X - disabled, I - inactive
0 routing-mark=test-vrf interfaces=ether5-slave-local
[admin@MikroTik] /ip route vrf> set numbers=0 disabled=no
Now it’s gone
[admin@MikroTik] /ip route vrf> /ipv6 route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, o - ospf, b - bgp, U - unreachable
# DST-ADDRESS GATEWAY DISTANCE
