MikroTik

What's new in 6.35.1 (2016-Apr-25 09:29):

*) bonding - do not corrupt bonding statistics on configuration changes;
*) bonding - fixed crash when vlan parent mtu is higher than bonding mtu;
*) ethernet - do not allow mtu to be higher than l2mtu and l2mtu to be higher than max-l2mtu (reduce automatically on upgrade if it was wrong before);
*) log - fixed reboot log messages;
*) lte - do not allow to set multiple modes when it is not supported;
*) lte - fixed address acquisition on Huaweii LTE interfaces;
*) winbox - show voltage in Health only if there actually is voltage monitor;
*) wireless - fixed issue when CAPsMAN could lock CAPs interface;

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after crash.

Just upgraded my 3011 to this version... looks good!

I get error in SNMP and script.
That seems to dissolve after restarting.
The identity also seems to disappear.

12:47:21 snmp,warning timeout while waiting for program 24
12:48:04 script,warning DefConf: Unable to find wireless interface(s)

After the log does not include the Timezone.

PCC load balancing does not work after upgrade
routes does not work

irghost, please send us support output file from your router (to support@mikrotik.com).

kometchtech. Script error is self-explained, it seems that wireless interface in configuration script appeared earlier, then device was up.
Perhaps you need to add some delay to the script.

What snmp configuration do you have? Do you get such error on every reboot?

SXT LTE after upgrading 6.34.4 =>6.35.1 does not finding LTE interface. One more reboot and LTE is found and after 30 sec is connected to network and working.
SXT LTE with RouterOS 6.34.4 and Firmware 3.32 crashes at least once per day. Looses connection to LTE network (PLME search), or Kernel crash.
With big hope i'm waiting good job from 6.35.1

irghost, please send us support output file from your router (to support@mikrotik.com).

kometchtech. Script error is self-explained, it seems that wireless interface in configuration script appeared earlier, then device was up.
Perhaps you need to add some delay to the script.

What snmp configuration do you have? Do you get such error on every reboot?

there is another problem time zone set back to default

i cant send my supout because i downgrade to 6.35 and problems fixed

please first try test with ur routers then publish it
full of bugs

kometchtech. Script error is self-explained, it seems that wireless interface in configuration script appeared earlier, then device was up.
Perhaps you need to add some delay to the script.

What snmp configuration do you have? Do you get such error on every reboot?

I see the same errors as kometchtech reported and I have no particular script installed.
This is just a RB951G-2HnD with normal configuration on it.
However, the errors do not appear to affect the function of the router.
SNMP works, Wireless works.

Of course versions are tested before release. But if you would try to count possibilities in RouterOS and calculate possible combinations of them, then number would be unexpectedly large. It is not possible to test everything in lab.

In most cases problems are caused by configuration issues or unusual combinations and/or new features.

In any case you must generate supout file on this version after you have experienced some kind of problem and send it to support@mikrotik.com. We will investigate each separate case and try to find reason and solution. Even if you will downgrade and use older version still generate supout file, send it to support and then downgrade.

Since release there are only 7 posts and not all of them are negative. You can not say that version is full of bugs if one particular issue appears.

Of course versions are tested before release. But if you would try to count possibilities in RouterOS and calculate possible combinations of them, then number would be unexpectedly large. It is not possible to test everything in lab.

In most cases problems are caused by configuration issues or unusual combinations and/or new features.

In any case you must generate supout file on this version after you have experienced some kind of problem and send it to support@mikrotik.com. We will investigate each separate case and try to find reason and solution. Even if you will downgrade and use older version still generate supout file, send it to support and then downgrade.

Since release there are only 7 posts and not all of them are negative. You can not say that version is full of bugs if one particular issue appears.

that routes works in 6.35 but not in 6.35.1

It appears that v6.35.1 breaks the OID for /system health voltage monitoring (OID .1.3.6.1.4.1.14988.1.1.3.8.0). This was working in v6.35 (and prior).


[arosen@admin ~]> snmpget -v 2c -c XxXxXx 172.12.23.1 .1.3.6.1.4.1.14988.1.1.3.8.0
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-SMI::enterprises.14988.1.1.3.8.0

Please report to support@mikrotik.com with your problem description and supout files. As you can see in changelog, there are no SNMP and route changes included in this version.

Just upgraded my RB951 to this version... looks good...

