Why not use both Cisco 675 _and_ Linux firewalling? In my home network, I'm using the 675's NAT to forward port 80's TCP traffic to a web server and everything else to a firewall. Because the web server is on the "DMZ" network (outside of the inner firewall), the machines behind the firewall are protected even if the web server gets 'sploited. Last December I put together a short presentation on the Linux Router Project (LRP) for TCLUG. The notes from that presentation, including some information about configuring the Cisco 675, are available at: http://joelschneider.org/lrp/ Although those notes definitely show signs of age, much of the information is still relevant/useful. A 486 firewall machine should have no trouble handling the bandwidth of a DSL line (mine's a 486/33). Joel Timothy Wilson wrote: > Hey everybody, > > DSL is finally available in my neighborhood and my line is scheduled > to go live 11/27. I thought this would be a good opportunity to > document the process and various do's and donts for people who would > like to have a simple network at home with DSL. The first question > is, should I stick to the Cisco 675's built-in NAT/firewall > capabilities or roll my own with a separate Linux box? I think it > would be instructive to consider some pros and cons. > > Here's my setup, which I think would be typically of the average, > non-professional Linux geek. I'll have two computers at home. The > first is a workstation dual-booting Linux and Win9x. The second is > Linux only and will provide whatever network services I need. At > this point I plan to have a simple Web page (I bought my own domain) > and provide listservs for family and friends. I can find an old 486 > (or better) to use as a dedicated firewall with no problem. > > Anyone care to contribute some thoughts on the 675 vs. Linux > firewall debate? > > -Tim