*) 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.
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
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.
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.
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 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 )
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