Edited:
System >> Health in RB951 looks weird http://www.tiikoni.com/tis/view/?id=7143c0b

It appears that v6.35.1 breaks the OID for /system health voltage monitoring (OID .1.3.6.1.4.1.14988.1.1.3.8.0). This was working in v6.35 (and prior).

[arosen@admin ~]> snmpget -v 2c -c XxXxXx 172.12.23.1 .1.3.6.1.4.1.14988.1.1.3.8.0
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-SMI::enterprises.14988.1.1.3.8.0

I can confirm this issue on CCR1009, CCR1016 and RB2011. No problems with CCR1036 and RB450G. The "funny" thing is that it shows fine in /system health print oid...

SXT LTE after upgrading 6.34.4 =>6.35.1 does not finding LTE interface. One more reboot and LTE is found and after 30 sec is connected to network and working.
SXT LTE with RouterOS 6.34.4 and Firmware 3.32 crashes at least once per day. Looses connection to LTE network (PLME search), or Kernel crash.
With big hope i'm waiting good job from 6.35.1

hello,

I have the same problem with a much high frequency ( around 5-6 times / day and down time 1 hours each and some time i need to disable the interface and enable it again to get linkup back )

and I cannot found a way to bridge the LTE to LAN

any help?

Hi

After upgrade i have facing some problem screenshot attached.

Dears,
I discovered a problem after the upgrade to 6.35.1(6.35). The problem is related to frozen ssh connections during inactivity.
If I turn off fasttrack, the problem disappears.
affected version: 6.35, 6.35.1
unaffected version: 6.34.1
hw: CCR1072

thank you for yor help

connection parameters:
with FASTTRACK:
Flag: SACF
TCP State: established
Timeout: After connection timeout 24:00:00 than shifts to 00:05:00

without FASTTRACK:
Flag: SAC
TCP State: established
Timeout: After connection holds timeout 24:00:00

We have managed to reproduce issues with Time Zone in log, SNMP and missing router identity. We are working on fixes. Follow 6.36rc topic:
http://forum.mikrotik.com/viewtopic.php?f=21&t=107422

we can confirm observance that pcq load-balancing stopped working after upgrading to v6.35.1 because of main-routes becoming inactive.

also snmp health monitoring fails since the upgrade.

we are running capsman so we need the fixes in there...

reverting to v6.35 resolves the pcq balancing issue and health monitoring but introduces again loss of caps interfaces

reverting back to v6.35 resolves the problem

PCC load balancing does not work after upgrade
routes does not work

I have the same problem
[Ticket#2016042766000307]

Upgrading 911G-5HPnD (QRT 5) from 6.34.2 to 6.35.1 using it as Mesh Portal. When upgraded the Mesh interface disappear from Mesh interfaces. Downgrade to 6.35 and it appear again.
Other unit (RB433) connected via mesh + wds slave to the Mesh Portal board (before upgrading the QRT 5 board), upgraded to 6.35.1 and became unreachable with ping, but registered as wds. After downgraded the Mesh Portal unit to 6.35, it becames accessible again running 6.35.1.

Hello,
I have a stange problem with this new firmware, on a RB912UAG-2hpnd.
The problem is on LTE interface. When I try to set the option network-mode=auto, I receive the "syntax error".

On old 6.33 firmware, the option work correctly.
Is a bug or something is changed?
Thanks.

About policy routing issue - we are not being able to reproduce this kind of situation here locally. Those who have this problem please test:

1) If disable/enable of routes helps;
2) If reboot helps;
3) If disable/enable of gateway interface helps.

On RB133 (mipsle), using Check For Updates and "channel" current selected, it tells "Latest Version" is 6.35.1, but at www.mikrotik.com/download latest version for MIPSLE is 6.32.4.

sindudas - Yes, for mipsle latest version is 6.32.4. Upgrade service does not know about it and shows that latest version is 6.35.1 but does not and will not allow for you to upgrade.

Quick question, hopefully.

Aside from wireless repeater feature that's new in wireless-rep, are there any other differences between wireless-rep and wireless-cm2?

Aside from wireless repeater feature that's new in wireless-rep, are there any other differences between wireless-rep and wireless-cm2?

Yes, and quite a lot. Basically, most of the new wireless configuration features mentioned in the 6.35 ChangeLog are only present in the new wireless-rep package.

