As you mention multiwan you might have to recreate the pools after upgrading if you use loadbalancer pools due to the changed gui and failoverfeature. Just edit them, delete all poolmembers and readd them with the new gui logic.
Holger -----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: Thursday, February 08, 2007 6:29 AM To: [email protected] Subject: [SPAM] Re: [pfSense Support] Pfsense Server Crash On 2/8/07, Vaughn L. Reid III <[EMAIL PROTECTED]> wrote: > I have a pfsense firewall up and running with the following specs: > 3.0 ghz Pentium IV processor > 1 gigabyte of ECC (unregistered unbuffered) ram > 1 40 gigabyte western digital hard drive Tyan entry level server > motherboard with 2 onboard intel gigabyte network cards > 2 dual port pci-x intel server gigabyte network cards (4 ports total > between the two cards) > 1 single port intel desktop gigabyte network card > 1 hifn pci vpn accelerator card (from soekris engineering) > > I'm running psense 1.0.1 > I have 2 dsl connections, and 3 lan connections. I have one port > reserved for sync and one unused ethernet port. I've got about 50 > users hitting the firewall on a regular basis and have approximately 5 > vpn connections using ipsec and 2 pptp users. > > All of my ethernet cards use different irqs. The hifn card uses the > same irq as one of the embedded ethernet cards. > > Here's the problem that I'm experiencing. When I try to perform some > actions with the pfsense configuration, the machine simply stops > responding. Rebooting does not help. Even though the network stops > responding and even though the web gui stops responding, I can still > log onto the system from the console and it appears that everything is > working correctly. Specifically, the logs seem normal, ifconfig > returns the expected values and show that the interfaces are up. The > system just won't respond to pings, won't route or forward or filter > traffic, and won't allow access to the web gui. The only way that I > can seem to fix the problem is to re-install pfsense from cd and then > reload my configuration file. > > Most actions don't cause this. For example adding nat and firewall > rules, setting up pptp and ipsec connections, doing things with the > dhcp server and dns forwarder seem to work normally. > > But, specifically I have found the following items cause the lock-up > for lack of a better work. Trying to change anything under the > advanced system tab that is in under the sub heading of "Traffic > Shaper and Firewall Advanced" and trying to check or uncheck "Block > private networks" or "bogon networks" on the wan tab seems to cause > this behavior. Also attempting to check or uncheck the "Disable the > userland FTP-Proxy application" on any interface seems to cause the > behavior noted above. > > If anyone can provide some insight into this, I'd appreciate it. I've > done some searching on my own of the forums and the existing > documentation, but I can't seem to find anything that answers my questions. Please try a recent snapshot that is based on FreeBSD 6.2. More information can be found here. http://pfsense.blogspot.com/2007/01/102-beta-period-will-start-soon-5-9s .html --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
