I switched from smoothwall to m0n0wall because I could get my firewall 
to get an IP on WAN when the firewall rebooted.  If the cable modem and 
firewall rebooted at the same time I would get DHCP WAN IP like it was 
supposed to but if I did an update or a change to the box that required 
a reboot, it would not renew the IP - upon switching m0n0wall it has 
worked flawlessly for me.  After the initial setup and reboot, I had my 
m0n0wall up for 150+ days before rebooting it.with not ever a problem. 
Only reason I rebooted it then was because I upgraded to the newly 
released firmware.
My only desire to see in the future is wireless G support and VPN that 
has support for NAT-T such as OpenVPN.  But PPTP VPN works great if you 
are not behind a router that blocks GRE traffic like my office server does.

Ken.

Brian McEntire wrote:
> I'm very impressed with Monowall and will probably replace my home f/w
> (Smoothwall Express) with it. I am using the DHCP server on Smoothwall 
> and I
> see Monowall has that functionality listed as one of it's features.
>
> Has anyone made this switch? Are there any features you used in 
> Smoothwall
> that you had to implement somewhere else on your network b/c they weren't
> part of Monowall? I'm just looking out for gotchas that might not be 
> obvious
> at first glance.
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.392 / Virus Database: 268.5.6/338 - Release Date: 5/12/2006
>