About policy routing issue - we are not being able to reproduce this kind of situation here locally. Those who have this problem please test:

1) If disable/enable of routes helps;
2) If reboot helps;
3) If disable/enable of gateway interface helps.

Same

About policy routing issue - we are not being able to reproduce this kind of situation here locally. Those who have this problem please test:

1) If disable/enable of routes helps;
2) If reboot helps;
3) If disable/enable of gateway interface helps.

NOP does not work

same problem in 6.36rc6

routes with mark routing does not active after upgrade

We were able to repeat routing mark problem. We will try to fix it as soon as possible.

After upgrade the RB2011L developed an inability to communicate over gigabit capable port (port started to go up/down). I disabled 1000M speeds for that port. Is it something expected for that release series?

Ivoshiee what device is connected on the other end of RB2011?

Ivoshiee what device is connected on the other end of RB2011?

It is on Telia provided Inteno. Model is unknown (at the moment), but it has GB capable ports and this box is actually running an OpenWRT.

Load balance (NTH) does not work for me any more after upgrade to 6.35.1. Reverted to 6.35 and it works again.

Also 6.35.1 boots much slower than before.

moutian
Please send us support output file from your router, when load balancing is not working.

Sergejs---I've asked this before but got no replies....in the CHANGELOG can you please add a date/timestamp for each line item on when these were added and even more info like version affected etc?

Thanks leon

wa4zlw, this 2016-Apr-25 09:29 is a timestamp for the listed features, when they were added to the specific version.

It appears that v6.35.1 breaks the OID for /system health voltage monitoring (OID .1.3.6.1.4.1.14988.1.1.3.8.0). This was working in v6.35 (and prior).

[arosen@admin ~]> snmpget -v 2c -c XxXxXx 172.12.23.1 .1.3.6.1.4.1.14988.1.1.3.8.0
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-SMI::enterprises.14988.1.1.3.8.0

I can confirm this issue on CCR1009, CCR1016 and RB2011. No problems with CCR1036 and RB450G. The "funny" thing is that it shows fine in /system health print oid...

I can also confirm this. Something is definitely broken with oids for health monitoring.(at least for RB1100ahx2)

Guys, thank you very much for the report on health. We were able to repeat the issue and it is being fixed right now.
The next .2 version will include fixes for it.

While you are at it, how about fixing the health stats on RB2011?

It has been reported multiple times many verions back and it was simply ignored.
http://forum.mikrotik.com/viewtopic.php ... 70#p530170
http://forum.mikrotik.com/viewtopic.php ... ge#p521666
http://forum.mikrotik.com/viewtopic.php ... 75#p520275

Here's RB2011UiAS-RM working perfectly fine: And here's RB2011UAS-RM reporting completely false (or missing) numbers: Both boards have the exact same configuration.

wireless-rep still does not work with an old Intel 2200BG wireless card in AB-Bridge mode.
wireless-cm2 works.

Just a note: I already reported this at http://forum.mikrotik.com/viewtopic.php ... 50#p522747

Cha0s, thank you very much for the report. We will see what we can do. For the future report such issues to us directly (support@mikrotik.com).

RB2011, after upgrading 6.35 -> 6.35.1 can't access to IP aliases from the same IP network.
# ADDRESS NETWORK INTERFACE
0 192.168.22.27/28 192.168.22.16 br-22
1 192.168.22.28/28 192.168.22.16 br-22
2 192.168.22.29/28 192.168.22.16 br-22
3 192.168.22.30/28 192.168.22.16 br-22

My address is 192.168.22.25/28 and I can ping (access) only one of aliases. After reboot the router I can ping only one another or nothing...
It look likes as something arp bug.

XaTTa6bl4 I assume your issue is related to the configuration, not to MikroTik RouterOS 6.35.1 version.
Make support output file from your router, when ping does not work properly and send it to support@mikrotik.com

I have RB2011UiAS and when I'm testing my connection 100MB I see that CPU is used 80-95%
I'm using PPPoE connection to my provider.

Because of this I have to change my config to not exceed 100% of CPU. Otherwise I can't fully use my speed.
I'm just supposed that this is only on this last version v 6.35.1.

