Hi Carl - I didn't apparently explain well in the first post - tcpdump
is running on the same machine as the ftp client that wedges. Since
tcpdump sees and decodes the packets they are getting to the machine -
just not to the ftp client, like so;
remote ftp server -> DSL circuit -> LM 6.1 box run
> Carl - no, the ftp transfer hangs happens both as a client and a server.
> The tcpdump trace in the original post is with the machine as a client.
I meant that particular machine, which served as client in some of your latter
tests. You indicated it =doesn't= see packets it should at times. A
Carl - no, the ftp transfer hangs happens both as a client and a server.
The tcpdump trace in the original post is with the machine as a client.
I thought about it being a NIC issue (or a module / driver NIC issue)
but since tcpdump sees the packet(s) isn't the packet being passed up
through the
I had a problem similar to this, and it turned out to be a bad SMC NIC. I
say hardware on the client. Does the server machine work OK as client to a
public server?
--
Carl A. Cook
quantumATaugustmailDOTcom
Sign the petition at http://www.libranet.com/petition.html
Help bring us more Linux Drive
Hi - I recently attempted to transfer a +50MB file over my DSL line to
my 6.1 box. The transfer repeatedly hung somewhere after 8MB was
transfered. I may get 9MB, I may get 40MB before the hang. The partial
file is not resumable once the hang happens. Whereas if I kill the
client during the trans
