Looks like you need to configure “switch1-cpu” port just like “ether2” port in the switch menu to allow access to DHCP servers configured on VLAN interfaces.
Did that and now it is working! But what’s means placing this “switch1-cpu” inside de vlans? What’s the logic that I should understand?
And why is shown switch2-cpu / switch3-cpu ?
The MikroTik swich configuration is hard to understand because it is based on how the switch chip has
to be programmed by the software, rather than on the typical view of a switch by the network engineer.
I had similar problems as you when trying to configure a MikroTik switch (part of a router) with tagged
and untagged VLANs, and when it all works it appears so obvious…
The documentation in the WiKi is also a bit lacking, “documentation by example” is sometimes useful
but should not be the only thing.
I consider it two separate devices… 6 port switch and one port router… hooked up by virtual Ethernet… on the switch side as swith1-cpu and the router side as the master-port.
I think that was a bug at one time. You’re pretty behind on updates, I’d update to at least 6.34x bug fix only.
Is it correct to assume when working with VLANs using the switch instead of bridges, is the best practice in terms of performance?
When using the switch like I did, we are using the ASIC chip, and the processor is more “free” to work with routes, QoS, etc? and if use bridges, the VLANs workload pass to the processor ? Am I wrong with this idea?
Definitely faster and less bottlenecks using the switch. Bridging does at least two things.
Sends everything to the cpu for processing, so takes cpu resources.
Sending everything to cpu also limits the total bandwidth across the switch to the bandwidth of the cpu links. (Very important on Gigabit switches, some Fast Ethernets have the CPU integrated)