From: "Bart Smit" <bit at pipe dot nl>
> On 14 feb , at 10:20, Jonathan De Graeve wrote:

>> I propose to implement this in a different project m0n0cache

Any word on this?  You havn't finished this in your extra free time? ;-) 
Frankly, with RADIUS and this obsession you have with having a life, I don't 
see how you could do another major project like m0n0cache. (You need to give 
everything to the ungratefull wretches here!)

> Well, *if* there is going to be something like that, I think it  should 
> include more of the stuff that refuses to go into m0n0wall and  for which 
> a separate box is typically needed (e.g. also MTA  functionality, ntpd, 
> radius...). That would suggest a name such as  m0n0proxy.

NTP, IDA, syslog...  Of course that means we can't make it as simple to 
config as m0n0wall.  It would be quite a major project.  And we would still 
need hooks in m0n0wall for most of it to work well.

> But frankly, there is already something like it: m0n0bsd. Grab it and 
> install whatever you want. Any extra effort is better spent getting 
> m0n0bsd up-to-date (haven't seen much happen there lately), instead  of 
> launching a separate project.

Not only is m0n0bsd way behind, it doesn't have the cool config of m0n0wall. 
Check out FreeNAS at http://www.freenas.org/ for a cool example.  However, 
it is not a small project, and is relatively simple by comparison with what 
you propose.

Lets scale back...  How about adding proxy hooks into m0n0wall?  What would 
it take to transparently capture and rout a single port to an internal 
server?  One page with port numbers, and you can set up mail, web, or new 
app dejure?

                        Lee