PfSense Squid Proxy for Multi-WAN

[AMD_infinium05]

has anyone tried this on 2.0.3 ?

I have tried it earlier and I think i have messed up…... i have removed packages and revert to original settings, now my internet is working fine with load balancing, and failovers.

[vielfede]

@fabianoheringer:

For some reason, this setup not working on pfsense 2.1 and squid 3.3.4, my box was working very well with 2.0.3, but now it´s not with 2.1, any ideas?

ON
2.1-RC1 (amd64)
built on Thu Aug 15 16:30:12 EDT 2013
FreeBSD 8.3-RELEASE-p9

I solved by activating "Allow default gateway switching" option in Advanced configs (failover only) and removing all floating and NAT rules..
Hope this helps…

[Makje]

@vielfede:

@fabianoheringer:

For some reason, this setup not working on pfsense 2.1 and squid 3.3.4, my box was working very well with 2.0.3, but now it´s not with 2.1, any ideas?

ON
2.1-RC1 (amd64)
built on Thu Aug 15 16:30:12 EDT 2013
FreeBSD 8.3-RELEASE-p9

I solved by activating "Allow default gateway switching" option in Advanced configs (failover only) and removing all floating and NAT rules..
Hope this helps…

that is not solved, it still has 2 problems that aren't an issue for your specific use.
It doesn't help with loadbalancing or when someone has more than 2 WANs of which 1 WAN reallly should not do http traffic (because it is reserved for other use like VoIP, or because the ip can't be known publicly etcetera)

It really is a stupid bug in 2.1. Worse is that 2.0.x had a bug that failover doesn't work for connections like VoIP/SIP so going back isn't an option either, at least for me… really nice

[hyrol]

Finally, after a long time trying pfSense Squid Package + Multi Wan and I have managed to find its way in a deadlock.
pfSense 2.1 Squid Package + Multi Wan, no longer using the Floating Rules, but using the Interface Groups.
Good Luck Everyone.


[niebla]

Thanks, and congratulations!

What version of squid and squidguard are you using?

Please send a screenshot of your system->routing screen showing your default route.

[niebla]

Created the interface group, but how are you getting squid to use the group and not the default gateway?

[hyrol]

Still configure the same as pfSense 2.0.3 Squid Package Multi Wan, only changes to the Floating Rules to Interface Group.


[niebla]

Thanks but I am not seeing where or how you have used the interface group.

[hyrol]

Under Menu Interface

[afrugone]

Hyrol,

Many thanks, but where I use the new "Internet" interface created at "Interface Groups", I don't like to abuse of your time, but could you resume how will be the new configuration?

[hyrol]

afrugone,

What you mean, all configure same as pfSense 2.0.3 Squid Multi WANs, difference only Floating rules vs Interface Group. pfSense 2.1 not more using Floating rules for Squid Multi WANs.

[afrugone]

OK I´ll try this,

Thanks

[mohamed hafez]

@hyrol:

afrugone,

What you mean, all configure same as pfSense 2.0.3 Squid Multi WANs, difference only Floating rules vs Interface Group. pfSense 2.1 not more using Floating rules for Squid Multi WANs.

I've done as you said exactly but not working at all

[hyrol]

Actually this is not Load-Balance Round Robin, this is Load-Balance Bandwith Agreggation and you can see all the WANs its working.
It is worth it from nothing.

[pubmsu]

Hi @hyrol,

The last LAN rule screenshot you posted actually bypasses the squid altogether and sends the traffic directly to the loadbalancer gateway group. That's how you're getting bandwidth aggregation (but not squid caching).

And the interface group "Internet" is not really playing any role anywhere.

So, in summary, this does not seem to be a working solution for 2.1.x for squid plus load-balancing or failover.

[dims]

NOTE:

if you have problems with multi WAN (which may be the reason you look at this topic) you may find it senseless, because you browser can have problems with downloading images

SO SEE THIS TOPIC NOT VIA ROUTER YOU PLAN TO CONFIGURE :)