From owner-freebsd-questions Thu Jun 29 15:44:36 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail3.aracnet.com (mail3.aracnet.com [216.99.193.38]) by hub.freebsd.org (Postfix) with ESMTP id 3ECFC37C3FF for ; Thu, 29 Jun 2000 15:44:31 -0700 (PDT) (envelope-from hamellr@aracnet.com) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail3.aracnet.com (8.9.3/8.9.3) with ESMTP id PAA24090; Thu, 29 Jun 2000 15:44:34 -0700 Received: by shell1.aracnet.com (8.9.3) id PAA11322; Thu, 29 Jun 2000 15:44:37 -0700 Date: Thu, 29 Jun 2000 15:44:37 -0700 (PDT) From: Rick Hamell To: "Robert M. Shields" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: DSL / Routing / ipfw issues In-Reply-To: <395BCDE4.C4276DBA@bnswest.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For some reason USWorst won't support what I'm doing.. i.e. they want every machine > on my network to DHCP the 675 for a IP address and the 675 then DHCP's uswest.net's > server for an IP address. The 675 then provides NAT to the network. I think it might be best to have the 675 get it's DHCP from USW, set it up in Bridging mode then make your firewall/Natd computer hand out DHCP too. The only reason I'd do it differently would be to have the redundancy of a 2nd firewall. Actually you should dump US West anyways and find a provider who'll give you a static IP, even easier to setup and if you look around it'll cost only marginally more (like $2/month) If you go that route you can do what I did, set the 675 to bridge, assign the IP to your firewall machine's primary NIC. Use IPFW/Natd to create a gateway through your second NIC. It'll cost you an extra card but I think it'd be easier to setup. :) Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message