From owner-freebsd-stable@FreeBSD.ORG Sun Nov 21 20:03:05 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 986EC16A4CE for ; Sun, 21 Nov 2004 20:03:05 +0000 (GMT) Received: from mail.vtec.ipme.de (Ad3e8.a.pppool.de [213.6.211.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id B607843D39 for ; Sun, 21 Nov 2004 20:03:04 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from [192.168.201.3] (unknown [192.168.201.3]) by bellona.sz.vwsoft.com (Postfix) with ESMTP id 2DE0DB804; Sat, 20 Nov 2004 15:56:16 +0100 (CET) Message-ID: <419F5B12.8010805@vwsoft.com> Date: Sat, 20 Nov 2004 15:56:18 +0100 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041103 Thunderbird/0.9 Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stable@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com cc: suutari@iki.fi Subject: natd same_ports X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Nov 2004 20:03:05 -0000 Hi folks! Running natd under 5.3-RELEASE I've seen natd doesn't touch the port numbers - natd let packets pass with the same port numbers. I've tried setting the -same_ports natd option to no but natd behaviour doesn't change. From what I've found in the natd sources (/usr/src/sbin/natd/natd.c) the command line option for -same_ports never gets processed. It's my believe there's been some code forgotten in natd.c but I'm not quite sure. Would please the maintainer or a core member check the natd.c source for the processing and correct defaults of natds' -same_ports option? Function ParseOption doesn't show any processing of this parameter. From my experience with natd under 5.3 I would say, natd isn't working as expected for the source port numbering. Thanks, Volker -- GPG/PGP fingerprint: FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1