From owner-freebsd-hackers@FreeBSD.ORG  Thu Apr 10 14:48:05 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1F02B37B401
	for <freebsd-hackers@freebsd.org>;
	Thu, 10 Apr 2003 14:48:05 -0700 (PDT)
Received: from mail6.bluewin.ch (mail6.bluewin.ch [195.186.4.229])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 59F6543F85
	for <freebsd-hackers@freebsd.org>;
	Thu, 10 Apr 2003 14:48:04 -0700 (PDT)
	(envelope-from cmathys@flippnet.org)
Received: from devil.bsd.local (62.203.66.147) by mail6.bluewin.ch (Bluewin AG
	6.7.016)        id 3E7194D500288007 for freebsd-hackers@freebsd.org;
	Thu, 10 Apr 2003 21:48:03 +0000
Date: Thu, 10 Apr 2003 23:48:00 +0200
From: Christoph Mathys <cmathys@flippnet.org>
To: freebsd-hackers@freebsd.org
Message-Id: <20030410234800.56980a69.cmathys@flippnet.org>
X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd4.8)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: mount_smbfs with diffrent destination-port
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 21:48:05 -0000

Hello

Just one question: Wouldn't it be possible to add a parameter or
something, that allows to tell 'mount_smbfs' which TCP-Port it tries to
connect to? I often forward smb-connections over ssh, and then the
destination-port is never 139. It would be very handy to have a
'clean' solution for this, not only an ugly, self-made hack. Or are
there specific reasons, why it's actually not possible to specify the
destination-port? Or am I just unable to do it right?

Regards
Chris

PS please include me in replies because I'm not on the list. thx!