From owner-freebsd-questions Wed Jul 28 15:38:28 1999 Delivered-To: freebsd-questions@freebsd.org Received: from deva.iclick.com (deva.iclick.com [209.176.19.254]) by hub.freebsd.org (Postfix) with ESMTP id 9C49214EEF for ; Wed, 28 Jul 1999 15:38:25 -0700 (PDT) (envelope-from dans@iclick.com) Received: from iclick.com ([209.176.19.42]) by deva.iclick.com (8.9.3/8.9.1) with ESMTP id SAA10791 for ; Wed, 28 Jul 1999 18:36:43 -0400 (EDT) Message-ID: <379F950C.A330E248@iclick.com> Date: Wed, 28 Jul 1999 18:41:00 -0500 From: Dan Simoes X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.ORG" Subject: need final help with natd/firewall Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem we are seeing right now is this: A box known on the private side as 192.168.100.210 runs a web server. This is being translated via natd to a public address of 199.176.19.210. We added the interface on the firewall with: ifconfig xl0 inet 199.176.19.210 255.255.255.255 alias And it works OK. Two oddities: - on the private side box, it cannot reach its public address of 209.176.19.210, though it can access any other box on that net - on the firewall, we can ping 192.168.100.210 but not the 199 version of it, nor can we telnet to port 80 on that box. ipfw rules are not a factor here as we've turned them off temporarily. We've tried adding routes, etc, running natd on xl1 as well as xl0, to no avail. Any thoughts? Thanks. -- Dan Simoes iClick, Inc. email:dans@iclick.com 410 Saw Mill River Road, LL135 voice:914-693-0837 Ardsley, NY 10502 fax:914-693-1055 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message