Squid and Multi-WAN
-
I currently have a setup where I'm aggregating 4 DSL WAN circuits for our office of about 200 users. On a good day, they're using about 50% of the capacity. I added the Squid module into the mix to reduce WAN traffic even more. Early on, as the Squid cache was being built, everything seemed to work OK, but in the last few days, virtually all my WAN traffic is being funneled into a single outbound pipe, which happens to be whichever one is defined as the default gateway. As a result, the link is being saturated and internet performance sucks for my users. As soon as I disabled Squid, it started sending everyone around the different circuits and everything worked great. Turned Squid back on, and it's going back out the Default Gateway link and nothing else.
Is Squid not aware of the multi-WAN routing?
-
I know the 1.2 version is totally unaware of multi-wan, it does exactly what you describe. I don't know if 2.0 fixes that.
-
Apparently not.
-
It can be made to work on 2.0, there are several threads on the 2.0 board about it. It's not exactly a simple process, but it works.
-
Could you elaborate a little more on where those can be found? I'm not having much luck with the search capability, it's pretty much coming up with a number of posts that aren't relevant.
-
Here's one:
http://forum.pfsense.org/index.php/topic,33895.0.htmlGoogle search works on the forum, too.
