The stalls are hardware or low-level driver, most likely...
Greg Alexander (galexand@sietch.bloomington.in.us)
Wed, 25 Jun 1997 07:07:24 -0500 (EST)
I had another linux box which has no obvious troubles do a tcpdump. He saw
plenty of packets like:
22:26:00.119361 irc1.phoenix.net.6668 >
sietch.sietch.bloomington.in.us.15431: P 100:194(94) ack 1 win 63488 (DF)
And he saw the SYN, SYNACK, and ACK at the beginning of my FTP connection:
22:28:56.408926 sietch.sietch.bloomington.in.us.ftp-data >
ezinfo.ucs.indiana.edu.3794: S 1597642555:1597642555(0) win 512
<mss 1460> [tos 0x8]
22:28:56.408926 ezinfo.ucs.indiana.edu.3794 >
sietch.sietch.bloomington.in.us.ftp-data: S 1386112000:1386112000(0) ack
1597642556 win 57344 <mss 1460> (DF)
22:28:56.408926 sietch.sietch.bloomington.in.us.ftp-data >
ezinfo.ucs.indiana.edu.3794: . ack 1 win 31744 (DF) [tos 0x8]
But when sietch started sending crap to ezinfo, as follows:
22:28:56.438926 sietch.sietch.bloomington.in.us.ftp-data >
ezinfo.ucs.indiana.edu.3794: . 1:1461(1460) ack 1 win 31744 (DF) [tos 0x8]
the packets never showed up on his tcpdump.
I'm fairly certain there's no hardware conflict, and I can't think
of any that could cause this problem. The card is a NIC2000 (crap clone) on
IRQ9, port 0x300. Again, other machines on the same ethernet hub have none
of these problems, and text transfers, like IRC and telnet seem to work
perfectly, and my machine seems to be able to send out ACK's just fine to
keep an ftp going quickly.
The monitoring machine, if it matters, has a 3c509.
Greg Alexander - http://www.cia-g.com/~sietch/
----
The law will never make men free; it is men who have got to make the
law free.
-- Henry David Thoreau