From owner-freebsd-hackers Wed Aug 27 17:29:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20894 for hackers-outgoing; Wed, 27 Aug 1997 17:29:42 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA20889 for ; Wed, 27 Aug 1997 17:29:38 -0700 (PDT) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id AAA02484; Thu, 28 Aug 1997 00:46:02 +0100 (BST) Message-Id: <199708272346.AAA02484@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: hackers@FreeBSD.ORG Subject: Re: FTP protocol questions (non-passive mode) In-reply-to: Your message of "Wed, 27 Aug 1997 16:34:07 MDT." <199708272234.QAA02520@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Aug 1997 00:46:01 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Can anyone explain to me the FTP 'Data' channel protocol? > > As I understand it, the client creates a socket, and the server binds to > it, and then the 'DATA' is sent to it. How does the server know which > port to bind on the client? Is there something obvious I don't > understand as to why they couldn't use the original 'channel'? > > Thanks for any help! The client, after creating a listening socket, sends a "PORT" command describing the IP & port that the server should bind to. It's done this way because it's easier. Ftp was designed way before things like firewalls made it a pain in the ass. > > Nate -- Brian , Don't _EVER_ lose your sense of humour....