sorry it’s years ago i used that stuff… but why not pinging the PPPoE-clients public IP-address? If the corresponding ADSL-line disconnects, the IP-address is unreachable as well. unfortunately this IP-Address will possibly be given to another ISPs client, but usually not within seconds. plus one could force the ping through the right interface. If it’s possible to get a fixed public IPs via PPPoE this test will work for sure.
To this, I added:
add comment="" disabled=no distance=1 dst-address=0.0.0.0/0 gateway=192.168.101.1 scope=30 target-scope=10
because my router needs to connect Internet to remote access or NTP..
well, for this you may add two last rules, but without routing marks =)
Yes, but i prefer only one, for make easy to get public ip with dyndns script.
I activated the 2, with diferent distance, 1 and 2 ; D!
Next week i have to make the same for 3 adsl.. I think i’ll have 8 rules ; (
Thanks,
hmmm… but again, what if the modem is up, but no connection to the internet? =) distance=2 won’t help =)
more than 8, I think ))) but… what’s problem? =)
Its 2^3
i’ll try to configure it ; D!
I mean, 3 routes to ‘checkpoints’, 3 routes to ‘fake’ gateways (it’s better to use them - in case of ‘checkpoint’ change you will change only one route, not three), and 3*3 default routes (including failover). 15 in total =)
souns right
I activated the 2 routers but with diferent distance. Now if one fails, router will work with the other, and I can enter always with my prefered line.
Hello,
I am biginner user of RouterOS and also new user of this forum. I have found this topic with google. I would like to thank you for good tip:
I have problem with this.
I have try to use it and it works following way:
When the connection is lost between modem and internet the all traffic is forwarded to working connection. When later the connection is restored, is the traffic splited accrording routing marks in both connections. That works perfectly.
But I have a problem when the connection is lost between routerboard and modem (for example modem2). The all traffic is forwarded to working connection (modem1). That also works. When the connection between routerboard and modem2 is restored, is NOT traffic splited to two connections. All traffic goes over modem1. In this way it works for both modems.
I woul like, that connection is again splited to both modems.
Could you help me please?
Thank You
and what do you see in the “/ip route print detail” at that moment?
Hello, here is output:
[ro3ot1@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 S dst-address=0.0.0.0/0 gateway=213.180.204.3 gateway-status=213.180.204.3 recursive via 192.168.10.1 5-gw check-gateway=ping distance=1 scope=30 target-scope=30 routing-mark=to_ISP1
1 A S dst-address=0.0.0.0/0 gateway=93.158.134.3 gateway-status=93.158.134.3 recursive via 192.168.0.1 4-gw check-gateway=ping distance=10 scope=30 target-scope=30 routing-mark=to_ISP1
2 A S dst-address=0.0.0.0/0 gateway=93.158.134.3 gateway-status=93.158.134.3 recursive via 192.168.0.1 4-gw check-gateway=ping distance=1 scope=30 target-scope=30 routing-mark=to_ISP2
3 S dst-address=0.0.0.0/0 gateway=213.180.204.3 gateway-status=213.180.204.3 recursive via 192.168.10.1 5-gw check-gateway=ping distance=10 scope=30 target-scope=30 routing-mark=to_ISP2
4 A S dst-address=0.0.0.0/0 gateway=93.158.134.3 gateway-status=93.158.134.3 recursive via 192.168.0.1 4-gw check-gateway=ping distance=10 scope=30 target-scope=30
5 S dst-address=0.0.0.0/0 gateway=213.180.204.3 gateway-status=213.180.204.3 recursive via 192.168.10.1 5-gw check-gateway=ping distance=10 scope=30 target-scope=30
6 A S dst-address=93.158.134.3/32 gateway=192.168.0.1 gateway-status=192.168.0.1 reachable 4-gw distance=1 scope=10 target-scope=10
7 ADC dst-address=192.168.0.0/24 pref-src=192.168.0.240 gateway=4-gw gateway-status=4-gw reachable distance=0 scope=10
8 ADC dst-address=192.168.1.0/24 pref-src=192.168.1.1 gateway=1-green gateway-status=1-local reachable distance=0 scope=10
9 ADC dst-address=192.168.5.0/24 pref-src=192.168.5.1 gateway=2-orange gateway-status=2-local reachable distance=0 scope=10
10 ADC dst-address=192.168.7.0/24 pref-src=192.168.7.1 gateway=3-blue gateway-status=3-local unreachable distance=0 scope=200
11 ADC dst-address=192.168.10.0/24 pref-src=192.168.10.12 gateway=5-gw gateway-status=5-gw reachable distance=0 scope=10
12 A S dst-address=213.180.204.3/32 gateway=192.168.10.1 gateway-status=192.168.10.1 reachable 5-gw distance=1 scope=10 target-scope=10
The active gateway after reconecting the modem on iterface 5 is still for trafic “to ISP1” the gateway with distance 10 (line 2). I would expected that after reconecting the modem on interface 5 will be active for trafic “to ISP1” the gateway with distance 1 (line 0).
Thank You for your help.
One question:
did you copy paste any part of these rules via terminal or console?
If yes, try to copy paste the export file without the “/32” in the dst addresses/gateways.
I have this problem and reported to Maris via support, but he says that rules are Active..
You can see the rules active but as you say, the rules don’t work correct. True?! Is something like this?
I have the same problem if I disable the isp1 ethernet (example), and enable it. The routes shown aren’t the same than after reboot.
treborr, please make supout.rif at that moment and send it to support@mikrotik.com together with “/ip rou pr det” output…
Hello,
it is done, the files are sended to support@mikrotik.com.
Yes the routes are different after reboot and reconecting of modem.
Here is the pasted report without /32
0 S dst-address=0.0.0.0 gateway=213.180.204.3 gateway-status=213.180.204.3 recursive via 192.168.10.1 5-gw check-gateway=ping distance=1 scope=30 target-scope=30 routing-mark=to_ISP1
1 A S dst-address=0.0.0.0 gateway=93.158.134.3 gateway-status=93.158.134.3 recursive via 192.168.0.1 4-gw check-gateway=ping distance=10 scope=30 target-scope=30 routing-mark=to_ISP1
2 A S dst-address=0.0.0.0 gateway=93.158.134.3 gateway-status=93.158.134.3 recursive via 192.168.0.1 4-gw check-gateway=ping distance=1 scope=30 target-scope=30 routing-mark=to_ISP2
3 S dst-address=0.0.0.0 gateway=213.180.204.3 gateway-status=213.180.204.3 recursive via 192.168.10.1 5-gw check-gateway=ping distance=10 scope=30 target-scope=30 routing-mark=to_ISP2
4 A S dst-address=0.0.0.0 gateway=93.158.134.3 gateway-status=93.158.134.3 recursive via 192.168.0.1 4-gw check-gateway=ping distance=10 scope=30 target-scope=30
5 S dst-address=0.0.0.0 gateway=213.180.204.3 gateway-status=213.180.204.3 recursive via 192.168.10.1 5-gw check-gateway=ping distance=10 scope=30 target-scope=30
6 A S dst-address=93.158.134.3 gateway=192.168.0.1 gateway-status=192.168.0.1 reachable 4-gw distance=1 scope=10 target-scope=10
7 ADC dst-address=192.168.0.0 pref-src=192.168.0.240 gateway=4-gw-cisco gateway-status=4-gw reachable distance=0 scope=10
8 ADC dst-address=192.168.1.0 pref-src=192.168.1.1 gateway=1-green gateway-status=1 reachable distance=0 scope=10
9 ADC dst-address=192.168.5.0 pref-src=192.168.5.1 gateway=2-orange gateway-status=2 unreachable distance=0 scope=200
10 ADC dst-address=192.168.7.0 pref-src=192.168.7.1 gateway=3-blue gateway-status=3 unreachable distance=0 scope=200
11 ADC dst-address=192.168.10.0 pref-src=192.168.10.12 gateway=5-gw-asus gateway-status=5-gw reachable distance=0 scope=10
12 A S dst-address=213.180.204.3 gateway=192.168.10.1 gateway-status=192.168.10.1 reachable 5-gw distance=1 scope=10 target-scope=10
Work diferent with the /32 or without in the copy paste?
yes?
In winbox it is without /32. /32 is only in terminal “/ip route print detail” and than in copy paste.
Sorry for confusing.
I noticed that if I copy paste with or without the /32 it works different and return or not to the initial state.