Re: [squid-users] One squid instance, two WAN links, how to failover from primary to secondary link?
On 8/26/2013 6:41 AM, Nishant Sharma wrote: Hi Thomas, Thomas Harold thomas-li...@nybeta.com 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 down? Yes, it should work that way. Simple and easy. Is it necessary to restart or reload squid when the default routes change?
Re: [squid-users] One squid instance, two WAN links, how to failover from primary to secondary link?
El 04/09/13 17:22, Thomas Harold escribió: On 8/26/2013 6:41 AM, Nishant Sharma wrote: Hi Thomas, Thomas Harold thomas-li...@nybeta.com 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 down? Yes, it should work that way. Simple and easy. Is it necessary to restart or reload squid when the default routes change? You can balance with ip route with nexthop with different weights for each link and change to a one link only route if the other fails. You only need to restart if DNSs change, if you have a local DNS no restart is needed cause for squid the DNS will be always localhost
[squid-users] One squid instance, two WAN links, how to failover from primary to secondary link?
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 between the 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 down?
Re: [squid-users] One squid instance, two WAN links, how to failover from primary to secondary link?
Hi Thomas, Thomas Harold thomas-li...@nybeta.com 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 down? Yes, it should work that way. Simple and easy. Regards, Nishant -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [squid-users] One squid instance, two WAN links, how to failover from primary to secondary link?
On 8/26/2013 6:41 AM, Nishant Sharma wrote: Hi Thomas, Thomas Harold thomas-li...@nybeta.com 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 down? Yes, it should work that way. Simple and easy. I'm guessing that balance_on_multiple_ip should be set to off as well, to keep squid from balancing across both WAN links? http://www.squid-cache.org/Doc/config/balance_on_multiple_ip/ It's not clear what the manual means when it says Modern IP resolvers in Squid sort lookup results by preferred access. By default Squid will use these IP in order and only rotates to the next listed when the most preffered fails. What is preferred access? Is that defined somewhere? Or does that mean the preferred routes defined by the TCP/IP network stack?
Re: [squid-users] One squid instance, two WAN links, how to failover from primary to secondary link?
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 thomas-li...@nybeta.com 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 down? Yes, it should work that way. Simple and easy. I'm guessing that balance_on_multiple_ip should be set to off as well, to keep squid from balancing across both WAN links? balance_on_multiple_ip has nothign to do with Squid and WAN links. It is balancing requests over the different remote IPs when a website lists more than 1 IP in its DNS results. Otherwise known as client-based load balancing. http://www.squid-cache.org/Doc/config/balance_on_multiple_ip/ It's not clear what the manual means when it says Modern IP resolvers in Squid sort lookup results by preferred access. By default Squid will use these IP in order and only rotates to the next listed when the most preffered fails. What is preferred access? Is that defined somewhere? Or does that mean the preferred routes defined by the TCP/IP network stack? http://www.squid-cache.org/Doc/config/dns_v4_first/ Amos
