All of lore.kernel.org
 help / color / mirror / Atom feed
From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
To: komurojun-mbn@nifty.com
Cc: bunk@stusta.de, jgarzik@pobox.com, viro@ftp.linux.org.uk,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [BUG KERNEL 2.6.20-rc1] ftp: get or put stops during file-transfer
Date: Sat, 30 Dec 2006 23:19:52 +0900 (JST)	[thread overview]
Message-ID: <20061230.231952.16573563.yoshfuji@linux-ipv6.org> (raw)
In-Reply-To: <20061230205931.9e430173.komurojun-mbn@nifty.com>

In article <20061230205931.9e430173.komurojun-mbn@nifty.com> (at Sat, 30 Dec 2006 20:59:31 +0900), Komuro <komurojun-mbn@nifty.com> says:

> > Do you see similar issue with other simple application?
> 
> sorry, I don't reproduce this problem on other application.

Can you reproduce it with other ftp client and/or server?


Anyway...

Please provide the output of "netstat -na" command during the
transfer, and the output of "lsmod | grep conntrack" (just for
sure).


More questions:

What kind of mode do you use? e.g. PORT/EPRT/LPRT/PASV/EPSV/LPSV

When the transfer get stuck, are other communication still working?

Are there any workaround?
e.g. stop-start vsftpd cycle, ifdown-ifup cycle, rmmod/insmod cycle etc.


Regards,

--yoshfuji

  reply	other threads:[~2006-12-30 14:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-17 12:27 [BUG KERNEL 2.6.20-rc1] ftp: get or put stops during file-transfer Komuro
2006-12-17  4:02 ` Al Viro
2006-12-17 14:23   ` Komuro
2006-12-18  3:01     ` Adrian Bunk
2006-12-18 20:55       ` Komuro
2006-12-23 11:17       ` Komuro
2006-12-30  9:50       ` Komuro
2006-12-30  1:23         ` YOSHIFUJI Hideaki / 吉藤英明
2006-12-30 11:59           ` Komuro
2006-12-30 14:19             ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2006-12-31  9:42               ` Komuro
2007-01-01 17:18               ` Komuro
2007-01-04 20:45               ` Komuro
2007-01-04 12:23                 ` Craig Schlenter
2007-01-09  1:24                   ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-09  5:11                     ` [PATCH] " Craig Schlenter
2007-01-09  5:22                       ` YOSHIFUJI Hideaki / 吉藤英明
2007-01-09  8:11                         ` David Miller
2007-01-09 22:01                   ` Komuro
     [not found]   ` <20070211101537.e40fa309.komurojun-mbn@nifty.com>
2007-02-11  1:56     ` [BUG] PATA_PCMCIA does not work Alan
2007-02-11 10:32       ` Haavard Skinnemoen
2007-02-11  2:40     ` Komuro
2007-02-18  2:09       ` Komuro
2007-02-21 15:37         ` Alan
2007-02-21 15:24           ` Manuel Lauss
2007-02-24  2:06           ` Komuro
2007-02-24 23:14           ` Komuro
2007-02-25  1:45             ` Jeff Garzik
2007-02-25  2:43               ` Komuro
2007-03-21  1:56           ` [PATCH]: pcmcia - spot slave decode flaws (for testing) Komuro
2007-03-17 13:00     ` [BUG] PATA_PCMCIA cmd port Komuro
2007-03-17 15:43       ` libata reports bogus addresses for everything (was PATA_PCMCIA cmd port) Alan Cox
2007-03-18  5:48         ` Tejun Heo
2007-03-17 16:10       ` [BUG] PATA_PCMCIA cmd port Jeff Garzik

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=20061230.231952.16573563.yoshfuji@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=jgarzik@pobox.com \
    --cc=komurojun-mbn@nifty.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.