I have been struggling with vlan configuration on my new L009UiGS-RM. Since this my first Mikrotik router I am not that familiar with the Mikrotik philosophy but I did some reading in the documentation.
Until now I have managed to configure a working configuration using an individual bridge for each vlan but this seems to result in a default bridge that is HW accelerated by the switch chip (ASIC) and the others seem to lack the hardware acceleration. I think I should use 1 bridge that is capable of managing vlans but when I do that, there is always something eventually leading to a factory default of my L009 while trying to get my vlans isolated, a working DHCP server or… , at least it has done so for at least a dozen times in the past 3 or 4 days
I want to create a configuration that lets me define a few trunk ports to connect to my (vlan aware) switches and a few ports that function as access port on the device itself.
Is the anyone that can point me into the right direction (or buy en nearly new L009UiGS-RM )?
The document, linked by @OP, has a few device-specific parts and one has to follow only one of them - the one which applies to actual device being configured. L009 has 88E6910 built in and hence only second part (the first after Introduction) applies. As it happens it’s essentially saying the same as tutorial, linked by @holvoetn.
Could not leave it at this for today but I guess I give up, I can’t even get:“add name=bridge1 frame-types=admit-only-vlan-tagged” in the device.
I would like to think that I have some CLI knowledge after configuring: Cisco, Palo Alto Networks, H3C, VMware NSX-T, HP , Pulse Secure, Ubiquity edgerouter.
In CLI, there are two commands that seem to be similar, but can not be used one instead of the other:
add
adds new item to the list of items in certain configuration tree. E.g. /interface bridge add … will create a new bridge. There are some configuration trees where items have to be unique in certain aspects. Bridges, for example, have to have unique names. So add command will inevitably fail if bridge, named “bridge1”, already exists prior to running command.
set
command sets certain property of already existing item and fails if item doesn’t already exist.
So, if you already have bridge named “bridge1” and you only want to change property (e.g. frame-types), you should execute command
I think that I kept messing up in different parts of the configuration, caused by not knowing default behavour.
I’ve built a new config based on 1 bridge (for all switch ports) with a few vlans and placed the bridge and the trunk ports in tagged and the acces port(s) in untagged.
I have set the PVID on the bridge ports where needed.
Created a few DHCP servers ( one for each vlan were needed with the apropriate settings).
Enabled vlan filtering on the bridge.
This all resulted in a more or less working configuration, enough for a proof of concept.
I will now start with the ins and outs of the CLI.
Thanks for explaining the set and add differences, it does help with understanding the CLI.
)?