The primary issue that I'm having is that I can't create an LACP bond between two ports on my CRS125-24G-15-IN because they are in the same port group, slaves of ether2.

I've followed the best practices for CRS VLANS on the wiki, and everything works great. But in order to create the LACP bond, I have to set the master on two ports to "none", and I cannot get connectivity to VLANS no matter how hard I try.

To troubleshoot at a more basic level, I'm removing just one port from the main port group and attempting to tag VLANS on that port, but I cannot connect on the Windows laptop I connect to. I just get "Unidentified Network". Multiple tagging configurations have led me nowhere, and bridging in many different ways hasn't either.

What is the best practice for utilizing VLANS across different port groups? How can I fix this issue? Thank you!

If i undersnd your q - you try to enable LACP between laptop (windows) and mikrotik?

If i undersnd your q - you try to enable LACP between laptop (windows) and mikrotik?

So, I should clarify that LACP is not the issue, the limitation is that I cannot bond slave ports, so when I remove them from the port group, I can't get VLANs to work even on one of those ports, much less an LACP pair.

So, first, MT doesn't support LACP in hardware on the CRS, only in software. That means that the bonding is done at the CPU. When working with slave ports, those ports are controlled by the switch chip, not the CPU, hence your problem. To enable link aggregation on slave ports, you need to use the Switch > Port > Trunk menu to create the aggregation trunk. Know, however, that this is static link aggregation, not dynamic, so the switch won't auto-drop a failed link from the group if one of the links goes down.