Thanks, we will look into this problem
Fasttrack is working fine for me on a RB951G-2HnD in a simple home NAT setup. Maybe something else in your config is causing it.
Hi all,
I updated my RB951G-2HnD to 6.38 version and I have an issue with my laptop (ThinkPad T420s), it’s connects fine to my WLAN but it’s disconnected after 5min. aprox.
Watching the log I can see a lot of entries like this:
Jan/05/2017 16:20:40 xx:xx:xx:xx:xx:xx@wlan1: connected
Jan/05/2017 16:20:55 xx:xx:xx:xx:xx:xx@wlan1: reassociating
Jan/05/2017 16:20:55 xx:xx:xx:xx:xx:xx@wlan1: disconnected, ok
Jan/05/2017 16:20:55 xx:xx:xx:xx:xx:xx@wlan1: connected
Jan/05/2017 16:21:05 xx:xx:xx:xx:xx:xx@wlan1: reassociating
Jan/05/2017 16:21:05 xx:xx:xx:xx:xx:xx@wlan1: disconnected, ok
Jan/05/2017 16:21:05 xx:xx:xx:xx:xx:xx@wlan1: connected
…
I rebooted the router and the issue it’s not gone, finally I downgraded it to 6.37.3 and it’s working fine again.
(the laptop has been in the same place all the time).
Regards.
Changes with RSTP is a complete disaster!!! IMHO such changes are not the subject for release branch! RPVST was great approach with high level of flexibility. Now if we just update all our routers in L2 segment it won’t work at all (fortunately tested on the table) and I’m talking about network that comes across few cities not a few offices!
And tell me what should I do with this situation now?
Upgrade to future versions is not possible without almost complete redo of L2 logic of whole network. With RPVST it was also possible to assign different bridges as root for vlans that have same parent interface and yes you may need it in some situations. Now this doesn’t work.
Please, revert this changes back!!! Put it to some beta ROS version first, give it good tests with feedbacks and provide same functionality with minimum reconfiguration required. Otherwise it turns for us into hell, really. Especially if similar “surprises” will come in future releases in the branch that considered as production branch.
It’s been in an RC version for months. It’s now in the “current” release channel. If you need the old functionality, there’s the “bugfix only” channel.
Installed 6.38 to a 50+ device mix of MT routers/crs devices(~50%) and AP’s(~50%) from v6.37.1.
Had 3x devices die from a 6.37.1 ->6.38 upgrade ( 1xRBwAP2nD & 2xRB912UAG-2HPnD), had to net-install to fix.
***** Had ALL 5x RB2011UiAS 2x CRS125-24G-1S give a WARNING in the log about OVERCLOCKED RAM at boot.**
I am in process of rolling back all 50+ MT devices to 6.37.3..
On RB750Gr3, where I have two PPPoE links to ISP, if I disable the secondary one, I can´t reenable it (tried through winbox, winbox “new terminal” and ssh).
Log shows the initializing/connecting messages, but nothing else, and the interface won´t go up / get ip address. Log shows this entries just once every time I put the PPPoE client down/up.
Anyway, can´t reboot or put the main PPPoE client down now, but I will do ASAP and report back.
To all who have upgraded to 6.38 I just wanted to give some info on what I have found.
I have found that I needed to rediscover all of my devices for 6.38 as I lost all SNMP graphing/oids that were CPU, temperatures, and voltages. However it was quickly fixed with a full rediscovery of the device.
I just wanted to give everyone a heads up that have upgraded.
issue with my check for update
http://forum.mikrotik.com/t/check-for-update-returns-error-could-not-resolve-dns-name/104917/1
I got a nightmare after upgrade ccr1009 & crs125 to 6.38.
All vlan via switchip error.
They should be test carefully more before release this to stable version
I found several other bugs:
RB2011 with NTP-Package is losing the correct time while displaying “synchronized” after a while, it does not matter if I enter another routerboard or official NTP-Servers. (Standard System-SNTP not tested, as I need the NTP-Server portion)
IPsec xAuth with Mode Config (ROS as Client): sometimes after a SA-Rekey the devices are losing their IP-Adresses and are not getting them back until ich do a manual peer “kill connections” which is obviously not the way to go. Until is do this, they have no IP-Address on the Interface making the tunnel anymore and display an invalid policy while at the same time having another identical dynamic policy which is not working because of the missing IP-Address.
What’s the upgrade scenario for CAPsMAN controller and devices?
Currently CAP<->Controller communication is done on VLAN, so if I go and upgrade controller I will loose communication with CAPs. If I upgrade CAP it will no longer connect to controller.
Am I missing something?
strods from MikroTik Support wrote:
Tue Jan 03, 2017 11:23 am
Do not worry about these overclocked messages - they are still work on progress. If you have not overclocked device manually, then there is no need to worry about that.
We are still improving this feature.
Please read the topic above.
73/dx
On my 2011 it works OK. Primary NTP server on the LAN, secondary on the internet.
are you using the separate NTP Package or integrated SNTP-Client?
The NTP package of course, that is what you are talking about.
From my own local server I have also added the router as a reference and I see this:
remote refid st t when poll reach delay offset jitter
==============================================================================
x127.127.8.0 .DCFa. 0 l 73 64 356 0.000 -1.904 2049498
+127.127.28.0 .GPS. 0 l 8 16 377 0.000 13.589 0.187
*127.127.28.1 .PPS. 0 l 7 16 377 0.000 -0.002 0.002
192.168.1.1 192.168.1.3 2 u 34 64 377 0.213 -1.042 0.033
So it is synchronized.
thats odd that it is working in your environment
but it was already odd that the 2011 was the only device in the network with this problem.
a periodic “restart” of ntp (disable+delay+enable) solves the problem at the moment for about 5 minutes as the clock deviates again
devices that are using this ntp-server are still getting bad packets with “server-not-synchronized”
Hi all,
After upgrade to 6.38, I feel my routerbox temperature too high than before. As I often check before upgraded the temperature about 50-51 but now it is 60-62, anybody have same with me?
My box is: RB850Gx2, already downgrade cpu speed to 400MHz but not effective.
Today I found a severe bug with 6.38:
It will not (or at least incompletely) learn MAC-Addresses on a bridge connected to the master-port of a switch.
I did notice this bug too: because of not learning MAC-Addresses on the bridge all packets are being broadcasted! My VPN is getting all the ether-master packets.
In the bridge there is only one MAC learned from ether2, but there are a lot of MAC in ARP Table:

The good news are:
What’s new in 6.39rc7 (2017-Jan-05 12:24):
*) bridge - fixed MAC address learning from switch master-port;
Hi all,
After upgrade to 6.38, I feel my routerbox temperature too high than before. As I often check before upgraded the temperature about 50-51 but now it is 60-62, anybody have same with me?
My box is: RB850Gx2, already downgrade cpu speed to 400MHz but not effective.
From the changelog:
*) rb850Gx2 - fixed pcb temperature monitor if temperature was above 60C;