On 11/27/05, Bennett <[EMAIL PROTECTED]> wrote:
> I've been looking for an open source firewall.  I found m0n0wall, IPCop,
> and few others.  I thought m0n0wall was great, but then I came across
> pfSense, and it was even better, picking up where m0n0wall left off.

I think you just summarized the fork right here.  "Picking up where
m0n0wall left off" - if this was m0n0 with a few patches here and
there, it wouldn't pick up where m0n0 left off, it'd be m0n0+patches.

> patches...Eventually, this bloated mess of patches is so convoluted that
> no one knows how it works and you're on your way to security holes and
> compromised networks.

m0n0 has a concept of a single administrator (as currently does
pfSense).  Unless the OS or web server has a remote vulnerability I
don't see any merit to your claim.  We are adding xmlrpc functionality
which will over time increase the security risk of an exposed GUI, but
until multiple administrators are added, that's not much of a risk
increase (same auth code).

> Thus, either you've doubled the work with half the developers/testers or
> you've doomed the code to buggy patches on top of patches.  This makes
> me question the founders of pfSense...Did they not foresee this when
> they decided to fork?  And these short-sighted individuals are who I am
> counting on to protect my valuable network?  Or is this some sort of ego
> thing?  Did the other m0n0wall programmers hurt their feelings so they
> ran off and made their own little project?  Or maybe the m0n0wall
> developers are unreasonable jerks and so pfSense politely forked rather
> than bash heads.  But those unreasonable developers are the ones who
> wrote the original m0n0wall code that you're using...

Never used m0n0, so I can't really speak about the original fork.  I
can however say why I started submitting patches to pfSense and not
m0n0.  pfSense uses pf, a filter software that I am comfortable with,
like, and has features far greater than ipfilter has.  I stumbled onto
pfSense after purchasing a 4801 and finding that the only embedded
firewall project ran ipfilter, which I didn't want to run, and had
started to write my own (for myself, it would have NEVER been
released).  To be frank, I work on pfSense BECAUSE it uses pf.  If
m0n0 switched today, I'd probably still stick with pfSense
development, I know the codebase pretty well, I like it's openness.  I
also see a lot of issues in the codebase, stuff that I'd like to
rewrite, stuff that once rewritten will have zero chance in hell of
being backported to m0n0 or receiving further updates from m0n0. 
Again, an example of how the fork is going it's own way and developing
it's own code, not just patches.


> So, having said all that, why should I consider pfSense for my firewall
> when it's written by a bunch of unreasonable jerks and short-sighted
> egoists who are churning out a insecure, bloated spaghetti?  (Please
> don't get me wrong--I plan on using pfSense to secure my network and
> most likely at least two of my clients' networks, too.  I'm just looking
> for answers to quell my concerns.)

I've got a better idea.  After all you've said, why are you choosing
pfSense over m0n0?  What have we done right that's made you want to
choose pfSense over m0n0?  I assume we've done _something_ right for
you to choose an alpha project over a released product.

--Bill

Reply via email to