We do this on several but it take a min or two for all client packets to
find its way out on good connection.
Clearing the arp usually will force the clients to all start using the
better connection until the other comes back.
I use netwatch to clear the arp but thats all
On 09/08/2016 09:16 PM, Judd Dare via Mikrotik-users wrote:
In your routes to the 3 different wan networks:
/ip route
add check-gateway=ping distance=1 dst-address=10.10.0.0/16
<http://10.10.0.0/16> gateway=10.81.35.193 pref-src=10.81.35.1
Set a preferred source (pref-src) to the public IP address on your WAN
ports and have check-gateway set to ping. If the remote gateway
(10.81.35.193) is not responding to pings, then the route goes down
and the other routes out your other WAN ports should still work.
On Thu, Sep 8, 2016 at 7:55 PM, OWS Optimum Wireless via
Mikrotik-users <[email protected]
<mailto:[email protected]>> wrote:
Thanks for replying.
Judd, I don't understand clearly what you mean. Is it creating a
script and run it with scheduler?
On Thu, Sep 8, 2016 at 9:43 PM, Judd Dare <[email protected]
<mailto:[email protected]>> wrote:
Change your preferred source on the gateway check and have it
ping the other side or something on the internet. No need to
go crazy on netwatch.
On Sep 8, 2016 7:35 PM, "OWS Optimum Wireless via
Mikrotik-users" <[email protected]
<mailto:[email protected]>> wrote:
Hello.
I'm trying to create a fail-over script to prevent outage
in our network. We have 3 WANs which are balanced with
PCC. The check-gateway=ping option in route doesn't work:
sometimes the gateway (modem) is up but, is not connected
to internet and that causes problems.
What I'm trying to do is create a script to disable mangle
rules if a line goes out:
- I created a static route for each WAN,
/ip route add dst-address=8.8.8.8 gateway=GW1 distance=1
/ip route add dst-address=8.8.4.4 gateway=GW2 distance=1
/ip route add dst-address=OTHER gateway=GW3 distance=1
Also have default routes for each GW with different
distance: 2,3,4.
The marked connections as well with marked routes.
The balance works well but, can't get the netwatch tool
change up/down state if I have a default route, which is
needed for DNS.
If I even unplug one of the GW/Modem cable netwatch still
have that link as up.
How can I force ping from the RB to 8.8.8.8 from/using a
specific route so I can test or disable the mangle rules
via a script ?
Please guide me to where I can get an idea or if someone
here has something similar.
Thanks in advanced for your time and help.
_______________________________________________
Mikrotik-users mailing list
[email protected] <mailto:[email protected]>
http://lists.wispa.org/mailman/listinfo/mikrotik-users
<http://lists.wispa.org/mailman/listinfo/mikrotik-users>
_______________________________________________
Mikrotik-users mailing list
[email protected] <mailto:[email protected]>
http://lists.wispa.org/mailman/listinfo/mikrotik-users
<http://lists.wispa.org/mailman/listinfo/mikrotik-users>
_______________________________________________
Mikrotik-users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/mikrotik-users
--
_______________________________________________
Mikrotik-users mailing list
[email protected]
http://lists.wispa.org/mailman/listinfo/mikrotik-users
