Correct, it is a fork of m0n0. I'm not sure what the differences are though.
Can someone tell me why IPCop and Smoothwall look 100% identical? What's the deal there? On 1/3/07, bogi <[EMAIL PROTECTED]> wrote: > It sure looks very capable, maybe we could do a presentation on it in the near > future, I know, it is not linux, but it is open source for sure :-) > It looks like a fork of m0n0, only double the functionality, very intresting. > > I have also stumbled yesterday upon a Endian firewall, > http://www.endian.it/en/community/ > Yes i know it is Italian, just got the iso yesterday, will give it a whirl and > tell you more about it. We could stitch a full presentation of these 2 > firewalls including the extra features and a live demo of both one of those > days. > > Cheers > Szemir > > On January 3, 2007 02:25, Gustin Johnson wrote: > > I find pfsense to be more elegantly designed than IPCop. IPCop is good > > for a generic firewall/router, but I find it very awkward to customize > > it beyond the default install. IPCop's shortcomings become quite > > evident when you have a bunch to manage. Plus outbound filtering > > requires a mildly clumsy hack with ipcop, not so with pfsense. > > > > Pfsense also does failover (it can handle two concurrent ISPs), it can > > also cluster for HA, all out of the box. These are things that IPCop > > cannot do. > > > > Mitchell Brown wrote: > > > I find that the firewall configuration in m0n0wall is more convoluted > > > then in IPCop. It doesn't open ports automatically, etc. It's just > > > clumsy imho. > > > > > > On 1/2/07, Gustin Johnson <[EMAIL PROTECTED]> wrote: > > > While both are excellent Open Source projects, neither really fits as a > > > presentation for the Calgary *LINUX* Users Group :) > > > > > > Interestingly enough, I prefer pfsense to IPCop, I have a box that can > > > be used as a demo. Maybe better for a show'n tell meeting. > > > > > > Mitchell Brown wrote: > > >>>> PFSense? m0n0wall? > > >>>> > > >>>> Monowall, while cumbersome to install, is amazing. > > >>>> > > >>>> On 1/2/07, Shawn <[EMAIL PROTECTED]> wrote: > > >>>> IPCop was presented last May - http://www.clug.ca/node/413 > > >>>> > > >>>> It hasn't really changed much since then, so I personally think a > > >>>> different presentation is in order... :) > > >>>> > > >>>> Shawn > > >>>> > > >>>> bogi wrote: > > >>>>>>> I think IpCop definitely deserves a good presentation, it has been > > >>>>>>> quite the time since we had a firewall or networking presentation. > > >>>>>>> I would also go into installing extra modules onto IpCop for > > >>>>>>> content filtering and Parenting purposes, yep, kids are getting > > >>>>>>> older ... > > > > > > _______________________________________________ > > > clug-talk mailing list > > > [email protected] > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > **Please remove these lines when replying > > > > _______________________________________________ > > clug-talk mailing list > > [email protected] > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > > > > > > _______________________________________________ > > clug-talk mailing list > > [email protected] > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > -- pub 1024D/9091C422 02/05/2006 Mitchell Brown <[EMAIL PROTECTED]> Primary key fingerprint: 812B 94BC EA0D 345A CC1C 2ED9 F7F6 5CCF 9091 C422 _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
