From owner-svn-src-all@FreeBSD.ORG Tue Apr 7 16:35:29 2009 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0FF91065672; Tue, 7 Apr 2009 16:35:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 768998FC17; Tue, 7 Apr 2009 16:35:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 02BB446BC5; Tue, 7 Apr 2009 12:35:29 -0400 (EDT) Date: Tue, 7 Apr 2009 17:35:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= In-Reply-To: <86prfoqvkp.fsf@ds4.des.no> Message-ID: References: <200904061009.n36A9K6l063517@svn.freebsd.org> <86prfoqvkp.fsf@ds4.des.no> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="621616949-2117236345-1239122129=:45341" Cc: svn-src-head@freebsd.org, Randall Stewart , svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r190758 - head/sbin/route X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Apr 2009 16:35:30 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --621616949-2117236345-1239122129=:45341 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Tue, 7 Apr 2009, Dag-Erling Smørgrav wrote: > Robert Watson writes: >> Does this maintain compatibility for people who may still mysteriously >> be specifying class-based IPs and netmasks in configuration files? If >> not, this should not be MFC'd... > > Here's the really ugly part... > > % ping 10 > PING 10 (0.0.0.10): 56 data bytes > % ping 10.1 > PING 10.1 (10.0.0.1): 56 data bytes > % ping 10.1.1 > PING 10.1.1 (10.1.0.1): 56 data bytes > > This makes no sense at all today, but we can't fix it, because it's the > documented and standard-mandated behavior of inet_pton(3) and, if I'm not > mistaken, getaddrinfo(3). Sadly, I'm familiar with this already :-(. However, for the time being, I'm less concerned about ugliness, and more concerned about breaking existing scripts and tools. Robert N M Watson Computer Laboratory University of Cambridge --621616949-2117236345-1239122129=:45341--