[Freedos-user] FTP Server testing needed

[Michael B. Brutman]

I have made a large round of improvements to the FTP server in mTCP and 
I am looking for a little testing help with it.  If you have a few spare 
moments over the next day or two just try to connect to it and browse 
the file structure.  Using a few different clients will help me shake 
out any new bugs.  Upload some relevant files if you are adventurous.

It can be reached at ftp://96.42.66.188:2021/ - if you are using a 
browser that URL should work as-is.  For command line clients just take 
note of the non-standard port number.  The FTP server is running on the 
slowest machine that I have, which is a PCjr; it if runs well on that, 
it will run well on anything you probably have.  (If you want to see the 
actual machine it is running on look at THISPCJR.JPG in the root directory.)

Changes for this version include:

- scanning for valid drive letters at startup to avoid errors when 
touching floppy drives
- a major rework of directory handling if you are not an anonymous 
user.  Drive letters now look like part of a normal Unix path so that 
the smarter FTP clients don't get confused by the drive letters and path 
delimiters.
- The flow control problem with FileZilla is now understood and fixed
- The wrong file date problem with FileZilla is fixed
- There is a new "message of the day" feature for putting up special 
notices at login time
- The local user interface is redesigned and little more friendly
- Better error checking on the password file

All if this will be part of the next mTCP release, which I'm targeting 
for the next week.  Getting some testing time on it is a good thing ...


Thanks in advance,
Mike



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Florian Xaver]

Works with Firefox.

Bye
 Flo

El Thu Sep 29 15:37:45 2011, Michael B. Brutman escribió:
>
> I have made a large round of improvements to the FTP server in mTCP and
> I am looking for a little testing help with it.  If you have a few spare
> moments over the next day or two just try to connect to it and browse
> the file structure.  Using a few different clients will help me shake
> out any new bugs.  Upload some relevant files if you are adventurous.
>
> It can be reached at ftp://96.42.66.188:2021/ - if you are using a
> browser that URL should work as-is.  For command line clients just take
> note of the non-standard port number.  The FTP server is running on the
> slowest machine that I have, which is a PCjr; it if runs well on that,
> it will run well on anything you probably have.  (If you want to see the
> actual machine it is running on look at THISPCJR.JPG in the root directory.)
>
> Changes for this version include:
>
> - scanning for valid drive letters at startup to avoid errors when
> touching floppy drives
> - a major rework of directory handling if you are not an anonymous
> user.  Drive letters now look like part of a normal Unix path so that
> the smarter FTP clients don't get confused by the drive letters and path
> delimiters.
> - The flow control problem with FileZilla is now understood and fixed
> - The wrong file date problem with FileZilla is fixed
> - There is a new "message of the day" feature for putting up special
> notices at login time
> - The local user interface is redesigned and little more friendly
> - Better error checking on the password file
>
> All if this will be part of the next mTCP release, which I'm targeting
> for the next week.  Getting some testing time on it is a good thing ...
>
>
> Thanks in advance,
> Mike
>
>
>
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user

-- 
 

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Single Stage to Orbit]

On Thu, 2011-09-29 at 08:37 -0500, Michael B. Brutman wrote:
> I have made a large round of improvements to the FTP server in mTCP and 
> I am looking for a little testing help with it.  If you have a few spare 
> moments over the next day or two just try to connect to it and browse 
> the file structure.  Using a few different clients will help me shake 
> out any new bugs.  Upload some relevant files if you are adventurous.

Uploads to incoming doesn't quite work for me. Here's the transcript of
my session:

$ ftp -n -p 96.42.66.188 2021
Connected to 96.42.66.188 (96.42.66.188).
220 mTCP FTP Server
ftp> user anonymous
331 Anonymous ok, send your email addr as the password
Password: 
230-Welcome to Mike's PCjr running the mTCP FTP server!  This machine
230-was released by IBM in 1983 and features a 4.77Mhz Nec V20 CPU (an
230-upgrade from the standard 8088), an XT-IDE modified for the PCjr, a
230-Western Digital 8003 Ethernet card, and a 20GB Maxtor hard drive.
230-It is running DOS 3.3 so most of the hard drive is not being used.
230-Please poke around, test things out, report any problems you might
230-have, and enjoy!  Incoming files may be deposited at /incoming, and
230-you can create subdirectories there if needed.  -Mike
230 User logged in
ftp> put alex_was_here
local: alex_was_here remote: alex_was_here
227 Entering Passive Mode (96,42,66,188,11,76)
550 You need to be in the /INCOMING directory to upload
ftp> cd incoming
250 CWD command successful
ftp> put alex_was_here
local: alex_was_here remote: alex_was_here
227 Entering Passive Mode (96,42,66,188,8,221)
550 Bad path
ftp> dir
425 Transfer already in progress
Passive mode refused.
ftp> ls
425 Transfer already in progress
Passive mode refused.
ftp> bye
221 Server closing connection

