I was able to successfully upgrade both of my home switches to 2.13.
CSS106-1G-4P-1S was updated without question, and CSS106-5G-1S only after enabling rstp.
if in acl add 3rules 192.168.88.0/24 192.168.88.1 and 192.168.88.1 192.168.88.0/24 allow and 0.0.0.0/0 0.0.0.0/0 to deny switch rebooted to default state. So, why?
I have CRS328-24P-4S+, CSS326-24G-2S+, CRS309-1G-8S+ all happily running on 2.13 used web auto update they all went without a flaw. I upgraded a day or two after it was released. I am hoping 2.14 will come some day its been 7 months now.
Having a strange issue with a computer when plugged directly into a Mikrotik CRS328-24P-4S+ switch with 2.13 software.
Ping time across local network are anywhere from 0ms to >1000ms. Link seems to jump from 10M to 100M to 1000M randomly. Often can’t even load the web page directly from the switch. If I plug a little 5 port TP-Link switch in between it still doesn’t work, but if I place a Mikrotik hAP ac lite with all the ethernet ports in a bridge group with ether1 plugged into CRS328-24P-4S+ with PoE, computer plugged into any of the other 4 ports, it works rock solid.
Device is an Intel NUC with integrated Intel I219V6 PCI Express Gigabit Ethernet. I have tried it in different ports on this switch, I even tried an Mikrotik 1Gig SFP transceiver for copper, a generic 10G SFP+ transceiver for copper, but the problem persists. I have not moved the computer to another room where it could plug into a different switch such as CSS326-24G-2S+, or the gig port on a CRS317-1G-16S+, or with any of the mentioned transceivers on these switches.
I have a couple same model NUCs at other locations, one plugged into a port on an RB4011 with no issues, the other is on a D-Link managed 24 port gig switch with no issues.
Seems like it may just be some rare incompatibility between this particular intel Ethernet chipset and this model switch.
If you place the TP-Link switch in between, which ethernet leg misbehaves, the NUC-TPLink or the TPLink-CRS? If it’s the former, then the blame is mostly on NUC. If it’s the later link leg, then the blame is largely on CRS.
I will be back at this location again next week. Plan on doing a little more diagnostics to narrow the issue down further.
After upgrading my CRS309-1G-8S to SWOS 2.13, when i attempt to boot into SWOS I am unable to connect to the switch via the ETH port. I have set the IP to static and specified the default 192.168.88.1 address. The only way to get back into the switch is by resetting it using reset button and booting back into RouterOS. I am running RouterOS 6.48.6 and have updated routerboard firmware. I don’t currently have a console cable to connect to the switch when it is trying to boot into SWOS. Any suggestions. I have also attempted to reset SWOS config via RouterOS cli.
Nearly 1 full year since the release and yet we still have no upgrades? They must consider this branch perfect and plan nothing more.
I have also been bitten by the RSTP root bridge pointed at itself when uplinked via SFP port (would have considered that fairly standard) had to set to ANY, eventually worked around it by setting VLAN Receive to ONLY TAGGED with an unused PVID up near the top of the VLAN range. That has been working fine for me for the last 4 months like that.
On CRS326-24S+2Q+ RouterOS 6.48.6 / SwOS 2.13 / WinBox 3.35 64bit
the IP inside WinBox / System / SwOS appear on reverse bytes order: 1.88.168.192
also on Terminal, both on print and export
but if is SET correctly
/system swos
set static-ip-address=192.168.88.102
is set rigtly (but stil appear with bytes inverted on print and export) when booted on SwOS
using CRS317-1G-16S+ access SFP tab menu using chrome become not responding
Please release new SwOS for CRS305 which contains backports of the marvell switch bugfixes and ability to force 2.5g mode please. It has been over a year, and the only way for me to use these 1gbps rj45 modules on CRS305 is to use SwOS (no way to get them working on RouterOS, always autonegotiation failed), set them to forced 1G mode, reboot SwOS (which thankfully only takes seconds not minutes like RouterOS), then set them to autonegotiate and then they work.
model?
what is this ?
shows up on automatic update of CRS305 SwOS
I also noticed it (not there anymore). Seems a mistake.
To anyone reading this, do not upgrade to a no older than 1 month firmware. First read what others are saying about it.
The 2.14/2.15 problem is fixed (the last now is 2.13), expect new updates soon.
Thanks.
I realize this is a very late reply, but I just encountered the same issue with a CRS309 I’m switching to SwOS.
If RouterBOOT firmware is 6.48.6, SwOS no longer boots - not with the version it came with (2.7) nor with 2.13. But when I factory reset, it downgrades to its stock firmware (6.44.3), and after setting it to boot SwOS, it goes without a problem.
So the solution to your problem should be downgrading the firmware via factory reset.
Feels a bit ironic seeing as I skipped firmware 6.48.5 due to reports of bricking, only for SwOS to get taken out to the back of the shed and shot by 6.48.6. Yet another LTS that fails to live up to its name…
“Feels a bit ironic seeing as I skipped firmware 6.48.5 due to reports of bricking, only for SwOS to get taken out to the back of the shed and shot by 6.48.6. Yet another LTS that fails to live up to its name…”
There is one important thing many people don’t know: the upgrade is done by the installed version, not by the new one!
So, when one version (say 6.48.6) is released to fix the upgrade problem, it means the fix is valid to upgrades from 6.48.6 onward - not from to 6.48.6. This is an important thing to keep in mind.
Hi guys
i have 2 CRS devices.. running in switchOS mode.. 1 crs305 and 1 crs317 both running 2.13 firmware latest upgraded…
and on both sides we have CCR1036 running long term 6.48.6.. all connected in 10G spf+ both ends..
i have setup static route ipv4.. and working 100%
i tried setting up ipv6 /126 on interfaces for communication.. but IPV6 not passing packets trough the CRS switches at all they get discarded.. when i plug the SFP+ direct on ports sfp+10g from the CCRs 1036.. it works ok communication ping.. etc.etc… but when i plug back the ccrs into the switches.. and inter-connectboth switchs via SFP+ cables.. ipv6 stops working..
so any ideas of what this could be? because it states in 2.12 version communication allowed local ipv6 not sure what it means.,
ACLs or anything that messes with multicast? igmp snooping etc.