From owner-freebsd-stable Tue Mar 18 15:42:25 2003 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 BBC8437B401 for ; Tue, 18 Mar 2003 15:42:24 -0800 (PST) Received: from strangelove.glynjones.com (63-212-172-50.glynjones.com [63.212.172.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5543143FA3 for ; Tue, 18 Mar 2003 15:42:22 -0800 (PST) (envelope-from dave@glynjones.com) Received: from (cts21612080135.cts.com) [216.120.80.135] by strangelove.glynjones.com with esmtp (Exim 3.34 ) id 18vQir-000CZI-00; Tue, 18 Mar 2003 15:42:21 -0800 Subject: portmap on all tcp addresses? From: Dave Byrne To: freebsd-stable@freebsd.org Content-Type: text/plain Organization: Message-Id: <1048031312.9815.18.camel@dave.glynjones.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2- Date: 18 Mar 2003 15:48:32 -0800 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a reason that portmap(8) has to listen on INADDR_ANY for tcp connections? the -h option specifies which ip addresses to bind to for UDP requests, but regaurdless of what is specified, portmap will bind to all addresses for TCP connections. I looked at portmap.c in /usr/usr.sbin/portmap and its an easy patch to fix this, which leads me to believe this was by design. Will forcing portmap to only bind to certain addresses on multi-homed hosts break its functionality? Thanks Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message