Hope this helps
-- 
Tactical Nuclear Kittens



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Robert Riebisch]

Michael B. Brutman wrote:

> I have made a large round of improvements to the FTP server in mTCP and 
> I am looking for a little testing help with it.  If you have a few spare 
> moments over the next day or two just try to connect to it and browse 
> the file structure.  Using a few different clients will help me shake 
> out any new bugs.  Upload some relevant files if you are adventurous.

Fine with Total Commander 7.55a.

Robert Riebisch
-- 
BTTR Software
http://www.bttr-software.de/

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Robert Riebisch]

Single Stage to Orbit wrote:

> ftp> put alex_was_here
   ^
I guess LFNs are not supported.

Robert Riebisch
-- 
BTTR Software
http://www.bttr-software.de/

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[David C. Kerber]

A quick test with ws_ftp PRO seems to be fine.
 

> -Original Message-
> From: Michael B. Brutman [mailto:mbbrut...@brutman.com] 
> Sent: Thursday, September 29, 2011 9:38 AM
> To: freedos-user@lists.sourceforge.net
> Subject: [Freedos-user] FTP Server testing needed
> 
> 
> I have made a large round of improvements to the FTP server 
> in mTCP and I am looking for a little testing help with it.  
> If you have a few spare moments over the next day or two just 
> try to connect to it and browse the file structure.  Using a 
> few different clients will help me shake out any new bugs.  
> Upload some relevant files if you are adventurous.
> 
> It can be reached at ftp://96.42.66.188:2021/ - if you are 
> using a browser that URL should work as-is.  For command line 
> clients just take note of the non-standard port number.  The 
> FTP server is running on the slowest machine that I have, 
> which is a PCjr; it if runs well on that, it will run well on 
> anything you probably have.  (If you want to see the actual 
> machine it is running on look at THISPCJR.JPG in the root directory.)
> 
> Changes for this version include:
> 
> - scanning for valid drive letters at startup to avoid errors 
> when touching floppy drives
> - a major rework of directory handling if you are not an 
> anonymous user.  Drive letters now look like part of a normal 
> Unix path so that the smarter FTP clients don't get confused 
> by the drive letters and path delimiters.
> - The flow control problem with FileZilla is now understood and fixed
> - The wrong file date problem with FileZilla is fixed
> - There is a new "message of the day" feature for putting up 
> special notices at login time
> - The local user interface is redesigned and little more friendly
> - Better error checking on the password file
> 
> All if this will be part of the next mTCP release, which I'm 
> targeting for the next week.  Getting some testing time on it 
> is a good thing ...
> 
> 
> Thanks in advance,
> Mike
> 
> 
> 
> --
> 
> All the data continuously generated in your IT infrastructure 
> contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data 
> and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Single Stage to Orbit]

On Thu, 2011-09-29 at 16:27 +0200, Robert Riebisch wrote:
> Single Stage to Orbit wrote:
> 
> > ftp> put alex_was_here
>^
> I guess LFNs are not supported.

I guess I've forgotten DOS can be quite anal about LFNs ;)
-- 
Tactical Nuclear Kittens



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Single Stage to Orbit]

On Thu, 2011-09-29 at 16:27 +0200, Robert Riebisch wrote:
> Single Stage to Orbit wrote:
> 
> > ftp> put alex_was_here
>^
> I guess LFNs are not supported.

Works fine for 8.3 files:

