From owner-freebsd-questions@FreeBSD.ORG Tue Nov 21 16:30:41 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8B8916A47E for ; Tue, 21 Nov 2006 16:30:41 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp1.utdallas.edu (smtp1.utdallas.edu [129.110.10.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 355D543D7F for ; Tue, 21 Nov 2006 16:30:17 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp1.utdallas.edu (Postfix) with ESMTP id CD9A7388E37 for ; Tue, 21 Nov 2006 10:30:35 -0600 (CST) Date: Tue, 21 Nov 2006 10:27:56 -0600 From: Paul Schmehl To: UNIX - Questions Message-ID: <556BBD73A562FFF4DCEC1E21@utd59514.utdallas.edu> In-Reply-To: <45632057.2080706@joeholden.co.uk> References: <2A97A175E0A3D7A039D1AA98@paul-schmehls-powerbook59.local> <456297CE.9030103@joeholden.co.uk> <3974ECF15478CC1AAEE19789@utd59514.utdallas.edu> <45632057.2080706@joeholden.co.uk> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========52477ECA6C82E750CDF9==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Totally stumped - very long post X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2006 16:30:41 -0000 --==========52477ECA6C82E750CDF9========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Tuesday, November 21, 2006 15:50:47 +0000 Joe Holden=20 wrote: >>> >> Care to give me a bigger hint? I'm not a routing guru. >> >> I tried this with no luck: >> route delete 66 >> route: writing to routing socket: No such process >> delete host 66: not in table >> Thanks, Joe. I'll keep this in mind for next time. I ended up logging in=20 through the console (using DRAC) and flushing the routing table. Then I=20 restarted networking, and everything looked normal, but I couldn't access=20 remotely, so I rebooted the box. Now everything is normal again. Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========52477ECA6C82E750CDF9==========--