v6.49 [stable] is released!

emils · Thu Oct 07, 2021 5:37 pm

RouterOS version 6.49 has been released in public "stable" channel!

Before an upgrade:
1) Remember to make backup/export files before an upgrade and save them on another storage device;
2) Make sure the device will not lose power during upgrade process;
3) Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 6.49 (2021-Oct-06 11:55):

*) branding - fixed LCD logo loading from branding package when installed via Netinstall;
*) branding - properly clean up old branding files before installing a new one;
*) bridge - added IGMP and MLD querier monitoring;
*) bridge - added IGMP snooping log when multicast table gets full;
*) bridge - fixed external flag in the host table for wireless clients;
*) bridge - improved controller bridge stability when adding RouterOS v7 port extender;
*) bridge - improved port extender stability when creating bond interfaces on excluded ports;
*) bridge - improved stability when quickly adding and removing bridge interface;
*) certificate - improved stability when removing dynamic CRL entries;
*) chr - fixed OS provisioning on Azure;
*) chr - improved stability when changing "flow-control" settings on interfaces with e1000 drivers;
*) conntrack - increased total connection tracking table size based on installed RAM size;
*) console - require "write+ftp" permissions for executing script to file;
*) console - require "write+ftp" permissions for printing to file;
*) crs3xx - correctly filter packets by L2MTU on 1Gbps Ethernet interfaces for CRS354 devices;
*) crs3xx - fixed LEDs for QSFP+ interface on CRS326-24S+2Q+ device;
*) crs3xx - fixed SFP and SFP+ link rate reporting (introduced in v6.48beta11);
*) crs3xx - fixed bridge controller and extender packet forwarding for CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed default MAC address calculation on management Ethernet for CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - fixed interface flow control;
*) crs3xx - improved QSFP+ linking and mode changing for CRS326-24S+2Q+ and CRS354 devices;
*) crs3xx - improved packet transmit on SFP+ interfaces;
*) crs3xx - improved switch resource allocation for CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) defconf - apply default configuration from branding package when performing reset with button;
*) defconf - removed overlapping IPv6 firewall rules;
*) defconf - use router as DNS server for DHCP hosts;
*) dhcp-server - fixed DHCP Option decimal value parsing;
*) dhcpv4-server - reset dynamic "bcast" flag when receiving offer from DHCP relay;
*) dhcpv4-server - reset lease's dynamic "bcast" flag on packets from relay;
*) dhcpv6-server - check if pool name has changed from RADIUS on renew;
*) dhcpv6-server - improved dynamic server entry update;
*) discovery - do not send discovery packets on interfaces that are blocked by STP (introduced in v6.48);
*) dns - fixed memory leak caused by large DNS replies;
*) firewall - fixed "ingress-priority" matcher;
*) firewall - fixed GRE protocol packets considered invalid when PPTP helper is disabled;
*) gps - improved interface monitoring;
*) health - added "phy-temperature" sensor monitoring for CRS312 device;
*) health - improved temperature readings on hEX S;
*) health - improved temperature reporting;
*) ike2 - added support for ASN.1 DN "my-id" value setting for initiators;
*) ike2 - check if TS is still valid after obtaining SPI;
*) ike2 - fixed initiator packet retransmit with DDOS cookie;
*) ipsec - fixed memory leak when processing DHCP packets;
*) ipsec - improved SA update by SPI;
*) ipsec - improved system stability on CHR;
*) ipsec - improved system stability on MMIPS devices;
*) kid-control - improved IPv6 firewall rule generation;
*) led - added LTE LED support for LHGGR;
*) leds - fixed LTE LED default mapping for wAP R ac LTE kit;
*) lora - added additional predefined network servers;
*) lora - added channel plan "il-917" for Israel;
*) lora - fixed "PULL_DATA" token generation;
*) m33g - improved support for "/system gpio" menu ("/system routerboard upgrade" required);
*) m33g - removed 12..16 pins from "/system gpio" menu;
*) mipsbe - improved booting speed on non-NAND devices ("/system routerboard upgrade" required);
*) mpls - allow to disable FastPath (CLI only);
*) mqtt - added server name indication;
*) netinstall - fixed lock file persistence after reinstall;
*) netinstall - improved bootp packet handling on Linux netinstall-cli version when multiple NIC's are present;
*) netinstall - require Netinstall version to be the same or newer as "factory-software";
*) ntp - use correct IPv6 multicast group for SNTP client;
*) package - always allow to uninstall package even if there is no free disk space left;
*) poe - update PoE firmware only on devices that supports it;
*) ppp - improved stability when receiving bogus response on modem channel;
*) qsfp - improved system stability when setting unsupported link rates;
*) quickset - use 5GHz interface's country for "Home AP Dual" configuration;
*) routerboard - fixed "reformat-hold-button-max" validation for values below 10s;
*) sfp - added "sfp-rate-select" setting;
*) sfp - fixed GPON module linking (introduced in v6.47);
*) sfp - improved 25Gbps optical module stability and linking;
*) sfp - improved SFP, SFP+, SFP28 and QSFP+ interface stability for CRS3xx and CCR2004 devices;
*) sfp - improved link stability for 10G, 25G and 40G modules on CRS309, CRS312, CRS326-24S+2Q+ CRS354 and CCR2004 devices;
*) sfp28 - changed FEC auto mode to disabled;
*) snmp - added "engine-id" OID support;
*) snmp - fixed "ipNetToMediaType" OID for incomplete entries;
*) ssh - fixed "undo" functionality;
*) supout - added controller bridge section;
*) supout - print detailed list of active user sessions;
*) switch - fixed (R/M)STP port blocking right before switching them in HW bridge (fixes possible packet loop when changing bridge settings);
*) switch - improved packet transmit between CPU and 98PX1012 for CCR2004-1G-12S+2XS device;
*) swos - fixed "static-ip-address" parameter;
*) tr069-client - added "X_MIKROTIK_LinkDowns" parameter for interface "link-downs" value reporting;
*) tr069-client - added support for Ethernet link speed reporting;
*) tr069-client - added support for interface comment reporting and editing;
*) tr069-client - added support for supout file upload;
*) tr069-client - fixed traceroute diagnostics time values;
*) tr069-client - improved XML with new-lines for readable output;
*) tr069-client - improved stability for download/upload diagnostics;
*) upgrade - fixed free space checking on flash type memories when installing new packages;
*) ups - added battery info for APC Back-UPS BX750MI;
*) user - added "expired" user status with suggestion to change password (WinBox v3.29 required);
*) user - fixed active user session purging on disconnect;
*) user - show "expired password" prompt for users with blank password;
*) w60g - general stability and performance improvements;
*) w60g - limit power output when using region EU to match EN302567 on nRAY;
*) w60g - use EU region by default;
*) webfig - added support for logo image from branding package;
*) webfig - do not show value units twice;
*) webfig - fixed "Wireless/CAP" menu opening;
*) webfig - fixed interface sorting by name;
*) webfig - show only "Close" button under "Wireless/Wireless Sniffer/Sniffed Packets" menu;
*) winbox - added "dhcp" option to "multicast-helper" setting;
*) winbox - added "fec-mode" parameter under "Interface/Ethernet" menu;
*) winbox - added "interface-speed-100G" LED type to "System/LEDs" menu;
*) winbox - added "name" and "file-name" parameter when importing and exporting certificates;
*) winbox - added "sfp-shutdown-temperature" setting to SFP interfaces;
*) winbox - added SSH settings under "IP/SSH" menu;
*) winbox - added TFTP settings under "IP/TFTP/Settings" menu;
*) winbox - allow setting MCS (24-31) to 4x4 Wireless interfaces;
*) winbox - do not allow to add/remove W60G interfaces;
*) winbox - do not allow to set empty "init-string" field under "System/GPS" menu;
*) winbox - do not show "GPS antenna" selection for devices without selection support;
*) winbox - fixed "Secondary Frequency" parameter setting under "CAPsMAN/Channel" menu;
*) winbox - fixed DNS "cache-size" parameter setting;
*) winbox - fixed health reporting on RB960, hEX, hEX S and hAP ac3 devices;
*) winbox - fixed order of weekdays under "IP/Firewall" menu;
*) winbox - fixed support for "Delegated-IPv6-Prefix" for PPP services;
*) winbox - match "MAC Protocol-Num" predefined values under "Bridge/Filters" menu;
*) winbox - minimal required version is v3.30;
*) winbox - properly show "CRL Signature" field under "System/Certificate" menu;
*) winbox - separated CCQ Tx and Rx values in their own unique columns;
*) winbox - show "System/Health/Settings" only on boards that have configurable values;
*) winbox - show "current-channel" column by default for CAP interfaces;
*) winbox - show IPv6 address in separate field under "IP/Cloud" menu;
*) wireless - added U-NII-2 support for US and Canada country profiles for hAP ac lite;
*) wireless - added override for multicast-to-unicast translation of DHCP traffic;
*) wireless - do not remove channels >2462 MHz from "scanlist" if scanning for fixed channel;
*) wireless - do not send packet back to station-bridge it was received from;
*) wireless - fixed minor typo in debug logging messages;
*) wireless - improve WMM priority assignment for packets with internal priority greater than 7;
*) wireless - improve regulatory compliance with DFS requirements;
*) wireless - improve signaling of QCA9984 interface capabilities when using 160/80+80MHz channel width;
*) wireless - improved system stability when sending packets through interface after L2MTU is increased;
*) wireless - log client signal strength on disconnect;
*) wireless - renamed "secondary-channel" to "secondary-frequency";
*) wireless - updated "israel" regulatory domain information;
*) wireless - updated "united kingdom" regulatory domain information;

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

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 some problem has appeared on device

Please keep this forum topic strictly related to this particular RouterOS release.

krafg · Thu Oct 07, 2021 5:46 pm

Thanks a lot, today I will upgrade my devices.

Edit: Upgraded all my devices successfully and the health information on my PowerBoxes has been fixed!

Regards.

VitohA · Thu Oct 07, 2021 5:58 pm

Just curious, why you chose such naming convention? 6.49rc2 (testing) vs 6.49 (stable), for me it looks like stable is a newer one, release candidate that became a release. Please correct me if I'm wrong.

Thu Oct 07, 2021 6:23 pm

https://help.mikrotik.com/docs/display/ ... stallation

VitohA · Thu Oct 07, 2021 7:10 pm

https://help.mikrotik.com/docs/display/ ... stallation

Thanks, got it. My bad, used to see that testing is usually 1 minor version ahead.

pe1chl · Thu Oct 07, 2021 7:20 pm

*) dns - fixed memory leak caused by large DNS replies;

Yes, the memory leak appears to be fixed, the resolver now returns the large replies OK, but they still aren't loaded into an address list :-(

pe1chl · Thu Oct 07, 2021 7:34 pm

Thanks, got it. My bad, used to see that testing is usually 1 minor version ahead.

When testing moves from beta## to rc# and after one or more rc# the new stable is released, the stable version gets that major version number (without beta or rc suffix) and the testing remains at rc# for some time until it updates to the next version number and beta##.

osc86 · Thu Oct 07, 2021 8:26 pm

*) sfp28 - changed FEC auto mode to disabled;

no, when I updated a CCR2004-1G-12S+2XS it turned on auto mode and I lost connectivity.
But even with auto mode enabled, it fails to detect the correct mode. fec91 is the only mode that works in my case, configured it manually.

Guscht · Thu Oct 07, 2021 10:18 pm

FCK MIKROTIK!!!!

Got half a heart attack and half a stroke!!!

The CCR1072 took around 15 minutes and CCR1036 around 10 minutes to come back after the firmware update.

PS: The (SNMP) voltage reading of the CCR1036 is correct again.

Edit: I can confirm, after applying the 6.49 firmware update, every reboot of the CCR1072 will took arounf 15 minutes and of the CCR1036 around 10 minutes.

