I Agree, and specially on FreeBSD. In fact, we have pretty complex configurations with about 25 vlans per firewall and on top of these, we have Carp Interfaces. We used to have FreeBSD but when manipulating the carp interface, we would regularly face Kernel Panic.
We decided to switch to OpenBSD. From now on, we don't have any problem anymore. Our Firewalls are used in production and a reboot is not acceptable for us. I never experienced any kernel panic or any kind of necessity to reboot the router. Would be nice to have a pfsense on an OpenBSD instead. OpenBSD made carp and pf :) Léo -----Message d'origine----- De : Chris Buechler [mailto:[EMAIL PROTECTED] Envoyé : mercredi 28 novembre 2007 22:42 À : [email protected] Objet : Re: [pfSense Support] Symlink gone after power outage Paul M wrote: > > when I first started using pfsense with rc1, it was so unstable when > either configuring CARP or expecting CARP to failover that the machine > would crash or lockup and would nearly always lose the config.xml. > > even RC2 when changing carp interfaces can still crash pfsense, and I > would have to manually recover the config.xml. (this is on regular x86 > server)... > > Destroying CARP interfaces causes a panic and always has. I don't know when the change was made (it was pre-RC2 for sure), but we force a reboot after the removal of CARP interfaces (we don't destroy them) to prevent ever triggering this panic, because it was exceptionally good at causing file system corruption because it happened at the same time the configuration was being written. If you can do something in the GUI to reliably trigger a panic, please let us know exactly how to replicate it. I've never heard of failovers causing a panic, and the conditions with CARP that do cause panics should no longer be possible in the webGUI. --------------------------------------------------------------------- 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]
