What’s new in 4.7:
*) fixed problem - wireless packet bridging with nstreme enabled
sometimes was very slow on RB1xx, RB5xx and RB4xx;
*) fixed problem - ipv6 traffic was not bridged if ipv6 package was not enabled;
*) ‘/user active’ now lists type of api connections as ‘api’
*) fixed getting interface stats in dude
*) fixed metarouter stability problem on RB400s & RB750s;
*) fixed metarouter - it didn’t work on RB1000 with 2Gb;
*) fixed metarouter - it locked up on RB800;
*) fixed problem - SFQ queues did not work on interfaces (wireless) if none
of simple or tree queues were added;
*) fixed RB800 temperature;
*) silentboot feature updated;
*) multicast - fixed possible crash during PIM startup;
*) ospf - changed “/routing ospf route” to show type 2 metric instead of
internal metric for type 2 external routes;
*) report platform name in “/sysrem resource”;
*) fixed problem - vlans were not working on RB750 ether1;
*) fixed mac address handling on RB750, some specific arp requests did not work;
*) more than two dns servers allowed in /ip dns;
*) sniffer and torch could process packet from other interfaces;
*) dns cache rotates order of records in reply messages;
*) ospf - fixed DR and BDR election;
Nice
Has the Router Advertisement bug in the IPv6 package been addressed? I’d love to use routerboards in an IPv6 deployment but I can’t until that works reliably.
Any news about
Router crashes when MNDP enabled on EOIP
and
KVM tap interface Packets always drops
?
They were confirmed bugs .
I too have this problem, however I was unaware the it was a confirmed bug. We need a better way of sharing confirmed bugs with other RouterOS users.
Problem to upgrade to 4.7 version.
I put file-4.7.npk whit winbox or ftp in the routerboard and reboot, but routerboard not upgrade .
I see that in the files list the icon of npk file is not as package, but as a text file … uhmm… there is a bug?
tnku
warning RB433, RB433AH sometimes freezes after software restart need power off/on.
I install only routerboard, system, seciurity, wireless packages.
In change log:
“dns cache rotates order of records in reply messages”
What does this mean?
*) fixed problem - SFQ queues did not work on interfaces (wireless) if none
of simple or tree queues were added;
![]()
*) fixed problem - wireless packet bridging with nstreme enabled
sometimes was very slow on RB1xx, RB5xx and RB4xx;
Anyone has tested this??? ![]()
BR
Upgraded to 4.7 today. Still the same problem with nstreme for me. As soon as i turn it on client connects then after i start any data transfer it immediatelly disconnects saying: “Extensive data loss”. When i turn nstreme off it works perfectly and when i use bandwidth test it says my connection has 43mbit/s tcp/ip full duplex throughput.
Round-Robin =) if cached request has multiple A records, they are rotated for each response
p.s. what is ‘silentboot’?..
no bip bip on booting ![]()
![]()
how do I manage it? ))
that no “bip bip” could be removed for quite some time now.
here is the wiki description of what is Silent boot on RouterBOARD
http://wiki.mikrotik.com/wiki/Silent_boot
in short - you can turn off any output that RouterBOARD made when it booted up, no bios output, no booting messages no sounds, of course, if configured.
*) fixed problem - SFQ queues did not work on interfaces (wireless
How did you allow this bug to happen?
What do I tell all the people that upgraded to 4.6?
What do I tell all their customers?
I will tell them “well these guys from Latvia sqrewed the Wireless packet queues up and so the service was worse, but now it’s OK its fixed now”
And what do I tell all the people that tell me to use an older version because it is a “known stable” ? I don’t want to use old versions. They are missing stuff.
Life is cruel.
this bug was present in all v4 versions, it’s now identified and fixed, and should solve many wireless issues.
FYI: the package http://download.mikrotik.com/routeros-mipsbe-4.7.npk is corrupted, however a copy from Sweden http://www.mikrotik.se/download/routeros-mipsbe-4.7.npk is all good.
What I posted above is the SHA/MD5 checksums from inside the download.mikrotik.com server, and as you can see, the files are completely normal.
$ md5 rou*
MD5 (routeros-mipsbe-4.7.npk-SE) = deee0b3e510e64d243be4804eea18122
MD5 (routeros-mipsbe-4.7.npk-US) = 3ca3a781721afe853c91e014da353ae9
This is taken from the serverside (download.mikrotik.com)
[***@download.mikrotik.com html]$ sha1sum -b routeros-powerpc-4.7.npk
cd3eeb14db2ef5d2f101fd7e851cd7ab6d9e3bee *routeros-powerpc-4.7.npk[***@download.mikrotik.com html]$ md5sum routeros-powerpc-4.7.npk
35607f4c9622b1d5aba494d73e8aeca5 routeros-powerpc-4.7.npk
So your download is broken, or you have a broken package in one of your proxy servers