netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: netdev@vger.kernel.org
Subject: Re: ipv6_addr_type() and mapped IPv4 loopback
Date: Mon, 03 Nov 2008 21:33:04 -0500	[thread overview]
Message-ID: <490FB460.2010501@hp.com> (raw)
In-Reply-To: <06930890-5BC3-4BE2-97CC-B3F6DF33B794@oracle.com>

Chuck Lever wrote:
> The __ipv6_addr_type() function does not recognize the mapped IPv4 
> loopback address:
> 
>    ::ffff:7f00:0001
> 
> as type IPV6_ADDR_LOOPBACK.  Is this intentional?

I would think that since the IPv6 loopback address is ::1, and 
ipv4-mapped is ::ffff:* that this would be IPV6_ADDR_MAPPED.  That's 
what RFC 4291 seems to say.

-Brian

  reply	other threads:[~2008-11-04  2:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 23:01 ipv6_addr_type() and mapped IPv4 loopback Chuck Lever
2008-11-04  2:33 ` Brian Haley [this message]
2008-11-04 16:44   ` Chuck Lever
2008-11-04 20:19     ` David Stevens
2008-11-04 21:16     ` Brian Haley
2008-11-04 21:33       ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=490FB460.2010501@hp.com \
    --to=brian.haley@hp.com \
    --cc=chuck.lever@oracle.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).