From owner-freebsd-questions Sat Sep 8 16:54:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from gahch.it.ca (gahch.it.ca [216.126.86.4]) by hub.freebsd.org (Postfix) with ESMTP id 61FB337B406 for ; Sat, 8 Sep 2001 16:54:44 -0700 (PDT) Received: (from paul@localhost) by gahch.it.ca (8.11.5/8.11.1) id f88NsVV77482; Sat, 8 Sep 2001 19:54:31 -0400 (EDT) (envelope-from paul) Date: Sat, 8 Sep 2001 19:54:31 -0400 From: Paul Chvostek To: Cherie&John Carri Cc: freebsd-questions@FreeBSD.ORG Subject: Re: slooooow ping reply and 60% packet loss on 3c509 Message-ID: <20010908195431.A55504@gahch.it.ca> References: <3.0.6.32.20010826190617.007a7c40@earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3.0.6.32.20010826190617.007a7c40@earthlink.net>; from cjcarri@earthlink.net on Sun, Aug 26, 2001 at 07:06:17PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiya. On Sun, Aug 26, 2001 at 07:06:17PM -0700, Cherie&John Carri wrote: > > End result? The FreeBSD machine now can ping the WinDoze machine with > response times ranging from one *second* to 60 *seconds* and a packet loss > of between 95% and 65%. The longer I let the pinging go on, the better the > packet loss number becomes, i.e it goes from 95% to 65% over several > minutes of pinging. I get similar behaviour on an ep which happens to be a 3C589D, which is a PCMCIA Etherlink III. Last week I posted here well as to freebsd-net, but so far I've had no responses. For more interesting information about what's going on, try using the tcpdump command (you need a bpf pseudo-device in your kernel). A command line of something like: # tcpdump -ne arp or icmp will let you see ... well, bizarre things which I described in great detail in freebsd-net on 2 September with the subject "laptop weirdness", because at the time I thought this could be a PCMCIA issue. > Anyone have any more suggestions? Someone mentioned verbally to me not long ago that this might have something to do with a "receive buffer bug" in the ep driver. I have not yet had a chance to research this and I am not C-savvy enough to poke at driver source myself, but ... receiving does indeed seem to be where I'm having a problem, so there's a chance that a newer cvsup will do the trick. But as I say, I haven't researched this. > Is it time to get another NIC, this one of the PCI persuasion? Probably not a bad idea, though I have 3C509's running on older builds of FreeBSD with no problems at all. In the past, 3C509's have been my *favourite* ISA NIC, because they autoconfigure so nicely. But it's very rare that I actually need to use ISA any more, and it would probably be wise of me to avoid situations where I'll need it in the future. ;-) -- Paul Chvostek Operations / Development / Abuse / Whatever vox: +1 416 598-0000 IT Canada http://www.it.ca/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message