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?
[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?
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] transparency Squid very slow internet
Guillaume Chartrand wrote: Hi I run squid 2.6.STABLE12 on RHEL3 AS for web-caching and filtering my internet. I use also Squidguard to block some sites. I configure squid to run with WCCP v2 with my cisco router. So all my web-cache traffic is redirected transparently to squid. I don't know why but when I activate the squid it's really decrease my internet speed. It's long to have page loaded, even when it's in my network. I look with the command top and the squid process run only about 2-3 % of CPU and 15% of Memory. I also run iftop and I have about 15 Mb/s Total on my ethernet interface. I don't know where to look in the config to increase the speed. I use about 50% of disk space so it's not so bad Another possible issue is that squid is having to wait on a slow DNS server. Take a look at the mgr:info report: $ /usr/sbin/squidclient mgr:info And look at Median Service Times section. In our case, DNS lookups were in the 5+ second range, due to the primary DNS server being broken. So squid was asking the primary DNS server, waiting 5 seconds, then asking the backup DNS server. A normal squid server will be servicing all requests in under 1 second (depending on your load).
