Mikrotik is interesting for the modification, one of which is to separate the traffic In IIX and easily with just a few minutes it is, why must be separated In and IIX? In the first bandwidth is usually more expensive than the ISP IIX and now sells packet-packet bandwidth and usually IIX In its different, both these can also proceed to make the bandwidth management.
This time I use a case study such as this: There is a cafe to buy a connection to an ISP with intl and its different Gateway IIX we take the easy way so there are 2 interface into the router NIC’s cafe for the ISP and IIX Intl NIC and 1 more to switch to lan warnetnya own.
And now, directly to how:
1. Setting ip address for each interface.
2. Enter routing rule only to IIX only take scriptnya below.
3. Enter Ip address list to mangle IIX network capture scriptnya below.
4. Create a gateway such as the following rule:
* Ip route add dst-address = 0.0.0.0 / 0 gateway = (gw ip traffic Intl) scope = 255 target-scope = 10 comment = “International traffic” disabled = no
* Ip route add dst-address = 0.0.0.0 / 0 gateway = (Ip a traffic IIX) scope = 255 target-scope = 10 routing-mark = (Name marknya routing in accordance with step no 2) comment = “traffic IIX” disabled = no
5. Create a mangle to mark the packet to the traffic IIX
* Ip firewall mangle add chain = postrouting dst-address-list = (adjust with no step 3) action = mark-routing new-routing-mark = (mark name address list in accordance with step no 3) passthrough = yes comment = “” disabled = no
6. Set allow request on ip dns set to be yes for the forward dns
7. Set NAT:
* Ip firewall nat add chain = srcnat src-address = (lan netwok) = out-interface (interface for ip In) action = disable = no Masquerade
* Ip firewall nat add chain = srcnat src-address = (network lan) out-interface = (ip interface for the IIX) Masquerade action = disable = no
After that can be tested from a client, do tracert to ensure
Good Luck
