From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3281345f7d653afc3e8f3317d7a0bfed@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Fri, 20 Oct 2006 09:56:32 -0400
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: ip(2) man page: return code of parseip() and
	parsemaskip()
In-Reply-To: <ee9e417a0610200644o289c7ef2x91dbef158e915c96@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: ce895a8c-ead1-11e9-9d60-3106f5b1d025

i isn't that what i said?

but i think it's silly to differentiate between 192.168.0.1 and
::ffff:192.168.0.1 an ip6 address. that's like a c compiler declaring
0x3 != 3.

it's not a hard fix, can we just do it?

- erik

On Fri Oct 20 09:45:25 EDT 2006, rsc@swtch.com wrote:
> ::ffff:192.168.0.1 is *not* an IPv4 address, syntactically.
> IPv4 addresses don't have colons and hexadecimal in them.
> 
> It may be an IPv6 address that is semantically equivalent
> to an IPv4 address, but parseip is just a poor little parser.
> 
> Russ