[3759] in linux-net channel archive
No subject found in mail header
daemon@ATHENA.MIT.EDU (Prof. Goerlich(ORACLE))
Fri Jul 19 18:01:31 1996
From: "Prof. Goerlich(ORACLE)" <goerlich@tfh-berlin.de>
Date: Thu, 18 Jul 1996 21:55:36 +0200 (MET DST)
To: ;@unlisted-recipients (no To-header on input)
Hi,
I posted the following message to comp.os.linux.networking, but I
haven't seen any response yet. So please let me tell it to you.
---------------------------------------------------------------
I'm using Linux 1.1.x, 1.2.x for years now for networking over PPP.
Last week I upgraded to Linux 2.0.1 and build the complete system new
with the actual software releases from the net.
Most of all works really fine, but I have problems uploading longer files
per ftp from my site to our highscool.
Of course I use the new pppd (2.2.0f). There's no problem on the IP/ICMP
level (ping, traceroute), telnet works without problems and I can use ftp
for downloading mbytes of data (e.g. linux-kernel).
I can also use ftp to send files with some hundred byte, sometimes some kbyte.
Transmitting a file of 1727 bytes was successful.
Suspicious data rates, mbytes per second, are shown - but it works.
Something goes wrong when I try to transmit longer files. I see all hash
marks at once - and ftp waits forever. It can not be interrupted with ^C,
but terminated with the kill command.
I got the kernel version 2.0.7 and installed it. The described effect remains
the same and a new effect occurs: killing the pppd with -INT sometimes leads
to a reboot :-(
After establishing the ftp connection, but before sending netstat -t shows
the following:
Proto Recv-Q Send-Q ... (State)
tcp -1 0 ...:ftp ESTABLISHED
When I try to send a file, another line occurs further:
tcp 0 17383 ...:20 FIN_WAIT1
Some seconds later:
tcp 0 16359 ...:20 FIN_WAIT1
After this, no change occurs. pppstat shows a decreasing number of
output bytes and then all nulls. On the server site, this one k
was successfully received.
I tried several ftp clients, with exactly the same effect. Therefore I think
that the problems is to be found in the TCP implementation.
Counterpart of my system at home is a Linux server with a kernel 1.1.8.
I'd like to upgrade our servers - but I must be sure that there are no
IP/PPP/TCP failures, because they are highly frequented.
The described effect occurs reproducible on my site. I would appreciate both
kind of messages: that it's reproducible on other sites too or that it must
be my specific problem. Please let me know.
Rene Goerlich goerlich@tfh-berlin.de
------------------------------------------------------------------------------
Thanks
Rene
