From owner-freebsd-isp Thu Nov 12 13:33:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24317 for freebsd-isp-outgoing; Thu, 12 Nov 1998 13:33:13 -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 NAA24304 for ; Thu, 12 Nov 1998 13:33:10 -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 AA050256285; Thu, 12 Nov 1998 16:31:25 -0500 Date: Thu, 12 Nov 1998 16:31:25 -0500 (EST) From: Bill Fumerola To: Terry Ewing Cc: freebsd-isp@FreeBSD.ORG Subject: Re: IP masqurading In-Reply-To: <4.1.19981112121648.00a813c0@mail1.dcomm.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, Terry Ewing wrote: > People here are thinking of putting our co-located computers behind a > FreeBSD IPFW firewall. At the same time they were thinking of giving the > co-located servers 192.168.x.x IP's so they can be removed if we go through > renumbering. We'd just masquerade the real IP to the 192.168 IP in the > firewall. > > Can anyone arm me with a good reason why we shouldn't do this? Because giving (paying) colocated server internal IPs is degrading the QoS. Some UDP and other programs don't work with it. - 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