$ ftp -n -p 96.42.66.188 2021
Connected to 96.42.66.188 (96.42.66.188).
220 mTCP FTP Server
ftp> user anonymous
331 Anonymous ok, send your email addr as the password
Password: 
230-Welcome to Mike's PCjr running the mTCP FTP server!  This machine
230-was released by IBM in 1983 and features a 4.77Mhz Nec V20 CPU (an
230-upgrade from the standard 8088), an XT-IDE modified for the PCjr, a
230-Western Digital 8003 Ethernet card, and a 20GB Maxtor hard drive.
230-It is running DOS 3.3 so most of the hard drive is not being used.
230-Please poke around, test things out, report any problems you might
230-have, and enjoy!  Incoming files may be deposited at /incoming, and
230-you can create subdirectories there if needed.  -Mike
230 User logged in
ftp> cd incoming
250 CWD command successful
ftp> put alexwas.ere
local: alexwas.ere remote: alexwas.ere
227 Entering Passive Mode (96,42,66,188,9,203)
150 BINARY type File STOR started
226 Transfer complete
ftp> bye
221 Server closing connection

-- 
Tactical Nuclear Kittens



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[escape]

Works with Filezilla/Linux, lukemftp, ncftp, but fails to retrieve
directory listing in Midnight Commander, Krusader and Dolphin - upon
connection shows empty filelist. Also I was unable to delete file
TEST.TXT uploaded to /INCOMING, despite its rwxrwxrwx permissions, but I
suspect this could be some restriction in server config:

Command:DELE TEST.TXT
Response:   550 permission denied


On 29.09.11 16:37, Michael B. Brutman wrote:
> 
> I have made a large round of improvements to the FTP server in mTCP and 
> I am looking for a little testing help with it.  If you have a few spare 
> moments over the next day or two just try to connect to it and browse 
> the file structure.  Using a few different clients will help me shake 
> out any new bugs.  Upload some relevant files if you are adventurous.
> 
> It can be reached at ftp://96.42.66.188:2021/ - if you are using a 
> browser that URL should work as-is.  For command line clients just take 
> note of the non-standard port number.  The FTP server is running on the 
> slowest machine that I have, which is a PCjr; it if runs well on that, 
> it will run well on anything you probably have.  (If you want to see the 
> actual machine it is running on look at THISPCJR.JPG in the root directory.)
> 
> Changes for this version include:
> 
> - scanning for valid drive letters at startup to avoid errors when 
> touching floppy drives
> - a major rework of directory handling if you are not an anonymous 
> user.  Drive letters now look like part of a normal Unix path so that 
> the smarter FTP clients don't get confused by the drive letters and path 
> delimiters.
> - The flow control problem with FileZilla is now understood and fixed
> - The wrong file date problem with FileZilla is fixed
> - There is a new "message of the day" feature for putting up special 
> notices at login time
> - The local user interface is redesigned and little more friendly
> - Better error checking on the password file
> 
> All if this will be part of the next mTCP release, which I'm targeting 
> for the next week.  Getting some testing time on it is a good thing ...
> 
> 
> Thanks in advance,
> Mike
> 
> 
> 
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
> 

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Michael Brutman]

I'll have to install those clients and try them.  But it is most likely to be 
something specific about them.

Anonymous users can't delete what they (or anybody else) upload.  So that was 
expected behavior.

Mike

escape  wrote:

