Bennett 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.
However, this fork of m0n0wall is a bit unnerving. Yes, I know you have
"radically different goals," but you also have similar goals and will
face similar issues. This fork detracts from BOTH projects because
you've effectively cut the manpower for each project roughly in half
(since everyone could be working on one project instead of two) while
doubling the work (since each project will be duplicating work). And
let's not forget the user base is split, too, so each project has half
the support and testers.
You're assuming that pfSense has "half the users and testers", an
assumption that I find unlikely in view of pfSense's current status (it
has yet to be released as a production version, though that day is coming.)
Even if you're sharing some code so you're not both reinventing the
wheel, you still have to merge disjoint code as m0n0wall tries to add
pfSense enhancements into their code and vice versa.
Where the goals of pfSense and m0n0(wall) are similar, this could be
true, but the goals are more different than similar. Manuel (whom I
don't profess to speak for, so I'm willing to be corrected) wants
m0n0wall to continue to focus on small(er) embedded systems (such as the
Soekris and PC Engines boards, along with old(er) PCs), with limited CPU
(486 equivalents clocked at 100MHz), memory (sometimes as little as
64MB) and storage (there is great reluctance to increase the CF image
beyond current the 8MB 'cap'), while making no sacrifices to performance
(normally expressed in terms of throughput) on these platforms.
Thus, the "fallback" to 4.11 for the 1.2 series release after FreeBSD
5.3 failed to live up to the performance metrics of the 4.11-based releases.
Manuel describes it quite well here:
http://doc.m0n0.ch/handbook/faq-goals.html
pfSense shares none of these constraints. Indeed, in direct opposition
to m0n0wall, pfSense *is* intended to be an enterprise-ready firewall,
and *is* targeted at a class of machines with more capacity that the
constraint envelope chosen for m0n0wall. Quoting the pfSense FAQ:
pfSense requires a machine with at least a 133 MHz processor but we
suggest using a 400+ MHz machine. 128+ MB of RAM and a 1 GB minimum
hard drive space is recommended.
(pfSense can be run with less than this, of course).
As a programmer, I
know what all this patching is going to do to the code. As you exchange
code back and forth, m0n0wall is going to have some pfSense-specific
code that they'll patch to retrofit into m0n0wall and then give it back
to pfSense who will add some patches to the m0n0wall
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.
You haven't proved your assumption here. (I haven't disproved it either.)
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...
It seems a wiser course of action would be to NOT FORK and instead focus
on incorporating an enhanced packaging system within m0n0wall that would
allow users to install/uninstall features on-demand. Thus,
m0n0wall/pfSense could still be installed on embedded systems with a
streamlined core, and then expanded with additional functionality as
needed. (You could have your cake and eat it, too, but without the
fork). ;) In addition, removing unused features will help minimize
exposure to security holes.
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?
this is a troll. I won't feed the troll.
(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.)
My suggestion is that you try to be more polite.
Jim