Path: utzoo!attcan!uunet!husc6!uwvax!umn-d-ub!rutgers!gatech!uflorida!haven!purdue!decwrl!ucbvax!VAX.FTP.COM!joel
From: joel@VAX.FTP.COM (Joel Gartland)
Newsgroups: comp.protocols.tcp-ip
Subject: (none)
Message-ID: <8810181555.AA01394@vax.ftp.com>
Date: 18 Oct 88 15:55:10 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 25

Date: Tue, 18 Oct 88 11:13:27 EDT
From: joel@vax.ftp.com (Joel Gartland)
Message-Id: <8810181513.AA01177@vax.ftp.com>
To: tcp-ip@src-nic.arpa
Subject: ftp option PASV
Cc: joel@vax.ftp.com


Well, 
	I've been mucking with the passive option and have found a machine that
at least thinks it understands the option. Me, I'm not so sure.
	When I send it the PASV command, the server responds:

	    227 Data transfers will passively listen to 128,127,2,150,p1,p2

(p1,p2 being the port), which makes sense except that 128,127,2,150 is
*my* address.
	Now, as I read the RFC(959), shouldn't the server send it's own
address and port it's listening on? If I'm misunderstanding, please let me 
know; if I'm correct, can anyone tell me of a host that does implement PASV
correctly so I can test it??

					Thanks much
						Joel Gartland
						FTP Software