Upgraded RB2011UiAS from 6.35 to 6.35.1 and all seemed to work... for a while. Then internet access over bridged pppoe DSL connection started slowing.
Remote Desktop to a client server with RB941 on 6.35 kept on disconnecting and very slow.
The next symptom was Teamviewer refused to connect to client computers from the Computers and Contacts list.
Some web sites maintained speed whilst others were impossibly slow.
RB CPU and memory were within normal parameters.

Removed Heimdal and eliminated DNS as an issue.
Did the usual reboots with no improvement.

Downgraded RB2011 to 6.35 and Teamviewer worked again. RDP to client still disconnecting.
Downgraded clients RB941 to 6.35 and RDP fine - fast and no disconnects

Reinstalled Heimdal - all functions working. RDP and Teamviewer working correctly.

Assumption it is to do with the pppoe interface on the latest release.

We will wait for next release and re test.

when restoring a config and space is very low, I get an errormessage, which leads me to a totally differen cause... It says, restoring config is not possible.
Do you create a local tempfile while restoring?

I have RB2011UiAS and when I'm testing my connection 100MB I see that CPU is used 80-95%
I'm using PPPoE connection to my provider.

Because of this I have to change my config to not exceed 100% of CPU. Otherwise I can't fully use my speed.
I'm just supposed that this is only on this last version v 6.35.1.

use fasttrack rules

PCC load balancing does not work after upgrade
routes does not work

: urgent help I have the same problem with load balancing, I have a rb850

Guys, after I did delete all my routes and firewall rules and added them back it all started to work again. I do not know.. maybe I just did mess up something myself but, just did "/ip route export" and "/ip firewall mangle export" and did remove all routes and mangle rules afterwards. Imported commands from export output and it started to work again.

we can confirm observance that pcq load-balancing stopped working after upgrading to v6.35.1 because of main-routes becoming inactive.

also snmp health monitoring fails since the upgrade.

we are running capsman so we need the fixes in there...

reverting to v6.35 resolves the pcq balancing issue and health monitoring but introduces again loss of caps interfaces

reverting back to v6.35 resolves the problem

same here: I'm running 3 hap ac here (1 is capsman+cap the other two are cap) and since upgrading to 6.35.1 I see the cap (on the box with capsman running) missing in capsman. rebooting not solving anything, disable/enable caps not working. the wlan interfaces do show and scanning does work. however when turning them on (as local wlan) the default microtik ssid also does not come alive and no logging

did reverting back solve the caps missing issue ?

wa4zlw, this 2016-Apr-25 09:29 is a timestamp for the listed features, when they were added to the specific version.

I'd like more specific info on each item with a date/timestamp

leon

6.35.1 finally solved fcs errors on AirFiber24 links for me!

After repeatedly performing the commands :
interface l2tp-server server set enabled=yes
or
interface pptp-server server set enabled=yes

(more than 10 times in a row), pptp and l2tp server stops working,
the connection of customers to them is impossible!
Please fix this error.

On a RB433 I have multiple default gateways set and the default gateways with routing mark set went out of use by the v6.35.1 (all these routes were turned blue in winbox) and I was cut off from the network on that box. I've managed to find an older firmware on my laptop and recovered that given functionality. Should I expect that to be fixed or what to think about it?

Please FINALLY FIX SFP DDM INFORMATION READING

On CRS125, there is nothing shown in SFP tab...

HOWEVER i've successfully readen DDM data (and RX/TX power was updated few times a seconds too) today on CRS125.

How it's fixed?
Run CRS125 without SFP module.
Tick system restart, while restarting PLUG SFP module in.
DDM data is there.

If you will reboot CRS now, DDM will not come back anymore

PPP User (pptp vpn) could not disconnect from routeros from 6.35

After the upgrade, i lost my vrrp interfaces ...
But this is fix in the next RC.

But i have problem with my site tot site now , they don't pass ant TCP trafic. UDP and ICMP are working fine.
But TCP not

Please FINALLY FIX SFP DDM INFORMATION READING

On CRS125, there is nothing shown in SFP tab...

HOWEVER i've successfully readen DDM data (and RX/TX power was updated few times a seconds too) today on CRS125.

How it's fixed?
Run CRS125 without SFP module.
Tick system restart, while restarting PLUG SFP module in.
DDM data is there.

If you will reboot CRS now, DDM will not come back anymore

What vendor - model transceiver you use in that CRS125? Possibly it is having some trouble reporting info back to host.