nithinkumar2000 · Thu Oct 07, 2021 10:47 pm

Any Imporvement in Delegated IPv6 Prefix Parameter in Radius Accounting Issue???

mkamenjak · Thu Oct 07, 2021 10:54 pm

FCK MIKROTIK!!!!
Got half a heart attack and half a stroke!!!

The CCR1072 took around 15 minutes and CCR1036 around 10 minutes to come back after the firmware update.

PS: The (SNMP) voltage reading of the CCR1036 is correct again.

Edit: I can confirm, after applying the 6.49 firmware update, every reboot of the CCR1072 will took arounf 15 minutes and of the CCR1036 around 10 minutes.

What version is your routerboot(firmware) at?

Guscht · Thu Oct 07, 2021 10:57 pm

What version is your routerboot(firmware) at?

ROS 6.49
Firmware: 6.49

Reproducable on all CCR1072 and CCR1036 devices...

honzam · Thu Oct 07, 2021 11:03 pm

*) wireless - log client signal strength on disconnect;
It is possible add this feature with NV2 protocol?

ivicask · Thu Oct 07, 2021 11:40 pm

Cant upgrade 2x LHG 5 AC from 6.49beta22 to 6.49 Stable, not enough space, i got nothing on internal storage...

diamuxin · Thu Oct 07, 2021 11:41 pm

Hi, I have a recently updated RB4011 to 6.49 and the temperature probe has a problem, it ranges between -274 and 32ºC. Before updating it was ok.

Any solution?

Edit: Also, the IPv6 address cannot be obtained through the IP Cloud.

:put [/ip cloud get public-address-ipv6]

Best regards.

pe1chl · Fri Oct 08, 2021 12:06 am

Cool! (very cool indeed...)

Guscht · Fri Oct 08, 2021 1:49 am

Did further investigation regarding the long-boot issue.

ROS 6.48.4 + Firmware 6.48.4 -> no issue -> booting takes around 1:30 minutes
ROS 6.49 + Firmware 6.48.4 -> no issue -> booting takes around 1:30 minutes
ROS 6.49 + Firmware 6.49 -> issue -> booting takes around 10 minutes!

I have done now a few down/upgrades, always with the same effect.
The shutdown sequence will durate about 8:15 minutes. The following boot is as fast as normal in about 1:30 minutes.

This issue is reproducible on all our CCR1072 and CCR1036 devices. Not reproducible on our CRS and RB devices.

nichky · Fri Oct 08, 2021 3:14 am

what "fec-mode" does?

maigonis · Fri Oct 08, 2021 8:40 am

Cant upgrade 2x LHG 5 AC from 6.49beta22 to 6.49 Stable, not enough space, i got nothing on internal storage...

That usually is an existing firmware bug, do netinstall.

mducharme · Fri Oct 08, 2021 8:48 am

*) winbox - fixed support for "Delegated-IPv6-Prefix" for PPP services;

What exactly was fixed here?

alexv87 · Fri Oct 08, 2021 9:31 am

*) ups - added battery info for APC Back-UPS BX750MI

How would you be able to connect this model to the device it only has usb and it's not Smart UPS. I thought Mikrotik supports only APC Smart.

jbl42 · Fri Oct 08, 2021 9:44 am

Confirm the temp reading problem in System/Health on RB4011 and 6.49:
The temp changes between -274° and the correct value every 10-15s.
Voltage value is OK.

-274° is probably some internal zero raw value converted to degrees (-273.15° is absolute zero temp).

mducharme · Fri Oct 08, 2021 10:15 am

Yes, this is unlikely a bug in the new version. We regularly see the RB temperature sensors return absolute zero when they cannot get a proper reading, in any version of RouterOS.

dhoulbrooke · Fri Oct 08, 2021 10:40 am

*) ups - added battery info for APC Back-UPS BX750MI
How would you be able to connect this model to the device it only has usb and it's not Smart UPS. I thought Mikrotik supports only APC Smart.

https://help.mikrotik.com/docs/display/ ... toring+UPS

Items needed for the setup:
1) A Mikrotik device with a USB or RS232 port;
2) USB or RS232 cable;
3) APC UPS with a USB port.

Chupaka · Fri Oct 08, 2021 10:46 am

*) user - added "expired" user status with suggestion to change password (WinBox v3.29 required);
*) winbox - minimal required version is v3.30;

DarkNate · Fri Oct 08, 2021 10:48 am

What exactly was removed?

*) defconf - removed overlapping IPv6 firewall rules;

pe1chl · Fri Oct 08, 2021 11:28 am

What exactly was removed?

*) defconf - removed overlapping IPv6 firewall rules;

In the default config there is an address list bad_ipv6 that contained some addresses that were actually subnets of another one. These were removed.

owsugde · Fri Oct 08, 2021 12:13 pm

*) wireless - improve regulatory compliance with DFS requirements;

Is there info on what has been changed with DFS a bit more precisely?

umatrix · Fri Oct 08, 2021 3:04 pm

Anyone have IP-IP tunnel + IPSec problem?
After morning update, between my CCR1036 and RB2011 stopped tunneled traffic if tunnel IPSec encrypted.
Nothing other changed on this routers.

Same issue with L2TP IPSec tunnels. Error message: "Tunnel was not encrypted"
Is there a solution besides downgrading?

jbl42 · Fri Oct 08, 2021 3:18 pm

Yes, this is unlikely a bug in the new version. We regularly see the RB temperature sensors return absolute zero when they cannot get a proper reading, in any version of RouterOS.

This might be a coincidence. But checking our SNMP log, we only see occasional -274° temp values on the two RB4011 updated to 6.49. Not on others still running 6.48.x.

krafg · Fri Oct 08, 2021 3:44 pm

Problems with health continues on some devices:

RB1100AHx4: No temperature
mANTBox2: Temperature = -274

Regards.

squeezypiano · Fri Oct 08, 2021 5:45 pm

Hi,

Does anyone know what has changed in 6.49 that would stop Rancid from connecting and taking a backup? Initially I thought it was to do with expired user account but have worked through all that and mtlogin can get in but rancid-run fails to pull the config.

Thanks.

pe1chl · Fri Oct 08, 2021 5:56 pm

Same issue with L2TP IPSec tunnels. Error message: "Tunnel was not encrypted"
Is there a solution besides downgrading?

Depending on the path the IPsec traffic takes between routers (e.g. via another NAT router or stateful firewall), IPsec tunnels can sometimes fail when one side is rebooted even without any software change.
So it is always risky to upgrade a router and then conclude there is an error in the new firmware. It could have failed when you had merely rebooted the router instead of upgrading it.
Only when you have experience with doing that and knowing that it never causes issues in your particular setup you can pinpoint the upgrade as a cause.
The tunnel may come back when you disable it for 5-10 minutes and then re-enable it. If so, it likely was an issue as suggested above.

Railander · Fri Oct 08, 2021 7:07 pm

Hi,

Does anyone know what has changed in 6.49 that would stop Rancid from connecting and taking a backup? Initially I thought it was to do with expired user account but have worked through all that and mtlogin can get in but rancid-run fails to pull the config.

Thanks.

maybe it's related to this?

*) console - require "write+ftp" permissions for executing script to file;
*) console - require "write+ftp" permissions for printing to file;

blazej44800 · Fri Oct 08, 2021 9:28 pm

Hello everyone,

today I used 6.49 on newly upgraded site with RB953GS-5HnT. After 80 minutes it was rebooted "Without proper shutdown by watchdog timer". After next 30 minutes again. I did downgrade to 6.48.5 and no reboot yet (5 hours). Auto supout was not created.

diamuxin · Sat Oct 09, 2021 8:48 am

IPv6 address mapping in IP Cloud does not work. Everything worked in RC2.

The same happens to me.

diamuxin · Sat Oct 09, 2021 8:57 am

Problems with health continues on some devices:

RB1100AHx4: No temperature
mANTBox2: Temperature = -274

Regards.

The same happens to me. RB4011. Temperature -274.
In 15-20s it changes to the correct temperature and again returns to -274

Regards.

JJT211 · Sat Oct 09, 2021 10:26 am

FCK MIKROTIK!!!!
Got half a heart attack and half a stroke!!!

The CCR1072 took around 15 minutes and CCR1036 around 10 minutes to come back after the firmware update.

PS: The (SNMP) voltage reading of the CCR1036 is correct again.

Edit: I can confirm, after applying the 6.49 firmware update, every reboot of the CCR1072 will took arounf 15 minutes and of the CCR1036 around 10 minutes.

Stick with long-term, especially on big routers like that that are most likely used for the Core of your network.

winap · Sat Oct 09, 2021 11:02 am

Hey Mikrotik,
When I looked on some threads, you make very basic bugs in every new firmware...Is this normal programming? Because when I buy some crap Asus, TP-Link...it has more stable firmware, than this...
In my view you don't understand, what you programming or what is some function for...Because if you know it, there will be less bugs in new firmware. Maybe will be better do less function, but stable than many features, but buggy and useless..Testing longer and than make publication like new firmware to people. Because it is not beta and some ISP have hard time, for repair it, or the internet wan't function correctly and the people are angry! And why..because ISP want to have newer FW and not so buggy. So make some new jobs for people, programming some AI for learning how to make work some router correctly and the AI will corect some code in your FW. Because the AI will be testing more functions, than human, if you don't have some time to testing it. This is not funny for me, as a costumer. Because when I setup some function and the setup not working, it's hard for me, because I don't know, if I make some mistake, or it's only bugs in your firmware. Thank you for understanding.

jbfavre · Sat Oct 09, 2021 11:13 am

Hello,
I upgraded my CCR1009 yesterday… and lost my internet connection.
My SERCOMM FGS202 SFP Module isn't recognized anymore. Problem is, it's a quite widely used one in France since the main ISP Orange ships it with their Internet box.

I did not see such change in the release notes.
Is this the intended behaviour ?

Best,
Jean Baptiste

jimmer · Sat Oct 09, 2021 12:08 pm

Hi all, not a real issue per se, but I did notice my CPU usage at idle went up 2-3% on my RB3011 between 6.48.4 and 6.49 - Anyone else seeing similar? it could just be the way SNMP is calculating it. Value graphed is being read from OID: .1.3.6.1.4.1.2021.11.10.0

Kind Regards,
Jim.

kehrlein · Sat Oct 09, 2021 2:03 pm

Updated several devices without any issues:
CCR1009-7G-1C-1S+
CCR2004-1G-12S+2XS
CRS326-24G-2S+
CRS112-8P-4S
RB750GL
RB1100AHx4

pe1chl · Sat Oct 09, 2021 4:44 pm

Hello,
I upgraded my CCR1009 yesterday… and lost my internet connection.
My SERCOMM FGS202 SFP Module isn't recognized anymore. Problem is, it's a quite widely used one in France since the main ISP Orange ships it with their Internet box.

When you have such a router (i.e. not one of the new home routers with 16MB flash), always partition the flash into 2 partitions so you can copy the working partition, then upgrade, and when you have issues like that you can switch to the other partition and have everything back untouched. No need to do downgrades, and when someone posts a workaround here you can switch back and try it.

Florian · Sat Oct 09, 2021 7:47 pm

Hello,
I upgraded my CCR1009 yesterday… and lost my internet connection.
My SERCOMM FGS202 SFP Module isn't recognized anymore. Problem is, it's a quite widely used one in France since the main ISP Orange ships it with their Internet box.
When you have such a router (i.e. not one of the new home routers with 16MB flash), always partition the flash into 2 partitions so you can copy the working partition, then upgrade, and when you have issues like that you can switch to the other partition and have everything back untouched. No need to do downgrades, and when someone posts a workaround here you can switch back and try it.

Is there a nice tutorial to do that without screwed everything up ?

Thx :)

jbfavre · Sat Oct 09, 2021 7:55 pm

