Question and Help before i try this... Simple Failover RB450

RouterOS Beginner Basics
1

i need simple failover

ether1-Fiber will be with static wan ip
ether2-Cable will be with dynamic wan ip

both connections will have different dns and gateway from my isp

for now i’m trying to configure in local lan before i put it to replace my pc-ruter

i see that my default config of router is little different then in wiki for some thing so i just want to ask before i try this
http://wiki.mikrotik.com/wiki/Advanced_Routing_Failover_without_Scripting

cose… now when i disconnect cable from ether1-fiber everything works thru ether2-Cable… but when i connect back ether1-fiber its not working it still goes to the net thru ether2-cable … i tried to disconnect ether2-cable but it does not go back to ether1-fiber as expected … so something is missing

would it work if i follow link on wiki? or should i find some script or anything else for this to work



this is when one cable is connected
[admin@MikroTik] /ip route> print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit

DST-ADDRESS PREF-SRC GATEWAY DISTANCE

0 ADS 0.0.0.0/0 192.168.1.1 0
1 ADC 192.168.1.0/24 192.168.1.214 ether1-Fiber 0
2 ADC 192.168.88.0/24 192.168.88.1 ether3-local 0

[admin@MikroTik] /ip route> print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
0 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable ether1-Fiber distance=0 scope=30 target-scope=10

1 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.214 gateway=ether1-Fiber gateway-status=ether1-Fiber reachable distance=0 scope=10

2 ADC dst-address=192.168.88.0/24 pref-src=192.168.88.1 gateway=ether3-local gateway-status=ether3-local reachable distance=0 scope=10

this is when both cables are connected
[admin@MikroTik] /ip route> print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit

DST-ADDRESS PREF-SRC GATEWAY DISTANCE

0 ADS 0.0.0.0/0 192.168.1.1 0
1 DS 0.0.0.0/0 192.168.1.1 10
2 ADC 192.168.1.0/24 192.168.1.214 ether1-Fiber 0
ether2-Cable
3 ADC 192.168.88.0/24 192.168.88.1 ether3-local 0

[admin@MikroTik] /ip route> print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit
0 ADS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable ether2-Cable distance=0 scope=30 target-scope=10

1 DS dst-address=0.0.0.0/0 gateway=192.168.1.1 gateway-status=192.168.1.1 reachable ether2-Cable distance=10 scope=30 target-scope=10

2 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.214 gateway=ether1-Fiber,ether2-Cable gateway-status=ether1-Fiber reachable,ether2-Cable reachable
distance=0 scope=10

3 ADC dst-address=192.168.88.0/24 pref-src=192.168.88.1 gateway=ether3-local gateway-status=ether3-local reachable distance=0 scope=10


p.s.

/ip firewall mangle print
Flags: X - disabled, I - invalid, D - dynamic

[admin@MikroTik] /ip firewall nat> print
Flags: X - disabled, I - invalid, D - dynamic
0 ;;; default configuration
chain=srcnat action=masquerade out-interface=ether1-Fiber

1 chain=srcnat action=masquerade out-interface=ether2-Cable

2

The main reason why you may not be seeing things fall back to your main route is because the router “remembers” where it has sent connections in the past. So your fiber connection goes down, and new connections start to use your cable, then your fiber comes back up. Because the router remembers that “for this session I have an established connection over this route”, it’s going to continue to use that connection unless there is a new session made or the current session is closed (I.E. someone goes to a different web site or the download is finished). It will also remember for connections to that site from the same host what route was used.

You cannot switch an established connection mid stream to go out another provider, a new session must be started for it to work over the new route. You can clear out the connections table on a down/up event, but this will break sessions in midstream and cause problems you probably don’t want. It’s normal behavior and the router isn’t doing anything wrong, you can lower the TCP timeout to some other value to make certain things change back faster, but you don’t want to set it too low.