The voltage displayed for an RB2011UiAS is not plausible. 1143.7V?
Edit to add: fixed by firmware update, so the problem is 6.35.1 (and perhaps earlier, I don't know when this problem started) plus firmware 3.18 (ditto).

Hi,
we have bis problem with tile CCR-1036-12G-4S.
Last version 6.35.1 is installed, but after 2 days later mikortik pasword is empty. You can login without password!
Ip> Pool is blank.

I try make supout.rif, but can´t find among Files!

Reboot can help, but aftter 2-3 days have the same problem!

What can I do?

I had a bug upgrading to this.

I use policy based routing, and had 3 route tables and main.

All my routes in my other route tables besides main went down when I upgraded. They would not show as active.

I had to completely remove them all, and add them all back in with different table names in order to get it all working again.

Even just changing the table names would fix the route, but then when I changed it back to the old table name, it made the route not active again.

As a side note I used interface names for all my routes And there were about 1500 static routes on the router (around 300 per routing table and in the main table.

Please FINALLY FIX SFP DDM INFORMATION READING

On CRS125, there is nothing shown in SFP tab...

HOWEVER i've successfully readen DDM data (and RX/TX power was updated few times a seconds too) today on CRS125.

How it's fixed?
Run CRS125 without SFP module.
Tick system restart, while restarting PLUG SFP module in.
DDM data is there.

If you will reboot CRS now, DDM will not come back anymore

What vendor - model transceiver you use in that CRS125? Possibly it is having some trouble reporting info back to host.

They are AscentOptics modules, you can get datasheet from there:

http://www.ascentoptics.com/en/dow.asp?Pid=93

The voltage displayed for an RB2011UiAS is not plausible. 1143.7V?

Code: Select all

[igb@rb2011-1] /system identity> /system routerboard print 
       routerboard: yes
             model: 2011UiAS
     serial-number: 444702957500
     firmware-type: ar9344
  factory-firmware: 3.09
  current-firmware: 3.18
  upgrade-firmware: 3.33
[igb@rb2011-1] /system identity> /system health print      
  voltage: 1143.7V
[igb@rb2011-1] /system identity> 

Edit to add: fixed by firmware update, so the problem is 6.35.1 (and perhaps earlier, I don't know when this problem started) plus firmware 3.18 (ditto).

Code: Select all

[igb@rb2011-1] > /system health print 
      voltage: 24.1V
  temperature: 27C
[igb@rb2011-1] > /system routerboard print 
       routerboard: yes
             model: 2011UiAS
     serial-number: 444702957500
     firmware-type: ar9344
  factory-firmware: 3.09
  current-firmware: 3.33
  upgrade-firmware: 3.33
[igb@rb2011-1] > 

The bug started on 6.34.1
http://forum.mikrotik.com/viewtopic.php ... 87#p519887

In my case an RB2011UiAS shows the proper voltage/temperature where an RB2011UAS does not
http://forum.mikrotik.com/viewtopic.php?f=21&t=107686

Both with latest firmware (3.33) and RouterOS v6.35.1.

RB433UAH (6.35.1) ethernet port graf statistic Top Speed 506,26 Mb/s

inserting images prohibited

where is update? 6.35.2 to fix these bugs

I'm using CCR1036-12G-4S 6.35.1 as PPPoE concentrator, about 100 PPPoE servers and all of them except one are on EoIP tunnels. That one server is running on ether5 interface with exactly same profile and settings as others. User connected to PPPoE server on ether5 interface will disconnect on exactly 5 minutes (it's for testing purposes and I'm only user there, so it's not that big of a problem), there is always 4-5mbps running so it isn't idle. As soon I connect to PPPoE over EoIP (same CPE) it works without problems. This didn't happen on 6.32.2 and error I get is "terminating... link inactive". Can anyone try to reproduce it?

edit: After inserting ether5 under bridge interface (eth5 is only interface in bridge) connection doesn't terminate after 5 minutes. So I guess that it is a bug.

i have some of oid functions broken on CRS...
but the same functions still work fine on RB750UP and RB2011.
while the snmpwalk only show : i wanna to attach the picture / screen shoot from my computer but i do now know how to do it.

P

'safe mode' under winbox also does not work.
i do connect into my CRS via wireless, open winbox, click safe mode, and disable wlan1
after long wait (more than 15 minutes), the interface wlan1 still disable and i have to connect with wire to enable it again.

P

It is not necessary to double the posts. You already rised this topic few days ago. http://forum.mikrotik.com/viewtopic.php ... 34#p535534

dear jarda,

the previous post was made when i use 6.35; not 6.35.1
while everyone talk about .6.35.1, is it wrong if i remind the mikrotik developer to have a look into unworking "safe mode" for winbox ?

P

Ok. But it seems that the lack of safe mode functionality is not linked specifically to the latest version introduced here but it is general bug.

i have a issue with wireless 2.4 which appears to also be in 32.4 none of my 40mhz capable device are going into 40mhz, they are stuck at 20mhz? 5gz dual band ac radio does not have this problem? anyone else seeing this?

PCC load balancing does not work after upgrade
routes does not work

The same issue!

Please FINALLY FIX SFP DDM INFORMATION READING

They are AscentOptics modules, you can get datasheet from there:

http://www.ascentoptics.com/en/dow.asp?Pid=93

I don't have exactly those modules for testing, but I checked with various other vendor ones and no problems with any of them.

As I mentioned possibly modules them selves are acting up sometimes. System can stop attempting to read ddmi if there are to many failed attempts.

[

As I mentioned possibly modules them selves are acting up sometimes. System can stop attempting to read ddmi if there are to many failed attempts.

These modules DDM works perfectly in other manufacturer equipment (i.e. DASAN networking).
I can send you one module for tests, or make some tests/debug if needed (i can attach logic analyzer to TWI line and give you sniff if needed )

Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.

After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:

00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss

I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...

Thanks for any help.

Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.

After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:

00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss

I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...

Thanks for any help.

1. the mentioned log means your signal was not great after all, it means weak signal due to low signal or noise
2. downgrade is done with a special command "/system package downgrade", simple reboot doesn't make downgrade like for upgrades

Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.

After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:

00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss

I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...

Thanks for any help.

1. the mentioned log means your signal was not great after all, it means weak signal due to low signal or noise
2. downgrade is done with a special command "/system package downgrade", simple reboot doesn't make downgrade like for upgrades

Normis, thank you for your response. Regarding your comments, the wifi signal was working perfectly before the upgrade. Is there any other report of problems with this newer version?

yes, the downgrade attempt was done using that command.. but for some reason, after the rebook, it came back with the same version. Just tried again:

[admin@ho-rt-01] > /system package downgrade
Router will be rebooted. Continue? [y/N]:
y
system will reboot shortly
[admin@ho-rt-01] >

And it still came back like:
MikroTik RouterOS 6.35.1 (c) 1999-2016

Any idea?

Best regards.

Seeing the time zone problem in the logs on 3011s and hEX. CCR1009 does not have the issue.

Did you upload the old firmware version first to the files area?

Yesterday I made the upgrade on my new router CRS125-24G-1S-2HnD, which I got 1 week ago and came running an old sw version, 6.6.

After the upgrade, the wifi clients keeps disconnecting all the time, even when signal is strong. On the logs, I see tons of for all wifi clients:

00:56:CD:XX:XX:XX@wlan1: disconnected, extensive data loss

I tried to downgrade, but for some reason, after the reboot, it came back with the same 6.35.1. I ried also searching the forum for problems like this, but none indicated what could be happening, and since the problem started after the upgrade...

Thanks for any help.

1. the mentioned log means your signal was not great after all, it means weak signal due to low signal or noise
2. downgrade is done with a special command "/system package downgrade", simple reboot doesn't make downgrade like for upgrades

Normis, thank you for your response. Regarding your comments, the wifi signal was working perfectly before the upgrade. Is there any other report of problems with this newer version?

yes, the downgrade attempt was done using that command.. but for some reason, after the rebook, it came back with the same version. Just tried again:

[admin@ho-rt-01] > /system package downgrade
Router will be rebooted. Continue? [y/N]:
y
system will reboot shortly
[admin@ho-rt-01] >

And it still came back like:
MikroTik RouterOS 6.35.1 (c) 1999-2016

Any idea?

Best regards.

Did you upload the old firmware version first to the files area?

Now I feel stupid.. haha

No, I didn't know I should (since I had not deleted anything, I thought it was there already and documentation I found didn't say anything about that).

But that gave me the direction already. Thank you

Version 6.35.2 has been released:
http://forum.mikrotik.com/viewtopic.php?f=21&t=108137