You should be careful of doing any kind of network latency sensitive
work with providers such as OVH. The latency of their networks can be
very unstable.
You can end up in a flip flopping state very easily.
On 15 November 2013 03:43, Mihamina RKTMB <mihamina@xxxxxxxxx> wrote:
> Hi,
>
> At office, we have I ISPs.
>
> I want to lightly monitor each link latency in order to decide several
> routing.
> For that, I have only one external server: 1 IP, it's an OVH dedicated
> server.
> The quick picture is http://s24.postimg.org/n3436z64l/defaul_route.png
>
> Default route is via ISP1.
> If OVH-server pings IP1:
> - the request will go through ISP1: it's OK
> - the reply will go through ISP1: it's OK
>
> If OVH-server pings IP2:
> - the request will go through ISP2: it's OK
> - the reply will go through ISP1: it's KO because the metric will
> involve ISP1
>
> How could I tell the Office gateway (CentOS 6)
> "IF you reply to a ping request from the OVH server that came on IP2
> THEN route it via IP2"
>
>
>
> --
> +261 34 81 738 69
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
