CRS also won't be able to fetch correct time and date from network servers, so after reboot timestamp will be 1st of January 1970. In this case, CRS won't have access to internet so you won't be able to perform ROS upgrades simply by running upgrade command from CRS (you'll have to upload upgrade packages from management PC). Also configure DHCP server on ether1 (assign a pool of IP addresses from management IP subnet) so that when you connect to management port, PC will get appropriate IP address. Then set static IP address on ether1 and better use different IP subnet than used in main LAN. In this case you add all ports to bridge except for the management port (let's say it'll be ether1, but any other will do just the same).

if you don't trust your LAN devices and/or users, then you can create management (V)LAN or management port on CRS device.Įasier is to create management port on CRS device, which means you have to connect to that port to get management access.

And be sure you're not running DHCP server on bridge interface not to mess with your LAN's DHCP server.

Then you either set static IP address or run DHCP client on bridge interface.

if you trust your LAN devices and users (sometimes that trust is not warranted), then you can configure all ports on CRS to single bridge.

If you're going to use CRS as normal switch (and will be running ROS as opposed to SwOS, some units are capable of running both), then you have two options:

Mikrotik cloud router switch