From owner-freebsd-stable Mon Jan 8 7:19:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 5635E37B400 for ; Mon, 8 Jan 2001 07:19:34 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f08FLDi31948; Mon, 8 Jan 2001 09:21:13 -0600 (CST) (envelope-from jlemon) Date: Mon, 8 Jan 2001 09:21:13 -0600 (CST) From: Jonathan Lemon Message-Id: <200101081521.f08FLDi31948@prism.flugsvamp.com> To: jeroen@vangelderen.org, stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? X-Newsgroups: local.mail.freebsd-stable In-Reply-To: Organization: Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Moreover, a tcpdump on both sides of a stalled TCP connection seems to >indicate that no packets get lost. I do an scp on hayek (problematic >machine) to fetch a file from keynes. It looks like hayek simply stops >responding to incoming packets and the TCP connection stalls until keynes >gives up and sends RST. > >I've stuck both tcpdumps for > hayek# scp me@keynes.ai:./bla.tgz /dev/null >at > http://vangelderen.org/~gelderen/tcpdump-hayek (problematic machine) > http://vangelderen.org/~gelderen/tcpdump-keynes (has the file) > >If someone with a clue could have a look over them? I'm sure some netstat >information could be useful but I don't know which bits to include. It looks like 'hayek' is refusing to accept one of the segments that 'keynes' is transmitting. The segment arrives at the machine, but 'hayek' never sends an ACK. I'd look at 'netstat -s' and see whether any of the 'bad checksum' counters are set, if so, then something is corrupting the packets. Does this happen even if you connect the machines back to back (with a crossover cable?) -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message