From owner-freebsd-net Tue Apr 3 22:25: 9 2001 Delivered-To: freebsd-net@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 63CCC37B720; Tue, 3 Apr 2001 22:25:02 -0700 (PDT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f345N4R04805; Wed, 4 Apr 2001 01:23:04 -0400 (EDT) (envelope-from matt@gsicomp.on.ca) Message-ID: <002001c0bcc7$a530b380$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Dan Debertin" , "Daehyun Yoon" Cc: "freebsd-questions@freebsd.org" , "freebsd-net@freebsd.org" References: Subject: Re: Slow netstat -r printout Date: Wed, 4 Apr 2001 01:25:20 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > It's taking so long because it's trying to do a DNS resolution of every IP > address that it prints. My guess is that @Home uses some non-registered > RFC1918 address space for its clients, so those addresses will never > resolve, and will take forever not doing so. The -n flag disables DNS > resolution, which is why it's so much faster. Do 'netstat -rn' once and record the RFC1918 addresses that @Home is using. Then add the appropriate entries to /etc/hosts. After that, you can do 'netstat -r' and the RFC1918 addresses will be resolved from /etc/hosts, which is much, much faster. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message