Date: Tue, 7 Apr 2009 17:35:28 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: =?ISO-8859-15?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: svn-src-head@freebsd.org, Randall Stewart <rrs@FreeBSD.org>, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r190758 - head/sbin/route Message-ID: <alpine.BSF.2.00.0904071734460.45341@fledge.watson.org> In-Reply-To: <86prfoqvkp.fsf@ds4.des.no> References: <200904061009.n36A9K6l063517@svn.freebsd.org> <alpine.BSF.2.00.0904061139110.34905@fledge.watson.org> <86prfoqvkp.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <rwatson@FreeBSD.org> 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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0904071734460.45341>