From owner-freebsd-isp Thu Nov 12 12:20:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17128 for freebsd-isp-outgoing; Thu, 12 Nov 1998 12:20:53 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail1.dcomm.net (mail1.dcomm.net [209.63.174.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17121 for ; Thu, 12 Nov 1998 12:20:51 -0800 (PST) (envelope-from terry@dcomm.net) Received: from terry ([209.63.174.33]) by mail1.dcomm.net (Post.Office MTA v3.1 release PO205e ID# DIGITALCOMMUNICATIONS-1997LS) with SMTP id AAA154 for ; Thu, 12 Nov 1998 11:49:58 -0800 Message-Id: <4.1.19981112121648.00a813c0@mail1.dcomm.net> X-Sender: mail@mail.windjammer.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 12 Nov 1998 12:21:44 -0800 To: freebsd-isp@FreeBSD.ORG From: terry@dcomm.net (Terry Ewing) Subject: IP masqurading Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message