From owner-freebsd-current@FreeBSD.ORG Mon Jul 28 12:52:36 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 106CE37B401 for ; Mon, 28 Jul 2003 12:52:36 -0700 (PDT) Received: from wasley.bl.mmtr.or.jp (wasley.bl.mmtr.or.jp [210.228.173.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D88A43FA3 for ; Mon, 28 Jul 2003 12:52:34 -0700 (PDT) (envelope-from rushani@bl.mmtr.or.jp) Received: (qmail 9863 invoked from network); 29 Jul 2003 04:52:32 +0900 Received: from unknown (HELO localhost) (202.229.16.132) by mx.bl.mmtr.or.jp with SMTP; 29 Jul 2003 04:52:32 +0900 Date: Tue, 29 Jul 2003 04:52:30 +0900 (JST) Message-Id: <20030729.045230.58434271.rushani@bl.mmtr.or.jp> To: PAHowes@Fair-ware.com From: Hideyuki KURASHINA In-Reply-To: <000001c35523$bc8e8920$0200a8c0@beast> References: <000001c35523$bc8e8920$0200a8c0@beast> X-PGP-Public-Key: http://www.bl.mmtr.or.jp/~rushani/rushani.asc X-PGP-Fingerprint: A052 6F98 6146 6FE3 91E2 DA6B F2FA 2088 439A DC57 X-URL: http://www.bl.mmtr.or.jp/~rushani/ X-Mailer: Mew version 4.0.54 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: FreeBSD-current@FreeBSD.org Subject: Re: NATD question... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jul 2003 19:52:36 -0000 Hi, >>> On Mon, 28 Jul 2003 12:17:24 -0400, "Paul A. Howes" said: > All, > > I am trying to redirect a port on my FreeBSD 5.1-based firewall to an > internal machine. My natd configuration contains a directive: > > redirect-port 192.168.x.x:http 5555 > > I performed a "kill -HUP" on the natd process, but it doesn't work. I can > verify that the internal Web server is functional, and accessible to the > internal network. I even added ipfw rules to allow for traffic on port > 5555, but still nothing. > > Am I missing something obvious here? Thanks! That's a wrong directive. Use ``redirect_port''. ^ -- rushani