*) added support for CRS354;
*) CRS328: fixed SFP status monitoring;
*) CRS328: fixed auto-negotiation on combo ports;
*) CRS326Q: fixed matching by ports in ACL;
*) CRS326Q: properly detect QSFP+ optical modules;
*) CRS326Q: properly detect QSFP+ DAC cable;
*) CRS326Q: fixed case where some deleted ACL rules were still active;
*) CRS305: make auto upgrade work;
*) CRS312: fixed 2.5G & 5G modes;
*) CRS312 & CRS326Q: fixed SNMP ifAdminStatus & ifOperStatus;
*) CRS312 & CRS326Q: do not freeze when showing Host tab with no entries;
*) CRS312 & CRS326Q & CRS309: fixed ingress rate limiter;
*) CSS106: added reset-counters to Statistics tab;
*) CSS106: make RSTP work with vlanMode=enabled or vlanMode=strict;
*) CSS106: fixed IGMP, PPPoE & DHCP snooping of VLAN tagged packets;
*) CSS106: make port isolation work when vlanMode=enabled or vlanMode=strict;
*) CRS318fi: make 1G ports link with other routerboards;
*) CRS309: fixed tx flow control;
*) CRS305: fixed traffic forwarding between SFP+ ports;
*) fixed ingress traffic port mirroring on first port;
*) fixed dst. & src. port matcher in ACL;
*) fixed redirect-to in ACL;
*) fixed storm rate limiter on SFP+ ports working in 1G mode;
*) fixed storm rate limiter on 40G links;
*) correctly recognize some copper SFP modules;
*) added name to VLAN entries;
*) fixed VLAN entry management when they were added unordered;
*) fixed IGMP snooping - stop forwarding multicast packets
if there are no more listeners;
*) added support for IGMP fast leave;
*) always forward link local IPv4 & IPV6 packets;
*) fixed password changing on Chrome and IE;
*) do not renew DHCP address and restart RSTP on any System tab change;
*) reset error & histogram counters separately from main ones;
*) report correct ifSpeed & ifHIghSpeed for ports with no active links;
*) fixed crash when receiving jumbo frames on management CPU;
To install SwOS v2.13 on CRS354 family devices, upgrade RouterOS to the latest stable version (6.48.2) and use “/system swos upgrade” command.
my 1st attempt to upgrade a RB260GS(CSS106-5G-1S) from 2.12 to 2.13 thru a browser failed.
Upgrade was visible and started, device prompted “upgrade failed” and did reset tot firmware 2.0 and lost normal settings …
we’ve had this exact problem for ages with these switches, not just this version in particular. sometimes upgrades fail with nothing happening, sometimes it reverts back to 2.0, and sometimes it works.
we just need to keep trying upgrading until it eventually works.
*) CSS106: make RSTP work with vlanMode=enabled or vlanMode=strict;
CSS106 - RSTP issue is resolved
SwOS 2.11 and 2.13 - RSTP finds the correct Root Bridge
Did have a problem with RSTP root bridge pointed at it itself when I had UPLINK port (SFP) set to TAGGED ONLY!
Do not forget to set VLAN Recieve on Uplnik port to ANY
Dont know if this is intentional or a bug! It worked on tagged only frames on version 2.11!?
I also have problems if VLAN1 is not defined.. It calculates wrong ROOT (not itself both nevertheless wrong one!)..
This is also present on hAP-Lite and ROS and VLANs in Switch chip .. If you do not add VLAN1 it does not work!
Did You get the switch to download and install? Or did You download the file and installed manually? I have one CSS106-1G-4P-1S, and the upgrade went fine. The switch downloaded and installed the update.
I tried both ways, downloading thru the switch starts and after a couple of seconds fails … reboots in FW2.0. after a power cycle it gets back online in 2.12 with the working config …
I also uploaded the FW file to the switch, same result.
If the upgrade fails on CSS106, try toggling the RSTP setting on the port you are connected to. If the switch still boots into an older (primary) version, try manually uploading the file in the “Upgrade” page. If the CSS106 still refuses to upgrade, follow this article - Cannot upgrade SwOS.
the switch was running rstp and I disabled it. same result. The upload process starts and fails. devices reboots into FW2.0.
after power cycle it is back in 2.12 and running.
I tried to manually upload the new fw, same result. device reboots into FW2.0 …
after power cycle it is back in 2.12 and running.
I can not access all switches power-supplies remotely, so doing the full reset thing will have to wait …
Remember that CSS106 with SwOS cannot connect to the internet. There is no gateway/router defined. It cannot be set.
The IP routing mechanism is: answering to the IP address by using the source MAC of the request received. SwOS can answer an IP connection, but cannot initiate an IP connection.
It looks like as if SwOS is checking for an update, but it actually is your browser doing that. So don’t move away from that browser page while download&upgrade.
The path to the CSS106 in my case is over a MT wifi bridge connection (AP bridge /-/ station bridge powered by the CSS106) and for one or other reason the download&upgrade failed.
Lost connection to the CSS106 after 3th attempt and had to physically power off/on to gain access again. Nothings seems to have changed.
EDIT.
Upgrade keeps failing.
Manual download … same problem
local attached PC (independent from the power loss at the “station bridge” link) … same problem
disabled Windows defender … same problem
What surprised me was that Windows 10 / Chrome browser had problems downloading the file. The download never completes.
Disabling the firewall (Windows defender) gave complete downloads. (no complains in windows)
By comparing the 2 files, they are identical. Upgrade problem persists.
What is the meaning of “new CSS106” in the download page ??? Can we still find 2.12 SwOS for download?
Let me explain a little bit more …
I am running vlan 99 on my uplink for management traffic. So the switches have an address in my management vlan.
I tried to upgrade from a W10 laptop connected to that vlan. The default gateway in that vlan has internet access.
Normal ROS devices can upgrade directly in that vlan.
Tried to upgrade SWOS within a browser, it says version 2.13 found, starts the upgrade procedure and fails. reboots in FW 2.0, need power-cycle to get back in FW 2.12 …
Tried to upload the 2.13 to the switch, after uploading pressing the upgrade button starts somtihing and fails. reboots in FW 2.0, need power-cycle to get back in FW 2.12 …
I had the same experience. In the second attempt (manually downloaded file) the browser still mentioned “Waiting for upgrade.mikrotik.com” after pressing the upgrade button. The file was already local, and the reference to it was entered, so what is the connection to upgrade.mikrotik.com for ? The file field changed in that “sad looking square emoi”.
After running 2.13 on three of my minor switches for the past day and a half, I just updated my two main CSS326-24G-2S+ via the “Download & Upgrade” button. Both took the upgrade just fine with only one or two pings to 8.8.8.8 dropped on each one.
Everything appears to be working fine.
In SwOS 2.12 on the Upgrade tab page the buttons “Download & Upgrade” and the “Upgrade” button seem to execute exactly the same code.
(Where the “Upgrade” button is supposed to use the local file, as indicated with “File for Upgrade”, it just seems to ignore this and tries to download just as the other button)
As the “Download & Upgrade” fails, so does the “Upgrade” button.
In a standalone and an Internet-disconnected scenario for the Upgrade, with already downloaded firmware, there is no progress with the “Upgrade” button, as the browser keeps waiting for http://upgrade.mikrotik.com. Something in “engine.js” or identical definitions in the html page?
<a class="btn" draggable="false">Download & Upgrade</a>
<a class="btn" draggable="false">Upgrade</a>