Hello,
I upgraded my CCR1009 yesterday… and lost my internet connection.
My SERCOMM FGS202 SFP Module isn't recognized anymore. Problem is, it's a quite widely used one in France since the main ISP Orange ships it with their Internet box.
When you have such a router (i.e. not one of the new home routers with 16MB flash), always partition the flash into 2 partitions so you can copy the working partition, then upgrade, and when you have issues like that you can switch to the other partition and have everything back untouched. No need to do downgrades, and when someone posts a workaround here you can switch back and try it.

Hello @pe1chl
Thanks for the answer. Indeed, I've been a bit lazy on this ;)
But, this is how I downgraded:

create new partition

copy the 6.49 version

activate the new partition

reboot to test it

downgrade routeros

It works !

That said, my question was more about the SFP module support which seems to have been dropped without any entry in releases notes.
And that worries me because this is the GPON provided by my Internet Access Provider.
Not having any support anymore for my SFP module will let me with no other solution than using my ISP box (😭) or find another router which supports it (😢)

Best,
Jean Baptiste

jbfavre · Sat Oct 09, 2021 8:05 pm

When you have such a router (i.e. not one of the new home routers with 16MB flash), always partition the flash into 2 partitions so you can copy the working partition, then upgrade, and when you have issues like that you can switch to the other partition and have everything back untouched. No need to do downgrades, and when someone posts a workaround here you can switch back and try it.
Is there a nice tutorial to do that without screwed everything up ?

Thx :)

It's pretty straightforward after reading the documentation: https://wiki.mikrotik.com/wiki/Manual:Partitions

What I did:

Create a partition:
Code: Select all
```
/partitions repartition partitions=2
```
(⚠ your router will reboot)
After reboot, check that you have 2 partitions
Code: Select all
```
/partitions print
```
Name both partitions (main & backup for me, always better than part0 & part1)
Copy the active & running partition to the new one:
Code: Select all
```
/partitions copy-to xxx
```
Do whatever you want/need on main (if something got wrong this partition has default fallback to "next"

To change the active partition, use

/partitions activate xxx

After validating changes on one partition, do not forget to sync the other one ;)

/partitions save-config-to xxx

Before a RouterOS upgrade, stating you're running on main, backup your existing system & config:

/partitions copy-to backup

Then upgrade RouterOS. If anything goes wrong, you'll be able to switch to the other partition, either automatically thans to partition fallback, or manually activating the backup partition after upgrade reboot and doing another reboot.

Florian · Sat Oct 09, 2021 8:23 pm

Thx a lot :)

EDIT : wait, will I lose my current partition / config when I do the repartition command ?

pe1chl · Sat Oct 09, 2021 9:28 pm

No when you repartition to 2 partitions, the first one will contain what your entire flash contains now, and the second one will be empty.
Check that the current disk usage is (much) less than half of the total, and you will be safe.

Florian · Sat Oct 09, 2021 9:47 pm

No when you repartition to 2 partitions, the first one will contain what your entire flash contains now, and the second one will be empty.
Check that the current disk usage is (much) less than half of the total, and you will be safe.

Perfect, thx :)

forenuser · Sat Oct 09, 2021 11:04 pm

Is it just with my RB4011 but with v6.19 there ist no default bridge and port configuration after resetting. There was with 6.47x and 6.48x.

mducharme · Sun Oct 10, 2021 5:04 am

This might be a coincidence. But checking our SNMP log, we only see occasional -274° temp values on the two RB4011 updated to 6.49. Not on others still running 6.48.x.

Yes, I spoke to soon. I occasionally see this -274 temperature value from other devices, but it is only for a brief time when the sensor is not working for some reason. This indeed seems to be an additional issue in this release.

mducharme · Sun Oct 10, 2021 5:05 am

Does anyone know what has changed in 6.49 that would stop Rancid from connecting and taking a backup? Initially I thought it was to do with expired user account but have worked through all that and mtlogin can get in but rancid-run fails to pull the config.

My coworker who uses RANCID is having the same issue in this version. I did a web search and found that people have this issue with 7.1rc3 and rc4 as well.

jimmer · Sun Oct 10, 2021 5:07 am

Is there a nice tutorial to do that without screwed everything up ?

Thx :)
It's pretty straightforward after reading the documentation: https://wiki.mikrotik.com/wiki/Manual:Partitions

I successfully did this on my RB3011 today following your instructions, it looks like the Mikrotik wiki is out of date as it doesnt state that it supports ARM architectures as featured in the RB3011.. However my RB3011 repartitioned perfectly fine into a pair of 64Mb partitions with ~50% free space on each.

Kind Regards,
Jim.

BrateloSlava · Sun Oct 10, 2021 1:16 pm

I have 5 devices RB2011. On the previous stable 6.48.4, they all displayed temperature and voltage correctly.
After update:

RB2011UiAS.png

RB2011UiAS-.png

RB2011UiAS-2HnD.png

And 3 4011 have no problem

4011-3.png

4011-2.png

4011-1.png

squeezypiano · Sun Oct 10, 2021 1:23 pm

My coworker who uses RANCID is having the same issue in this version. I did a web search and found that people have this issue with 7.1rc3 and rc4 as well.

Thanks. Tried 7.1rc4 and found the same too. Still can’t figure out why (rancid account with full permissions etc.) If you figure anything, please let me know. Going back to 6.48 for now.

kibitzer · Sun Oct 10, 2021 1:47 pm

I can confirm the rancid problem. Rancid is able to login but unable to parse the console output, something seems to have changed.

East2 · Sun Oct 10, 2021 2:09 pm

Screenshot (641).png

Same too.

fedorovic · Sun Oct 10, 2021 5:37 pm

The problem with rebooting is connected with Queues. Spent 7 hours with that! :-( Simple rules are broken and causing problems. Tested on CCR1036 r1.

Guscht · Mon Oct 11, 2021 12:25 am

The problem with rebooting is connected with Queues. Spent 7 hours with that! :-( Simple rules are broken and causing problems. Tested on CCR1036 r1.

Does this refer to "my" problem with the long reboot sequence?
My next step for the coming week was to do a full reset and then - step by step - load my config to see which part causes the issue.

If this is related to my described problem, please write to support@mikrotik.com
I have opened a ticket for this issue, you can refer to my case-ID: SUP-62573.

EDIT: I can confirm, the issue gets better if I remove all Simple Queues. The deletion of all queues took around 10 minutes!
The follwing reboot with around 2 minutes slightly longer than normal (1:30 minutes with V6.48.4 and older versions).

THANKS fedorovic FOR YOUR 7 HOURS!!

Note · Mon Oct 11, 2021 10:47 am

Is there any way to bypass the new "change password popup" screen at login? The problem is that opening also terminal asks u to change password. I do not use-need password so i wanna vanish those reminders.

Mandroid76 · Mon Oct 11, 2021 10:51 am

hAP AC2 fully updated without any problems
Constant reboot after RouterBoard Upgrade on two SXT SA5. RouterOS upgraded without any trouble

pe1chl · Mon Oct 11, 2021 10:57 am

I do not use-need password so i wanna vanish those reminders.

I hope that is on an isolated lab testing network.
Because even when you are using a proper firewall so the router is only accessible from inside, or even from your own computer, you still need a password when you use that computer to browse the internet!
There are several tricks that potentially allow webpages to access your router from your browser when you visit them, and without a password they could immediately modify some settings!

mkamenjak · Mon Oct 11, 2021 11:27 am

Is there a way to increase the password expiry time or remove this check completely?

pe1chl · Mon Oct 11, 2021 11:36 am

Is there a way to increase the password expiry time or remove this check completely?

There is no password expiry time. The expiration is done manually (using a command or script).
The initial setting after a full reset (blank password) is considered an "expired password" so you have to set a password one time.

prislonsky · Mon Oct 11, 2021 12:09 pm

6.49 and 7.1RC4 - there is no protected bootloader setting in the "System-RouterBOARD-Settings" section of Winbox

Note · Mon Oct 11, 2021 12:14 pm

So is there anyway to remove those fucin password reminders or not? Mikrotik wtf is this? R u a kind of sadist? If i want a password i know the way to change it or set it. Plz remove that shiit.

Mon Oct 11, 2021 12:23 pm

This only applies to a device with no password at all. In the light of recent attacks against MikroTik devises, why not simply set any kind of password? It will stop asking

Smoerrebroed · Mon Oct 11, 2021 1:20 pm

*) wireless - improve regulatory compliance with DFS requirements;
*) wireless - improve signaling of QCA9984 interface capabilities when using 160/80+80MHz channel width;

Where can I find more detailed information about these two items?

HTdeagle · Mon Oct 11, 2021 4:08 pm

Hello,

