PfSense 2.1 Floating rules for Multi Wan doesn't work.

Oliver_

@Kababayan:

Got it working!!! Using Openvpn as Wan2 with Unofficial Lusca proxy. Should work with squid.

The simple Question is, How did you achieve this goal?
Please share your knowledge with us!

greetings Oli

hyrol

Admin edit to remove harmful instructions.

DO NOT USE THAT LUSCA PACKAGE!

Capture6.PNG_thumb

Capture4.PNG_thumb

Oliver_

Admin edit to remove harmful instructions.

DO NOT USE THAT LUSCA PACKAGE!

jimp

Do not use Lusca. It changes your package repository to look at a server that is not controlled by us, and it is not kept up-to-date. There is no telling what you're actually fetching from them.

rubic

Hi, jimp!
I'm not very familiar with git and code, but I know for sure that squid multi-wan functionality in 2.0.3-RELEASE was provided by one of ermal patches (https://github.com/pfsense/pfsense-tools/commit/457052913414f7c2109fed415e66ed912a530ebe#diff-7304e60ae2121cfce1c817e216d6b95cR14, I think).
I doubt if the patch applied in 2.1-RELEASE. This could be cause of the problem discussed here.

craibo

If you switched your package repository over to lusca, because you were desperate for a solution to this and a bit of an idiot, how would you switch it back?

Thanks

ptt

https://doc.pfsense.org/index.php/Package_Manager_Settings ;)

craibo

@ptt:

https://doc.pfsense.org/index.php/Package_Manager_Settings ;)

Unfortunately, Going to the pkg_mgr_settings.php page and saving with out checking the box, doesn't revert back to the pfsnese package repository.

cheonne

@Tram:

@ptt:

https://doc.pfsense.org/index.php/Package_Manager_Settings ;)

Unfortunately, Going to the pkg_mgr_settings.php page and saving with out checking the box, doesn't revert back to the pfsnese package repository.

To restore or use original repository.
you can no longer see lusca updates

./package.sh off

pubmsu

Does anyone know how to make this work? This is probably the number one issue for many users, which is stopping them from upgrading to 2.1.

There may have been a simple bug that is not letting squid and the quick floating rule work like before.

We really need the fix!

SaFi

Hello folks,

After about 8 months past, did someone try the new release of pf (2.1.1-RELEASE) to check if the issue still exist?
for myself I've removed squid for a long time ago waiting a one's hero report that it's was fixed.
I will keeping my eyes on this topic and I will waiting that HERO

God bless all of you

hyrol

Has anyone tried pfSense 2.1.2 Release with Squid Proxy for Multi-Wan Load-Balacing.

georgio777

@hyrol:

Has anyone tried pfSense 2.1.2 Release with Squid Proxy for Multi-Wan Load-Balacing.

I am on the latest version on pfSense and there has not been a fix yet to the issue. Still suffering from the same problem.

timthetortoise

If you're only looking for failover capabilities, here's a workaround.

hyrol

@georgio777:

@hyrol:

Has anyone tried pfSense 2.1.2 Release with Squid Proxy for Multi-Wan Load-Balacing.

I am on the latest version on pfSense and there has not been a fix yet to the issue. Still suffering from the same problem.

Hi georgio777 thanks for info.

georgio777

@timthetortoise:

If you're only looking for failover capabilities, here's a workaround.

By any chance do you know if it is possible to maintain Load Balancing for all traffic except HTTP traffic and use Failover for HTTP? The reason is that if the default gateway is down, Squid will stop working, if I can take the advantages of Failover only for the Squid traffic without stop using Load Balancing, that will be great.

Thanks!

timthetortoise

You should be able to use standard gateways like normal for everything but HTTP. Floating rules are not broken, as evidenced by setting a rule for any source to any destination HTTP with the active gateway being something other than the default gateway. At this point squid is unable to pass traffic because it's trying to push it out the default gateway and it's actually being sent out another.

As long as you have default gateway switching enabled, squid will switch to that gateway when it is restarted. I've tested this and it's working great.

Daouid

Hello !
Any news?
I test an upgrade from 2.0.x to 2.1.4 and it don't work. Squid is very slow, and the http port don't work.
We can't update pfsense :-(

Thanks a lot

arclegna

Same question here, im on pfsense 2.1.4 and wondering if any solution yet to squid (no transparency) + loadbalance + failover, thanks in advance.

klazoid

I came back hoping that after one year there would be a fix but :'(
Wasting 2 lines atm as long as the default gateway doesn't go down.