public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Lambrecht Jürgen" <J.Lambrecht@TELEVIC.com>
To: Elad Yosef <elad.yosef@gmail.com>
Cc: "ecos-discuss@ecos.sourceware.org"
	<ecos-discuss@ecos.sourceware.org>,
	"ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>
Subject: Re: [ECOS] Help with validation of FTP client for LwIP
Date: Tue, 07 Jun 2011 07:23:00 -0000	[thread overview]
Message-ID: <4DEDD1D0.5050902@televic.com> (raw)
In-Reply-To: <BANLkTi=1jCRep8gLXoZBcZO0VAVyszYZPw@mail.gmail.com>

On 05/18/2011 07:18 AM, Elad Yosef wrote:
>
> Hi,
> I have ported the FTP client to work with LwIP and I want to 
> contribute it.
> The Client supports only IPv4
> The hostname must be the IP address of the server.
> The temporary buffer is allocated on the calling thread stack.
>
> temporary buffer size and the data port are configurable
>
> 1- Where should I post the file?
>
try ecos-devel
>
> 2 - I Did some tests on it and I found some problems that I think come
> from the IP stack:
>
> The Client IP is 192.168.1.222
> The Data port on client side is 20
> The FTP server is FileZilla on Windows
> I also tested with port 1030 and I get the same result
>
> - Get_File() one after another  – Failures from second try and on
> The FTP Server reports:  425 Can't open data connection.
> And The client is blocked on the accept() in receive_file()
>
maybe socket problem. Then increase the max. no. of sockets (no. of file 
descriptors)
there is now a more recent post of Stanislav Meduna
>
> - Put_File() one after another – constant errors
> The FTP Server reports: 426 Connection closed; transfer aborted.
> The client gets transfer failed, but not blocked
>
> - Get_File() and then Put_File()
> The Get passes
> The Put - fails
> The FTP Server reports: 425 Can't open data connection.
> And The client is blocked on the accept() in send_file()
>
> - Put File() and then Get File()
> The First Put fails with  426 Connection closed; transfer aborted.
> The First Get passes
> Second Put fails
> The FTP Server reports: 425 Can't open data connection.
> And The client is blocked on the accept() in send_file()
>
> The Result of the Put File is corrupted file (832 bytes and not 1008)
> Note that the client is blocked on the accept() even after the FTP
> server dropped the connection due to Time-Out
> I applied O_NONBLOCK attribute on the data_s and the result is the
> same (don’t think it works at all)
>
> Elad
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>


-- 
Jürgen Lambrecht
R&D Associate
Tel: +32 (0)51 303045    Fax: +32 (0)51 310670
http://www.televic-rail.com
Televic Rail NV - Leo Bekaertlaan 1 - 8870 Izegem - Belgium
Company number 0825.539.581 - RPR Kortrijk

           reply	other threads:[~2011-06-07  7:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <BANLkTi=1jCRep8gLXoZBcZO0VAVyszYZPw@mail.gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DEDD1D0.5050902@televic.com \
    --to=j.lambrecht@televic.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=elad.yosef@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).