El 04/09/13 17:22, Thomas Harold escribió:
On 8/26/2013 6:41 AM, Nishant Sharma wrote:
Hi Thomas,
Thomas Harold wrote:
In an instance where you have a single instance of squid running on
a two WAN links as WAN
#2
is very slow compared to WAN #1.
Is this simply handled by changing the defaul
On 8/26/2013 6:41 AM, Nishant Sharma wrote:
Hi Thomas,
Thomas Harold wrote:
In an instance where you have a single instance of squid running on a two WAN
links as WAN
#2
is very slow compared to WAN #1.
Is this simply handled by changing the default gateway of the server
using the "ip route"
On 27/08/2013 5:09 a.m., Thomas Harold wrote:
On 8/26/2013 6:41 AM, Nishant Sharma wrote:
Hi Thomas,
Thomas Harold wrote:
In an instance where you have a single instance of squid running on
a two WAN links as WAN
#2
is very slow compared to WAN #1.
Is this simply handled by changing the def
On 8/26/2013 6:41 AM, Nishant Sharma wrote:
Hi Thomas,
Thomas Harold wrote:
In an instance where you have a single instance of squid running on a two WAN
links as WAN
#2
is very slow compared to WAN #1.
Is this simply handled by changing the default gateway of the server
using the "ip route"
Hi Thomas,
Thomas Harold wrote:
>In an instance where you have a single instance of squid running on a two WAN
>links as WAN
>#2
>is very slow compared to WAN #1.
>
>Is this simply handled by changing the default gateway of the server
>using the "ip route" commands when we detect that WAN#1 is
In an instance where you have a single instance of squid running on a
system with two WAN links, how would you configure things so that squid
will default to proxying all traffic from the LAN to WAN#1, but fallback
(failover) to WAN#2 if WAN#1 is down?
We're not interested in load-balance betw
