v6.38 [current] is released!

I experienced no problems when upgrading my RB750Gr3 from version 6.37.3 to version 6.38

Updating to 6.38 fastrack is broken, maximum download and upload speed is 150 Mbits, after downgraded to 6.37.3 all ok, speed about 800-850 Mbits

Thanks very much for letting me know.

i get in logs a critical system error “memory overclocked”

Mikrotik has confirmed to ignore it if you haven’t manually overlocked it. Its a feature they are improving on.

What device you are testing the fasttrack?
Please report to support@mikotik.com with a support output file attached.

For now everything runs smoothly and as expected. I still dont use it for wifi p2p or p2mp links, because of wifi “problems”, on other devices as I said - works great

Had no problems upgrading my RB750Gr3 to 6.38, only difference from the described, is that I upgraded from 6.38rc52.

Awesome, thank you for the confirmation and as soon as I get home, I will update mine.

Thanks again everyone who’s put my mind at ease.

Thanks for the explanation. Currently we use straight up RSTP, but I can see a day coming when we could benefit from using MSTP. Any plans to add that option?

It is fixed, I have no problems using 33character passwords and longer. Contact support with supout file if you still cannot use longer passwords.

model: RouterBOARD 962UiGS-5HacT2HnT
support output file contains pre-shared key in clear text format I will not send it
v 6.7.3


CPU load 85-90%
and after update
v 6.8


and CPU load 100%

vitaliyy, please provide the export file to support@mikrotik.com from both versions (you can replace the pre-shared keys in those files).
At least on my spare hAP AC router I got 500/700Mbps (download/upload), I hit ISP bandwidth limit.

Hi Guys,

I have just received another RB750Gr3 in the post today and I decided to update the firmware and rOS as the first things I do before configuring it. After doing the upgrade(s) I started to adjust the packages which are installed by default as there are a few which isn’t so useful to me like wireless and hotspot as it doesn’t have wireless in this model.

I then just found that there is a very small graphical bug with the icon that is used for disabled packages.

I am enclosing a screenshot below which shows the disabled missing graphic.

https://www.dropbox.com/s/8xhlamew8y1yia4/Screenshot%202017-01-04%2017.19.50.png?dl=0

If you look at my existing router (same one but previous rOS version, you will see its much neater graphic.

https://www.dropbox.com/s/u107oxfziubmdf4/Screenshot%202017-01-04%2017.43.34.png?dl=0

Im sure its just an oversight that the main image seems to have a bad graphic.

HTH

I upgrade my hap lite to 6.38 and upgrade firmware to 3.36 whats chanelog in new firmware version 3.36 for hap lite?

Sent from my C6833 using Tapatalk

Every update new problems
When was 5.x no problems with updates
6.1x was last stable, future realese fix on fix
I have also hex r3 with vlan bridge and problems
5ghz sxt ap lvl4 update to 6,38 and die
Maybe config conflict?
But he is in bridge and no other config
Bad bad and bad


Sent from my iPhone using Tapatalk Pro

After updating RB2011 I got issues with flapping sfp-port. All worked fine before on 6.37.3 and now I reverted back to bugfix only and all is fine again.

ROS: v6.38
RB: CRS125-24G-1S-2HnD and 2011UiAS (both 3.33)

WebFig doesn’t allow to set “Profile” property for L2TP-Client or PPTP-Client interfaces. WinBox (3.7) works as expected.

Steps to reproduce:

  1. Open WebFig
  2. Interfaces → Add New → PPTP Client
  3. Fill in “Connect To” and “User” fields
  4. Select “default-encryption” in “Profile”
  5. Click “Apply”
  6. Profile switches to “default”.

Most of our 1100Ax2 are freezing and have to be power cycled.

It was not fixed for my situation, when the main site was 6.38 and the clients were still 6.37.3.
It was “fixed” by upgrading every router to 6.38 which was not planned this day.
This still means that IPsec with xAuth and a password longer than 31 Chars is treated differently in ROS 6.37.3 than in 6.38 which leads to problems when “old” clients try to connect.