James A. Robbins wrote: > > I'm trying to understand what commercial firewalls have that ipfilter > doesn't (besides a pretty GUI). Are there specific packet inspection > technologies in products like PIX or Checkpoint that aren't present in > ipfilter? I've never used a commercial firewall product (only > ipfilter for 6 years), so I'm wondering what I'm missing :-) >
I would comment here that it's not necessarily "Commercial vs IPFilter" Such a comparison implies that IPFilter, and it's other open-source peers have an inability to have a certain subset of features because they are not commercial (and to be *really* technical, I think you mean proprietary, not commercial, which I believe simply means that it's marketed, and with all the marketing linux gets, you could say IPTables gets said marketing as well). But the truth, at least as I see it, is that different firewalls have different features, and those differences are (for the most part), independent of whether they are free or not[1]. IP Filter has things that Checkpoint doesn't, and CP has things IPF doesn't, and IPTables has things that FW1 doesn't, which has things IPF doesn't, which... [1] There is one exception to that - Proprietary firewalls' features will have "stunted" growth in an area that it's customers don't necessarily use as much. Free firewalls' features will be limited by time of the author who has a full-time job, and a life, and does the world a huge-ass favor by building one of the greatest firewalls I know without getting paid for it. Therefore it's "stunted" growth is more likely to be in areas the author personally doesn't find as important. But my point is, while you can point out the above trend, you still can't say "see, IPFilter lacks (and always will lack) feature X because it's not proprietary" Just a thought. Phil -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, 1759
