The available firmware (2.5) at the time broke DHCP on any VLANs the switch could see.

The default SwOS firmware (2.3p) on the switch resulted in a SwOS bootloop.

RouterOS, which gives you full layer 3 capabilites, but potentially sacrifices line-rate speeds if you try and use any routing features, or SwOS, which turns the switch into an almost too-dumb managed switch that only supports LAGs, VLANs, RSTP, and not much else. With a CRS (Cloud Router Switch), there are two options.

Switching on the other hand is a disaster, and for almost a month when I first had the CRS317, I was unable to even use the switch. I have even started replacing some of my VPSs with CHRs, just because it works so well. But there’s a certain logic to the config, especially if you’ve ever done any CLI work on something like a Cisco.Ī recent photo of the CCR (cabling disaster included):įor routing, I’ll say I absolutely adore Mikrotik and RouterOS. As mentioned, Mikrotik likes to do things a little differently. I wasn’t worried about any layer 3 capabilities on the switch (at the time), so it didn’t bother me at all that while the CRS317 was capable of being a full layer 3 switch, it couldn’t do it at anywhere near line-rate. Around that time, I also started using a CCR (Cloud Core Router) for my main edge device.

This is Mikrotik’s 16 port SFP+ switch with a single gigabit port, ostenibly for management. A few days ago, thanks to a one or two sentence post on Reddit, I finally figured it out.īack in October 2017, I picked up a CRS317-1G-16S+RM. Well, not constantly, but it’s something that I keep finding reasons to try and hash out. Since October of 2017, I’ve been fighting with RouterOS and switching. That tiny company from Latvia does things a bit… different. I think anybody that’s ever used a Mikrotik and RouterOS can probably agree.

Swos winbox