We make a volume to hold the configuration we will create below. Note: Use the internal eMMC if it exists. ip/firewall/nat/add chain=srcnat action=masquerade src-address=172.17.0.0/24 Step 3: Confirm sufficient storage space interface/bridge/port add bridge=dockers interface=veth1 Later when the Agilicus connector is installed, it will need to be able to resolve DNS and perform outbound connectivity to /interface/veth/add name=veth1 address=172.17.0.2/24 gateway=172.17.0.1 If you wish, you may use direct interfaces without NAT by assigning a second IP, or, by assigning physical ports.

Now we will enable a virtual Ethernet bridge (veth1) and assign it to the container use. If you are using the Web or WinBox configuration, you will see a package installed as below:Ĭonfirm the container command exists: /container/print count-only system/device-mode/update container=yesĪfter this is complete, confirm it is enabled: system/device-mode/print Step 1: Enable Containerįor more information, see MikroTik Container Instructions. If you have, skip ahead to the Setup config-volume step. Note: the first steps assume you have not enabled container-package and networking on the RouterOS device. They may also be performed via the Web GUI or the WinBox. The below instructions were performed using the MikroTik CLI. The below instructions were tested on the CHR version of MikroTik (v7.8) and are believed to work on RB5009UG+S+IN with v7.8, specifically: /system/resource/print In order to be appropriate for the Agilicus Connector, they need to support: Other MikroTik devices may work as well, MikroTik has a broad family of devices. NOTE: this is an ARM-based device, not X86. it is a good vantage point to run the Agilicus Connector. The MikroTik RB5009UG+S+IN is a small-form factor router.

Agilicus Connector Install: MikroTik RouterOS

Install mikrotik chr