Hello all,
I have a MT router running v3 OS that does nat for 192.168.0.0/24 network
Router has 2 DSL lines as an uplink. DSL modems are in bridge mode. Public ips are, lets say:
ether2: 12.12.12.5/24
ether3: 12.12.12.6/24
gateway for those two uplinks is the same, 12.12.12.1
the problem is that the load balancing with persistent rules from MT wiki does not work for this case, since we are using same gateway for both interfaces. Neither does one with failover
Is there a way to do load balancing with failover for this case?
I could put modems in router mode and have them do NAT, but in this case i don’t have failover, since modem will always(mostly) be pingable, while most problems are happening past the modem on the phone line
The problem is that addresses used on public interfaces are broadcast addresses.
MikroTik RouterOS interface routing is working correctly with point-to-point addresses.
Since /24 addresses are not point, interface routing is not suitable solution for this case.
I too have been struggling with a solution to this problem.
I would love to be able to interface 2-3 connections into 1 router all from the same provider with the same subnet using a mixture of dynamic and static ip’s. The statics I would like to be able to map to either a server internal subnet and also into my general internal subnet running through a hot spot.
As I could not figure out how to make this happen easily, in such a way my other techs would understand, I have gone ahead and ordered 2 RB150’s. I plan to put a RB150 w/lvl4 Lic on each cable connection. Theory was to have connection go to a switch, use 1 port on RB for statics, 3 ports for dynamics, and 1 port to uplink to a main Mikrotik router.
I have two line of ADSL Provider in Indonesia.
They served PPPoE for their clients.
PPPoE is point to point right? I have try it already and it wont work.
The problem is not the routing for default gateway. I have try to disable the default routing on the PPPoE client so the server dont assign me any default routing, but still the connection got hang up every times.
So perhaps this is not routing issue, but network / broadcast issue. CMIIW
In Ros v3 you DONT have to specify an ip address for the gateway. You can just say, HTTPS traffic to go out of interface ether1 and then you say FTP traffic to go out interface ether2. (when I say HTTPS traffic to go somewhere that obviously implies that you have already configred your mangle rules for policy routing as per wiki)
R-OS in this case doesnt care what the gateway is, it just sends the data to the interface regardless of the addressing.
So, using the RouterOS 3 sounds cheaper than buying new hardware and ROS licenses…