PfSense 2.1 Floating rules for Multi Wan doesn't work.
-
I problem in the floating for multi wan, after I upgraded to version 2.1, it does not work.
 -
I'm not entirely sure but that rule looks fundamentally wrong in the first place. You've created a floating rule with direction Out on a WAN interface. This means by the time the rule fires, NAT has already occured and a gateway has already been chosen.
Just create a normal Internet access rule on the LAN interface and set the gateway there. There is generally no need for floating rules for multi-WAN conditional gateway selection.
You rule is just for HTTP, so simply create a new Internet access rule on the LAN interface above the existing one and set the destination port to HTTP.
-
previously no problems during pfSense 2.0.3, you can refer to this link.
-
It doesn't matter. The floating rule seems overly complex and unnecessary when a simpler solution achieves the same thing.
-
Need floating rules for squid multi wan, have any idea without floating rules.
-
Are both your gateways on the same WAN interface or do you have 2 WAN interfaces each with their own gateway?
Your rule specifies "WAN" so it's only going to fire after traffic has already been translated to "WAN"'s public IP address. There is no question of "WAN2" ever being used. If it worked before, it sounds like it was thanks to a bug that has now been fixed.
Unless you can somehow make the OS itself use the "LoadBalancer" gateway I don't see how it could work. You should probably install Squid on a separate box and use a conditional gateway rule on that interface for incoming traffic from Squid.
-
Try selecting both WAN and WAN2 in the floating rule. IMO it still shouldn't work since NAT has already taken place, but try your luck.
-
I don't see where that rule would have ever done anything since quick isn't checked, the default pass out rules will override it.
-
My knowledge, squid works only in WAN, that's why i need Floating rules for multi wan work in squid.
-
i have the same problem. In pfsense 2.03 i can use all my wan with squid. In pfsense 2.1 squid only use default wan.
In 2.03 i use directive tcp_outgoing_address 127.0.0.1 in squid and add a floating rule with quick flag on that pass the traffic from the default gateway to a gateway Group.How can do the same in pfsense 2.1
thanks.
-
some problem…i cant fix it...much people wait fix that...in my country...
-
maybe squid proxy not compatible for pfsense 2.1.
-
Not sure what's the "me too" stuff about. If you are creating the broken rule without "quick" checkbox, it will not ever apply, as noted by cmb.
-
Hi doktornotor, hyrol
I understand from the thread that the rule was working due to a "bug" prior to 2.1, however is there another way to get Squid to use a Multi WAN Loadbalancing gateway?
The rule may have been a bug but it was a great help!!Kind Regards and thanks in advance
P.S hyrol thank you for your Squid with Load balancing solution it has worked brilliantly for me prior to upgrading.
-
Which part of "you must tick the quick checkbox" for the rule to have any effect is unclear?
-
That does not fix the problem of the load balancing. Does the same as if it wasn't checked…
-
scusa non capisco provo a postarti le cose che ho fatto
alias : host(s) e poi sotto ho aggiunto www.speedtest.net
ruels : Pass - LAN - IMCP - any - 192.168.0.15 - speedtest.net - GTWOPT1la regola l'ho messa anche in varie posizioni ma non va se vado su speedtest mi mostra l'ip della WAN e non della OPT1 e funziona se spendo la WAN mi va in failover e solo in quel caso va in OPT1
ma la mia domanda era oltre a fare la regola su ruels devo fare qualcosa su out/nat ecc ecc?
-
Uh, English please!
-
I have been using another method "Use sticky connections", but not Load Balacing i want, it is just temporary use.
 -
i stuck that problem to 2.1
squid - (wpad configured) - loadbalance not working.
