[ previous ] [ next ] [ threads ]
 From:  "Bosse Timothy" <Bosse dot tf at mellon dot com>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] FreeBSD 5.2
 Date:  Mon, 5 Apr 2004 17:26:01 -0400
The problem with 5.2 is that it is considered an "unstable" branch of
FreeBSD.  Unstable meaning that it requires testing and potential
bug-fixes.  As such, it should not be considered for production use.  I
believe it is Manuel's goal to provide a stable, secure and mature
firewall solution.  As such, FreeBSD 5.2 does not meet the requirements
of stable, secure or mature by even FreeBSD standards, let alone
Manuel's standards.  I would have to agree with both FreeBSD and
Manual's opinion of 5.2 especially when considered for a firewall

If you want m0n0 to run 5.2, you (or somebody else) will need to make it
happen.  One of the many possible issues you could run into might
include possible configuration incompatibilities between 4.9 and 5.2.
You might also see some apps called differently, etc...

-----Original Message-----
From: Dave C. [mailto:mono at comm dot it] 
Sent: Monday, April 05, 2004 4:59 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] FreeBSD 5.2

> It doesn't look like we can do this anytime soon, because FreeBSD 5.2 
> is very far from being as stable as 4.9, as I recently had to find out

> again. Besides, it's also still a good deal slower. 5.x doesn't

May I ask what are the problems related to 5.2 ? 
If I understand correctly, ipfw and dummynet should be quite similar, 
and the same should be true for the other userspace processes.

I'm asking because I was going to start a personal port to 5.2 to see
how well it could perform, but perhaps I should ask who has done it


To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch 
The information contained in this e-mail may be confidential and is intended solely for the use of
the named addressee. 
Access, copying or re-use of the e-mail or any information contained therein by any other person is
not authorized. 
If you are not the intended recipient please notify us immediately by returning the e-mail to the