PfSense 2.1 Floating rules for Multi Wan doesn't work.
-
The problem is squid is using the default route and does not care about interface groups. What am I missing?
-
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.
-
How does Squid know to use the interface group instead of the default gateway?
-
I do not know how Squid works, most importantly it works. ;)
-
Squid works with multi-wan on 2.0.3 by using floating rules. Users have reported that it is not working with 2.1 with multi-wan even when using floating rules.
Many users are looking for a way to use multi-wan and squid using 2.1.
When this is solved many of us who have squid and multi wan will be able to use 2.1, and be grateful to the person who provides the solution.
-
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.I have followed the same steps but all in vain,
squid still uses only default gateway :( does not work with Interface Groupstill waiting to fix it…
-
If you check whatmyip you can see only default WAN, but you can see all the WANs work together.
Note: This Load-Balance Bandwith Agreggation not Load-Balance Round Robin.
-
My tests show that squid is only using the default gateway. I understand and have the interface group. It can be used by rules but is not being used by squid, which has a large majority of our traffic.
-
pfSense 2.1.1 soon be out, hoping the problem will be solved.
-
I'm not sure if 2.1.1 wil fix something abaout this, JIMP answer that they don't now the problem, https://forum.pfsense.org/index.php/topic,71546.msg391065.html#msg391065, perhaps any you that have a better understanding than me about this problem can add bug ticket.
-
I don't think it's an issue or bug in pfsense 2.1 multi-wans and proxy (squid), but it's seems that there is a mess-configuration in squid to does not use multi-wan and still sticking using default gateway.
http://wiki.squid-cache.org/SquidFaq/NetworkOptimizations
-
Bottom line: There is no solution for this issue so far. We have to keep pfSense 2.0.3 until somebody comes with a final solution. Hope the gurus to figure this out.
Thanks.
-
compare /tmp/rules.debug on 2.0.3 where it works and on 2.1 where it doesn't, the answer may lie there. The config would have to be identical for it to be a valid comparison.
-
Got it working!!! Using Openvpn as Wan2 with Unofficial Lusca proxy. Should work with squid.
-
Great and congrats .. Actually pfSense 2.1 is not stable for me sometimes it works, after reboot it does not work, a few hours later it works, sometimes it do not work. :'( :'(
-
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
-
Admin edit to remove harmful instructions.
DO NOT USE THAT LUSCA PACKAGE!
-
Admin edit to remove harmful instructions.
DO NOT USE THAT LUSCA PACKAGE!
-
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.
-
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.
