From owner-freebsd-isp Thu Nov 12 06:46:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13099 for freebsd-isp-outgoing; Thu, 12 Nov 1998 06:46:10 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13061 for ; Thu, 12 Nov 1998 06:46:06 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA207171875; Thu, 12 Nov 1998 09:44:35 -0500 Date: Thu, 12 Nov 1998 09:44:35 -0500 (EST) From: Bill Fumerola To: Lukman Salim Cc: FreeBSD-isp Subject: Re: Using NAT for ISP customer In-Reply-To: <364A4EC5.EBDD266B@usa.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 12 Nov 1998, Lukman Salim wrote: > I will be starting a cable-modem based ISP in the near future. Because > of the potential concurrent online user among the cable modem user would > be a lot greater than traditional ISP, I'm thinking of using local IP > with NAT for those who don't need real IP. Has anyone had any experience > with such a scheme using FreeBSD's natd? I know that some apps would not > run, but does the majority of Internet user use such software? If you have the IPs, you really should run public IP, though some may claim that using nat provides 'protection' or such, the same things can be achieved with a firewall. On the other hand, I run an office of 50+ clients through nat without a problem or large load on a p75. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message