I'm biased (core dev), but pfSense is built on FreeBSD 6.2-STABLE. We're basically the userland layer (although we do have a handful of well tested - usually backported - kernel patches). What you risk by going to a non-release version is that we won't generate rules correctly (trust me when I say that'd be something we'd fix mighty quick!) or some other aspect of management. Stability of the packet forwarding is left to FreeBSD. Our release branches run release branches of FreeBSD code, we don't release from development trees (although our dev branches may be on FreeBSD dev branches...as well as pre-beta snapshots...for whatever that's worth). By the time we reach beta, we're on a release FreeBSD branch, further RC1 is a release candidate, not a beta. However, based on the fact that we've made a couple changes to the tree since RC1 came out, there will likely be an RC2 (release candidates tend to get a little more visibility in the community - and corresponding bug reports - than beta's do).
--Bill On 7/24/07, Paul Brown <[EMAIL PROTECTED]> wrote:
Will do then. I'm going to be changing out some UPS's soon (if they ever get delivered) so I'll do the upgrade then. Thanks for the endorsement of RC1. Paul On 7/24/07, Gary Buckmaster <[EMAIL PROTECTED]> wrote: > I hear this question come up just about every day and frankly it > frustrates me greatly. We've been using pfSense in production since > pre-version 1. We've had 1.2-Beta snapshots in production load > balancing a database cluster which handles 35 million requests daily, > and which is responsible for our company's day-to-day operations. It > simply cannot go offline, and so far pfSense hasn't failed us. How's > that for a production environment? > > I know that there's a general impression that Beta software is buggy and > potentially inappropriate for production. Certainly I'd never put a > Windows Beta into production anywhere, but then I try to avoid putting > Windows into production anyhow. Similarly, before putting anything into > production, use common sense. Test the solution entirely before making > the switch over. Build yourself in some failover. pfSense has a great > track record for stability and reliability. The quality of the code is > top-notch. 'nuff said. > > Paul Brown wrote: > > I can do that. I installed RC1 at home last night and I like it a lot > > but this other system is in a production environment. Given that, > > would you consider RC1 stable enough to deploy? > > > > On 7/24/07, *Scott Ullrich* <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > On 7/24/07, Paul Brown < [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > I'm running 1.0.1 and having some trouble with bandwidthd, > > installed from > > > the packages tab. > > > > > > If I try to click the link for viewing the subnet... > > > > > > Pick a Subnet: > > > - Top20 -- 172.16.2.0 <http://172.16.2.0> - > > > > > > which takes me to... > > > https://Pu.bl.ic.IP/bandwidthd/Subnet-1-172.16.2.0.html > > <https://Pu.bl.ic.IP/bandwidthd/Subnet-1-172.16.2.0.html> > > > > > > I get a 404 - Not Found. > > > > > > Also, when I click on a link to view the details for a specific > > IP in the > > > "Top 20", it takes me to a page with an address similar to... > > > > > > https://Pu.bl.ic.IP/bandwidthd/#172.16.2.207-1 > > > > > > but the content of that page is entirely the same as the "Top > > 20" page. I > > > don't get any more specific detail about that IP. > > > > > > Are these due to some misconfiguration on my end or are they > > bugs or what? > > > Thanks. > > > Paul > > > > > > > 1. Upgrade to a newer version > > 2. Reinstall package > > 3. Click save button in bandwidthd settings screen > > > > Scott > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: [EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > > > > > --------------------------------------------------------------------- > 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]