>Works with Filezilla/Linux, lukemftp, ncftp, but fails to retrieve
>directory listing in Midnight Commander, Krusader and Dolphin - upon
>connection shows empty filelist. Also I was unable to delete file
>TEST.TXT uploaded to /INCOMING, despite its rwxrwxrwx permissions, but I
>suspect this could be some restriction in server config:
>
>Command:   DELE TEST.TXT
>Response:  550 permission denied
>
>
>On 29.09.11 16:37, Michael B. Brutman wrote:
>> 
>> I have made a large round of improvements to the FTP server in mTCP and 
>> I am looking for a little testing help with it.  If you have a few spare 
>> moments over the next day or two just try to connect to it and browse 
>> the file structure.  Using a few different clients will help me shake 
>> out any new bugs.  Upload some relevant files if you are adventurous.
>> 
>> It can be reached at ftp://96.42.66.188:2021/ - if you are using a 
>> browser that URL should work as-is.  For command line clients just take 
>> note of the non-standard port number.  The FTP server is running on the 
>> slowest machine that I have, which is a PCjr; it if runs well on that, 
>> it will run well on anything you probably have.  (If you want to see the 
>> actual machine it is running on look at THISPCJR.JPG in the root directory.)
>> 
>> Changes for this version include:
>> 
>> - scanning for valid drive letters at startup to avoid errors when 
>> touching floppy drives
>> - a major rework of directory handling if you are not an anonymous 
>> user.  Drive letters now look like part of a normal Unix path so that 
>> the smarter FTP clients don't get confused by the drive letters and path 
>> delimiters.
>> - The flow control problem with FileZilla is now understood and fixed
>> - The wrong file date problem with FileZilla is fixed
>> - There is a new "message of the day" feature for putting up special 
>> notices at login time
>> - The local user interface is redesigned and little more friendly
>> - Better error checking on the password file
>> 
>> All if this will be part of the next mTCP release, which I'm targeting 
>> for the next week.  Getting some testing time on it is a good thing ...
>> 
>> 
>> Thanks in advance,
>> Mike
>> 
>> 
>> 
>> --
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>> 
>
>--
>All the data continuously generated in your IT infrastructure contains a
>definitive record of customers, application performance, security
>threats, fraudulent activity and more. Splunk takes this data and makes
>sense of it. Business sense. IT sense. Common sense.
>http://p.sf.net/sfu/splunk-d2dcopy1
>___
>Freedos-user mailing list
>Freedos-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/freedos-user
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Michael Brutman]

It's DOS so the filename was in error, but it should have aborted the data 
transfer fully.  I'll look into that after work - for now stick to 8.3 style 
filenames.

Single Stage to Orbit  wrote:

>On Thu, 2011-09-29 at 08:37 -0500, Michael B. Brutman wrote:
>> I have made a large round of improvements to the FTP server in mTCP and 
>> I am looking for a little testing help with it.  If you have a few spare 
>> moments over the next day or two just try to connect to it and browse 
>> the file structure.  Using a few different clients will help me shake 
>> out any new bugs.  Upload some relevant files if you are adventurous.
>
>Uploads to incoming doesn't quite work for me. Here's the transcript of
>my session:
>
>$ ftp -n -p 96.42.66.188 2021
>Connected to 96.42.66.188 (96.42.66.188).
>220 mTCP FTP Server
>ftp> user anonymous
>331 Anonymous ok, send your email addr as the password
>Password: 
>230-Welcome to Mike's PCjr running the mTCP FTP server!  This machine
>230-was released by IBM in 1983 and features a 4.77Mhz Nec V20 CPU (an
>230-upgrade from the standard 8088), an XT-IDE modified for the PCjr, a
>230-Western Digital 8003 Ethernet card, and a 20GB Maxtor hard drive.
>230-It is running DOS 3.3 so most of the hard drive is not being used.
>230-Please poke around, test things out, report any problems you might
>230-have, and enjoy!  Incoming files may be deposited at /incoming, and
>230-you can create subdirectories there if needed. -Mike
>230 User logged in
>ftp> put alex_was_here
>local: alex_was_here remote: alex_was_here
>227 Entering Passive Mode (96,42,66,188,11,76)
>550 You need to be in the /INCOMING directory to upload
>ftp> cd incoming
>250 CWD command successful
>ftp> put alex_was_here
>local: alex_was_here remote: alex_was_here
>227 Entering Passive Mode (96,42,66,188,8,221)
>550 Bad path
>ftp> dir
>425 Transfer already in progress
>Passive mode refused.
>ftp> ls
>425 Transfer already in progress
>Passive mode refused.
>ftp> bye
>221 Server closing connection
>
>Hope this helps
>-- 
>Tactical Nuclear Kittens
>
>
>
>--
>All the data continuously generated in your IT infrastructure contains a
>definitive record of customers, application performance, security
>threats, fraudulent activity and more. Splunk takes this data and makes
>sense of it. Business sense. IT sense. Common sense.
>http://p.sf.net/sfu/splunk-d2dcopy1
>___
>Freedos-user mailing list
>Freedos-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/freedos-user
--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Michael B. Brutman]

Alex,

Interesting bug.  I thought that this would be an easy catch, but it is 
more subtle than I thought.  I can't recreate it here.

Your client sends a PASV command before attempting to put the file, 
which is the correct behavior.  Under normal circumstances that just 
tells the server to start listening on port for an incoming connection 
from your client.  If a PORT command or another PASV command is issued 
that listening socket gets tossed away.

