[squid-users] Load balancing WITHOUT parents over multiple WAN connections

[Jon DeLee]

*This message was scanned for all current viruses and is certified clean*


Hi All,

I'm using Squid 3.0. STABLE 8 as my main cache, and I have two other 2.7 
caches set up, one on each WAN connection.  The only reason we have 
multiple proxy servers is to load balance; in reality I only need the 
one 3.0 server, which has access to both WAN links. 

I don't want any ACLs that force one group of users to one outgoing IP; 
I just want Squid to see that it has two paths to the internet and use 
them in a weighted round-robin fashion. 

I have tried setting up one direct and one parent, but no weighting 
occurs because Squid prefers direct routes if possible.


I have tried to force squid to use an IP address on the machine and set 
up multiple weighted routes from that IP, but strange things happen with 
web sites that check source IP address, so it needs to be something that 
Squid can control.



Any suggestions?

Thanks,

Jon DeLee

[squid-users] 2.7STABLE6 weight has no effect - weight not working

[Jon DeLee]

*This message was scanned for all current viruses and is certified clean*


I  upgraded 2 days ago from 2.7.STABLE5 to 2.7.STABLE6 due to complaints
about hotmail hanging.  I have 3 squid servers, and I updated all 3 at
the same time.  I use one as the primary in a transparent mode, and it
is forced to make requests from the other two parents, which are on
different connections to the internet.  This gives me a way to load
balance between two connections.

Anyway, the weighting was working great until I upgraded.  After I
noticed the problem, I made sure that I was seeing ICP packets coming
from the primary to both parents, and they were, and ICP packets are
coming back from the parents.  The primary would always use the closest
parent, no matter the weight setting.  I went back to 2.7.STABLE5 on the
primary and the problem disappeared.

I found a reference to bug 2241, which seems to address this issue, but
the patch for neighbors.c appears to patch a different version than the
2.7.STABLE6 source that I built from.  It does appear that 2241 has been
incorporated into Squid 3.

Is Squid 3 mature enough to simply migrate to with my setup?  Or should
I continue to try to patch 2.7S6?  If so, how can I patch from a
different source version?

Thanks in advance,

Jon