From owner-freebsd-hackers Tue Jul 8 21:35:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26671 for hackers-outgoing; Tue, 8 Jul 1997 21:35:05 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA26651 for ; Tue, 8 Jul 1997 21:34:58 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wloOF-0005Iy-00; Tue, 8 Jul 1997 21:30:07 -0700 Date: Tue, 8 Jul 1997 21:30:07 -0700 (PDT) From: Tom Samplonius To: Jaye Mathisen cc: hackers@freebsd.org Subject: Re: Not sure about this netstat -ss output In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 8 Jul 1997, Jaye Mathisen wrote: > I was messing around with Net.Medic's vitalsigns the other day, and it > told me that my DNS server was having problems responding. Net.Quack is junk. Since it runs in the background (and Win95 multitasking isn't so great), it will report all kinds of "slow downs" as you do stuff in the foreground. It will also misreport all kinds of connection problems. For example, if you disconnect the ethernet, it wil tell you the DNS server and gateway routers are down. But of course they aren't, the connection itself is down, but net.quack can't tell the difference! Plus, if you do a big download at the same moment that net.medic is "testing", it determine that all kinds of things are "slow". If you want to test DNS response time, use "dig" under unix. It gives you the DNS server response times in ms. Meanwhile, I'm still trying to figure out what units net.quack uses. Tom