Two ISP/Gateway in one Network

I have an RB4011isG+RM. I'm using it for my internet cafe running diskless on client PC's, with one server and one timer PC. I have two ISP's. I want to run two ISP's in one network so my customers can manually change ISP whichever they prefer since some games have high ping on the other ISP.

  1. Is running two ISP's in one network possible without merging? For example, ISP1 = 128.0.0.1, ISP2 = 128.0.0.2.
  2. Is it possible to config load balancing for this type of config?

The easiest way of dealing with TWO WAN connections for customers is the following:

a. WIFI - one can dedicate an SSID for WAN1 connectivity and SSID2 for WAN2 connectivity.
b. WIRED - Supply desktop switches with labels for connectivity to appropriate WAN. ( would entail different subnets).

Yes, failover is possible to setup such that one WAN takes the entire load if the other WAN is not available, but only works if the ISPs are different etc.

Dual WAN won't work on diskless setup. I tried with different subnet. I just could get it to work so as my tech.

Thanks for the quick response.

My only issue is the wired ones. I want to use two ISP's in one network(ISP1 = 128.0.0.1, ISP2 = 128.0.0.1) and I want my customers to manually change gateway as they pleased. I made a .bat script for this.

Yep, but if I get it right there are three different things at play:

  1. failover
  2. load balance
  3. user choice of the appropriate WAN

The first two can be automated inside the Mikrotik device, but the third cannot, because it is a manual choice and would imply that the users have access to the router settings.

I presume that your batch file changes IP of the gateway of the PC client,
so that it connects through one of two existing gateways, one "going out" through WAN1 and the other through WAN2?

Or what does it do?

You can achieve what you want with this setup (pretty common in internet cafés in my country):

  1. You'll need to add a MACVLAN interface on the same interface that currently has your LAN subnet.
  • Now if that interface is a VLAN interface like vlan100 or a port such as ether2, you can add the MACVLAN interface without issue with for example:

    /interface macvlan
    add interface=vlan100 name=macvlan1
    

    or

    /interface macvlan
    add interface=ether2 name=macvlan1
    
  • But if that interface is a bridge (for example bridge) then you have to:

    • Either upgrade the router to 7.20beta7 (or newer) and create the MACVLAN interface on that bridge interface:
      /interface macvlan
      add interface=bridge name=macvlan1
      
    • Or if you still want to use stable version of RouterOS, such as 7.19.4, you'll need to move your LAN subnet to a VLAN interface or a stand-alone ethernet port first, then create the MACVLAN interface as described above. Current stable versions of RouterOS do not allow adding MACVLAN interfaces to bridges yet!
  1. Add an IP address to this MACVLAN interface in the same subnet as your LAN subnet. For example, if the router has 192.168.88.1/24 on the main VLAN/bridge/ether-port, then set 192.168.88.2 for macvlan1:

    /ip address
    add address=192.168.88.2 interface=macvlan1 network=192.168.88.2
    
  2. Add this interface to the LAN interface list if you use defconf, or do whatever needed so that macvlan1 has the same firewall setup as your main LAN interface (the VLAN/bridge/ether-port above).

    /interface list member
    add interface=macvlan1 list=LAN
    
  3. Assuming that you have already setup your routing tables with the main table using ISP1 as default route and you have a second table isp2 that has the ISP2 as default route. You'll need to add this routing rule:

    /routing rule
    add action=lookup dst-address=0.0.0.0/0 interface=macvlan1 table=isp2
    

    This ensures that packets coming through the macvlan1 interface are routed using the isp2 routing table.

That's all you need on the router. Now, on the client devices in the LAN subnet, if they use 192.168.88.1 as default gateway, their packets will be routed through ISP1, but if they change the gateway address to 192.168.88.2, they'll use ISP2 to go out to the internet.

On Windows you can use tools such as this one GitHub - KurtisLiggett/Simple-IP-Config: View and change your local IP addresses. to quickly switch between predefined list of default gateways. Or you can write batch files that runs netsh or Powershell commandlets to swap the gateway without GUI.

If you have more WAN, add more MACVLAN interfaces to have more gateway addresses for your clients to choose from.

I forwarded this thread to my technician. I guess he got it upon reading everything here. My internet cafe is now running smoothly thou still in the process adding Mangle routing to dozens of games.

Thank you all for your help.