From owner-freebsd-net@FreeBSD.ORG Wed Jul 6 22:39:26 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 BED3616A42D; Wed, 6 Jul 2005 22:39:26 +0000 (GMT) (envelope-from bms@spc.org) Received: from arginine.spc.org (arginine.spc.org [83.167.185.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 646BD43D45; Wed, 6 Jul 2005 22:39:25 +0000 (GMT) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id 68EF365435; Wed, 6 Jul 2005 23:39:24 +0100 (BST) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 91392-01-6; Wed, 6 Jul 2005 23:39:24 +0100 (BST) Received: from empiric.dek.spc.org (82-35-114-35.cable.ubr07.dals.blueyonder.co.uk [82.35.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id E511E65426; Wed, 6 Jul 2005 23:39:23 +0100 (BST) Received: by empiric.dek.spc.org (Postfix, from userid 1001) id 41C4469E7; Wed, 6 Jul 2005 23:39:07 +0100 (BST) Date: Wed, 6 Jul 2005 23:39:07 +0100 From: Bruce M Simpson To: gnn@freebsd.org Message-ID: <20050706223907.GM757@empiric.icir.org> Mail-Followup-To: gnn@freebsd.org, freebsd-net@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-net@freebsd.org Subject: Re: A bit of a route socket bug... 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: Wed, 06 Jul 2005 22:39:27 -0000 On Wed, Jul 06, 2005 at 11:46:00PM +0900, gnn@freebsd.org wrote: > As was reported in > http://www.freebsd.org/cgi/query-pr.cgi?pr=%0D%0A82974 [snip] This is definitely a bug, no question about it. RTM_CHANGE should let you change the next-hop, but not the destination or the netmask. [Sklower] As to how to fix it, I ENOTIME at the moment. :-( BMS