Are sticky connections working in 2.0 or do I have another problem?
-
I went ahead and took the plunge and upgraded from 1.2.3 to 2.0. So far so good, no problems whatsoever. I enabled sticky connections and my machines were able to browse the web for 2 or 3 sites and then nothing. Every attempt to load a page failed.
-
I have the same problem with using sticky connections, however i'm with 1.2.3 release.
My suggestion is if your config is not too complicated to reset to factory defaults and then do a fresh set up.
-
Sticky definitely doesn't work with multi-WAN in FreeBSD 7.x (pfSense 1.2.x), and I don't think it works in FreeBSD 8 (2.0) either. It's something we need to look into.
-
So if you're using multi-WAN in ANY pfSense build, you should disable sticky connections? That seems like a rather glaring detail that should be noted on the appropriate configuration page.
-
I Did a reply at http://blog.pfsense.org/?p=186 to "Michael in July 1st, 2008 at 11:59 am". But the moderator has informed that the forum would be the more apropriate place. So here we go:
Hi, I'm with pfSense 2.0 and I have the exact problem that Michael has described.
My setup
WAN1 = static ip via radio connection (no PPPoE) - tier1
OPT1 = DHCP via cable connection - tier 1
OPT2 = static ip via other radio connection (no PPPoE) - tier2This issue can be saw by accessing www.whatsmyip.org. I have problem when 'sticky connection' is activated. The outbound traffic just does not work when going out by OPT1. I only see the WAN1 IP and half of the connections fails (OPT1 connections).
When I dissable the 'sticky connection' everything goes OK. I can see both IPs at the www.whatsmyip.org and no connections fails.
I'm using pfSense 2.0-BETA1
built on Wed Mar 24 09:56:45 EDT 2010
FreeBSD pfsense.mii.com.br 8.0-STABLE FreeBSD 8.0-STABLE #0: Wed Mar 24 07:38:52 EDT 2010 sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense.8 i386There is some more information that I could give to you about this?
Thanks
-
known issue, there is a ticket open: http://redmine.pfsense.org/issues/show/337