How to configure multiprofile on Mikrotik

overview through the creation of firewall rules, multiple browsing profiles can be used on the same network in this way, two or more machines connected to the same network will be able to use different filtering rules and you can more easily split data traffic for additional information on multiprofile configurations, please refer to our main platform documentation this guide is only usable in standard workgroup environments, meaning setups without active directory servers variables to replace the following commands allow you to create rules to manage up to five browsing profiles however, it is not mandatory to use all of them depending on your needs, it will be sufficient to delete the superfluous parts of the code before running the commands on your mikrotik terminal, you must edit the following placeholder fields with your actual data list ip1 to list ip4 the list of ip addresses that will be assigned to each specific profile you can enter a single ip or a range of ips using the hyphen symbol between the first and last ip in the range, like 192 168 1 2 192 168 1 100 profile1 to profile4 the custom name assigned to each profile, if applicable terminal configuration open a new terminal window in winbox and execute the following customized commands routeros /ip firewall address list add address=\<list ip1> list=\<profile1> add address=\<list ip2> list=\<profile2> add address=\<list ip3> list=\<profile3> add address=\<list ip4> list=\<profile4> /ip firewall nat \# \<profile1> add action=dst nat chain=dstnat comment=\<profile1> dst port=53 protocol=udp \\ src address list=\<profile1> to addresses=185 236 104 114 to ports=53 add action=dst nat chain=dstnat comment=\<profile1> dst port=53 protocol=tcp \\ src address list=\<profile1> to addresses=185 236 104 114 to ports=53 \# \<profile2> add action=dst nat chain=dstnat comment=\<profile2> dst port=53 protocol=udp \\ src address list=\<profile2> to addresses=185 236 104 124 to ports=53 add action=dst nat chain=dstnat comment=\<profile2> dst port=53 protocol=tcp \\ src address list=\<profile2> to addresses=185 236 104 124 to ports=53 \# \<profile3> add action=dst nat chain=dstnat comment=\<profile3> dst port=53 protocol=udp \\ src address list=\<profile3> to addresses=185 236 104 134 to ports=53 add action=dst nat chain=dstnat comment=\<profile3> dst port=53 protocol=tcp \\ src address list=\<profile3> to addresses=185 236 104 134 to ports=53 \# \<profile4> add action=dst nat chain=dstnat comment=\<profile4> dst port=53 protocol=udp \\ src address list=\<profile4> to addresses=185 236 104 144 to ports=53 add action=dst nat chain=dstnat comment=\<profile4> dst port=53 protocol=tcp \\ src address list=\<profile4> to addresses=185 236 104 144 to ports=53 \# default profile add action=dst nat chain=dstnat comment=default dst port=53 protocol=udp \\ to addresses=185 236 104 104 to ports=53 add action=dst nat chain=dstnat comment=default dst port=53 protocol=tcp \\ to addresses=185 236 104 104 to ports=53 the default profile rule routing to 104 104 must always have a lower priority than your other specific profile rules inside your firewall table