From owner-freebsd-net@FreeBSD.ORG Fri Sep 7 15:57:17 2007 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2173D16A417 for ; Fri, 7 Sep 2007 15:57:17 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 0641B13C467 for ; Fri, 7 Sep 2007 15:57:16 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 5AB3A2C37B; Fri, 7 Sep 2007 11:57:16 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 07 Sep 2007 11:57:16 -0400 X-Sasl-enc: hNL98o1Yt0xuFuxFV1su/9ZTYrkzn0H09diJBub6YMgh 1189180636 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id D75453D51; Fri, 7 Sep 2007 11:57:15 -0400 (EDT) Message-ID: <46E174DB.8070004@FreeBSD.org> Date: Fri, 07 Sep 2007 16:57:15 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.4 (X11/20070630) MIME-Version: 1.0 To: Tom Judge References: <46E11515.8090007@tomjudge.com> In-Reply-To: <46E11515.8090007@tomjudge.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: Strange behaviour of route command X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Sep 2007 15:57:17 -0000 Tom Judge wrote: > Hi, > > While making some changes to the routing table on one of our routers > today I noticed that "route add" was showing some strange behaviour. > When adding a route for 128/8 to the table rather than adding > 128.0.0.0/8 it would add 0.0.0.0/8, however adding 10/9 works correctly. > > Is this a bug in route or the routing table? Run 'route -nv monitor' in another shell while you do this and post the output to this list so someone can get more of a handle on it. BMS