Both firmware packages coexist in the flash memory and you can easily switch back and forth as required.Īlthough SwOS could suffice for my needs in the home lab, I’m not one to shy away from a challenge and really want to be able to take advantage of some of the 元 features. There is no need to flash back and forth from RouterOS to SwOS and vice-versa. If you are not looking to use any of the advanced 元 features that RouterOS offers, I’d highly recommend using SwOS instead. I found SwOS’s UI to be very intuitive and a lot more like what I’d expect to see on a switch.
The CRS309 also includes ‘SwOS’ – a straight-forward L2 firmware that is designed especially for their switches. Things get easier when you learn the terminology and understand what does and does not apply to a switch within RouterOS. Configuring RouterOS on the CRS309/CRS317 can be challenging and there is a learning curve to overcome – even for those with a lot of networking experience. Because of this, it feels more like router firmware adapted for use with switches as opposed to something designed especially for them. Today, it works with many of their other products, including switches, and wireless devices. It’s a multi-purpose firmware that was originally created for MikroTik’s routers.
It has everything from BGP/OSPF, to firewalling, NAT, DHCP services – you name it. MikroTik’s RouterOS firmware that comes pre-loaded on the switch is very feature rich with loads of 元 functionality. Please note that although this was written for the CRS309, this should be applicable to all CRS3xx series switches, including the popular CRS317. Today’s first post will introduce MikroTik’s RouterOS and will focus on VLAN trunking. This will be the first of several posts on configuring the new MikroTik CRS309-1G-8S+IN for use in a VMware home lab.
0 kommentar(er)
