From owner-freebsd-net@FreeBSD.ORG Sun May 1 08:52:48 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E72AF16A4CF for ; Sun, 1 May 2005 08:52:48 +0000 (GMT) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D38AD43D45 for ; Sun, 1 May 2005 08:52:47 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received-SPF: pass (mp2.macomnet.net: domain of maxim@macomnet.ru designates 127.0.0.1 as permitted sender) receiver=mp2.macomnet.net; client_ip=127.0.0.1; envelope-from=maxim@macomnet.ru; Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.12.11/8.12.11) with ESMTP id j418qkxm010451; Sun, 1 May 2005 12:52:46 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Sun, 1 May 2005 12:52:46 +0400 (MSD) From: Maxim Konovalov To: Tomasz Konefal In-Reply-To: <42748E82.4020403@gmail.com> Message-ID: <20050501125137.R10423@mp2.macomnet.net> References: <4272A118.4070603@vineyard.net> <42748E82.4020403@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: net@freebsd.org Subject: Re: netstat errors after upgrading 4.9 -> 5.3 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 May 2005 08:52:49 -0000 On Sun, 1 May 2005, 01:08-0700, Tomasz Konefal wrote: > Eric W. Bates wrote: > > [sigh] I have created the same problem on 2 machines. > > > > After an upgrade from 4.x to 5.3-p10 netstat will no longer display the > > routing table: > > > > ** root@fw ** ~ ** Fri Apr 29 16:59:37 > > # netstat -nr > > netstat: kvm not available > > Routing tables > > rt_tables: symbol not in namelist > > > > During the upgrade, I deleted all of /usr/src/*. And followed the rest of > > the procedures outlined in /usr/src/UPGRADING. I have also deleted /kernel* > > and /modules* (random thot that perhaps the wrong kvm's were being loaded). > > > > As far as I can tell, the netstat dump of the routing tables is the only > > failure. > > i have these exact same symptoms on a box i recently upgraded from 5.2.1 to > 5.4-RC3. admittedly, i don't know whether netstat worked on 5.2.1, but that > was a fresh install with only the security updates applied. IIRC you need mem_load="YES" io_load="YES" in /boot/loader.conf or the appropriate devices compiled in your kernel. -- Maxim Konovalov