From owner-freebsd-current@FreeBSD.ORG Mon Jul 28 09:15:26 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 97DFC37B401 for ; Mon, 28 Jul 2003 09:15:26 -0700 (PDT) Received: from silicon.nocdirect.com (silicon.nocdirect.com [66.227.56.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC97E43F93 for ; Mon, 28 Jul 2003 09:15:25 -0700 (PDT) (envelope-from PAHowes@Fair-ware.com) Received: from h00e081502390.ne.client2.attbi.com ([66.30.212.150] helo=beast) by silicon.nocdirect.com with asmtp (Exim 4.20) id 19hAeX-0007sy-Ft for freebsd-current@freebsd.org; Mon, 28 Jul 2003 11:15:13 -0500 From: "Paul A. Howes" To: Date: Mon, 28 Jul 2003 12:17:24 -0400 Organization: Fairware Message-ID: <000001c35523$bc8e8920$0200a8c0@beast> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - silicon.nocdirect.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - Fair-ware.com Subject: NATD question... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@fair-ware.com 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 16:15:27 -0000 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! -- Paul A. Howes