If invalid VLAN filtering is not enabled, management access to the device using tagged or untagged ( VLAN 0) traffic is already allowed from any port, though this is not a good practice, this can cause security issues and can cause the device's CPU to be overloaded in certain situations (most commonly with broadcast type of traffic).

You should also assign an IP address to the bridge interface so the device is reachable using an IP address (the device is also reachable using a MAC address):Īdd address=192.168.88.1/24 interface=bridge1 In all types of management access it is assumed that ports must be switched together, use the following commands to switch together the required ports:Īdd bridge=bridge1 interface=ether2 hw=yesĪdd bridge=bridge1 interface=ether3 hw=yesĪdd bridge=bridge1 interface=ether4 hw=yesĪdd bridge=bridge1 interface=ether5 hw=yes In such cases you will need to configure management access. It is possible to use device's serial port for management access, but in most cases such an access method is not desired and access using an IP address is more suitable. In general, switches are only supposed to forward packets by using the built-in switch chip, but not allow access to the device itself for security reasons. Prior to RouterOS v6.41 port switching was done using the master-port property, for more details check the Master-port page. Note: Port switching in RouterOS v6.41 and newer is done using the bridge configuration.

Mikrotik cloud router switch