next »

[gladizxx]

Do not worry about Dasboard load balance.
on the update 20090530-2140 Dasboard  is running normally.   

[gladizxx]

At first I pfsense system upgrade from pfsense system FreeBSD 7.1 to 7.2, in general, do not have constraints, but if there be a little sharper constraints on the traffic, namely the delay in the connection game. Whereas in the other network that uses the 7.1 setting pfsense traffic sharper the same did not experience any problems, aka running very excellent. But after I update with the latest updater (last pfsense system 7.2), everything went normal, although with the same settings before. effisient performance even more than before. so conclusion, I think, please  upgrade your Pfsense system from 7.1 to  Pfsense system FreeBSD 7.2.

Don't Worry Be Happy......

[gladizxx]

Update-1.2.3-20090612-0600.tgz I then proceed to the last updater pfSense-Full-Update-1.2.3-20090613-0129.tgz, I have a problem on the connection. There is problem in LoadBalance, causing the dissolution internet connection. Although I have been setting up pfsense GUI back problem but is also still running. 

[DeCex]

Update-1.2.3-20090612-0600.tgz I then proceed to the last updater pfSense-Full-Update-1.2.3-20090613-0129.tgz, I have a problem on the connection. There is problem in LoadBalance, causing the dissolution internet connection. Although I have been setting up pfsense GUI back problem but is also still running. 

These one kills internet on me after 1-2h of uptime. They can be call badSense, so im backflash to RC1 for now, everything works.

pfSense-Full-Update-1.2.3-20090613-0129.tgz
pfSense-Full-Update-1.2.3-20090613-0944.tgz
pfSense-Full-Update-1.2.3-20090614-0015.tgz

[jimp]

Update-1.2.3-20090612-0600.tgz I then proceed to the last updater pfSense-Full-Update-1.2.3-20090613-0129.tgz, I have a problem on the connection. There is problem in LoadBalance, causing the dissolution internet connection. Although I have been setting up pfsense GUI back problem but is also still running. 

These one kills internet on me after 1-2h of uptime. They can be call badSense, so im backflash to RC1 for now, everything works.

pfSense-Full-Update-1.2.3-20090613-0129.tgz
pfSense-Full-Update-1.2.3-20090613-0944.tgz
pfSense-Full-Update-1.2.3-20090614-0015.tgz

This was likely due to a bug that wasn't allowing the state table to clear out normally. Should be fixed in the most current snapshots.

[idelta]

bug that wasn't allowing the state table to clear out normally
You are right. Version 20090614-0015. Tried every (and many more) :
net.inet.tcp.hostcache.expire=1
net.inet.tcp.keepidle=30000
net.inet.tcp.keepintvl=5000
net.inet.tcp.finwait2_timeout=15000
net.inet.tcp.fast_finwait2_recycle=1
kern.ipc.somaxconn=32768
net.inet.icmp.icmplim=3000
kern.ipc.maxsockets=300000
net.inet.tcp.delayed_ack=1
net.inet.tcp.maxtcptw=196607

Nothing solves the problem : State table growing inevitably !
I would not like to kill more or less running system.
How do we know that the problem is solved ?

"State Timeout in seconds" in Advanced options for firewall rules also does no effect !

[jimp]

bug that wasn't allowing the state table to clear out normally
You are right. Version 20090614-0015. Tried every (and many more) :

It was fixed today, the most current updates have been confirmed to work by several people.

Try this snapshot, or later:
http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/updates/pfSense-Full-Update-1.2.3-20090614-1815.tgz

[DeCex]

Try this snapshot, or later:
http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/updates/pfSense-Full-Update-1.2.3-20090614-1815.tgz

Yey, been up over 2h now, i guess is fixed, thanks

[gladizxx]

After I upgraded to version 1.2.3-20090614-0015, all with normal pfsense running back, then I upgrade to the latest version 20090616--0034 Pfsense running very wonderfull, internet connection the more aggressive, Load Balance running optimally, as if the entire resource that have empowered perfectly. While the IP Sec're setting me back, because of internal reasons. From there I use my old Pfsense, once I find new problems, while the rest are internal constraints on me.  

[gladizxx]

It seems PFsense, near the start .... stable release ....   

[Sylhouette]

I use RC2
1.2.3-RC2
built on Wed Jun 24 00:36:43 EDT 2009

It runs on a soekriss 5501, but after a couple of days it stalls, no traffic is coming through any more.
I can still ping the box but it hangs.
only a power cycle gets it going again.

It is my main router so i can not investigate the state and need to reboot as quickly as possible.
Is has 3 interfaces enabled.
vr0 LAN
vr1 WAN pptp
vr2 DMZ

Further more nothing special.
No traffic shaping load balance or other stuff.

I use revert back to 1.2  now to make sure i get no calls in the evening about a dead router.

No complains, just an observation!

regards,
Johan

[gladizxx]

I have several multi wan router, which I apply on some SOHO multiclient. I always update the pfsense 1.2.3. RC2 latest updater, ( http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/updates/ ). In fact I have never experienced problems with the router, all interface with the normal running. The only true version of the updater prior to the current still found the log loadbalance (as in the sticky ( http://forum.pfsense.org/index.php/topic, 16671.0.html ) and I really understand it, because it does not disrupt the performance of the router in general. And up to now all of my router is running normally, without any obstacles that means.


Not trying to defend. 
just the story of the fact that I experienced.   

THKS

[Sylhouette]

i think i have been bitten by the following:

http://cvstrac.pfsense.com/tktview?tn=1935

regards,
Johan

[pfsense_fan009]

It seems PFsense, near the start .... stable release ....   

changes from 16juni?

which version is the latest working? (the latest gives me a huge problem,can't do anything anymore)

[gladizxx]

One Pfsense  used for the Multi-WAN, Multi-LAN (wireless, openvpn) can run Load Balance with Normal. Just log on the load balance constraints are still there .....