SQUID and Load Balancing doesn't work!!!! I tried for a week but nothing :'(

max_ens

i think its better you try tcp_outgoing_address, cause one line for normal http ant other for downloads and youtube never lose the connection cuz the internet no get all bandwith and only the line with the downloads and videos get slow, in other way you try also put 2 computers with pfsense one lb and other with squid

eri--

Does it work with dynamic addresses tcp_outgoing_address?

OyyoDams

@ermal:

For those of you who still want to try this.
I added a fix which should be presented on latest snapshot to help with this.

Yeah thank you very much erman !

I just tried with the latest snapshot and it works.

My floating rules work. Of course I had to add outbound NAT rules, so now a very good thing you could add is aliases in outbound rules ! :)

n1ko

How about writing a howto about how to get it working? Have you tested failover?

OyyoDams

@n1ko:

How about writing a howto about how to get it working? Have you tested failover?

I'll try to write a howto later, but I haven't tested failover. In fact, my WAN interface goes directly to my ISP, and my OPT1 is an openvpn connexion to an alternative ISP.
Default gateway is WAN, but when the VPN connexion is established, the default gateway becomes OPT1.
So my goal was to route some addresses to WAN instead of OPT1 from the pfsense itself, because I use squid as transparent proxy, so http traffic is generated by pfsense, and so standard firewall rules (from LAN) can't be applied.

In my case here is how I got it to work:

add a floating rule with specific address as destination, and WAN gateway to force traffic on this gateway instead of OPT1
add a virtual IP alias on WAN interface, in WAN network range
add an outbound NAT rule, interface OPT1, source any, destination "the same specific address", NAT address "the virtual IP"

This last point is important, because if you only set the floating rule, traffic is sent from WAN interface, but with OPT1 address as source.

My english is not very good, so here is an example.
Imagine you want to reach http://my-i-p.com/ from WAN instead of VPN (OPT1) interface:
my-i-p.com ip address is 74.86.20.234

See step1 picture for floating rule
My WAN ip address is 192.168.0.1, let's add a virtual IP (for example 192.168.0.30) on this interface: see step2 picture
See step3 for NAT rule

Hope that helps you :)

step1.jpg_thumb

step2.jpg_thumb

step3.jpg_thumb

vito

Does anyone have this working with Squid and HAVP?
thanks

nassman

Please i need the arrange steps, how to setup squid with load balance

heper

@nassman:

Please i need the arrange steps, how to setup squid with load balance

i'm having the same problem …. once i figure it out with ermal's help i'll write a simple how-to.

for now all i can accomplish is failover with custom scripting.
with the latest snapshot its possible to use the tcp_outgoing_adress directive in squids config in combination with a floating rule to get it working. changing the outgoing adress from WAN1 ip to WAN2 ip when either of them goes offline should be possible with fairly easy scripting.

i haven't been able to get any loadbalancing to work tho ... but its very well possible i just don't have enough braincells

nassman

I try apply the above setting, but i fail, the load balance and squid not work.
why not there any standard documents?

jimp

@nassman:

I try apply the above setting, but i fail, the load balance and squid not work.
why not there any standard documents?

Because nobody that has made it work has taken the time to write out any. :-)

It's a new feature of 2.0 and only recently has it been proven to work at all for some people… Once the config is documented it'll be on the doc wiki, but until someone in a position to (a) make it work and (b) write it out in a way people can follow, some patience is needed.

nassman

thanks

heper

@jimp:

@nassman:

I try apply the above setting, but i fail, the load balance and squid not work.
why not there any standard documents?

Because nobody that has made it work has taken the time to write out any. :-)

It's a new feature of 2.0 and only recently has it been proven to work at all for some people… Once the config is documented it'll be on the doc wiki, but until someone in a position to (a) make it work and (b) write it out in a way people can follow, some patience is needed.

Would you happen to know who those people are who got it to work, and how to get in touch with them ?

OyyoDams

@OyyoDams:

I'll try to write a howto later, but I haven't tested failover. In fact, my WAN interface goes directly to my ISP, and my OPT1 is an openvpn connexion to an alternative ISP.
Default gateway is WAN, but when the VPN connexion is established, the default gateway becomes OPT1.
So my goal was to route some addresses to WAN instead of OPT1 from the pfsense itself, because I use squid as transparent proxy, so http traffic is generated by pfsense, and so standard firewall rules (from LAN) can't be applied.

In my case here is how I got it to work:

add a floating rule with specific address as destination, and WAN gateway to force traffic on this gateway instead of OPT1

add a virtual IP alias on WAN interface, in WAN network range

add an outbound NAT rule, interface OPT1, source any, destination "the same specific address", NAT address "the virtual IP"

This last point is important, because if you only set the floating rule, traffic is sent from WAN interface, but with OPT1 address as source.

My english is not very good, so here is an example.
Imagine you want to reach http://my-i-p.com/ from WAN instead of VPN (OPT1) interface:
my-i-p.com ip address is 74.86.20.234

See step1 picture for floating rule

My WAN ip address is 192.168.0.1, let's add a virtual IP (for example 192.168.0.30) on this interface: see step2 picture

See step3 for NAT rule

Hope that helps you :)

This works on 30th november build. But it doesn't work with latest build (16th january).
It's very strange:

I didn't change anything in my configuration
I can't ping any address through WAN (i.e. 74.86.20.234)
When I launch tcpdump, I see ping and echo reply, so the packet is sent and received back, but ping command doesn't see it
When I revert back to 30th november it works again

Any idea ?

eri--

Anybody please upgrade to a snapshot of Feb 9 and after and just create a floating rule with direction out and a gateway pool and activate AON with source put to any.