Hi
Before buying my first cloud router switch I’d like to ask a community how to deal with VLANs. I believe that dispatching VLANs with bridge would not be a good idea, isn’t it? What is the better than bridge way to receive, for example, 10 vlans in a trunk port 1, 1 vlan assign as native (PVID) to port 2 and dispatch 9 others to the next switch in a 801.1q trunk via port 3?
That is quite simple.
Create a bridge with port 1 and 3.
Create a VLAN on the bridge with the desired VLAN id to be linked to ether2 and put the vlan interface together with ether2 into a dedicated bridge.
I did not made a tests but I think this will eat CPU and will complicate the config because I will need to make a bridge for each VLAN. Is there any “vlan membership” 's analog? Is there a possibility to play with VLANs like switches do it?
How many switches in CRS125-24G-1S-RM?
Could VLANs be managed in a switch manner with “/interface ethernet switch” commands?
You can find some examples in the wiki:
http://wiki.mikrotik.com/wiki/Manual:CRS_examples
You would not necessarily need to add a bridge to use vlans across ports 1-3. You should be able to use the switch functionality at wire speeds without needing to add a bridge to the CPU load.
Go to routerboard.com.
Download The Block diagram.
It shows that Ether1-8 are wire speed on one switch chip, Ether9-16 are wire speed on a second switch chip, and Ether17-24 are wire speed on a third switch chip.
It then shows all three of those switch chips connected to a “26 port non blocking wire speed switch chip”. The central “26 port non blocking wire speed switch chip” also connects to the SFP1 cage and the CPU.
This will allow you to use the switch menu to use vlans at wire speed or add a port to the CPU to allow for full functionality of RouterOS.
dynamic desirable - This option means that the port is running Dynamic Trunk Protocol (DTP). Port int this mode (the default setting on this particular switch), will send special frames to the device connected to it, trying to negotiate trunk connection. If the other end responds to this proposal, both interfaces become trunks. Since in my case, it is a PC that is connected to port F0/1, and did not respond to this negotiation (no DTP), the port became a ‘static access’ (member of one VLAN only).