Important note!!!
Upgrading to SwOS lite 2.17 will retain your current switch configuration.
However, downgrading to older SwOS lite versions could result in complete loss of your configuration settings.
Save configuration backup before and after upgrade.
SwOS lite 2.17 version configuration backup is not compatible with older SwOS lite versions.
*) added notification when Primary backup firmware is in use
and encourage moving to Secondary regular firmware;
*) added confirmation dialog before resetting configuration;
*) added support for board-specific backup filename generation;
*) added SNMP serial number and version OIDs;
*) added option to disable IGMP querier;
*) added option to specify IGMP version;
*) added IGMP fast leave feature;
*) added support for host table sorting;
*) added Clear All/Set Default buttons in the Port Isolation menu;
*) added option to set forced 10G for SFP ports;
*) css610: improved Ingress Rate limiter precision;
*) css610: improved stability of SFP status readings;
*) css610pi: updated PoE firmware;
*) fixed neighbor discovery from WinBox;
*) fixed port numbering in BPDU packets;
*) fixed IGMP group removal on link down;
*) fixed DHCPv6 packet drops by “Add Information Option”;
*) fixed fragmented packet drops by “Add Information Option”;
*) fixed SNMP port indexation for BRIDGE-MIB;
*) fixed erroneous SFP monitor after link disable;
*) gpen21: fixed DAC linking when auto-negotiation is enabled;
*) improved SwOS lite web interface stability and responsiveness;
*) increased max VLAN entries to 250;
*) increased up to 63 byte SNMP Community/Contact Info/Location;
*) limited max ACL rules to 32;
DHCP option 82 for IGMP snooping was completely borked in SwOS, is there any acknowledgement on this? from this changelog it doesn’t seem like it was fixed.
Awesome! Now I can finally upgrade my CSS610-8P from the SwOS 17rc1 I was running for the past 1.5 years! So glad to see SwOS isn’t dead. It really is great for normal L2 implementations where ROS is complete overkill. Keep it coming Mikrotik!
Thanks, but more of “release early, release often” from now on please - so many accumulated changes means more risk the upgrade breaks something (especially if it makes the device inaccessible after remote upgrade, so can’t rollback easily).
Would it be possible to add something like “safe mode” - some way to restore previous working config when remote access is lost due to a wrong config change. It has been standard in TP-Link managed switches - changes applied but not saved permanently until “save config” menu option is selected (can’t do that if you just lost remote access), until then changes can be undone by reboot/power-cycle. Better yet, undo changes if not confirmed within some specified timeout, for situations where power-cycle is not easy (as in reverse-PoE switches, asking a few people to power-cycle their PoE at the same time is a challenge).
I updated my CSS610-8P-2S+ last night from 2.17RC1. For some reason I had to do it twice as the first time it seems to have rebooted the switch but did nothing. Second time worked without any issues.
Probably you should mention that POE devices will all get a powercut during the update.
The only reason I mentioned ROS is that is what I test on. I think the power/reboot functionality would have to do more with the hardware(and warm/hard reboot) and not ROS as it is rebooting anyway.
hmmmm… i did the upgrade on Aug 16 and today i had the switch lock-up on me, no ip, no arp, no forwarding! All LEDs were lit as expected and even links negotiated. needed a power cycle to recover. i hope this was a unique random occasion but if you experience something similar, please post here so we can collect for a support ticket.
I was really hoping for an adding info/option 82 addition for the GPEN21 units