From owner-freebsd-questions@FreeBSD.ORG Wed Aug 8 14:48:39 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFAB716A468 for ; Wed, 8 Aug 2007 14:48:39 +0000 (UTC) (envelope-from jdow@earthlink.net) Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by mx1.freebsd.org (Postfix) with ESMTP id A31FE13C4A8 for ; Wed, 8 Aug 2007 14:48:38 +0000 (UTC) (envelope-from jdow@earthlink.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=E/Lx8JwtpjmfCbyqE00Q5TUOmMhlPH5xILaI0KjqKWX7Oz1SeOOCSzcrhdk3Ykk1; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP; Received: from [68.183.128.206] (helo=wednesday) by elasmtp-mealy.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IImLd-0001LX-9V for freebsd-questions@freebsd.org; Wed, 08 Aug 2007 10:17:17 -0400 Message-ID: <03ab01c7d9c6$d33cd600$0225a8c0@wednesday> From: "jdow" To: References: <64c038660708071210w1950ccccwda1bb8464587d1de@mail.gmail.com> <8cb6106e0708071331v47c866beh2296110c75a846c2@mail.gmail.com> Date: Wed, 8 Aug 2007 07:17:16 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-ELNK-Trace: bb89ecdb26a8f9f24d2b10475b57112081bea3e5d4036f0fa0460e56192b03cff966978d6047df59350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 68.183.128.206 Subject: Re: Bizzare routing table entry. 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: Wed, 08 Aug 2007 14:48:40 -0000 From: "Josh Carroll" >> root# route delete 0&0xc0a80132 >> >> [1] 37343 >> route: writing to routing socket: No such process >> delete net 0: not in table >> 0xc0a80132: Command not found. >> [1] + Exit 1 route delete 0 > >> root# route delete 0&0xc0a80132 >> >> [1] 37343 >> route: writing to routing socket: No such process >> delete net 0: not in table >> 0xc0a80132: Command not found. >> [1] + Exit 1 route delete 0 > > I've no idea whether that is a valid route or not, but the reason > you're getting that funkiness is that the shell is eating the & and > thinks you are sending the route process to the background. Try: > > route delete '0&0xc0a80132' There goes 192.168.1.50. {^_-} Joanne