If you recall in part one, I created a VLAN interface in VLAN 1 to get management connectivity to the switch again. Second, we need to assign an IP address to these interfaces. To get inter-VLAN routing working on the CRS3xx series switches, there are two steps – first, we’ll need to create VLAN interfaces with the correct VLAN ID specified. Now that we have a management IP configured, we can continue in the UI. In the part one I relied on the CLI to get started. None the less, this is still plenty of routing throughput for a home lab and I’m really happy that they include a huge number of these features even if they are somewhat performance limited. MikroTik rates the switch for around 2.5Gbps for anything that will need to be processed by the CPU cores. This means that things like inter-VLAN routing, firewalling and other 元/L4 features are done in software. To use the 元 features, however, the CRS3xx switches rely on the integrated 32-bit ARM CPU cores in the Prestera DX. This is great for a home lab, because your non-routed vSAN, iSCSI and vMotion kernel traffic can take advantage of full 10Gbps line rate throughput. It uses the Marvell Prestera DX switching chip with a forwarding ASIC for line-rate L2 performance at very low power consumption levels. Keep in mind that I’m using the CRS309, but this should be applicable to the popular CRS317 and other CRS3xx switches running RouterOS as well.Īs I mentioned in my unboxing and overview post, the CRS309 is a fully featured 元 switch. Today I’ll be configuring inter-VLAN routing. In part one, I discussed RouterOS and how to get VLAN trunking configured for all ports from the CLI. Welcome to part two of a series on configuring the MikroTik CRS309-1G-8S+IN for use in a VMware home lab.

Mikrotik vlan firewall