I upgraded 3 RB 4xx series, and after update firmware they don`t back. I think that you have problem with 4xx series and firmware upgrade. 6.48.4 was OK. I upgrade: RB493Ah, RB411AH, RB433AH. If i remember previous version was 6.37

CZFan · Mon Oct 11, 2021 4:43 pm

...If i remember previous version was 6.37

That is a "massive" jump between versions, I suspect there might be config problems on your side

HTdeagle · Mon Oct 11, 2021 5:10 pm

...If i remember previous version was 6.37

That is a "massive" jump between versions, I suspect there might be config problems on your side

Now i upgraded RB411U from 6.40 to 6.48.4 to 6.49. First upgrade was perfect, second upgrade to 6.49 and RB stop working, when i was upgrade firmware. There is a problem when upgrade only "system-routerboard-firmware".

Mon Oct 11, 2021 5:11 pm

https://mikrotik.com/download/changelog ... af72e8eef6

nithinkumar2000 · Mon Oct 11, 2021 5:48 pm

*) winbox - fixed support for "Delegated-IPv6-Prefix" for PPP services;
What exactly was fixed here?

Same Question from My side...

Why Mikrotik Team is not responding to anything related to IPv6.... Are they themself not clear about it???

Note · Mon Oct 11, 2021 7:03 pm

This only applies to a device with no password at all. In the light of recent attacks against MikroTik devises, why not simply set any kind of password? It will stop asking

Yes i know that, but for my setup that i cant explain now, i do not want to use passwords. The problem is that i cant use terminal without setting up a password and not so much the annoying popup. I need the old option for that plz so i can work without everytime need to set password. This is bullying......

andrey0001 · Tue Oct 12, 2021 1:04 am

Hi,

Does anyone know what has changed in 6.49 that would stop Rancid from connecting and taking a backup? Initially I thought it was to do with expired user account but have worked through all that and mtlogin can get in but rancid-run fails to pull the config.

Thanks.

I confirm , 6.49 and 7.x doesn't work rancid-run.
the error is:
------------
rancid@umac:~$ bin/mtrancid -d 192.168.72.5
executing mtlogin -t 90 -c"system package print detail without-paging;system routerboard print;system license print;export" 192.168.72.5
192.168.72.5: missed cmd(s): all commands
192.168.72.5: End of run not found
192.168.72.5: clean_run is false
192.168.72.5: found_end is false
------------

Rancid can't determine the end of output

I am back to long-term 6.48.5

---------------
rancid@umac:~$ bin/mtrancid -d 192.168.72.1
executing mtlogin -t 90 -c"system package print detail without-paging;system routerboard print;system license print;export" 192.168.72.1
PROMPT MATCH: ] >
HIT COMMAND:[rancid@192.168.72.1] > system package print detail without-paging
In SystemPackagePrintDetail: [rancid@192.168.72.1] > system package print detail without-paging
HIT COMMAND:[rancid@192.168.72.1] > system routerboard print
In SystemRouterboardPrint: [rancid@192.168.72.1] > system routerboard print
HIT COMMAND:[rancid@192.168.72.1] > system license print
In SystemLicensePrint: [rancid@192.168.72.1] > system license print
HIT COMMAND:[rancid@192.168.72.1] > export
In Export: [rancid@192.168.72.1] > export
--------------
and it works perfect on 6.48.5

wtechlink · Tue Oct 12, 2021 1:34 am

Did further investigation regarding the long-boot issue.

ROS 6.48.4 + Firmware 6.48.4 -> no issue -> booting takes around 1:30 minutes
ROS 6.49 + Firmware 6.48.4 -> no issue -> booting takes around 1:30 minutes
ROS 6.49 + Firmware 6.49 -> issue -> booting takes around 10 minutes!

I have done now a few down/upgrades, always with the same effect.
The shutdown sequence will durate about 8:15 minutes. The following boot is as fast as normal in about 1:30 minutes.

This issue is reproducible on all our CCR1072 and CCR1036 devices. Not reproducible on our CRS and RB devices.

I saw the same issue with my 1072 and came here to see. Going to downgrade until the next version I guess...Thanks for doing the testing for us!

osc86 · Tue Oct 12, 2021 2:05 am

I have a dual-partition setup on my CCR1009. Part0 is used for known-stable versions, Part1 for testing. Part1 was active and had 6.49rc2 installed. The upgrade to 6.49 went ok, but after the second boot when RouterBoot was upgraded it didn't come back online and was stuck in a reboot loop. Tried everything, cut the power for a few minutes, rebooted endless times, nothing helped, I had to reset the config. After restoring the auto-created backup everything was ok again, Router booted into 6.49 without any problems, no netinstall required. So either there's something really wrong with RouterBoot in this Version or the file system used is just shit and files get somehow corrupted.

redskilldough · Tue Oct 12, 2021 5:23 am

*) dns - fixed memory leak caused by large DNS replies;
Yes, the memory leak appears to be fixed, the resolver now returns the large replies OK, but they still aren't loaded into an address list :-(

Still not fixed on my rb951G-2hnd. Have to turn off 'Verify DOH Certificate'

pe1chl · Tue Oct 12, 2021 11:35 am

Yes, the memory leak appears to be fixed, the resolver now returns the large replies OK, but they still aren't loaded into an address list :-(
Still not fixed on my rb951G-2hnd. Have to turn off 'Verify DOH Certificate'

The issue I reported and was fixed was not related to DoH. Maybe there are still issues in that.

Guscht · Tue Oct 12, 2021 1:59 pm

I saw the same issue with my 1072 and came here to see. Going to downgrade until the next version I guess...Thanks for doing the testing for us!

Thanks for reporting! I hope Mikrotik will react, if more user will report this problem.
User fedorovic spend 7 hours to isolate the problem and he found, it is somehow connected to Simple Queues.

I did a downgrade to V6.48.4 too.
I always have the hope that a version-step (6.47 -> 6.48 -> 6.49) will cause no issues, but they disappoint me always...

mkamenjak · Tue Oct 12, 2021 2:07 pm

This only applies to a device with no password at all. In the light of recent attacks against MikroTik devises, why not simply set any kind of password? It will stop asking

Oh, ok, that is fine.

spiritamokk · Tue Oct 12, 2021 7:03 pm

Anyone have IP-IP tunnel + IPSec problem?
After morning update, between my CCR1036 and RB2011 stopped tunneled traffic if tunnel IPSec encrypted.
Nothing other changed on this routers.

I'm running GRE+IPSec behind the NAT on both sides with between MikroTIK devices of a different models. IKE1 with MAIN exchange mode. All my 40 tunnels broke overnight after automated installation of long-term 6.48.5. It seems that initially IPsec tunnels establish just fine, but hang on the next Phase1 (1 day in my case) . The only temporary fix for me now is to manually clear all tunnels once a day which is a pain in my arse. I can't figure out what to do and how to reconfigure it =(

AntoineS · Wed Oct 13, 2021 12:40 am

I upgraded my CCR1009 yesterday… and lost my internet connection.
My SERCOMM FGS202 SFP Module isn't recognized anymore. Problem is, it's a quite widely used one in France since the main ISP Orange ships it with their Internet box.

Hi,
This is quite strange. I have experienced this bug for more than a year since v6.47 with the same SFP (SERCOMM FGS202) and my RB3011. This release (v6.49) is the first one that make my SFP work.
On my side I am very happy with this release which has allowed me to upgrade from v6.46.6 since it was the last working version for the SFP.
Antoine

SteveG · Wed Oct 13, 2021 11:47 am

This only applies to a device with no password at all. In the light of recent attacks against MikroTik devises, why not simply set any kind of password? It will stop asking

@Normis, So in a big installation where we install 160+ devices that are configured script bassed from the main after reset and upgrades, it will ask for password. This is supid and require us to do extra steps.

from security view i understand, but not from mass config view.

If you ask this via winbox or webfig, i can live with that.
But not from mac telnet.

this is rubbish

Please reconsider

pe1chl · Wed Oct 13, 2021 12:50 pm

Can't you change your script to set a password instead? That is usually easy to do with tools like "expect".

mrz · Wed Oct 13, 2021 12:51 pm

What exact difficulties you are expecting to have? Password is asked only for interactive connections, so it really depends on how your "script-based" configuration is executed. And even if it uses interactive mode, it is still one line of code to ignore password prompt.

infabo · Wed Oct 13, 2021 1:41 pm

super secure.

"you need to set a password"
"nope. *click skip*"
"ok thanks. ask you next time again"

anuser · Wed Oct 13, 2021 2:25 pm

Upgrade from 6.48.4 to 6.49 => Clients do not get IP address via DHCP over the EoIP tunnel
Downgrade to 6.48.5 => Clients do not get IP address via DHCP over the EoIP tunnel
Downgrade to 6.48.4 => Clients receive an IP address again.

jbfavre · Wed Oct 13, 2021 2:51 pm

I upgraded my CCR1009 yesterday… and lost my internet connection.
My SERCOMM FGS202 SFP Module isn't recognized anymore. Problem is, it's a quite widely used one in France since the main ISP Orange ships it with their Internet box.
Hi,
This is quite strange. I have experienced this bug for more than a year since v6.47 with the same SFP (SERCOMM FGS202) and my RB3011. This release (v6.49) is the first one that make my SFP work.
On my side I am very happy with this release which has allowed me to upgrade from v6.46.6 since it was the last working version for the SFP.
Antoine

Hi,
Thanks for the update.
Maybe it's due to some difference between CR1009 and RB3011.

Out of curiosity, do you any specific specific sfp-rate-select settings for your FGS202 interface ?

pe1chl · Wed Oct 13, 2021 2:56 pm

Upgrade from 6.48.4 to 6.49 => Clients do not get IP address via DHCP over the EoIP tunnel

Are you running CHR on a virtualization environment? Or is it a physical router?
I had such issues and it was due to permission settings in the virtualization (allow promiscuous mode, allow MAC spoofing, etc)

BrateloSlava · Wed Oct 13, 2021 8:01 pm

I decided to experiment and created several rules for the indicators. How can I delete them now?
From GUI - not work, from command line - not work.

andkar · Wed Oct 13, 2021 8:18 pm

RB3011UiAS v.6.49

Missing after upgrade from 6.48.4:
write-sect-since-reboot
write-sect-total
bad-blocks

Edit

After some googling I'm realizing that RB3011 might not provide disk wear statistics (I was pretty shure I that I had seen it though).

DarkNate · Wed Oct 13, 2021 9:33 pm

What exactly was removed?

In the default config there is an address list bad_ipv6 that contained some addresses that were actually subnets of another one. These were removed.

Can you share the overlapping subnets that were removed?

DarkNate · Wed Oct 13, 2021 9:35 pm

What exactly was fixed here?
Same Question from My side...

Why Mikrotik Team is not responding to anything related to IPv6.... Are they themself not clear about it???

It's been years and even on RouterOS v7, IPv6 support is lacking, no NAT64, no PCP etc.

Although I'd advise you to migrate from PPPoE (which has overhead anyways) to DHCP with option 82 (for security).

anuser · Wed Oct 13, 2021 10:41 pm

Upgrade from 6.48.4 to 6.49 => Clients do not get IP address via DHCP over the EoIP tunnel
Are you running CHR on a virtualization environment? Or is it a physical router?
I had such issues and it was due to permission settings in the virtualization (allow promiscuous mode, allow MAC spoofing, etc)

RB750GR3 on both sites.

pe1chl · Thu Oct 14, 2021 10:49 am

It looks like rancid is using a telnet or ssh session to talk to the command interpreter intended for humans.
That is not a wise thing to do. It is better to write a client that uses API. That could take the place of that mtlogin program and extract the information in a much more repeatable way (and make it much easier to parse as well).
When this is not done, you are at the mercy of the control character processing and it looks like in this case the Hotlock mode (used to be Ctrl-V, this has changed, but unfortunately MikroTik have not updated the documentation) has been inadvertently enabled.
That means that all commands auto-complete when they are unique, instead of requiring TAB for that.

From the sequences above I guess that the login to the router is not using any of the options that are available to keep the console UI as simple as possible.
When logging in from software like this, you should append options to the username, see https://wiki.mikrotik.com/wiki/Manual:C ... in_process
At least you can try to login using admin+cte (or whatever_username+cte) to suppress the cursor control and color stuff.
However that does not disable hotlock mode, unfortunately. And as it is a toggle, you never know if it is enabled or not.
Of course there should have been an option to turn it off or it should be always off in dumb mode.

But it remains a sub-optimal solution relative to using API, please use that.

eddieb · Thu Oct 14, 2021 12:07 pm

Just upgraded a bunch of devices from 6.48.4 to 6.49

on my CRS125 I lost temperature from system health ... (and so on snmp ...)
created a support ticket #[SUP-63119] on this

deadkat · Thu Oct 14, 2021 4:43 pm

6.49 and 7.1RC4 - there is no protected bootloader setting in the "System-RouterBOARD-Settings" section of Winbox

noted here viewtopic.php?p=881501#p881511
The option is still available in CLI.

rpingar · Thu Oct 14, 2021 4:44 pm

ccr2004 configured as PPPoE Concentrator ipv4&ipv6 with hundreds of vlan with pppoe server over them crashes as soon as the users are authenticated by radius.
opened a ticket SUP-63086
autogenerated supout seems corrupted-

Any other experience about it with CCR2004???

regards
Ros

deadkat · Thu Oct 14, 2021 4:49 pm

Hey Mikrotik,
When I looked on some threads, you make very basic bugs in every new firmware...Is this normal programming? Because when I buy some crap Asus, TP-Link...it has more stable firmware, than this...
In my view you don't understand, what you programming or what is some function for...Because if you know it, there will be less bugs in new firmware. Maybe will be better do less function, but stable than many features, but buggy and useless..Testing longer and than make publication like new firmware to people. Because it is not beta and some ISP have hard time, for repair it, or the internet wan't function correctly and the people are angry! And why..because ISP want to have newer FW and not so buggy. So make some new jobs for people, programming some AI for learning how to make work some router correctly and the AI will corect some code in your FW. Because the AI will be testing more functions, than human, if you don't have some time to testing it. This is not funny for me, as a costumer. Because when I setup some function and the setup not working, it's hard for me, because I don't know, if I make some mistake, or it's only bugs in your firmware. Thank you for understanding.

Every post you make is always nothing but general complaints. no specific problems mentioned.

you said here that viewtopic.php?p=884907#p884857

Yes, but when I don't need all this functions, so [TPlink, Asus, etc] is ok for me.

nobody can help you except to offer some cheese and crackers with your wine.... if normal consumer brands are ok for you, as you mentioned, then stop complaining and go get something that works for you. Mikrotik devices are not easy, nobody says they are. but they are far more powerful and flexible than any other piece of networking equipment I've ever used...including Openwrt or DDwrt

winap · Thu Oct 14, 2021 5:45 pm

deadkat
Yes..It's only complaints..Why? Because I only see here, so the normal function didn't work!!!! Are you blind man?
What I see here? bricked router, wifi...not function this and there..
I wrote to support on mikrotik, so I had problems with loggin to device and you thing, so they can help me? No..
As I had cheap router, it never happend so the router was bricked after FW update!!
Yes, I am new here, but when I buy something not so cheap, I want also working things..And logic said, so newer version must be better, because they MUST repair those things, which is not working in previous versions...It is like life..If I make some bad thing, I must to learn, how to make it better in future..!
I bought RB5009..and when I turn on, sometimes it restart and reset to defaults..And this I wrote to support, and any help!!..Now, I have it on my desk and wait, for better FW..
So is this funny, when you upgrade to newer version, and you have more bugs, or bricked routerboard and you don't made any mistake? When I make in job this things every week, or month, I will be fired from work...But mikrotik is still cool and good, because fans are happy and blind. Because it has a lot of options, but not functions. Haha

edit1:Why I writing it? Also critics here are needed, so I hope, some people from Mikrotik read this post, and make better firmware in future. If they make new FW, they will be testing longer time and than release to the world...They made long therm and it has more bugs, than previous version... Haha also funny, no?
edit2: Now I have Zyxel and Netgear router and works ok. Previous routers was 2x Asus and they was also great. But Netgear is from weaker brand, yes.
Mikrotik is for backup now. Why I am angry? because I want more from life..I must more offer to people, make good work, so I hope, they will also work great for me, like FW. Lazy people don't offer good things...Because they don't live by soul, they do it only because money, the work must enjoy it!

infabo · Thu Oct 14, 2021 6:15 pm

Relax, you are in the wrong topic. RB5009 is v7 only and here is 6.49 topic. ROFL

winap · Thu Oct 14, 2021 6:44 pm

Relax, you are in the wrong topic. RB5009 is v7 only and here is 6.49 topic. ROFL

Hello,
I know, but I only respond on buggy FW....Sorry for it , have a nice day.

infabo · Thu Oct 14, 2021 7:09 pm

I feel with you. I have Chateau which is v7 only too.

AntoineS · Fri Oct 15, 2021 12:38 am

Out of curiosity, do you any specific specific sfp-rate-select settings for your FGS202 interface ?

sfp-rate-select=high

eddieb · Fri Oct 15, 2021 12:28 pm

Just upgraded a bunch of devices from 6.48.4 to 6.49

on my CRS125 I lost temperature from system health ... (and so on snmp ...)
created a support ticket #[SUP-63119] on this

I just got an answer from support with a fix. Works fine.
I guess this will be released soon.

great work MT,
thanks

rushlife · Fri Oct 15, 2021 3:35 pm

+1 for -274°C temperature

jbfavre · Fri Oct 15, 2021 6:23 pm

Out of curiosity, do you any specific specific sfp-rate-select settings for your FGS202 interface ?
Code: Select all
sfp-rate-select=high

Hello,
Thanks for the update.
I got an answer from Mikrotik support suggesting to change sfp-rate-select setting.
And actually,

/interface ethernet set sfp1 sfp-rate-select=low

solved the issue.
The SERCOMM FGS202 is now well detected and functional on my CCR1009.

winap · Sun Oct 17, 2021 11:29 am

jbfavre:
What is the difference please? SFP rate.low/high..Is it type of bitrate, or frequency on input SFP? And the rate is on every brand different?
Thanks

r00t · Sun Oct 17, 2021 7:02 pm

SFP rate low/hi is state on a specific SFP slot pin. Actual function depends on specific SFP module model and should be noted in a documentation/datasheet. There is no standardized meaning what low and high mean, that's up to the SFP manufacturer to define.

winap · Sun Oct 17, 2021 11:00 pm

SFP rate low/hi is state on a specific SFP slot pin. Actual function depends on specific SFP module model and should be noted in a documentation/datasheet. There is no standardized meaning what low and high mean, that's up to the SFP manufacturer to define.

Thank you.
So If I don't know, how to setup it, what is better setup? Or default rate is? The bad setup only don't work, or function is ok, but sometimes with troubles..?

ofca · Mon Oct 18, 2021 11:15 am

is it me or is 6.49 firmware update bricking RB2011? (etherboot required)

soabbd · Mon Oct 18, 2021 3:30 pm

After upgrading having problem with route table previously i was able to view full route table by clicking on show them all or i can filter dynamic only or static only etc now this options are gone. See image attachments below

ofca · Tue Oct 19, 2021 3:22 am

I updated two Mikrotik 2011UiAS models. The first reboot was fine, but neither have come back from the firmware update reboot. They're off-site, so I haven't had a chance to discover what state they're in.

OK then. PSA:

___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___
___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___
___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___

You will have to get physical with the device if you do this.

tongjinooi · Tue Oct 19, 2021 5:01 am

I had the same happening. But only on 6.49 with IPv6 enabled. No issue with only 6.49 without IPV6.
Had to reset2 and netinstall.

tongjinooi · Tue Oct 19, 2021 5:14 am

Which means u have to open the router and short the reset2 button with a screwdriver . The reset1 button does nothing

roe1974 · Tue Oct 19, 2021 5:04 pm

system/health on a ltAP is still empty ;-)

jbfavre · Wed Oct 20, 2021 6:46 pm

SFP rate low/hi is state on a specific SFP slot pin. Actual function depends on specific SFP module model and should be noted in a documentation/datasheet. There is no standardized meaning what low and high mean, that's up to the SFP manufacturer to define.
Thank you.
So If I don't know, how to setup it, what is better setup? Or default rate is? The bad setup only don't work, or function is ok, but sometimes with troubles..?

Hello,
I've currently no idea of what sfp-rate-select does exactly (except that it uses a different pin on the module, whatever it could mean).
I've asked Mikrotik support for precisions.

About the "best" setting to use, my answer would be: if it works, keep current setting. If not, meaning if your SFP isn't recognized and/or unstable, try to change from high (default value) to low.
What I can tell however is that it has no visible impact on performances.

Best,
Jean Baptiste Favre

winap · Wed Oct 20, 2021 7:59 pm

Hello,
I've currently no idea of what sfp-rate-select does exactly (except that it uses a different pin on the module, whatever it could mean).
I've asked Mikrotik support for precisions.

About the "best" setting to use, my answer would be: if it works, keep current setting. If not, meaning if your SFP isn't recognized and/or unstable, try to change from high (default value) to low.
What I can tell however is that it has no visible impact on performances.

Best,
Jean Baptiste Favre

Hello, thank you so much, for explanation and for your time :)

TracesOfNut · Thu Oct 21, 2021 6:27 am

Hi,

I just upgraded a 922UAGS-5HPacD to 6.49. The package update went ok and it restarted. When I updated the RouterBoard to 6.49 and reset, it never came back.

The POE status for the port it is connected to shows it is restarting every 5 or so seconds. When it is powering up and the ethernet port is 'up', the cable test shows no problems.

Power supply isn't a problem, it is connected to 24V of large batteries that are fully charged and the solar panels are currently supplying about 3 amps. The router powering it (RB960PG) is showing 23.0V

Justin.

anuser · Thu Oct 21, 2021 5:42 pm

cAP ac with v6.49. Macbook Pro with macOS Big Sur 11.3 disconnects after 60 minutes (repeatable) while other devices stay connected (and needs some minutes to connect again) => Group Key Update is set to 60 minutes.

vili11 · Thu Oct 21, 2021 8:11 pm

I think I'm going to stick with the long-term channel from now on...

It looks like rancid is using a telnet or ssh session to talk to the command interpreter intended for humans.
That is not a wise thing to do. It is better to write a client that uses API. That could take the place of that mtlogin program and extract the information in a much more repeatable way (and make it much easier to parse as well).

That sounds great, but we don't have time to program something new at the drop of a hat, with zero warning that a long-running solution will just stop working.

When this is not done, you are at the mercy of the control character processing and it looks like in this case the Hotlock mode (used to be Ctrl-V, this has changed, but unfortunately MikroTik have not updated the documentation) has been inadvertently enabled.

I would have hoped the changelog commented on this change AND the documentation saw updates.

From the sequences above I guess that the login to the router is not using any of the options that are available to keep the console UI as simple as possible.
When logging in from software like this, you should append options to the username, see https://wiki.mikrotik.com/wiki/Manual:C ... in_process
At least you can try to login using admin+cte (or whatever_username+cte) to suppress the cursor control and color stuff.
However that does not disable hotlock mode, unfortunately. And as it is a toggle, you never know if it is enabled or not.
Of course there should have been an option to turn it off or it should be always off in dumb mode.

Even in an export verbose there's no default parameter for hotlock in any conditions, which is far from unreasonable to request if they're going to change the default. But thankfully dumb mode seems to work around the problem. If anyone is stuck with this, modify your cloginrc file to include +cte in the user. This is what works for me:

add method host ssh
add user host admin+cte
add password host password

But it remains a sub-optimal solution relative to using API, please use that.

Not always practical, and even if people have something like that in development they probably need their configs backed up in the interim.

vili11 · Thu Oct 21, 2021 8:14 pm

I updated two Mikrotik 2011UiAS models. The first reboot was fine, but neither have come back from the firmware update reboot. They're off-site, so I haven't had a chance to discover what state they're in.
OK then. PSA:

___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___
___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___
___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___

You will have to get physical with the device if you do this.

It seemed to work for me...

> system router print
       routerboard: yes
             model: 2011UiAS-2HnD
     serial-number: <redacted>
     firmware-type: ar9344
  factory-firmware: 3.33
  current-firmware: 6.49
  upgrade-firmware: 6.49

ofca · Fri Oct 22, 2021 4:38 am

OK then. PSA:

___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___
___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___
___DO NOT UNDER ANY CIRCUMSTANCES UPGRADE FIRMWARE ON RB2011 TO 6.49___

You will have to get physical with the device if you do this.

It seemed to work for me...
Code: Select all
> system router print
       routerboard: yes
             model: 2011UiAS-2HnD
     serial-number: <redacted>
     firmware-type: ar9344
  factory-firmware: 3.33
  current-firmware: 6.49
  upgrade-firmware: 6.49

Well, roll the dice few more times then. I had 100% "success" ratio on my 2 attempts. Few others above were also "lucky". ;)
btw. this seems to be a problem with whole MIPSBE range, not only RB2011 judging by more "success stories" above.

asimko · Sat Oct 23, 2021 4:07 pm

Do no upgrade any older SXT, already almost 10 upgraded devices after reboot not accessible, have to do netinstall on all of them!
Also a CRS125-24G-1S-IN the same problem = but here after routerboard upgrade, after reboot router not accessible, now in serial console I have "check ethernet cable" so I cannot do neinstall, still figuring out how to make it workable...

jirinovak · Sun Oct 24, 2021 10:06 am

In the morning I upgraded 200 sxts from 6.48.4 also fw 6.48.4 to 6.49 with fw and without any problem

anav · Mon Oct 25, 2021 9:42 pm

I gather they were on UPSs tha eventually stopped as well. One can get UPS warnings from MT router setups but havent done that yet. IT may help in teh future to gracefully shut down boards in the future...............

ofca · Tue Oct 26, 2021 7:54 am

In the morning I upgraded 200 sxts from 6.48.4 also fw 6.48.4 to 6.49 with fw and without any problem

You did do a second reboot after upgrading firmware to 6.49, right?

osc86 · Tue Oct 26, 2021 11:09 am

It may be a good idea to turn off auto-upgrade until this mystery has been solved.

Tue Oct 26, 2021 12:20 pm

It may be a good idea to turn off auto-upgrade until this mystery has been solved.

For anything business-critical, it's always a good idea whatever equipment or supplier.
Just as with Windows Updates. No way these get rolled in without some weeks passing by.
Urgent security upgrades being the only exception.

Test environments, that's another thing.

suran · Wed Oct 27, 2021 1:09 am

Have had 3 of 3 RB2011 6.49 firmware upgrades result in bricks. Definitely something here.

mietusik · Wed Oct 27, 2021 11:45 am

Same problem, 130 devices on remote locations to fix with net install...
After upgrade to 6.49 or 6.48.5 do, a check installation (winbox) in system packages. If it says that installation is corrupted, you have a 100% chance to brick device after another reboot.
To avoid this, when installation is corrupted, downgrade it do 6.48.4, after that upgrade again to 6.48.5 or 6.49 and then Check installation will show You, that everything is OK. From now Next reboot are safe.

ofca · Wed Oct 27, 2021 11:53 am

Same problem, 130 devices on remote locations to fix with net install...
After upgrade to 6.49 or 6.48.5 do, a check installation (winbox) in system packages. If it says that installation is corrupted, you have a 100% chance to brick device after another reboot.
To avoid this, when installation is corrupted, downgrade it do 6.48.4, after that upgrade again to 6.48.5 or 6.49 and then Check installation will show You, that everything is OK. From now Next reboot are safe.

From my observations actually bricking the device requires firmware upgrade. But good catch with check-installation. I'll do some more experiments.

mietusik · Wed Oct 27, 2021 12:21 pm

Same problem, 130 devices on remote locations to fix with net install...
After upgrade to 6.49 or 6.48.5 do, a check installation (winbox) in system packages. If it says that installation is corrupted, you have a 100% chance to brick device after another reboot.
To avoid this, when installation is corrupted, downgrade it do 6.48.4, after that upgrade again to 6.48.5 or 6.49 and then Check installation will show You, that everything is OK. From now Next reboot are safe.
From my observations actually bricking the device requires firmware upgrade. But good catch with check-installation. I'll do some more experiments.

Upgrading firmware has nothing to do with it. I think that problem is with upgrade path between some old to new (latest) versions.

pe1chl · Wed Oct 27, 2021 3:55 pm

When a /export is made of a router that has a secondary BGP instance with the default AS number 65530 but some other setting, it is exported like this:

/routing bgp instance
set default as=12345 router-id=1.2.3.4
add name=bgp2 router-id=2.3.4.5

But when an export file with this info is imported into a router without config, the second line results in a prompt "as:" requesting an AS number.
Of course when 65530 is entered there it works OK.
I think it would be better when the AS number is always exported, even when it is the "default" value (65530).

jirinovak · Thu Oct 28, 2021 9:07 pm

In the morning I upgraded 200 sxts from 6.48.4 also fw 6.48.4 to 6.49 with fw and without any problem
You did do a second reboot after upgrading firmware to 6.49, right?

Fist reboot was after the ros upgrade and the second after firmware upgrade. I can see that 9 SXTs went down due to power outage and came back normally. So they survived third reboot.

pe1chl · Thu Oct 28, 2021 11:04 pm

Another export/import problem: I created a scanlist to limit the 2GHz WiFi to using channels 1, 6 and 11. As is best practice (would help if the router did that by default!).
I named the scanlist "1-6-11" (without the quotes). This exports as:

/interface wireless channels
add band=2ghz-b/g/n frequency=2412 list=1-6-11 name=ch1 width=20
add band=2ghz-b/g/n frequency=2437 list=1-6-11 name=ch6 width=20
add band=2ghz-b/g/n frequency=2462 list=1-6-11 name=ch11 width=20

which is fine, it imports OK.
But then when it is used in the wlan interface it exports as:

set [ find default-name=wlan2 ] ....
scan-list=1-6-11 ...

and this does not import correctly, it requires scan-list="1-6-11" to work correctly (note the quotes).

eworm · Thu Oct 28, 2021 11:57 pm

I reported the scan list issue to support years ago... Looks like nothing has changed since then.

ricky011 · Fri Oct 29, 2021 10:42 am

after upgrade to 6.49 on CCR1072, boot time went to +10 minutes, openvpn started dropping clients, and the whole router started slowing down... after downgrade ROS and FW to 6.48.5 everything went back to normal...

!!!! DO NOT UPGRADE TO 6.49.

pe1chl · Fri Oct 29, 2021 11:26 am

after upgrade to 6.49 on CCR1072, boot time went to +10 minutes

Do you have thousands of static DNS records in your router e.g. for some form of blacklist?

r00t · Fri Oct 29, 2021 3:48 pm

Firmware update over serial x-modem can ONLY be used to update bootloader and nothing else. It can only flash .fwf files.
To get older FWF file, download ROS .npk package that you know worked before, then unpack it with 7zip and look for tilegx-<version>.fwf in /etc.
This way you can revert back to older bootloader and then hopefully recover the device to older ROS version. If anything goes wrong, you can still revert to backup bootloader.

CyB3RMX · Fri Oct 29, 2021 10:11 pm

on a 3011.. i updated to 6.49 from 6.48.5 and the router booted fine, i did a /sys routerboard upgrade to upgrade firmware. and the router bricked..
I netinstall it on the 6.49 and started working fine for 4 days... today the traffic didnt go up than 10mbps on ether10 (WAN)... and i notice that the ISP CPE was on 100% CPU usage with 10mbps... y disconnected the router and plug a laptop, and hte laptop works fine...

So i downgraded, reset to factory, imported the backup RSC and downgrade the firmware to 6.48.5 and then started working as usual..

Im not sure what was causing this.. no errors, no more than 500pps, and 10mbps on the interface, but as soon i plugeed the 3011 on the ISP CPE the CPU on the CPE was rising to 100% and the ping between both was around 90ms-100ms ... since the downgrade it came back to <1ms
fyi..

Wublide · Fri Oct 29, 2021 11:43 pm

I had to downgrade back to 6.48.3 because the 6.49 broke my PPPOE connection

pe1chl · Sat Oct 30, 2021 12:13 am

I had to downgrade back to 6.48.3 because the 6.49 broke my PPPOE connection

On what model of router?

Wublide · Sat Oct 30, 2021 12:28 am

I had to downgrade back to 6.48.3 because the 6.49 broke my PPPOE connection
On what model of router?

RB4011iGS+5HacQ2HnD

I have a vlan on a phisical ethernet interface, and the pppoe interface is on top of that vlan interface. The pppoe remain on "connecting"

pe1chl · Sat Oct 30, 2021 10:39 am

Ok that is interesting! This config works for me (it connects), but I have other strange problems with it. And downgrading does not fix it.
BTW, on some networks it may help to turn the router (or the PPPoE interface) off for a couple of minutes and then try again.
Because of that, you may get confused when actions like downgrading fix it, but just turning the router off for some time might have fixed it as well.

Wublide · Sat Oct 30, 2021 11:17 am

Ok that is interesting! This config works for me (it connects), but I have other strange problems with it. And downgrading does not fix it.
BTW, on some networks it may help to turn the router (or the PPPoE interface) off for a couple of minutes and then try again.
Because of that, you may get confused when actions like downgrading fix it, but just turning the router off for some time might have fixed it as well.

The router was not powered off but resetted 2 times: once to 6.49 and once to 6.48.3, and it start to work again as soon as I downgraded to the 6.48.3
The only things that puzzles me is that I upgraded the packages instead of upgrading the firmware first, I don't know if the sequence matter. Anyway once the packages were upgraded and the router rebooted I saw that the firmware was uprgaded too

pe1chl · Sat Oct 30, 2021 11:21 am

The updating of firmware depends on the setting under system->routerboard->settings. I advise to keep that "auto upgrade" setting OFF and do the upgrade at your own convenience. That keeps you away from bricked devices due to unwanted firmware upgrades to broken versions.
Just rebooting the router may not take long enough to solve the issue with PPPoE setup I observe in our national carrier network. I advise to keep the router off for 5 minutes before concluding that the connection cannot be made.

Wublide · Sat Oct 30, 2021 11:30 am

The updating of firmware depends on the setting under system->routerboard->settings. I advise to keep that "auto upgrade" setting OFF and do the upgrade at your own convenience. That keeps you away from bricked devices due to unwanted firmware upgrades to broken versions.
Just rebooting the router may not take long enough to solve the issue with PPPoE setup I observe in our national carrier network. I advise to keep the router off for 5 minutes before concluding that the connection cannot be made.

auto upgrade is disabled. As soon as I can do maintenance again I'll try to do as you suggest, thank you
I just noticed that now in the system/routerboard menu i have
Current firmware: 6.49
Upgrade firmware: 6.48.3
and in system/packages all the packages are 6.48.3, is there something wrong?

pe1chl · Sat Oct 30, 2021 12:07 pm

No this means you upgraded the firmware from version 6.49 and not (yet) from 6.48.3 (or you did not yet reboot after that).

Wublide · Sat Oct 30, 2021 12:17 pm

No this means you upgraded the firmware from version 6.49 and not (yet) from 6.48.3 (or you did not yet reboot after that).

so now I'm on 6.49 (until reboot) with 6.48.3 packages? is that possible?

pe1chl · Sat Oct 30, 2021 12:55 pm

There is no need to update it every time nor to downgrade it now. The firmware is just the bootloader that initializes the hardware and loads RouterOS.
Originally it had a separate version number that changes only very occasionally, now it always has the same version number as the RouterOS it comes with, but usually there are no changes other than the version number. This time there appear to be changes (see the many troubles reported) but there is no changelog entry that describes a useful change in the firmware, so it would have been better not to upgrade it at all.

However, my RB4011 currently runs with RouterOS v6.49 and firmware v6.49 and I do not see the issues described above.
I also have a PPPoE connection over VLAN same as you describe (and with RFC4638 so 1500-byte MTU) and it works.

desertadmin · Sun Oct 31, 2021 7:55 am

FYI this version broke our network. 2-6% packet loss. Issue primarily if your pushing greater than 2 Gbps is where we saw this. At our lowest point of operation in a day we are still pushing greater than 2 Gbps. Various CPUs would be pegged on networking and firewall at 100% even though the overall CPU would be at 40% CPU on a CCR 1072. The total would show 11+ less on the CPU % which I thought was odd. Several trace routes got us to this point. We even had our fiber provider inspecting the fiber lines. If we ping the gateway then there was no loss, but if you pinged another subnet at the same gateway point then there would be a variable amount of packet loss. After a week straight analyzing everything I downgraded from stable v6.49 to Long term v6.48.5 . This corrected everything. I guess production people should never use stable. It feels like Beta is Alpha and Stable is Beta. Any ways. No other stories in the forums about this... But yes boot up with router and bridge configs will take 10 mins.

If you have packet loss down grade to the very stable Long Term ROS. Hope this helps other people out there. I do like Mikrotik Products but man stable is not fully stable. This has happened before with previous versions. But their product is very good. Just wanted to mention our woes. Hope they figure it out.

-Sincerely,
DesertAdmin

slarner · Mon Nov 01, 2021 6:15 pm

Thats the second device ive now upgreaded to 6.49 and its now a door stop.

RouterOS upgrade is fine. Its the routerboot firmware bit that screws it.

RB450Gx4

HAP AC

Come on guys!

pe1chl · Mon Nov 01, 2021 7:15 pm

RouterOS upgrade is fine. Its the routerboot firmware bit that screws it.

You could (and should) have skipped that...

desertadmin · Mon Nov 01, 2021 9:12 pm

Another note is that Powerbox Pro if they have auto power on some units stop detecting power and shut down. There seems to be an odd power upgrade issue that messes with the voltage passive detection on Firmware version 6.49 stable. Again I highly recommend going to Long Term for production devices especially if you have paying clients. This firm caused some issues. I do not meant to bash on Mikrotik just this one has some caveats that were not known.

-Sincerely,
DesertAdmin

mducharme · Mon Nov 01, 2021 11:45 pm

Somebody else had reported that it wasn't actually the routerboot firmware that did it, but simply the second reboot after the successful upgrade causes the issue even if you don't upgrade routerboot. I have no idea what is actually the case.

desertadmin · Tue Nov 02, 2021 12:11 am

Hmm that is interesting got some gear across a large are of Northern New Mexico USA. So hopefully that is just the case. Nonetheless I think I am to upgrade to Long Term. . But thank you for the re-mention of this issue.

Wublide · Tue Nov 02, 2021 2:53 am

There is no need to update it every time nor to downgrade it now. The firmware is just the bootloader that initializes the hardware and loads RouterOS.
Originally it had a separate version number that changes only very occasionally, now it always has the same version number as the RouterOS it comes with, but usually there are no changes other than the version number. This time there appear to be changes (see the many troubles reported) but there is no changelog entry that describes a useful change in the firmware, so it would have been better not to upgrade it at all.

However, my RB4011 currently runs with RouterOS v6.49 and firmware v6.49 and I do not see the issues described above.
I also have a PPPoE connection over VLAN same as you describe (and with RFC4638 so 1500-byte MTU) and it works.

Tried again in the maintenance window but keeping it shutted down as you suggested didn't work.
I updated from packages, tried before and after upgrading firmware too but the pppoe doesn't want to work in any combination given

one thing: the vlan interface is sitting on the sfp ethernet, maybe that could be one thing that differentiate my setup from yours and could be the source of the problem; the router shows no problem on the physical sfp plug though

amojak · Tue Nov 02, 2021 12:02 pm

hi,

Don't post often but a HEADS up for Mikrotik here.

We have had a collection of RB750 / RB951 based routers brick after upgrading to 6.49 Ros and Firmware.

The problem looks to be with the firmware side.

Usually they brick after a power cycle at some point after upgrade, we had one RB951 router brick as soon as the firmware was updated and the router rebooted. This was one we were fitting to replace a bricked router before we noticed the pattern, it had an older 6.3x firmware on it originally as it had been on the shelf a while.

This seems to be affecting Mipsbe hardware specifically.

Thank you

amojak · Tue Nov 02, 2021 12:21 pm

hi,

one other thing, how do i disable this potential time bomb, is there a way to cancel a firmware upgrade ?

Screenshot from 2021-11-02 10-19-31.png

thanks

infabo · Tue Nov 02, 2021 12:43 pm

Too late.

pe1chl · Tue Nov 02, 2021 2:00 pm

I updated the firmware on a hPA ac2 without issue. But your mileage may vary.

       routerboard: yes
        board-name: hAP ac^2
             model: RBD52G-5HacD2HnD
     serial-number: E5780DC.....
     firmware-type: ipq4000L
  factory-firmware: 6.45.9
  current-firmware: 6.49
  upgrade-firmware: 6.49

luminescentsimian · Tue Nov 02, 2021 7:58 pm

hi,

Don't post often but a HEADS up for Mikrotik here.

We have had a collection of RB750 / RB951 based routers brick after upgrading to 6.49 Ros and Firmware.

I came here looking for this. I recently pulled an RB750 out of storage to use temporarily. I updated the OS but not the firmware and it seemed fine until I did a /system reset-configuration. Now it's stuck in a boot loop, flashing all port LEDs every 10-20 seconds, and neither a 5-second config reset nor 10-second netinstall boot helps.

amojak · Wed Nov 03, 2021 1:13 am

hi,

Don't post often but a HEADS up for Mikrotik here.

We have had a collection of RB750 / RB951 based routers brick after upgrading to 6.49 Ros and Firmware.

I came here looking for this. I recently pulled an RB750 out of storage to use temporarily. I updated the OS but not the firmware and it seemed fine until I did a /system reset-configuration. Now it's stuck in a boot loop, flashing all port LEDs every 10-20 seconds, and neither a 5-second config reset nor 10-second netinstall boot helps.

Sadly we have been going around to customers to sort these router failures. Calling 6.49 Stable is a misnomer and shows a distinct lack of pre-release testing.

Just glad we don't have a centralised upgrade setup else we could of taken out 100's or even 1000's of devices.

If your RB750 is the non UP variant at least then it will get upset with various firmwares above 6.2, usually suffering a glue up after so many weeks online that only clears with a reboot.

Fortunately nearly all 750's are gone now, the ones that remain are running early firmware and not internet facing.

Bill

amojak · Wed Nov 03, 2021 1:16 am

I updated the firmware on a hPA ac2 without issue. But your mileage may vary.

       routerboard: yes
        board-name: hAP ac^2
             model: RBD52G-5HacD2HnD
     serial-number: E5780DC.....
     firmware-type: ipq4000L
  factory-firmware: 6.45.9
  current-firmware: 6.49
  upgrade-firmware: 6.49

Hi,

Thanks for this, i am hoping it is limited to the Mipsbe processor units. only just installed the AC2 i posted about to replace a bricked 951 and i didn't want the wrath of the customer again if it dies too!

I am hoping MT are working on this issue and have a fix soon, by soon i don't mean Apple timescales ether.

Bill

mducharme · Wed Nov 03, 2021 7:41 am

I have a bunch of routers that I am looking to upgrade to 6.49 but I'm very worried by these reports of issues, even though I haven't experienced any myself, so I am holding off just to be safe. I am hoping to see a 6.49.1 relatively soon that might fix this.

Hominidae · Wed Nov 03, 2021 12:11 pm

...as it seems, the same bug hits long-term as well and this is even more a nuisance viewtopic.php?t=179260

I only did upgrade my LHGG yet, fortunately without issues but will definitely stay away with my other gear - even from long-term upgrade

deadkat · Wed Nov 03, 2021 4:01 pm

I would like to say I successfully updated all of my devices last weekend (both ROS and bootloader/firmware) with absolutely no problems.

This includes an RB3011, a pair of LHG2, and pair of LHG5, an LHG R, a hap ac2, a hEX poe, a hEX poe lite, a RB922UAGS-5HPacD, a RB911G-5HPacD, two hAPs, and a CRS226-24G-2S+RM

VincentL · Wed Nov 03, 2021 4:35 pm

Hello,

We own and use a bunch of "still useful" rb600 (ppc, powerpc) for voip.
We 've tried to upgrade some of our testing board by the common way (through Winbox, package upgrade then firmware upgrade)
Everything goes fine until we reboot after firmware upgrade then, the board crash and are bricked (no beep, static green and blue led).

We were able to save them with NetInstall. With NetInstall, installing a running 6.49 (packages and firmware) is possible.
But we will not upgrade our remote board until this problem will be fixed.

Has anyone encountered and fixed this problem ?

Regards,

EDIT : I've just seen I not alone !

Vincent

onnoossendrijver · Wed Nov 03, 2021 6:16 pm

Me too. I would really like to get ROS 7 on the RB600 fixed. It has plenty of storage and RAM, and the CPU is still very capable.

matmor · Wed Nov 03, 2021 7:38 pm

Had problem on my side with all MIPSBE board ( Mostly RB751 and RB951 ) ... upgrade to 6.49 work ...
BUT don't try to reboot the device or have a power failure else you just have a doorstop you have to flash with NetInstall.

If you run " /system check-installation " on MIPSBE and get " damaged routeros-mipsbe ... upload routeros-mipsbe-6.48.4.npk on your device and do a DOWNGRADE

After the downgrade I have been able to upgrade back to 6.49 and this time it work correctly and a reboot / power outage don't brick the device anymore !

By chance all our new clients are deployed with ARM ( RB4011, CRS328, cAP AC and wAP AC ) network !

matmor · Wed Nov 03, 2021 7:47 pm

This seems to be affecting Mipsbe hardware specifically.

I can confirm !

eddieb · Wed Nov 03, 2021 8:54 pm

I upgraded a bunch of mipsbe devices to 6.49

- hAP AC (RouterBOARD 962UiGS-5HacT2HnT)
- CRS125 (CRS125-24G-1S)
- RB2011 (RB2011UAS)
- PWR-Line
upgrading firmware went fine ...

RB1100 (PowerPC)
hAP mini (RB931-2nD) (smips)
also went fine

waiting with my CCR1009 until there is more known about the reboot-delays ...

Lits33 · Thu Nov 04, 2021 12:07 pm

I've update a RB951Ui and when update the Routerboard it reboots constantly in 30 seconds and i can't acces remotely. Is it there a bug on its Routers with this firmware ?

matmor · Thu Nov 04, 2021 2:03 pm

I've update a RB951Ui and when update the Routerboard it reboots constantly in 30 seconds and i can't acces remotely. Is it there a bug on its Routers with this firmware ?

For the RB951Ui, it look like the update is done correctly, but the package get damaged ( /system check-installation ) and if you reboot the device or there is a power outage ( no need to update the RouterBoard Firmware ) it's done ... It will just reboot in loop and you will have to use NetInstall

Had problem on my side with all MIPSBE board ( Mostly RB751 and RB951 ) ... upgrade to 6.49 work ...
BUT don't try to reboot the device or have a power failure else you just have a doorstop you have to flash with NetInstall.

If you run " /system check-installation " on MIPSBE and get " damaged routeros-mipsbe ... upload routeros-mipsbe-6.48.4.npk on your device and do a DOWNGRADE

After the downgrade I have been able to upgrade back to 6.49 and this time it work correctly and a reboot / power outage don't brick the device anymore !

r00t · Thu Nov 04, 2021 3:03 pm

Me too. I would really like to get ROS 7 on the RB600 fixed. It has plenty of storage and RAM, and the CPU is still very capable.

Same here, got quite a few RB600 boards. I asked support about ROS 7 on RB600 and got following reply:

The device might be too old to use with v7. Please test with any other or use CHR.

I also have RB800 and that runs ROS 7 just fine, both are same architecture, so it can't be that hard to make it work... I guess we will see what happens.

But this is 6.49 thread, so enough of this off-topic ROS 7 mumbling...

onnoossendrijver · Thu Nov 04, 2021 6:13 pm

But this is 6.49 thread, so enough of this off-topic ROS 7 mumbling...

Oops.. sorry, I didn't see that. Sorry.
I didn't have any problems upgrading 6.48.? to 6.49 on my RB600A.

amojak · Thu Nov 04, 2021 6:45 pm

hi all,

Silence seems to be the response to this issue so far, Not sure how the firmware, if corrupt, is able to pass the checksums that are surely done before it is installed?

We have just finished visiting customers and replacing bricked routers, fortunately we had NOT updated any infrastructure kit.

It seems 6.49 and 6.48.5 and MipsBE architecture are the primary victims with some suggestion that PPC types are also hit?

So "release" and "long term" are broken possibly. Not a good look and things like this need achnowledging and addressing urgently as it has been a while since we suffered MT upgrade anxiety from when it used to be a common problem.

Bill

pe1chl · Thu Nov 04, 2021 6:50 pm

Well, in any case, and especially when equipment installed at customer locations is involved, you need to read the release topic of this forum before doing any upgrade.
No matter if it is called stable, .0 releases have usually experienced major problems in the past, and careful users have waited for the .1 or .2.

amojak · Thu Nov 04, 2021 7:04 pm

Well, in any case, and especially when equipment installed at customer locations is involved, you need to read the release topic of this forum before doing any upgrade.
No matter if it is called stable, .0 releases have usually experienced major problems in the past, and careful users have waited for the .1 or .2.

The Long term version is affected too, as i mentioned in a post, there should be a "known stable" channel that contains the last version without major problems and th elog for it needs to show what small issues have been found with it over time since release.

Aka a proper Long term version, not one that is updated when the 'stable' is, else it gains the risk of show stopping issues like this.

The ones we upgraded were due to ethernet port flapping issues that were causing VoIP problems in a long term version. undocumented of course.

ivugrinec · Thu Nov 04, 2021 7:43 pm

Is there anyone with long boot delay issue on CCR1036 (or any other Tile)? After flashing firmware 6.49 (RouterOS 6.49) we have very long boot time with our router.
Check installation is OK. Router boots but it takes about 8minutes or so. I am unable to test it with default config as this is my only device.
I have seen some of other forum users narrowed down the problem to 6.49 RouterBoard firmware AND SimpleQoS config. I've removed that config but long reboot issue is still present.
Mikrotik Support answered to try with NetInstall but i am unable to bring router offline and try NetInstall.

Rox169 · Fri Nov 05, 2021 9:29 am

Hi,

has anyone tried to instal it on w60g? Is it safe?

Fri Nov 05, 2021 10:10 am

The issue with unavailable devices after 2nd reboot has been reproduced and it seems to be related when upgrading from 6.41.4 (or older) RouterOS/RouterBOOT versions. Our apologies for the caused issues, the fix will be included in upcoming releases.

So anyone using older than 6.42 RouterOS or RouterBOOT versions, please first upgrade RouterOS and RouterBOOT to 6.48.4 or 6.47.10, and only then use the latest version.

eddieb · Fri Nov 05, 2021 11:36 am

I upgraded a bunch of mipsbe devices to 6.49

- hAP AC (RouterBOARD 962UiGS-5HacT2HnT)
- CRS125 (CRS125-24G-1S)
- RB2011 (RB2011UAS)
- PWR-Line
upgrading firmware went fine ...

RB1100 (PowerPC)
hAP mini (RB931-2nD) (smips)
also went fine

waiting with my CCR1009 until there is more known about the reboot-delays ...

Finally I upgraded the last devices without issues
- RB750GL (mipsbe)
- RB750Gr3 (mipsbe) running dude
- CCR1009-8G-1S (Tile) gateway running multiple ipsec tunnels
flashing took less than a minute including 1st reboot
2nd reboot within 15sec
no problems

amojak · Fri Nov 05, 2021 12:51 pm

The issue with unavailable devices after 2nd reboot has been reproduced and it seems to be related when upgrading from 6.41.4 (or older) RouterOS/RouterBOOT versions. Our apologies for the caused issues, the fix will be included in upcoming releases.

So anyone using older than 6.42 RouterOS or RouterBOOT versions, please first upgrade RouterOS and RouterBOOT to 6.48.4 or 6.47.10, and only then use the latest version.

As mentioned in the long term thread >

hi,

Do you have the ability to stop customers from upgrading the brick way? If not then withdrawing the release sounds a damn good idea as it is now over a month down the road.

Unless you can instruct distributors to accept free returns/swaps of bricked hardware for swap for the duration?

It is not a "caused issue", it is turning your hardware useless, this is more than just an issue.

Where are the warnings in CAPS on the update firmware notes as stage 1?

Screenshot from 2021-11-05 10-45-32.png

Screenshot from 2021-11-05 10-46-01.png

Speeding up your response to this maybe a good idea as i doubt your distributors/resellers will be happy with the returns and angry customers.

Thanks

Guscht · Fri Nov 05, 2021 4:02 pm

Is there anyone with long boot delay issue on CCR1036 (or any other Tile)? After flashing firmware 6.49 (RouterOS 6.49) we have very long boot time with our router.
Check installation is OK. Router boots but it takes about 8minutes or so.

Same here, all our CCR 1036 and 1072 (Tile) Routers are affected by this issue. If we remove all Simple-Queues, the router will boot faster but still slower than with 6.48... versions. From 10 minutes to 3 minutes... And the router will behave not normal, deleting a bridge (with Simple Queues present) will result in an "Timeout (13)" error.

We did a clean Netinstall and imported a backup -> same outcome.

We connected a serial cable, the long reboot duration is caused by shutting down a service ("Stopping Services"). The follwoing start is as fast as normal. I assume something runs into a timeout as by deleting a bridge ("Timeout (13)").

At the moment we downgraded to 6.48.5 (long-term), no issues here with our Tile-CCRs. To be honest, we simply dont have the time (working hours are money) to do endless research for the manufacturer, because they have a poor Software-Quality-Assurance...

Edit: Answer from MT regarding the long boot issue:

We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide an ETA now. Meanwhile please use 6.48.x.

My recommendation for the CCR/Tile-User: Stay away from 6.49 until the fix is out! 6.48.5 (long-term) is fine and the wrong voltage issue is fixed (for the SNMP-user).

zdiv · Sat Nov 06, 2021 12:27 am

The issue with unavailable devices after 2nd reboot has been reproduced and it seems to be related when upgrading from 6.41.4 (or older) RouterOS/RouterBOOT versions. Our apologies for the caused issues, the fix will be included in upcoming releases.

So anyone using older than 6.42 RouterOS or RouterBOOT versions, please first upgrade RouterOS and RouterBOOT to 6.48.4 or 6.47.10, and only then use the latest version.

upgraded RB2011 from 6.48.3 to 6.48.5 and after second reboot (firmware upgrade) it has gone in netboot mode.
same happened with attempt to upgrade from 6.48.3 to 6.49 at ccr1009
Tested than 911,hex, rb912, rb2011,rb4011,rb1100ahx4, etc.. and same has happened.

mducharme · Sat Nov 06, 2021 2:07 pm

upgraded RB2011 from 6.48.3 to 6.48.5 and after second reboot (firmware upgrade) it has gone in netboot mode.

Was it running firmware 6.48.3 before, or an older firmware? Above, MikroTik says that this happens if the device is running 6.41.4 or older before the upgrade, if it is running newer firmware it is supposedly fine.

mducharme · Sat Nov 06, 2021 3:37 pm

You could (and should) have skipped that...

Personally I disagree on this, I always do the RouterBOOT upgrades. MikroTik says the issue only appears here when the RouterBOOT upgrade is done from a very old version, 6.41.4 or older. We have upgraded quite a few devices successfully with no issues because we always did the RouterBOOT upgrades previously, and so all of the RouterBOOT firmware versions were new enough to not have this problem. But I am always really cautious with new RouterOS versions in general, and don't necessarily assume that they work properly or are safe to deploy. We always test them in our lab before doing an initial pilot deployment, then the final rollout.

pe1chl · Sat Nov 06, 2021 3:58 pm

You could (and should) have skipped that...
Personally I disagree on this, I always do the RouterBOOT upgrades. MikroTik says the issue only appears here when the RouterBOOT upgrade is done from a very old version, 6.41.4 or older.

Well, I wrote that in the context of the current issue, which was quite apparently caused by the RouterBOOT upgrade and not the RouterOS upgrade, and people not doing the RouterBOOT upgrade were not affected.
When I wrote that, it was not yet known that "it would only happen when updating a very old RouterBOOT version" but I also expect this not to be the full story, as I would not expect that everyone who never upgrades their RouterBOOT is now suddenly doing that and consequently bricking their devices. There is probably more to it.

It shows again it was a bad idea to sync the RouterBOOT version with the RouterOS version. Now we do not know how often it has been updated, and if it was updated this time. I remember before this change was made the RouterBOOT updates were very seldom, maybe once or twice a year. And now everyone updates it with every RouterOS update, requiring an extra reboot and incurring an extra risk. Not good.

infabo · Sun Nov 07, 2021 5:09 pm

and extra wear. it is nonsense to align ROS and bootloader version whrn changes are so infrequent.

mducharme · Mon Nov 08, 2021 12:48 am

and extra wear. it is nonsense to align ROS and bootloader version whrn changes are so infrequent.

We don't upgrade RouterOS often. Our last standard version was 6.44.5 and early this year we adopted 6.47.9 as the new standard version after a lot of testing, so there are almost always guaranteed to be changes in the boot loader in that time.

We use The Dude to push down new RouterOS versions to our devices. The Dude has no feature to trigger a firmware update, so updating the firmware would mean manually logging into hundreds of devices and triggering the update one at a time. That means it would never happen and all our devices would be on factory RouterBOOT firmware forever basically. I know this because before there was no auto upgrade firmware and then we just never upgraded the RouterBOOT, everything was factory RouterBOOT forever. I am not sure if that is better or worse than using auto upgrade firmware and upgrading the devices very infrequently.

r00t · Mon Nov 08, 2021 3:48 pm

Mikrotik going from proper RouterBOOT versioning to making it always the same as ROS version was the worst decision ever. There are rarely any RouterBOOT related changes in a changelog, so it's likely that only change is version number string. This stupid system also completely hides any importance of updates, because they all look the same.

Enough of this mess! Bring back the proper RouterBOOT versioning!

rushlife · Mon Nov 08, 2021 11:57 pm

On my devices I always using "auto-upgrade=yes " since times, when this option become available and I was never have any problem as described by folks above. Never ever.

Btw. I am using about 500 pcs devices from Mikrotik in my network/company.

I had to use netinstall ONCE, when I fuc**d up password. Entirely my fault.

mducharme · Tue Nov 09, 2021 1:57 am

Mikrotik going from proper RouterBOOT versioning to making it always the same as ROS version was the worst decision ever. There are rarely any RouterBOOT related changes in a changelog, so it's likely that only change is version number string. This stupid system also completely hides any importance of updates, because they all look the same.

Enough of this mess! Bring back the proper RouterBOOT versioning!

I don't completely agree with this - the problem with the old RouterBOOT versioning was it was different for different devices, and became hard to track what changes and versions were associated with what releases to determine whether an upgrade was necessary.

What I think might work better is if they followed the RouterOS releases *but* did not increment versions needlessly if there were no changes to that firmware. For instance, if 6.48.2 came with a new RouterBOOT firmware, then the version listed there would be 6.48.2. If 6.48.3 did not come with a new firmware, then upgrade firmware there would still be listed as 6.48.2 and it would not upgrade. Then if 6.48.4 had RouterBOOT firmware changes, the upgrade firmware there would be listed as 6.48.4 so you would simply skip 6.48.3. The advantage there is that you can check the changelog for the RouterOS versions to see what has changed in RouterBOOT between them.

This would allow avoiding firmware updates where nothing has changed, but be better than the old independent system in that you could still track the changes between firmware versions in the main changelog. The only downside I can see is that a small number of people might wonder why they installed RouterOS 6.48.3 and upgrade firmware still showed 6.48.2, but that's probably not a big deal.

r00t · Tue Nov 09, 2021 3:26 pm

Yes, that would still be better than current situation. As long as RouterBOOT versions are not increased for no reason every release.
And during NPK installation, it's easy to check for too old RouterBOOT and stop the install, leaving error message in a log. So if you attempt to install new version on old RouterBOOT, it would simply not do anything to router software or configuration. Just deal with these problems in a better way.
Hopefully this recent issue will result in a better compatibility checks on Mikrotik side, before each release and during installation process...

BrateloSlava · Tue Nov 09, 2021 7:15 pm

Today employees brought me two RB2011UiAS-2HnD-INs from branches, which do not boot after updating to 6.49. Moreover, the packages update itself was successful, and the firmware update led to a crash. Previous version - 6.47.9.
Recovery attempts were unsuccessful. The router is determined by the netinstall program. However, an attempt to install stable or long-term - unsuccessful.

chm0d755 · Thu Nov 11, 2021 2:16 pm

On SXT 5HPnD upgrading was OK but after "system routerboard upgrade" bootloader is broken (reboots constantly, no even single beep). Only netinstall helps!
It happened on two devices, didn't try more.

I had the same problem after upgrade "RB SXT 5HPnD"
Model: SXT 5HPnD
Firmware Type: ar7240

osc86 · Thu Nov 11, 2021 6:00 pm

@BrateloSlava try another version of netinstall, some don't seem to work. Last week I had to download 3 different versions, until I found a working one, I think it was 6.47.10. Same story, Router appeared in netinstall, you hit install and nothing happens, or it is stuck forever at formatting harddisk. I don't know what is wrong with netinstall lately, maybe the image file transferred over tftp is broken or smth..