In this case it is behaving like your client actually started connecting 
on that socket, or even connected.  So there is an open data connection 
but no data flowing.  And the next command (the dir or ls) requires a 
data connection, but it can't just blast the existing one.  Hence the 
error message.

I'm not sure what's going on, but I suspect that after about 10 seconds 
it would go away if it was just a connection that was starting.  At 
worst case that session is hosed up until that user logs out.

I'm going to keep looking at it, but it's not obvious.  It's also 
probably been in the code since day one - you just got lucky enough to 
hit it.


Mike


On 9/29/2011 9:20 AM, Single Stage to Orbit wrote:
> On Thu, 2011-09-29 at 08:37 -0500, Michael B. Brutman wrote:
>> I have made a large round of improvements to the FTP server in mTCP and
>> I am looking for a little testing help with it.  If you have a few spare
>> moments over the next day or two just try to connect to it and browse
>> the file structure.  Using a few different clients will help me shake
>> out any new bugs.  Upload some relevant files if you are adventurous.
> Uploads to incoming doesn't quite work for me. Here's the transcript of
> my session:
>
> $ ftp -n -p 96.42.66.188 2021
> Connected to 96.42.66.188 (96.42.66.188).
> 220 mTCP FTP Server
> ftp>  user anonymous
> 331 Anonymous ok, send your email addr as the password
> Password:
> 230-Welcome to Mike's PCjr running the mTCP FTP server!  This machine
> 230-was released by IBM in 1983 and features a 4.77Mhz Nec V20 CPU (an
> 230-upgrade from the standard 8088), an XT-IDE modified for the PCjr, a
> 230-Western Digital 8003 Ethernet card, and a 20GB Maxtor hard drive.
> 230-It is running DOS 3.3 so most of the hard drive is not being used.
> 230-Please poke around, test things out, report any problems you might
> 230-have, and enjoy!  Incoming files may be deposited at /incoming, and
> 230-you can create subdirectories there if needed.-Mike
> 230 User logged in
> ftp>  put alex_was_here
> local: alex_was_here remote: alex_was_here
> 227 Entering Passive Mode (96,42,66,188,11,76)
> 550 You need to be in the /INCOMING directory to upload
> ftp>  cd incoming
> 250 CWD command successful
> ftp>  put alex_was_here
> local: alex_was_here remote: alex_was_here
> 227 Entering Passive Mode (96,42,66,188,8,221)
> 550 Bad path
> ftp>  dir
> 425 Transfer already in progress
> Passive mode refused.
> ftp>  ls
> 425 Transfer already in progress
> Passive mode refused.
> ftp>  bye
> 221 Server closing connection
>
> Hope this helps



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Single Stage to Orbit]

On Thu, 2011-09-29 at 14:14 -0500, Michael B. Brutman wrote:

> Interesting bug.  I thought that this would be an easy catch, but it is 
> more subtle than I thought.  I can't recreate it here.
> 
> Your client sends a PASV command before attempting to put the file, 
> which is the correct behavior.  Under normal circumstances that just 
> tells the server to start listening on port for an incoming connection 
> from your client.  If a PORT command or another PASV command is issued 
> that listening socket gets tossed away.
> 
> In this case it is behaving like your client actually started connecting 
> on that socket, or even connected.  So there is an open data connection 
> but no data flowing.  And the next command (the dir or ls) requires a 
> data connection, but it can't just blast the existing one.  Hence the 
> error message.
> 
> I'm not sure what's going on, but I suspect that after about 10 seconds 
> it would go away if it was just a connection that was starting.  At 
> worst case that session is hosed up until that user logs out.
> 
> I'm going to keep looking at it, but it's not obvious.  It's also 
> probably been in the code since day one - you just got lucky enough to 
> hit it.

In case you want to replicate it on Linux, it's part of the netkit
(http://www.hcs.harvard.edu/~dholland/computers/netkit.html)
distribution, release 0.17. It's one of the oldest ftp clients out
there. 
-- 
Tactical Nuclear Kittens



--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] FTP Server testing needed

[Ulrich Hansen]

Hi Michael!

