Hey there. Years ago I bought a CRS125 and had hoped I could make it work as my all-in-one router/switch. No dice on that front. It seems I wanted bonding (lacp), intervlan routing and that was a no-go. I read that the CRS3xx series overcome some of the limitations of that platform. So, I bought myself one. But, I have been banging my head on the wall because of it. I thought (coming from a cisco + linux background) it would be simple.
I have an openwrt device, amplifi wifi, and a qnap nas. I was looking to have a trunk from the openwrt device into sfp1 on the CRS328 carrying vlan 200, 201, 202 (all tagged). The amplifi wifi device would use one access port on vlan 201. And, the qnap device would establish 4x gigabit links in a bond/port channel with vlans 200, 201, 202 (all tagged). Seems simple enough right?
After many hours of banging my head on the CRS328 I seem to be no further. I have reset the factory defaults. From here I was following https://wiki.mikrotik.com/wiki/Manual:CRS3xx_VLANs_with_Bonds but got lost in the weeds. I am trying to figure out the differences between interface vlans and bridge vlans. How things are tagged/or not. Any recommendations on a simple and straight forward approach? I hate to think I have another paperweight here.
IMO VLAN is an advanced stuff. You need good planning, and in such a heterogenous environment
one has to know each device very well in respect to interoperability and compatibility, eventhough they all follow some same standards.
My tip to you would be: first ensure interoperability with basic IP segmenting method (if needed), ie. without any VLAN at all, and sometime later you can switch to VLAN (if then still needed ).
Ie. take it easy, man
I personally think that I myself will never ever need any VLAN in my small SOHO environment as simple IP segmenting is more than sufficient for my needs, and IMO much simpler to setup, monitor, administer. But YMMV.
Another tip: you can also use a netmask that is not the usual /24, for example /20 :
Can’t help you on the bonding part (never done that), but VLANs are a piece of cake in either RouterOS or SwitchOS. As for routing between VLANs, RouteOS will automatically do that unless you specifically exclude that in firewall rules.
).