I wouldn't have a problem using the 675 to do the NAT, but I wouldn't use it as the firewall just because it's not powerful/configurable enough. I have a routed block so I'm not doing NAT, but none of my customers have any problems with it. Some of them are even doing some pretty complicated static NAT entries. Adam Maloney Systems Administrator Sihope Communications On Fri, 17 Nov 2000, 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 > > -- > Tim Wilson | Visit Sibley online: | Check out: > Henry Sibley HS | http://www.isd197.k12.mn.us/ | http://www.zope.org/ > W. St. Paul, MN | | http://slashdot.org/ > wilson at visi.com | <dtml-var pithy_quote> | http://linux.com/ > > _______________________________________________ > tclug-list mailing list > tclug-list at lists.real-time.com > https://mailman.real-time.com/mailman/listinfo/tclug-list >