I played around with Filezilla and Cyberduck on my Mac. Everything 
seems to work OK for me. That's really great! Made some test 
directories and browsed through them. I forgot that DOS directory 
names are limited to 8 letters, got a "550 Bad path" and nearly blamed 
you for it ;-)

I also tried Datalight sockets on FreeDOS (Virtualbox) which seem to 
work OK too - but it was just a short login and I am not really 
familiar with the client.

A DOS client that connected but was unable to browse was Minuet. I 
have placed the screenshot of the error message here:


ftp://96.42.66.188:2021/INCOMING/TEST/TEST1/TEST11/TEST112/TEST1122

:-)

Google Chrome v14 (Mac) seems to be unable to open the ftp adress 
above, while Firefox 7 (Mac) and 6.02 (Ubuntu 11.04) didn't have a 
problem.

Your site also worked OK with AndFTP on my crappy Sony Ericsson Xperia 
with Android 2.1. I switched to the directory above and downloaded the 
image.

All in all it was a lot of fun.
Thanks.
Ulrich




Am 29.09.11 21:14, schrieb Michael B. Brutman:
>
> Alex,
>
> Interesting bug.  I thought that this would be an easy catch, but it is
> more subtle than I thought.  I can't recreate it here.
>
> Your client sends a PASV command before attempting to put the file,
> which is the correct behavior.  Under normal circumstances that just
> tells the server to start listening on port for an incoming connection
> from your client.  If a PORT command or another PASV command is issued
> that listening socket gets tossed away.
>
> In this case it is behaving like your client actually started connecting
> on that socket, or even connected.  So there is an open data connection
> but no data flowing.  And the next command (the dir or ls) requires a
> data connection, but it can't just blast the existing one.  Hence the
> error message.
>
> I'm not sure what's going on, but I suspect that after about 10 seconds
> it would go away if it was just a connection that was starting.  At
> worst case that session is hosed up until that user logs out.
>
> I'm going to keep looking at it, but it's not obvious.  It's also
> probably been in the code since day one - you just got lucky enough to
> hit it.
>
>
> Mike
>
>
> On 9/29/2011 9:20 AM, Single Stage to Orbit wrote:
>> On Thu, 2011-09-29 at 08:37 -0500, Michael B. Brutman wrote:
>>> I have made a large round of improvements to the FTP server in mTCP and
>>> I am looking for a little testing help with it.  If you have a few spare
>>> moments over the next day or two just try to connect to it and browse
>>> the file structure.  Using a few different clients will help me shake
>>> out any new bugs.  Upload some relevant files if you are adventurous.
>> Uploads to incoming doesn't quite work for me. Here's the transcript of
>> my session:
>>
>> $ ftp -n -p 96.42.66.188 2021
>> Connected to 96.42.66.188 (96.42.66.188).
>> 220 mTCP FTP Server
>> ftp>   user anonymous
>> 331 Anonymous ok, send your email addr as the password
>> Password:
>> 230-Welcome to Mike's PCjr running the mTCP FTP server!  This machine
>> 230-was released by IBM in 1983 and features a 4.77Mhz Nec V20 CPU (an
>> 230-upgrade from the standard 8088), an XT-IDE modified for the PCjr, a
>> 230-Western Digital 8003 Ethernet card, and a 20GB Maxtor hard drive.
>> 230-It is running DOS 3.3 so most of the hard drive is not being used.
>> 230-Please poke around, test things out, report any problems you might
>> 230-have, and enjoy!  Incoming files may be deposited at /incoming, and
>> 230-you can create subdirectories there if needed.   -Mike
>> 230 User logged in
>> ftp>   put alex_was_here
>> local: alex_was_here remote: alex_was_here
>> 227 Entering Passive Mode (96,42,66,188,11,76)
>> 550 You need to be in the /INCOMING directory to upload
>> ftp>   cd incoming
>> 250 CWD command successful
>> ftp>   put alex_was_here
>> local: alex_was_here remote: alex_was_here
>> 227 Entering Passive Mode (96,42,66,188,8,221)
>> 550 Bad path
>> ftp>   dir
>> 425 Transfer already in progress
>> Passive mode refused.
>> ftp>   ls
>> 425 Transfer already in progress
>> Passive mode refused.
>> ftp>   bye
>> 221 Server closing connection
>>
>> Hope this helps
>
>
>
> --
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fr